I am looking for a code coverage plugin for netbeans that supports JDK 7, Netbeans 7.4 and Module development. The closest one is TikiOne JaCoCoverage but it does not support module development.
Is there any plugin for that combination? How can i find any solution?
I am not sure but you may need to change or add some segment of the plugin sections in the POM.xml. It seems like this was the way when creating maven projects.
Related
Got a simple question. Is it possible to use GWT versions 2.6+ with NetBeans 8.0, taking into consideration, that the last GWT version gwt4nb plugin for NB 8.0 checks for is 2.5?
Or does that mean, that I can only use features from GWT under 2.5 versions with 2.6+ libs?
Yes, you can use NetBeans to develop GWT, and you don't need any plugin.
If you delegate the whole project configuration to maven or gradle (or buck, bazel…) then you can use any IDE. This is the best approach, and the project will work seamlessly also in your CI and using the command line. NetBeans maven integration is excellent and currently, maven is the easiest way to manage a GWT project.
Clone any "modern" project and try it out in your NetBeans installation to see if it satisfies you. Also, take a look at this tutorial for a more detailed explanation.
I'm maintaining a parent pom for my team which will provide the latest compatible version of various maven plugins per the JDK that the project uses. Sometimes if a project utilizes an older version of Java (like 1.5) maven will fail due to a plugin requiring a newer version. Is there a way to get a map of a given plugin and see what the minimum java version is for said plugin? I was thinking there was some sort of report or something that would show me that, but I'm not seeing anything.
What about: https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-prerequisites.html Apart from that on every plugin page you can find the goals page which contains the information you need. One more thing if you are using not the most uptodate versions all older versions pages are available where you can look at which version which JDK versions uses. It shouldn't be problem to write some kind of script to programmatically extract the information of the older plugins. The above site contains the informations of the uptodate plugins.
Apart from that plugin version selection basead on JDK version is not a good idea. The plugins have only a minimum version for JDK they need to run with. Apart from that they run on all versions (already on JDK 9 with one exception)...Furthermore plugins might require a minimum Maven version to run with which is either Maven 2.2.1 or Maven 3.0+ which shouldn't a problem.
You should define your plugins versions simply based on problems you might have but i would recommend to keep uptodate with your plugins.
If you need running you build with JDK 6 for example, but you use Maven 3.3.X which needs JDK 7 to run you can achieve this by using toolchain to handle this situation.
In theory this shouldn't be an issue. Maven will use the Java version you run it with, so the plugin's dependency will be satisfied, independent of the project's language level. Just make sure your devs are using a current version.
Example: running Maven with Java 8 will satisfy the dependency of a Plugin that requires Java 8, independent of the project's source and target level.
(With dependencies it's more complicated, I am afraid, but since you are not actually coding against your plugins, you should be fine)
OS: 64x Windows 7
IDE: IntelliJ IDEA 12.1.4
After activating the plugins log4j and IdeaSpring, IntelliJ wants to restart itself. While restarting IntelliJ, there are 2 messages which prompt that either log4j and IdeaSpring couldn't be initialized.
How can I set up my IntelliJ that those 2 plugins work?
Messages:
Plugin IdeaSpring failed to initialize and will be disabled:
Could not load API connector for IntelliJ IDEA build #IC-129.713
Please restart IntelliJ IDEA.
and
Plugin IdeaSpring failed to initialize and will be disabled:
com.intellij.javaee.ExternalResourceManager.addStdResource(Ljava/lang/String;Ljava/langString;Ljava/lang/Class;)V
Please restart IntelliJ IDEA.
IdeaSpring is a third-party plugin which wasn't adapted to the API changes in IDEA 9 (note that it hasn't been updated since 2006) Please report the problem to the plugin vendor (http://www.yanaware.com/)
BTW, Intellij Idea has its own Spring support - why do you need using third-party plugins?
The answer to the question is: you shouldn't. The plugin you're trying to install IdeaSpring) is from 2006. You should use the Ultimate Version of IntelliJ, which has excellent Spring support. The free version doesn't.
The same for the other plugin; it's also very old, and probably doesn't work anymore. I'm not sure if you need that one, since IntelliJ also has support for most of the XML log4j provides.
I'd say: try the Ultimate version, and either buy it or try to get a free version if you're working on a Open Source project.
Alternatively, if you can't spare the money, you could have a look at SpringSource Tool Suite, which is pretty decent too, but at least it doesn't cost money, and it does have support for Spring.
Objective is to set up developer environment for:
JBoss 7.1, Maven 3.04, Drools 5.3.0 , eclipse platform 3.72 (IDE for Java EE 1.4.2...)
Goal is to be able to follow tutorials and learn Drools using latest available versions of software - without running into version incompatibilities between different components.
Seem to be getting a lot of "missing reference" type errors in eclipse package explorer after compiling code examples in maven. I am a newbie so apologies in advance if this is an obvious question.
Examples appear to compile in maven fine, but when trying to integrate with Eclipse ide am having a lot of reference errors. The version of Java SDK on my PC is 1.7.0_04.
There is no official maven archetype for Drools, and I doubt that any of the community ones are up to date.
Take a look at these resources:
Drools and jBPM version compatibility matrix
On the download page, section "Eclipse update site". IIRC, in 5.3 the plugin was part of JBoss Tools, but for 5.4 it's a separate update site as linked there.
Alternatively to using the 5.4 update site, you can download the droolsjbpm tools zip (5.4 or 5.3), unzip it and configure the plugin in eclipse as a local update site.
PS: I recommend upgrading everything to 5.4.0.Final, that's the latest and greatest community release.
I have developed an Eclipse plugin using the RCP version of Eclipse. I have used the plugin via a 'run application' launch as well as by exporting the plugin as a JAR and putting it in the plugins directory of Eclipse RCP.
The problem is that when I put the plugin JAR in the plugins directory for my Java version or Java EE version of Eclipse, it doesn't seem to be loaded as one of the plugins. I go to the preferences to look at the pref. page for my plugin and it isn't even listed.
This is my first Eclipse plugin, so I don't have much experience using plugins across different distributions of Eclipse and so forth. Any ideas of how to fix this? I would like to be able to use the plugin in any Eclipse (Java, Java EE, RCP, etc.)
Try putting your plugin under install/dropins/plugins directory. As of Eclipse 3.5, adding plugins directly to the root plugins directory isn't supported.
This should be enough for you to experiment further, but this isn't a good way to install finished plugins. The best way to install plugins is via a published repository. You will need to create a feature to hold your plugin and then use Export -> Plug-in Development -> Deployable features wizard or investigate command line build solutions such as pdeBuild.