[ http://jira.codehaus.org/browse/MPXDOC-114?page=all ]
     
Lukas Theussl closed MPXDOC-114:
--------------------------------

     Resolution: Fixed
    Fix Version: 1.10

Fixed with MPXDOC-130

> cvs-usage presumes pserve protocol on <connection>
> --------------------------------------------------
>
>          Key: MPXDOC-114
>          URL: http://jira.codehaus.org/browse/MPXDOC-114
>      Project: maven-xdoc-plugin
>         Type: Bug

>     Reporter: Erik Husby
>      Fix For: 1.10
>  Attachments: Repository.java.patch, cvs-usage.xml.patch, 
> maven-plugins.patch, maven.patch
>
>
> The Repository report makes some assumptions about ones use of cvs that are 
> not necessarily true.
> 1. The pom.repository.connection is assumed to be the pserve protocol. Not 
> true for our in-house projects.
> 2. The pom.repository.developerConnection is only displayed when there is a 
> pom.repository.connection entry. The two fields are not connected.
> 3. The CVS Access behind firewall is always included if 
> pom.repository.connection is specified. This is not true in our in-house 
> environment.
> The changelog report works fine if only pom.repository.developerConnection is 
> specified, I would like to not specify pom.repository.connnection
> Problem#1 can be addressed by examinging the cvs protocol and adjusting the 
> comments.
> Problem#2 I experimented with modifing the cvs-usage.xml but not being 
> knowledge in velocity, I could not see why problem #2 occurs.
> Problem#3 can be solved in a number of ways from an addition to the 
> pom.repository or by an additional maven-xdoc-plugin property.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to