[ayang]

This message has not been recovered.

[Remixen]

That is really a impressive topic..
Thank you for sharing this with us…

[seba-de]

Dear MyEclipse Softwareteam,
come on… We need a solution for this issue. Doesn’t matter how it looks like…
such as a list of steps what to do to get this working. (copy files from A to B, check here, checkout there)! But some hints.
That’s not a special scenario – checking out maven projects from SVN. It’s really unbelievable that you don’t support that.

Best regards,
Rudi

[deeanton]

I agree, I need a solution for this right away!

[mfkilgore]

I would like to add to this post as well. As much as we might like, we can not assume everyone is using myecipse. Other tools are used save projects into subversion. Being able to check out a maven project, which is supported in other IDEs including Eclipse is much more than a nice to have it is clear requirement. Please consider this for the 9x release!

[Joerg Wesely]

Any news about this issue? I have the same problem….

[Michael E Brown]

Same here.

I checked out an exiting Maven project from SVN various ways:

Checking out the project into a regular Java project,
Checking out the project into a regular Maven project,
Checking out the project into a regular generic project,

So far, the least mangled result is the last (as a generic project). Then I can add the Maven builder to the project and things seem to build properly. But, I can’t view class and call hierarchies – I get the message “The resource is not on the build path of a java project”. The .classpath, .project were not part of the checkin, and these outlined steps above don’t seem to rebuild the .classpath, which I read somewhere else is necessary for this type of activity.

So, I have a couple of questions:

When is MyEclipse going to support Maven in exiting projects? (I’ll beta test if you need testers)
Is there a current workaround that will get my existing Maven project integrated entirely in MyEclipse?

Thanks,
Mike

[Author]

Posts