[ksgetting]

Last week my workspace was corrupted so badly I decided to create a new one and migrate to MyEclipse 2014. After spending a lot of time migrating all of my Java projects, I thought I have my new workspace all working nicely. But I have been fighting an issue off and on all week. I have 1 web project. And 1 deployment defined for Tomcat 7. I can’t seem to convince MyEclipse to deploy all of the class files to Tomcat. This usually indicates that 1 of my Java projects has a build problem. And I have fixed a number of them this week. And each time I fix the issue, the deployment works again. This time I can’t find any error showing up in any of my projects. Does MyEclipse log errors somewhere indicating why it’s not deploying everything it should be? When I click on redeploy, it finishes way too quickly (a couple seconds).

*** Date:
Friday, April 11, 2014 9:10:35 AM 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=-Xmx768m
-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 Workbench

Version: 2014
Build id: 12.0.0-20131202

Blueprint: 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-0605

org.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-20130612210623

Eclipse 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
1854_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-swapna]

Ksgetting,

Sorry that you are seeing this issue.

Can you please answer some more questions for us?

1. From which version of MyEclipse did you migrate the project to MyEclipse 2014? Did you see any errors during migration?

2. Do you see the issue only with this one project?

3. Once migrated, if your project has any dependencies, you should add them in the Deployment Assembly page (Right click on the project > Properties > MyEclipse > Deployment Assembly). Click on Advanced and see if you need merged deployment of modules for this project.

4. Switch to a new workspace, import the project, migrate it, check whether the dependencies are added in the DA page and try deploying. If you still see issues, please send us the entire contents of the .log file which is located at <workspace dir>/.metadata/.log , along with the details of the project structure.

5. If possible please also share all the .* files (.classpath,.settings,.project etc) of the project and for all the dependent projects, if any to help us investigate the issue.

[ksgetting]

I could not find a way to export the web project from my other workspace. I had created a new one.

I fixed the issue by deleting the web project and creating a new one again. It appears that you have to add every jar and java project manually to the Deployment Assembly before they will properly deploy. I used to just add them to the Java build path with version 10.7.

[support-swapna]

Hi,

Glad that the issue is fixed.The deployment engine was modified from MyEclipse 2013 for a more transparent Deployment Assembly mechanism.

Please take a look about changes in deployment in MyEclipse 2013 Help :

http://docs.myeclipseide.com/index.jsp?topic=%2Fcom.genuitec.myeclipse.doc%2Fhtml%2Fgettingstarted%2Fme_2013%2Findex.html&cp=1_0

A more detailed explanation can be found here :

http://docs.myeclipseide.com/index.jsp?topic=%2Fcom.genuitec.myeclipse.web.doc%2Fhtml%2Fquickstarts%2Fwebprojects%2Findex.html&cp=1_8_1_3_7&anchor=dependent_projects

When you add a project dependency to a web project using the Deployment Assembly, this will also add it to the build path, via the Web App Libraries container in the build path (that is, you won’t see it in the Projects tab, of the build path configuration, but on the Libraries tab, under the Web App Libraries entry).

Regarding the Export of the project, you can choose Export > General > Archive File to export as .zip file or Export > MyEclipse JEE > WAR file to export as .war. What exact issue are you seeing during Export?

Let us know if you see any issues or if you have any questions.

[ksgetting]

I wasn’t sure on the steps, since I am only familiar with exporting as a Team Project Set and the web project cannot be exported with that option. Thanks for the tip.

One other migration issue I ran across. Exporting JDBC drivers. I have about 30. After I imported them, they were all corrupted. They all had the driver template set to Axion, which caused the Connection URL, Driver Jars and Driver classname to be reset.

[support-swapna]

Hi,

Can you please switch to a new workspace, try importing the project and then go through the migration wizard when it prompts ? If you see any issues during migration, please attach a screenshot of the issue. Also copy paste the entire contents of the .log file which is located at <workspace dir>/.metadata/.log.

Can you please if possible send us all the .* files (.project,.classpath, .settings etc) of the project to help us replicate the issue at our end?

[Author]

Posts