- This topic has 5 replies, 3 voices, and was last updated 10 years, 1 month ago by support-swapna.
-
AuthorPosts
-
tdevosMemberHi,
I’m using MyEclipse 10.5 and we have converted our project to use maven. I created a new Enterprise Application Project to deploy our web application to WAS 8.5. If I create the EAR file using right-click-> run as -> maven install, the EAR is perfectly okay and I can deploy it using the web console of WAS.
Howerver, If I deploy the application in MyEclipse using “Add deployment” on our WAS, there seems to be a problem. If I choose “browse” I can see that all librarties are added to the WEB-INF\lib folder, even the jar files which are excluded in the pom files.
To make a long story short I can give a small example. In the pom of a maven module we have
<dependency> <groupId>net.sf.jasperreports</groupId> <artifactId>jasperreports</artifactId> <version>3.7.6</version> <exclusions> <exclusion> <artifactId>commons-logging</artifactId> <groupId>commons-logging</groupId> </exclusion> </exclusions> </dependency>
In the maven build, the commons-logging file is NOT added (which is correct). If I choose deploy from within MyEclipse the commons-logging.jar is added. It seems that MyEclipse does not take into account the exlcusions. I tried creating the EAR with Maven4MyEclipse support as well as the classic m2Eclipse. I also tried classic deployment as wel as enhanced deployment. All with the same result.
Any idea what i”m doing wrong?
Regards,
support-swapnaModeratortdevos,
Sorry that you are seeing this issue. I am afraid we could not replicate the issue at our end.
The MyEclipse deployment is in sync with the pom.xml exclusions.1. Can you please copy paste the Installation Details from MyEclipse > Installation Summary > Installation Details.
2. Can you please look in the Maven Dependencies library in the Package Explorer? Do you see the commons-logging.jar in there before and after exclusion?
3. Can you share the steps you followed right from EAR creation, adding the maven support and the dependencies to help us replicate the issue at our end?
Let us know how it works for you.
tdevosMemberHi,
Thanks for your reply.
The installation details are:
*** Date: donderdag 19 juli 2012 13.47 u. CEST *** System properties: OS=WindowsVista OS version=6.1.0 OS arch=amd64 Profile arch=x86_64 Window system=win32 Java version=1.6.0_13 Workspace=file:/D:/workspaceUbench_maven_myeclipse/ VM Args=-Xmx512m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=64m -Dosgi.nls.warnings=ignore -jar D:\Programs\Genuitec\MYECLI~2\../Common/plugins/ORB7B5~1.JAR *** Subscription information Product Id: E3MB (MyEclipse Blue Subscription) License version: 3.0 Full Maintenance Included Subscription expiration date (YYYYMMDD): 20130403 Number of users: 6 *** Eclipse details: MyEclipse Blue Edition Version: 10.5 Blue Build id: 10.5-Blue-20120615 Blueprint: MyEclipse Blue Edition 10 com.genuitec.myeclipse.blue.feature - 10.5.0.me201206141911 com.genuitec.myeclipse.database - 10.5.0.me201206141911 com.genuitec.myeclipse.db2 - 10.5.0.me201206141911 com.genuitec.myeclipse.desktop - 10.5.0.me201206141911 com.genuitec.myeclipse.editor - 10.5.0.me201206141911 com.genuitec.myeclipse.geronimo - 10.5.0.me201206141911 com.genuitec.myeclipse.glassfish - 10.5.0.me201206141911 com.genuitec.myeclipse.icefaces.feature - 10.5.0.me201206141911 com.genuitec.myeclipse.iedebugger - 10.5.0.me201206141911 com.genuitec.myeclipse.imageeditor - 10.5.0.me201206141911 com.genuitec.myeclipse.jboss - 10.5.0.me201206141911 com.genuitec.myeclipse.jetty - 10.5.0.me201206141911 com.genuitec.myeclipse.jonas - 10.5.0.me201206141911 com.genuitec.myeclipse.jrun - 10.5.0.me201206141911 com.genuitec.myeclipse.jsf - 10.5.0.me201206141911 com.genuitec.myeclipse.matisse - 10.5.0.me201206141911 com.genuitec.myeclipse.maven - 10.5.0.me201206141911 com.genuitec.myeclipse.oracle - 10.5.0.me201206141911 com.genuitec.myeclipse.orion - 10.5.0.me201206141911 com.genuitec.myeclipse.persistence - 10.5.0.me201206141911 com.genuitec.myeclipse.pulse - 10.5.0.me201206141911 com.genuitec.myeclipse.reports - 10.5.0.me201206141911 com.genuitec.myeclipse.resin - 10.5.0.me201206141911 com.genuitec.myeclipse.struts - 10.5.0.me201206141911 com.genuitec.myeclipse.sun - 10.5.0.me201206141911 com.genuitec.myeclipse.tomcat - 10.5.0.me201206141911 com.genuitec.myeclipse.uml2 - 10.5.0.me201206141911 com.genuitec.myeclipse.visualvm - 10.5.0.me201206141911 com.genuitec.myeclipse.visualvm.server - 10.5.0.me201206141911 com.genuitec.myeclipse.weblogic - 10.5.0.me201206141911 com.genuitec.myeclipse.ws - 10.5.0.me201206141911 com.genuitec.myeclipse.ws.blue - 10.5.0.me201206141911 org.eclipse.birt - 2.6.1.me201206141911 org.eclipse.datatools.connectivity.feature - 1.9.0.me201206141911 org.eclipse.datatools.enablement.feature - 1.9.0.me201206141911 org.eclipse.datatools.modelbase.feature - 1.9.0.v201106031100-77078CcNBHCBYKYEbNV org.eclipse.datatools.sqldevtools.feature - 1.9.0.me201206141911 org.eclipse.emf - 2.7.0.v20110606-0949 org.eclipse.gef - 3.7.0.v20110425-2050-777D-81B2Bz0685C3A6E34272 org.eclipse.graphiti.feature - 0.8.0.v20110607-1252 org.eclipse.jpt.jpa.feature - 3.0.0.me201206141911 org.eclipse.jpt.jpadiagrameditor.feature - 1.0.0.me201206141911 org.eclipse.jst.common.fproj.enablement.jdt - 3.3.0.me201206141911 org.eclipse.jst.enterprise_ui.feature - 3.3.0.me201206141911 org.eclipse.jst.server_adapters.ext.feature - 3.3.0.me201206141911 org.eclipse.jst.server_adapters.feature - 3.2.100.me201206141911 org.eclipse.jst.server_ui.feature - 3.3.0.me201206141911 org.eclipse.jst.ws.axis2tools.feature - 1.1.200.me201206141911 org.eclipse.m2e.feature - 1.0.0.me201206141911 org.eclipse.sapphire.platform - 0.3.0.201106221325 org.eclipse.wst.common.fproj - 3.3.0.me201206141911 org.eclipse.wst.server_adapters.feature - 3.2.100.me201206141911 org.eclipse.xsd - 2.7.0.v20110606-0949 org.springframework.ide.eclipse.feature - 2.9.1.me201206141911 edu.umd.cs.findbugs.plugin.eclipse - 2.0.0.20111221 fr.obeo.acceleo.bridge.feature - 2.6.0.200906261742 org.eclipse.cvs - 1.3.100.v20110520-0800-7B78FHl9VF7BD7KBM4GP9C org.eclipse.draw2d - 3.7.0.v20110425-2050-46-7w3122153603161 org.eclipse.equinox.p2.core.feature - 1.0.1.v20110906-1605-8290FZ9FVKHVRKtmx3fpNuo02129 org.eclipse.equinox.p2.extras.feature - 1.0.1.v20110906-1605-7A4FD4DiVOMap8cHSc6vPuny4gqO org.eclipse.equinox.p2.rcp.feature - 1.0.1.v20110906-1605-782EqBqNKGVkiV-PUsgz-uny4gqO org.eclipse.equinox.p2.user.ui - 2.1.2.R37x_v20110815-1155-6-Bk8pYWZz0qUTX5I15GZWwbXkrl org.eclipse.help - 1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx org.eclipse.jdt - 3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1 org.eclipse.jsf.feature - 3.3.0.me201206141911 org.eclipse.ocl - 3.1.0.v20110606-1427 org.eclipse.pde - 3.7.2.v20120120-1420-7b7rFUOFEx2Xnqafnpz0E--0 org.eclipse.platform - 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q org.eclipse.rcp - 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272 Eclipse startup command=-os win32 -ws win32 -arch x86_64 -showsplash -launcher D:\Programs\Genuitec\MyEclipse Blue Edition 10\myeclipse-blue.exe -name Myeclipse-blue --launcher.library D:\Programs\Genuitec\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_4.2.0.v201201111650\eclipse_4201.dll -startup D:\Programs\Genuitec\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -exitdata 128c_5c -install D:\Programs\Genuitec\MyEclipse Blue Edition 10 -configuration D:\Programs\Genuitec\MyEclipse Blue Edition 10\configuration -vm D:\Programs\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_64_1.6.0.013\bin\javaw.exe
2. The commongs-logging jar is there before I add the exclusion.After updating the pom with
<exclusion> <artifactId>commons-logging</artifactId> <groupId>commons-logging</groupId> </exclusion>
The commons-logging jar disappears from the maven-dependencies in the package explorer.
3. The project is created using -> new Enterprise Application Project ->specify Java EE6 level-> check “Add maven support” -> check MyEclipse Maven JEE project and checked “Add existing web and EJB module projects”.
Artifact, groupId etc is left on the default values and in the last screen I choose my WAR module as a dependency.
The next step is adding the war module to the application.xml as well as to the pom.xml. This is all done via the gui.
The last step is choosing “Add deployment” on our WAS 8.5 server connector defined in MyEclipse Blue.
If I now navigate to “Manage deployments” and click “Browse”. We see in the lib folder the commons-logging jar. In fact this not the only jar. All our excluded jars are there in the lib fiolder.
If I right click the EAR project and choose Maven->”maven install” the EAR is correctly build and the excluded jars are ommitted.
Thanks for your help. If you need any further information please let me know.
Regards,
support-swapnaModeratortdevos,
Thank you for the steps.
Can you give us some more details ?
1. Are you using the Deployment Assembly for EAR, EJB and the Web modules? Right click on the project > Properties > MyEclipse > Deployment Assembly to check the same.
2. Can you please also send us all the pom.xmls in the project to help us investigate further?
syed20MemberIn the maven build, the commons-logging file is NOT added (which is correct). If I choose deploy from within MyEclipse the commons-logging.jar is added. It seems that MyEclipse does not take into account the exlcusions. I tried creating the EAR with Maven4MyEclipse support as well as the classic m2Eclipse. I also tried classic deployment as wel as enhanced deployment. All with the same result.
support-swapnaModeratorSyed,
The issue is fixed in our latest release MyEclipse 2015 CI 6.
Can you please download MyEclipse 2015 CI and check if you still see the issue?
Please download MyEclipse 2015 CI 6 from here : https://www.genuitec.com/products/myeclipse/download/You can install MyEclipse 2015 CI to a different location alongside your existing MyEclipse installation. The license you currently hold is valid for MyEclipse 2015 CI as well.
Let us know how it works for you.
-
AuthorPosts