You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "creyle (JIRA)" <ji...@codehaus.org> on 2007/12/19 12:26:57 UTC
[jira] Created: (MPIR-78) Unable to exclude scm anonymous access
info
Unable to exclude scm anonymous access info
-------------------------------------------
Key: MPIR-78
URL: http://jira.codehaus.org/browse/MPIR-78
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Affects Versions: 2.0.1, 2.1, 2.2
Environment: WinXP SP2 fully patched, jdk 1.6.0_03, Maven 2.0.8, Continuum 1.1
Reporter: creyle
Priority: Minor
Currently there's no way to exclude the information, about anonymous access to the source repository, from the scm report.
In the doc [1] it says, the anonymousConnection defaults to project.scm.connection in POM, but explicitly setting a blank <anonymousConnection/> configuration element just has no effect, as discussed in the maven user list [2], while setting it to a invalid value e.g. <anonymousConnection>foo</anonymousConnection> still has no effect with 2.0.1, but will cause "horrible" problems with 2.1-SNAPSHOT.
[1] http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html#anonymousConnection
[2] http://www.nabble.com/forum/ViewPost.jtp?post=14413537&framed=y&skin=177
--
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] Updated: (MPIR-78) Unable to exclude scm anonymous access
info
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MPIR-78:
--------------------------------
Component/s: scm
> Unable to exclude scm anonymous access info
> -------------------------------------------
>
> Key: MPIR-78
> URL: http://jira.codehaus.org/browse/MPIR-78
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0.1
> Environment: WinXP SP2 fully patched, jdk 1.6.0_03, Maven 2.0.8, Continuum 1.1
> Reporter: creyle
> Priority: Minor
>
> Currently there's no way to exclude the information, about anonymous access to the source repository, from the scm report.
> In the doc [1] it says, the anonymousConnection defaults to project.scm.connection in POM, but explicitly setting a blank <anonymousConnection/> configuration element just has no effect, as discussed in the maven user list [2], while setting it to a invalid value e.g. <anonymousConnection>foo</anonymousConnection> still has no effect with 2.0.1, but will cause "horrible" problems with 2.1-SNAPSHOT.
> [1] http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html#anonymousConnection
> [2] http://www.nabble.com/forum/ViewPost.jtp?post=14413537&framed=y&skin=177
--
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: (MPIR-78) Unable to exclude scm anonymous access
info
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MPIR-78.
-------------------------------
Assignee: Vincent Siveton
Resolution: Not A Bug
Yes you could do it if you leave empty scm.connection tag ie:
{noformat}
<project>
...
<scm>
<!-- Unspecified <connection/> tag -->
<developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/</developerConnection>
<url>http://svn.apache.org/viewvc/maven/plugins/trunk/maven-project-info-reports-plugin/</url>
</scm>
...
</project>
{noformat}
BUT it doesn't work using an empty <anonymousConnection/> tag due to Plexus constraints.
I updated the doc in r674128
> Unable to exclude scm anonymous access info
> -------------------------------------------
>
> Key: MPIR-78
> URL: http://jira.codehaus.org/browse/MPIR-78
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0.1
> Environment: WinXP SP2 fully patched, jdk 1.6.0_03, Maven 2.0.8, Continuum 1.1
> Reporter: creyle
> Assignee: Vincent Siveton
> Priority: Minor
>
> Currently there's no way to exclude the information, about anonymous access to the source repository, from the scm report.
> In the doc [1] it says, the anonymousConnection defaults to project.scm.connection in POM, but explicitly setting a blank <anonymousConnection/> configuration element just has no effect, as discussed in the maven user list [2], while setting it to a invalid value e.g. <anonymousConnection>foo</anonymousConnection> still has no effect with 2.0.1, but will cause "horrible" problems with 2.1-SNAPSHOT.
> [1] http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html#anonymousConnection
> [2] http://www.nabble.com/forum/ViewPost.jtp?post=14413537&framed=y&skin=177
--
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] Updated: (MPIR-78) Unable to exclude scm anonymous access
info
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MPIR-78:
--------------------------------
Affects Version/s: (was: 2.2)
(was: 2.1)
Issue Type: Improvement (was: Bug)
> Unable to exclude scm anonymous access info
> -------------------------------------------
>
> Key: MPIR-78
> URL: http://jira.codehaus.org/browse/MPIR-78
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.0.1
> Environment: WinXP SP2 fully patched, jdk 1.6.0_03, Maven 2.0.8, Continuum 1.1
> Reporter: creyle
> Priority: Minor
>
> Currently there's no way to exclude the information, about anonymous access to the source repository, from the scm report.
> In the doc [1] it says, the anonymousConnection defaults to project.scm.connection in POM, but explicitly setting a blank <anonymousConnection/> configuration element just has no effect, as discussed in the maven user list [2], while setting it to a invalid value e.g. <anonymousConnection>foo</anonymousConnection> still has no effect with 2.0.1, but will cause "horrible" problems with 2.1-SNAPSHOT.
> [1] http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html#anonymousConnection
> [2] http://www.nabble.com/forum/ViewPost.jtp?post=14413537&framed=y&skin=177
--
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