Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] [tycho-user] Project generated from tycho-eclipse-plugin-archetype is missing JUnit

lets take this to m2e-dev list, where I think this discussion is more appropriate.

On 11/12/2013, 17:14, Doug Schaefer wrote:

Yes sorry, .classpath. And, cool, you already have that. I have to admit I
haven’t tried m2e really yet. But I am concerned our maven builds are so
much different than our workspace builds especially as I cheat and have
the odd antrun into our poms. Would m2e help me there?

m2e needs to know what to do with maven plugins during Eclipse workspace
build. At very least it needs to be able to keep workspace and
filesystem in sync and make sure not to leak any JVM and OS resources.
For some maven plugins this is relatively straightforward, but for
general purpose tools like ant this is really hard. So far no one has
suggested a good approach what to do about it, so most likely m2e won't
work for your out of the box and will require some configuration.

http://wiki.eclipse.org/M2E_plugin_execution_not_covered


BTW, the .project thing is my real question. We have the same problem with
CDT workspaces where the .project file is overly constraining, especially
compared to Visual Studio and Xcode.

I don't mind .project per se, my problem is with eclipse workspace in
general. I think m2e and cdt both have to deal with nested project
structures and current resource and builder model is simply inadequate.
In m2e we have to present maven multimodule project as a flat list of
workspace project, which, quite frankly, results in very poor user
experience. I have pretty good idea how to solve this for m2e, but this
involves pretty extensive changes to JDT and likely resources layer and
unfortunately I can't commit this much time to this project at the moment.


--
Regards,
Igor



Back to the top