[ http://jira.codehaus.org/browse/SCM-138?page=all ]
Emmanuel Venisse closed SCM-138:
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0-beta-3
Done.
> clearcase-settings.xml is been searched for in the wrong dir
> --
Create a utility class for scm url checking/parsing
---
Key: SCM-139
URL: http://jira.codehaus.org/browse/SCM-139
Project: Maven SCM
Type: New Feature
Components: maven-scm-api
Reporter: Dennis Lundberg
There
Hi,
I've finally finished the Bazaar provider.
What is the procedure to get it into the maven-scm tree?
Regards
Torbjørn
[ http://jira.codehaus.org/browse/SCM-139?page=all ]
Dennis Lundberg updated SCM-139:
Attachment: ScmUrlUtils.java
> Create a utility class for scm url checking/parsing
> ---
>
> Key: SCM-139
>
File an issue in jira (http://jira.codehaus.org/browse/SCM) and attach your
code.
Emmanuel
Torbjørn Smørgrav a écrit :
Hi,
I've finally finished the Bazaar provider.
What is the procedure to get it into the maven-scm tree?
Regards
Torbjørn
[ http://jira.codehaus.org/browse/SCM-139?page=comments#action_56596 ]
Emmanuel Venisse commented on SCM-139:
--
- isValid(): I'd prefer an other name like isValidGeneralFormat
- remove "void validate( scmUrl )
- getSeparator() : I prefer a String as retur
Torbjørn Smørgrav wrote:
Hi,
I've finally finished the Bazaar provider.
What is the procedure to get it into the maven-scm tree?
Regards
Torbjørn
Hello,
The first thing to do is create a new issue for this in jira:
http://jira.codehaus.org/browse/SCM
Read through this document:
http://m
I'm agree.
Lukas Theussl a écrit :
According to [1], the format for a scm url is
scm
ie, scm:| would not be a valid form.
I would also find it confusing if there were other colons in one of the
variables, so I think it should not be allowed.
-Lukas
[1] http://maven.apache.org/scm/scm-url
Do you use maven-scm in changelog plugin? I guess it isn't (same thing for m2
changelog plugin)
I think it will be a good idea to use it for scm url parsing and changelog command, so this plugin
will do only the page result generation from changelog output and will can obtain bug fixes from
mav
You are right, it's not currently used and I totally agree that it
should be. However, I am just now preparing a new release which I expect
to be ready next week (when MPCHANGELOG-81 is resolved), and I don't
want to hold that back now.
-Lukas
Emmanuel Venisse wrote:
Do you use maven-scm in
[ http://jira.codehaus.org/browse/SCM-135?page=all ]
Emmanuel Venisse closed SCM-135:
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0-beta-3
Applied.
Frederic, can you provide a patch for documentation of settings.xml?
> C
Refactoring clearcase-setting.xml loading
-
Key: SCM-140
URL: http://jira.codehaus.org/browse/SCM-140
Project: Maven SCM
Type: Task
Components: maven-scm-provider-clearcase
Versions: 1.0-alpha-3
Reporter: Emman
[ http://jira.codehaus.org/browse/SCM-140?page=all ]
Emmanuel Venisse updated SCM-140:
-
Version: (was: 1.0-alpha-3)
1.0-beta-3
Fix Version: 1.0-beta-3
> Refactoring clearcase-setting.xml loading
>
No problem Lukas. It can be done in next version.
Emmanuel
Lukas Theussl a écrit :
You are right, it's not currently used and I totally agree that it
should be. However, I am just now preparing a new release which I expect
to be ready next week (when MPCHANGELOG-81 is resolved), and I don't
w
I've had some more time to think about this. We called it an SCM URL, so
that would mean that it is a URL of some sort. Having had a look at
RFC2396 [2] section 3 "URI Syntactic Components", the syntax for a URI is:
:
URIs start with the scheme, which in our case is "scm", followed by a
col
Yes, an url must have this syntax that was supported until few days before your
patch (SCM-106).
I prefer too that scm url start with scm:, so we'll respect URI standard format.You can provide a
new patch for code and docs and i'll apply it.
Your previous patch wasn't in previoys release, so i
I'm fine with that too, as long as the documentation gets updated
accordingly.
Dennis, can you attach a new patch for MPCHANGELOG-81? I'd like to
release it this week.
Cheers,
-Lukas
Emmanuel Venisse wrote:
Yes, an url must have this syntax that was supported until few days
before your pat
[ http://jira.codehaus.org/browse/SCM-126?page=comments#action_56622 ]
Emmanuel Venisse commented on SCM-126:
--
change set isn't populated correctly (at least for svn provider).
For svn provider, file path is relative to working directory for update comma
Emmanuel Venisse wrote:
Yes, an url must have this syntax that was supported until few days
before your patch (SCM-106).
I prefer too that scm url start with scm:, so we'll respect URI standard
format.You can provide a new patch for code and docs and i'll apply it.
I'll put together a patch. S
One new patch, coming up...
--
Dennis Lundberg
Lukas Theussl wrote:
I'm fine with that too, as long as the documentation gets updated
accordingly.
Dennis, can you attach a new patch for MPCHANGELOG-81? I'd like to
release it this week.
Cheers,
-Lukas
Emmanuel Venisse wrote:
Yes, an url m
Allow compression option
Key: SCM-141
URL: http://jira.codehaus.org/browse/SCM-141
Project: Maven SCM
Type: New Feature
Components: maven-scm-provider-starteam
Reporter: Dan Tran
starteam stdcmd allows compression for slow link (
[ http://jira.codehaus.org/browse/SCM-141?page=all ]
Dan Tran closed SCM-141:
Assign To: Dan Tran
Resolution: Fixed
Fix Version: 1.0-beta-3
fixed
> Allow compression option
>
>
> Key: SCM-141
> URL: htt
22 matches
Mail list logo