The following comment has been added to this issue:
Author: Dennis Lundberg
Created: Sun, 25 Jul 2004 6:24 AM
Body:
These sound like good ideas to me too. It felt rather strange having to patch
maven-core because of something that is only needed in one plugin.
1) Separate the scm reports from the xdoc plugin and move them to the scm plugin.
This is something that I'm not sure I know how to do, yet...
2) Keep the gleaning of CVS info out of the org.apache.maven.project.Repository class
and place it in a class in the SCM plugin
So would we have something like o.a.m.scm.cvs.Repository extends
o.a.m.project.Repository or maybe o.a.m.scm.CvsRepository extends
o.a.m.project.Repository?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPXDOC-114?page=comments#action_22277
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPXDOC-114
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPXDOC-114
Summary: cvs-usage presumes pserve protocol on <connection>
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-xdoc-plugin
Assignee: Jason van Zyl
Reporter: Erik Husby
Created: Wed, 7 Jul 2004 4:10 PM
Updated: Sun, 25 Jul 2004 6:24 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
