Actually, it turns out that the appassembler plugin is almost what I
want. It requires that the project be installed to be included in the
classpath and I'd rather run my project jar from the target directory.
My purpose here is to provide a way for people who modify the source
to test their mods without installing and such. It would be more
streamlined.
My distribution profile, which uses the assembly plugin, packages the
project jar into a lib directory along with the dependencies. Then I
can use Dawid Weiss's invoker jar (not in Maven, unfortunately) to
automagically put everything in that directory into the classpath.
-K
On Jun 27, 2008, at 10:34 AM, Kathryn Huxtable wrote:
I am using the jar plugin to add the dependencies to the manifest of
my project's jar, and the dependencies plugin to create a lib
directory to contain them. I like that my jar has the version number
appended.
Given that, is there any way to inject the version number into a
shell script and a Windows batch file to create runner scripts
during packaging? The essence of the script would be a line of the
form:
java -jar target/artifactId-version.jar $*
or something like that.
I've looked at Codehaus's appassembler plugin and it does too much.
I haven't really looked at Codehaus's xslt plugin, but maybe that's
the way to go.
Any ideas?
-K, who has always gotten good suggestions from this list.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
