maven.final.name

2003-08-25 Thread Leo Sutic
When defining a postGoal to jar:jar, I expect the maven.final.name variable to point to the recently-created jar file. This is correct when jar:jar is invoked directly, but not when it is invoked via jar:snapshot. jar:snapshot does a of maven.final.name to snapshotSignature. However, that j:set is

RE: Accessing maven.compile.src.set and maven.final.name

2003-08-23 Thread Leo Sutic
On Sat, 23 Aug 2003, O'Fallon, Paul (MAN-Corporate) wrote: > ... Thanks! /LS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Accessing maven.compile.src.set and maven.final.name

2003-08-23 Thread Leo Sutic
On Sat, 23 Aug 2003, Jason van Zyl wrote: > On Sat, 2003-08-23 at 06:49, Leo Sutic wrote: > maven.compile.src.set. Basically antlr generates the specified sources > from a grammar and then appends the path containing the generated > sources to maven.compile.src.set. Thanks! That

RE: Accessing maven.compile.src.set and maven.final.name

2003-08-23 Thread Leo Sutic
Thanks, however I think that the torque plugin does things a bit differently than what I want to achieve. In particular: + Must be run explicitely, and not as a preGoal to java:compile. + Generates into the src/java directory, and not a temporary directory: >>> outputDirectory="${torque.j

Accessing maven.compile.src.set and maven.final.name

2003-08-23 Thread Leo Sutic
Hi all, I have been trying Maven for the past week, and come up against two major difficulties: CODE GENERATOR -- I have a code-generator task written for Ant that I'm trying to turn into a Maven plugin. Since it is a code generator, I need to do the following: 1. Run the code gene