> -----Original Message-----
> From: David Corbin [mailto:[EMAIL PROTECTED]]
> Sent: 22 August 2002 12:14
> To: Turbine Maven Users List
> Subject: Re: Maven Beta 6 Released!
>
> 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
ok
> * automatically refresh everything in eclipse that changes
ok
> * an option for using the Eclipse compiler (as ant does)
ok
> *.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.
A view like the ant plugin one, right ? It will be hard to separate
junit/compilet stuff from the rest as it is viewed as a black block. But
actually, maybe we simply need to replace the maven driver/App by an
eclipse driver. Actually what would be nice is the ability to plug
listeners in Jelly. Then we would be able to do magical stuff ... I'll
speak to James about that.
> * "new project - Maven", which creates all your basic setup stuff
yep, that would be nice.
>
> There's no end of possibilities if you want to really make integration
> tight.
Right.
>
> >>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?
It doesn't at the moment but would be a nice addition. Do you want to
help ? The code is really simple. See here :
http://cvs.apache.org/viewcvs/jakarta-turbine-maven/src/plugins-build/ec
lipse/plugin.jelly?rev=1.3&content-type=text/vnd.viewcvs-markup
> Also, is it extensible?
Yes, sure. Just add new goals to the plugin jelly script.
> 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.
You mean to be able to refresh the IDE without restarting it when a
.project, .classpath changes ? What is the intent of your Eclipse
builder ? Sounds cool.
-Vincent
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
