[jira] Updated: (MNG-4316) uniqueVersion flag doesn't work anymore for snapshotRepository
[ http://jira.codehaus.org/browse/MNG-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-4316: -- Fix Version/s: 3.0-alpha-3 > uniqueVersion flag doesn't work anymore for snapshotRepository > -- > > Key: MNG-4316 > URL: http://jira.codehaus.org/browse/MNG-4316 > Project: Maven 2 > Issue Type: Bug > Components: Deployment >Affects Versions: 3.0-alpha-3 > Environment: all >Reporter: Olivier Lamy > Fix For: 3.0-alpha-3 > > > Testing it site-attach-descriptor in site plugin 3.x branch. > The uniqueVersion flag is not supported 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
[jira] Created: (MNG-4316) uniqueVersion flag doesn't work anymore for snapshotRepository
uniqueVersion flag doesn't work anymore for snapshotRepository -- Key: MNG-4316 URL: http://jira.codehaus.org/browse/MNG-4316 Project: Maven 2 Issue Type: Bug Components: Deployment Affects Versions: 3.0-alpha-3 Environment: all Reporter: Olivier Lamy Testing it site-attach-descriptor in site plugin 3.x branch. The uniqueVersion flag is not supported 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
[jira] Issue Comment Edited: (MSHARED-120) Unable to generate single report with latest maven-reporting-impl
[
http://jira.codehaus.org/browse/MSHARED-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188129#action_188129
]
Benjamin Bentmann edited comment on MSHARED-120 at 8/22/09 7:20 AM:
Given that this patch restores significant functionality, how about using this
patch to get back to some normal (i.e. Maven parseable) version number like
"2.1.0" for the maven-reporting-impl? Likewise, the trunk of
maven-reporting-impl seems abandoned, we had two releases from the branch
already, so maybe we should just drop trunk and make the branch the trunk?
was (Author: bentmann):
Given that this patch restores significant functionality, how about using
this patch to get back to some normal (i.e. Maven parseable) version number
like "2.1.0" for the maven-reporting-impl? Likewise, the trunk of
maven-reporting-impl seems abonded, we had two releases from the branch
already, so maybe we should just drop trunk and make the branch the trunk?
> Unable to generate single report with latest maven-reporting-impl
> -
>
> Key: MSHARED-120
> URL: http://jira.codehaus.org/browse/MSHARED-120
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-reporting-impl
>Affects Versions: maven-reporting-impl 2.0.4.1, maven-reporting-impl
> 2.0.4.2
>Reporter: Vincent Siveton
>Priority: Blocker
> Attachments: MSHARED-120.patch, reporting.patch
>
>
> Recently, I fixed several report plugins (changelog, changes etc.) to use
> Doxia 1.0 and latest maven-reporting-impl.
> The main goal was to make reporting plugins available in PDF (see MPDF-26 and
> doc [1])
> I notified that running a single report doesn't work but works when coupling
> with maven-site-plugin 2.0.x.
> For instance, run:
> {noformat}
> mvn org.apache.maven.plugins:maven-changelog-plugin:2.2-SNAPSHOT:changelog
> {noformat}
> In Doxia 1.0, the SiteRenderSink [2] uses a StringWriter by default to use
> getBody() in the renderer [3]. So running a single report doesn't write a
> file with reporting-impl:2.0.4.2
> In MPIR 2.1.2, we overrided the mojo.execute() to handle a default renderer
> [4] so we are able to run a single report. I propose to move this logic in
> AbstractMavenReport.
> [1]
> http://maven.apache.org/plugins/maven-pdf-plugin-1.1-SNAPSHOT/examples/configuring-reports.html#Maven_Reporting_Plugins_Issues
> [2]
> http://maven.apache.org/doxia/doxia-sitetools-1.0.x/xref/org/apache/maven/doxia/siterenderer/sink/SiteRendererSink.html#47
> [3]
> http://maven.apache.org/doxia/doxia-sitetools-1.0.x/xref/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.html#433
> [4]
> http://maven.apache.org/plugins/maven-project-info-reports-plugin/xref/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.html#137
--
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] Commented: (MSHARED-120) Unable to generate single report with latest maven-reporting-impl
[
http://jira.codehaus.org/browse/MSHARED-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188129#action_188129
]
Benjamin Bentmann commented on MSHARED-120:
---
Given that this patch restores significant functionality, how about using this
patch to get back to some normal (i.e. Maven parseable) version number like
"2.1.0" for the maven-reporting-impl? Likewise, the trunk of
maven-reporting-impl seems abonded, we had two releases from the branch
already, so maybe we should just drop trunk and make the branch the trunk?
> Unable to generate single report with latest maven-reporting-impl
> -
>
> Key: MSHARED-120
> URL: http://jira.codehaus.org/browse/MSHARED-120
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-reporting-impl
>Affects Versions: maven-reporting-impl 2.0.4.1, maven-reporting-impl
> 2.0.4.2
>Reporter: Vincent Siveton
>Priority: Blocker
> Attachments: MSHARED-120.patch, reporting.patch
>
>
> Recently, I fixed several report plugins (changelog, changes etc.) to use
> Doxia 1.0 and latest maven-reporting-impl.
> The main goal was to make reporting plugins available in PDF (see MPDF-26 and
> doc [1])
> I notified that running a single report doesn't work but works when coupling
> with maven-site-plugin 2.0.x.
> For instance, run:
> {noformat}
> mvn org.apache.maven.plugins:maven-changelog-plugin:2.2-SNAPSHOT:changelog
> {noformat}
> In Doxia 1.0, the SiteRenderSink [2] uses a StringWriter by default to use
> getBody() in the renderer [3]. So running a single report doesn't write a
> file with reporting-impl:2.0.4.2
> In MPIR 2.1.2, we overrided the mojo.execute() to handle a default renderer
> [4] so we are able to run a single report. I propose to move this logic in
> AbstractMavenReport.
> [1]
> http://maven.apache.org/plugins/maven-pdf-plugin-1.1-SNAPSHOT/examples/configuring-reports.html#Maven_Reporting_Plugins_Issues
> [2]
> http://maven.apache.org/doxia/doxia-sitetools-1.0.x/xref/org/apache/maven/doxia/siterenderer/sink/SiteRendererSink.html#47
> [3]
> http://maven.apache.org/doxia/doxia-sitetools-1.0.x/xref/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.html#433
> [4]
> http://maven.apache.org/plugins/maven-project-info-reports-plugin/xref/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.html#137
--
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] Closed: (MNG-4315) Arbitrary command line environment variables no longer pass to POM
[
http://jira.codehaus.org/browse/MNG-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4315.
--
Assignee: Benjamin Bentmann
Resolution: Not A Bug
This change in behavior is indeed intentional. The simple rationale: {{${var}}}
!= {{${project.var}}} != {{${env.var}}}, i.e. the prefix of an expression
matters. So, when you want to override a property from the CLI be sure to use
the proper name, e.g. {{-Denv.svnRevNumber=xx}} in your example.
> Arbitrary command line environment variables no longer pass to POM
> --
>
> Key: MNG-4315
> URL: http://jira.codehaus.org/browse/MNG-4315
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line, POM
>Affects Versions: 2.1.0, 2.2.0, 2.2.1
>Reporter: Mark Anderson
>Assignee: Benjamin Bentmann
>
> Up through Maven v2.0.9 we used to be able to specify arbitrary command line
> variables such as:
> mvn clean install -DsvnRevNumber=xx
> And that variable was available in a POM with:
> ${env.svnRevNumber}
> At v2.1.0 this stopped working and still seems to be that way in v2.2.1.
> Though this may not have been the original intent, it was a useful feature to
> get dynamic information into the POM and passed to a custom mojo.
--
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
