Wayne,
Thanks for the reply.
I am the resident expert with Maven, so I am the only help I have. If we
had someone like you are describing, I would very happy indeed. So far
though, things are looking good, but it's like walking through the dark with
a flashlight.
As for the other formats, I'm not looking to get rid of them forever, only
in the iterative development cycle where I compile, deploy and test upwards
to 20 times a day. The jar is all I need in this situation.
The old build was done exclusively with Ant.
My guess about why I'm generating so many different deployment artifacts is
that it is due to the assembly plugin in my project pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>${maven.assembly.plugin.version}</version>
<executions>
<execution>
<id>create-project-bundle</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptorRefs>
<descriptorRef>project</descriptorRef>
</descriptorRefs>
</configuration>
</execution>
</executions>
</plugin>
Is there a way to configure this to only generate the jar? If I am to use
the shade plugin, how do I configure it to indicate the suppression I'm
looking for? I read the usage page for both plugins but haven't found what
I'm looking for (though I admit I could easily have missed it).
Thanks,
Scott
--
View this message in context:
http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5154628.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
