I am an Eclipse user.
I am going to be using Glassfish on a project.
Is the Glassfish IDE integration substantially better in NetBeans (or some other), or is the integration the same as Eclipse?
I can't compare it to eclipse because I never tried it in eclipse but I can cast my vote for Netbeans integration. I've been using it for a while with Netbeans and I am very satisfied with the result.
with the full set of JavaEE plugins in Eclipse, it's trivial to control/deploy to glassfish. Grab the JavaEE version of Eclipse and follow the wizard for creating a new enterprise application.
Generally speaking, unless you're debugging the only intergration you really need is: start, stop, deploy. You can make almost any IDE/script/buildfile do that. Stick with the IDE you're most productive in.
I stuck with Eclipse.
Glassfish IDE integration is better with NetBeans.
The plugin for Eclipse isn't quite ready for primetime.
https://glassfishplugins.dev.java.net/eclipse34/
My personal experience is that Eclipse with the Java EE extensions are more than sufficient for development, and deployment of JAX-WS apps are faster in Eclipse than with Netbeans.
The Glassfish plugin has forms for editing configuration for things as nuanced as WSIT WS-Security and WS-AtomicTransaction. This speeds configuration. However, I've found that deploying a JAX-WS app performs ws-import more times than necessary, which doubles deployment time.
Related
I recently switched from eclipse and netbeans to intellij, but I have also liferay stuff to do and intelliJ seems to lack a decent liferay integration.
Does someone know how to use intelliJ for that, with as much of intelliJs comfort as possible :-/
As the themes are no simple java project the import stuff doesn't seem to recognize it properly...
You could look into the maven integration for Liferay (depending on the version of Liferay you're using - the more recent the version, the better the maven integration) and just import a pure maven project. The layout of this differs a bit from the usual ant-based SDK.
But of course you can also use the pure Ant buildfiles you find in the plugins sdk. As there's typically no java in a theme, it doesn't make a lot of differences.
Not wanting to start IDE wars here, but you also might consider Liferay IDE (or Developer Studio, it's EE-Version) for theme-related development. As there's no Java development done in themes, the conflict of changing tools should be handleable. I wouldn't want to work in both IDEs for Java development again (been there, done that), but for themes I can imagine just going the easy route - it's mainly CSS that you edit.
I've been looking around for a while how can I hotdeploy my projects when using m2eclipse plugin on MyEclipse and working with Websphere 6.1.
What I've done so far is to deploy my full application using the was6 maven plugin (http://mojo.codehaus.org/was6-maven-plugin/) but that plugin will only deploy the EAR into the Websphere.So whenever I have to change just one line of code I have to redeploy the application again. The server doesn't take the changes just by saving the modified source code or JSP file.
I am working with MyEclipse 8.5 IDE and with the original m2eclipse plugin (Not Maven4MyEclipse).
Has anyone been able to do that? And if so how?
Thanks in advance
JRebel is a commercial solution that would make your life much easier. It's cheap (like $60). I actually bought a personal license intead of waiting for my company to purchase it. There is a free 30 day trial!
JRebel will hotswap your .class files and resources. No need to maven package, just save the resource in Eclipse, and JRebel will put on the server. There a few limitations, but in my opinion, its a life save.
We have used JRebel on Jetty, and I have read it is supported on WAS.
I am using Maven to automate a project that is being developed in RAD 7.5.
I've installed m2eclipse in RAD 7.5 , updated ( manually ) maven dependencies , and it builds Maven way within RAD.
My main question : what is the best practice using m2eclipse with RAD?
Should we keep both ( RAD and maven ) settings in the project workspace or remove all RAD settings and stick with Maven only?
Also , I am wondering about m2eclipse dependency management feature. I was hoping that it will update pom.xml with the new dependency when I add it to the classpath and vise versa ( in case we are keeping both configurations ). Is this a correct assumption?
this doesn't seem to happen. Maybe I need to give it another try....
Any suggestions are very much appreciated!
The article "Java EE development using Rational Application Developer 7.5.5 and Maven" (http://www.ibm.com/developerworks/wikis/display/rad/Articles) is OK but the site is wrong.
Since RAD 7.5.5 is based on Eclipse 3.4.2 you need to point here:
http://m2eclipse.sonatype.org/sites/m2e-e34/
My main question : what is the best practice using m2eclipse with RAD? Should we keep both (RAD and maven) settings in the project workspace or remove all RAD settings and stick with Maven only?
I don't work with RAD so I'm not sure my answer will be totally accurate but when working with Eclipse, m2eclipse takes care of the .classpath and the .project files and everything is derived from the pom.xml, not the other way around. I don't think it's different with RAD.
[...] I was hoping that it will update pom.xml with the new dependency when I add it to the classpath and vise versa (in case we are keeping both configurations). Is this a correct assumption?
I don't think so, m2eclipse won't translate a random dependency (that may not be available in any repo) into a maven artifact and add the coordinates to the pom.xml. Edit the pom.xml or use the wizard to add a dependency. As I said above, it works the other way around, things are derived from a pom.xml.
As there seem to be many open issues with m2eclipse (at least 0.10+) and RAD 7.5, I'm thinking of going the manual way in RAD with the eclipse:rad goal:
http://maven.apache.org/plugins/maven-eclipse-plugin/rad-mojo.html
Please to go to http://www.ibm.com/developerworks/wikis/display/rad/Articles
See section Java EE, article "Java EE development using Rational Application Developer 7.5.5 and Maven".
This is a best-practices paper published by Rational Application Developer development team.
Be aware that the comment from Pascal might have performance implications during publishing to WebSphere Application Server or WebSphere Portal Server.
The developerWorks forum for Rational Application Developer contains also quite a number of posts.
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
I am completelty new to the BB development.
I want to start development of BlackBerry application.
I am confused how to start? And what plugins have to download and from which link?
And bit confused about the JDE plugin <--> Java plugin for Eclipse
Which I have to download for development?
Can any one explaine the above things?
thanks in advance...
JDE and eclipse plugin are same other than, JDE has only debug mode, but the eclipse has both debug and run mode. I am using eclipse for several years, so I feel comfortable in using eclipse. I recommend eclipse because, it is more developer friendly when compared to JDE.
I agree with Karthikeyan that eclipse has a more feature rich environment plus it can incorporate other plugins such as cvs, svn, mysql etc.
Sometimes it can take more configuration to get everything set up right properly. If you want to get your code up and running quickly without any configuration, I would highly recommend using the JDE.
Glen
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