I have a maven web app project which has a dependency on a maven skinny war project.
Both projects, the main webapp and the skinny war project are in my eclipse.
Now when I run the main webapp in my original eclipse, where I built the projects, I can use my controllers from the skinny war project etc.
Now I installed the same projects on a different eclipse on a different computer. I can run the main webapp but the controllers from the skinny war are not available.
There is a difference in the target folder of the project between my original eclipse and the other eclipse instance.
folders in target folder in original eclipse:
m2e-wtp
war
...
folder in target folder in new eclipse:
m2e-wtp
Maybe it has something to do with this ?
Funny thing I found out.
When I close the project in eclipse, the controllers are available.
I somebody has the same problem. I installed the following eclipse plugin. Even though I did not install this one on my original eclipse. But it works now.
http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/
Related
I have a maven jar project common_platform that is producing the usual .jar file and also a .war overlay (using the maven-assembly-plugin)
I have another maven project with war packaging, it's including both those artifacts.
Now I want to use WTP to deploy the webapp project to Tomcat. Unfortunately the common_platform .war overlay is not getting processed.
If I go to Web Deployment Assembly view I see the project is included twice, but the files do not appear in the deployed webapplication.
I have another (external) overlay with ExtJs and it's being unpacked as expected.
I tried adding the package manually to the descriptor, but it's added as a package, not unpacked.
How to make WTP unpack the overlay contents?
I'm using Eclipse Mars with recent WTP, m2e and m2e-wtp.
Filled a bug in m2e-wtp
TL;DR:
Unfortunately m2e-wtp doesn't support workspace projects generating
multiple archives.
I'm using the Eclipse "Internal Glassfish 3.1.2.2" server with the Eclipse Glassfish plugin (http://download.java.net/glassfish/eclipse/juno). I'm also using Maven with the m2e Eclipse plugin. The Glassfish plugin correctly deploys my EAR modules to the Internal Glassfish, but it does not deploy my dependency jars, which I believe should end up in a folder called "lib".
I found a partial solution here, which is to add my maven target lib folder to the EAR Deployment Assembly (double-click in the Deploy Path box to edit). This works, but m2e (or m2e-wtp) undoes the config change when I do Maven > Update Project.
There ought to be a cleaner solution. The Eclipse Ear Module Assembly dialog has a field to name the "EAR library directory", so it's aware of the lib folder. Where does Eclipse EAR assembly (without Maven) look for jars to put in the lib folder? I assume the Glassfish plugin is looking in the same place.
You can use the following steps to find the source of the problem:
Take Eclipse out of the equation and build EAR on command line using Maven, does it turn out ok? If not, look for a solution in your pom.xml.
If ok so far, open Eclipse and perform Maven -> Update Project. Then export EAR using Eclipse (look for EAR export wizard under File -> Export). Did the exported EAR turn out ok? If not, file a bug report for m2e-wtp plugin. It is still pretty raw, so it wouldn't be surprising if it doesn't setup Eclipse metadata correctly in some cases.
If ok so far, then it is time to look for a problem in Glassfish plugin. I doubt that you will get this far, but if you do I will help you to follow up.
I have a problem with my eclipse (3.6, Helios) and my jboss tools plugin (3.2).
When I publish my war project with JbossTools in a jboss server, all jars in build path are publish in WEB-INF/lib directory on the server. It's ok for that.
But, I have several jar projects in eclipse linked to my war project. In the build path of my war project, these jars appear in the "Projects" tab, no in the "Libraries" tab. This works is normal but all projects in "Projects" tab are not publish in the server.
Someone can help me about that ?
Thanks.
For jar/wars you use the deployment/module assembly page in project properties.
We have existing maven project. I have imported it with m2eclipse plugin.But
I can not run the project. Tomcat can not see resources(WAR files under target folder).
What am I missing? BTW we have multi-module project(2 WAR files).
Thanks in advance!
You need to add the tomcat server in your eclipse.
The maven project should be a web based project
You need to add the web project to the tomcat server.
You need to add J2EE Module Dependencies - Eclipse 3.3 ( To enable all library dependencies to be available at runtime to tomcat). Paths that point to your m2 repo & the lib files.
It may be Java EE Dependencies in earlier versions.
Both your projects needed to be added similarly.
How can I import a maven EAR project into Eclipse 3.4, and be able to use the IDE (WTP) to deploy the ear successfully to Weblogic (9.2)?
The main issue is that the dependent jars are not being included in the ear (under APP-INF/lib) when it gets deployed through the IDE. When I build from command line, the ear is exactly how I want it.
I am using the APP-INF/lib configuration for the ear plugin, and have included the jarModule sections for all the required jars.
When editing the eclipse EAR project's Java EE components, all the jars are listed, but not in the APP-INF/lib. Only when I open a dependent jar project do those specific jars get set under that subfolder. All the 3rd party jars are showing they will end up in the wrong place.
If you need more info, just let me know. Thanks!
You might want to use maven to create the eclipse WTP projects for you. This might be helpful.
The Using maven-eclipse-plugin in multi-module projects with WTP of the maven website describes how to develop Multi-module projects with Maven and Eclipse efficiently using the best of both Maven 2 and Eclipse's WTP. This covers projects that have EJB and EAR modules.
An fully working example of a multi-module projects, containing some JAR-, a WAR- and an EAR-project is even available for download if necessary.