[alikic]

Hi,

I upgraded to MyEclipse 6.6, and deployment to WebSphere doesn’t work any more. I installed m2eclipse (which is supposed to work well now). I tried all possible combinations of maven options from MyEclipse->Preferences: disable m2eclipse (use Maven4MyEclipse only), enable only m2eclipse, enable both, in all cases the same thing happens – maven dependencies don’t get copied to WEb-INF/lib on WebShpere 6.0 target during deployment. Including Maven Dependencies explicitly in Project Properties->”Order end Export” doesn’t help.

Thanks,
Aleksandar Likic

[Riyad Kalla]

Aleksandar,

MyEclipse already integrates m2eclipse, that setting “enable only m2eclipse” is what you want to do, but then you are “on your own” so to speak, MyEclipse’s integration with m2eclipse is disabled. So things like deployment management is no longer possible.

You will need to manage the deployment yourself using Maven in that case. That’s part of the value-add of Maven4MyEclipse.

Let’s back up, why did you have to disable Maven4MyEclipse? Maybe if we can figure out a way to keep it enabled, we can get the best of both worlds going?

[alikic]

I tried all possible combinations, both maven4myeclipse and m2eclipse enabled, etc.

Ultimately, I need the following: I want to check out the existing Web project from SVN. Then, I create a new EAR project in my workspace and include the Web project in it. Finally, I deploy the EAR to WebSphere 6.0. I just want to have a maven-aware environment that supports this simple use case, in a stable way. I don’t care if it is going to be maven4myeclipse or m2eclipse. The only reason I enabled m2eclipse is because I don’t know how to “enable maven dependency management” without it on the existing project.

I can say that deploying to WebSphere 6.0 with having both maven4myeclipse and m2eclipse is a nightmare. It behaves unpredictable, I have to do lots of manual tweaking to make both JUnit and deployment working at the same time, and then ones in a while it gets screwed up for no apparent reason (e.g. just by doing project clean).

[alikic]

NOTE; When checking the existing project from SVN, the .project and .classpath files are NOT in the SVN. I create the new project from SVN using the New Project Wizard.

[alikic]

Also, I am already familiar with the WebSphere specifics and workarounds when it comes to EAR deployment. I had everything setup correctly on MyEclpse 6.5, and it was working well. I started having problems after migrating to MyEclipse 6.6. I also tried 7M2 (which I am using now), it behaves exactly the same as 6.6 in this regard.

At one point I wanted to downgrade to 6.5, but I couldn’t find a download link on your site. Do you keep links to old releases somewhere?

Thanks,
Aleks

[Riyad Kalla]

Aleks,
We are swamped trying to get 7.0 out the door right now but I’ve filed this for further investigation to see what is going on. At a quick glance on JBoss things seem OK so this might be a WebSphere specific interaction.

[Author]

Posts