You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2003/03/01 00:59:44 UTC
[maven-bug] Updated: (MAVEN-305) changelog plug-in cannot parse non-pserver remote cvs repository connections
The following issue has been updated:
Updater: robert burrell donkin (mailto:robertburrelldonkin@blueyonder.co.uk)
Date: Fri, 28 Feb 2003 5:59 PM
Comment:
patch containing fix and testcase.
Changes:
[Attachment] [changelog.patch] was added
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-305&page=history
---------------------------------------------------------------------
View the issue:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-305
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-305
Summary: changelog plug-in cannot parse non-pserver remote cvs repository connections
Type: Bug
Status: Assigned
Priority: Minor
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Component: None
Versions:
1.0-beta-8
Assignee: Jason van Zyl
Reporter: robert burrell donkin
Created: Fri, 28 Feb 2003 5:58 PM
Updated: Fri, 28 Feb 2003 5:59 PM
Environment: macOS X
using ssh-agent and public key to connect to cvs.apache.org
Description:
when running site:generate the CVS/root file is overwritten with the repository setting from maven.
this is a PITA since this means i have to edit this file and replace :pserver:anoncvs@... with rdonkin@... every time i want to use cvs after running site:generate. the obvious solution seemed (to me) to use rdonkin@... in the repository setting in the project.xml (well alright - i used a variable which i could set to :pserver:anoncvs@... in the project.properties files and then override in the build.xml).
anyway, the only problem with this plan was that the repository scm parser in the changelog plug-in can only parse pserver remote cvs repository connections.
i've created a patch which allows non-pserver remote repository descriptions to be parsed together with a patch for the test case.
an example of the type of connection which will work with this patch is:
<connection>scm:cvs:rdonkin@cvs.apache.org:/home/cvs:jakarta-commons</connection>
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.werken.com/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: Conventions for messages
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sat, 2003-03-01 at 17:31, O'brien, Tim wrote:
> What is the right thing to do when internationalizing a message? I don't
> know seven languages (yet), and I'm wondering what the convention is for
> adding a new message resource.
Most times the english message will be added which is the default. This
is generally ok because the folks translating the messages are here. If
the locale specific message isn't found the english message will be
used. Anglo-centric but that's the way it is right now.
> --------
> Tim O'Brien
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-dev-help@jakarta.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
Conventions for messages
Posted by .
What is the right thing to do when internationalizing a message? I don't
know seven languages (yet), and I'm wondering what the convention is for
adding a new message resource.
--------
Tim O'Brien