- This topic has 13 replies, 10 voices, and was last updated 16 years, 8 months ago by
.
-
Posts
-
Any word on maven integration progress?
Being able to hot-deploy a EJB or webapp from a maven layout/config would just make my day.
No Maven integration has been explicitly speced out on our timeline yet, but until 4.0 gets out the door, I don’t know that we will be focusing on anything else.
@mcantrell wrote:
Any word on maven integration progress?
Being able to hot-deploy a EJB or webapp from a maven layout/config would just make my day.
I want to have the same! In a first step the hot-deploy and auto-resolve the libraries is enough. No full integration of maven is necessary (but will be nice). WTP 0.7 has this feature (flexible project layout). The configuration is not easy but possible.
I really would like to hot-deploy from a maven2 layout. In the beginning it could be solved by just allowing the user to select a .war file in some Project Properties config. When hitting deploy it would deploy that war file.
I would also like the JSP Content Assist to work when I have JSP libraries added via pom.xml 🙂
Brian,
There has been no commitment by the management team yet to Maven. Besides this thread there has not been much inerest in it. Not saying it won’t happen, only providing a reason why it hasn’t yet. These features are expensive (developer hours/support) to produce and there are requests for every feature under the sun so management has to be selective which we commit to.@Oliver.Nautsch wrote:
@mcantrell wrote:
Any word on maven integration progress?
Being able to hot-deploy a EJB or webapp from a maven layout/config would just make my day.
I want to have the same! In a first step the hot-deploy and auto-resolve the libraries is enough. No full integration of maven is necessary (but will be nice). WTP 0.7 has this feature (flexible project layout). The configuration is not easy but possible.
Auto-resolve of the maven libraries is already working in the ‘standard’ eclipse plugin:
- Create a workspace variable M2_REPO that points to your local Maven repository (%USERPROFILE%\.m2\repository) on Windows.
- Run ‘mvn eclipse:eclipse’ (generates project file for eclipse and creates classpath from Maven dependencies).
or ‘mvn eclipse:clean’ (removes project files)Then refresh your workspace, and you are set 😀
Regarding hot-deploy, things get a bit more complicated….
In our current project, we have an .EAR project with several subprojects (one of which is a .WAR struts web project). We were not able to get .EAR deployment work in a reasonable way that also enabled hot-deploy, but came up with a ‘hack’ that enables it by deploying as a .WAR file and performing some manual (or scripted) file copying….1. First copy any .ear deployment files manually to your appserver deploy folder (in our case JBoss 4):
– Copy ‘target\$projectname*.(ds|har)’ to ‘$jboss\server\default\deploy’
2. Then copy any .EAR-level libraries directly into your appservers classpath:
– Copy ‘target\$projectname\(*.jar|lib*.jar)’ to ‘$jboss\server\default\lib’
3. Check-out the .WAR (web/struts) subproject and run ‘mvn package eclipse:eclipse’
4. Create ‘lib’ directory in maven file structure: (‘src\main\webapp\WEB-INF\lib’)
5. Copy ‘target\$projectname\WEB-INF\lib*.jar’ to ‘src\main\webapp\WEB-INF\lib’
6. Import the generated project into Eclipse using ‘File->Import->Existing Projects into Workspace’
7. Make sure the project is ME web-enabled: Right-click the project and select ‘MyEclipse->Add WebProject Capabilities’Then you should be able to hot-deploy your maven2 project 😀
….And since the standard maven2 eclipse plugin also generates WTP files, there’s good hope that the integration situation might easily improve as soon as ME is based on WTP 1.0…– If only this pesky little ME bug that makes my ‘web project capabilities’ dialogs turn up blank on my nVidia Quadro card were fixed, I wouldn’t have to run ME in a VMWARE setup to make all this work….
If you are using Maven 2.0, here’s a nice solution, some bugs and not a lof of features for the moment but it is making progress :
http://maven.apache.org/eclipse-plugin.html@pouet wrote:
If you are using Maven 2.0, here’s a nice solution, some bugs and not a lof of features for the moment but it is making progress :
http://maven.apache.org/eclipse-plugin.htmlI can see that it works OK for java jar-only projects, but have you managed to get it working with ear applications, or even war applications?
I tried this tool, and for managing the projects that my .ear and .war projects depend on, this plugin works fine. But it does not handle e.g. the mismatch between maven’s compile ‘target’ folder and the location where myeclipse expects to find the compiled classes for deployment
I’m sucessfully using Maven Plugin and MyEclipse for hot-deploy (except for one small bug with user libraries), so there should be no issues around here. Why are people suggesting that MyEclipse reivents the wheel? There’s an available plugin for Maven 2: http://m2eclipse.codehaus.org/
So there should be no need for MyEclipse to reimplement it. Maybe integrate it? It’s still in alpha, though.
@lquijano wrote:
I’m sucessfully using Maven Plugin and MyEclipse for hot-deploy (except for one small bug with user libraries), so there should be no issues around here. Why are people suggesting that MyEclipse reivents the wheel? There’s an available plugin for Maven 2: http://m2eclipse.codehaus.org/
So there should be no need for MyEclipse to reimplement it. Maybe integrate it? It’s still in alpha, though.
Well, maybe because this very good plugin doesn’t solve all problems.
It’s fine as long as you use .jar projects, and can even work for .war projects.
– but when you come to a more complex .ear project that contains common libraries, several .war’s and several ejb modules you can simply wave goodbye to using MyEclipse to deploy the project in your appserver – and then you also have to wave goodbye to hot-code-replace (which is *THE*NICEST* feature of Eclipse/MyEclipse)
🙁The first product that lets me perfom an ‘exploded deployment’ with hot-code-replace of a Maven EAR project certainly will get my dollars…
@support-rkalla wrote:
Brian,
There has been no commitment by the management team yet to Maven. Besides this thread there has not been much inerest in it. Not saying it won’t happen, only providing a reason why it hasn’t yet. These features are expensive (developer hours/support) to produce and there are requests for every feature under the sun so management has to be selective which we commit to.My development group recently switched from MyEclipseIDE to Intelij specifically for their ability to work with the maven pom files directly.
In general Intelij works better with maven, the concepts mesh better than eclipse’s idea of projects.
