Yup, this is exactly what I do now... There are some plans to add
some support to this in the plugin itself:
http://jira.codehaus.org/browse/MOJO-428
--jason
On Feb 8, 2007, at 8:42 AM, Rupert Smith wrote:
Actually I got it working with:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<executions>
<execution>
<id>attach-artifacts</id>
<phase>package</phase>
<goals>
<goal>attach-artifact</goal>
</goals>
<configuration>
<artifacts>
<artifact>
<file>$
{ project.build.directory}/${project.build.finalName}-retro1.4.jar</
file>
<type>jar</type>
<classifier>retro1.4</classifier>
</artifact>
</artifacts>
</configuration>
</execution>
</executions>
</plugin>
Any plans to build this extra step into the retrotranslator itself?
On 2/8/07, Rupert Smith < [EMAIL PROTECTED]> wrote:
I have succesfully used the retrotranslator plugin to translate my
main build .jar into a seperate one (named - java1.4.jar). Now I
need a way to publish that jar (in parallel to the non-
retrotranslated one) as a different artifact type. There is a
comment in the MOJO-28 Jira from Jason Dillan about this:
Jason Dillon [14/Jul/06 05:52 PM]
>I had originally attempted to add this... but this breaks down
when converting entire trees of jar files.
>So, I had opted to just use the buildhelper plugin to add
artifacts for publishing when needed.
>But... I think that its probably a good idea to support something
like that w/o the buildhelper... just pending how to best implement
it.
Does this work? Any help on how to get it to work? If it can't be
done this way, I will gladly submit a patch to the retrotranslator
plugin to get this working in the way that I need.
- Rupert
[ Show ยป ]
Jason Dillon [14/Jul/06 05:52 PM] I had originally attempted to add
this... but this breaks down when converting entire trees of jar
files. So, I had opted to just use the buildhelper plugin to add
artifacts for publishing when needed. But... I think that its
probably a good idea to support something like that w/o the
buildhelper... just pending how to best implement it.
