Hi,

2008/8/28 Brett Porter <[EMAIL PROTECTED]>:
> Can't remember if I said it before, but I think this is a good idea.
> I think Olivier was asking you to create JIRA issues for the functionality
> so we make sure to track it for 1.2.
> I haven't reviewed the code yet, but one thought that occurred to me is
> whether it is best to have the API have explicit "remote" commands (rlist,
> etc), or is it a mode of operation passed to the existing commands (list,
> told to act remotely)? The first (which you've done) seems simpler to me.
I prefer new remote commands too.
> There was also talk of a 1.1.1 so we might need to branch for that too?

IMHO we can create a 1.1.x branch and apply your patch on the trunk ?

> Cheers,
> Brett
> On 28/08/2008, at 8:06 AM, Alexey Kakunin wrote:
>
> OK, It was already discussed some time ago in this list.
> So, currently, maven-scm is used in two major projects: maven itself and
> continuum. (Probably some other but I do not have such info).
> It is mostly designed to do the things, required by these project.
>
> We proposed to add commands to work with remote repositories (not with local
> copy) - 4 commands:
> 1. rlist - to get list of files in remote repository
> 2. rlog - get history of remote file/folder
> 3. rinfo - get information about remote file
> 4. rcat - get contents of remote file
>
> We already implemented such commands for svnjava & cvs provider, and
> currently starting to work on mercurial

As you know due to license issue we can't use svnjava. Can you provide
a patch with svnexe ?

> We are using these commands for source-browser implementation in emforge
> (currently http://www.emforge.org/browser used our extended version of
> maven-scm)
>
> For us - usage of maven-scm give the good infrastructure. Maven-scm can
> receive extra-functionality from our job and example of another tool, used
> maven-scm.
>
> Currently all our changes are stored in our repository:
> http://svn.emforge.org/svn/emforge/maven-scm/
> So, it looks like a fork - but, I do not like forks, and, will be happy to
> include somehow & sometime our changes into core maven-scm, so, we will
> avoid synhronization problems, and other user will be able to use these
> commands.
>

big +1 on this approach.

>
> 2008/8/28 Olivier Lamy <[EMAIL PROTECTED]>
>>
>> Hi,
>> Can you explain in a issue what will be this changes ?
>> Thanks,
>> --
>> Olivier
>>
>> 2008/8/27 Alexey Kakunin <[EMAIL PROTECTED]>:
>> > +1 (even I have no voice for voiting)
>> > We have couple of changes, related to allow maven-scm better work with
>> > remote repositories (as example of using such extensions - source
>> > browser in
>> > http://www.emforge.org)
>> >
>> > We are not able to incorporate our changes now - since project near to
>> > release and it is not make sense to include big changes. Releasing of
>> > 1.1
>> > will allow us to start move our changes into 1.2 trunk
>> >
>> >
>> >
>> > 2008/8/27 Dan Fabulich <[EMAIL PROTECTED]>
>> >>
>> >> +1, new settings work for me!
>> >>
>> >> 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 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]
>> >>>
>> >>>
>> >>
>> >
>> >
>> >
>> > --
>> > With best regards,
>> > Alexey Kakunin
>> >
>
>
>
> --
> With best regards,
> Alexey Kakunin
>
> --
> Brett Porter
> [EMAIL PROTECTED]
> http://blogs.exist.com/bporter/
>

Reply via email to