Hi Mirko,
Mirko Friedenhagen 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?
Actually there is no requirement, that an artifact is copied to target first
before it is added to a repo. With the build helper plugin you can attach
any arbitrary file and most of the plugins allow the configuration of an
individual target or a final name within the target (which is different then
from the name in the repo). But, yes, a POM with packaging pom could point
to itself as artifact.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
