Yeah, I wish I knew how to disable the jar plugin... that's why I
posted the antrun solution!
On Wed, Jul 16, 2008 at 7:54 AM, Kristian Rink <[EMAIL PROTECTED]> wrote:
> Stephen;
>
> and first off, thanks a bunch for your hints on that, much appreciated
> (and indeed quite a bit enlightening):
>
> Stephen Connolly schrieb:
> [...]
>> <plugins>
>> <!-- fake out maven and install the binary artifact -->
>> <plugin>
>> <artifactId>maven-antrun-plugin</artifactId>
>> <executions>
>> <execution>
>> <phase>package</phase>
>> <goals>
>> <goal>run</goal>
>> </goals>
>> <configuration>
>> <tasks>
>> <copy
>> file="${basedir}/src/main/jar/${pom.artifactId}-${pom.version}.jar"
>>
>> tofile="${basedir}/target/${pom.artifactId}-${pom.version}.jar"
>> overwrite="true"/>
>> </tasks>
>> </configuration>
>> </execution>
>> </executions>
>> </plugin>
>> </plugins>
> [...]
>> On Wed, Jul 16, 2008 at 7:45 AM, Stephen Connolly
>> <[EMAIL PROTECTED]> wrote:
>>> I would do a simple trickery...
>>>
>>> disable the jar plugin and then use the build-helper plugin to attach
>>> the jar file.
>
> Is any of the two approaches to be preferred in the given use case?
> Personally, from my current point of knowledge, though, I'd go for
> antrun simply because so far I have never disabled a plugin in maven2
> and am not sure I know how to get that done. ;)
>
> Cheers & thanks again,
> Kristian
>
>
> --
> Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
> jab: [EMAIL PROTECTED] * icq: 48874445 * fon: ++49 176 2447 2771 "One
> dreaming alone, it will be only a dream; many dreaming together is the
> beginning of a new reality." (Hundertwasser)
>
>
> ---------------------------------------------------------------------
> 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]
