Re: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9

[Emmanuel Venisse]

+2

Emmanuel

On Mon, Mar 23, 2009 at 11:55 PM, Olivier Lamy  wrote:

> Hi,
> I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
> This two release are in only one vote because they are very dependant
> due to a fix for people using subversion version > 1.5.0.
>
> Concerning maven-scm :
> We solved 36 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14522&styleName=Html&projectId=10527&Create=Create
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/maven-staging-52b28ae7ef880d/
>
> Staging site:
> http://maven.apache.org/scm-1.2 (wait sync)
>
> Concerning maven-release-plugin :
> We solved 12 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14682&styleName=Html&projectId=11144&Create=Create
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/maven-staging-52b241d05aa847/
>
> Staging site:
> http://maven.apache.org/plugins/maven-release-plugin-2.0-beta-9/ (wait
> sync)
>
> Vote open for 72 hours.
>
> Here my +1.
>
> Thanks,
> --
> Olivier
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: checkout source code from svn

[Emmanuel Venisse]

It is normal, you don't use the same protocol :-)

In the first case, you use the svn protocol and in the second case, you use
the file protocol.

Modify the scm url in your pom to something like that:

scm:svn:svn://my_svn_Ip/Development/execute-workflow

Emmanuel

On Tue, Sep 30, 2008 at 6:04 AM, mydesktop79 <
[EMAIL PROTECTED]> wrote:

>
> Hi,
> I'm newbie in Maven. I'd like to checkout svn source. When I tried bellow
> command line
>
> svn co svn://my_svn_Ip/Development/execute-workflow
>
> my source code checked out successful.
>
> But I fail when tried mvn scm:checkout. Bellow is my pom.xml file:
> 
>  ...
> 
>  
> 
> org.apache.maven.plugins
> maven-scm-plugin
> 1.1
>
> 
>  username
>  password
>  
>
> 
> 
> 
>
>
>
> scm:svn:file:///my_svn_Ip/Development/execute-workflow
>
>   HEAD
>
>  
>
>  
>
> 
>
> It said that:
> [ERROR] svn: Unable to open an ra_local session to URL
> svn: Unable to open repository
> 'file:///my_svn_Ip/Development/execute-workflow'
> svn: Can't open file '\my_svn_Ip/Development/execute-workflow\format': The
> filename, directory name, or volume label syntax is incorrect
>
> My svn url is pure ( don't use http or https url ). Could anybody help me?
>
>
> --
> View this message in context:
> http://www.nabble.com/checkout-source-code-from-svn-tp19735835p19735835.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
>

Re: Maven and SVN Plugin

[Emmanuel Venisse]

Look at the link I sent in my previous post, it's the solution.This plugin
generate a buildNumber property.
Then if you allow filtering on your resources files, ${buildNumber} will be
replaced by the property.

Emmanuel

On Thu, Sep 25, 2008 at 3:32 PM, dineshatit <[EMAIL PROTECTED]> wrote:

>
>
>
> Emmanuel Venisse-2 wrote:
> >
> > You want the svn revision, right?In this case, look at buildnumber
> plugin:
> > http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html
> >
> > Emmanuel
> >
> > On Thu, Sep 25, 2008 at 9:13 AM, dineshatit <[EMAIL PROTECTED]>
> wrote:
> >
> >>
> >> Dear Reader,
> >>   In maven, want to retrive the svn last commit value of
> >> repository in maven property (pom.xml) .
> >>  please suggest me
> >>
> >> what plugin ?
> >> HOWTO ?
> >>
> >>
> >> Dinesh Kumar .R
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Maven-and-SVN-Plugin-tp19664217p19664217.html
> >> Sent from the Maven - SCM mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> i want to get latest revision number of svn info svn://../repo/sdp/.
> result of the command , want to set in property file. plz give the solution
> ...
>
> --
> View this message in context:
> http://www.nabble.com/Maven-and-SVN-Plugin-tp19664217p19669594.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
>

Re: Maven and SVN Plugin

[Emmanuel Venisse]

You want the svn revision, right?In this case, look at buildnumber plugin:
http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html

Emmanuel

On Thu, Sep 25, 2008 at 9:13 AM, dineshatit <[EMAIL PROTECTED]> wrote:

>
> Dear Reader,
>   In maven, want to retrive the svn last commit value of
> repository in maven property (pom.xml) .
>  please suggest me
>
> what plugin ?
> HOWTO ?
>
>
> Dinesh Kumar .R
> --
> View this message in context:
> http://www.nabble.com/Maven-and-SVN-Plugin-tp19664217p19664217.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
>

Re: Importing into Eclipse

[Emmanuel Venisse]

Remove maven-scm-api/target/ directory manually and retry. You have probably
a lock on it.
Do you have added the classpath variable 'M2_REPO' in your workspace?
You can do it with the maven eclipse plugin :
http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html

Emmanuel

On Thu, Sep 18, 2008 at 12:44 PM, <[EMAIL PROTECTED]> wrote:

> So,
>
> i've done that. I get following Errors:
>
>
> DescriptionResourcePathLocationType
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommendedmaven-scm-client
> UnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-manager-plexusUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommendedmaven-scm-plugin
> UnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-accurevUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-bazaarUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-clearcaseUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-cvs-commonsUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-cvsexeUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-cvsjavaUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-cvstestUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-git-commonsUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-gitexeUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-gittestUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-hgUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-localUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-perforceUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-starteamUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-svn-commonsUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-svnexeUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-svntestUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-synergyUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommended
> maven-scm-provider-vssUnknownJava Problem
> The project cannot be built until its prerequisite maven-scm-api is built.
> Cleaning and building all projects is recommendedmaven-scm-test
> UnknownJava Problem
> The project was not built due to "Could not delete
> '/maven-scm-api/target/classes/org'.". Fix the problem, then try refreshing
> this project and building it since it may be inconsistent
> maven-scm-apiUnknownJava Problem
>
>
>
>

Re: Importing into Eclipse

[Emmanuel Venisse]

Yes.

On Thu, Sep 18, 2008 at 12:19 PM, <[EMAIL PROTECTED]> wrote:

> hello,
>
> that have to be done on root of the SCM Checkout location ?
> And later i can import the Project within Eclipse ?
>
> - Jens
>
>
>   mvn eclipse:eclipse should work to generate eclipse projects but you
> won't use m2 eclipse plugin.
> Emmanuel
>
> On Thu, Sep 18, 2008 at 12:07 PM, <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>>
>> im new therer and want to add DCM Based Support for Synergy.
>> Actually i try to us the m2 Eclipse plugin.
>> I imported all SCM Projects in my eclipse Workspace using the Plugin.
>> At all my CPU is busy for minutes and than my workspace still have
>> compiler error - i wonder because a cmd line mvn install works pretty well.
>>
>> Anyone can help me a bit with the setup/import in eclipse ?
>>
>> Best Regards,
>> Jens
>>
>
>

Re: Importing into Eclipse

[Emmanuel Venisse]

mvn eclipse:eclipse should work to generate eclipse projects but you won't
use m2 eclipse plugin.
Emmanuel

On Thu, Sep 18, 2008 at 12:07 PM, <[EMAIL PROTECTED]> wrote:

> Hello,
>
> im new therer and want to add DCM Based Support for Synergy.
> Actually i try to us the m2 Eclipse plugin.
> I imported all SCM Projects in my eclipse Workspace using the Plugin.
> At all my CPU is busy for minutes and than my workspace still have compiler
> error - i wonder because a cmd line mvn install works pretty well.
>
> Anyone can help me a bit with the setup/import in eclipse ?
>
> Best Regards,
> Jens
>

Re: Looking for a possibility to use "svn status -uv" command and capture the output into a text file

[Emmanuel Venisse]

Please add your patch to an issue instead of to attach it on an email.

Thanks
Emmanuel

On Fri, Aug 29, 2008 at 1:26 PM, Kiss Tibor <[EMAIL PROTECTED]> wrote:

> Here is a possible extension of the svn-settings.xml.
>
> Overview:
> Since SCM goals are generalisations of many version control provider's
> commands, that enforces some limitation in using any of the extra parameters
> of the underlaying command line tool. It would be ideal, that at the
> configuration level of all SCM specific Mojos to be able to set extra
> parameters to the underlaying version control command, but that somewhat
> distroys the generalisation itself. Instead, there are the provider specific
> ???-settings.xml files where there is nice to have such a possibility to set
> extra parameters for any goals we consider useful to have open this
> possibility.
>
> Example:
> In my case I really need to be able to set some additional parameters to
> svn status command. Such as "-uv > svnstatus.txt". In this way I am able to
> obtain much more information than it is returned by the SvnStatusConsumer.
> Moreover, I am able to prepare that intrinsic information right to be
> packaged into my assembly. Otherwise there is no possibility to extract such
> information from maven-scm plugin families.
>
> Proposal:
> 1. Add extra parameters to svn-settings.mdo, such as statusExtraParams,
> listExtraParams,.. with the following pattern: ExtraParams
> 2. All of these new svn-settings parameters to be added to the end of the
> corresponding SvnCommand.
>
> Has to be examined exactly which goals deserve to have such an extra
> parametrizing, without distroying the functionality of the associated
> consumer implementation. First, I think that those goals whose consumer
> output plays a role mainly in the maven output console, just printing some
> status information, or lists. Maybe there is worth to have such an extension
> possibility to a more active family of goals like add, branch, checkin,
> checkout. What do you think?
>
> THE PATCH (as a prototype only):
> I made and attached to this email a patch only to have statusExtraParams,
> only for status goal.
> I tested it with the following settings.xml
> 
>   -uv > svnstatus.txt
> 
> and I obtained the svnstatus.txt exactly as I would like to have on each
> maven project while building a subset of maven projects.
>
> I would like to have such a possibility to extend the provider's commands.
> That's why I raise the question to a discussion if it fit in scope of the
> maven-scm-provider-svn project?
> If seems to be acceptable, that let's discuss which other goals needs to
> extend to have a somewhat complete feature implemented. If so, I will help
> you by sending further patches. This patch mainly is only a prototype. I
> tested whithout junit testing.
>
> Regards,
> Tibor
>
>
>
> On Thu, Aug 28, 2008 at 12:08 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
>
>> You may want to take a look at svn provider source to see if it can be
>> extended to
>> accept additional arguments via svn-settings.xml for scm:status command
>>
>> see
>>
>> http://maven.apache.org/scm/subversion.html
>>
>> -D
>>
>> On Thu, Aug 28, 2008 at 2:57 AM, Kiss Tibor <[EMAIL PROTECTED]> wrote:
>> > Hi SCM team!
>> >
>> > I am involved in grounding a maven release management. So I have to keep
>> > some backward functionality.
>> >
>> > I have to generate a textfile containing exactly what provide the "svn
>> > status -uv" command.
>> >
>> > Looking at the SvnStatusCommand and SvnStatusConsumer implementation, it
>> > seems that actually is not possible without further modification. I am
>> > wrong?
>> >
>> > I would't like to migrate into a new maven plugin the Ant task based on
>> > SVNKit wich does that, instead I would like to use the SCM plugin
>> families.
>> >
>> > The entier maven-scm-providers-svn subset it would be affected by a
>> possible
>> > substitution, or is there a more elegant way to achieve my goals?
>> >
>> > At least some extra svn status parameters I would like to have, and of
>> > course a new consumer which would capture the output in a file, which
>> file
>> > would be moved into META-INF directory of the output. (Please don't ask
>> why
>> > is necessary this stupidity to capture that information in a META-INF
>> :-) )
>> >
>> > Regards,
>> > Tibor
>> >
>>
>
>

Re: [VOTE] Release Maven Scm 1.1 (take 3)

[Emmanuel Venisse]

+1

Emmanuel

On Sat, Aug 23, 2008 at 8:23 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:

> Hi,
> The last release of maven-scm is now 14 months old.
> I'd like to release maven-scm 1.1 which include two new providers git
> and accurev and fix some issues.
>
> We solved 41 issues :
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13984&styleName=Html&projectId=10527&Create=Create
>
> Staging repo: 
> http://people.apache.org/~olamy/staging-repo/.
>
> Staging site: http://maven.apache.org/scm-1.1/ .
>
> One more issue has been fixed since take 2 ([SCM-402] - scm:checkin
> doesn't work on OS X 10.5 Leopard)
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Here my +1.
>
> Thanks
> --
> Olivier
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE] Release Maven Scm 1.1 (take 2)

[Emmanuel Venisse]

It's ok.

Emmanuel

On Fri, Aug 22, 2008 at 11:48 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:

> Patch applied and snapshot deploy.
>
> Mac users are welcome to test :-)
>
> Just add the file svn-settings.xml (same as here [1] ) in ~/.scm/
>
> Thanks,
> --
> Olivier
>
> [1]
> https://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/resources/svn/checkin/macos/svn-settings.xml
>
> 2008/8/22 Emmanuel Venisse <[EMAIL PROTECTED]>:
> > I'll test it :)
> >
> > Emmanuel
> >
> > On Fri, Aug 22, 2008 at 11:10 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> >>
> >> Ok I will apply the patch (I hope a mac user will test the fix :-) ).
> >>
> >> And restart the release process .
> >>
> >> --
> >> Olivier
> >>
> >> 2008/8/22 Olivier Lamy <[EMAIL PROTECTED]>:
> >> > Hi Emmanuel,
> >> > Be sure about my spare time is not 100% sure :-)
> >> > Currently there are only 7 issues for 1.1.1 (some have patches).
> >> >
> >> > But it looks Mark has attached a patch to SCM-402 (I can certainly
> >> > apply it quickly and rebuild a release process tomorrow).
> >> >
> >> > WDYT ?
> >> >
> >> > --
> >> > Olivier
> >> >
> >> > 2008/8/22 Emmanuel Venisse <[EMAIL PROTECTED]>:
> >> >> Are you sure for the 1.1.1 date?
> >> >>
> >> >> Emmanuel
> >> >>
> >> >> On Fri, Aug 22, 2008 at 10:04 PM, Olivier Lamy <[EMAIL PROTECTED]>
> >> >> wrote:
> >> >>
> >> >>> Dan,
> >> >>> I have already planned/think about a 1.1.1 (with bug fixes) 4/5
> weeks
> >> >>> after the 1.1.
> >> >>> Can we wait this ??
> >> >>>
> >> >>> Thanks,
> >> >>> --
> >> >>> Olivier
> >> >>>
> >> >>>
> >> >>> 2008/8/22 Mark Struberg <[EMAIL PROTECTED]>:
> >> >>> > For what I understand, this is a pure Apple/subversion problem,
> and
> >> >>> > has
> >> >>> nothing to do with maven-scm.
> >> >>> >
> >> >>> > The only thing we could do is to introduce a new parameter in the
> >> >>> > maven-scm-provider-svn-commons/src/main/mdo/svn-settings.mdo
> >> >>> > 'useNonInteractive' which defaults to true.
> >> >>> >
> >> >>> > Use this information in
> >> >>> >
> >> >>> >
> org/apache/maven/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java
> >> >>> > to suppress the --non-interactive option.
> >> >>> >
> >> >>> > I'll attach the patch in SCM-402.
> >> >>> >
> >> >>> > LieGrü,
> >> >>> > strub
> >> >>> >
> >> >>> > --- Dan Fabulich <[EMAIL PROTECTED]> schrieb am Fr, 22.8.2008:
> >> >>> >
> >> >>> >> Von: Dan Fabulich <[EMAIL PROTECTED]>
> >> >>> >> Betreff: Re: [VOTE] Release Maven Scm 1.1 (take 2)
> >> >>> >> An: "Maven Developers List" <[EMAIL PROTECTED]>
> >> >>> >> CC: scm-dev@maven.apache.org
> >> >>> >> Datum: Freitag, 22. August 2008, 17:47
> >> >>> >> -0.
> >> >>> >>
> >> >>> >> SCM-402 scm:checkin doesn't work on OS X 10.5 Leopard
> >> >>> >> http://jira.codehaus.org/browse/SCM-402
> >> >>> >>
> >> >>> >> This breaks the release plugin on Leopard also.  I'd
> >> >>> >> mark it -1 if I
> >> >>> >> thought I had time to help fix it.
> >> >>> >>
> >> >>> >> -Dan
> >> >>> >>
> >> >>> >> Olivier Lamy wrote:
> >> >>> >>
> >> >>> >> > Hi,
> >> >>> >> > The last release of maven-scm is now 14 months old.
> >> >>> >> > I'd like to release maven-scm 1.1 which include
> >> >>> >> two new providers git
> >> >>> >> > and 

Re: [VOTE] Release Maven Scm 1.1 (take 2)

[Emmanuel Venisse]

I'll test it :)

Emmanuel

On Fri, Aug 22, 2008 at 11:10 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:

> Ok I will apply the patch (I hope a mac user will test the fix :-) ).
>
> And restart the release process .
>
> --
> Olivier
>
> 2008/8/22 Olivier Lamy <[EMAIL PROTECTED]>:
> > Hi Emmanuel,
> > Be sure about my spare time is not 100% sure :-)
> > Currently there are only 7 issues for 1.1.1 (some have patches).
> >
> > But it looks Mark has attached a patch to SCM-402 (I can certainly
> > apply it quickly and rebuild a release process tomorrow).
> >
> > WDYT ?
> >
> > --
> > Olivier
> >
> > 2008/8/22 Emmanuel Venisse <[EMAIL PROTECTED]>:
> >> Are you sure for the 1.1.1 date?
> >>
> >> Emmanuel
> >>
> >> On Fri, Aug 22, 2008 at 10:04 PM, Olivier Lamy <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> Dan,
> >>> I have already planned/think about a 1.1.1 (with bug fixes) 4/5 weeks
> >>> after the 1.1.
> >>> Can we wait this ??
> >>>
> >>> Thanks,
> >>> --
> >>> Olivier
> >>>
> >>>
> >>> 2008/8/22 Mark Struberg <[EMAIL PROTECTED]>:
> >>> > For what I understand, this is a pure Apple/subversion problem, and
> has
> >>> nothing to do with maven-scm.
> >>> >
> >>> > The only thing we could do is to introduce a new parameter in the
> >>> > maven-scm-provider-svn-commons/src/main/mdo/svn-settings.mdo
> >>> > 'useNonInteractive' which defaults to true.
> >>> >
> >>> > Use this information in
> >>> >
> org/apache/maven/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java
> >>> > to suppress the --non-interactive option.
> >>> >
> >>> > I'll attach the patch in SCM-402.
> >>> >
> >>> > LieGrü,
> >>> > strub
> >>> >
> >>> > --- Dan Fabulich <[EMAIL PROTECTED]> schrieb am Fr, 22.8.2008:
> >>> >
> >>> >> Von: Dan Fabulich <[EMAIL PROTECTED]>
> >>> >> Betreff: Re: [VOTE] Release Maven Scm 1.1 (take 2)
> >>> >> An: "Maven Developers List" <[EMAIL PROTECTED]>
> >>> >> CC: scm-dev@maven.apache.org
> >>> >> Datum: Freitag, 22. August 2008, 17:47
> >>> >> -0.
> >>> >>
> >>> >> SCM-402 scm:checkin doesn't work on OS X 10.5 Leopard
> >>> >> http://jira.codehaus.org/browse/SCM-402
> >>> >>
> >>> >> This breaks the release plugin on Leopard also.  I'd
> >>> >> mark it -1 if I
> >>> >> thought I had time to help fix it.
> >>> >>
> >>> >> -Dan
> >>> >>
> >>> >> Olivier Lamy wrote:
> >>> >>
> >>> >> > Hi,
> >>> >> > The last release of maven-scm is now 14 months old.
> >>> >> > I'd like to release maven-scm 1.1 which include
> >>> >> two new providers git
> >>> >> > and accurev and fix some issues.
> >>> >> >
> >>> >> > We solved 26 issues :
> >>> >> >
> >>> >>
> >>>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13984&styleName=Html&projectId=10527&Create=Create
> >>> >> >
> >>> >> > Staging repo:
> >>> >> http://people.apache.org/~olamy/staging-repo/<http://people.apache.org/%7Eolamy/staging-repo/>
> <http://people.apache.org/%7Eolamy/staging-repo/>.
> >>> >> >
> >>> >> > Staging site: http://maven.apache.org/scm-1.1/ .
> >>> >> >
> >>> >> > Vote open for 72 hours.
> >>> >> >
> >>> >> > [ ] +1
> >>> >> > [ ] +0
> >>> >> > [ ] -1
> >>> >> >
> >>> >> > Here my +1.
> >>> >> >
> >>> >> > Thanks
> >>> >> > --
> >>> >> > Olivier
> >>> >> >
> >>> >> >
> >>> >>
> -
> >>> >> > To unsubscribe, e-mail:
> >>> >> [EMAIL PROTECTED]
> >>> >> > For additional commands, e-mail:
> >>> >> [EMAIL PROTECTED]
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> >>> >>
> -
> >>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>> >
> >>> > __
> >>> > Do You Yahoo!?
> >>> > Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden
> Schutz
> >>> gegen Massenmails.
> >>> > http://mail.yahoo.com
> >>> >
> >>> > -
> >>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> > For additional commands, e-mail: [EMAIL PROTECTED]
> >>> >
> >>> >
> >>>
> >>> -
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>
> >
>

Re: mutable CVS User

[Emmanuel Venisse]

Personnally, when I used cvs, I prefered to used ext protocol with ssh
because the pserver isn't independant of the user.

