poms have an implicit basedir, so copying the pom to target would change
the implicit basedir.
pom packaging can be hijacked when you want to attach a primary artifact
without defining a custom packaging.
Not saying these are good reasons, but they are a sort of reason!
There may be others
On 26 July 2012 08:01, Mirko Friedenhagen <mfriedenha...@gmail.com> wrote:
> Hello,
>
> while developing a plugin, I stumbled upon the IMO irregularity, that
> projects with packaging POM have no artifact (i.e.
> project.getArtifact() will return `null)`. At least my usecase would
> have been easier when:
> - the POM of a POM project would be it's own artifact.
> - the had been copied to `target` as ${project.artifactId}-${version}.pom
>
> Are there any reasons why this is handled differently?
>
> Regards Mirko
> --
> http://illegalstateexception.blogspot.com/
> https://github.com/mfriedenhagen/
> https://bitbucket.org/mfriedenhagen/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
