> >
> > Is not installing the pom if a classifier is used the intended
> behaviour?
>
> No, it was reported and fixed in version 2.3 of the install plugin.
> What version are you using? Depending on what version is set in the
> super pom inside Maven, you may need to specify a later version to
>
On Wed, Apr 22, 2009 at 2:03 AM, Niklas Grossmann wrote:
> Hi All,
>
> when I do a 'mvn install' and the maven jar/ejb plugin is configured to use a
> classifier e.g.
> ...
> only the .jar file gets installed in the local repository. If I don't use a
> classifier the pom gets installed alongside
H...
what I would do is run two executions of the jar plugin...
execution #1 generates the artifact without a classifier but excludes the
persistance.xml
execution #2 generates the artifact with the classifier and includes the
persistance.xml
That would at least work around your issue (as y
Since nobody answered my question I'll try to explain why I think this is a
problem. I use profiles and filters to adjust e.g. persistence.xml files to a
given environment, e.g. dev, staging, prd. Because the persistence.xml file is
part of the installed artifact I use classifiers to distinguish
Hi All,
when I do a 'mvn install' and the maven jar/ejb plugin is configured to use a
classifier e.g.
...
maven-jar-plugin
dev
...
only the .jar file gets installed in the local repository. If I don't use a
classifier the pom gets installed alongside the .jar file. and
