Vincent Massol wrote:
>You mean a view to easily edit the project.xml ?
>
>
That, and the project.properties, and build.properties. The project.xml
editor might be like the manifest editor. Don't get me wrong -- I don't
have a problem editing .xml files by hand, so this isn't a high
priority, but it's a natural extension. And some programmers do better
when they're led by the hand.
>>And act like ant (it's my understanding that recent version of
>>maven really supplant ant).
>>
>>
>
>Be able to start Maven from Eclipse. This is easy to do.
>
>
Well, just running it isn't the only thing.
* You need to be able to pick targets
* automatically refresh everything in eclipse that changes
* an option for using the Eclipse compiler (as ant does)
*.errors encountered should show up in an eclipse view (Tasks for
compiler errors).
* junit test runs should have their result shown in the Junit view.
* "new project - Maven", which creates all your basic setup stuff
There's no end of possibilities if you want to really make integration
tight.
>>But what I wanted was more information on the Eclipse-related code
>>
>>
>that
>
>
>>is part of Maven.
>>
>>
>
>Oh you mean the "The Maven plugin for Eclipse" ! (and not "The Eclipse
>plugin for Maven") ... :-)
>
>
We really need clearer terms for these things....
>It's a very simple plugin that generates automatically Eclipse .project
>and .classpath files from the information in the POM.
>
>
How does it handle attaching source and javadoc to dependent libraries?
Also, is it extensible? I'm working on an Eclipse builder that will be
added to a java project, so if it's regenerating .project files and
.classpaths, it needs to know about such things.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
