> > >> *.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 ? > Well, I'm not familiar with a view for the ant plugin, but there are several plugin's for ant available.
>It will be hard to separate >junit/compilet stuff from the rest as it is viewed as a black block. > Let me elaborate, in the context of ant. When I run an ant target with a junit task, I can register different listeners with the TestRunner to process the results. Conceptually, you should be able to register another listener only when running under eclipse, and that listener should show you the results in the an eclipse view. Now, I don't know if it is currently supported, but it should be possible through an eclipse extension point to drive the existing junit view so you don't have to write a new one. If it's not supported, an extension point should be requested of the Eclipse team. >But >actually, maybe we simply need to replace the maven driver/App by an >eclipse driver. > I don't know *anything* about the maven internal architecture, so I won't comment on this part. >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. > > >>>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 > > After I get my eclipse builder(s) done, perhaps. I already have my coding hand in a about 3 open source pies, not to mention my kibitzing on new features for other projects. >> 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 ? > Not so much refresh, but integrate. That is, if maven re-writes the .classpath and .project files in their entirety, but I've got some other eclipse plugin that adds additional information to a .project file that Maven doesn't know about, that information will get lost. That would be bad. *IF* Maven acts like it owns those files, it needs to handle ALL (hah!) the possibilities. >What is the intent of your Eclipse >builder ? Sounds cool. > My builder is for driving Enhydra's xml compiler (http://xmlc.enhydra.org). Essentially, it builds Java classes from HTML files, so it is added to an existing Java project. Other similar types of plugins (in regard to being pre-java builders) are: AspectJ pre-processor and Compiler-Compilers that build Java from a grammar. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
