Ben Walding wrote:
Here's how you go about answering this question for yourself!
thanks for the info below! quite useful for a newcomer to maven.
4. Unfortunately the plugin only puts LICENSE.txt into META-INF, so you're going to have to raise a feature request and include a patch (well we can all dream!)do you mean to say that you *only* need to change plugin.jelly?
<metainf dir="${basedir}">
<include name="LICENSE.txt"/>
<your paths go here.../>
</metainf>
say, changing it to something like:
<metainf dir="${basedir}"
includes="${maven.jar.metainf.includes}"
excludes="${maven.jar.metainf.excludes}">
<include name="LICENSE.txt"/>
</metainf>
where the properties are defined in one of the properties files?
I've tried this and it doesn't work. Do the properties need to be initialised somewhere?
BTW, is there a way of setting a property *local* to a goal or a task,
rather than in properties files?
5. To add extra bits to your jar, take a look at java:jar-resources or if that is too primitive, write a preGoal for java:jar that copies
the appropriate files into ${maven.build.dest} - copy the general concept from java:jar-resources. Essentially the POM build/resources element determines what ends up in the jar.
will look into this.
If you want to "hack" your plugin to make it work for you / experiment... edit $MAVEN_HOME/plugins/<plugin>/plugin.jelly (this will be overwritten during bootstrap, so it is only useful for quick hacks in testing).
sorry - don't follow you. what do you mean by bootstrap here? you mean when I execute maven? then how are the changes going to show up?
Then when you're satisfied with your changes, submit patches back to the maven developer list.
will do if I get it working :-) Thanks, Mauro -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
