Thanks! That's pretty much what I need. I didn't even look at the
filtering option because I thought they meant something else. I guess
I should just RT all of the FM. ;-) -K
On Jun 28, 2008, at 8:40 AM, Andrew Robinson wrote:
I just did something like this. Just use the maven assembly plug
actually you may be able to use pom.version, it was the site plugin
that doesn't like dots because it uses velocity.
On 2008-06-28, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> I just did something like this. Just use the maven assembly plugin to
> package your app as a zip, tar or whatever. It ca
On 2008-06-28, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> actually you may be able to use pom.version, it was the site plugin
> that doesn't like dots because it uses velocity.
>
> On 2008-06-28, Andrew Robinson <[EMAIL PROTECTED]> wrote:
>> I just did something like this. Just use the maven asse
I just did something like this. Just use the maven assembly plugin to
package your app as a zip, tar or whatever. It can filter ${ in the
files. It is documented as not liking . In the names though. Steps (I
am on my iPod so this is not 100% accurate):
1) add a poroperty to your pom.xml:
${pom.ver
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 thei
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 a
