I am new to creating Drools DRL files and I have been using business-central packaged in latest jbpm artifacts as standalone web interface. I find the IDE for writing drl non intuitive, and validation errors keep stacking up even when I change the code and fix it. Is there a better development tool where we can check syntax, correct compilation errors and also debug/troubleshoot the rule definitions
Short answer is no, there's no such a thing.
The closest thing you could use with latest Drools is the Eclipse Plugin, but you have to use the 7.46.0.Final (source)
With IDEA community you can debug Drools' execution but you cannot put breakpoint inside consequences, and you don't get syntax highlighting out of the box.
The IDEA Ultimate has a Drools plugin but it's not developed by the same team (it's made by JetBrains instead of Red Hat) and has plenty of bugs (source) I'm not even sure it's maintained anymore.
Kogito has some VS Code tooling but still doesn't support DRL files.
Related
I am facing issue with TypeScript in IntelliJ IDEA Community Edition. Earlier I have used IntelliJ IDEA Ultimate Edition for Angular 2 development and it works fine.
This is the error I am getting in my .ts file. Plus there is no intelliSense. Is this feature unavailable in the Community Edition?
As zhengyue pointed out in comments, apparently you are using the "TypoScript" plugin, which is not a "Typescript" plugin.
I made the same mistake. And I also had the same problems that you experienced. Personally I thought it was the #Component decorator that messed things up. But it was zhengyue who pointed out I was using the wrong plugin.
The conclusion for me was that it was better to search for a good alternative. Because I still want to develop my back-end in Java, I wanted ...
something that integrates with IntelliJ as good as possible
but still something which is powerful.
At first I tried eclipse, and found powerful tools in their marketplace, which turned out to be commercial products and expired after 8 days.
Secondly, I downloaded "Visual Studio Code", (not to be confused with the full blown Visual Studio). It is FAST and user-friendly. It launches in less than 2 seconds on my system. And it has great plugins, which allow me to use code completion and refacturing tools. Here is the list of plugins I have installed:
As you can see, there is a plugin that makes you use the keybindings of intellij.
In IntelliJ I configured my ".ts" files to be handled as javascript files. Because it's better than nothing.
I work in IntelliJ all day when I'm working on the Java back-end, and thanks to the javascript features, I still have some (limited) code highlights for the Angular front-end as well. But, when I want to edit something in the front end, I use Visual Studio Code. To make this a smooth transition, I right-click inside the file and use an external tool configuration:
Inside my IntelliJ I configured the root of the angular project as a module. Then the configuration of this external tool looks like this:
This allows me to switch from IntelliJ to Visual Studio code in about 2 seconds, and immediately to the correct line in the correct file.
So, that's what my free Angular-with-Java-combo development workspace looks like.
JavaScript/TypeScript support and many other features are not available in the Community Edition.
Problem
I'm trying to create a Play 2.3.1 framework, because the lack of info on how to get started with 2.4.3. So much has changed apparently that the tutorials on youtube is useless and I can't get it to work.
Question
How do I do this?
I have tried to go to https://www.playframework.com/download#older-versions but all versions yield the same link to https://downloads.typesafe.com/typesafe-activator/1.3.6/typesafe-activator-1.3.6-minimal.zip
which installs the newest playframework 2.4.3.
Please say that someone knows how to do this?
Also, why should I bother using 2.4.3 > 2.3.1 if I'm only creating a simple mobile app w/database? Security reasons or just "easier"?
Same question for IntelliJ 14 > IntelliJ 13 ?
https://www.playframework.com/download#older-versions is the link you need.
When you're new to Play! it can be quite confusing so I think a bit of terminology is needed.
SBT - Scala build tool. This is a build tool that is baked into every Play! project but totally independent of Play! framework, ie. many Scala projects use this to manage their builds without ever using Play! It's just the Scala equivilient of a Maven, Gradle or Ant. Nothing special.
Activator - This is Play!'s commandline, like a build-tool++. It's commandline tool with a superset of the SBT commands clean compile etc etc, with Play! specific ones like 'new', 'run'. It actually just amounts to not much more than a script (.sh/.bat) which bootstraps SBT and some extra goodness for running play commands. In earlier versions like 1.x this command was named play. Version 2.x was a practically a re-write so you can ignore all related advice.
Play - the playframework itself is just a regular jar (and all its dependencies). It is declared in the project/plugins.sbt
So the reason all the download links point to activator-1.3.6 is because that is just the version of the commandline tool. This will default to latest: 2.4.x.
When you perform an activator new you get a choice of templates. If you REALLY REALLY want to use 2.3.x you could choose this template when prompted hello-play-2_3-scala.
But I don't suggest you do that because:
The documentation for 2.4.x is comprehensive and there are walkthrough guides, it won't take any longer than a youtube video.
There are bug fixes and new features in 2.4.x
2.4.x introduced dependency injection which means it will be harder to upgrade once you'ved developed everything in 2.3x.
Apart from dependency injection most stuff works the same in 2.4.x
Intellij:
Use 14. Play support is improving all the time. If you can use the Early Access Program and the latest version of the Scala plugin.
Don't run 'activator idea' - this is deprecated. File -> open project from Intellij should be enough.
I am a beginner with Play2 framework and Scala.
Is there any eclipse play 2 plugin available?
If yes, then please provide me the link for the same. I am used to Eclipse and have never used Scala before;hence in a confusion like how and where to start from. Looking at the Play2 Doc, sems like working in command prompt IDE which is very difficult (though I have tried yet)
Please let me know the eclipse plugin for Play2 or some other IDE helpful for this.
Regards,
There in no plugin as such for Eclipse.
Play! framework has nice set of tools for doing tasks such as following
creating new play project
running the project
deployment of the application
doing the continuous testing mode etc
Trust me, once you start using this, you gonna love it.
Beside you do not require any experience in Scala, as for Play framework you can use Java language, if you are comfortable with it (you can choose Java template while creating new Play project )
and also you can use IDE for syntax highlighting , code completion etc
I had a brief try of Play development using Eclipse and the Scala Plugin. I personally found it awkward and not terribly helpful. (The errors which the IDE reported were not always the same as the ones that the Play compiler reported, for example.)
I’ve had a lot more joy using the Intellij IDEA IDE, with its Scala plugin. As with Eclipse the current version of IDEA does not have specific support for Play Framework 2, but it does have specific support for Scala.
The next version of Intellij IDEA, v12, will have explicit support for Play Framework 2: http://www.jetbrains.com/idea/nextversion/index.html#Frameworks_Support (but only in the paid-for ‘Ultimate’ edition, not in the free ‘Community’ edition).
I am experimenting with Groovy Griffon development and I am wondering what IDE to use.
I am trying to use NetBeans 6.5, and I found this post
https://blogs.oracle.com/geertjan/entry/notes_on_converting_netbeans_grails
essentially it describes forking the NetBeans trunk and hacking the Grails support; I was hoping for something more lightweight.
Are there any simple tools to create eclipse, netbeans or pom.xml's from Griffin Apps?
Or is it best to use a simple text editor?
There is a NetBeans Griffon plugin already available at http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp?pluginid=18664
Griffon apps have some rudimentry hooks already for IDE integration.
First, a .classpath and .project file are generated that mark the expected source and test directories for Eclipse. Both IntelliJ and NetBeans have importers for these eclipse files (and they work, I use them regularly).
Second, Griffon 0.1.1 adds more targets to the parallel build.xml so that more of the common scripts can be used as though they were ant tasks (run-app, compile, debug-app, etc.)
Third, there is some better IDE support in the works form some of the IDE vendors. As mentioned in the article you linked because Griffon is grails derived it is fairly easy to re-purpose existing Grails support. IntelliJ has the only specific tracked feature request I am aware of.
IntelliJ Idea has very good Griffon support.
This question usually comes with a next question:
How to debug Griffon?
Just in case someone still requires a helping hand trying to figure out how to debug Griffon in Eclipse/STS I've written a simple step by step guide to get it done:
http://ivo43.blogspot.com/2012/02/debugging-griffon-in-eclipsests.html
Hope it helps someone someday, :D
PD: I've tried Netbeans and even though it looks great am still with STS, call me a maniac!
My company starts a new project next week. We have planned to develop the application with eclipse rcp. The build process should be fully automated, so we're prepared to set up a continuous integration environment (e.g. Continuum). For the build-automation-part I intended to use maven2, because I want use its dependency management.
I have used maven2 for a small old-style java project, but have never set up maven for using it with eclipse rcp.
What's the best way to do this? Basic concepts? Common traps? Are any tutorials or book's around there? The tutorials and informations I found, seemed outdated or incomplete.
PS: The main project will be divided into sub-project's (plug-in's). But I think this is typical for eclipse rcp projects.
You should take a look at Tycho:
the-future-of-maven-osgi-join-the-tycho-users-mailing-list
the-next-generation-of-build-tools-for-eclipse-plugins-and-rcp-applications
Like most Maven questions, this is solved by a link to a plug-in:
"pde-maven-plugin"
Other advice:
use the assembly plug-in to build
the update site
consider using hudson rather than
Continuum
I've been battling maven2/Eclipse RCP integration for some time. The key is not so much getting your setup right: You can get it to work - eventually - by reverse-engineering Eclipse's build process in maven.
In my experience, the hard part is keeping everything up to date. Every time Eclipse revs their libs, you'll find yourself re-writing a bunch of pom files for that newest RCP widget or SWT lib. Naturally, CI helps with this somewhat. The problem is that Eclipse and maven are very particular about the way they do the business of building, and their approaches are quite different. To make matters worse, PDE dev (and Eclipse dev, more generally) is powered by a lot of wizard code, which is sometimes quite opaque as to what's happening behind the scenes.
The question you really need to ask yourself is if it's worth the effort. In my particular case, I believe it has been. (CI is too good to live without.) But the trade-off is that you may find yourself being the "build guy", which can take valuable time away from actual development, which is probably what you enjoy most.
I've got recently the same problem : build eclipse RCP application through continuous integration.
I haven't applied them yet but I've found some interesting articles :
Here's the documentation for Tycho
Building Eclipse Plugins with Maven 2 on eclipse.org
Build Eclipse RCP products using Maven 2 - how hard can it be? from Immo Hüneke's blog
Here's an article about PDE build automation
Here's a shell script to automate JUnit test launch