- This topic has 4 replies, 3 voices, and was last updated 10 years, 4 months ago by support-tony.
-
AuthorPosts
-
ksgettingParticipantOn my web project, I added a long list of jars needed for deployment to my Tomcat webapp. I have several newer jars that I just added. But I also needed to remove the older (incompatible) jars, I am able to use the Remove button to remove the jar from the list of assembly objects, but after I click on OK to close the preferences window and reopen the web project’s preferences window again, the remove jars reappear. I can’t get rid of them. And those old jars keep getting deployed to my webapp.
How can I remove them permanently?
*** Date:
Thursday, April 24, 2014 12:11:55 PM CDT*** System properties:
OS=Windows7
OS version=6.1.0
OS arch=amd64
Profile arch=x86_64
Window system=win32
Java version=1.7.0_45
Workspace=file:/C:/data/workspace/
VM Args=-Xmx1536m
-XX:MaxPermSize=320m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-jar
C:\Users\Owner\AppData\Local\MYECLI~2\plugins/OR8508~1.JAR*** Subscription information
Product Id: E3MP (MyEclipse Professional Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20140613
Number of users: 2*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 2014
Build id: 12.0.0-20131202Blueprint: N/A
com.genuitec.myeclipse.database – 12.0.0.me201311281640
com.genuitec.myeclipse.enterprise.workbench – 12.0.0.me201311281640
com.genuitec.myeclipse.jsf – 12.0.0.me201311281640
com.genuitec.myeclipse.maven – 12.0.0.me201311281640
com.genuitec.myeclipse.tomcat – 12.0.0.me201311281640
com.genuitec.myeclipse.ws – 12.0.0.me201311281640
org.eclipse.datatools.connectivity.feature – 1.11.1.me201311281640
org.eclipse.datatools.enablement.feature – 1.11.1.me201311281640
org.eclipse.datatools.modelbase.feature – 1.11.1.v201306041610-7707GCcNBHLDaKTEcRi
org.eclipse.datatools.sqldevtools.feature – 1.11.1.me201311281640
org.eclipse.emf – 2.9.1.v20130902-0605
org.eclipse.gef – 3.9.1.201308190730
org.eclipse.graphiti.feature – 0.10.1.v20130918-0838
org.eclipse.jst.common.fproj.enablement.jdt – 3.4.0.me201311281640
org.eclipse.jst.enterprise_ui.feature – 3.5.0.me201311281640
org.eclipse.jst.server_adapters.ext.feature – 3.3.103.me201311281640
org.eclipse.jst.server_adapters.feature – 3.2.201.me201311281640
org.eclipse.jst.server_ui.feature – 3.4.1.me201311281640
org.eclipse.jst.ws.axis2tools.feature – 1.1.200.me201311281640
org.eclipse.m2e.feature – 1.4.0.me201311281640
org.eclipse.sapphire.platform – 0.6.6.201310081535
org.eclipse.wst.common.fproj – 3.4.0.me201311281640
org.eclipse.wst.server_adapters.feature – 3.2.300.me201311281640
org.eclipse.xsd – 2.9.1.v20130902-0605org.eclipse.cvs – 1.4.0.v20130911-1000
org.eclipse.draw2d – 3.9.1.201308190730
org.eclipse.e4.rcp – 1.2.1.v20130910-2014
org.eclipse.egit – 3.1.0.201310021548-r
org.eclipse.epp.mpc – 1.2.1.I20130917-2019
org.eclipse.equinox.p2.core.feature – 1.2.1.v20130827-1605
org.eclipse.equinox.p2.discovery.feature – 1.0.100.v20130502-0334
org.eclipse.equinox.p2.extras.feature – 1.2.0.v20130827-1605
org.eclipse.equinox.p2.rcp.feature – 1.2.0.v20130828-0031
org.eclipse.equinox.p2.user.ui – 2.2.0.v20130828-0031
org.eclipse.help – 2.0.1.v20130911-1000
org.eclipse.jdt – 3.9.1.v20130911-1000
org.eclipse.jgit – 3.1.0.201310021548-r
org.eclipse.jsf.feature – 3.7.0.me201311281640
org.eclipse.mylyn.bugzilla_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.commons – 3.9.1.v20130917-0100
org.eclipse.mylyn.commons.identity – 1.1.1.v20130917-0100
org.eclipse.mylyn.commons.notifications – 1.1.1.v20130917-0100
org.eclipse.mylyn.commons.repositories – 1.1.1.v20130917-0100
org.eclipse.mylyn.context_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.discovery – 3.9.1.v20130917-0100
org.eclipse.mylyn.ide_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.monitor – 3.9.1.v20130917-0100
org.eclipse.mylyn.tasks.ide – 3.9.1.v20130917-0100
org.eclipse.mylyn.team_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn_feature – 3.9.1.v20130917-0100
org.eclipse.pde – 3.9.1.v20130911-1000
org.eclipse.platform – 4.3.1.v20130911-1000
org.eclipse.rcp – 4.3.1.v20130911-1000
org.eclipse.team.svn – 1.1.3.I20140206-1700
org.eclipse.team.svn.mylyn – 1.1.2.I20131116-1700
org.eclipse.team.svn.nl1 – 1.1.0.I20130619-1700
org.eclipse.team.svn.resource.ignore.rules.jdt – 1.1.0.I20130619-1700
org.eclipse.team.svn.revision.graph – 1.1.0.I20130619-1700
org.polarion.eclipse.team.svn.connector – 3.0.5.I20140122-1700
org.polarion.eclipse.team.svn.connector.svnkit16 – 3.0.5.I20140122-1700
org.sonatype.m2e.mavenarchiver.feature – 0.15.0.201207090125-signed-20130612210623Eclipse startup command=-os
win32
-ws
win32
-arch
x86_64
-showsplash
-launcher
C:\Users\Owner\AppData\Local\MyEclipse Professional 2014\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Users\Owner\AppData\Local\MyEclipse Professional 2014\plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\Users\Owner\AppData\Local\MyEclipse Professional 2014\plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-exitdata
1844_5c
-install
C:\Users\Owner\AppData\Local\MyEclipse Professional 2014
-vm
C:\Users\Owner\AppData\Local\MyEclipse Professional 2014\binary/com.sun.java.jdk7.win32.x86_64_1.7.0.u45/bin/javaw.exe
support-pradeepMemberksgetting,
A bug report is already filed for this and our dev team has fixed it. The fix will be available in the upcoming release 2015 Early access which is due towards the end of May 2014.
As a workaround, you can remove the jars from deployment assembly page by deleting the jar file entries from .settings/org.eclipse.wst.common.component file. (To make .settings folder visible, click on View menu (CTRL+F10) in the package explorer, select Filters and unselect or uncheck .*resources checkbox and click Ok)
Let us know how the workaround works for you.
ksgettingParticipantThe work around did the trick. Thanks!
support-pradeepMemberksgetting,
Thanks for getting back to us.
Do let us know if you see any issues in MyEclipse.
support-tonyKeymasterksgetting,
For your information, this problem has been fixed in our 2015 CI 1 release. For details of this release, please see this announcement.
Thanks for reporting the issue and sorry for the inconvenience it caused.
-
AuthorPosts