Will Gwaltney wrote:

Hi Brett,

Thanks for the information. I've been told that due to jcoverage/Cobertura licensing issues we can't directly call the main Cobertura class, thus the need to do getRuntime.exec().
This really depends. The plugin could well be licensed GPL, just like corbetura. Maven won't be able to host it, but it will work all the same.

Glad to hear that there's going to be support for system.exec in alpha 3; is 
there going to be a way to grab the return code and the streams?  Right now 
I've taken the easy way out and am using the Execute class from Ant.  I don't 
like the Ant dependency, but I figured when the time comes the appropriate 
functionality can be moved over into a Maven utility class.
You can already do "exec" - check out the Commandline class in plexus-utils (it is used in plugins such as javadoc already). IT does all you need here. The support coming is proper passing of a classpath.

Another thing I'm swiping from Ant is the way they use wildcards in filesets.  
That'll save a lot of typing when adding jars to a classpath.  Will Maven have 
something similar?  (This might be another good opportunity for an Ant-derived 
utility class! :-)
Look in plexus-utils here again. FileUtils contains a way to match patterns which I think is what you are after. For dependencies, they should be handed to you by the mojo.

We'll definitely contribute the Cobertura plugin back out somewhere when it's 
ready.  The Cobertura project is a definite possibility.  Would it make more 
sense to contribute it directly to Maven?  Either way would be fine with us.
If corbertura will maintain it, it is better there. The GPL part is a bit hairy for us hosting it, and if we have too many plugins they may become unmaintained. Generally, the project have the know-how to make it the best it can be, and we'll help out wherever possible.

With m2, it is also possible to share a lot of code between the mojo and ant tasks, so it shouldn't be a huge burden.

The other alternative is to fire up a project somewhere (we haven't used java.net yet! :) where folks such as yourself can maintain plugins dear to them.

BTW, if you need any help with the system.exec API let me know; since I need 
it, I've got some spare cycles available to work on it.
Checkout some of the other plugins, I think you'll find all you need.

Thanks,
Brett



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to