To give a little more idea of what I am looking for:
I want to see if in my jar module, I can have something like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>package</goal>
</goals>
</execution>
</executions>
<configuration>
<includes>/target/bpel.jar</includes>
</configuration>
</plugin>
Then the bpel.jar can get renamed to moduleone-1.0.3.jar and added to my
repository (if I use the install goal)
But regaurdless, moduleone-1.0.3.jar is now a valid dependency for my
moduletwo module.
On 7/26/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
I have a module that is defined as a jar as this jar is a dependency
within other modules in my project.
This pom.xml: jar calls a bpel and task that creates a bpel suitcase JAR.
The bpel jar is the artifact I actually want in my repository and available
as a dependency.
So, how do I accomplish this as I end up with 2 different jars right now.
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