If you can't migrate to ext protocol (just need a ssh access on the cvs
server), you don't have an other solution that the one you use. You can
report a bug on the release plugin to fix it (
http://jira.codehaus.org/browse/MRELEASE)

Emmanuel

On Fri, Jun 13, 2008 at 3:33 PM, fma-001 <[EMAIL PROTECTED]> wrote:

>
> Hi,
>
> I would like to have a mutable user of the cvs-connection, since the
> changes
> are done of different users. So I tried to do it like this:
> 
>scm:cvs:pserver:${CVS_USER}@
> 
>
> The ${CVS_USER} is a property in settings.xml. This works fine for the
> first
> time, but when doing mvn release:clean release:prepare maven substitutes
> the
> CVS_USER for the current user and checks the pom in like this:
> 
>scm:cvs:pserver:@
> 
>
> Is there another way to have the CVS user mutable?
>
> Thanks in advance,
> Franz
> --
> View this message in context:
> http://www.nabble.com/mutable-CVS-User-tp17823535p17823535.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
>

Re: EmForge 0.24 released

[Emmanuel Venisse]

Thanks for this feedback, it is really appreciated to see maven-scm can be
used outside the maven/continuum spheres.

Emmanuel

On Thu, Jun 12, 2008 at 11:16 AM, Alexey Kakunin <[EMAIL PROTECTED]> wrote:

> Dear maven-scm developers.
>
> We are happy to announce EmForge 0.24 - one of the major changes in this
> version - we switched to use maven-scm for implementing our repository
> browser (look project news for more details: http://www.emforge.org/news)
>
> Currently, remote commands we are using in for implementing browser is not
> n the core of maven-scm, so, we implemented them by our own and using our
> "extended" version of maven-scm. During next week I hope we will prepeare
> our changes to be able to send to maven-scm community for accept (we need to
> write integration unit-tests, check other commands, that should be local -
> to do not use remote interface and so on). Hope this changes will be
> included into maven-scm core and this functionality will become available to
> other maven-scm users.
>
>
> Maven-scm is really great library! Thank you.
>
>
>
> --
> With best regards,
> Alexey Kakunin

Re: Multiple CVS Modules + SCM

[Emmanuel Venisse]

[EMAIL PROTECTED] will be a better to post your question.

But quickly, you must have a multi-module maven project with one or more pom
by cvs module

Emmanuel

On Tue, Jun 3, 2008 at 5:23 PM, silvamayne <[EMAIL PROTECTED]> wrote:

>
> Hi to all
>
> Firstly I am new to maven so apologies if this question has been answered
> already (I am looking through the forums)
> I am attempting to configure a new project part of which requires me to
> checkout several modules from a CVS repository (to build one large jar) Is
> there a way to specify multiple cvs modules in the pom.xml? or is it a case
> of creating a multi-module maven project and create a pom for each checkout
> and have them all 'dump' to the same destination directory?
>
> Any pointers greatly appreciated
> --
> View this message in context:
> http://www.nabble.com/Multiple-CVS-Modules-%2B-SCM-tp17626189p17626189.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
>

Re: Extending API to support remote commands like rlist, rlog

[Emmanuel Venisse]

Great idea, I'm +1 for it, but some actual command use already remote
commands instead of local command, they need to be fixed during  the
implementation of this new features.

Emmanuel

On Mon, Jun 2, 2008 at 1:50 PM, Sergey Zakusov <[EMAIL PROTECTED]> wrote:

> Hello,
>
> We propose to extend the existing API to support some remote commands -
> it's a really required feature to allow work with SCMs without Working
> Copies.
>
> For a start there should be done the following commands:
>
>1. *rlist* - to list remotely repository entries;
>2. *rinfo* - to get information about repository entries;
>3. *rlog* - to get change log of repository entries;
>4. *rcat* - to get file contents remotely.
>
> Additional information see here: http://jira.codehaus.org/browse/SCM-381
>
>
>
> --
> Best regards,
> Sergey Zakusov
> --
> Software Developer, EmDev,
> Saint-Petersburg, Remeslennaya 17-415,
> 197110, Russia
>
> Phone: +7 (812) 498-72-21
> Mobile: +7 (921) 301-77-13

Re: 2READ: Should remote or "local" command be used to List, Changelog and etc. commands?

[Emmanuel Venisse]

If some commands use local and some others use remote, I think it's an
error. I'd prefer to have something consistent.

If local and remote are possible for some commands/providers, it would be
good to create both in each providers so applications that use maven-scm
will can choose the way they want.

Emmanuel

On Fri, May 30, 2008 at 5:38 PM, Sergey Zakusov <[EMAIL PROTECTED]> wrote:

> Sorry for my previous mail, it has been sent by chance :(
>
> So, my question is: which kind of command should be used for commands like
> List, Changelog and etc. - remote or local?
>
> For example, CVS returns different results for Log (local) and Rlog
> (remote) commands.
> REM: Rlog result cannot be parsed by CvsChangeLogConsumer.
>
> All SCM providers for CVS uses:
>
>- Rlist (remote) command (in any case the result cannot be parsed by
>CvsStatusConsumer: http://jira.codehaus.org/browse/SCM-380),
>- Log (local) command (but at the same time SCM providers for SVN uses
>Log command for remote items).
>
>
> In our case (for EmForge source browser) we would like to use remote
> commands where it's possible.
> How can it be done with Maven SCM?
> Should we create a new path for AbstractCvsChangeLogCommand?
> or can the Maven API be extended to add the remote commands too?
>
>
> --
> Best regards,
> Sergey Zakusov
> --
> Software Developer, EmDev,
> Saint-Petersburg, Remeslennaya 17-415,
> 197110, Russia
>
> Phone: +7 (812) 498-72-21
> Mobile: +7 (921) 301-77-13

Re: CvsExeScmProvider makes wrong arguments for List command (?)

[Emmanuel Venisse]

Can you create an issue and attach the patch? Thanks.

Emmanuel

On Thu, May 29, 2008 at 1:00 PM, Sergey Zakusov <[EMAIL PROTECTED]> wrote:

> The "Unknown file status" problem was in that
> AbstractCvsListCommand.executeListCommand executed rls command without -e
> option and the result was parsed by CvsStatusConsumer.consumeLine (who
> logged the problem). You can find the fix here:
> http://www.emforge.org/changeset/3240/maven-scm
>
>
> 2008/5/23, Sergey Zakusov <[EMAIL PROTECTED]>:
>
>> Hello,
>>
>> I'm trying to list a cvs repository via CvsExeScmProvider - it makes and
>> executes the following command:
>>
>> cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -n -q rls -d
>>
>> but the cvs client - Concurrent Versions System (CVSNT) 2.5.03 (Scorpio)
>> Build 2382 (client/server)
>> [Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn, Jeff Polk,
>> and other authors
>> CVSNT version (Jul  5 2006) Copyright (c) 1999-2005 Tony Hoyle and 
>> others]throws the error:
>>
>> rls: invalid option -- d
>> Usage: cvs rls [-q] [-e] [-l] [-R] [-r rev] [-D date] [-t] [modules...]
>> -D dateShow files from date.
>> -eDisplay in CVS/Entries format.
>> -lDisplay all details.
>> -PIgnore empty directories.
>> -qQuieter output.
>> -RList recursively.
>> -r revShow files with revision or tag.
>> -TShow time in local time instead of GMT.
>> (Specify the --help global option for a list of other help options)
>>
>> Another cvs client - Concurrent Versions System (CVS) 1.12.11.1 (client) 
>> [Copyright
>> (C) 2005 Free Software Foundation, Inc.]
>> processes the command without any error, but CvsExeScmProvider does not
>> return result anyway, I just see in the console:
>>
>> Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -n -q
>> rls -d
>> Working directory: C:\Documents and Settings\szakusov\Local Settings\Temp
>> Unknown file status: '3'.
>> Unknown file status: 'K'.
>> Unknown file status: 'a'.
>> Unknown file status: 'b'.
>> Unknown file status: 'b'.
>> Unknown file status: 'c'.
>> Unknown file status: 'c'.
>> Unknown file status: 'c'.
>> Unknown file status: 'c'.
>> Unknown file status: 'c'.
>> Unknown file status: 'c'.
>> Unknown file status: 'd'.
>> Unknown file status: 'd'.
>> Unknown file status: 'd'.
>> Unknown file status: 'd'.
>> Unknown file status: 'd'.
>> Unknown file status: 'e'.
>> Unknown file status: 'f'.
>> Unknown file status: 'g'.
>> Unable to parse output from command: line length must be bigger than 3.
>> (hg).
>> Unknown file status: 'j'.
>> Unknown file status: 'j'.
>> Unknown file status: 'j'.
>> Unknown file status: 'l'.
>> Unknown file status: 'l'.
>> Unknown file status: 'l'.
>> Unknown file status: 'm'.
>> Unknown file status: 'm'.
>> Unknown file status: 'm'.
>> Unable to parse output from command: line length must be bigger than 3.
>> (n4).
>> Unknown file status: 'n'.
>> Unknown file status: 'p'.
>> Unknown file status: 'p'.
>> Unknown file status: 'p'.
>> Unknown file status: 'p'.
>> Unknown file status: 'p'.
>> Unknown file status: 'p'.
>> Unknown file status: 'p'.
>> Unknown file status: 'p'.
>> Unknown file status: 'r'.
>> Unknown file status: 'r'.
>> Unknown file status: 'r'.
>> Unknown file status: 'r'.
>> Unknown file status: 'r'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 's'.
>> Unknown file status: 't'.
>> Unknown file status: 't'.
>> Unknown file status: 'u'.
>> Unknown file status: 'u'.
>> Unknown file status: 'w'.
>> Unknown file status: 'w'.
>>
>> Where is the problem? Does anybody have an example how to list a cvs
>> repository and which cvs client can be used?
>>
>>
>> --
>> Best regards,
>> Sergey Zakusov
>> --
>> Software Developer, EmDev,
>> Saint-Petersburg, Remeslennaya 17-415,
>> 197110, Russia
>>
>> Phone: +7 (812) 498-72-21
>> Mobile: +7 (921) 301-77-13
>>
>
>
>
> --
> Best regards,
> Sergey Zakusov
> --
> Software Developer, EmDev,
> Saint-Petersburg, Remeslennaya 17-415,
> 197110, Russia
>
> Phone: +7 (812) 498-72-21
> Mobile: +7 (921) 301-77-13
>

Re: CvsExeScmProvider makes wrong arguments for List command (?)

[Emmanuel Venisse]

I don't know. It is the problem with cvs. Lot of implementation exist and
with differents options :(

What is the output of this command: 'cvs --help-commands'

Emmanuel

On Fri, May 23, 2008 at 5:20 PM, Sergey Zakusov <[EMAIL PROTECTED]> wrote:

> Hm, I've downloaded version 1.12.13a from
> http://download.savannah.gnu.org/releases/cvs/binary/feature/x86-woe,
> but result is the same.. :(
>
>
> 2008/5/23, Emmanuel Venisse <[EMAIL PROTECTED]>:
>
>> I'm not sure but I think rls command is appeared in 1.12.12.1
>>
>> You can downlowd it from this site:
>> http://ximbiot.com/cvs/wiki/CVS--Concurrent%20Versions%20System%20v1.12.12.1:%20Guide%20to%20CVS%20commands#SEC161
>>
>> Emmanuel
>>
>> On Fri, May 23, 2008 at 2:45 PM, Sergey Zakusov <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Hello,
>>>
>>> I'm trying to list a cvs repository via CvsExeScmProvider - it makes and
>>> executes the following command:
>>>
>>> cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -n -q rls -d
>>>
>>> but the cvs client - Concurrent Versions System (CVSNT) 2.5.03 (Scorpio)
>>> Build 2382 (client/server)
>>> [Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn, Jeff Polk,
>>> and other authors
>>> CVSNT version (Jul  5 2006) Copyright (c) 1999-2005 Tony Hoyle and
>>> others] throws the error:
>>>
>>> rls: invalid option -- d
>>> Usage: cvs rls [-q] [-e] [-l] [-R] [-r rev] [-D date] [-t] [modules...]
>>> -D dateShow files from date.
>>> -eDisplay in CVS/Entries format.
>>> -lDisplay all details.
>>> -PIgnore empty directories.
>>> -qQuieter output.
>>> -RList recursively.
>>> -r revShow files with revision or tag.
>>> -TShow time in local time instead of GMT.
>>> (Specify the --help global option for a list of other help options)
>>>
>>> Another cvs client - Concurrent Versions System (CVS) 1.12.11.1 (client)
>>> [Copyright (C) 2005 Free Software Foundation, Inc.]
>>> processes the command without any error, but CvsExeScmProvider does not
>>> return result anyway, I just see in the console:
>>>
>>> Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -n -q
>>> rls -d
>>> Working directory: C:\Documents and Settings\szakusov\Local Settings\Temp
>>> Unknown file status: '3'.
>>> Unknown file status: 'K'.
>>> Unknown file status: 'a'.
>>> Unknown file status: 'b'.
>>> Unknown file status: 'b'.
>>> Unknown file status: 'c'.
>>> Unknown file status: 'c'.
>>> Unknown file status: 'c'.
>>> Unknown file status: 'c'.
>>> Unknown file status: 'c'.
>>> Unknown file status: 'c'.
>>> Unknown file status: 'd'.
>>> Unknown file status: 'd'.
>>> Unknown file status: 'd'.
>>> Unknown file status: 'd'.
>>> Unknown file status: 'd'.
>>> Unknown file status: 'e'.
>>> Unknown file status: 'f'.
>>> Unknown file status: 'g'.
>>> Unable to parse output from command: line length must be bigger than 3.
>>> (hg).
>>> Unknown file status: 'j'.
>>> Unknown file status: 'j'.
>>> Unknown file status: 'j'.
>>> Unknown file status: 'l'.
>>> Unknown file status: 'l'.
>>> Unknown file status: 'l'.
>>> Unknown file status: 'm'.
>>> Unknown file status: 'm'.
>>> Unknown file status: 'm'.
>>> Unable to parse output from command: line length must be bigger than 3.
>>> (n4).
>>> Unknown file status: 'n'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'p'.
>>> Unknown file status: 'r'.
>>> Unknown file status: 'r'.
>>> Unknown file status: 'r'.
>>> Unknown file status: 'r'.
>>> Unknown file status: 'r'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 's'.
>>> Unknown file status: 't'.
>>> Unknown file status: 't'.
>>> Unknown file status: 'u'.
>>> Unknown file status: 'u'.
>>> Unknown file status: 'w'.
>>> Unknown file status: 'w'.
>>>
>>> Where is the problem? Does anybody have an example how to list a cvs
>>> repository and which cvs client can be used?
>>>
>>>
>>> --
>>> Best regards,
>>> Sergey Zakusov
>>> --
>>> Software Developer, EmDev,
>>> Saint-Petersburg, Remeslennaya 17-415,
>>> 197110, Russia
>>>
>>> Phone: +7 (812) 498-72-21
>>> Mobile: +7 (921) 301-77-13
>>>
>>
>>
>
>
> --
> Best regards,
> Sergey Zakusov
> --
> Software Developer, EmDev,
> Saint-Petersburg, Remeslennaya 17-415,
> 197110, Russia
>
> Phone: +7 (812) 498-72-21
> Mobile: +7 (921) 301-77-13
>

Re: CvsExeScmProvider makes wrong arguments for List command (?)

[Emmanuel Venisse]

I'm not sure but I think rls command is appeared in 1.12.12.1

You can downlowd it from this site:
http://ximbiot.com/cvs/wiki/CVS--Concurrent%20Versions%20System%20v1.12.12.1:%20Guide%20to%20CVS%20commands#SEC161

Emmanuel

On Fri, May 23, 2008 at 2:45 PM, Sergey Zakusov <[EMAIL PROTECTED]> wrote:

> Hello,
>
> I'm trying to list a cvs repository via CvsExeScmProvider - it makes and
> executes the following command:
>
> cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -n -q rls -d
>
> but the cvs client - Concurrent Versions System (CVSNT) 2.5.03 (Scorpio)
> Build 2382 (client/server)
> [Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn, Jeff Polk, and
> other authors
> CVSNT version (Jul  5 2006) Copyright (c) 1999-2005 Tony Hoyle and 
> others]throws the error:
>
> rls: invalid option -- d
> Usage: cvs rls [-q] [-e] [-l] [-R] [-r rev] [-D date] [-t] [modules...]
> -D dateShow files from date.
> -eDisplay in CVS/Entries format.
> -lDisplay all details.
> -PIgnore empty directories.
> -qQuieter output.
> -RList recursively.
> -r revShow files with revision or tag.
> -TShow time in local time instead of GMT.
> (Specify the --help global option for a list of other help options)
>
> Another cvs client - Concurrent Versions System (CVS) 1.12.11.1 (client) 
> [Copyright
> (C) 2005 Free Software Foundation, Inc.]
> processes the command without any error, but CvsExeScmProvider does not
> return result anyway, I just see in the console:
>
> Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -n -q rls
> -d
> Working directory: C:\Documents and Settings\szakusov\Local Settings\Temp
> Unknown file status: '3'.
> Unknown file status: 'K'.
> Unknown file status: 'a'.
> Unknown file status: 'b'.
> Unknown file status: 'b'.
> Unknown file status: 'c'.
> Unknown file status: 'c'.
> Unknown file status: 'c'.
> Unknown file status: 'c'.
> Unknown file status: 'c'.
> Unknown file status: 'c'.
> Unknown file status: 'd'.
> Unknown file status: 'd'.
> Unknown file status: 'd'.
> Unknown file status: 'd'.
> Unknown file status: 'd'.
> Unknown file status: 'e'.
> Unknown file status: 'f'.
> Unknown file status: 'g'.
> Unable to parse output from command: line length must be bigger than 3.
> (hg).
> Unknown file status: 'j'.
> Unknown file status: 'j'.
> Unknown file status: 'j'.
> Unknown file status: 'l'.
> Unknown file status: 'l'.
> Unknown file status: 'l'.
> Unknown file status: 'm'.
> Unknown file status: 'm'.
> Unknown file status: 'm'.
> Unable to parse output from command: line length must be bigger than 3.
> (n4).
> Unknown file status: 'n'.
> Unknown file status: 'p'.
> Unknown file status: 'p'.
> Unknown file status: 'p'.
> Unknown file status: 'p'.
> Unknown file status: 'p'.
> Unknown file status: 'p'.
> Unknown file status: 'p'.
> Unknown file status: 'p'.
> Unknown file status: 'r'.
> Unknown file status: 'r'.
> Unknown file status: 'r'.
> Unknown file status: 'r'.
> Unknown file status: 'r'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 's'.
> Unknown file status: 't'.
> Unknown file status: 't'.
> Unknown file status: 'u'.
> Unknown file status: 'u'.
> Unknown file status: 'w'.
> Unknown file status: 'w'.
>
> Where is the problem? Does anybody have an example how to list a cvs
> repository and which cvs client can be used?
>
>
> --
> Best regards,
> Sergey Zakusov
> --
> Software Developer, EmDev,
> Saint-Petersburg, Remeslennaya 17-415,
> 197110, Russia
>
> Phone: +7 (812) 498-72-21
> Mobile: +7 (921) 301-77-13
>

Re: Trouble with CvsJavaScmProvider's list command

[Emmanuel Venisse]

Before to use by default the netbeans cvs client, it used the native cvs
client.

If you want to use the native cvs client, you need the following system
property:

-Dmaven.scm.provider.cvs.implementation=cvs_native

Emmanuel



On Mon, May 19, 2008 at 5:25 PM, Sergey Zakusov <[EMAIL PROTECTED]> wrote:

> Hello,
>
> I've found that AbstractCvsListCommand.executeListCommand uses RLS command
> to execute a list command (see
> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-cvs/maven-scm-provider-cvs-commons/src/main/java/org/apache/maven/scm/provider/cvslib/command/list/AbstractCvsListCommand.java?view=markup
> ),
> but CvsJavaScmProvider (maven-scm-provider-cvsjava) uses netbeans cvsclient
> which does not support RLS command
> (see
> http://hg.netbeans.org/main/file/8a8cbbb3d315/lib.cvsclient/src/org/netbeans/lib/cvsclient/commandLine/CommandFactory.java
> ).
>
> As result I have the error:
> Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvsroot -n -q rls
> -d
> Working directory: C:\temp
> [ERROR] Illegal argument: Unknown command: 'rls'
>
> Can anybody tell me how did it work before?
>
>
> --
> Best regards,
> Sergey Zakusov
> --
> Software Developer, EmDev,
> Saint-Petersburg, Remeslennaya 17-415,
> 197110, Russia
>
> Phone: +7 (812) 498-72-21
> Mobile: +7 (921) 301-77-13

Re: Many diff / status / update commands miss files with the deleted flag (patch check)

[Emmanuel Venisse]

You can commit it, I'll review it.
I'm not sure about bazaar.

Emmanuel

Andrew Williams a écrit :
(apologies, was not subscribed before - please disregard a dupe if it 
arrives)


I am sending this to the list before I try to commit (not certain I have 
privs tbh...) to make sure that folk are in agreement with this change:


Basically many commands (svn diff, status and up for a start) do not 
report files that have been deleted (reported so using the deleted flag) 
as the file no longer exists.
Surely fixing this has to be the right thing to do, as I want to know 
when my files have been deleted ;)


The only thing in this patch that I am not 100% sure of is in 
maven-scm-providers/maven-scm-provider-bazaar/src/main/java/org/apache/maven/scm/provider/bazaar/command/diff/BazaarDiffConsumer.java 

it will allow a file that is marked deleted to appear in the log even 
though (looking at the code) it might have a preceding '/' - does the 
Bazaar parser really not know whether or not to expect a preceding slash?!?


if I don't hear any grumbles I will try to commit this - it is a major 
annoyance for me...


Andy

Re: cvs tag -F (patch)

[Emmanuel Venisse]

Please, attach your patch to an issue and I'll look at it when I'll found some 
time.

Thanks.
Emmanuel

Benoit Decherf a écrit :

Hi,

As I told you in scm-users list (12/07), I need to disable the -F option 
in cvs tag.
I make a patch to add the option useForceTag. This works, but in case of 
a conflict with an existing flag, the cvs tag won't failed. (the tag is 
not set). Is this acceptable ?
Or maybe I should check for Warning messages in the output and the 
command should fail if there are any warnings ?


Benoit

Re: release:perform changes perforce clientspec

[Emmanuel Venisse]

File an issue.

Emmanuel

brewk9 a écrit :

Maven is changing my perforce client spec! It's changing the root to the
target\checkout directory of the project I'm building. This directory
doesn't even exist in perforce!

This is happening when I call the release:perform goal with system property
-Dmaven.scm.perforce.clientspec.name=brewke_all.

Re: problem with release plugin + perforce

[Emmanuel Venisse]

Hi,

Yes, I think it's a bug somewhere but I don't use Perforce so I can't help.
Maybe someone will can help you on the Maven users list because I don't think 
lot of Perforce users are on this list.

Emmanuel

brewk9 a écrit :

I am using -DgenerateReleasePoms=true. When I run release:prepare, maven
creates and adds the release-pom.xml to perforce. Then, when I run
release:perform, maven deletes release-pom.xml from perforce. Then, when I
run release:prepare for a subsequent release, maven fails to readd
release-pom.xml to perforce and gives this error 'Unknown input:
//pem_rd/portal/development/code/mainbea10/maven-jee-shared-lib-plugin/release-pom.xml
- can't add (already opened for edit)' which comes directly from perforce.

Is this a bug? Anyone else using perforce + generateReleasePoms=true
successfully?

Re: Custom SCM Provider - Works!

[Emmanuel Venisse]

checkout the maven-scm site 
(http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-site/), create a 
patch and attach it to a jira issue.

Emmanuel

[EMAIL PROTECTED] a écrit :


Thanks, those were the missing steps!

Question for the SCM group in general, how can I add this to the web 
site before it gets forgotten? I have a JIRA account, although I've 
never actually submitted any code or docs.



Robert Egan

"Genschaw, Shane" <[EMAIL PROTECTED]> wrote on 10/22/2007 11:54:32 AM:

 > Robert,
 >  
 > Try adding this to your POM:
 >  
 > 

 >   [...]
 >   
 > [...]
 > 
 >   org.apache.maven.plugins
 >   maven-scm-plugin
 >   1.0
 >   
 > 
 >   com.ph.buildtools.plugins
 >   scm-plugin
 >   7.4.0.0
 > 
 >   
 > 
 > [...]
 >   
 >   [...]
 > 
 >  
 > Also, you'll want to change your "packaging" to be "jar" instead of "

 > maven-plugin".  You are not actually creating a new plugin, you are
 > creating a new provider jar for the existing scm plugin to use.  A
 > related suggestion would be to change your artifact id to something 
like "

 > scm-provider-aci-custom".
 >  
 > I have created a custom provider for Serena PVCS/Changeman (my

 > company's SCM tool) and the "discovery" works just fine as long as
 > you add the dependency config for the scm plugin as shown above.  
 > You'll also have to similarly configure other plugins that rely on

 > your provider (maven-release-plugin, maven-changelog-plugin, etc.)
 > if you use them.
 >  
 > I didn't add "DefaultScmManager.setScmProvider( String providerType,

 > ScmProvider provider )" anywhere in the code.
 >  
 > - Shane Genschaw


This email message and any attachments may contain confidential, 
proprietary or non-public information.  The information is intended 
solely for the designated recipient(s).  If an addressing or 
transmission error has misdirected this email, please notify the sender 
immediately and destroy this email.  Any review, dissemination, use or 
reliance upon this information by unintended recipients is prohibited. 
 Any opinions expressed in this email are those of the author personally.

Re: Questions about Starteam provider

[Emmanuel Venisse]

[EMAIL PROTECTED] a écrit :


I've been looking at the maven documentation and the source code for the 
starteam provider and have some quick questions.


1) StarteamAddCommand, StarteamRemoveCommand do not have a corresponding 
scm goal listed on page http://maven.apache.org/scm/plugins/. Is this 
because they are undocumented, or that they are required by the 
framework for some kind of internal processing?


add goal is implemented and remove goal isn't. I don't know why add goal isn't 
on the site. I'll look at it.



2) StarteamEditCommand, StarteamUneditCommand are implemented although 
the Matrix says they are not 
(http://docs.codehaus.org/display/SCM/SCM+Matrix). Is the Matrix out of 
date, or is there some other reason for listing them as not implemented?


Fixed.



3) Does the provider or individual command implementations have 
to use a command line framework, or was that just done for ease of 
implementation? The reason I ask is that our build environment uses 
Starteam in a manner that exposes a design flaw in their checkout 
process (I can provide details if anyone asks, but it's not really 
relevant to the discussion).


We use starteam cli to run command because we can't redistribute starteam jars.

Emmanuel

Re: build failures on JDK 1.4

[Emmanuel Venisse]

huh, it must be 1.4 code

Brett Porter a écrit :

Hi,

Is SCM meant to support JDK 1.4? I notice the API is causing build 
failures on maven.zones.apache.org.


Cheers,
Brett

--
Brett Porter - [EMAIL PROTECTED] 
Blog: http://www.devzuz.org/blogs/bporter/

Re: Stuck with svn diff and multiple patches

[Emmanuel Venisse]

Allan Lang a écrit :

Hi

I'm trying to fix up the VSS provider and have already submitted a 
couple of patches, which haven't yet been incorporated into the SVN 
repository. My problem is that as I continue with the development work, 
I'm having trouble separating out the various pieces of work into 
separate patch files (I'm new to using svn diff).


Am I just making my life difficult trying to do things as separate 
patches? Should I be working on everything I want to fix, and then 
submitting one uber-patch?


As we don't have lot of contribution on this provider, if you prefer, you can 
do a big patch. Please add some explanations about it in the issue when you'll 
attach your patch.



At the moment I feel that getting my previous patches checked in would 
help me a lot to stop getting confused, but that seems like a slow process.


Actually, it is a slow process because I have lot of work to do on other 
projects and don't find time to review your patches. I'll do it asap.

Emmanuel



Any hints?

Thanks,
Allan

Re: Maven scm plugin unable to load maven scm local provider

[Emmanuel Venisse]

maybe I'll miss some of them but they are:

checkout, checkin, changelog, tag, status, update

Emmanuel

Allan Lang a écrit :

Hi Emmanuel

Out of interest, what are the required methods required for release 
plugin support?


Thanks,
Allan

On 12 Sep 2007, at 14:17, Emmanuel Venisse wrote:

The local scm provider isn't supported by the release plugin because 
some of required methods aren't implemented in this provider.


Instead of using the local provider, it would be better to implement 
an accurev provider, but it will require few hours.


Emmanuel

Terala, Satish (IS Consultant) a écrit :

Hi
I use accurev as my version control system. Since there is no scm 
plugin for accurev, I am planning to use ‘ local ‘ as my scm to do a 
prepare and perform a release. I just noticed that the maven scm 
providers does not even download the maven-scm-local provider even 
though the local provider has been defined as module in the  
tag of the providers pom.

In my pom file I specify the scm plugin as

 org.apache.maven.plugins
   maven-scm-plugin
   1.0-SNAPSHOT
 
  
connection

   
   
And then

scm:local|C:/rds_workspace|rds

scm:local|C:/rds_workspace|rds 



Here is the out put when I run mvn –X release:prepare. Basically all 
the scm providers are loaded at runtime except for local and hence at 
the point of running the prepare I get the error
*org.apache.maven.BuildFailureException: The provider given in the 
SCM URL could not be found: No such provider: 'local'.*
I have checked up the poms in my local repository for 
maven-scm-providers, and did a comparision between poms for the local 
provider and other providers that are actually getting loaded, I 
don’t see any glaring differences that might be a cause of the issue. 
I wonder if I am missing something or is there any other config 
setting that needs to be done ?

Thanks
-Satish
e)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime 
(removed - near

er found: 1.1)
[DEBUG] Retrieving parent-POM: org.apache.maven.scm:maven-scm::1.0 
for project:

null:maven-scm-api:jar:1.0 from the repository.
[DEBUG] org.apache.maven.scm:maven-scm-api:jar:1.0:runtime 
(selected for run

time)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-managers::1.0 for

project: null:maven-scm-manager-plexus:jar:1.0 from the repository.
[DEBUG] 
org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0:runtime (selec

ted for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers::1.0 for

 project: null:maven-scm-provider-bazaar:jar:1.0 from the repository.
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-bazaar:jar:1.0:runtime (sele

cted for runtime)
[DEBUG]   regexp:regexp:jar:1.3:runtime (selected for runtime)
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-clearcase:jar:1.0:runtime (s

elected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers-cvs::1.0
 for project: null:maven-scm-provider-cvsexe:jar:1.0 from the 
repository.
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-cvsexe:jar:1.0:runtime (sele

cted for runtime)
[DEBUG]   
org.apache.maven.scm:maven-scm-provider-cvs-commons:jar:1.0:runtim

e (selected for runtime)
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-cvsjava:jar:1.0:runtime (sel

ected for runtime)
[DEBUG]   org.netbeans.lib:cvsclient:jar:20060125:runtime 
(selected for runt

ime)
[DEBUG]   ch.ethz.ganymed:ganymed-ssh2:jar:build210:runtime 
(selected for ru

ntime)
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-hg:jar:1.0:runtime (selected

 for runtime)
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0:runtime (se

lected for runtime)
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-starteam:jar:1.0:runtime (se

lected for runtime)
[DEBUG] Retrieving parent-POM: 
org.apache.maven.scm:maven-scm-providers-svn::1.0
 for project: null:maven-scm-provider-svnexe:jar:1.0 from the 
repository.
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-svnexe:jar:1.0:runtime (sele

cted for runtime)
[DEBUG]   
org.apache.maven.scm:maven-scm-provider-svn-commons:jar:1.0:runtim

e (selected for runtime)
[DEBUG] 
org.apache.maven.scm:maven-scm-provider-synergy:jar:1.0:runtime (sel

ected for runtime)
[DEBUG] jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG] jaxen:jaxen:jar:1.1-beta-8:runtime (selected for runtime)
[DEBUG]   jaxen:jaxen:jar:1.0-FCS:runtime (removed - causes a 
cycle in the g

raph)
[DEBUG] Adding managed dependencies for 
org.apache.maven:maven-plugin-api

[DEBUG]   org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4
[DEBUG]   org.apache.maven.wagon:wagon-provider-a

Re: What if multiple scm commands ?

[Emmanuel Venisse]

yes, I think it will good to concate all, so users will knwo all commands that 
ran and will get all output

Emmanuel

Gilles Scokart a écrit :
I'm currently trying to write a provider for Dimensions.  Whit this 
tool, a checkout operation will result in multiple commands sent to the 
scm client (one per file).


How should I place the result in the CheckOutResult?

I thought to place only the commands & provider messages for the 
commands that have fail.  But if there is more than one failing, I will 
have to concate all commands and all messages into one string.


Is it the right thing to do?  I'm not sure of how this info is used.

Thanks,

--
Gilles SCOKART

Re: Query on enhancements to SCM VSS provider

[Emmanuel Venisse]

Yes, this project is always active but we don't have lot of modification on it 
because providers seems to work correctly for users in the majority of case.

I'll look at your patches.

Emmanuel

Allan Lang a écrit :

Hi

I've recently started working with the VSS SCM provider and have
found a number of issues. I'm currently working through these and
submitting patches via JIRA, however I'm not sure that this project
is currently active. Could anyone tell me if enhancements are still
being incorporated for SCM and VSS specifically?

I think getting the VSS provider working properly make help with
adoption of Maven / Continuum into the enterprise (which is certainly
what I'm trying to do).

Thanks,
Allan

Re: Maven SCM resolution problem when used with parent pom

[Emmanuel Venisse]

It's a problem with maven when you don't have modules in sub-directories. SCM 
URL are calculated and provided by maven to Maven-SCM.
I think the only solution you'll have will be to define your scm url in all 
your pom, or use the recommended directory structure.

Emmanuel

Nicky Sandhu a écrit :

Here's the problem
I have a parent pom defining the scm url


  
http://svn/repository

  
scm:svn:${svn-repository}/${artifactId}/trunk
${svn-repository}/${artifactId}
  

This works fine for the parent pom project
Output on debug >>
Configuring mojo 'org.apache.maven.plugins:maven-scm-plugin:1.0:validate'
-->
[DEBUG]   (f) basedir = c:\wk\raleys.maven\com.raleys.maven
[DEBUG]   (f) connectionType = connection
[DEBUG]   (s) connectionUrl =
scm:svn:http://svn/repository/com.raleys.maven/trunk
[DEBUG]   (f) scmConnection =
scm:svn:http://svn/repository/com.raleys.maven/trunk
[DEBUG]   (f) settings = [EMAIL PROTECTED]
<<

For the child project
There is no definition for scm and here is what i get
mvn -X scm:validate
Output 
(f) basedir = c:\wk\raleys.maven\com.raleys.utils
[DEBUG]   (f) connectionType = connection
[DEBUG]   (s) connectionUrl =
scm:svn:http://svn/repository/com.raleys.utils/trunk/com.raleys.utils
[DEBUG]   (f) developerConnectionUrl =
scm:svn:http://svn/repository/com.raleys.utils/trunk/com.raleys.utils
[DEBUG]   (f) settings = [EMAIL PROTECTED]
<<<

However if I put the definition cut and paste from the parent pom into the
child pom
  
scm:svn:${svn-repository}/${artifactId}/trunk
${svn-repository}/${artifactId}
  

mvn -X scm:validate gives this output
[DEBUG]   (f) basedir = c:\wk\raleys.maven\com.raleys.utils
[DEBUG]   (f) connectionType = connection
[DEBUG]   (s) connectionUrl =
scm:svn:http://svn/repository/com.raleys.utils/trunk
[DEBUG]   (f) scmConnection =
scm:svn:http://svn/repository/com.raleys.utils/trunk
[DEBUG]   (f) settings = [EMAIL PROTECTED]
<<<



Is this a bug or am I missing something

Re: [vote] Release Maven-SCM 1.0 final

[Emmanuel Venisse]

4 +1 binding votes (Jason Van Zyl, John Casey, Mike Perham, Emmanuel Venisse)
1 +1 non-binding vote (Ryan Daum)

I'm releasing it now.

Emmanuel

Emmanuel Venisse a écrit :

Hi,

I'd like to release Maven-SCM-1.0 that contains few bug fixes found in rc1.

The road map: 
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&styleName=Html&version=13380 



Staging repo: http://people.apache.org/~evenisse/stage/maven-scm-repo/

Tag: http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.0/

So, let's try 72h +1/+0/-1. Please cast your votes!

Here my +1

Emmanuel

Re: [vote] Release Maven-SCM 1.0 final

[Emmanuel Venisse]

I'm restarting the release process to integrate SCM-319

For those of you that have already tested the release, it won't change the result becuase the patch added is only for the Mercurial (hg) provider with tag command, so it will be supported by the 
release plugin too.


Emmanuel

Emmanuel Venisse a écrit :

Hi,

I'd like to release Maven-SCM-1.0 that contains few bug fixes found in rc1.

The road map: 
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&styleName=Html&version=13380 



Staging repo: http://people.apache.org/~evenisse/stage/maven-scm-repo/

Tag: http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.0/

So, let's try 72h +1/+0/-1. Please cast your votes!

Here my +1

Emmanuel

Re: mercurial provider patch

[Emmanuel Venisse]

You can't get the files list by parsing the tag command output only?

Ryan Daum a écrit :
No, it's not possible to do this -- and in any case the list of tagged 
files would be the entire repository; not sure it makes sense that the 
Tck test should require that a provider return a list like this in this 
case.  I'm very skeptical of making the provider's tag command perform 
an additional operation to list all the files in the repository given 
that it already is doing two operations: tag and push.


Given the set of tests in the tck test, I'm not sure how meaningful this 
test is.  I'm of the mind to say: just remove the test from the test 
suite.  I have manually tested the functionality and know that it works, 
and I think this feature is pretty critical for a 1.0 release which 
includes the Mercurial provider.


Your call,
Ryan

On 5/22/07, *Emmanuel Venisse* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


It doesn't tag arbitrary files but it test the TagScmResult that
must contains the list of tagged files. I'm sure you can know with
the hg tag command the list of tagged files by parsing the output.

Emmanuel

Ryan Daum a écrit :
 > What is the expected behaviour for this test given that many SCM
 > providers (hg being one) do not provide such a facility to tag
arbitrary
 > files? Many SCMs only support laying a tag against the current
revision
 > of the entire repository.  The parent tck test seems to require the
 > ability to tag specific files only.
 >
 > Ryan
 >
 > On 5/22/07, *Ryan Daum* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
 > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
 >
 > So if the latest commit is the release correction... what you're
 > saying is unless you branched (did you?  where can I check
out the
 > branch), there's no way at all that my changes can make it in
before
 > the release.
 >
 > Ryan
 >
 >
 > On 5/22/07, *Emmanuel Venisse* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
 > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>
wrote:
 >
 >
 >
 > Ryan Daum a écrit :
 > >  Firstly, it does not build at all after update given the
 > commits you
 > >  checked in earlier today, because it complains about
missing
 > >  org.apache.maven.scm:maven-scm-api:jar:1.0 , so I can't
 > actually run
 > >  through the tck profile you mention; can you provide me
 > instructions on
 > >  how to get the latest checkout to build?
 >
 > My latest commit is the release creation, so it will be
build
 > when the 1.0 will be validated and deployed to the
central repo.
 > You can use the staging repo to get 1.0 artifacts (
 > http://people.apache.org/~evenisse/stage/maven-scm-repo/
 > <http://people.apache.org/%7Eevenisse/stage/maven-scm-repo/>)
 >
 > >
 > >  What specifically fails on the tck?  Please provide
surefire
 > results, as
 > >  I cannot replicate your failure given the test I added.
 >
 > the TagScmResult doesn't contains tagged files list:
 >
 >
---

 > Test set:
 >
org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest
 >
---

 >
 > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
elapsed:
 > 2 sec <<< FAILURE!
 >
testTagCommandTest(org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest)  Time

 > elapsed: 1.985 sec  <<< ERROR!
 > java.lang.NullPointerException
 > at
 >
org.apache.maven.scm.tck.command.tag.TagCommandTckTest.testTagCommandTest(TagCommandTckTest.java:53)

 > at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
 > Method)
 > at
 >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

 > at
 >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java

:25)
 > at java.lang.reflect.Method.invoke (Method.java:585

Re: Re: Re: mercurial provider patch

[Emmanuel Venisse]

Ryan Daum a écrit :
I have a local version here which now passes all Tck tests by doing the 
inventory of the repository after the tag. 

Emmanuel, I can provide you with a patch, but can you give me advice on 
how to get Subversion to produce a diff file (from svn diff) that will 
do the right thing with creating new files?  All the output I get from 
svn diff seems to do the same as the patch I provided to you yesterday.


It's probably because you do a svn copy instead of create a new file from 
scratch.
If you can't create a clean patch, attach it to jira with the new file attached 
too and I'll work around.

Emmanuel



Ryan

On 5/22/07, *Ryan Daum* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


Just want to point out one more thing, and that is that the class
TagScmResult has two constructors, one of which accepts the list of
tagged files and the other which does not, leaving that list null. 
If the intention is that all SCM providers provide this list, then

the other constructor should not exist.  Alternatively, if this is
not the intention, then the Tck test should not require that this
list be populated.

Ryan


On 5/22/07, *Ryan Daum* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:

No, it's not possible to do this -- and in any case the list of
tagged files would be the entire repository; not sure it makes
sense that the Tck test should require that a provider return a
list like this in this case.  I'm very skeptical of making the
provider's tag command perform an additional operation to list
all the files in the repository given that it already is doing
two operations: tag and push.

Given the set of tests in the tck test, I'm not sure how
meaningful this test is.  I'm of the mind to say: just remove
the test from the test suite.  I have manually tested the
functionality and know that it works, and I think this feature
is pretty critical for a 1.0 release which includes the
Mercurial provider.

    Your call,
Ryan


On 5/22/07, * Emmanuel Venisse* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:

It doesn't tag arbitrary files but it test the TagScmResult
that must contains the list of tagged files. I'm sure you
can know with the hg tag command the list of tagged files by
parsing the output.

Emmanuel

Ryan Daum a écrit :
>  What is the expected behaviour for this test given that
many SCM
>  providers (hg being one) do not provide such a facility to
tag arbitrary
>  files? Many SCMs only support laying a tag against the
current revision
>  of the entire repository.  The parent tck test seems to
require the
>  ability to tag specific files only.
>
>  Ryan
>
>  On 5/22/07, *Ryan Daum* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
>  <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>
wrote:
>
> So if the latest commit is the release correction...
what you're
> saying is unless you branched (did you?  where can I
check out the
> branch), there's no way at all that my changes can make
    it in before
> the release.
>
> Ryan
>
>
> On 5/22/07, *Emmanuel Venisse* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>> wrote:
>
>
>
> Ryan Daum a écrit :
> >  Firstly, it does not build at all after update
given the
> commits you
> >  checked in earlier today, because it complains
about missing
> >  org.apache.maven.scm:maven-scm-api:jar:1.0 , so
I can't
> actually run
> >  through the tck profile you mention; can you
provide me
> instructions on
> >  how to get the latest checkout to build?
>
> My latest commit is the release creation, so it
will be build
> when the 1.0 will be validated and deployed to the
central repo.
> You can use the staging repo to get

Re: Re: Re: mercurial provider patch

[Emmanuel Venisse]

If I remember it correctly, the constructor without the files list is to add 
scm errors with providers messages...
Maybe we must add more javadoc on this class or deprecate this constructor, but 
a result in success must have the list of tagged files.

Emmanuel

Ryan Daum a écrit :
Just want to point out one more thing, and that is that the class 
TagScmResult has two constructors, one of which accepts the list of 
tagged files and the other which does not, leaving that list null.  If 
the intention is that all SCM providers provide this list, then the 
other constructor should not exist.  Alternatively, if this is not the 
intention, then the Tck test should not require that this list be 
populated.


Ryan

On 5/22/07, *Ryan Daum* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


No, it's not possible to do this -- and in any case the list of
tagged files would be the entire repository; not sure it makes sense
that the Tck test should require that a provider return a list like
this in this case.  I'm very skeptical of making the provider's tag
command perform an additional operation to list all the files in the
repository given that it already is doing two operations: tag and push.

Given the set of tests in the tck test, I'm not sure how meaningful
this test is.  I'm of the mind to say: just remove the test from the
test suite.  I have manually tested the functionality and know that
it works, and I think this feature is pretty critical for a 1.0
release which includes the Mercurial provider.

Your call,
    Ryan


On 5/22/07, * Emmanuel Venisse* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:

It doesn't tag arbitrary files but it test the TagScmResult that
must contains the list of tagged files. I'm sure you can know
with the hg tag command the list of tagged files by parsing the
output.

Emmanuel

Ryan Daum a écrit :
>  What is the expected behaviour for this test given that many SCM
>  providers (hg being one) do not provide such a facility to tag
arbitrary
>  files? Many SCMs only support laying a tag against the current
revision
>  of the entire repository.  The parent tck test seems to
require the
>  ability to tag specific files only.
>
>  Ryan
>
>  On 5/22/07, *Ryan Daum* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
>  <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>
> So if the latest commit is the release correction... what
you're
> saying is unless you branched (did you?  where can I check
out the
> branch), there's no way at all that my changes can make it
    in before
> the release.
>
> Ryan
>
>
> On 5/22/07, *Emmanuel Venisse* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>> wrote:
>
>
>
> Ryan Daum a écrit :
> >  Firstly, it does not build at all after update given
the
> commits you
> >  checked in earlier today, because it complains about
missing
> >  org.apache.maven.scm:maven-scm-api:jar:1.0 , so I can't
> actually run
> >  through the tck profile you mention; can you provide me
> instructions on
> >  how to get the latest checkout to build?
>
> My latest commit is the release creation, so it will be
build
> when the 1.0 will be validated and deployed to the
central repo.
> You can use the staging repo to get 1.0 artifacts (
>
http://people.apache.org/~evenisse/stage/maven-scm-repo/

<http://people.apache.org/%7Eevenisse/stage/maven-scm-repo/>
> <
http://people.apache.org/%7Eevenisse/stage/maven-scm-repo/>)
>
> >
> >  What specifically fails on the tck?  Please provide
surefire
> results, as
> >  I cannot replicate your failure given the test I added.
>
> the TagScmResult doesn't contains tagged files list:
>
>
---

> Test set:
>
org.apache.maven.scm.provider.hg.command

Re: Re: mercurial provider patch

[Emmanuel Venisse]

It doesn't tag arbitrary files but it test the TagScmResult that must contains 
the list of tagged files. I'm sure you can know with the hg tag command the 
list of tagged files by parsing the output.

Emmanuel

Ryan Daum a écrit :
What is the expected behaviour for this test given that many SCM 
providers (hg being one) do not provide such a facility to tag arbitrary 
files? Many SCMs only support laying a tag against the current revision 
of the entire repository.  The parent tck test seems to require the 
ability to tag specific files only.


Ryan

On 5/22/07, *Ryan Daum* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


So if the latest commit is the release correction... what you're
saying is unless you branched (did you?  where can I check out the
branch), there's no way at all that my changes can make it in before
the release.

Ryan


    On 5/22/07, *Emmanuel Venisse* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:



Ryan Daum a écrit :
>  Firstly, it does not build at all after update given the
commits you
>  checked in earlier today, because it complains about missing
>  org.apache.maven.scm:maven-scm-api:jar:1.0 , so I can't
actually run
>  through the tck profile you mention; can you provide me
instructions on
>  how to get the latest checkout to build?

My latest commit is the release creation, so it will be build
when the 1.0 will be validated and deployed to the central repo.
You can use the staging repo to get 1.0 artifacts (
http://people.apache.org/~evenisse/stage/maven-scm-repo/
<http://people.apache.org/%7Eevenisse/stage/maven-scm-repo/>)

>
>  What specifically fails on the tck?  Please provide surefire
results, as
>  I cannot replicate your failure given the test I added.

the TagScmResult doesn't contains tagged files list:


---
Test set:
org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest

---

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
2 sec <<< FAILURE!

testTagCommandTest(org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest)
  Time
elapsed: 1.985 sec  <<< ERROR!
java.lang.NullPointerException
at

org.apache.maven.scm.tck.command.tag.TagCommandTckTest.testTagCommandTest(TagCommandTckTest.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke (Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at
junit.framework.TestResult$1.protect(TestResult.java:106)
at
junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest (TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:39)
at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute
(JUnitTestSet.java:213)
at

org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute
(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.

Re: mercurial provider patch

[Emmanuel Venisse]

You can checkout the 1.0 tag 
(http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.0/) or the revision 
before the release creation

Emmanuel

Ryan Daum a écrit :
So if the latest commit is the release correction... what you're saying 
is unless you branched (did you?  where can I check out the branch), 
there's no way at all that my changes can make it in before the release.


Ryan

On 5/22/07, *Emmanuel Venisse* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:




Ryan Daum a écrit :
 > Firstly, it does not build at all after update given the commits you
 > checked in earlier today, because it complains about missing
 > org.apache.maven.scm:maven-scm-api:jar:1.0 , so I can't actually run
 > through the tck profile you mention; can you provide me
instructions on
 > how to get the latest checkout to build?

My latest commit is the release creation, so it will be build when
the 1.0 will be validated and deployed to the central repo.
You can use the staging repo to get 1.0 artifacts
(http://people.apache.org/~evenisse/stage/maven-scm-repo/
<http://people.apache.org/~evenisse/stage/maven-scm-repo/>)

 >
 > What specifically fails on the tck?  Please provide surefire
results, as
 > I cannot replicate your failure given the test I added.

the TagScmResult doesn't contains tagged files list:


---
Test set:
org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest

---

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2
sec <<< FAILURE!

testTagCommandTest(org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest)
  Time
elapsed: 1.985 sec  <<< ERROR!
java.lang.NullPointerException
at

org.apache.maven.scm.tck.command.tag.TagCommandTckTest.testTagCommandTest(TagCommandTckTest.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke (Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest (TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:39)
at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute
(JUnitTestSet.java:213)
at

org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute
(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess
(SurefireBooter.java:290)
at

org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
at

org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)


 >
 > Secondly, the patch is output from svn diff, I don't see from the
first
 > lines how it is invalid.

Index:

maven-scm-providers/maven-scm-provider-hg/src/test/java/org/apache/maven/scm/provider/hg/command/tag/HgTagCommandTckTest.java

===
---
maven-scm-providers/maven-scm-provider-hg/src/test/java/org/apache/maven/scm/provider/hg/command/tag/HgTagCommandTckTest.java  
(revision 0)

+++
maven-scm-providers/maven-scm-p

Re: mercurial provider patch

[Emmanuel Venisse]

Ryan Daum a écrit :
Firstly, it does not build at all after update given the commits you 
checked in earlier today, because it complains about missing 
org.apache.maven.scm:maven-scm-api:jar:1.0, so I can't actually run 
through the tck profile you mention; can you provide me instructions on 
how to get the latest checkout to build?


My latest commit is the release creation, so it will be build when the 1.0 will 
be validated and deployed to the central repo.
You can use the staging repo to get 1.0 artifacts 
(http://people.apache.org/~evenisse/stage/maven-scm-repo/)



What specifically fails on the tck?  Please provide surefire results, as 
I cannot replicate your failure given the test I added.


the TagScmResult doesn't contains tagged files list:

---
Test set: org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2 sec <<< 
FAILURE!
testTagCommandTest(org.apache.maven.scm.provider.hg.command.tag.HgTagCommandTckTest)  
Time elapsed: 1.985 sec  <<< ERROR!
java.lang.NullPointerException
at 
org.apache.maven.scm.tck.command.tag.TagCommandTckTest.testTagCommandTest(TagCommandTckTest.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)




Secondly, the patch is output from svn diff, I don't see from the first 
lines how it is invalid.


Index: 
maven-scm-providers/maven-scm-provider-hg/src/test/java/org/apache/maven/scm/provider/hg/command/tag/HgTagCommandTckTest.java
===
--- 
maven-scm-providers/maven-scm-provider-hg/src/test/java/org/apache/maven/scm/provider/hg/command/tag/HgTagCommandTckTest.java
   (revision 0)
+++ 
maven-scm-providers/maven-scm-provider-hg/src/test/java/org/apache/maven/scm/provider/hg/command/tag/HgTagCommandTckTest.java
   (working copy)
@@ -1,4 +1,4 @@
-package org.apache.maven.scm.provider.cvslib.command.tag;
+package org.apache.maven.scm.provider.hg.command.tag;

 /*
  * Licensed to the Apache Software Foundation (ASF) under one
@@ -19,31 +19,27 @@
  * under the License.
  */

-import org.apache.maven.scm.provider.cvslib.CvsScmTestUtils;
+import org.apache.maven.scm.provider.hg.HgRepoUtils;

...

It isn't a patch for a file creation.

Emmanuel


Ryan

On 5/22/07, *Emmanuel Venisse* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


I can't apply because your patch fail on the tck.

You can verify it by running 'mvn clean package -Ptck' on the hg
provider

For your next patch, generate a valid one, the one in SCM-319 wasn't
correct (look at first lines)

I'm sending the vote for the release of the 1

[vote] Release Maven-SCM 1.0 final

[Emmanuel Venisse]

Hi,

I'd like to release Maven-SCM-1.0 that contains few bug fixes found in rc1.

The road map: 
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&styleName=Html&version=13380

Staging repo: http://people.apache.org/~evenisse/stage/maven-scm-repo/

Tag: http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.0/

So, let's try 72h +1/+0/-1. Please cast your votes!

Here my +1

Emmanuel

Re: mercurial provider patch

[Emmanuel Venisse]

I can't apply because your patch fail on the tck.

You can verify it by running 'mvn clean package -Ptck' on the hg provider

For your next patch, generate a valid one, the one in SCM-319 wasn't correct 
(look at first lines)

I'm sending the vote for the release of the 1.0, if I don't have your patch 
tomorrow, it will be include in the next version.

Emmanuel

Ryan Daum a écrit :
During further use/testing of the mercurial provider 
(maven-scm-provider-hg) I discovered that the "tag" command was 
missing.  I've just fixed this.


Please see the patch attached to http://jira.codehaus.org/browse/SCM-319

Thank you,
  Ryan Daum

--
Ryan Daum
[EMAIL PROTECTED] 
Senior Developer, Toronto
647.724.5232 x 2073

Re: svn commit: r533717 - /maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/

[Emmanuel Venisse]

Jason van Zyl a écrit :


On 30 Apr 07, at 8:12 AM 30 Apr 07, [EMAIL PROTECTED] wrote:


Author: evenisse
Date: Mon Apr 30 05:12:41 2007
New Revision: 533717

URL: http://svn.apache.org/viewvc?view=rev&rev=533717
Log:
[SCM-303] Allow to define system properties in plugin configuration



Why not simple execution properties? System properties are terrible for 
embedding. I would suggest doing the exact same thing we are doing in 
2.1 where System Properties are banned and you pass in a Properties 
object in the request. This way it's thread safe.


I'm agree, but this system property is used actually by the scm manager. I must 
change it before 1.0 final.

Emmanuel


Jason.


Modified:

maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AbstractScmMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AddMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BranchMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/ChangeLogMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/CheckinMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/CheckoutMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/DiffMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/EditMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/ExportMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/ListMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/StatusMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/TagMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/UnEditMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/UpdateMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/UpdateSubprojectsMojo.java 


maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/ValidateMojo.java 



Modified: 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AbstractScmMojo.java 

URL: 
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AbstractScmMojo.java?view=diff&rev=533717&r1=533716&r2=533717 

== 

--- 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AbstractScmMojo.java 
(original)
+++ 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AbstractScmMojo.java 
Mon Apr 30 05:12:41 2007

@@ -41,6 +41,7 @@
 import java.io.File;
 import java.io.IOException;
 import java.util.Iterator;
+import java.util.Properties;

 /**
  * @author Emmanuel Venisse
@@ -149,6 +150,33 @@
  * @readonly
  */
 private Settings settings;
+
+/**
+ * List of System properties to pass to the JUnit tests.
+ *
+ * @parameter
+ */
+private Properties systemProperties;
+
+
+public void execute()
+throws MojoExecutionException
+{
+if ( systemProperties != null )
+{
+// Add all system properties configured by the user
+Iterator iter = systemProperties.keySet().iterator();
+
+while ( iter.hasNext() )
+{
+String key = (String) iter.next();
+
+String value = systemProperties.getProperty( key );
+
+System.setProperty( key, value );
+}
+}
+}

 protected void setConnectionType( String connectionType )
 {

Modified: 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AddMojo.java 

URL: 
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AddMojo.java?view=diff&rev=533717&r1=533716&r2=533717 

== 

--- 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AddMojo.java 
(original)
+++ 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/AddMojo.java 
Mon Apr 30 05:12:41 2007

@@ -38,6 +38,8 @@
 public void execute()
 throws MojoExecutionException
 {
+super.execute();
+
 try
 {
 ScmRepository repository = getScmRepository();

Modified: 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java 

URL: 
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/s

[VOTE] Release Maven-SCM 1.0-rc1

[Emmanuel Venisse]

Hi,

I'd like to release Maven SCM 1.0-rc1
This version fix few bugs, add a new provider (mercurial) and few commands.

Road Map:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&styleName=Html&version=13066

Site:
http://people.apache.org/~evenisse/stage/site/

Staging repo:
http://people.apache.org/~evenisse/stage/repo/

Tag:
http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.0-rc1/

So, let's try 72h +1/+0/-1. Please cast your votes!

Here my +1

Emmanuel

Re: maven-scm-test compilation failure

[Emmanuel Venisse]

Fixed.

Emmanuel

Antoine Véret a écrit :

with revision: 527139

thanks

Re: Commit privileges for maven-scm?

[Emmanuel Venisse]

If it is ok, I'll apply it next week.

Emmanuel

Ryan Daum a écrit :
Last time I attached patches to Jira they were ignored for 3 months 
until bugged someone on #maven.


Ryan

On 4/7/07, *Emmanuel Venisse* < [EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


It isn't possible to give you commits privilege now, it's a
meritocracy at ASF.

Can you attach your patches to jira.

Thanks,
Emmanuel

Ryan Daum a écrit :
 > I've just finished updating maven-scm-provider-hg to work with the
 > newest rev of the API.  I also properly fixed SCM-244, as the
amount of
 > time for the sleep in the patch I originally submitted was not
 > sufficient.  I'd like to commit my work to the trunk, if possible.
 >
 > Ryan
 >
 > --
 > Ryan Daum
 > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
 > Senior Developer, Toronto
 > 647.724.5232 x 2073




--
Ryan Daum
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Senior Developer, Toronto
647.724.5232 x 2073

Re: Commit privileges for maven-scm?

[Emmanuel Venisse]

It isn't possible to give you commits privilege now, it's a meritocracy at ASF.

Can you attach your patches to jira.

Thanks,
Emmanuel

Ryan Daum a écrit :
I've just finished updating maven-scm-provider-hg to work with the 
newest rev of the API.  I also properly fixed SCM-244, as the amount of 
time for the sleep in the patch I originally submitted was not 
sufficient.  I'd like to commit my work to the trunk, if possible.


Ryan

--
Ryan Daum
[EMAIL PROTECTED] 
Senior Developer, Toronto
647.724.5232 x 2073

Re: Other scms...

[Emmanuel Venisse]

et tested of course ;)

Emmanuel

Emmanuel Venisse a écrit :

They need to be updated with latest code of maven-scm-api.

Emmanuel

Ryan Daum a écrit :

What is the procedure for graduating from sandbox?

Ryan

On 4/4/07, *Mike Perham* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


Ah, right.  http://svn.apache.org/viewvc/maven/sandbox/trunk/scm/
<http://svn.apache.org/viewvc/maven/sandbox/trunk/scm/>

But until it graduates from the sandbox, it's not integrated into the
release plugin, etc and so isn't terribly useful to the community at
large.  That's what I meant by "it doesn't exist", i.e. most people
can't use it.

mike

On 4/3/07, Ryan Daum <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
 > I know there are more SCM providers than what's on the trunk
there -- what
 > happened to the Mercurial provider (maven-scm-provider-hg) which
I submitted
 > patches to months ago and I was told was transferred to the SVN
sandbox
 > repository? See http://jira.codehaus.org/browse/SCM-230 ...
 >
 > Is there a document on the process involved in getting an SCM
provider out
 > into official distribution?  From my experience, commenting and
submitting
 > patches via JIRA doesn't seem to do it, as this work was
submitted many
 > months ago and seems to have been ignored :-)
 >
 > Ryan
 >
 >
 > On 4/3/07, Mike Perham < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
 > > I'm not aware of any.  If it's not here, it doesn't exist.
 > >
 > >
 > http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/
 > >
 > >
 > > On 4/3/07, Tim Reilly <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
 > > > Can anyone tell me what the state of PVCS integration is.
 > > > I recall some discussions a while ago that a provider for
PVCS was in
 > the
 > > > works?
 > > >
 > > >
 > > >
 > >
 >
 >
 >
 > --
 > Ryan Daum
 > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
 > Senior Developer, Toronto
 > 647.724.5232 x 2073




--
Ryan Daum
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Senior Developer, Toronto
647.724.5232 x 2073

Re: Other scms...

[Emmanuel Venisse]

They need to be updated with latest code of maven-scm-api.

Emmanuel

Ryan Daum a écrit :

What is the procedure for graduating from sandbox?

Ryan

On 4/4/07, *Mike Perham* <[EMAIL PROTECTED] > 
wrote:


Ah, right.  http://svn.apache.org/viewvc/maven/sandbox/trunk/scm/


But until it graduates from the sandbox, it's not integrated into the
release plugin, etc and so isn't terribly useful to the community at
large.  That's what I meant by "it doesn't exist", i.e. most people
can't use it.

mike

On 4/3/07, Ryan Daum <[EMAIL PROTECTED]
> wrote:
 > I know there are more SCM providers than what's on the trunk
there -- what
 > happened to the Mercurial provider (maven-scm-provider-hg) which
I submitted
 > patches to months ago and I was told was transferred to the SVN
sandbox
 > repository? See http://jira.codehaus.org/browse/SCM-230 ...
 >
 > Is there a document on the process involved in getting an SCM
provider out
 > into official distribution?  From my experience, commenting and
submitting
 > patches via JIRA doesn't seem to do it, as this work was
submitted many
 > months ago and seems to have been ignored :-)
 >
 > Ryan
 >
 >
 > On 4/3/07, Mike Perham < [EMAIL PROTECTED]
> wrote:
 > > I'm not aware of any.  If it's not here, it doesn't exist.
 > >
 > >
 > http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/
 > >
 > >
 > > On 4/3/07, Tim Reilly <[EMAIL PROTECTED]
> wrote:
 > > > Can anyone tell me what the state of PVCS integration is.
 > > > I recall some discussions a while ago that a provider for
PVCS was in
 > the
 > > > works?
 > > >
 > > >
 > > >
 > >
 >
 >
 >
 > --
 > Ryan Daum
 > [EMAIL PROTECTED] 
 > Senior Developer, Toronto
 > 647.724.5232 x 2073




--
Ryan Daum
[EMAIL PROTECTED] 
Senior Developer, Toronto
647.724.5232 x 2073

Re: We're near the release of 1.0 final

[Emmanuel Venisse]

Brett Porter a écrit :


On 28/03/2007, at 2:37 AM, Emmanuel Venisse wrote:

I added two development guide in the site, it would be cool if you can 
look at it.


The docs look good - thanks for that.


cool :)



I have some questions about the SCM manager part: it's unclear about how 
getScmManager is used. It looks like something you'd get all the time, 
but you wouldn't want to start a new plexus container, or construct and 
add all the time. Maybe this needs to be altered a bit to be clearer?


Yes, I wanted to change it today, with an initialize method and the getter that 
will return the container.



Also, can we add a basic SCM manager to the release? That looks pretty 
straight-forward and would take care of the JIRA issue about creating a 
POJO facade.


sure. I'll modify the doc with it.



For the commands: might be good to break these out into individual 
documents? I imagine there are probable more commands to list and 
document too.


ok



Finally, on the site structure:
- I think more detail on the front page, as well as links to the guides 
is needed.


ok


- The guides index page is missing one of the links


ok

- need breadcrumbs so that when you go into the plugin site, you can get 
back


ok


- we should have the javadoc for the API on the site somewhere


sure.

- should we move the SCM space to cwiki since it can be autoexported? 
Then we can put the provider matrix and the provider details pages 
together and link them in to the site as static pages


cwiki? where is it?

- do we need small guides on each provider that outline the 
differences/quirks/specific configuration needed?


we already have it, each provider page provide informations but maybe we need 
more information



Just lots of thoughts... not sure how many we need to do for 1.0 :)


I'll see what I can do :)

Emmanuel


wdyt?

- Brett

Re: We're near the release of 1.0 final

[Emmanuel Venisse]

Dennis Lundberg a écrit :

Emmanuel Venisse wrote:

Hi,

Now, we have only one issue to fix and all issues assigned to 1.0 will 
be fixed :)


When building the site I noticed that Maven SCM is using 
modello-maven-plugin 1.0-alpha-6, which is quite old. It is used for the 
settings in provider implementations. The latest version of 
modello-maven-plugin is alpha-15. Should I update it?


Go for it.





I added two development guide in the site, it would be cool if you can 
look at it.


Emmanuel

Re: We're near the release of 1.0 final

[Emmanuel Venisse]

Dennis Lundberg a écrit :

Emmanuel Venisse wrote:

Hi,

Now, we have only one issue to fix and all issues assigned to 1.0 will 
be fixed :)


I added two development guide in the site, it would be cool if you can 
look at it.


Emmanuel



As you might have seen by the commits, I have read through the new docs 
and made some minor changes and fixes. I also had a look at the site as 
a whole and removed some skin parts that are no longer needed.




Thanks Dennis.

Emmanuel

Re: svn commit: r520837 - in /maven/scm/trunk: maven-scm-api/src/main/java/org/apache/maven/scm/command/checkout/ maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/ maven-scm-plugin/src/test/

[Emmanuel Venisse]

Mike,

I don't know if Perforce checkout files in the current directory or in a subdirectory for a "view", but if it's in a subdirectory like clearcase, it would be useful to use the new contructor of 
CheckOutScmResult.


Emmanuel

[EMAIL PROTECTED] a écrit :

Author: evenisse
Date: Wed Mar 21 04:04:06 2007
New Revision: 520837

URL: http://svn.apache.org/viewvc?view=rev&rev=520837
Log:
[SCM-288] Improved support for SCM providers like ClearCase that do NOT check 
out directly into the check-out-dir but into sub-directories of the 
check-out-dir
Submitted by: Arne Degenring

Added:

maven/scm/trunk/maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/BootstrapMojoTest.java
   (with props)
Modified:

maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/command/checkout/CheckOutScmResult.java

maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java

maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/CheckoutMojo.java

maven/scm/trunk/maven-scm-providers/maven-scm-provider-clearcase/src/main/java/org/apache/maven/scm/provider/clearcase/command/checkout/ClearCaseCheckOutCommand.java

Modified: 
maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/command/checkout/CheckOutScmResult.java
URL: 
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/command/checkout/CheckOutScmResult.java?view=diff&rev=520837&r1=520836&r2=520837
==
--- 
maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/command/checkout/CheckOutScmResult.java
 (original)
+++ 
maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/command/checkout/CheckOutScmResult.java
 Wed Mar 21 04:04:06 2007
@@ -31,8 +31,21 @@
 public class CheckOutScmResult
 extends ScmResult
 {
+
 private List checkedOutFiles;
 
+/**

+ * The relative path of the directory of the checked out project in 
comparison to the checkout directory, or
+ * an empty String in case the checkout directory equals the project 
directory.
+ * 
+ * With most SCMs, this is just an empty String, meaning that the checkout 
directory equals the project directory.
+ * But there are cases (e.g. ClearCase) where within the checkout 
directory, the directory structure of the
+ * SCM system is repeated. E.g. if you check out the project "my/project" to 
"/some/dir", the project sources
+ * are actually checked out to "my/project/some/dir". In this example, 
relativePathProjectDirectory would
+ * contain "my/project".
+ */
+protected String relativePathProjectDirectory = "";
+
 public CheckOutScmResult( String commandLine, String providerMessage, 
String commandOutput, boolean success )
 {
 super( commandLine, providerMessage, commandOutput, success );
@@ -45,6 +58,16 @@
 this.checkedOutFiles = checkedOutFiles;
 }
 
+public CheckOutScmResult( String commandLine, List checkedOutFiles, String relativePathProjectDirectory )

+{
+this( commandLine, checkedOutFiles );
+
+if ( relativePathProjectDirectory != null )
+{
+this.relativePathProjectDirectory = relativePathProjectDirectory;
+}
+}
+
 public CheckOutScmResult( List checkedOutFiles, ScmResult result )
 {
 super( result );
@@ -55,5 +78,14 @@
 public List getCheckedOutFiles()
 {
 return checkedOutFiles;
+}
+
+/**
+ * @return the contents of [EMAIL PROTECTED] #relativePathProjectDirectory}
+ * @see #relativePathProjectDirectory
+ */
+public String getRelativePathProjectDirectory()
+{
+return relativePathProjectDirectory;
 }
 }

Modified: 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java
URL: 
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java?view=diff&rev=520837&r1=520836&r2=520837
==
--- 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java
 (original)
+++ 
maven/scm/trunk/maven-scm-plugin/src/main/java/org/apache/maven/scm/plugin/BootstrapMojo.java
 Wed Mar 21 04:04:06 2007
@@ -20,6 +20,7 @@
  */
 
 import org.apache.maven.plugin.MojoExecutionException;

+import org.apache.maven.scm.command.checkout.CheckOutScmResult;
 import org.codehaus.plexus.util.StringUtils;
 import org.codehaus.plexus.util.cli.CommandLineException;
 import org.codehaus.plexus.util.cli.CommandLineUtils;
@@ -55,7 +56,9 @@
 private String goals;
 
 /**

- * The subdirectory (under the checkout directory) in which to run the 
goals.
+ * The subdirectory (under the project directory) in which to run the 
goals.
+ * The project directory is the same as the checkout directory in most

Re: Preparing Maven SCM 1.0

[Emmanuel Venisse]

Emmanuel Venisse a écrit :



Trygve Laugstøl a écrit :

Emmanuel Venisse wrote:

Hi,

I'd like to release Maven 1.0 in next weeks. As you can see, I 
updated jira for this version.


Before to do it, we need to fix some major issues with some providers.


[snip]

The issues you listed are only technical issues with the provider, not 
something that should you from releasing 1.0 of the API. I think that 
at the same time that the API is releases we split out the providers 
from the API and give them their own release cycle.


We have some changes in API like list and export commands.



That makes it easier to release providers as necessary and we get a 
stable API that doesn't move (or doesn't move but is released) every 
time someone fixes an issue in the Foo provider.


With 1.0 release, I'll release providers too with 1.0 version, then, 
providers will have their own release cycle with a version like 1.0.x 
for providers that use API 1.0, 1.1.x for providers that use API 1.1...


An other possibility would be to release all when we want to release API or a 
provider like we do it in some other projects like Modello

Re: Preparing Maven SCM 1.0

[Emmanuel Venisse]

Trygve Laugstøl a écrit :

Emmanuel Venisse wrote:

Hi,

I'd like to release Maven 1.0 in next weeks. As you can see, I updated 
jira for this version.


Before to do it, we need to fix some major issues with some providers.


[snip]

The issues you listed are only technical issues with the provider, not 
something that should you from releasing 1.0 of the API. I think that at 
the same time that the API is releases we split out the providers from 
the API and give them their own release cycle.


We have some changes in API like list and export commands.



That makes it easier to release providers as necessary and we get a 
stable API that doesn't move (or doesn't move but is released) every 
time someone fixes an issue in the Foo provider.


With 1.0 release, I'll release providers too with 1.0 version, then, providers will have their own release cycle with a version like 1.0.x for providers that use API 1.0, 1.1.x for providers that use 
API 1.1...


Emmanuel

Re: Is a Changeset without files allowed?

[Emmanuel Venisse]

It would be better to return an empty list instead of null. File an issue and 
we'll look at it
But for the changelog plugin, you need to make a workaround for now.

Emmanuel

Dennis Lundberg a écrit :

I'm trying to figure out
  http://jira.codehaus.org/browse/MCHANGELOG-54

The reporter is getting an NPE based on the fact that the ChangeSet 
returns null from getFiles(). I'm curious to know whether it is valid to 
have a ChangeSet without files, i.e. where getFiles() returns null. I 
feel as if the SCM provider should at least return an empty List from 
getFiles() if it contains no files.


The provider in this case is Synergy. Is this a bug in the Synergy 
provider? Or should the changes-plugin be altered to handle the case 
that getFiles() might return null?

Re: Bazaar test failures

[Emmanuel Venisse]

build fine now

Emmanuel

Brett Porter a écrit :

Hi,

There appears to be a test failure in Continuum for Bazaar now that I 
have the client installed again. This is bzr-0.13, Python-2.5, Solaris 
10 x86.


http://maven.zones.apache.org/continuum/surefireReport.action?buildId=2367&projectId=202&projectGroupId=16#org.apache.maven.scm.provider.bazaar.command.changelog.BazaarChangeLogCommandTckTest 



Anyone have any ideas?

- Brett

Re: Serena/PVCS support

[Emmanuel Venisse]

Peter,

if you stop your work on the serena provider, can you attach it to an issue? So we'll can add it in 
the maven-scm sandbox and users will can look at it and provide other commands.


Emmanuel

Peter Ineson a écrit :

Opps, I sent this to the incorrect address
 
 
Hi Steve & Antoine,


Sorry about the slow replies, Holdays, jet lag and general bussiness have
not left much time.

I did end pondering about which API to use, I plummed for PCLI command line
tools as it is probably the best supported for the various versions of
Serena.

URL format;
   scm:serena:user:[EMAIL PROTECTED]:project_path:sub_directory

Promotion group can be set via a system property or from a comfiguration
file.

Now at work I have just been tasked with porting our projects from 
Serena to

Subversion (yipppethe nagging worked) so I am not planning to do
much more development, so Antoine I shall pass on what code I had done so
far. I have only checkout functionality and I am at the testing phase at 
the

moment.

Cheers
Peter Ineson
Cheers
Peter Ineson
 
Web: http://home.people.net.au/~peter_ineson/


- Original Message -
*From:* Antoine Veret 
*To:* scm-dev@maven.apache.org 
*Sent:* Monday, October 09, 2006 10:35 PM
*Subject:* Serena/PVCS support

Hello, I need the PVCS provider, is Peter Ineson (or someone else)
still working it ?
The SCM-34 issue doesn’t seem to be up to date.

Thanks you

Antoine Véret

Re: How to use VSS in Maven 2 together with Continuum?

[Emmanuel Venisse]

I don't think all commands required by continuum are implemented in vss provider

Emmanuel

Julien Henry a écrit :


Hi,

You don't have anything to add in your pom (only write the correct scm 
URL). But you have to add maven-scm-provider-vss-XXX.jar in 
$CONTINUUM_HOME/apps/continuum/lib, because it seems it was not packaged 
with Continuum 1.0.3.


++

Julien

Bill Qiu a écrit :


Hi,

Could anybody tell me how to use Visual Source Safe in Maven 2? From 
the Maven 2 web page, I see the VSS has been partially implemented,
and following the instruction, I am using the right scm url, I am 
trying to use Continuum to set up the auto build, but somehow, I got 
error message

like below:

Provider message: No such provider: 'vss'.


Then I downloaded the latest maven-scm-plugin, and modify my pom to 
include




org.apache.maven.plugins
maven-scm-plugin
1.0-beta-3


in the plugins section to override the scm plugin. but I still got the 
same problem. Is there particular thing I need to do to register the 
new scm

provider?

Could anybody help?

Thanks a lot,

Bill 

Re: Serena/PVCS support

[Emmanuel Venisse]

Peter Ineson a écrit :
Well, I have made a start, I rekon by the end of next week I should have 
completed basic checkout functionality. How do I go about getting the 
code checked in? Pass the code on to someone in the project team for 
review and checkin, or do I need to get a developer access to svn?


You just need to attach your patch to an issue (http://jira.codehaus.org/browse/SCM), and we'll 
review it.

You must respect our code style 
(http://maven.apache.org/guides/development/guide-m2-development.html)
Each part must be tested with junit tests, and it would be great to implement 
the TCK too.



Another question, which version of Java is being used to build with? I 
was thinking of using assertions and possibly enum's if possible.


1.4

Emmanuel


Cheers
Peter Ineson

Web: http://home.people.net.au/~peter_ineson/

- Original Message - From: "Peter Ineson" 
<[EMAIL PROTECTED]>

To: 
Sent: Thursday, August 10, 2006 9:58 PM
Subject: Re: Serena/PVCS support


Bugger, possibly the worst answer ;-) I should be able to spend some 
time adding basic functionality. (you just know when I've completed 
then Serena will permit their guys to release their code)


I have been looking at the code and it looks pretty easy to do. If I 
follow the code structure used by the cvs/svn then it should be pretty 
easy to change implementation if Serena ever release the code. I shall 
have a ponder over the weekend.


On a different tack. One thing that did occur to me, on the source 
repository page there is not an example for checking out the code 
using SCM!


Cheers
Peter Ineson

Web: http://home.people.net.au/~peter_ineson/

- Original Message - From: "Brett Porter" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, August 09, 2006 10:27 AM
Subject: Re: Serena/PVCS support


So the answer is, yes, we're interested if you can spend some time 
writing it :)


- Brett

On 9/08/2006 1:07 AM, Emmanuel Venisse wrote:
The latest news we have is that they can't donate the code due to a 
pb with company policy : 
http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200606.mbox/[EMAIL PROTECTED] 
Emmanuel


Jason van Zyl a écrit :

Hi,

Serena themselves have actually written support for Maven SCM. If 
there is anyone from Serena on this list maybe the could update us 
on the status of donating the code?


I will also try to find out.

Jason.

Re: Serena/PVCS support

[Emmanuel Venisse]

The latest news we have is that they can't donate the code due to a pb with company policy : 
http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200606.mbox/[EMAIL PROTECTED]


Emmanuel

Jason van Zyl a écrit :

Hi,

Serena themselves have actually written support for Maven SCM. If there 
is anyone from Serena on this list maybe the could update us on the 
status of donating the code?


I will also try to find out.

Jason.

On 8 Aug 06, at 8:36 AM 8 Aug 06, Peter Ineson wrote:


Hi,

Is anyone writing support Serena/PVCS at the moment? If no one is at 
the moment I can spend some time writing some support if you like.


Cheers
Peter Ineson




Jason van Zyl
[EMAIL PROTECTED]

Re: RE: scm:add

[Emmanuel Venisse]

yes.

Emmanuel

Sharma, Jaikumar a écrit :
   Does it mean if I implement "add" in my provider it is still valid 
and used by wagon-scm-provider for its operations ?  
   Thanks.


-Original Message-
*From:* dan tran [mailto:[EMAIL PROTECTED]
*Sent:* Friday, July 21, 2006 11:50 AM
*To:* scm-dev@maven.apache.org
*Subject:* Re: scm:add

wagon-scm-provider talks directly to maven-scm-api, not
maven-scm-plugin
 
-d


 
On 7/20/06, *Sharma, Jaikumar*

<[EMAIL PROTECTED]
> wrote:

As per earlier posts, add is used by
wagon-scm-provider ?

http://www.nabble.com/maven-scm-plugin-goals-question-t1906299.html

-Original Message-
*From:* dan tran [mailto: [EMAIL PROTECTED]
]
*Sent:* Friday, July 21, 2006 9:07 AM
*To:* scm-dev@maven.apache.org

*Subject:* Re: scm:add

add mojo is not in plugin yet since we dont see
a good use for it yet
and no one asks.  But you are welcome to
implement it
 
-D


 
On 7/20/06, *Henry C.* < [EMAIL PROTECTED]

> wrote:

Hello,

I am trying to write a scm provider and
noticed I cannot run the scm:add
goal.  Maven was complaining the goal does
not exist or something.  In the
scm project I checked out (from
http://maven.apache.org/scm/source-repository.html),
I noticed
maven-scm-plugin does not have an add mojo
(no AddMojo.java ).  Did I check
out the wrong project?

Thank you,
Ekio


_

Play Q6 for your chance to WIN great prizes.
http://q6trivia.imagine-live.com/enca/landing


- - - - - - - DISCLAIMER- - - - - - - -

Unless indicated otherwise, the information
contained in this message is privileged and
confidential, and is intended only for the use of
the addressee(s) named above and others who have
been specifically authorized to receive it. If you
are not the intended recipient, you are hereby
notified that any dissemination, distribution or
copying of this message and/or attachments is
strictly prohibited. The company accepts no
liability for any damage caused by any virus
transmitted by this email. Furthermore, the company
does not warrant a proper and complete transmission
of this information, nor does it accept liability
for any delays. If you have received this message in
error, please contact the sender and delete the
message. Thank you.


- - - - - - - DISCLAIMER- - - - - - - -

Unless indicated otherwise, the information contained in this message is 
privileged and confidential, and is intended only for the use of the 
addressee(s) named above and others who have been specifically 
authorized to receive it. If you are not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
message and/or attachments is strictly prohibited. The company accepts 
no liability for any damage caused by any virus transmitted by this 
email. Furthermore, the company does not warrant a proper and complete 
transmission of this information, nor does it accept liability for any 
delays. If you have received this message in error, please contact the 
sender and delete the message. Thank you.

Re: Integrating custom SCM with maven

[Emmanuel Venisse]

1- create a new project that extends maven-scm-providers project
2- create a ScmProvider that extends 
org.apache.maven.scm.provider.AbstractScmProvider
3- create a ScmProviderRepository
4- implement scm commands

Emmanuel

Anirudh Chandrakant a écrit :

Hi,

I have my own built-from-scratch version control system. I wish to now 
integrate this with Maven (like CVS, Subversion, etc).


Could anyone please list down the things i need to do to be able to 
achieve this?


Thanks,
Anirudh

Re: PVCS and Maven

[Emmanuel Venisse]

Hi Francis,

Do you have some news?

Thanks
Emmanuel

Francis Long a écrit :
> Hi Brett,
> 
> One of our partner has developed this integration and we are talking with 
> them for devoting this code. 
> 
> 
> Thanks and best regards,
> 
>  
> 
> Francis Long Guangyu
> 
>  Serena Software
> 
>  
> 
> TEL:  +86 21 51160595
> 
> FAX:  +86 21 51160780
> 
> Mobile: +86 139 1818 4826
> 
> www.serena.com
> 
> 
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED] 
> Sent: 2006年5月19日 15:04
> To: scm-dev@maven.apache.org
> Cc: David Parker; Francis Long; Kevin Parker
> Subject: Re: PVCS and Maven
> 
> Hi Kevin,
> 
> I was wondering if there had been any further progress on this matter?
> 
> Thanks,
> Brett
> 
> Kevin Parker wrote:
>> Dear Maven’s,
>>
>> We have recently developed a Maven interface for our PVCS product and 
>> are interested in the process for potentially donating this to the 
>> project. Could someone contact me and let me know what the process would be.
>>
>> Sincerely,
>>
>> *//**//**//**/Kevin
>> /**//**//**/
>> /Kevin Parker
>> *///Vice President Market Development /***Serena Software 
>> Inc*.
>> 2755 Campus Drive, 3^rd Floor, San Mateo, CA 94403-2538
>> ***www.serena.com
>> *tel 650-522-6635
>> fax 650-522-6835
>> cell650-224-1691
>> email   [EMAIL PROTECTED]
>>
>>
>>
>> **
>> This email and any files transmitted with it are confidential and 
>> intended solely for the use of the individual or entity to whom they 
>> are addressed. Any unauthorized review, use, disclosure or 
>> distribution is prohibited. If you are not the intended recipient, 
>> please contact the sender by reply e-mail and destroy all copies of the 
>> original message.
> 
> 
> --
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
> 
> 
> 

Re: M2 : Log info is duplicated

[Emmanuel Venisse]

We check three parameters connectionUrl, project.scm.connection and project.scm.developerConnection, 
so if you use these three parameters, you'll see three validations in logs but they aren't the same.


Emmanuel

Sharma, Jaikumar a écrit :
Does any one of you know the reason or it might be repeated goals 
executions in Maven lifecycle ?
 
Thanks.


-Original Message-
*From:* Sharma, Jaikumar
*Sent:* Wednesday, June 07, 2006 11:21 AM
*To:* 'scm-dev@maven.apache.org'
*Subject:* M2 : Log info is duplicated

Emmanuel,
 
When I run scm:validate, the info you can see below is duplicated

(two times) while I have specified it at one place in
MksScmRepository class as :
log.info("Parsing MKS URL
 
I have tried to search for the reason, but could not find any

relevent clue.
 
Does it parses the class two times or what ?
 
Jaikumar
 
 
[INFO] Scanning for projects...

[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO]

[INFO] Building Unnamed - com.mycompany.testplugin:testmksplugin:jar:1.0
[INFO]task-segment: [scm:validate] (aggregator-style)
[INFO]

[INFO] Preparing scm:validate
[INFO] No goals needed for project - skipping
[WARNING]
 Artifact org.codehaus.plexus:plexus-utils:jar:1.1:runtime retains
local scope 'runtime' overriding broader scope 'compile'
 given by a dependency. If this is not intended, modify or remove
the local scope.
 
[INFO] [scm:validate]

Parsing MKS URL
user name is :username
password is :password
servername isservername
project name is projectname
sandbox location is sbxlocation
[INFO] connectionUrl scm connection string is valid.
Parsing MKS URL
user name is :username
password is :password
servername isservername
project name is projectname
sandbox location is sbxlocation
[INFO] project.scm.connection scm connection string is valid.
[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]

[INFO] Total time: 4 seconds
[INFO] Finished at: Wed Jun 07 11:13:35 GMT+05:30 2006
[INFO] Final Memory: 3M/8M
[INFO]

 

Re: M2 : where [connection] parameter is documented for SCM ?

[Emmanuel Venisse]

http://maven.apache.org/ref/current/maven-model/maven.html#class_scm
http://maven.apache.org/scm/scm-url-format.html

Emmanuel

Sharma, Jaikumar a écrit :

Emmanuel,
 
Where this  (as shown below) parameter is documented, I can 
not find it ? 
 
 
scm:scmprovidername:

 
Regards,


- - - - - - - DISCLAIMER- - - - - - - -

Unless indicated otherwise, the information contained in this message is 
privileged and confidential, and is intended only for the use of the 
addressee(s) named above and others who have been specifically 
authorized to receive it. If you are not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
message and/or attachments is strictly prohibited. The company accepts 
no liability for any damage caused by any virus transmitted by this 
email. Furthermore, the company does not warrant a proper and complete 
transmission of this information, nor does it accept liability for any 
delays. If you have received this message in error, please contact the 
sender and delete the message. Thank you.

Re: M2 : How to handle login into SCM provider implementation ?

[Emmanuel Venisse]

It's used in 
http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/provider/AbstractScmProvider.java


and public LoginScmResult login( ScmRepository repository, ScmFileSet fileSet, CommandParameters 
parameters ) is overridden in 
http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/maven-scm-providers-cvs/maven-scm-provider-cvs-commons/src/main/java/org/apache/maven/scm/provider/cvslib/AbstractCvsScmProvider.java


Emmanuel

Sharma, Jaikumar a écrit :
How Login interface is being used in cvs provider ? Could you please 
give me a hint ?


-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 06, 2006 3:56 PM
To: scm-dev@maven.apache.org
Subject: Re: M2 : How to handle login into SCM provider implementation ?


A user can log with username/password mojo parameters.

mvn -Dusername=your_username -Dpassword=your_password scm:checkout

In maven-scm api, we have an Login interface that can be used by the 
provider like we do it in cvs
provider. You can do the same in your provider if you need it, but the 
login won't be available as a
scm mojo. You won't need it if mks allow to define username/password on 
all commands.


<<< How Login interface is being used in cvs provider ? Could you please 
give me a hint ? >>>


   or I have to wrap the login functionality into scm:validate itself ?


Emmanuel

Sharma, Jaikumar a écrit :
 > Emmanuel,
 > How I can handle user login into the SCM provider implementation ?
 > There
 > is no login goal available in SCM plugin ?
 > http://maven.apache.org/scm/plugins/index.html
 > Regards
 > 
 > 


- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is 
privileged and confidential, and is intended only for the use of the 
addressee(s) named above and others who have been specifically 
authorized to receive it. If you are not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
message and/or attachments is strictly prohibited. The company accepts 
no liability for any damage caused by any virus transmitted by this 
email. Furthermore, the company does not warrant a proper and complete 
transmission of this information, nor does it accept liability for any 
delays. If you have received this message in error, please contact the 
sender and delete the message. Thank you.

Re: M2 : How to handle login into SCM provider implementation ?

[Emmanuel Venisse]

A user can log with username/password mojo parameters.

mvn -Dusername=your_username -Dpassword=your_password scm:checkout

In maven-scm api, we have an Login interface that can be used by the provider like we do it in cvs 
provider. You can do the same in your provider if you need it, but the login won't be available as a 
scm mojo. You won't need it if mks allow to define username/password on all commands.


Emmanuel

Sharma, Jaikumar a écrit :

Emmanuel,
How I can handle user login into the SCM provider implementation ? There 
is no login goal available in SCM plugin ?

http://maven.apache.org/scm/plugins/index.html
Regards
 
 

Re: RE: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

It seems you got some connection pb to the repo because artifacts are there.
http://repo.mergere.com/maven2/org/apache/maven/scm/maven-scm-provider-bazaar/1.0-beta-3/
http://repo.mergere.com/maven2/org/apache/maven/scm/maven-scm-provider-local/1.0-beta-3/
http://repo.mergere.com/maven2/org/apache/maven/scm/maven-scm-provider-vss/1.0-beta-3/

Emmanuel

Sharma, Jaikumar a écrit :

I run mvn scm:validate in the folder where the test pom is located, it
gave me the following, or I had to run different command line ?

D:\Plugin_Tests>mvn scm:validate
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO]


[INFO] Building Unnamed - com.mycompany.testplugin:testmksplugin:jar:1.0
[INFO]task-segment: [scm:validate] (aggregator-style)
[INFO]


[INFO] Preparing scm:validate
[INFO] No goals needed for project - skipping
Downloading:
file:C:\Lang\maven-2.0.4/Repository/org/apache/maven/scm/maven-scm-p
rovider-local/1.0-beta-3/maven-scm-provider-local-1.0-beta-3.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
file:C:\Lang\maven-2.0.4/Repository/org/apache/maven/scm/maven-scm-p
rovider-bazaar/1.0-beta-3/maven-scm-provider-bazaar-1.0-beta-3.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
Artifact org.codehaus.plexus:plexus-utils:jar:1.1:runtime
retains local scope 'runtime' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove
the local scope.

Downloading:
file:C:\Lang\maven-2.0.4/Repository/org/apache/maven/scm/maven-scm-p
rovider-bazaar/1.0-beta-3/maven-scm-provider-bazaar-1.0-beta-3.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
file:C:\Lang\maven-2.0.4/Repository/org/apache/maven/scm/maven-scm-p
rovider-vss/1.0-beta-3/maven-scm-provider-vss-1.0-beta-3.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
file:C:\Lang\maven-2.0.4/Repository/org/apache/maven/scm/maven-scm-p
rovider-local/1.0-beta-3/maven-scm-provider-local-1.0-beta-3.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) org.apache.maven.scm:maven-scm-provider-bazaar:jar:1.0-beta-3

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.maven.scm
-DartifactId=maven-scm-provider-bazaar \
  -Dversion=1.0-beta-3 -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency:
1)
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-3
2) org.apache.maven.scm:maven-scm-provider-bazaar:jar:1.0-beta-3

2) org.apache.maven.scm:maven-scm-provider-vss:jar:1.0-beta-3

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.maven.scm
-DartifactId=maven-scm-provider-vss \
  -Dversion=1.0-beta-3 -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency:
1)
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-3
2) org.apache.maven.scm:maven-scm-provider-vss:jar:1.0-beta-3

3) org.apache.maven.scm:maven-scm-provider-local:jar:1.0-beta-3

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.maven.scm
-DartifactId=maven-scm-provider-local \
  -Dversion=1.0-beta-3 -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency:
1)
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-3
2) org.apache.maven.scm:maven-scm-provider-local:jar:1.0-beta-3

--
3 required artifacts are missing.

for artifact:
  org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-3

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.snapshots (http://svn.apache.org/maven-snapshot-repository)


[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 2 seconds
[INFO] Finished at: Mon Jun 05 15:40:05 GMT+05:30 2006
[INFO] Final Memory: 3M/6M
[INFO]




-Original Message-
From: Emmanuel Venisse [mail

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

Do you have some errors when you run the scm plugin?
<<  Do you mean, if I have the correct / running version of scm plugin 
is installed ? if yes, then yes, I can see al the gols listed in that using


  command : mvn help:describe -DgroupId=org.apache.maven.plugins 
-DartifactId=maven-scm-plugin -Dfull=true >>>


I meant when you run scm:validate with the mks provider.



Why do you add a main method in MksScmProvider?
<<< It had been add to test the results of scmURL, this has to be 
removed >>>


It would be better to implement junit tests so you'll can check the test 
coverage.



Thanks for your help!


No Problem

Emmanuel

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

It depends of your log implementation. How do you use them? Do you use scm logger like in other 
providers?


When you execute scm-api with a mojo like the scm plugin, the log level used is INFO and if you use 
-X maven parameter, it will be DEBUG.


Emmanuel

Jaikumar Sharma a écrit :

Emmanuel,
 
As you mentioned, pom corrected, but there is no breakthrough, not 
getting any test result for the tag   mentioend below in the 
test pom.
 
1. Can I get some Info or type of log message while testing (which I 
specify in MksScmProvider class in the main implementation class) ?
2. My basic objective is just to get log type of message first, just to 
get an idea whether the implementation class is executed during my test.
 
Please suggest !
 
Regards,
 
 
 
 
Sharma, Jaikumar a écrit :
 


Thanks Emmanuel, pom.xml is corrected, but at the first hand I would
like to know the following to get the better idea of the sequence of
execution from the entry point of the plugin :

1.components.xml contains the entry point of the pluing ? If yes, in
my case main entry point mentioned is components.xml is MksScmProvider. 

It's the entry point of the provider. Maven-SCM find the provider to use 
with the second token in the connection url that must be the role-hint 
of one of the providers.



  


org.apache.maven.scm.provider.ScmProvider

  mks


org.apache.maven.scm.provider.mks.MksScmProvider



  


so, in my view, this class is executed and chanin of methods also as
called from this only ? So, in my case it is not responding any
error or something irrspective of whatever I specify in :

   
 scm:mks:"[EMAIL [EMAIL PROTECTED]"
 

Something else can be checked ? As I can see in case of other
provider implementations xpp3 (xml pull parser ? Do I have to tweak
or change something in this too ? 

If you don't have general settings that can be used by all scm 
connection, you don't need to create a provider settings loaded by xpp3, 
depends on the provider usage. A sample of parameter that can be general 
for the cvs provider is the compression level to use for all commands.


Emmanuel


Jaikumar

-Original Message-
    From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 11:00 AM
To: scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
Subject: Re: M2 : How to implement goals in SCM provider implementation ?


Your pom is totally wrong. It must be:



 4.0.0
 com.mycompany.mytestscm
 testmksplugin
 1.0

 
 scm:mks:"[EMAIL [EMAIL PROTECTED]"
 

 

 
  
 org.apache.maven.scm
 maven-scm-plugin
 1.0-beta-3
 

   org.apache.maven.scm
   maven-mks-provider

1.0 

 
  
 

 





Sharma, Jaikumar a écrit :
 > Hi Emmanuel, I am using the following pom.xml to connect to
 > Mks-Provider :
 >
 > 
 >
 > 4.0.0

 > com.mycompany.mytestscm >
testmksplugin

 > 1.0

 > > > 

 >  
 > org.apache.maven.scm
 > maven-scm-plugin
 > 1.0-beta-3

 >  > > 

 >

 >  > > 

 >  
 > org.apache.maven.scm
 > maven-mks-provider
 > 1.0
 >
 >  

 > > scm:mks:"[EMAIL [EMAIL PROTECTED]"

 >  
 >

 >  >  > >  > > 

 >
 > -Original Message-
 > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
 > Sent: Thursday, June 01, 2006 7:49 PM
 > To: scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
 > Subject: Re: M2 : How to implement goals in SCM provider
 > implementation ?
 >
 >
 > What is  ? Where do you put it?
 >
 > Can you provide a sample scm url for mks? I guess
 > scm:mks:"[EMAIL PROTECTED]" isn't one, right? If it is, I'm not sure

 > it's correct because you don't have info about path to the
project on a MKS

 >
 > Server or locally or something else, Note that I don't know how mks
 > works and 

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

No it isn't necessary. They are added when new providers are added in svn.

Emmanuel

Sharma, Jaikumar a écrit :
Is it necessary that a any new SCM provider should be registered in 
maven-scm-providers list first before compilation / test of the new 
implementation ?
 
Regards.
 
-Original Message-

*From:* Sharma, Jaikumar
*Sent:* Monday, June 05, 2006 12:17 PM
*To:* scm-dev@maven.apache.org
*Subject:* M2 : How to implement goals in SCM provider implementation ?

Emmanuel,
 
As you mentioned, pom corrected, but there is no breakthrough, not

getting any test result for the tag   mentioend below in
the test pom.
 
 How can I know, my main implementation class is instantiated ? 
 
Please suggest !
 
Regards,
 
 
Sharma, Jaikumar a écrit :
 


Thanks Emmanuel, pom.xml is corrected, but at the first hand I
would like to know the following to get the better idea of the
sequence of execution from the entry point of the plugin :

1.components.xml contains the entry point of the pluing ? If
yes, in my case main entry point mentioned is components.xml is
MksScmProvider. 


It's the entry point of the provider. Maven-SCM find the provider to
use with the second token in the connection url that must be the
role-hint of one of the providers.


  


org.apache.maven.scm.provider.ScmProvider

  mks


org.apache.maven.scm.provider.mks.MksScmProvider



  


so, in my view, this class is executed and chanin of methods
also as called from this only ? So, in my case it is not
responding any error or something irrspective of whatever I
specify in :

   
 scm:mks:"[EMAIL [EMAIL PROTECTED]"
 

Something else can be checked ? As I can see in case of other
provider implementations xpp3 (xml pull parser ? Do I have to
tweak or change something in this too ? 


If you don't have general settings that can be used by all scm
connection, you don't need to create a provider settings loaded by
xpp3, depends on the provider usage. A sample of parameter that can
be general for the cvs provider is the compression level to use for
all commands.

Emmanuel


Jaikumar

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 11:00 AM
To: scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
Subject: Re: M2 : How to implement goals in SCM provider implementation 
?


Your pom is totally wrong. It must be:



 4.0.0
 com.mycompany.mytestscm
 testmksplugin
 1.0

 
 scm:mks:"[EMAIL [EMAIL PROTECTED]"
 

 

 
  
 org.apache.maven.scm
 maven-scm-plugin
 1.0-beta-3
 

   org.apache.maven.scm
   maven-mks-provider

1.0 

 
  
 

 





Sharma, Jaikumar a écrit :
 > Hi Emmanuel, I am using the following pom.xml to connect to
 > Mks-Provider :
 >
 > 
 >
 > 4.0.0

 > com.mycompany.mytestscm >
testmksplugin

 > 1.0

 > > > 

 >  
 > org.apache.maven.scm
 > maven-scm-plugin
 > 1.0-beta-3

 >  > > 

 >

 >  > > 

 >  
 > org.apache.maven.scm
 > maven-mks-provider
 > 1.0
 >
 >  

 > > scm:mks:"[EMAIL [EMAIL PROTECTED]"

 >          
 >

 >  >  > >  > > 

 >
 > -Original Message-
 > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
 > Sent: Thursday, June 01, 2006 7:49 PM
 > To: scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
 > Subject: Re: M2 : How to implement goals in SCM provider
 > implementation ?
 >
  

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

if you use a mks scm url in your pom and you use one of tha scm mojo and you don't get an error 
about non existent provider, your mks provider is used.


Emmanuel

Sharma, Jaikumar a écrit :

Emmanuel,
 
As you mentioned, pom corrected, but there is no breakthrough, not 
getting any test result for the tag   mentioend below in the 
test pom.
 
 How can I know, my main implementation class is instantiated ? 
 
Please suggest !
 
Regards,
 
 
Sharma, Jaikumar a écrit :
 


Thanks Emmanuel, pom.xml is corrected, but at the first hand I would
like to know the following to get the better idea of the sequence of
execution from the entry point of the plugin :

1.components.xml contains the entry point of the pluing ? If yes, in
my case main entry point mentioned is components.xml is MksScmProvider. 

It's the entry point of the provider. Maven-SCM find the provider to use 
with the second token in the connection url that must be the role-hint 
of one of the providers.



  


org.apache.maven.scm.provider.ScmProvider

  mks


org.apache.maven.scm.provider.mks.MksScmProvider



  


so, in my view, this class is executed and chanin of methods also as
called from this only ? So, in my case it is not responding any
error or something irrspective of whatever I specify in :

   
 scm:mks:"[EMAIL [EMAIL PROTECTED]"
 

Something else can be checked ? As I can see in case of other
provider implementations xpp3 (xml pull parser ? Do I have to tweak
or change something in this too ? 

If you don't have general settings that can be used by all scm 
connection, you don't need to create a provider settings loaded by xpp3, 
depends on the provider usage. A sample of parameter that can be general 
for the cvs provider is the compression level to use for all commands.


Emmanuel


Jaikumar

-Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 11:00 AM
To: scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
Subject: Re: M2 : How to implement goals in SCM provider implementation ?


Your pom is totally wrong. It must be:



 4.0.0
 com.mycompany.mytestscm
 testmksplugin
 1.0

 
 scm:mks:"[EMAIL [EMAIL PROTECTED]"
 

 

 
  
 org.apache.maven.scm
 maven-scm-plugin
 1.0-beta-3
 

   org.apache.maven.scm
   maven-mks-provider

1.0 

 
  
 

 





Sharma, Jaikumar a écrit :
 > Hi Emmanuel, I am using the following pom.xml to connect to
 > Mks-Provider :
 >
 > 
 >
 > 4.0.0

 > com.mycompany.mytestscm >
testmksplugin

 > 1.0

 > > > 

 >  
 > org.apache.maven.scm
 > maven-scm-plugin
 > 1.0-beta-3

 >  > > 

 >

 >  > > 

 >  
 > org.apache.maven.scm
 > maven-mks-provider
 > 1.0
 >
 >  

 > > scm:mks:"[EMAIL [EMAIL PROTECTED]"

 >  
 >

 >  >  > >  > > 

 >
 > -Original Message-
 > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
 > Sent: Thursday, June 01, 2006 7:49 PM
 > To: scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
 > Subject: Re: M2 : How to implement goals in SCM provider
 > implementation ?
 >
 >
 > What is  ? Where do you put it?
 >
 > Can you provide a sample scm url for mks? I guess
 > scm:mks:"[EMAIL PROTECTED]" isn't one, right? If it is, I'm not sure

 > it's correct because you don't have info about path to the
project on a MKS

 >
 > Server or locally or something else, Note that I don't know how mks
 > works and mks command lines.
 >
 > Emmanuel
 >
 > Sharma, Jaikumar a écrit :

 > > Fine, I have compiled it now by setting the packaging to 'jar',
but > > now > it is giving 'NullPointerExecption' after I try to
pass the

 > parameters to
 >  >
 >

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

Sharma, Jaikumar a écrit :
Thanks Emmanuel, pom.xml is corrected, but at the first hand I would 
like to know the following to get the better idea of the sequence of 
execution from the entry point of the plugin :


1.components.xml contains the entry point of the pluing ? If 
yes, in my case main entry point mentioned is components.xml is 
MksScmProvider.


It's the entry point of the provider. Maven-SCM find the provider to use with the second token in 
the connection url that must be the role-hint of one of the providers.





  

  
org.apache.maven.scm.provider.ScmProvider

  mks
  
org.apache.maven.scm.provider.mks.MksScmProvider 



  


 so, in my view, this class is executed and chanin of methods also as 
called from this only ? So, in my case it is not responding any error or 
something irrspective of whatever I specify in :


   
 scm:mks:"[EMAIL PROTECTED]@project"
 

Something else can be checked ? As I can see in case of other provider 
implementations xpp3 (xml pull parser ? Do I have to tweak or change 
something in this too ?


If you don't have general settings that can be used by all scm connection, you don't need to create 
a provider settings loaded by xpp3, depends on the provider usage.
A sample of parameter that can be general for the cvs provider is the compression level to use for 
all commands.


Emmanuel



Jaikumar   





   


-Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 11:00 AM
To: scm-dev@maven.apache.org
Subject: Re: M2 : How to implement goals in SCM provider implementation ?


Your pom is totally wrong. It must be:



 4.0.0
 com.mycompany.mytestscm
 testmksplugin
 1.0

 
 scm:mks:"[EMAIL PROTECTED]@project"
 

 

 
  
 org.apache.maven.scm
 maven-scm-plugin
 1.0-beta-3
 

   org.apache.maven.scm
   maven-mks-provider
   1.0 

 
  
 

 





Sharma, Jaikumar a écrit :
 > Hi Emmanuel, I am using the following pom.xml to connect to
 > Mks-Provider :
 >
 > 
 >
 > 4.0.0
 > com.mycompany.mytestscm
 > testmksplugin

 > 1.0
 >   
 >   
 > 

 >  
 > org.apache.maven.scm
 > maven-scm-plugin
 > 1.0-beta-3
 >
 >
 > 

 >
 > 
 >   
 > 

 >  
 > org.apache.maven.scm
 > maven-mks-provider
 > 1.0
 >
 >  
 >   
 > scm:mks:"[EMAIL PROTECTED]@project"

 >  
 >        
 >   
 > 
 >   
 > 
 >   
 > 

 >
 > -Original Message-
 > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
 > Sent: Thursday, June 01, 2006 7:49 PM
 > To: scm-dev@maven.apache.org
 > Subject: Re: M2 : How to implement goals in SCM provider
 > implementation ?
 >
 >
 > What is  ? Where do you put it?
 >
 > Can you provide a sample scm url for mks? I guess
 > scm:mks:"[EMAIL PROTECTED]" isn't one, right? If it is, I'm not sure
 > it's correct because you don't have info about path to the project on 
a MKS

 >
 > Server or locally or something else, Note that I don't know how mks
 > works and mks command lines.
 >
 > Emmanuel
 >
 > Sharma, Jaikumar a écrit :
 >  > Fine, I have compiled it now by setting the packaging to 'jar', but 
 > > now  > it is giving 'NullPointerExecption' after I try to pass the

 > parameters to
 >  >
 >  > 
 >  >  
 >  >   scm:mks:"[EMAIL PROTECTED]"
 >  >  
 >  > 
 >  >
 >  > Parameter  username and password in the form as mentioned above, it
 >  > expects as a parameter of MksScmProvider classs'
 >  >
 >  > Please suggest!
 >  >
 >  >
 >  >
 >  > -Original Message-
 >  > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
 >  > Sent: Thursday, June 01, 2006 6:38 PM
 >  > To: scm-dev@maven.apache.org
 >  > Subject: Re: M

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

Your pom is totally wrong. It must be:



4.0.0
com.mycompany.mytestscm
testmksplugin
1.0


scm:mks:"[EMAIL PROTECTED]@project"





 
org.apache.maven.scm
maven-scm-plugin
1.0-beta-3

   
  org.apache.maven.scm
  maven-mks-provider
  1.0 

   

 








Sharma, Jaikumar a écrit :

Hi Emmanuel, I am using the following pom.xml to connect to Mks-Provider :



4.0.0
com.mycompany.mytestscm 
testmksplugin

1.0
   
   


 
org.apache.maven.scm
maven-scm-plugin
1.0-beta-3


  

 
   


 
org.apache.maven.scm
maven-mks-provider
1.0 
   

 
   
scm:mks:"[EMAIL PROTECTED]@project"

 
   
   

   

   



-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 7:49 PM
To: scm-dev@maven.apache.org
Subject: Re: M2 : How to implement goals in SCM provider implementation ?


What is  ? Where do you put it?

Can you provide a sample scm url for mks? I guess 
scm:mks:"[EMAIL PROTECTED]" isn't one, right? If it is, I'm not sure 
it's correct because you don't have info about path to the project on a MKS


Server or locally or something else, Note that I don't know how mks 
works and mks command lines.


Emmanuel

Sharma, Jaikumar a écrit :
 > Fine, I have compiled it now by setting the packaging to 'jar', but
 > now
 > it is giving 'NullPointerExecption' after I try to pass the 
parameters to

 >
 > 
 >  
 >   scm:mks:"[EMAIL PROTECTED]"
 >  
 > 
 >
 > Parameter  username and password in the form as mentioned above, it
 > expects as a parameter of MksScmProvider classs'
 >
 > Please suggest!
 > 
 >

 >
 > -Original Message-
 > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
 > Sent: Thursday, June 01, 2006 6:38 PM
 > To: scm-dev@maven.apache.org
 > Subject: Re: M2 : How to implement goals in SCM provider
 > implementation ?
 >
 >
 > your provider must be a jar (default type) and not a plugin.
 >
 > Emmanuel
 >
 > Sharma, Jaikumar a écrit :
 >  > Hi Emmanuel,
 >  > Something unusual, which I am not aware of, while building the
 > plugin  > it  > says java 0 mojo descriptors. Could you please see,
 > where I am wrong ?  >
 >  > Regards, Jaikumar
 >  > 
--

 >  > -
 >  >
 >  > D:\Plugin_Development\maven-mks-provider>mvn clean install [INFO]
 >  > Scanning for projects... [INFO]
 >  >
 > 
 


 >
 >  >
 >  > [INFO] Building Unnamed -
 >  > org.apache.maven.scm:maven-mks-provider:maven-plugin:1.0
 >  > [INFO]task-segment: [clean, install]
 >  > [INFO]
 >  >
 > 
 


 >
 >  >
 >  > [INFO] [clean:clean]
 >  > [INFO] Deleting directory
 >  > D:\Plugin_Development\maven-mks-provider\target
 >  > [INFO] Deleting directory
 >  > D:\Plugin_Development\maven-mks-provider\target\classes
 >  > [INFO] Deleting directory
 >  > D:\Plugin_Development\maven-mks-provider\target\test-classes
 >  > [INFO] [plugin:descriptor]
 >  > [INFO] Using 2 extractors.
 >  > [INFO] Applying extractor for language: java
 >  > [INFO] Extractor for language: java found 0 mojo descriptors.
 > [INFO]  > Applying extractor for language: bsh [INFO] Extractor for
 > language: bsh  > found 0 mojo descriptors. [INFO]
 > [resources:resources] [INFO] Using  > default encoding to copy
 > filtered resources. [INFO] [compiler:compile]  > Compiling 6 source
 > files to  > D:\Plugin_Development\maven-mks-provider\target\classes
 >  >
 >  > [INFO] [resources:testResources]
 >  > [INFO] Using default encoding to copy filtered resources. [INFO]  >
 > [compiler:testCompile] [INFO] No sources to compile [INFO]  >
 > [surefire:test] [INFO] No tests to run. [INFO] [jar:jar] [INFO]
 > Building  > jar:  >
 > 
D:\Plugi

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

I guess you have define the scm url for MKS, right?

so, you can test it by adding this in your pom:

  scm:mks:mks_connection_parameters
  scm:mks:mks_connection_parameters


The first steap you can test is to add your provider as a dependency of maven-scm plugin and you'll 
can try scm:checkout, scm:update and other.


If all is ok, you'll need to test it with changelog plugin, release plugin and 
Continuum.

For changelog and release plugins, you'll need to add your provider as a dependency in the plugin or 
if you don't want to modify them for now, you can add it as a plugin dependency in your pom.


For continuum, put your provider in $CONTINUUM/apps/continuum/lib

Emmanuel

Sharma, Jaikumar a écrit :

Hi Emmanuel,
Initially, I have implemented the connect method other functionality in 
SCM provider for MKS plugin and it has been been built and installed in 
local repository. I want to know, how to configure this plugin in my pom 
so that I can test to connect to MKS provider, if it works or I have to 
change something ?


Thanks for your help!

Regards, Jaikumar

-Original Message-
From: Sharma, Jaikumar
Sent: Monday, May 29, 2006 2:12 PM
To: 'scm-dev@maven.apache.org'
Subject: RE: M2 : How to implement goals in SCM provider implementation ?


Thanks Emmanuel, that was the enlightment, I was expecting from you ;-)

-----Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 29, 2006 1:54 PM
To: scm-dev@maven.apache.org
Subject: Re: M2 : How to implement goals in SCM provider implementation ?


ok, it what I thought :-)

SCM providers don't know anythink about maven and goals. It's the role 
of scm plugin.


SCM providers implements SCM commands and scm plugin use them with 
Maven-SCM APIs.


Emmanuel

Sharma, Jaikumar a écrit :
 > Emmanuel, As per the documentation on
 > http://maven.apache.org/guides/plugin/guide-java-plugin-development.ht
 > ml
 > . A simple Mojo needs to have a '@goal', well I mentioned 'goals' --
 > mentioned term in a general way. Please see below some snippet from the
 > above mentioned web link.
 >
 > Well, I think I have not hurt you ;-)
 >
 > Rgds, Jaikumar
 >
 > -
 > package sample.plugin;
 >
 > import org.apache.maven.plugin.AbstractMojo;
 > import org.apache.maven.plugin.MojoExecutionException;
 >
 > /**
 >  * @goal sayhi
 >  * @description Says "Hi" to the user
 >  */
 > public class GreetingMojo extends AbstractMojo
 > {
 > public void execute() throws MojoExecutionException
 > {
 > getLog().info("Hello, world.");
 > }
 > }
 >
 > -
 >
 > -Original Message-
 > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
 > Sent: Monday, May 29, 2006 1:14 PM
 > To: scm-dev@maven.apache.org
 > Subject: Re: M2 : How to implement goals in SCM provider
 > implementation ?
 >
 >
 > what do you mean by goals?
 >
 > Emmanuel
 >
 > Sharma, Jaikumar a écrit :
 >  > I am working on SCM provider implementation for MKS. Could somebody
 > > throw some lights on goals implementation for SCM provider. I had a
 > look  > on SCM provider implementation for VSS, but could not find the
 > goals  > definition in any of the classes ?  >
 >  > Thanks!
 >  >
 >  > Jaikumar
 >

- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is 
privileged and confidential, and is intended only for the use of the 
addressee(s) named above and others who have been specifically 
authorized to receive it. If you are not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
message and/or attachments is strictly prohibited. The company accepts 
no liability for any damage caused by any virus transmitted by this 
email. Furthermore, the company does not warrant a proper and complete 
transmission of this information, nor does it accept liability for any 
delays. If you have received this message in error, please contact the 
sender and delete the message. Thank you.

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

ok, it what I thought :-)

SCM providers don't know anythink about maven and goals. It's the role of scm 
plugin.

SCM providers implements SCM commands and scm plugin use them with Maven-SCM 
APIs.

Emmanuel

Sharma, Jaikumar a écrit :
Emmanuel, As per the documentation on 
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html 
. A simple Mojo needs to have a '@goal', well I mentioned 'goals' -- 
mentioned term in a general way. Please see below some snippet from the 
above mentioned web link.


Well, I think I have not hurt you ;-)

Rgds, Jaikumar

-
package sample.plugin;

import org.apache.maven.plugin.AbstractMojo;
import org.apache.maven.plugin.MojoExecutionException;

/**
 * @goal sayhi
 * @description Says "Hi" to the user
 */
public class GreetingMojo extends AbstractMojo
{
public void execute() throws MojoExecutionException
{
getLog().info("Hello, world.");
}
}

-----

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 29, 2006 1:14 PM
To: scm-dev@maven.apache.org
Subject: Re: M2 : How to implement goals in SCM provider implementation ?


what do you mean by goals?

Emmanuel

Sharma, Jaikumar a écrit :
 > I am working on SCM provider implementation for MKS. Could somebody
 > throw some lights on goals implementation for SCM provider. I had a look
 > on SCM provider implementation for VSS, but could not find the goals
 > definition in any of the classes ?
 > 
 > Thanks!
 > 
 > Jaikumar

Re: M2 : How to implement goals in SCM provider implementation ?

[Emmanuel Venisse]

what do you mean by goals?

Emmanuel

Sharma, Jaikumar a écrit :
I am working on SCM provider implementation for MKS. Could somebody 
throw some lights on goals implementation for SCM provider. I had a look 
on SCM provider implementation for VSS, but could not find the goals 
definition in any of the classes ?
 
Thanks!
 
Jaikumar

Re: AW: Maven support for MKS Source Integrity?

[Emmanuel Venisse]

I don't know if someone works on it.

Emmanuel

Grandverger, Marijan a écrit :

Hi Emmanuel,
thanks for your help.
I will take a look at the things that have to be done.
Due to to my project schedules I won´t start immediatelly.
Do you know if somebody else is already working on a complete implementation of 
MKS support?
kind regards
Marijan 


-Ursprüngliche Nachricht-
Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 16. Mai 2006 2:21

An: scm-dev@maven.apache.org
Betreff: Re: Maven support for MKS Source Integrity?

Do you want to start the implementation of MKS provider?

1- Checkout Maven-SCM project 
(http://maven.apache.org/scm/source-repository.html)
2- Look at other providers so you'll know how they are implemented
3- Create a child project of maven-scm-providers project
4- Create a MksScmProvider that will extends 
org.apache.maven.scm.provider.AbstractScmProvider
5- Create a META-INF/plexus/components.xml file
6- Create a MksScmProviderRepository that will extends 
org.apache.maven.scm.provider.ScmProviderRepository or 
org.apache.maven.scm.provider.ScmProviderRepositoryWithHost
7- Implement MKS commands with unit tests
8- Implement TCK tests

A MKS changelog parser is already available in m1 changelog plugin, you can perhaps reuse it : 
http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk/changelog/src/main/org/apache/maven/mkslib/MksChangeLogParser.java


Let us know if you need more informations and the status of your implementation.

Emmanuel

Grandverger, Marijan a écrit :


Hi Folks

I found that statement in another maillist:

*> Re: Any progress on an MKS provider for Maven-SCM?*


Emmanuel Venisse
Thu, 27 Apr 2006 10:13:09 -0700

I don't have news on development of MKS provider.

if you use command line for MKS call, it will work fine with Maven-SCM.
Suscribe to Maven Scm developers list and we'll help you to start 
the  implementation.


Emmanuel




So I subscribed to this list and any help would be appreciated.

kind regards

*Marijan Grandverger*
Diplom-Ingenieur ETEC (TU)
Application Services Consultant
NCR GmbH Financial Solutions Division
Professional Services Central Europe
Center of Expertise Banken und Sparkassen Ulmer Straße 160
D-86156 Augsburg
Tel. +49 821 405 8352
Fax +49 821 405 7224
e-Mail [EMAIL PROTECTED]
Sitz der Gesellschaft: Augsburg
Registergericht: Amtsgericht Augsburg, Handelsregister-Nr.: HRB 11581
Geschäftsführung: Hermann Wimmer
*Vorsitzender des Aufsichtsrates: Werner Sülzer
Ust-ID: DE127492877
St.-Nr.: 9/103/116/10207
Informationen **___www.NCR.com_*
oft/Signatures/www.NCR.com>* Anfragen 
**___Mailto:[EMAIL PROTECTED]

<mailto:[EMAIL PROTECTED]>**

Re: Maven support for MKS Source Integrity?

[Emmanuel Venisse]

Do you want to start the implementation of MKS provider?

1- Checkout Maven-SCM project 
(http://maven.apache.org/scm/source-repository.html)
2- Look at other providers so you'll know how they are implemented
3- Create a child project of maven-scm-providers project
4- Create a MksScmProvider that will extends 
org.apache.maven.scm.provider.AbstractScmProvider
5- Create a META-INF/plexus/components.xml file
6- Create a MksScmProviderRepository that will extends 
org.apache.maven.scm.provider.ScmProviderRepository or 
org.apache.maven.scm.provider.ScmProviderRepositoryWithHost

7- Implement MKS commands with unit tests
8- Implement TCK tests

A MKS changelog parser is already available in m1 changelog plugin, you can perhaps reuse it : 
http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk/changelog/src/main/org/apache/maven/mkslib/MksChangeLogParser.java


Let us know if you need more informations and the status of your implementation.

Emmanuel

Grandverger, Marijan a écrit :

Hi Folks

I found that statement in another maillist:

*> Re: Any progress on an MKS provider for Maven-SCM?*


 Emmanuel Venisse
 Thu, 27 Apr 2006 10:13:09 -0700

 I don't have news on development of MKS provider.

 if you use command line for MKS call, it will work fine with Maven-SCM.
 Suscribe to Maven Scm developers list and we'll help you to start the
 implementation.

 Emmanuel




So I subscribed to this list and any help would be appreciated.

kind regards

*Marijan Grandverger*
Diplom-Ingenieur ETEC (TU)
Application Services Consultant
NCR GmbH Financial Solutions Division
Professional Services Central Europe
Center of Expertise Banken und Sparkassen
Ulmer Straße 160
D-86156 Augsburg
Tel. +49 821 405 8352
Fax +49 821 405 7224
e-Mail [EMAIL PROTECTED]
Sitz der Gesellschaft: Augsburg
Registergericht: Amtsgericht Augsburg, Handelsregister-Nr.: HRB 11581
Geschäftsführung: Hermann Wimmer
*Vorsitzender des Aufsichtsrates: Werner Sülzer
Ust-ID: DE127492877
St.-Nr.: 9/103/116/10207
Informationen **___www.NCR.com_* 
*  
Anfragen **___Mailto:[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>**

Re: Pure java SCM provider

[Emmanuel Venisse]

Carlos Sanchez a écrit :

What's the status of the javasvn provider? I've uploaded 1.1.0.beta of
tmate to ibiblio, I think we were waiting for this


I was waiting for it because it support file protocol necessary for TCK tests.
but 1.1.0.beta doesn't include all patches applied to 1.0.4, so we keep 1.0.4 
for now.



I'll be looking into how to commit files in svn to a folder that
doesn't exist (how to commit all the required folders), so I'll take a
look to what support tmate offers.


In future, I want to rewrite javasvn provider like cvsjava provider, so all command will be in 
svncommons and it will be more easy to maintain svn providers. tmate provide a class that take a 
command line as argument like command run in command line.


Emmanuel

Re: Site and plugin matrix updates

[Emmanuel Venisse]

Torbjorn Smorgrav a écrit :
1. Can I add Bazaar as an item under the Supported SCM's on the 
maven-scm-site?

(or are there any policies that I should know about?)


You can.



2. I would like to promote the bazaar provider from partially 
implemented to fully implemented in the scms-overview.

Any objections?


You can



3. In both cases, should the entries be sorted by importance or alphabetic?


We can sort them in an alphabetic order.



4. How can I edit the plugin matrix?
Bazaar has no concept of a tag (as of version 0.8), so I'd like to 
change the entry from "not implemented" to "doesn't exist".




Send me a mail with your username on confluence and I'll add you on writers.

Emmanuel

Re: Setting svn properties or how to avoid problems with line endings

[Emmanuel Venisse]

Carlos Sanchez a écrit :

So I have a problem when svn tries to commit text files with
inconsistent line endings (dos and unix), eg. the site generated docs
that we're trying to make consistent.

I have set auto props with the svn:native, svn complains when
commiting new files with the "inconsistent new line" message.


so you have dos and unix line endings in your file.



I've seen this code in the svn add command, but don't know how to use
it from the scm provider.

protected ScmResult executeAddCommand( ScmProviderRepository
repository, ScmFileSet fileSet, String message,
   boolean binary )
throws ScmException
{
// TODO: could do this with propset?
if ( binary )
{
throw new ScmException( "This provider does not yet
support binary files" );
}


If I don't find a solution, i'm gonna add the setProperty and
deleteProperty methods to the scm provider and check if my scm is
instance of it to remove the native property before commit.


I'm +1 for these two methods but it isn't a good workaround. It'd be better to fix your line endings 
before to commit your files and keep svn properties like they are defined in svn or with auto props.


Emmanuel

Re: Adding a directory recursively

[Emmanuel Venisse]

Brett Porter a écrit :

Emmanuel Venisse wrote:

I think it would be good to add this method and it's easy to do. For 
svn, we must check if :

- .svn directory exist in directory for subversion
- CVS directory exist in directory for CVS
- .bzr directory exist in directory for bazaar
- nothing to do for file provider
- don't know for clearcase, perforce and starteam



Is that really necessary? Shouldn't it error out if you try to add 
something that is already added?


If you don't have .svn, CVS... directories, they aren't already added.

Emmanuel

Re: Adding a directory recursively

[Emmanuel Venisse]

Carlos Sanchez a écrit :

I have created http://jira.codehaus.org/browse/SCM-188

For the scm wagon I'd need to add a whole directory to scm.

Right now the only solution is create a ScmFileSet, but none of the
current methods adds directories, i have to look for them and add in
order so the svn add works correctly.

It'd be a nice to have in the API an addDirectory or make the add
command add directories recursively (I don't know what's the use case
of the current behaviour)


Actual use case is to add all directories to add in scm in a scmFileSet.


eg. translated to svn it would call a svn add recursively, also
optimizing the current approach of calling lots of times to external
svn

WDYT?


I think it would be good to add this method and it's easy to do. For svn, we 
must check if :
- .svn directory exist in directory for subversion
- CVS directory exist in directory for CVS
- .bzr directory exist in directory for bazaar
- nothing to do for file provider
- don't know for clearcase, perforce and starteam

Emmanuel

Re: newbie question

[Emmanuel Venisse]

cvs isn't in your path, you must add it

Emmanuel

Narasimha Narahari a écrit :

Hi there,
I am trying to use the maven.scm plugins with CVS as my service 
provider. I have set the maven.scm.url but when I execute maven 
scm:update I get the following error.
 
Executing: cvs -f -q update -d

Working directory: C:\Projects\x
Provider message:
The cvs command failed.
Command output:
'cvs' is not recognized as an internal or external command, operable 
program or batch file.
 
Can someone tell me what I need to do fix this?
 
Thanks in advance
 
--Narasimha

Re: no commits on HEAD?

[Emmanuel Venisse]

I'll look at your patch and it will be perhaps included in next release.
I'll release a new beta before one week.

All developments are stopped until the release.

Emmanuel

Zsolt a écrit :

Hi,

I haven't seen any commit on http://svn.apache.org/repos/asf/maven/scm/trunk
for days.

Is no development going on?

Zsolt

Re: Java version policy

[Emmanuel Venisse]

It's defined in parent scm pom

Emmanuel

Brett Porter a écrit :

Torbjorn Smorgrav wrote:


Do we have a Java version policy?
I guess we are targeting 1.3?

Cheers
Torbjørn




1.4

Re: The best approach to extend ScmProvider

[Emmanuel Venisse]

It isn't a plugin to develop but a standard java library

1- you need to create a pom for your scm provider that extends 
maven-scm-providers like this :
  
maven-scm-providers
org.apache.maven.scm
1.0-beta-3-SNAPSHOT
  

2- create directory structure like others providers (we'll need to create an 
archetype for this)
3- create 2 classes that extends ScmProviderRepository and AbstractScmProvider
4- create src/main/resources/META-INF/plexus/components.xml like it's done in 
other providers
5- implement your commands and tests
6- implement the TCK that will validate your code

Emmanuel


Sharma, Jaikumar a écrit :
Kindly send me some getting started info about plugin development, never 
developed a plugin ealier. My approach would be to do it as fast as 
possible.


-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 2:35 PM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider


If you know well scm commands, a new scm provider can be implemented in 
2-3 days.


The minimal commands are add, checkin, checkout, changelog, remove, tag, 
update, status, and the TCK

implementation for validation of code.

Emmanuel

[EMAIL PROTECTED] a écrit :
 >
 >
 >
 >
 >
 > A task and a change set is almost the same thing.
 >
 > I also have plans to implement support for CM Synergy. However, as my
 > workload is pretty heavy at the moment, I will not be able to start
 > this until a couple of weeks from now.
 >
 > Does anyone knows approximately how long it takes to implement support
 > for a new SCM provider?
 >
 > If you start please let me know. I'll be happy to test your work if
 > you implement something.
 >
 > Regards
 >
 > Henrik
 >
 >
 >
 >
 >
 >
 >
 >
 > "Zsolt" <[EMAIL PROTECTED]>
 > 2006-04-05 07:24
 >
 > Please respond to
 > scm-dev@maven.apache.org
 >
 >
 > To
 > 
 > cc
 >
 > Subject
 > RE: The best approach to extend ScmProvider
 >
 >
 >
 >
 >
 >
 > I'm not sure what you exactly mean. CM-Synergy task is created BEFORE
 > you checkout.
 >
 > Zsolt
 >
 >
 >>-Original Message-
 >>From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]
 >>Sent: Tuesday, April 04, 2006 4:41 PM
 >>To: scm-dev@maven.apache.org
 >>Subject: RE: The best approach to extend ScmProvider
 >>
 >>Is it the same as a change set?
 >>A change set you can append to?
 >>
 >>Torbjorn
 >>
 >>
 >>
 >>-Original Message-
 >>From: Zsolt [mailto:[EMAIL PROTECTED]
 >>Sent: 4. april 2006 16:00
 >>To: scm-dev@maven.apache.org
 >>Subject: RE: The best approach to extend ScmProvider
 >>
 >>
 >>In Cm-Synergy (ClearCase has that also) you can checkin with a task
 >
 > created
 >
 >>and maintained by CM-Synergy, and I would like to browse the tasks
 >
 > created
 >
 >>in CM-Synergy.
 >>
 >>Zsolt
 >>
 >>
 >>>-Original Message-
 >>>From: Torbjorn Smorgrav
 >>>[mailto:[EMAIL PROTECTED]
 >>>Sent: Tuesday, April 04, 2006 9:31 AM
 >>>To: scm-dev@maven.apache.org
 >>>Subject: RE: The best approach to extend ScmProvider
 >>>
 >>>What is a task in this context?
 >>>
 >>>Torbjorn
 >>>
 >>>-Original Message-
 >>>From: Zsolt [mailto:[EMAIL PROTECTED]
 >>>Sent: 3. april 2006 19:31
 >>>To: scm-dev@maven.apache.org
 >>>Subject: RE: The best approach to extend ScmProvider
 >>>
 >>>
 >>>Thank you Carlos,
 >>>
 >>>I will also need a merthod: listTasks (or something like that) that
 >>
 >>returns
 >>
 >>>the tasks of the version control system.
 >>>
 >>>Can (should) I use commit to the repository?
 >>>
 >>>Zsolt
 >>>
 >>>
 >>>>-Original Message-
 >>>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 >
 > Carlos
 >
 >>>>Sanchez
 >>>>Sent: Monday, April 03, 2006 6:26 PM
 >>>>To: scm-dev@maven.apache.org
 >>>>Subject: Re: The best approach to extend ScmProvider
 >>>>
 >>>>I'd create a new list method. Providers that don't support a list
 >>>>operation can explain in the javadocs that they don't support it or
 >>>>that the operation is not efficient because it requires checkout.
 >>>>
 >>>>On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:
 >>>>
 >>>>>From the source code:
 >>>>>
 >>>>&

Re: The best approach to extend ScmProvider

[Emmanuel Venisse]

If you know well scm commands, a new scm provider can be implemented in 2-3 
days.

The minimal commands are add, checkin, checkout, changelog, remove, tag, update, status, and the TCK 
implementation for validation of code.


Emmanuel

[EMAIL PROTECTED] a écrit :






A task and a change set is almost the same thing.

I also have plans to implement support for CM Synergy. However, as my
workload is pretty heavy at the moment, I will not be able to start this
until a couple of weeks from now.

Does anyone knows approximately how long it takes to implement support for
a new SCM provider?

If you start please let me know. I'll be happy to test your work if you
implement something.

Regards

Henrik








"Zsolt" <[EMAIL PROTECTED]>
2006-04-05 07:24

Please respond to
scm-dev@maven.apache.org


To

cc

Subject
RE: The best approach to extend ScmProvider






I'm not sure what you exactly mean. CM-Synergy task is created BEFORE you
checkout.

Zsolt



-Original Message-
From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 4:41 PM
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider

Is it the same as a change set?
A change set you can append to?

Torbjorn



-Original Message-
From: Zsolt [mailto:[EMAIL PROTECTED]
Sent: 4. april 2006 16:00
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider


In Cm-Synergy (ClearCase has that also) you can checkin with a task


created


and maintained by CM-Synergy, and I would like to browse the tasks


created


in CM-Synergy.

Zsolt



-Original Message-
From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 9:31 AM
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider

What is a task in this context?

Torbjorn

-Original Message-
From: Zsolt [mailto:[EMAIL PROTECTED]
Sent: 3. april 2006 19:31
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider


Thank you Carlos,

I will also need a merthod: listTasks (or something like that) that


returns


the tasks of the version control system.

Can (should) I use commit to the repository?

Zsolt



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of


Carlos


Sanchez
Sent: Monday, April 03, 2006 6:26 PM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider

I'd create a new list method. Providers that don't support a list
operation can explain in the javadocs that they don't support it or
that the operation is not efficient because it requires checkout.

On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:


From the source code:

   public interface ScmProvider


I'm very under time pressure:

We have our own (limited scm support) and have to decide until Monday
whether we join to scm-maven (of course we would make all


modifications


available) or extend our scm implementation.

For us it is a must that we can get the list of files of a directory
directly from the repository and we must also support huge projects


(thus


an


entire checkout is not an option).

"svn list -v" does exactly what we need. For CVS we could execute:
  cvs checkout -l  DIRECTORY
into a temporary directory read the contents of CVS/* files (to get
revision, modification date etc.) and remove the temporary directors.

I don't know ClearCase but I guess it has also a list command.

If we join to scm-maven we will very probably implement CM-Synergy


because


one of our customers uses only Cm-Synergy it.

Please give me hints as soon as possible.

Zsolt



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of


Carlos


Sanchez
Sent: Saturday, April 01, 2006 10:24 AM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider

Not sure if ScmProvider is an interface but if it is we better add


the


method to it before 1.0 and implement in the providers throwing a


not


implemented exception, because if not we'll need to create another
interface to avoid breaking backwards compatibility in 1.x

On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:


Hi,

I need to extend ScmProvider to support a list method (like svn


list).


What


is the best approach to do that?

I need this functionally for CVS, svn and clearcase. Later we


might


even


add


CM Synergy support for maven scm.

What is the best approach?

Should I use the maven repository or create my own one?

I work with eclipse. How should I setup the project compile


everything?


Zsolt







--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
   -- The Princess Bride





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
   -- The Princess Bride







___


Thi

Re: The best approach to extend ScmProvider

[Emmanuel Venisse]

Torbjorn Smorgrav a écrit :

Can you checkin changes to the same task several times?

If no, then this should map well to a change set (except the task creation).
If yes, then I like :)

This may be related:
http://jira.codehaus.org/browse/SCM-38

A follow-up question to all:
Is there a plan or vision on how scm-maven should evolve?
Should it become a super-set of all SCM commands and features available?


We want to implement all SCM commands/features if possible. For the moment, we implemented all 
commands/fetures required by continuum and plugins but i'd want to add more.



What about non-core features like access control, bugtracker integration and
audit systems?


We have an issue for this (SCM-38)

Emmanuel


Regards
Torbjorn

-Original Message-
From: Zsolt [mailto:[EMAIL PROTECTED]
Sent: 5. april 2006 07:25
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider


I'm not sure what you exactly mean. CM-Synergy task is created BEFORE you
checkout.

Zsolt



-Original Message-
From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 4:41 PM
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider

Is it the same as a change set?
A change set you can append to?

Torbjorn



-Original Message-
From: Zsolt [mailto:[EMAIL PROTECTED]
Sent: 4. april 2006 16:00
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider


In Cm-Synergy (ClearCase has that also) you can checkin with a task created
and maintained by CM-Synergy, and I would like to browse the tasks created
in CM-Synergy.

Zsolt



-Original Message-
From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 9:31 AM
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider

What is a task in this context?

Torbjorn

-Original Message-
From: Zsolt [mailto:[EMAIL PROTECTED]
Sent: 3. april 2006 19:31
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider


Thank you Carlos,

I will also need a merthod: listTasks (or something like that) that


returns


the tasks of the version control system.

Can (should) I use commit to the repository?

Zsolt



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Monday, April 03, 2006 6:26 PM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider

I'd create a new list method. Providers that don't support a list
operation can explain in the javadocs that they don't support it or
that the operation is not efficient because it requires checkout.

On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:


From the source code:

   public interface ScmProvider


I'm very under time pressure:

We have our own (limited scm support) and have to decide until Monday
whether we join to scm-maven (of course we would make all modifications
available) or extend our scm implementation.

For us it is a must that we can get the list of files of a directory
directly from the repository and we must also support huge projects


(thus


an


entire checkout is not an option).

"svn list -v" does exactly what we need. For CVS we could execute:
  cvs checkout -l  DIRECTORY
into a temporary directory read the contents of CVS/* files (to get
revision, modification date etc.) and remove the temporary directors.

I don't know ClearCase but I guess it has also a list command.

If we join to scm-maven we will very probably implement CM-Synergy


because


one of our customers uses only Cm-Synergy it.

Please give me hints as soon as possible.

Zsolt



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of


Carlos


Sanchez
Sent: Saturday, April 01, 2006 10:24 AM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider

Not sure if ScmProvider is an interface but if it is we better add the
method to it before 1.0 and implement in the providers throwing a not
implemented exception, because if not we'll need to create another
interface to avoid breaking backwards compatibility in 1.x

On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:


Hi,

I need to extend ScmProvider to support a list method (like svn


list).


What


is the best approach to do that?

I need this functionally for CVS, svn and clearcase. Later we might


even


add


CM Synergy support for maven scm.

What is the best approach?

Should I use the maven repository or create my own one?

I work with eclipse. How should I setup the project compile


everything?


Zsolt







--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
   -- The Princess Bride





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
   -- The Princess Bride

Re: The best approach to extend ScmProvider

[Emmanuel Venisse]

What is the role of a task?

Zsolt a écrit :

I'm not sure what you exactly mean. CM-Synergy task is created BEFORE you
checkout.

Zsolt



-Original Message-
From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 4:41 PM
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider

Is it the same as a change set?
A change set you can append to?

Torbjorn



-Original Message-
From: Zsolt [mailto:[EMAIL PROTECTED]
Sent: 4. april 2006 16:00
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider


In Cm-Synergy (ClearCase has that also) you can checkin with a task created
and maintained by CM-Synergy, and I would like to browse the tasks created
in CM-Synergy.

Zsolt



-Original Message-
From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 9:31 AM
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider

What is a task in this context?

Torbjorn

-Original Message-
From: Zsolt [mailto:[EMAIL PROTECTED]
Sent: 3. april 2006 19:31
To: scm-dev@maven.apache.org
Subject: RE: The best approach to extend ScmProvider


Thank you Carlos,

I will also need a merthod: listTasks (or something like that) that


returns


the tasks of the version control system.

Can (should) I use commit to the repository?

Zsolt



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Monday, April 03, 2006 6:26 PM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider

I'd create a new list method. Providers that don't support a list
operation can explain in the javadocs that they don't support it or
that the operation is not efficient because it requires checkout.

On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:


From the source code:

   public interface ScmProvider


I'm very under time pressure:

We have our own (limited scm support) and have to decide until Monday
whether we join to scm-maven (of course we would make all modifications
available) or extend our scm implementation.

For us it is a must that we can get the list of files of a directory
directly from the repository and we must also support huge projects


(thus


an


entire checkout is not an option).

"svn list -v" does exactly what we need. For CVS we could execute:
  cvs checkout -l  DIRECTORY
into a temporary directory read the contents of CVS/* files (to get
revision, modification date etc.) and remove the temporary directors.

I don't know ClearCase but I guess it has also a list command.

If we join to scm-maven we will very probably implement CM-Synergy


because


one of our customers uses only Cm-Synergy it.

Please give me hints as soon as possible.

Zsolt



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of


Carlos


Sanchez
Sent: Saturday, April 01, 2006 10:24 AM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider

Not sure if ScmProvider is an interface but if it is we better add the
method to it before 1.0 and implement in the providers throwing a not
implemented exception, because if not we'll need to create another
interface to avoid breaking backwards compatibility in 1.x

On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:


Hi,

I need to extend ScmProvider to support a list method (like svn


list).


What


is the best approach to do that?

I need this functionally for CVS, svn and clearcase. Later we might


even


add


CM Synergy support for maven scm.

What is the best approach?

Should I use the maven repository or create my own one?

I work with eclipse. How should I setup the project compile


everything?


Zsolt







--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
   -- The Princess Bride





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
   -- The Princess Bride

Re: ClearCase SCM provider

[Emmanuel Venisse]

I think i'll release it before two weeks.

Emmanuel

Igor Czechowski a écrit :

Emmanuel,

Thanks. Do you know when it will be released ?

Igor

On 4/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:


This problem is already fixed.

If you want to try the latest snapshot of maven-scm, add this in your pom :

  

  
false
  
  apache.snapshots
  Apache Development Repository
  http://cvs.apache.org/maven-snapshot-repository

  

The snapshot version of Maven-scm is 1.0-beta-3-SNAPSHOT that will be in few 
days 1.0

Emmanuel

Igor Czechowski a écrit :


I have a problem executing clearcase scm provider.

When I run the goal scm:update the snapshot view is being updated but
maven fails the build when there are any updates pulled out form the
clearcase. Regardless of build result (success or error) the view is
fresh with all the view files and updates.

Turning the stack trace showed (just part for clarity)

   ... 18 more
Caused by: java.lang.NullPointerException
   at 
org.apache.maven.scm.provider.clearcase.command.changelog.ClearCaseChangeLogCommand.executeChangeLogCommand(ClearCaseChangeLogCommand.java:51)
   at 
org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:63)
   at 
org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:60)
   at 
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55)
   ... 21 more


My system is:
Linux RedHat AS 3.5
ClearCase version 2003.06.00
Maven 2.0.2

If anyone can tell me how to get sources and debug the problem it
would appreciate. I ask since I'm new to maven and have no idea how to
setup the development environment for maven scm plugins.

Thanks in advance
 Igor

Re: ClearCase SCM provider

[Emmanuel Venisse]

This problem is already fixed.

If you want to try the latest snapshot of maven-scm, add this in your pom :

  

  
false
  
  apache.snapshots
  Apache Development Repository
  http://cvs.apache.org/maven-snapshot-repository

  

The snapshot version of Maven-scm is 1.0-beta-3-SNAPSHOT that will be in few 
days 1.0

Emmanuel

Igor Czechowski a écrit :

I have a problem executing clearcase scm provider.

When I run the goal scm:update the snapshot view is being updated but
maven fails the build when there are any updates pulled out form the
clearcase. Regardless of build result (success or error) the view is
fresh with all the view files and updates.

Turning the stack trace showed (just part for clarity)

... 18 more
Caused by: java.lang.NullPointerException
at 
org.apache.maven.scm.provider.clearcase.command.changelog.ClearCaseChangeLogCommand.executeChangeLogCommand(ClearCaseChangeLogCommand.java:51)
at 
org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:63)
at 
org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:60)
at 
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55)
... 21 more


My system is:
Linux RedHat AS 3.5
ClearCase version 2003.06.00
Maven 2.0.2

If anyone can tell me how to get sources and debug the problem it
would appreciate. I ask since I'm new to maven and have no idea how to
setup the development environment for maven scm plugins.

Thanks in advance
  Igor

Welcome to Torbjørn

[Emmanuel Venisse]

Everyone, please welcome Torbjørn as our newest Maven-SCM committer.

Torbjørn: you may already be familiar with them, but here are some
resources to get you started:

* How to log in, commit, etc:
http://www.apache.org/dev/new-committers-guide.html

* Information on Apache and how it works, and how we all play nice
together: http://www.apache.org/foundation/how-it-works.html

* How voting works: http://www.apache.org/foundation/voting.html

* For technical resources: http://www.apache.org/dev/committers.html

If you've got any questions, feel free to ask, and I look forward to
working with you!

Emmanuel

Re: PVCS and Maven

[Emmanuel Venisse]

Thank you.

Emmanuel

Kevin Parker a écrit :

Dear Sir,

Thank you. Once we have approval to donate the code we will follow the process 
you suggested.

Sincerely,

Kevin

Kevin Parker
Vice President Market Development
Serena Software Inc. 
2755 Campus Drive, 3rd Floor, San Mateo, CA 94403-2538
www.serena.com 
tel	650-522-6635

fax 650-522-6835
cell650-224-1691
email   [EMAIL PROTECTED]


-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 28, 2006 11:24

To: scm-dev@maven.apache.org
Cc: David Parker; Francis Long; Kevin Parker
Subject: Re: PVCS and Maven

Hi,

Do you have implemented maven-scm interfaces for PVCS?
You can create an issue (http://jira.codehaus.org/browse/SCM) and attach your 
code to it.
You can subscribe too scm developers list (little traffic) so you'll can help users that want to use 
your provider.


If you have any questions about maven-scm, don't hesitate to send a mail to 
developers list.

Emmanuel

Kevin Parker a écrit :


Dear Maven's,

We have recently developed a Maven interface for our PVCS product and 
are interested in the process for potentially donating this to the 
project. Could someone contact me and let me know what the process would be.


Sincerely,

*//**//**//**/Kevin
/**//**//**/
/Kevin Parker
*///Vice President Market Development
/***Serena Software Inc*.
2755 Campus Drive, 3^rd Floor, San Mateo, CA 94403-2538
***www.serena.com
*tel 650-522-6635
fax 650-522-6835
cell650-224-1691
email   [EMAIL PROTECTED]



**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. Any unauthorized review, use, disclosure or distribution 
is prohibited. If you are not the intended recipient, please contact the 
sender by reply e-mail and destroy all copies of the original message.

Re: PVCS and Maven

[Emmanuel Venisse]

Hi,

Do you have implemented maven-scm interfaces for PVCS?
You can create an issue (http://jira.codehaus.org/browse/SCM) and attach your 
code to it.
You can subscribe too scm developers list (little traffic) so you'll can help users that want to use 
your provider.


If you have any questions about maven-scm, don't hesitate to send a mail to 
developers list.

Emmanuel

Kevin Parker a écrit :

Dear Maven’s,

We have recently developed a Maven interface for our PVCS product and 
are interested in the process for potentially donating this to the 
project. Could someone contact me and let me know what the process would be.


Sincerely,

*//**//**//**/Kevin
/**//**//**/
/Kevin Parker
*///Vice President Market Development
/***Serena Software Inc*.
2755 Campus Drive, 3^rd Floor, San Mateo, CA 94403-2538
***www.serena.com
*tel 650-522-6635
fax 650-522-6835
cell650-224-1691
email   [EMAIL PROTECTED]



**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. Any unauthorized review, use, disclosure or distribution 
is prohibited. If you are not the intended recipient, please contact the 
sender by reply e-mail and destroy all copies of the original message.

Re: Implementing support for CM Synergy?

[Emmanuel Venisse]

[EMAIL PROTECTED] a écrit :


Hi and thanks for the info!

I'm new to both maven and maven-scm so bear with me...
I have checked out maven-scm from svn.

What would be the best solution to import this into Eclipse?


mvn eclipse:eclipse

Should I have each module (maven-scm-api, maven-scm-providers) as 
separate Eclipse projects?


yes, all eclipse projects will be generated by eclipse mojo


Eclipse has a different directory standard.


yes, with eclipse you can't add pom projects but only jar projects, so you'll 
need to remove them



I'm sorry if these are simple questions, but the documentation of doing 
this on the web site is quite thin.


http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html
http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html

Emmanuel



Regards

Henrik







*"Torbjorn Smorgrav" <[EMAIL PROTECTED]>*
2006-03-22 21:54
Please respond to
scm-dev@maven.apache.org



To
scm-dev@maven.apache.org
cc

Subject
Re: Implementing support for CM Synergy?








Hi Henrik!

 > I posted this yesterday as well. But I haven't got any response yet. So
 > I'll ask again.
 > I want to implement support for CM Synergy.

I'll be happy to help you.
I recently added the Bazaar provider (yet to be released) so I can
at least guide you through the same path that I took.

 > What baseline should I use?

Use the current development baseline.
http://maven.apache.org/scm/source-repository.html

 > What do I need to check out?

Start with:

maven-scm-api/ 


maven-scm-test/


And a reference provider eg. maven-scm-provider-bazaar/

Perhapes choose one that is most similar to the CM Synergy

 > What class or interfaced do I need to implement?

What I did was change the implementation of an existing provider.
That way I got fast results and I learned the API one step at the time.

Basically what you need to implements is an (Abstract)ScmProvider and
its commands.

 > How can I test my provider?

1. Run unit tests from your IDE
The test classes in maven-scm-test was really helpfull to me. Try to
include a tck test
as soon as possible. See how the tck tests are implemented in the
reference provider (its a no brainer :).

It can be a bit tricky to setup your IDE to pickup your current
modifications and not the installed
version of the provider. Let me know it this becomes a problem.

2. Build and install the provider and test it with eg. "mvn
scm:checkout" on a project where
you have defined a scm url in the pom.xml.

This was probably a too short answer. But if you post your questions
as they come,
I'll do my best to help you. And in the end I like to make a mave-scm
howto webpage
with all of this.

Good luck,
Torbjørn
[attachment "C.htm" deleted by Henrik Jonsson/SE/Transport/Bombardier]




___ 

This e-mail communication (and any attachment/s) may contain 
confidential or privileged information and is intended only for the 
individual(s) or entity named above and to others who have been 
specifically authorized to receive it. If you are not the intended 
recipient, please do not read, copy, use or disclose the contents of 
this communication to others. Please notify the sender that you have 
received this e-mail in error by reply e-mail, and delete the e-mail 
subsequently.

Thank you.
_ 



Ce message (ainsi que le(s) fichier/s), transmis par courriel, peut 
contenir des renseignements confidentiels ou protégés et est destiné à 
l’usage exclusif du destinataire ci-dessus. Toute autre personne est par 
les présentes avisée qu’il est strictement interdit de le diffuser, le 
distribuer ou le reproduire. Si vous l’avez reçu par inadvertance, 
veuillez nous en aviser et détruire ce message.

Merci.
_ 

Re: git repository provider

[Emmanuel Venisse]

is it possible to run git locally? in this case, you can use the TCK and create the repository in 
target directory with initRepo method. You can look at other providers like bazaar that do it.


Emmanuel

Dominik Winter a écrit :
2006/3/23, Emmanuel Venisse <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>>:


What is a git archive?


The repository directory.

Re: git repository provider

[Emmanuel Venisse]

What is a git archive?

Emmanuel

Dominik Winter a écrit :

Hi,

it seems that nobody works on a git provider so far. So I started to
implement one. Creating an archive ("repository"), adding files,
checking out and committing changes work already.

I use git itself as the SCM, of course. But I have no public place to
host the git archive, yet.
Any suggestions?

Regards,
0x7f0c