Hi again!
When I'm using the ear-plugin, the same issue as with the ejb-plugin arises.
It doesn't have support for the classifier tag. In my webapp, I configure my
profile like this:
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>war</goal>
</goals>
<configuration>
<classifier>prod</classifier>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
and end up with an artifact named [artifactId-version-classifier.war]. Does
anybody know how to achieve this with the ear-plugin, or if it is at all
possible? I find it very usefull to be able to "tag" my artifacts using the
classifer based on what profile was used to build it.
Are there anybody else out there who use classifier to build, for instance,
a webapp with different name for development, testing, and production?
Best regards
Bent
On 9/12/06, Bent André Solheim <[EMAIL PROTECTED]> wrote:
Hi all!
I have an ejb-project that I have to build with several sets of
property-files. In the past, I have used profiles and configured the
jar-plugin with the <classifier/> tag for each set of propery-files. I would
like to do this with ejb projects also.
What I have found is that the ejb-plugin does not support classifier
directly, but I can configure the jar-plugin with the classifier I want.
This works pretty well, but configuring the jar-plugin in the profile seems
to clear the keys and values put in the MANIFEST.MF file by the
ejb-plugin. Does anybody know if there is any plans to put classifier
support in the ejb-plugin, or if there are other ways to achieve what I
want? As a temporary solution, I set the finalName manually in the different
profiles.
Hope to hear from you!
Best regards
Bent André Solheim
