MyEclipse :: View topic - WAR file deployment failure...

MyEclipse: WAR file deployment failure...

rbreitling - Mar 01, 2012 - 08:11 PM
Post subject: WAR file deployment failure...

I have a project that I am trying to deploy in myelipse 10.0.2. All it's class files and class files from other dependent projects get deployed except projects that have Maven enabled.

This used to work in 8.6 just fine.

Am I missing something or is this just broken?

support-swapna - Mar 02, 2012 - 11:30 AM
Post subject:

rbreitling,

Sorry that you are seeing this issue. I could replicate the issue at my end. I have filed a PR for the dev team to investigate.

Can you throw more information about your project setup? Is there a specific reason behind a non-maven web project dependent on a maven java project in your setup ?

rbreitling - Mar 02, 2012 - 03:48 PM
Post subject: more information as requested..

support-swapna wrote:

We are in the process of converting from ant to maven builds and this is the situation I find myself in. In the past, this has always worked so, obviously, it wasn't a problem until I upgraded to 10.0.2.

Bob

support-tony - Mar 05, 2012 - 06:46 AM
Post subject:

Bob,

I've found that rebuilding the dependent maven project causes its classes to appear in the deployed location. Could you try that? At first, I thought a full rebuild of all associated projects might be needed but, on the Mac, I got the classes to appear with just a rebuild of the maven project. To do this, go to Project->Clean... then Click the "Clean projects selected below" and select the dependent maven project, then click OK. A redeploy shouldn't be necessary after this though, if the above doesn't work, please try a redeploy.

Note, you can browse the deployed location by going to the Servers view, expanding the deployed to server, right clicking on the deployed project and selecting "Browse deployment location".

I've updated the bug that was raised with this new information and we are investigating.

Please let us know if this workaround is effective for you.

rbreitling - Mar 07, 2012 - 03:05 PM
Post subject:

Interesting, doing a clean of the maven project did redeploy the classes to the server.

Bob

support-tony - Mar 08, 2012 - 07:59 AM
Post subject:

Bob,

Thanks for getting back to us. I'm glad that workaround worked for you. Hopefully, we will get this fixed soon but, in the meantime, at least you can deploy.

rbreitling - Mar 23, 2012 - 05:04 PM
Post subject:

support-tony wrote:

Bob,

Thanks for getting back to us. I'm glad that workaround worked for you. Hopefully, we will get this fixed soon but, in the meantime, at least you can deploy.

Do you have any idea when this is going to be fixed? I had hopes it would be in 10.1 but alas the problem is still there...

Bob

support-tony - Mar 26, 2012 - 05:28 AM
Post subject:

Bob,

Actually, there is a fix for this in 10.1. However, the fix is in some project settings and so will only apply to a new project. That is, only new maven dependent projects will be affected by this fix. So, if you recreate the dependent maven project, it should get deployed with MyEclipse 10.1.

Alternatively, there is a .settings folder in the project. Look for the com.genuitec.eclipse.j2eedt.core.prefs file and remove the useAssemblyMapping line. If this is the only line apart from the version, then you can delete the whole file.

Sorry for the inconvenience. Please let us know if this works for you.

rbreitling - Mar 27, 2012 - 02:46 PM
Post subject:

support-tony wrote:

Tony,

This seems to have worked. Thanks....that was a big deal to have working, very good.

On another front. I have a Spring applicationContext.xml file in my web projects src/main/resources directory that gets copied to the target/classes tree, but when I deploy the web app it is missing.

I'll create an new thread for this if you prefer.

Bob

support-tony - Mar 28, 2012 - 06:53 AM
Post subject:

Bob,

Yes, a new forum topic would be good. Could you include the application server in the new post? I couldn't replicate it with MyEclipse Tomcat. Also indicate if the MyEclipse automatic build put the applicationContext.xml file in the output folder or if it was a maven build.