Ok, it is getting closer.
Here is my pom.xml and plugin:
groupIdorg.delta.esp.dap.c2.bpel/groupId
version1.0.0.0/version
artifactIdmis-file-intake/artifactId
packagingjar/packaging
plugin
groupIdorg.codehaus.mojo/groupId
For #1, I have no idea. There is probably a way to suppress the Jar
but I've never needed to do this myself.
For #2, this is what you're looking for:
dependency
groupIdorg.delta.esp.dap.bpel/groupId
artifactIdmis-file-intake/artifactId
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
Not sure i understand what this plugin will do for the artifact.
I have a modele, that runs an ant task that creates a jar. So maven module
is not creating the jar from the target DIR, the ant task already creates
the jar I want inside the target DIR that I want to add to my repository.
On
If I understand you correctly, build-helper-maven-plugin should be
what you're looking for:
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
Wayne
On 7/26/07, Mick Knutson [EMAIL PROTECTED] wrote:
To give a little more idea of what I am looking for:
I want to see
Yes, I think I understand, and I still think the
build-helper-maven-plugin can help you. Take a look at goal
attach-artifact in the usage page:
http://mojo.codehaus.org/build-helper-maven-plugin/howto.html
Wayne
On 7/26/07, Mick Knutson [EMAIL PROTECTED] wrote:
Not sure i understand what this
