maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tamás Cservenák (JIRA) <j...@codehaus.org>
Subject [jira] Commented: (MNG-4716) Make the interpolated POM of a released artifact accessible too
Date Thu, 01 Jul 2010 17:33:32 GMT

    [ http://jira.codehaus.org/browse/MNG-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226941#action_226941
] 

Tamás Cservenák commented on MNG-4716:
--------------------------------------

If there are better way to describe "how this build (how this very artifact) was built", just
explain it, since that's the one thing I am interested in.

> Make the interpolated POM of a released artifact accessible too
> ---------------------------------------------------------------
>
>                 Key: MNG-4716
>                 URL: http://jira.codehaus.org/browse/MNG-4716
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Deployment
>            Reporter: Tamás Cservenák
>
> Make the interpolated POM of a released artifact accessible too. Whether embedded into
deployed JAR, or next to "real" POM.
> Reasoning: the interpolated POM is not for "downstream consumers" (build consuming this
artifact), but for about "how this build is done". We always argument against this in way
that "profiles" and plugin settings (and other things) are lost with interpolated POM. That's
true, but again, I'd like to have an interpolated POM of a _released_ artifact that would
describe me _how this artifact was built_, and not to be referenced and consumed by others
(as dependency or whatever).
> So, after deploying org.test:foo:1.0. i'd like to have:
> /org/test/foo/1.0
> foo-1.0.pom
> foo-1.0.pom.interpolated
> foo-1.0.jar
> Or something similar (having the interpolated POM embedded in JAR). Not embedding would
allow us to "calculate" interpolated poms for already released POMs too.
> So, ultimately, POM is "changing", yes, but only when it is consumed. But during release,
it is frozen, and will stay like that, since all it's parent POM, deps, plugins are released,
are not "moving targets" anymore.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message