[jira] Commented: (MNG-2971) Variables are not replaced into installed pom file
[
http://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264576#action_264576
]
Andreas Pieber commented on MNG-2971:
-
Hey Luke, would you mind sharing the antrun configuration section of your pom
with us? :)
> Variables are not replaced into installed pom file
> --
>
> Key: MNG-2971
> URL: http://jira.codehaus.org/browse/MNG-2971
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment, Inheritance and Interpolation
> Environment: Windows, Solaris
> Maven version 2.0.4
>Reporter: Laurent Dauvilaire
>Assignee: Ralph Goers
> Fix For: Issues to be reviewed for 3.x
>
>
> Variables are not replaced into installed pom file.
> Here is a sample pom file
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.xxx.root
> root
> pom
> ${prop.version}
> My Project
> ...
>
> 3.0.20
>
>
> The installed pom is into
> ${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
> is the same as the project pom file but the version referenced into the
> installed pom file is ${prop.version} instead of 3.0.20
> which creates problem to artifacts depending of this one.
> Thanks in advance
--
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
[jira] Created: (MSITE-614) site plugin failure when forking a lifecycle
site plugin failure when forking a lifecycle Key: MSITE-614 URL: https://jira.codehaus.org/browse/MSITE-614 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0 Reporter: Andreas Pieber Attachments: 5ebbfe13_maven-test.tar.gz If you execute "mvn site" in the attached test project it fails because of the forked cycles. The test project could therefore not be resolved in the maven plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280972#comment-280972 ] Andreas Pieber commented on MSITE-614: -- btw, using the site plugin in version 2.3 (no forks) works fine. > site plugin failure when forking a lifecycle > > > Key: MSITE-614 > URL: https://jira.codehaus.org/browse/MSITE-614 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Andreas Pieber > Attachments: 5ebbfe13_maven-test.tar.gz > > > If you execute "mvn site" in the attached test project it fails because of > the forked cycles. The test project could therefore not be resolved in the > maven plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-285) regression: duplicate files added to the assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255752#action_255752 ] Andreas Pieber commented on MASSEMBLY-285: -- Please reopen this issue. I've the same problems as Daniel thanks > regression: duplicate files added to the assembly > - > > Key: MASSEMBLY-285 > URL: http://jira.codehaus.org/browse/MASSEMBLY-285 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 >Reporter: Brett Porter >Assignee: John Casey >Priority: Blocker > Fix For: 2.2-beta-3 > > > I found that it was possible to add a file twice to the assembly through > different filesets (a zip file) so that when it extracted it prompted for > overwrite. > It should error out or collapse the entries (as 2.1 did). -- 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
[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306614#comment-306614 ] Andreas Pieber commented on MSITE-614: -- well, I know that commenting out features-maven-plugin works, but why does it work using version 2.3 of site? > site plugin failure when forking a lifecycle > > > Key: MSITE-614 > URL: https://jira.codehaus.org/browse/MSITE-614 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Andreas Pieber > Attachments: 5ebbfe13_maven-test.tar.gz > > > If you execute "mvn site" in the attached test project it fails because of > the forked cycles. The test project could therefore not be resolved in the > maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307121#comment-307121 ] Andreas Pieber commented on MSITE-614: -- fair enough; still the question persists: is it a regression then or something we need to change in our configuration? > site plugin failure when forking a lifecycle > > > Key: MSITE-614 > URL: https://jira.codehaus.org/browse/MSITE-614 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Andreas Pieber > Attachments: 5ebbfe13_maven-test.tar.gz > > > If you execute "mvn site" in the attached test project it fails because of > the forked cycles. The test project could therefore not be resolved in the > maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
