Re: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/ maven-scm-pro

[Mark Struberg]

hmm funny, now the svnexe tests fail^^ 

w :(

Olivier, any idea whats going on their? Is it the hanging perforce provider 
which causes this problems?

LieGrue,
strub

--- On Mon, 2/7/11, Mark Struberg  wrote:

> From: Mark Struberg 
> Subject: Re: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: 
> maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/
>  maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java
> To: scm-dev@maven.apache.org
> Date: Monday, February 7, 2011, 2:46 PM
> No, I use git native if I'm on git
> projects but for maven-scm I only use svn 1.6.15 via the
> commandline on Fedora 14. 
> 
> I've now checked the sources and maybe the problem is your
> use of a 'standard' git repo, whereas I used a 'bare' repo
> because this doesn't get affected by gits internal parent
> logic. In other words: the ".git" directory in
> src/test/repository/git/info/ might cause some troubles if
> you use  git-svn or git native.
> 
> LieGrue,
> strub
> 
> --- On Mon, 2/7/11, Olivier Lamy 
> wrote:
> 
> > From: Olivier Lamy 
> > Subject: Re: svn commit: r1067545 - in
> /maven/scm/trunk/maven-scm-providers:
> maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/
> maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java
> > To: scm-dev@maven.apache.org
> > Date: Monday, February 7, 2011, 1:51 PM
> > Hello,
> > Yes I know (I wanted to revert but didn't have enough
> time
> > this morning).
> > That's weird in fact because it fail here.
> > Are you using  git svn for working with maven scm ?
> > 
> > 
> > 2011/2/7 Mark Struberg :
> > > Hi olivier!
> > >
> > > what was the reason for the following change?
> > >
> > > -        assertEquals(
> > "cd3c0dfacb65955e6fbb35c56cc5b1bf8ce4f767",
> > result.getInfoItems().get( 0 ).getRevision() );
> > > +        assertEquals(
> > "d42193018c2fc462a103ef6440cd162d73595c53",
> > result.getInfoItems().get( 0 ).getRevision() );
> > >         //
> > >
> > > This broke the git-tck on my system.
> > > Think we should revert that part.
> > >
> > > txs and LieGrue,
> > > strub
> > >
> > > --- On Sat, 2/5/11, ol...@apache.org
> > 
> > wrote:
> > >
> > >> From: ol...@apache.org
> > 
> > >> Subject: svn commit: r1067545 - in
> > /maven/scm/trunk/maven-scm-providers:
> >
> maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/
> >
> maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/a...
> > >> To: scm-comm...@maven.apache.org
> > >> Date: Saturday, February 5, 2011, 10:39 PM
> > >> Author: olamy
> > >> Date: Sat Feb  5 22:39:49 2011
> > >> New Revision: 1067545
> > >>
> > >> URL: http://svn.apache.org/viewvc?rev=1067545&view=rev
> > >> Log:
> > >> [SCM-555] paths reported in svn-exe checkout
> do
> > not match
> > >> update command (always reports absolute).
> > >> Submitted by Andrew Williams.
> > >>
> > >> Modified:
> > >>
> > >>
> >
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> > >>
> > >>
> >
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
> > >>
> > >>
> >
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutCommand.java
> > >>
> > >>
> >
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutConsumer.java
> > >>
> > >> Modified:
> > >>
> >
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> > >> URL: 
> > >> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/ma

Re: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/ maven-scm-pro

[Mark Struberg]

No, I use git native if I'm on git projects but for maven-scm I only use svn 
1.6.15 via the commandline on Fedora 14. 

I've now checked the sources and maybe the problem is your use of a 'standard' 
git repo, whereas I used a 'bare' repo because this doesn't get affected by 
gits internal parent logic. In other words: the ".git" directory in 
src/test/repository/git/info/ might cause some troubles if you use  git-svn or 
git native.

LieGrue,
strub

--- On Mon, 2/7/11, Olivier Lamy  wrote:

> From: Olivier Lamy 
> Subject: Re: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: 
> maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/
>  maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java
> To: scm-dev@maven.apache.org
> Date: Monday, February 7, 2011, 1:51 PM
> Hello,
> Yes I know (I wanted to revert but didn't have enough time
> this morning).
> That's weird in fact because it fail here.
> Are you using  git svn for working with maven scm ?
> 
> 
> 2011/2/7 Mark Struberg :
> > Hi olivier!
> >
> > what was the reason for the following change?
> >
> > -        assertEquals(
> "cd3c0dfacb65955e6fbb35c56cc5b1bf8ce4f767",
> result.getInfoItems().get( 0 ).getRevision() );
> > +        assertEquals(
> "d42193018c2fc462a103ef6440cd162d73595c53",
> result.getInfoItems().get( 0 ).getRevision() );
> >         //
> >
> > This broke the git-tck on my system.
> > Think we should revert that part.
> >
> > txs and LieGrue,
> > strub
> >
> > --- On Sat, 2/5/11, ol...@apache.org
> 
> wrote:
> >
> >> From: ol...@apache.org
> 
> >> Subject: svn commit: r1067545 - in
> /maven/scm/trunk/maven-scm-providers:
> maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/
> maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/a...
> >> To: scm-comm...@maven.apache.org
> >> Date: Saturday, February 5, 2011, 10:39 PM
> >> Author: olamy
> >> Date: Sat Feb  5 22:39:49 2011
> >> New Revision: 1067545
> >>
> >> URL: http://svn.apache.org/viewvc?rev=1067545&view=rev
> >> Log:
> >> [SCM-555] paths reported in svn-exe checkout do
> not match
> >> update command (always reports absolute).
> >> Submitted by Andrew Williams.
> >>
> >> Modified:
> >>
> >>
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> >>
> >>
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
> >>
> >>
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutCommand.java
> >>
> >>
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutConsumer.java
> >>
> >> Modified:
> >>
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> >> URL: 
> >> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java?rev=1067545&r1=1067544&r2=1067545&view=diff
> >>
> ==
> >> ---
> >>
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> >> (original)
> >> +++
> >>
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> >> Sat Feb  5 22:39:49 2011
> >> @@ -45,7 +45,7 @@ public class
> GitInfoCommandTckTest
> >>          assertNotNull(
> >> repository );
> >>          InfoScmResult result
> >> = provider.info( repository, new ScmFileSet(
> >> getRepositoryRoot() ), new CommandParameters() );

Re: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/ maven-scm-pro

[Olivier Lamy]

Hello,
Yes I know (I wanted to revert but didn't have enough time this morning).
That's weird in fact because it fail here.
Are you using  git svn for working with maven scm ?


2011/2/7 Mark Struberg :
> Hi olivier!
>
> what was the reason for the following change?
>
> -        assertEquals( "cd3c0dfacb65955e6fbb35c56cc5b1bf8ce4f767", 
> result.getInfoItems().get( 0 ).getRevision() );
> +        assertEquals( "d42193018c2fc462a103ef6440cd162d73595c53", 
> result.getInfoItems().get( 0 ).getRevision() );
>         //
>
> This broke the git-tck on my system.
> Think we should revert that part.
>
> txs and LieGrue,
> strub
>
> --- On Sat, 2/5/11, ol...@apache.org  wrote:
>
>> From: ol...@apache.org 
>> Subject: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: 
>> maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/
>>  maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/a...
>> To: scm-comm...@maven.apache.org
>> Date: Saturday, February 5, 2011, 10:39 PM
>> Author: olamy
>> Date: Sat Feb  5 22:39:49 2011
>> New Revision: 1067545
>>
>> URL: http://svn.apache.org/viewvc?rev=1067545&view=rev
>> Log:
>> [SCM-555] paths reported in svn-exe checkout do not match
>> update command (always reports absolute).
>> Submitted by Andrew Williams.
>>
>> Modified:
>>
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
>>
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
>>
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutCommand.java
>>
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutConsumer.java
>>
>> Modified:
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
>> URL: 
>> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java?rev=1067545&r1=1067544&r2=1067545&view=diff
>> ==
>> ---
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
>> (original)
>> +++
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
>> Sat Feb  5 22:39:49 2011
>> @@ -45,7 +45,7 @@ public class GitInfoCommandTckTest
>>          assertNotNull(
>> repository );
>>          InfoScmResult result
>> = provider.info( repository, new ScmFileSet(
>> getRepositoryRoot() ), new CommandParameters() );
>>          assertNotNull(
>> result );
>> -        assertEquals(
>> "cd3c0dfacb65955e6fbb35c56cc5b1bf8ce4f767",
>> result.getInfoItems().get( 0 ).getRevision() );
>> +        assertEquals(
>> "d42193018c2fc462a103ef6440cd162d73595c53",
>> result.getInfoItems().get( 0 ).getRevision() );
>>          //
>>      }
>>
>>
>> Modified:
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
>> URL: 
>> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java?rev=1067545&r1=1067544&r2=1067545&view=diff
>> ==
>> ---
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
>> (original)
>> +++
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
>> Sat Feb  5 22:39:49 2011
>> @@ -113,4 +113,9 @@ public abstract class
>> AbstractFileChecki
>>          return revision;
>>      }
>>
>> +    public File getWorkingDirectory()
>> +    {
>> +        return workingDirectory;
>> +    }
>> +
>>  }
>>
>> Modified:
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/c

Re: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/ maven-scm-pro

[Mark Struberg]

Hi olivier!

what was the reason for the following change?

-assertEquals( "cd3c0dfacb65955e6fbb35c56cc5b1bf8ce4f767", 
result.getInfoItems().get( 0 ).getRevision() );
+assertEquals( "d42193018c2fc462a103ef6440cd162d73595c53", 
result.getInfoItems().get( 0 ).getRevision() );
 // 

This broke the git-tck on my system.
Think we should revert that part.

txs and LieGrue,
strub

--- On Sat, 2/5/11, ol...@apache.org  wrote:

> From: ol...@apache.org 
> Subject: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: 
> maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/
>  maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/a...
> To: scm-comm...@maven.apache.org
> Date: Saturday, February 5, 2011, 10:39 PM
> Author: olamy
> Date: Sat Feb  5 22:39:49 2011
> New Revision: 1067545
> 
> URL: http://svn.apache.org/viewvc?rev=1067545&view=rev
> Log:
> [SCM-555] paths reported in svn-exe checkout do not match
> update command (always reports absolute).
> Submitted by Andrew Williams.
> 
> Modified:
>    
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
>    
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
>    
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutCommand.java
>    
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutConsumer.java
> 
> Modified:
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> URL: 
> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java?rev=1067545&r1=1067544&r2=1067545&view=diff
> ==
> ---
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> (original)
> +++
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/GitInfoCommandTckTest.java
> Sat Feb  5 22:39:49 2011
> @@ -45,7 +45,7 @@ public class GitInfoCommandTckTest
>          assertNotNull(
> repository );
>          InfoScmResult result
> = provider.info( repository, new ScmFileSet(
> getRepositoryRoot() ), new CommandParameters() );
>          assertNotNull(
> result );
> -        assertEquals(
> "cd3c0dfacb65955e6fbb35c56cc5b1bf8ce4f767",
> result.getInfoItems().get( 0 ).getRevision() );
> +        assertEquals(
> "d42193018c2fc462a103ef6440cd162d73595c53",
> result.getInfoItems().get( 0 ).getRevision() );
>          // 
>      }
>      
> 
> Modified:
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
> URL: 
> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java?rev=1067545&r1=1067544&r2=1067545&view=diff
> ==
> ---
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
> (original)
> +++
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/AbstractFileCheckingConsumer.java
> Sat Feb  5 22:39:49 2011
> @@ -113,4 +113,9 @@ public abstract class
> AbstractFileChecki
>          return revision;
>      }
>  
> +    public File getWorkingDirectory()
> +    {
> +        return workingDirectory;
> +    }
> +
>  }
> 
> Modified:
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutCommand.java
> URL: 
> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkout/SvnCheckOutCommand.java?rev=1067545&r1=10675

Re: Any plans to fix/update maven-scm-provider-hg ?

[Lord.Quackstar]

Got it working today. Thanks for the update.

Some quick things
-Why does this not work when you put it in the  area?
-Will this work with other plugins that deploy like a source deploy?
-Shouldn't it url encode the username and password? My username has a @ symbol 
in it which breaks the url and the initial clone

Thanks again for the update,
Leon






From: Olivier Lamy 
To: scm-dev@maven.apache.org
Sent: Thu, January 20, 2011 5:32:39 PM
Subject: Re: Any plans to fix/update maven-scm-provider-hg ?

Hello,
Fixed in scm trunk you can use (note where the dependency is declared)


  

  org.apache.maven.plugins
  maven-site-plugin
  3.0-beta-3
  

  org.apache.maven.scm
  maven-scm-api
  1.5-SNAPSHOT


  org.apache.maven.scm
  maven-scm-provider-hg
  1.5-SNAPSHOT

  

  


And use this repo (until scm 1.5 is released ) :
https://repository.apache.org/content/groups/snapshots-group/

let us know if you still have issues.

2011/1/20 Lord.Quackstar :
> Sorry for the delay, I sent this with another email address that wasn't
> subscribed.
>
> I have this in my POM
> 
> 
> 
> org.apache.maven.wagon
> wagon-webdav
> 1.0-beta-2
> 
> 
> org.apache.maven.scm
> maven-scm-provider-hg
> 1.4
> 
> 
> org.apache.maven.wagon
> wagon-scm
> 1.0-beta-7
> 
> 
>..
> 
>
> 
> 
> 
> 
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.7
> 
> Leon Blakey
> ${project.version}
> 
> http://download.oracle.com/javase/6/docs/api
> 
> 
> 
> 
> 
>
> 
>  ...
> 
> maven-general-repo.googlecode.com
> General Maven Repo on Google Code
> scm:hg:https://site.pircbotx.googlecode.com/hg
> false
> 
> 
> maven-general-repo.googlecode.com
> scm:hg:https://site.pircbotx.googlecode.com/hg/
> 
> 
>
>
> Leon
>
> 
> From: Olivier Lamy 
> To: scm-dev@maven.apache.org
> Sent: Fri, January 14, 2011 4:27:51 PM
> Subject: Re: Any plans to fix/update maven-scm-provider-hg ?
>
> Hello
> Can you give more details ?
> version of wagon scm you are using in your pom ?
>
> 2011/1/13 Lord.Quackstar :
>> It seems that the only way to use Mercurial in Maven is through
>> maven-scm-provider-hg. However there are so many problems that the plugin
>> is
>> unusable
>>
>> First, you have it being out of date. In Maven 2.2.1 it works somewhat (by
>> working I mean it detects that it exists and tries to use it), but in
>> Maven
>> 3.0.2 you get this:
>>
>>  Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException:
>> No
>> such provider: 'hg'.
>>
>> Second, you have the list command bug, which seems to affect even people
>> using hudsun. They were able to fix it by creating their own plugin, which
>> doesn't work with Maven-only installations. Following is the error message
>>
>> [INFO] [deploy:deploy {execution: default-deploy}]
>> [INFO] Retrieving previous build number from
>>  pircbotx.googlecode.com
>> [INFO] Removing
>> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pir
>> cbotx\pircbotx\1.3-SNAPSHOT
>> [INFO] EXECUTING: cmd.exe /X /C "hg clone -r tip
>>
>>https://*SNIP*@site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT
>>T
>>
>>C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pircbotx\pircbotx\1.3-SNAPSHOT"
>>"
>> [INFO] EXECUTING: cmd.exe /X /C "hg locate"
>> [INFO] repository metadata for: 'snapshot pircbotx:pircbotx:1.3-SNAPSHOT'
>> could not be found on repository: pircbotx.googlecode.com, so will be
>> created Uploading:
>>
>>scm:hg:https://site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT/pircbotx-1.3-SNAPSHOT.jar
>>r
>> [INFO]

Re: How to attach a patch in jar?

[Olivier Lamy]

Which cvs version are you using for not having this option -d ??

Here I have :

olamy@olamy-laptop:~/dev/sources/maven/scm$ cvs --help-options rlist
CVS global options (specified before the command name) are:
-H   Displays usage information for command.
-Q   Cause CVS to be really quiet.
-q   Cause CVS to be somewhat quiet.
-r   Make checked-out files read-only.
-w   Make checked-out files read-write (default).
-n   Do not execute anything that will change the disk.
-t   Show trace of program execution (repeat for more
 verbosity) -- try with -n.
-R   Assume repository is read-only, such as CDROM
-v   CVS version and copyright.
-T tmpdirUse 'tmpdir' for temporary files.
-e editorUse 'editor' for editing log information.
-d CVS_root  Overrides $CVSROOT as the root of the CVS tree.
-f   Do not use the ~/.cvsrc file.
-z # Request compression level '#' for net traffic.
-a   Authenticate all net traffic.
-4   Use IPv4 addresses only.
-6   Use IPv6 addresses only.
-s VAR=VAL   Set CVS user variable.

olamy@olamy-laptop:~/dev/sources/maven/scm$ cvs -v

Concurrent Versions System (CVS) 1.12.13 (client/server)

2011/1/25 samuellawrence :
>
> Hi,
>
> My problem is, I have to list the files that are in the repository and it
> can be any repository. So I have chosen maven to do that. Now I could list
> the files from svn repository. and when I used to list from cvs I got the
> following error and I am using maven scm 1.4 version.
>
> D:\temp
> basedir = D:\temp; files = [DQA\Doc\Development\3.4.0]
> [INFO] Executing: cmd.exe /X /C "cvs -z3 -f -d
> :pserver:samuel@192.168.1.8:/bosco/cvsrep -n -q rls -d  -e -R
> DQA\Doc\Development\3.4.0"
> [INFO] Working directory: D:\temp
> There was a error while executing the SCM command.
> Error message from the provider: The cvs command failed.
> Command output:
> rls: invalid option -- d
> Usage: cvs rls [-q] [-e] [-l] [-R] [-r rev] [-D date] [-t] [modules...]
>        -D date Show files from date.
>        -e      Display in CVS/Entries format.
>        -l      Display all details.
>        -P      Ignore empty directories.
>        -q      Quieter output.
>        -R      List recursively.
>        -r rev  Show files with revision or tag.
>        -T      Show time in local time instead of GMT.
> (Specify the --help global option for a list of other help options)
>
> Where I remove and "-d" from the command and it worked fine in the command
> line but in the program "-d" is appended automatically. Kindly help me how
> to remove the "-d" using api or run the with '-d' Or if you have a jar that
> resolved this problem kindly pass it to me. it will very helpful.
>
> Kindly help me.
>
> Thanks in Advance
>
>
>
> Olivier Lamy wrote:
>>
>> Hello,
>> AFAIK the issue is closed and marked as fixed for scm 1.1 .
>> Which version are you using ? If >= 1.1 and you still have the issue,
>> the best is probably to open an other one with a description.
>>
>> Thanks,
>> --
>> Olivier Lamy
>> http://twitter.com/olamy
>> http://www.linkedin.com/in/olamy
>>
>> 2011/1/25 samuellawrence :
>>>
>>> Dear all,
>>>
>>> I am working on maven-scm-client using api. When I use list cvs command.
>>> I
>>> am getting the following error message from the provider:
>>>
>>> The cvs command failed.
>>> Command output:
>>> rls: invalid option -- d
>>> Usage: cvs rls [-q] [-e] [-l] [-R] [-r rev] [-D date] [-t] [modules...]
>>>        -D date Show files from date.
>>>        -e Display in CVS/Entries format.
>>>        -l Display all details.
>>>        -P Ignore empty directories.
>>>        -q Quieter output.
>>>        -R List recursively.
>>>        -r rev Show files with revision or tag.
>>>        -T Show time in local time instead of GMT.
>>> (Specify the --help global option for a list of other help options)
>>>
>>> I found solution in http://jira.codehaus.org/browse/SCM-380 url but it a
>>> patch. I don't know how to apply the patch to the maven scm jars.
>>>
>>> Please help me how to apply the patch to a jar.
>>>
>>> Thank in Advance.
>>> --
>>> View this message in context:
>>> http://maven.40175.n5.nabble.com/How-to-attach-a-patch-in-jar-tp3355871p3355871.html
>>> Sent from the Maven Developers mailing list archive at Nabble.com.
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>>
>
> --
> View this message in context: 
> http://maven.40175.n5.nabble.com/How-to-attach-a-patch-in-jar-tp3355871p3356124.html
> Sent from the Maven Developers mai

Re: How to attach a patch in jar?

[Mark Struberg]

Use the patch command [1].
There is a windows distribution of lots of GNU tools [2] which might help you 
too.

$> patch -p0 < yourpatchfile

LieGrue,
strub

[1] http://linux.die.net/man/1/patch
[2] http://gnuwin32.sourceforge.net/

--- On Tue, 1/25/11, Ricky Clarkson  wrote:

> From: Ricky Clarkson 
> Subject: Re: How to attach a patch in jar?
> To: scm-dev@maven.apache.org
> Date: Tuesday, January 25, 2011, 7:58 AM
> Check out the source code for the
> project you wish to patch.  Apply
> the patch (see the patch command, or look into whatever
> tortoise etc.
> supply), change the pom.xml's version number to something
> non-standard
> and mvn clean install (deploy if you like).
> 
> You can't apply a source code patch to a binary jar, you
> need to apply
> it to source.
> 
> On Tue, Jan 25, 2011 at 7:14 AM, samuellawrence 
> wrote:
> >
> > Dear all,
> >
> > I am working on maven-scm-client using api. When I use
> list cvs command. I
> > am getting the following error message from the
> provider:
> >
> > The cvs command failed.
> > Command output:
> > rls: invalid option -- d
> > Usage: cvs rls [-q] [-e] [-l] [-R] [-r rev] [-D date]
> [-t] [modules...]
> >        -D date Show files from date.
> >        -e Display in CVS/Entries format.
> >        -l Display all details.
> >        -P Ignore empty directories.
> >        -q Quieter output.
> >        -R List recursively.
> >        -r rev Show files with revision or tag.
> >        -T Show time in local time instead of GMT.
> > (Specify the --help global option for a list of other
> help options)
> >
> > I found solution in http://jira.codehaus.org/browse/SCM-380 url but it a
> > patch. I don't know how to apply the patch to the
> maven scm jars.
> >
> > Please help me how to apply the patch to a jar.
> >
> > Thanks in Advance
> > --
> > View this message in context: 
> > http://maven.40175.n5.nabble.com/How-to-attach-a-patch-in-jar-tp3355857p3355857.html
> > Sent from the Maven - SCM mailing list archive at
> Nabble.com.
> >
> 

Re: How to attach a patch in jar?

[Ricky Clarkson]

Check out the source code for the project you wish to patch.  Apply
the patch (see the patch command, or look into whatever tortoise etc.
supply), change the pom.xml's version number to something non-standard
and mvn clean install (deploy if you like).

You can't apply a source code patch to a binary jar, you need to apply
it to source.

On Tue, Jan 25, 2011 at 7:14 AM, samuellawrence  wrote:
>
> Dear all,
>
> I am working on maven-scm-client using api. When I use list cvs command. I
> am getting the following error message from the provider:
>
> The cvs command failed.
> Command output:
> rls: invalid option -- d
> Usage: cvs rls [-q] [-e] [-l] [-R] [-r rev] [-D date] [-t] [modules...]
>        -D date Show files from date.
>        -e Display in CVS/Entries format.
>        -l Display all details.
>        -P Ignore empty directories.
>        -q Quieter output.
>        -R List recursively.
>        -r rev Show files with revision or tag.
>        -T Show time in local time instead of GMT.
> (Specify the --help global option for a list of other help options)
>
> I found solution in http://jira.codehaus.org/browse/SCM-380 url but it a
> patch. I don't know how to apply the patch to the maven scm jars.
>
> Please help me how to apply the patch to a jar.
>
> Thanks in Advance
> --
> View this message in context: 
> http://maven.40175.n5.nabble.com/How-to-attach-a-patch-in-jar-tp3355857p3355857.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>

Re: Any plans to fix/update maven-scm-provider-hg ?

[Olivier Lamy]

Hello,
Fixed in scm trunk you can use (note where the dependency is declared)


  

  org.apache.maven.plugins
  maven-site-plugin
  3.0-beta-3
  

  org.apache.maven.scm
  maven-scm-api
  1.5-SNAPSHOT


  org.apache.maven.scm
  maven-scm-provider-hg
  1.5-SNAPSHOT

  

  


And use this repo (until scm 1.5 is released ) :
https://repository.apache.org/content/groups/snapshots-group/

let us know if you still have issues.

2011/1/20 Lord.Quackstar :
> Sorry for the delay, I sent this with another email address that wasn't
> subscribed.
>
> I have this in my POM
>     
>         
>             
>                 org.apache.maven.wagon
>                 wagon-webdav
>                 1.0-beta-2
>             
>             
>                 org.apache.maven.scm
>                 maven-scm-provider-hg
>                 1.4
>             
>             
>                 org.apache.maven.wagon
>                 wagon-scm
>                 1.0-beta-7
>             
>         
>    ..
>     
>
>     
>         
>             
>             
>                 org.apache.maven.plugins
>                 maven-javadoc-plugin
>                 2.7
>                 
>                     Leon Blakey
>                     ${project.version}
>                     
>                         http://download.oracle.com/javase/6/docs/api
>                     
>                 
>             
>         
>     
>
>     
>  ...
>         
>             maven-general-repo.googlecode.com
>             General Maven Repo on Google Code
>             scm:hg:https://site.pircbotx.googlecode.com/hg
>             false
>         
>         
>             maven-general-repo.googlecode.com
>             scm:hg:https://site.pircbotx.googlecode.com/hg/
>         
>     
>
>
> Leon
>
> 
> From: Olivier Lamy 
> To: scm-dev@maven.apache.org
> Sent: Fri, January 14, 2011 4:27:51 PM
> Subject: Re: Any plans to fix/update maven-scm-provider-hg ?
>
> Hello
> Can you give more details ?
> version of wagon scm you are using in your pom ?
>
> 2011/1/13 Lord.Quackstar :
>> It seems that the only way to use Mercurial in Maven is through
>> maven-scm-provider-hg. However there are so many problems that the plugin
>> is
>> unusable
>>
>> First, you have it being out of date. In Maven 2.2.1 it works somewhat (by
>> working I mean it detects that it exists and tries to use it), but in
>> Maven
>> 3.0.2 you get this:
>>
>>  Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException:
>> No
>> such provider: 'hg'.
>>
>> Second, you have the list command bug, which seems to affect even people
>> using hudsun. They were able to fix it by creating their own plugin, which
>> doesn't work with Maven-only installations. Following is the error message
>>
>> [INFO] [deploy:deploy {execution: default-deploy}]
>> [INFO] Retrieving previous build number from
>>  pircbotx.googlecode.com
>> [INFO] Removing
>> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pir
>> cbotx\pircbotx\1.3-SNAPSHOT
>> [INFO] EXECUTING: cmd.exe /X /C "hg clone -r tip
>>
>> https://*SNIP*@site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT
>>
>> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pircbotx\pircbotx\1.3-SNAPSHOT"
>> [INFO] EXECUTING: cmd.exe /X /C "hg locate"
>> [INFO] repository metadata for: 'snapshot pircbotx:pircbotx:1.3-SNAPSHOT'
>> could not be found on repository: pircbotx.googlecode.com, so will be
>> created Uploading:
>>
>> scm:hg:https://site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT/pircbotx-1.3-SNAPSHOT.jar
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Error deploying artifact: Error listing repository: No such command
>> 'list'.
>>
>> (This is replicated on site:deploy as well).
>>
>> Third, you have the complete lack of documentation on using it. It took me
>> 3+ hours to get the results above; everything else kept erroring out as I
>> slipp

Re: Any plans to fix/update maven-scm-provider-hg ?

[Olivier Lamy]

Hello
Can you give more details ?
version of wagon scm you are using in your pom ?

2011/1/13 Lord.Quackstar :
> It seems that the only way to use Mercurial in Maven is through
> maven-scm-provider-hg. However there are so many problems that the plugin is
> unusable
>
> First, you have it being out of date. In Maven 2.2.1 it works somewhat (by
> working I mean it detects that it exists and tries to use it), but in Maven
> 3.0.2 you get this:
>
>  Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException: No
> such provider: 'hg'.
>
> Second, you have the list command bug, which seems to affect even people
> using hudsun. They were able to fix it by creating their own plugin, which
> doesn't work with Maven-only installations. Following is the error message
>
> [INFO] [deploy:deploy {execution: default-deploy}]
> [INFO] Retrieving previous build number from
>  pircbotx.googlecode.com
> [INFO] Removing
> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pir
> cbotx\pircbotx\1.3-SNAPSHOT
> [INFO] EXECUTING: cmd.exe /X /C "hg clone -r tip
> https://*SNIP*@site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT
> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pircbotx\pircbotx\1.3-SNAPSHOT"
> [INFO] EXECUTING: cmd.exe /X /C "hg locate"
> [INFO] repository metadata for: 'snapshot pircbotx:pircbotx:1.3-SNAPSHOT'
> could not be found on repository: pircbotx.googlecode.com, so will be
> created Uploading:
> scm:hg:https://site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT/pircbotx-1.3-SNAPSHOT.jar
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error deploying artifact: Error listing repository: No such command
> 'list'.
>
> (This is replicated on site:deploy as well).
>
> Third, you have the complete lack of documentation on using it. It took me
> 3+ hours to get the results above; everything else kept erroring out as I
> slipped further into dependency hell. None of the projects have docs on how
> to use this.
>
> Fourth, you have the abandonment of the user support mailing list (
> http://mail-archives.apache.org/mod_mbox/maven-scm-users/ ). This is more
> general to maven-scm, but does affect this plugin. The last email talks
> about this very same problem, however it's been almost 2 months with no
> response. Even for the past year none of the support questions have been
> answered.
>
> ---
>
> Combined, this leads to a plugin that isn't usable at all and can mislead
> people into thinking that it works. Are their any plans to update it? Are
> their any plans to depreciate it?
>
> Thanks,
> Leon
>
>



-- 
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

Re: Question about status of maven-scm-provider-jgit

[Mark Struberg]

Hi!

You most probably also will need to tinker on jgit-simple [1]. It got hosted on 
github because it contains sources which are partly copy&pasted over from 
Shawns eclipse integration. So this was just not possible to ALv2... But 
actually the most important parts sit there. The scm-provider itself is obvious.

Another thing: you cannot easily split it out of maven-scm-providers-git, 
because it shares a lot code and test data, etc. To be more exact: you can but 
it doesn't make that much sense ;)

LieGrue,
strub



[1] https://github.com/sonatype/jgit-simple

--- On Mon, 1/10/11, Evgeny Mandrikov  wrote:

From: Evgeny Mandrikov 
Subject: Re: Question about status of maven-scm-provider-jgit
To: scm-dev@maven.apache.org
Date: Monday, January 10, 2011, 11:25 PM

Thank you!

On Tue, Jan 11, 2011 at 02:21, Olivier Lamy  wrote:


so you have now karma on both (svnjava and jgit)

Let me know others who need this too.



We will see later more details (groupId/artifactId etc ).







2011/1/11 Evgeny Mandrikov :

> My google id : Mandrikov

>

> On Tue, Jan 11, 2011 at 02:11, Olivier Lamy  wrote:

>>

>> So I have reserved the name here :

>> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-jgit/

>> And import current stuff from [1]

>> And move svnjava to

>> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/

>>

>> Evgeny what is your google id ?

>>

>> --

>> Olivier

>> [1]

>> http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/

>>

>>

>> 2011/1/10 Evgeny Mandrikov :

>> > Hi Marc,

>> > So it means that actual sources here - [1]. Right?

>> > Yes - I think it's time to come back to this implementation, since jgit

>> > evolves. If you don't have time to do so - I can be a volunteer for

>> > this.

>> > [1]

>> >

>> > http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/

>> >

>> > On Mon, Jan 10, 2011 at 17:55, Mark Struberg  wrote:

>> >>

>> >> Hi Evgeny!

>> >>

>> >> I've imported my sources to the maven-scm repo but we had to move it to

>> >> the sandbox because jgit/egit wasn't stable at the time. This was

>> >> written

>> >> just before egit moved to eclipse.org and underwent significant

>> >> changes. So

>> >> I fear the code will currently not compile against the latest version.

>> >>

>> >> Also I was forced to introduce a middle layer because of license

>> >> constraints (egit was LGPL at the time). I'm not sure if jgit-simple

>> >> got

>> >> maintained itmt. I didn't have found time to work on jgit again but

>> >> I've

>> >> improved the handling of the much more stable git-exe provider.

>> >>

>> >> Since egit/jgit now got an official release, it might be time to peek

>> >> at

>> >> it again.

>> >>

>> >> LieGrue,

>> >> strub

>> >>

>> >>

>> >> --- On Mon, 1/10/11, Evgeny Mandrikov  wrote:

>> >>

>> >> From: Evgeny Mandrikov 

>> >> Subject: Re: Question about status of maven-scm-provider-jgit

>> >> To: scm-dev@maven.apache.org

>> >> Date: Monday, January 10, 2011, 2:40 PM

>> >>

>> >> Mainly my question wasn't not about why this is not in ASF Maven SCM

>> >> repository and not released, but about stability of this project and

>> >> where

>> >> is an official source code ? I think I can made private release for me

>> >> and

>> >> use it.

>> >>

>> >>

>> >>

>> >> On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov 

>> >> wrote:

>> >>

>> >>

>> >> But I believe that this problem can be resolved ? ;)

>> >>

>> >> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:

>> >>

>> >>

>> >>

>> >> Hello,

>> >>

>> >> The problem : jgit is not available in central ( see

>> >>

>> >> http://www.eclipse.org/jgit/download/ ).

>> >>

>> >> As I remember we only allow dependencies which are in central.

>> >>

>> >>

>> >>

>> >>

>> >>

>> >>

>> >>

>> >> 2011/1/10 Evgeny Mandrikov :

>> >>

>> >>

Re: Question about status of maven-scm-provider-jgit

[Evgeny Mandrikov]

Thank you!

On Tue, Jan 11, 2011 at 02:21, Olivier Lamy  wrote:

> so you have now karma on both (svnjava and jgit)
> Let me know others who need this too.
>
> We will see later more details (groupId/artifactId etc ).
>
>
>
> 2011/1/11 Evgeny Mandrikov :
> > My google id : Mandrikov
> >
> > On Tue, Jan 11, 2011 at 02:11, Olivier Lamy  wrote:
> >>
> >> So I have reserved the name here :
> >> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-jgit/
> >> And import current stuff from [1]
> >> And move svnjava to
> >>
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
> >>
> >> Evgeny what is your google id ?
> >>
> >> --
> >> Olivier
> >> [1]
> >>
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/
> >>
> >>
> >> 2011/1/10 Evgeny Mandrikov :
> >> > Hi Marc,
> >> > So it means that actual sources here - [1]. Right?
> >> > Yes - I think it's time to come back to this implementation, since
> jgit
> >> > evolves. If you don't have time to do so - I can be a volunteer for
> >> > this.
> >> > [1]
> >> >
> >> >
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/
> >> >
> >> > On Mon, Jan 10, 2011 at 17:55, Mark Struberg 
> wrote:
> >> >>
> >> >> Hi Evgeny!
> >> >>
> >> >> I've imported my sources to the maven-scm repo but we had to move it
> to
> >> >> the sandbox because jgit/egit wasn't stable at the time. This was
> >> >> written
> >> >> just before egit moved to eclipse.org and underwent significant
> >> >> changes. So
> >> >> I fear the code will currently not compile against the latest
> version.
> >> >>
> >> >> Also I was forced to introduce a middle layer because of license
> >> >> constraints (egit was LGPL at the time). I'm not sure if jgit-simple
> >> >> got
> >> >> maintained itmt. I didn't have found time to work on jgit again but
> >> >> I've
> >> >> improved the handling of the much more stable git-exe provider.
> >> >>
> >> >> Since egit/jgit now got an official release, it might be time to peek
> >> >> at
> >> >> it again.
> >> >>
> >> >> LieGrue,
> >> >> strub
> >> >>
> >> >>
> >> >> --- On Mon, 1/10/11, Evgeny Mandrikov  wrote:
> >> >>
> >> >> From: Evgeny Mandrikov 
> >> >> Subject: Re: Question about status of maven-scm-provider-jgit
> >> >> To: scm-dev@maven.apache.org
> >> >> Date: Monday, January 10, 2011, 2:40 PM
> >> >>
> >> >> Mainly my question wasn't not about why this is not in ASF Maven SCM
> >> >> repository and not released, but about stability of this project and
> >> >> where
> >> >> is an official source code ? I think I can made private release for
> me
> >> >> and
> >> >> use it.
> >> >>
> >> >>
> >> >>
> >> >> On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov  >
> >> >> wrote:
> >> >>
> >> >>
> >> >> But I believe that this problem can be resolved ? ;)
> >> >>
> >> >> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy 
> wrote:
> >> >>
> >> >>
> >> >>
> >> >> Hello,
> >> >>
> >> >> The problem : jgit is not available in central ( see
> >> >>
> >> >> http://www.eclipse.org/jgit/download/ ).
> >> >>
> >> >> As I remember we only allow dependencies which are in central.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> 2011/1/10 Evgeny Mandrikov :
> >> >>
> >> >> > Hi,
> >> >>
> >> >> > Which status of implementation of Git SCM provider based on JGit
> >> >> > ? Any
> >> >>
> >> >> > progress?
> >> >>
> >> >> > I found several sources. For example implementation in GitHub
> >

Re: Question about status of maven-scm-provider-jgit

[Evgeny Mandrikov]

My google id : Mandrikov

On Tue, Jan 11, 2011 at 02:11, Olivier Lamy  wrote:

> So I have reserved the name here :
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-jgit/
> And import current stuff from [1]
> And move svnjava to
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
>
> Evgeny what is your google id ?
>
> --
> Olivier
> [1]
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/
>
>
> 2011/1/10 Evgeny Mandrikov :
> > Hi Marc,
> > So it means that actual sources here - [1]. Right?
> > Yes - I think it's time to come back to this implementation, since jgit
> > evolves. If you don't have time to do so - I can be a volunteer for this.
> > [1]
> >
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/
> >
> > On Mon, Jan 10, 2011 at 17:55, Mark Struberg  wrote:
> >>
> >> Hi Evgeny!
> >>
> >> I've imported my sources to the maven-scm repo but we had to move it to
> >> the sandbox because jgit/egit wasn't stable at the time. This was
> written
> >> just before egit moved to eclipse.org and underwent significant
> changes. So
> >> I fear the code will currently not compile against the latest version.
> >>
> >> Also I was forced to introduce a middle layer because of license
> >> constraints (egit was LGPL at the time). I'm not sure if jgit-simple got
> >> maintained itmt. I didn't have found time to work on jgit again but I've
> >> improved the handling of the much more stable git-exe provider.
> >>
> >> Since egit/jgit now got an official release, it might be time to peek at
> >> it again.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >> --- On Mon, 1/10/11, Evgeny Mandrikov  wrote:
> >>
> >> From: Evgeny Mandrikov 
> >> Subject: Re: Question about status of maven-scm-provider-jgit
> >> To: scm-dev@maven.apache.org
> >> Date: Monday, January 10, 2011, 2:40 PM
> >>
> >> Mainly my question wasn't not about why this is not in ASF Maven SCM
> >> repository and not released, but about stability of this project and
> where
> >> is an official source code ? I think I can made private release for me
> and
> >> use it.
> >>
> >>
> >>
> >> On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov 
> >> wrote:
> >>
> >>
> >> But I believe that this problem can be resolved ? ;)
> >>
> >> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:
> >>
> >>
> >>
> >> Hello,
> >>
> >> The problem : jgit is not available in central ( see
> >>
> >> http://www.eclipse.org/jgit/download/ ).
> >>
> >> As I remember we only allow dependencies which are in central.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> 2011/1/10 Evgeny Mandrikov :
> >>
> >> > Hi,
> >>
> >> > Which status of implementation of Git SCM provider based on JGit ? Any
> >>
> >> > progress?
> >>
> >> > I found several sources. For example implementation in GitHub
> >>
> >> >
> >> > (
> https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit
>  ),
> >>
> >> > but it seems a bit outdated.
> >>
> >> >
> >>
> >> > --
> >>
> >> > Best regards,
> >>
> >> > Evgeny Mandrikov aka Godin <http://godin.net.ru>
> >>
> >> > http://twitter.com/_godin_
> >>
> >> >
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >>
> >> Olivier Lamy
> >>
> >> http://twitter.com/olamy
> >>
> >> http://www.linkedin.com/in/olamy
> >>
> >>
> >>
> >>
> >> --
> >> Best regards,
> >> Evgeny Mandrikov aka Godin <http://godin.net.ru>
> >>
> >>
> >> http://twitter.com/_godin_
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Best regards,
> >> Evgeny Mandrikov aka Godin <http://godin.net.ru>
> >> http://twitter.com/_godin_
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> > --
> > Best regards,
> > Evgeny Mandrikov aka Godin <http://godin.net.ru>
> > http://twitter.com/_godin_
> >
>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>



-- 
Best regards,
Evgeny Mandrikov aka Godin <http://godin.net.ru>
http://twitter.com/_godin_

Re: Question about status of maven-scm-provider-jgit

[Olivier Lamy]

So I have reserved the name here :
http://code.google.com/a/apache-extras.org/p/maven-scm-provider-jgit/
And import current stuff from [1]
And move svnjava to
http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/

Evgeny what is your google id ?

--
Olivier
[1] 
http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/


2011/1/10 Evgeny Mandrikov :
> Hi Marc,
> So it means that actual sources here - [1]. Right?
> Yes - I think it's time to come back to this implementation, since jgit
> evolves. If you don't have time to do so - I can be a volunteer for this.
> [1]
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/
>
> On Mon, Jan 10, 2011 at 17:55, Mark Struberg  wrote:
>>
>> Hi Evgeny!
>>
>> I've imported my sources to the maven-scm repo but we had to move it to
>> the sandbox because jgit/egit wasn't stable at the time. This was written
>> just before egit moved to eclipse.org and underwent significant changes. So
>> I fear the code will currently not compile against the latest version.
>>
>> Also I was forced to introduce a middle layer because of license
>> constraints (egit was LGPL at the time). I'm not sure if jgit-simple got
>> maintained itmt. I didn't have found time to work on jgit again but I've
>> improved the handling of the much more stable git-exe provider.
>>
>> Since egit/jgit now got an official release, it might be time to peek at
>> it again.
>>
>> LieGrue,
>> strub
>>
>>
>> --- On Mon, 1/10/11, Evgeny Mandrikov  wrote:
>>
>> From: Evgeny Mandrikov 
>> Subject: Re: Question about status of maven-scm-provider-jgit
>> To: scm-dev@maven.apache.org
>> Date: Monday, January 10, 2011, 2:40 PM
>>
>> Mainly my question wasn't not about why this is not in ASF Maven SCM
>> repository and not released, but about stability of this project and where
>> is an official source code ? I think I can made private release for me and
>> use it.
>>
>>
>>
>> On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov 
>> wrote:
>>
>>
>> But I believe that this problem can be resolved ? ;)
>>
>> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:
>>
>>
>>
>> Hello,
>>
>> The problem : jgit is not available in central ( see
>>
>> http://www.eclipse.org/jgit/download/ ).
>>
>> As I remember we only allow dependencies which are in central.
>>
>>
>>
>>
>>
>>
>>
>> 2011/1/10 Evgeny Mandrikov :
>>
>> > Hi,
>>
>> > Which status of implementation of Git SCM provider based on JGit ? Any
>>
>> > progress?
>>
>> > I found several sources. For example implementation in GitHub
>>
>> >
>> > ( https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit ),
>>
>> > but it seems a bit outdated.
>>
>> >
>>
>> > --
>>
>> > Best regards,
>>
>> > Evgeny Mandrikov aka Godin <http://godin.net.ru>
>>
>> > http://twitter.com/_godin_
>>
>> >
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Olivier Lamy
>>
>> http://twitter.com/olamy
>>
>> http://www.linkedin.com/in/olamy
>>
>>
>>
>>
>> --
>> Best regards,
>> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>>
>>
>> http://twitter.com/_godin_
>>
>>
>>
>>
>>
>> --
>> Best regards,
>> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>> http://twitter.com/_godin_
>>
>>
>>
>>
>>
>>
>>
>
>
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin <http://godin.net.ru>
> http://twitter.com/_godin_
>



-- 
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

Re: Question about status of maven-scm-provider-jgit

[Evgeny Mandrikov]

Hi Marc,

So it means that actual sources here - [1]. Right?

Yes - I think it's time to come back to this implementation, since jgit
evolves. If you don't have time to do so - I can be a volunteer for this.

[1]
http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/

On Mon, Jan 10, 2011 at 17:55, Mark Struberg  wrote:

> Hi Evgeny!
>
> I've imported my sources to the maven-scm repo but we had to move it to the
> sandbox because jgit/egit wasn't stable at the time. This was written just
> before egit moved to eclipse.org and underwent significant changes. So I
> fear the code will currently not compile against the latest version.
>
> Also I was forced to introduce a middle layer because of license
> constraints (egit was LGPL at the time). I'm not sure if jgit-simple got
> maintained itmt. I didn't have found time to work on jgit again but I've
> improved the handling of the much more stable git-exe provider.
>
> Since egit/jgit now got an official release, it might be time to peek at it
> again.
>
> LieGrue,
> strub
>
>
> --- On Mon, 1/10/11, Evgeny Mandrikov  wrote:
>
> From: Evgeny Mandrikov 
> Subject: Re: Question about status of maven-scm-provider-jgit
> To: scm-dev@maven.apache.org
> Date: Monday, January 10, 2011, 2:40 PM
>
> Mainly my question wasn't not about why this is not in ASF Maven SCM
> repository and not released, but about stability of this project and where
> is an official source code ? I think I can made private release for me and
> use it.
>
>
>
> On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov 
> wrote:
>
>
> But I believe that this problem can be resolved ? ;)
>
> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:
>
>
>
> Hello,
>
> The problem : jgit is not available in central ( see
>
> http://www.eclipse.org/jgit/download/ ).
>
> As I remember we only allow dependencies which are in central.
>
>
>
>
>
>
>
> 2011/1/10 Evgeny Mandrikov :
>
> > Hi,
>
> > Which status of implementation of Git SCM provider based on JGit ? Any
>
> > progress?
>
> > I found several sources. For example implementation in GitHub
>
> > (
> https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit
>  ),
>
> > but it seems a bit outdated.
>
> >
>
> > --
>
> > Best regards,
>
> > Evgeny Mandrikov aka Godin <http://godin.net.ru>
>
> > http://twitter.com/_godin_
>
> >
>
>
>
>
>
>
>
> --
>
> Olivier Lamy
>
> http://twitter.com/olamy
>
> http://www.linkedin.com/in/olamy
>
>
>
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>
>
> http://twitter.com/_godin_
>
>
>
>
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin <http://godin.net.ru>
> http://twitter.com/_godin_
>
>
>
>
>
>
>
>


-- 
Best regards,
Evgeny Mandrikov aka Godin <http://godin.net.ru>
http://twitter.com/_godin_

Re: Question about status of maven-scm-provider-jgit

[Dennis Lundberg]

On 2011-01-10 21:34, Olivier Lamy wrote:
> Due to this reasons, we can maybe think about moving [1] to apache-extras.org 
> ?
> WDYT ?
> 
> I have planned to move svnjava [2] to this place too.

+1

I was thinking the same thing. Let's put all license-encumbered SCM
implementations at apache-extras.

> 
> Thanks,
> --
> Olivier
> 
> [1] 
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/
> [2] http://code.google.com/p/maven-scm-provider-svnjava/
> 
> 2011/1/10 Mark Struberg :
>> Hi Evgeny!
>>
>> I've imported my sources to the maven-scm repo but we had to move it to the 
>> sandbox because jgit/egit wasn't stable at the time. This was written just 
>> before egit moved to eclipse.org and underwent significant changes. So I 
>> fear the code will currently not compile against the latest version.
>>
>> Also I was forced to introduce a middle layer because of license constraints 
>> (egit was LGPL at the time). I'm not sure if jgit-simple got maintained 
>> itmt. I didn't have found time to work on jgit again but I've improved the 
>> handling of the much more stable git-exe provider.
>>
>> Since egit/jgit now got an official release, it might be time to peek at it 
>> again.
>>
>> LieGrue,
>> strub
>>
>>
>> --- On Mon, 1/10/11, Evgeny Mandrikov  wrote:
>>
>> From: Evgeny Mandrikov 
>> Subject: Re: Question about status of maven-scm-provider-jgit
>> To: scm-dev@maven.apache.org
>> Date: Monday, January 10, 2011, 2:40 PM
>>
>> Mainly my question wasn't not about why this is not in ASF Maven SCM 
>> repository and not released, but about stability of this project and where 
>> is an official source code ? I think I can made private release for me and 
>> use it.
>>
>>
>>
>> On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov  wrote:
>>
>>
>> But I believe that this problem can be resolved ? ;)
>>
>> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:
>>
>>
>>
>> Hello,
>>
>> The problem : jgit is not available in central ( see
>>
>> http://www.eclipse.org/jgit/download/ ).
>>
>> As I remember we only allow dependencies which are in central.
>>
>>
>>
>>
>>
>>
>>
>> 2011/1/10 Evgeny Mandrikov :
>>
>>> Hi,
>>
>>> Which status of implementation of Git SCM provider based on JGit ? Any
>>
>>> progress?
>>
>>> I found several sources. For example implementation in GitHub
>>
>>> ( 
>>> https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit
>>>  ),
>>
>>> but it seems a bit outdated.
>>
>>>
>>
>>> --
>>
>>> Best regards,
>>
>>> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>>
>>> http://twitter.com/_godin_
>>
>>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Olivier Lamy
>>
>> http://twitter.com/olamy
>>
>> http://www.linkedin.com/in/olamy
>>
>>
>>
>>
>> --
>> Best regards,
>> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>>
>>
>> http://twitter.com/_godin_
>>
>>
>>
>>
>>
>> --
>> Best regards,
>> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>> http://twitter.com/_godin_
>>
>>
>>
>>
>>
>>
>>
>>
> 
> 
> 


-- 
Dennis Lundberg

Re: Question about status of maven-scm-provider-jgit

[Olivier Lamy]

Due to this reasons, we can maybe think about moving [1] to apache-extras.org ?
WDYT ?

I have planned to move svnjava [2] to this place too.

Thanks,
--
Olivier

[1] 
http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-jgit/
[2] http://code.google.com/p/maven-scm-provider-svnjava/

2011/1/10 Mark Struberg :
> Hi Evgeny!
>
> I've imported my sources to the maven-scm repo but we had to move it to the 
> sandbox because jgit/egit wasn't stable at the time. This was written just 
> before egit moved to eclipse.org and underwent significant changes. So I fear 
> the code will currently not compile against the latest version.
>
> Also I was forced to introduce a middle layer because of license constraints 
> (egit was LGPL at the time). I'm not sure if jgit-simple got maintained itmt. 
> I didn't have found time to work on jgit again but I've improved the handling 
> of the much more stable git-exe provider.
>
> Since egit/jgit now got an official release, it might be time to peek at it 
> again.
>
> LieGrue,
> strub
>
>
> --- On Mon, 1/10/11, Evgeny Mandrikov  wrote:
>
> From: Evgeny Mandrikov 
> Subject: Re: Question about status of maven-scm-provider-jgit
> To: scm-dev@maven.apache.org
> Date: Monday, January 10, 2011, 2:40 PM
>
> Mainly my question wasn't not about why this is not in ASF Maven SCM 
> repository and not released, but about stability of this project and where is 
> an official source code ? I think I can made private release for me and use 
> it.
>
>
>
> On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov  wrote:
>
>
> But I believe that this problem can be resolved ? ;)
>
> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:
>
>
>
> Hello,
>
> The problem : jgit is not available in central ( see
>
> http://www.eclipse.org/jgit/download/ ).
>
> As I remember we only allow dependencies which are in central.
>
>
>
>
>
>
>
> 2011/1/10 Evgeny Mandrikov :
>
>> Hi,
>
>> Which status of implementation of Git SCM provider based on JGit ? Any
>
>> progress?
>
>> I found several sources. For example implementation in GitHub
>
>> ( https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit ),
>
>> but it seems a bit outdated.
>
>>
>
>> --
>
>> Best regards,
>
>> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>
>> http://twitter.com/_godin_
>
>>
>
>
>
>
>
>
>
> --
>
> Olivier Lamy
>
> http://twitter.com/olamy
>
> http://www.linkedin.com/in/olamy
>
>
>
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin <http://godin.net.ru>
>
>
> http://twitter.com/_godin_
>
>
>
>
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin <http://godin.net.ru>
> http://twitter.com/_godin_
>
>
>
>
>
>
>
>



-- 
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

Re: Question about status of maven-scm-provider-jgit

[Mark Struberg]

Hi Evgeny!

I've imported my sources to the maven-scm repo but we had to move it to the 
sandbox because jgit/egit wasn't stable at the time. This was written just 
before egit moved to eclipse.org and underwent significant changes. So I fear 
the code will currently not compile against the latest version.

Also I was forced to introduce a middle layer because of license constraints 
(egit was LGPL at the time). I'm not sure if jgit-simple got maintained itmt. I 
didn't have found time to work on jgit again but I've improved the handling of 
the much more stable git-exe provider. 

Since egit/jgit now got an official release, it might be time to peek at it 
again.

LieGrue,
strub


--- On Mon, 1/10/11, Evgeny Mandrikov  wrote:

From: Evgeny Mandrikov 
Subject: Re: Question about status of maven-scm-provider-jgit
To: scm-dev@maven.apache.org
Date: Monday, January 10, 2011, 2:40 PM

Mainly my question wasn't not about why this is not in ASF Maven SCM repository 
and not released, but about stability of this project and where is an official 
source code ? I think I can made private release for me and use it.



On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov  wrote:


But I believe that this problem can be resolved ? ;)

On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:



Hello,

The problem : jgit is not available in central ( see

http://www.eclipse.org/jgit/download/ ).

As I remember we only allow dependencies which are in central.







2011/1/10 Evgeny Mandrikov :

> Hi,

> Which status of implementation of Git SCM provider based on JGit ? Any

> progress?

> I found several sources. For example implementation in GitHub

> ( https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit ),

> but it seems a bit outdated.

>

> --

> Best regards,

> Evgeny Mandrikov aka Godin <http://godin.net.ru>

> http://twitter.com/_godin_

>







--

Olivier Lamy

http://twitter.com/olamy

http://www.linkedin.com/in/olamy




-- 
Best regards,
Evgeny Mandrikov aka Godin <http://godin.net.ru>


http://twitter.com/_godin_





-- 
Best regards,
Evgeny Mandrikov aka Godin <http://godin.net.ru>
http://twitter.com/_godin_

Re: Question about status of maven-scm-provider-jgit

[Evgeny Mandrikov]

Mainly my question wasn't not about why this is not in ASF Maven SCM
repository and not released, but about stability of this project and where
is an official source code ? I think I can made private release for me and
use it.

On Mon, Jan 10, 2011 at 17:38, Evgeny Mandrikov  wrote:

> But I believe that this problem can be resolved ? ;)
>
>
> On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:
>
>> Hello,
>> The problem : jgit is not available in central ( see
>> http://www.eclipse.org/jgit/download/ ).
>> As I remember we only allow dependencies which are in central.
>>
>>
>>
>> 2011/1/10 Evgeny Mandrikov :
>> > Hi,
>> > Which status of implementation of Git SCM provider based on JGit ? Any
>> > progress?
>> > I found several sources. For example implementation in GitHub
>> > (
>> https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit
>>  ),
>> > but it seems a bit outdated.
>> >
>> > --
>> > Best regards,
>> > Evgeny Mandrikov aka Godin 
>> > http://twitter.com/_godin_
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> http://twitter.com/olamy
>> http://www.linkedin.com/in/olamy
>>
>
>
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin 
> http://twitter.com/_godin_
>



-- 
Best regards,
Evgeny Mandrikov aka Godin 
http://twitter.com/_godin_

Re: Question about status of maven-scm-provider-jgit

[Evgeny Mandrikov]

But I believe that this problem can be resolved ? ;)

On Mon, Jan 10, 2011 at 17:00, Olivier Lamy  wrote:

> Hello,
> The problem : jgit is not available in central ( see
> http://www.eclipse.org/jgit/download/ ).
> As I remember we only allow dependencies which are in central.
>
>
>
> 2011/1/10 Evgeny Mandrikov :
> > Hi,
> > Which status of implementation of Git SCM provider based on JGit ? Any
> > progress?
> > I found several sources. For example implementation in GitHub
> > (
> https://github.com/struberg/maven-scm-providers-git/tree/master/maven-scm-provider-jgit
>  ),
> > but it seems a bit outdated.
> >
> > --
> > Best regards,
> > Evgeny Mandrikov aka Godin 
> > http://twitter.com/_godin_
> >
>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>



-- 
Best regards,
Evgeny Mandrikov aka Godin 
http://twitter.com/_godin_

Re: Subversion and BASE revision

[Evgeny Mandrikov]

Hi,

No pb - it seems that all changes made by my already in trunk made by you ;)

There shouldn't be any problems with IP - I've signed ASF CLA before ;)

FYI: I'm successfully use git-svn for mirroring several svn repositories,
but don't use for contributing back to svn - there is a nice command "git
format-patch", which creates series of patches which can be applied on svn
;)

On Tue, Jan 4, 2011 at 11:58, Olivier Lamy  wrote:

> Salut,
> Oups I missed this.
> Uhm currently I prefer patches (not very clear for me using this at least
> for IP reason).
>
> But let me try again svn git (I add bad experiences first time I used this)
>
> --
> Olivier
>  Le 4 janv. 2011 02:12, "Evgeny Mandrikov"  a écrit :
>
> > Hi Olivier,
> >
> > I've asked this question in comments for issue SCM-591. But I didn't
> > received an answer, so : is it ok for you to pull patches from GitHub ?
> >
> > On Mon, Jan 3, 2011 at 23:45, Olivier Lamy  wrote:
> >
> >> Hi,
> >> I confirm it's not supported currently.
> >>
> >> Thanks in advance for the patch :-)
> >>
> >> --
> >> Olivier
> >>
> >> 2011/1/3 Evgeny Mandrikov :
> >> > Hi guys,
> >> > Subversion has a term "BASE" revision - is a revision of working copy.
> >> > However seems that changelog command from Maven SCM doesn't support it
> in
> >> a
> >> > revision range. Or I missed something ?
> >> > If it's true, then I can create Jira ticket and I'd like to contribute
> >> > support for this.
> >> >
> >> > --
> >> > Best regards,
> >> > Evgeny Mandrikov aka Godin 
> >> > http://twitter.com/_godin_
> >> >
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> http://twitter.com/olamy
> >> http://www.linkedin.com/in/olamy
> >>
> >
> >
> >
> > --
> > Best regards,
> > Evgeny Mandrikov aka Godin 
> > http://twitter.com/_godin_
>



-- 
Best regards,
Evgeny Mandrikov aka Godin 
http://twitter.com/_godin_

Re: Subversion and BASE revision

[Olivier Lamy]

Salut,
Oups I missed this.
Uhm currently I prefer patches (not very clear for me using this at least
for IP reason).

But let me try again svn git (I add bad experiences first time I used this)

--
Olivier
 Le 4 janv. 2011 02:12, "Evgeny Mandrikov"  a écrit :
> Hi Olivier,
>
> I've asked this question in comments for issue SCM-591. But I didn't
> received an answer, so : is it ok for you to pull patches from GitHub ?
>
> On Mon, Jan 3, 2011 at 23:45, Olivier Lamy  wrote:
>
>> Hi,
>> I confirm it's not supported currently.
>>
>> Thanks in advance for the patch :-)
>>
>> --
>> Olivier
>>
>> 2011/1/3 Evgeny Mandrikov :
>> > Hi guys,
>> > Subversion has a term "BASE" revision - is a revision of working copy.
>> > However seems that changelog command from Maven SCM doesn't support it
in
>> a
>> > revision range. Or I missed something ?
>> > If it's true, then I can create Jira ticket and I'd like to contribute
>> > support for this.
>> >
>> > --
>> > Best regards,
>> > Evgeny Mandrikov aka Godin 
>> > http://twitter.com/_godin_
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> http://twitter.com/olamy
>> http://www.linkedin.com/in/olamy
>>
>
>
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin 
> http://twitter.com/_godin_

Re: Subversion and BASE revision

[Evgeny Mandrikov]

Hi Olivier,

I've asked this question in comments for issue SCM-591. But I didn't
received an answer, so : is it ok for you to pull patches from GitHub ?

On Mon, Jan 3, 2011 at 23:45, Olivier Lamy  wrote:

> Hi,
> I confirm it's not supported currently.
>
> Thanks in advance for the patch :-)
>
> --
> Olivier
>
> 2011/1/3 Evgeny Mandrikov :
> > Hi guys,
> > Subversion has a term "BASE" revision - is a revision of working copy.
> > However seems that changelog command from Maven SCM doesn't support it in
> a
> > revision range. Or I missed something ?
> > If it's true, then I can create Jira ticket and I'd like to contribute
> > support for this.
> >
> > --
> > Best regards,
> > Evgeny Mandrikov aka Godin 
> > http://twitter.com/_godin_
> >
>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>



-- 
Best regards,
Evgeny Mandrikov aka Godin 
http://twitter.com/_godin_

Re: Subversion and BASE revision

[Olivier Lamy]

Hi,
I confirm it's not supported currently.

Thanks in advance for the patch :-)

--
Olivier

2011/1/3 Evgeny Mandrikov :
> Hi guys,
> Subversion has a term "BASE" revision - is a revision of working copy.
> However seems that changelog command from Maven SCM doesn't support it in a
> revision range. Or I missed something ?
> If it's true, then I can create Jira ticket and I'd like to contribute
> support for this.
>
> --
> Best regards,
> Evgeny Mandrikov aka Godin 
> http://twitter.com/_godin_
>



-- 
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

Re: Can't checkout maven project from Subversion repository

[Dennis Lundberg]

Right, but this is not the list for the m2eclipse team.

This list is for the SCM subproject of Maven.

On 2010-12-11 12:43, nicolasduminil wrote:
> 
> The m2eclipse documentation states that maven projects may be checked-out, as
> such, from Subversion repositories and explains how to do it. The problem is
> that it doesn't work as documented and the number of posting on this topic
> is very important. But while I could find lots of persons experimenting this
> same problem, I couldn't find any solution. Consequently, it seems very
> normal to me to post this question to the m2eclipse team as the problem may
> be observed in the context of the utilisation of m2eclipse plugin. Now, it
> may be that the problem is not at the m2eclipse plugin lebvel but at the
> Subversive one. In any case, it would deserve some analysis in my opinion
> and a more advised answer.
> 
> Kind regards,
> 
> Nicolas


-- 
Dennis Lundberg

Re: Can't checkout maven project from Subversion repository

[nicolasduminil]

The m2eclipse documentation states that maven projects may be checked-out, as
such, from Subversion repositories and explains how to do it. The problem is
that it doesn't work as documented and the number of posting on this topic
is very important. But while I could find lots of persons experimenting this
same problem, I couldn't find any solution. Consequently, it seems very
normal to me to post this question to the m2eclipse team as the problem may
be observed in the context of the utilisation of m2eclipse plugin. Now, it
may be that the problem is not at the m2eclipse plugin lebvel but at the
Subversive one. In any case, it would deserve some analysis in my opinion
and a more advised answer.

Kind regards,

Nicolas
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Can-t-checkout-maven-project-from-Subversion-repository-tp3299066p3301424.html
Sent from the Maven - SCM mailing list archive at Nabble.com.

Re: Can't checkout maven project from Subversion repository

[Dennis Lundberg]

Hi

This seems like a question for the Subversive team.

On 2010-12-09 16:32, nicolasduminil wrote:
> 
> Greetings,
> 
> I'm using Eclipse Helios with m2eclipse plugin. The "Installed Software"
> window shows the following:
> 
>   Maven Integration for Eclipse (Required)0.12.0.20101115-1102
> org.maven.ide.eclipse.feature.feature.group
>   Maven Integration for WTP (Optional)0.11.1.20101108-1810
> org.maven.ide.eclipse.wtp.feature.feature.group
> 
> I'm using also the Subversive plugin. The same "Installed Software" window
> is dispolaying:
> 
>   Subversive Revision Graph (Optional) (Incubation)   0.7.9.I20101203-1700
> org.eclipse.team.svn.revision.graph.feature.group
>   Subversive SVN Connectors   2.2.2.I20101203-1700
> org.polarion.eclipse.team.svn.connector.feature.group
>   Subversive SVN Integration for the Mylyn Project (Optional) (Incubation)
> 0.7.9.I20101203-1700  org.eclipse.team.svn.mylyn.feature.group
>   Subversive SVN JDT Ignore Extensions (Optional) (Incubation)
> 0.7.9.I20101203-1700
> org.eclipse.team.svn.resource.ignore.rules.jdt.feature.group
>   Subversive SVN Team Provider (Incubation)   0.7.9.I20101203-1700
> org.eclipse.team.svn.feature.group
>   Subversive SVN Team Provider Localization (Optional) (Incubation)
> 0.7.9.I20101203-1700  org.eclipse.team.svn.nl1.feature.group
>   Subversive SVN Team Provider Sources (Incubation)   0.7.9.I20101203-1700
> org.eclipse.team.svn.source.feature.group
> 
> Going to the sonatype update site as well as to the Subversive one, the
> Eclipse installer says: "There is nothing to install" as I checked the
> option "Hide already installed items".
> 
> However; trying to checkout maven projects from the Subversion repository
> says:
> 
> 12/9/10 3:18:22 PM CET: SCM provider is not available for
> scm:svn:https://gtssvn.xeop.de/svn/GTS/ad/thirdparty/advisory/trunk
> 
> After having googled a while I've noticed that this problem has appeared to
> many people and they were advised to install the Maven SCM provider for
> Subversive. But how and where since the Subversive site says that every
> thing which could have been installed is already installed ? m2e-extras has
> been completely installed, but the Tycho project configuration which, in my
> opinion, is not related to what I need.
> 
> Many thanks in advance for helping me.
> 
> kind regards,
> 
> Nicolas


-- 
Dennis Lundberg

Re: Multiple CVS Modules + SCM

[jiruihua]

Hi,

I am glad you got it worked. But I am still struggling with it now.
I would like to checkout multiple repositories and dump them to a same
folder. 

My parent pom:

http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";
xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  4.0.0
  com
  workspace
  0.0.1-SNAPSHOT
pom

  
 
 org.apache.maven.plugins
 maven-scm-plugin
 1.3
 
  username
  password 
  
 
  



boxcloud
cloudfire
cloudstack
  
 

One of my child pom:

http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";
xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

  4.0.0

workspace
com
0.0.1-SNAPSHOT
  
  com
  boxclound
  0.0.1-SNAPSHOT

  
 
 org.apache.maven.plugins
 maven-scm-plugin
 1.3
 
  username
  password
  

 
  


  

scm:svn:http://www.wiredreach.com:5775/svn/boxcloud/trunk
  
 

When I run this in the parent pom folder, I got error "can not load the scm
provider". 
If I add the scm element in the parent pom file, it can checkout, but the
child mudule will be skipped.

A similar guy:
http://maven.40175.n5.nabble.com/multi-module-checkout-td396061.html

Thanks a lot!
Jerry
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Multiple-CVS-Modules-SCM-tp325776p511504.html
Sent from the Maven - SCM mailing list archive at Nabble.com.

Re: making checkout paths match update

[Jason van Zyl]

-1 without some additional tests. I see no tests in the patches.

On Jun 6, 2010, at 11:05 AM, Andrew Williams wrote:

> Hi,
> 
> I just created an issue regarding the paths returned from the svn-exe command,
> http://jira.codehaus.org/browse/SCM-555
> 
> If there are no objections I will go ahead and check it in but I thought I 
> would just flag the change in behaviour first.
> 
> Andy

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.

  -- Jakob Burckhardt

Re: release:prepare how commit when SVN+SSH

[Pierre DEVREUX]

I found solution :

- install TurtoiseSVN.
- add SVN_SSH environment variable
(SVN_SSH=C:\\Progra~1\\TortoiseSVN\\bin\\TortoisePlink.exe)
- launch pageant with private key (Putty).

and it is working fine.

-- 
View this message in context: 
http://old.nabble.com/release%3Aprepare-how-commit-when-SVN%2BSSH-tp28162377p28164789.html
Sent from the Maven - SCM mailing list archive at Nabble.com.

Re: svn commit: r885618 - in /maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src: main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/ test/java/org

[Olivier Lamy]

the code is AS BEFORE except two commented lines.

2009/12/1 Dan Tran :
> oops, I miss read the changes.  but still want to ask,
>
> the change still compatible with svn 1.4 right?
>
> -Dan
>
> On Mon, Nov 30, 2009 at 3:46 PM, Dan Tran  wrote:
>> is it necessary to required svn 1.5?? and break backward compatibility?
>>
>> -        cl.createArg().setValue( "--parents" );
>> +        // SCM-487 olamy : this need a svn 1.5 cli
>> +        //cl.createArg().setValue( "--parents" );
>>
>> I hope release plugin would never pick this up
>>
>>
>>
>> -Dan
>>
>> On Mon, Nov 30, 2009 at 3:29 PM,   wrote:
>>> Author: olamy
>>> Date: Mon Nov 30 23:29:16 2009
>>> New Revision: 885618
>>>
>>> URL: http://svn.apache.org/viewvc?rev=885618&view=rev
>>> Log:
>>> revert SCM-487
>>>
>>> Modified:
>>>    
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>>>    
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>>>
>>> Modified: 
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>>> URL: 
>>> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java?rev=885618&r1=885617&r2=885618&view=diff
>>> ==
>>> --- 
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>>>  (original)
>>> +++ 
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>>>  Mon Nov 30 23:29:16 2009
>>> @@ -230,7 +230,8 @@
>>>
>>>         cl.createArg().setValue( messageFile.getAbsolutePath() );
>>>
>>> -        cl.createArg().setValue( "--parents" );
>>> +        // SCM-487 olamy : this need a svn 1.5 cli
>>> +        //cl.createArg().setValue( "--parents" );
>>>
>>>         if ( scmTagParameters != null && scmTagParameters.getScmRevision() 
>>> != null )
>>>         {
>>>
>>> Modified: 
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>>> URL: 
>>> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java?rev=885618&r1=885617&r2=885618&view=diff
>>> ==
>>> --- 
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>>>  (original)
>>> +++ 
>>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>>>  Mon Nov 30 23:29:16 2009
>>> @@ -44,7 +44,7 @@
>>>
>>>         testCommandLine( "scm:svn:svn+ssh://foo.com/svn/trunk", "svntag", 
>>> messageFile, "user",
>>>                          "svn --username user --non-interactive copy --file 
>>> " + messageFile.getAbsolutePath() +
>>> -                             " --parents . 
>>> svn+ssh://u...@foo.com/svn/tags/svntag", null );
>>> +                             " . svn+ssh://u...@foo.com/svn/tags/svntag", 
>>> null );
>>>     }
>>>
>>>     public void testTagRemoteTagHttps()
>>> @@ -57,7 +57,7 @@
>>>         scmTagParameters.setRemoteTagging( true );
>>>         testCommandLine( "scm:svn:https://foo.com/svn/trunk";, "svntag", 
>>> messageFile, "user",
>>>                          "svn --username user --non-interactive copy --file 
>>> " + messageFile.getAbsolutePath()
>>> -                             + " --parents https://foo.com/svn/trunk 
>>> https://foo.com/svn/tags/svntag";, scmTagParameters );
>>> +                             + " https://foo.com/svn/trunk 
>>> https://foo.com/svn/tags/svntag";, scmTagParameters );
>>>     }
>>>
>>>     public void testTagRemoteTagHttpsWithRevision()
>>> @@ -71,7 +71,7 @@
>>>         scmTagParameters.setScmRevision( "12" );
>>>         testCommandLine( "scm:svn:https://foo.com/svn/trunk";, "svntag", 
>>> messageFile, "user",
>>>                          "svn --username user --non-interactive copy --file 
>>> " + messageFile.getAbsolutePath()
>>> -                             + " --parents --revision 12 
>>> https://foo.com/svn/tr

Re: svn commit: r885618 - in /maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src: main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/ test/java/org

[Dan Tran]

oops, I miss read the changes.  but still want to ask,

the change still compatible with svn 1.4 right?

-Dan

On Mon, Nov 30, 2009 at 3:46 PM, Dan Tran  wrote:
> is it necessary to required svn 1.5?? and break backward compatibility?
>
> -        cl.createArg().setValue( "--parents" );
> +        // SCM-487 olamy : this need a svn 1.5 cli
> +        //cl.createArg().setValue( "--parents" );
>
> I hope release plugin would never pick this up
>
>
>
> -Dan
>
> On Mon, Nov 30, 2009 at 3:29 PM,   wrote:
>> Author: olamy
>> Date: Mon Nov 30 23:29:16 2009
>> New Revision: 885618
>>
>> URL: http://svn.apache.org/viewvc?rev=885618&view=rev
>> Log:
>> revert SCM-487
>>
>> Modified:
>>    
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>>    
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>>
>> Modified: 
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>> URL: 
>> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java?rev=885618&r1=885617&r2=885618&view=diff
>> ==
>> --- 
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>>  (original)
>> +++ 
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>>  Mon Nov 30 23:29:16 2009
>> @@ -230,7 +230,8 @@
>>
>>         cl.createArg().setValue( messageFile.getAbsolutePath() );
>>
>> -        cl.createArg().setValue( "--parents" );
>> +        // SCM-487 olamy : this need a svn 1.5 cli
>> +        //cl.createArg().setValue( "--parents" );
>>
>>         if ( scmTagParameters != null && scmTagParameters.getScmRevision() 
>> != null )
>>         {
>>
>> Modified: 
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>> URL: 
>> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java?rev=885618&r1=885617&r2=885618&view=diff
>> ==
>> --- 
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>>  (original)
>> +++ 
>> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>>  Mon Nov 30 23:29:16 2009
>> @@ -44,7 +44,7 @@
>>
>>         testCommandLine( "scm:svn:svn+ssh://foo.com/svn/trunk", "svntag", 
>> messageFile, "user",
>>                          "svn --username user --non-interactive copy --file 
>> " + messageFile.getAbsolutePath() +
>> -                             " --parents . 
>> svn+ssh://u...@foo.com/svn/tags/svntag", null );
>> +                             " . svn+ssh://u...@foo.com/svn/tags/svntag", 
>> null );
>>     }
>>
>>     public void testTagRemoteTagHttps()
>> @@ -57,7 +57,7 @@
>>         scmTagParameters.setRemoteTagging( true );
>>         testCommandLine( "scm:svn:https://foo.com/svn/trunk";, "svntag", 
>> messageFile, "user",
>>                          "svn --username user --non-interactive copy --file 
>> " + messageFile.getAbsolutePath()
>> -                             + " --parents https://foo.com/svn/trunk 
>> https://foo.com/svn/tags/svntag";, scmTagParameters );
>> +                             + " https://foo.com/svn/trunk 
>> https://foo.com/svn/tags/svntag";, scmTagParameters );
>>     }
>>
>>     public void testTagRemoteTagHttpsWithRevision()
>> @@ -71,7 +71,7 @@
>>         scmTagParameters.setScmRevision( "12" );
>>         testCommandLine( "scm:svn:https://foo.com/svn/trunk";, "svntag", 
>> messageFile, "user",
>>                          "svn --username user --non-interactive copy --file 
>> " + messageFile.getAbsolutePath()
>> -                             + " --parents --revision 12 
>> https://foo.com/svn/trunk https://foo.com/svn/tags/svntag";,
>> +                             + " --revision 12 https://foo.com/svn/trunk 
>> https://foo.com/svn/tags/svntag";,
>>                     

Re: svn commit: r885618 - in /maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src: main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/ test/java/org

[Dan Tran]

is it necessary to required svn 1.5?? and break backward compatibility?

-cl.createArg().setValue( "--parents" );
+// SCM-487 olamy : this need a svn 1.5 cli
+//cl.createArg().setValue( "--parents" );

I hope release plugin would never pick this up



-Dan

On Mon, Nov 30, 2009 at 3:29 PM,   wrote:
> Author: olamy
> Date: Mon Nov 30 23:29:16 2009
> New Revision: 885618
>
> URL: http://svn.apache.org/viewvc?rev=885618&view=rev
> Log:
> revert SCM-487
>
> Modified:
>    
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>    
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>
> Modified: 
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
> URL: 
> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java?rev=885618&r1=885617&r2=885618&view=diff
> ==
> --- 
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>  (original)
> +++ 
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
>  Mon Nov 30 23:29:16 2009
> @@ -230,7 +230,8 @@
>
>         cl.createArg().setValue( messageFile.getAbsolutePath() );
>
> -        cl.createArg().setValue( "--parents" );
> +        // SCM-487 olamy : this need a svn 1.5 cli
> +        //cl.createArg().setValue( "--parents" );
>
>         if ( scmTagParameters != null && scmTagParameters.getScmRevision() != 
> null )
>         {
>
> Modified: 
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
> URL: 
> http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java?rev=885618&r1=885617&r2=885618&view=diff
> ==
> --- 
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>  (original)
> +++ 
> maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnExeTagCommandTckTest.java
>  Mon Nov 30 23:29:16 2009
> @@ -44,7 +44,7 @@
>
>         testCommandLine( "scm:svn:svn+ssh://foo.com/svn/trunk", "svntag", 
> messageFile, "user",
>                          "svn --username user --non-interactive copy --file " 
> + messageFile.getAbsolutePath() +
> -                             " --parents . 
> svn+ssh://u...@foo.com/svn/tags/svntag", null );
> +                             " . svn+ssh://u...@foo.com/svn/tags/svntag", 
> null );
>     }
>
>     public void testTagRemoteTagHttps()
> @@ -57,7 +57,7 @@
>         scmTagParameters.setRemoteTagging( true );
>         testCommandLine( "scm:svn:https://foo.com/svn/trunk";, "svntag", 
> messageFile, "user",
>                          "svn --username user --non-interactive copy --file " 
> + messageFile.getAbsolutePath()
> -                             + " --parents https://foo.com/svn/trunk 
> https://foo.com/svn/tags/svntag";, scmTagParameters );
> +                             + " https://foo.com/svn/trunk 
> https://foo.com/svn/tags/svntag";, scmTagParameters );
>     }
>
>     public void testTagRemoteTagHttpsWithRevision()
> @@ -71,7 +71,7 @@
>         scmTagParameters.setScmRevision( "12" );
>         testCommandLine( "scm:svn:https://foo.com/svn/trunk";, "svntag", 
> messageFile, "user",
>                          "svn --username user --non-interactive copy --file " 
> + messageFile.getAbsolutePath()
> -                             + " --parents --revision 12 
> https://foo.com/svn/trunk https://foo.com/svn/tags/svntag";,
> +                             + " --revision 12 https://foo.com/svn/trunk 
> https://foo.com/svn/tags/svntag";,
>                          scmTagParameters );
>     }
>
>
>
>

Re: Register new scm provider

[Lee Freyberg]

No, that did not work either, but adding the provider as a dependency  
of the scm plugin in the plugins section of the build definition did.


Thanks for your help.
Lee









Brett Porter
Mon, 26 Oct 2009 01:32:47 -0700

It should not be in the lib directory. You should add it under the  
build extensions.

- Brett

On 24/10/2009, at 4:56 AM, Lee Freyberg wrote:

Hi,

How do you go about registering a new provider?

I have created a stub impl following the instructions on the scm site,  
and placed the its jar in the maven/lib dir (adding it as a dependecy  
in the pom did not work), but I get an error when I try and run any of  
the scm commands.
I am fairly sure mvn is picking up the provider, as if I remove the  
jar from the lib dir I get a 'no provider for scm 'xxx'' message.

With the jar present I get a different error:

[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-scm-plugin:1.2:bootstrap': Unable to  
load the mojo 'org.apache.maven.plugins:maven-scm-plugin: 
1.2:bootstrap' in the

plugin 'org.apache.maven.plugins:maven-scm-plugin'. A
required class is missing:
org/apache/maven/scm/provider/AbstractScmProvider
org.apache.maven.scm.provider.AbstractScmProvider

Am I missing a dependency somewhere? Or is this not the correct way to  
register a provider?

Any pointers appreciated.

Cheers,
Lee

Re: Register new scm provider

[Brett Porter]

It should not be in the lib directory. You should add it under the  
build extensions.


- Brett

On 24/10/2009, at 4:56 AM, Lee Freyberg wrote:



Hi,

How do you go about registering a new provider?

I have created a stub impl following the instructions on the scm  
site, and placed the its jar in the maven/lib dir (adding it as a  
dependecy in the pom did not work), but I get an error when I try  
and run any of the scm commands.


I am fairly sure mvn is picking up the provider, as if I remove the  
jar from the lib dir I get a 'no provider for scm 'xxx'' message.


With the jar present I get a different error:

[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-scm-plugin:1.2:bootstrap': Unable to  
load
the mojo 'org.apache.maven.plugins:maven-scm-plugin:1.2:bootstrap'  
in the

plugin 'org.apache.maven.plugins:maven-scm-plugin'. A
required class is missing:
org/apache/maven/scm/provider/AbstractScmProvider
org.apache.maven.scm.provider.AbstractScmProvider

Am I missing a dependency somewhere? Or is this not the correct way  
to register a provider?


Any pointers appreciated.

Cheers,
Lee

Re: svn commit: r799755 - in /maven/scm/trunk: pom.xml src/main/ src/main/assembly/ src/main/assembly/source-release.xml

[Benjamin Bentmann]

Brian Fox wrote:


On the infra list it seems like we'll be required to add
them to svn anyway


When we do, could we use a well-known file extension like .txt for these 
files? The source bundles we currently produce contain "LICENSE" and 
"NOTICE" and these are not easily opened on Windows without a file 
extension.



Benjamin

Re: svn commit: r799755 - in /maven/scm/trunk: pom.xml src/main/ src/main/assembly/ src/main/assembly/source-release.xml

[Brian Fox]

2009/7/31 Jason van Zyl :
> Ok, we need to figure out how to do this generally. I really don't want to 
> see this in every POM we have. Brian, is there no way to share this?
>

Yes there is. The problem was getting the license and notice files
included. On the infra list it seems like we'll be required to add
them to svn anyway so that will make it easier for me to wrap up.

Re: svn commit: r799755 - in /maven/scm/trunk: pom.xml src/main/ src/main/assembly/ src/main/assembly/source-release.xml

[Jason van Zyl]

Ok, we need to figure out how to do this generally. I really don't  
want to see this in every POM we have. Brian, is there no way to share  
this?


On 31-Jul-09, at 3:06 PM, ol...@apache.org wrote:


Author: olamy
Date: Fri Jul 31 22:06:43 2009
New Revision: 799755

URL: http://svn.apache.org/viewvc?rev=799755&view=rev
Log:
Add an ASF-compliant source release assembly

Added:
   maven/scm/trunk/src/main/
   maven/scm/trunk/src/main/assembly/
   maven/scm/trunk/src/main/assembly/source-release.xml   (with props)
Modified:
   maven/scm/trunk/pom.xml

Modified: maven/scm/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/maven/scm/trunk/pom.xml?rev=799755&r1=799754&r2=799755&view=diff
= 
= 
= 
= 
= 
= 
= 
= 
==

--- maven/scm/trunk/pom.xml (original)
+++ maven/scm/trunk/pom.xml Fri Jul 31 22:06:43 2009
@@ -318,5 +318,33 @@

  

+
+  release
+  
+
+  
+
+maven-assembly-plugin
+
+  
+make-project-src-distro
+package
+
+  single
+
+
+  
+   src/main/assembly/source- 
release.xml

+  
+  gnu
+
+  
+
+  
+
+  
+
  


Added: maven/scm/trunk/src/main/assembly/source-release.xml
URL: 
http://svn.apache.org/viewvc/maven/scm/trunk/src/main/assembly/source-release.xml?rev=799755&view=auto
= 
= 
= 
= 
= 
= 
= 
= 
==

--- maven/scm/trunk/src/main/assembly/source-release.xml (added)
+++ maven/scm/trunk/src/main/assembly/source-release.xml Fri Jul 31  
22:06:43 2009

@@ -0,0 +1,49 @@
+
+
+
+
+  source-release
+  
+tar.gz
+tar.bz2
+zip
+  
+  
+
+  ${project.basedir}
+  /
+  true
+  
+**/*.iws
+**/*.ipr
+**/*.iml
+*.log
+target/**
+**/.settings/**
+**/*.classpath
+**/*.project
+  
+
+
+  ${project.build.directory}/maven-shared-archive- 
resources/META-INF

+  /
+
+  
+

Propchange: maven/scm/trunk/src/main/assembly/source-release.xml
--
   svn:eol-style = native

Propchange: maven/scm/trunk/src/main/assembly/source-release.xml
--
   svn:keywords = Author Date Id Revision




Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
--

believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.

 -- Buddha

Re: [PATCH] Git Change log takes current path into account

[Imran M Yousuf]

On Mon, Apr 13, 2009 at 3:30 PM, Mark Struberg  wrote:
>
> Btw Imran, if you find such things then please file a Jira yourself so we'd 
> also have tracked your highly appreciated help as a git pro
> :)
>

Thanks for the hint :), I will do that in future as soon as I come
across it. Thank you too for quick responses with patches for the
issues that I have come up with in the past :).

Best regards,

Imran

> LieGrue,
> strub
>
> --- Mark Struberg  schrieb am Mo, 13.4.2009:
>
>> Von: Mark Struberg 
>> Betreff: Re: [PATCH] Git Change log takes current path into account
>> An: scm-dev@maven.apache.org
>> Datum: Montag, 13. April 2009, 11:22
>>
>> Hi Imran!
>>
>> Sorry that it took so long, but I was busy.
>>
>> > I would be grateful if you would kindly state an
>> example
>> > where it
>> > would not be sufficient with the change and was
>> without
>> > it.
>>
>> Benjamin pointed me to a page [1] where all those pitfalls
>> are listed.
>>
>> So what I'd do is to add a
>> -- ${basedir}
>> to the git-whatchanged command.
>>
>> I created a Jira [2] and attached my changes as patch.
>>
>> Please note that I've only tested this on Linux, so I'd be
>> glad if someone can test this on Win also? - txs!
>>
>>
>> LieGrue,
>> strub
>>
>> [1] 
>> http://maven.apache.org/plugin-developers/common-bugs.html#Resolving_Relative_Paths
>> [2] http://jira.codehaus.org/browse/SCM-458
>>
>> --- Imran M Yousuf 
>> schrieb am Di, 7.4.2009:
>>
>> > Von: Imran M Yousuf 
>> > Betreff: Re: [PATCH] Git Change log takes current path
>> into account
>> > An: "Mark Struberg" 
>> > CC: scm-dev@maven.apache.org
>> > Datum: Dienstag, 7. April 2009, 10:32
>> > On Tue, Apr 7, 2009 at 1:42 PM, Mark
>> > Struberg 
>> > wrote:
>> > >
>> > > Hi Imran!
>> > >
>> > > What is the special usecase for this?
>> > > Maybe multi-module builds where the current pom
>> is
>> > only 1 sub-module of the whole build?
>> > >
>> >
>> > It is not a special case but the usual case that I am
>> want
>> > it to work
>> > as it should :). Lets think of a multi-module build or
>> a
>> > project that
>> > has the pom.xml in a sub-directory of the project. I
>> will
>> > try to
>> > explain more with 2 examples.
>> >
>> > First, a single module project. Let us suppose that we
>> have
>> > a project
>> > tree as follows:
>> >
>> > root
>> > |->project
>> >      |->pom.xml
>> > |->some_other_stuff
>> >
>> > Now when maven will take changelog of it the history
>> > rationally should
>> > include only histories of the changes under 'project'
>> > sub-tree and not
>> > of all the project. Adding the '.' will do just that.
>> >
>> > Secondly, let us take a multi-module project. In that
>> case
>> > when a
>> > changelog is requested it should show the changes made
>> to
>> > that tree,
>> > and not whole project. Adding the '.' will do just
>> that.
>> >
>> > > I'm not really sure if we can safely assume to
>> always
>> > execute in the modules path. To be honest, I doubt it!
>> I
>> > have something in my mind, but I'm not sure which case
>> it
>> > was. Maybe CI builds, hmmm? In those cases a single
>> '.'
>> > would not be sufficient.
>> > >
>> >
>> > I would be grateful if you would kindly state an
>> example
>> > where it
>> > would not be sufficient with the change and was
>> without
>> > it.
>> >
>> > > And there is a really subtle difference with git
>> in
>> > releasing multi-module builds.
>> > >
>> >
>> > Yes that is true, but I do not see that effecting
>> release
>> > process :).
>> >
>> > > As you know, Git only handles full trees and not
>> > single files. So the behaviour of a release differes
>> if the
>> > git repo contains all the modules (including parent)
>> or if
>> > there is a git-submodule involved.
>> > >
>> >
>> > What I am not sure how does it adversely effect
>> release
>> > behavior? It
&

Re: [PATCH] Git Change log takes current path into account

[Mark Struberg]

Btw Imran, if you find such things then please file a Jira yourself so we'd 
also have tracked your highly appreciated help as a git pro 
:)

LieGrue,
strub

--- Mark Struberg  schrieb am Mo, 13.4.2009:

> Von: Mark Struberg 
> Betreff: Re: [PATCH] Git Change log takes current path into account
> An: scm-dev@maven.apache.org
> Datum: Montag, 13. April 2009, 11:22
> 
> Hi Imran!
> 
> Sorry that it took so long, but I was busy.
> 
> > I would be grateful if you would kindly state an
> example
> > where it
> > would not be sufficient with the change and was
> without
> > it.
> 
> Benjamin pointed me to a page [1] where all those pitfalls
> are listed.
> 
> So what I'd do is to add a
> -- ${basedir} 
> to the git-whatchanged command.
> 
> I created a Jira [2] and attached my changes as patch.
> 
> Please note that I've only tested this on Linux, so I'd be
> glad if someone can test this on Win also? - txs!
> 
> 
> LieGrue,
> strub
> 
> [1] 
> http://maven.apache.org/plugin-developers/common-bugs.html#Resolving_Relative_Paths
> [2] http://jira.codehaus.org/browse/SCM-458
> 
> --- Imran M Yousuf 
> schrieb am Di, 7.4.2009:
> 
> > Von: Imran M Yousuf 
> > Betreff: Re: [PATCH] Git Change log takes current path
> into account
> > An: "Mark Struberg" 
> > CC: scm-dev@maven.apache.org
> > Datum: Dienstag, 7. April 2009, 10:32
> > On Tue, Apr 7, 2009 at 1:42 PM, Mark
> > Struberg 
> > wrote:
> > >
> > > Hi Imran!
> > >
> > > What is the special usecase for this?
> > > Maybe multi-module builds where the current pom
> is
> > only 1 sub-module of the whole build?
> > >
> > 
> > It is not a special case but the usual case that I am
> want
> > it to work
> > as it should :). Lets think of a multi-module build or
> a
> > project that
> > has the pom.xml in a sub-directory of the project. I
> will
> > try to
> > explain more with 2 examples.
> > 
> > First, a single module project. Let us suppose that we
> have
> > a project
> > tree as follows:
> > 
> > root
> > |->project
> >      |->pom.xml
> > |->some_other_stuff
> > 
> > Now when maven will take changelog of it the history
> > rationally should
> > include only histories of the changes under 'project'
> > sub-tree and not
> > of all the project. Adding the '.' will do just that.
> > 
> > Secondly, let us take a multi-module project. In that
> case
> > when a
> > changelog is requested it should show the changes made
> to
> > that tree,
> > and not whole project. Adding the '.' will do just
> that.
> > 
> > > I'm not really sure if we can safely assume to
> always
> > execute in the modules path. To be honest, I doubt it!
> I
> > have something in my mind, but I'm not sure which case
> it
> > was. Maybe CI builds, hmmm? In those cases a single
> '.'
> > would not be sufficient.
> > >
> > 
> > I would be grateful if you would kindly state an
> example
> > where it
> > would not be sufficient with the change and was
> without
> > it.
> > 
> > > And there is a really subtle difference with git
> in
> > releasing multi-module builds.
> > >
> > 
> > Yes that is true, but I do not see that effecting
> release
> > process :).
> > 
> > > As you know, Git only handles full trees and not
> > single files. So the behaviour of a release differes
> if the
> > git repo contains all the modules (including parent)
> or if
> > there is a git-submodule involved.
> > >
> > 
> > What I am not sure how does it adversely effect
> release
> > behavior? It
> > is not clear to me.
> > 
> > > So there are most probably still a few things
> left to
> > do.
> > >
> > 
> > Please point them out and I will gladly help out. But
> this
> > is a change
> > I think would be beneficial to many not to mention
> that I
> > am eagerly
> > waiting to see its introduction :). Without this in a
> > multi-module
> > scenario changelog does not make much (if any at all)
> > sense.
> > 
> > Thank you,
> > 
> > > LieGrue,
> > > strub
> > >
> > > --- Imran M Yousuf 
> > schrieb am Di, 7.4.2009:
> > >
> > >> Von: Imran M Yousuf 
> > >> Betreff: [PATCH] Git Change log takes current
>

Re: [PATCH] Git Change log takes current path into account

[Mark Struberg]

Hi Imran!

Sorry that it took so long, but I was busy.

> I would be grateful if you would kindly state an example
> where it
> would not be sufficient with the change and was without
> it.

Benjamin pointed me to a page [1] where all those pitfalls are listed.

So what I'd do is to add a
-- ${basedir} 
to the git-whatchanged command.

I created a Jira [2] and attached my changes as patch.

Please note that I've only tested this on Linux, so I'd be glad if someone can 
test this on Win also? - txs!


LieGrue,
strub

[1] 
http://maven.apache.org/plugin-developers/common-bugs.html#Resolving_Relative_Paths
[2] http://jira.codehaus.org/browse/SCM-458

--- Imran M Yousuf  schrieb am Di, 7.4.2009:

> Von: Imran M Yousuf 
> Betreff: Re: [PATCH] Git Change log takes current path into account
> An: "Mark Struberg" 
> CC: scm-dev@maven.apache.org
> Datum: Dienstag, 7. April 2009, 10:32
> On Tue, Apr 7, 2009 at 1:42 PM, Mark
> Struberg 
> wrote:
> >
> > Hi Imran!
> >
> > What is the special usecase for this?
> > Maybe multi-module builds where the current pom is
> only 1 sub-module of the whole build?
> >
> 
> It is not a special case but the usual case that I am want
> it to work
> as it should :). Lets think of a multi-module build or a
> project that
> has the pom.xml in a sub-directory of the project. I will
> try to
> explain more with 2 examples.
> 
> First, a single module project. Let us suppose that we have
> a project
> tree as follows:
> 
> root
> |->project
>      |->pom.xml
> |->some_other_stuff
> 
> Now when maven will take changelog of it the history
> rationally should
> include only histories of the changes under 'project'
> sub-tree and not
> of all the project. Adding the '.' will do just that.
> 
> Secondly, let us take a multi-module project. In that case
> when a
> changelog is requested it should show the changes made to
> that tree,
> and not whole project. Adding the '.' will do just that.
> 
> > I'm not really sure if we can safely assume to always
> execute in the modules path. To be honest, I doubt it! I
> have something in my mind, but I'm not sure which case it
> was. Maybe CI builds, hmmm? In those cases a single '.'
> would not be sufficient.
> >
> 
> I would be grateful if you would kindly state an example
> where it
> would not be sufficient with the change and was without
> it.
> 
> > And there is a really subtle difference with git in
> releasing multi-module builds.
> >
> 
> Yes that is true, but I do not see that effecting release
> process :).
> 
> > As you know, Git only handles full trees and not
> single files. So the behaviour of a release differes if the
> git repo contains all the modules (including parent) or if
> there is a git-submodule involved.
> >
> 
> What I am not sure how does it adversely effect release
> behavior? It
> is not clear to me.
> 
> > So there are most probably still a few things left to
> do.
> >
> 
> Please point them out and I will gladly help out. But this
> is a change
> I think would be beneficial to many not to mention that I
> am eagerly
> waiting to see its introduction :). Without this in a
> multi-module
> scenario changelog does not make much (if any at all)
> sense.
> 
> Thank you,
> 
> > LieGrue,
> > strub
> >
> > --- Imran M Yousuf 
> schrieb am Di, 7.4.2009:
> >
> >> Von: Imran M Yousuf 
> >> Betreff: [PATCH] Git Change log takes current path
> into account
> >> An: scm-dev@maven.apache.org
> >> CC: "Mark Struberg" 
> >> Datum: Dienstag, 7. April 2009, 5:23
> >> Hi,
> >>
> >> I was just checking the commands generated by git
> changelog
> >> and I
> >> noticed that it does not respect the path, whereas
> it is
> >> very easy to
> >> integrate it, mentioning a simple '.' at the end
> of the
> >> 'git
> >> whatchanged' command does the trick and thats what
> the
> >> attached patch
> >> does.
> >>
> >> I would be grateful if this would be integrated
> with the
> >> current
> >> version as this change has a grave positive effect
> on maven
> >> site's
> >> changelog report.
> >>
> >> Thank you,
> >>
> >> --
> >> Imran M Yousuf
> >> Entrepreneur & Software Engineer
> >> Smart IT Engineering
> >> Dhaka, Bangladesh
> >> Email: im...@smartitengineering.com
> >> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> >> Mobile: +880-1711402557
> >>
> >
> >
> >
> >
> 
> 
> 
> -- 
> Imran M Yousuf
> Entrepreneur & Software Engineer
> Smart IT Engineering
> Dhaka, Bangladesh
> Email: im...@smartitengineering.com
> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> Mobile: +880-1711402557
> 

Re: [PATCH] Git Change log takes current path into account

[Imran M Yousuf]

On Tue, Apr 7, 2009 at 1:42 PM, Mark Struberg  wrote:
>
> Hi Imran!
>
> What is the special usecase for this?
> Maybe multi-module builds where the current pom is only 1 sub-module of the 
> whole build?
>

It is not a special case but the usual case that I am want it to work
as it should :). Lets think of a multi-module build or a project that
has the pom.xml in a sub-directory of the project. I will try to
explain more with 2 examples.

First, a single module project. Let us suppose that we have a project
tree as follows:

root
|->project
 |->pom.xml
|->some_other_stuff

Now when maven will take changelog of it the history rationally should
include only histories of the changes under 'project' sub-tree and not
of all the project. Adding the '.' will do just that.

Secondly, let us take a multi-module project. In that case when a
changelog is requested it should show the changes made to that tree,
and not whole project. Adding the '.' will do just that.

> I'm not really sure if we can safely assume to always execute in the modules 
> path. To be honest, I doubt it! I have something in my mind, but I'm not sure 
> which case it was. Maybe CI builds, hmmm? In those cases a single '.' would 
> not be sufficient.
>

I would be grateful if you would kindly state an example where it
would not be sufficient with the change and was without it.

> And there is a really subtle difference with git in releasing multi-module 
> builds.
>

Yes that is true, but I do not see that effecting release process :).

> As you know, Git only handles full trees and not single files. So the 
> behaviour of a release differes if the git repo contains all the modules 
> (including parent) or if there is a git-submodule involved.
>

What I am not sure how does it adversely effect release behavior? It
is not clear to me.

> So there are most probably still a few things left to do.
>

Please point them out and I will gladly help out. But this is a change
I think would be beneficial to many not to mention that I am eagerly
waiting to see its introduction :). Without this in a multi-module
scenario changelog does not make much (if any at all) sense.

Thank you,

> LieGrue,
> strub
>
> --- Imran M Yousuf  schrieb am Di, 7.4.2009:
>
>> Von: Imran M Yousuf 
>> Betreff: [PATCH] Git Change log takes current path into account
>> An: scm-dev@maven.apache.org
>> CC: "Mark Struberg" 
>> Datum: Dienstag, 7. April 2009, 5:23
>> Hi,
>>
>> I was just checking the commands generated by git changelog
>> and I
>> noticed that it does not respect the path, whereas it is
>> very easy to
>> integrate it, mentioning a simple '.' at the end of the
>> 'git
>> whatchanged' command does the trick and thats what the
>> attached patch
>> does.
>>
>> I would be grateful if this would be integrated with the
>> current
>> version as this change has a grave positive effect on maven
>> site's
>> changelog report.
>>
>> Thank you,
>>
>> --
>> Imran M Yousuf
>> Entrepreneur & Software Engineer
>> Smart IT Engineering
>> Dhaka, Bangladesh
>> Email: im...@smartitengineering.com
>> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
>> Mobile: +880-1711402557
>>
>
>
>
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

Re: [PATCH] Git Change log takes current path into account

[Imran M Yousuf]

FYI, please check the following site to see the patch in action.
http://imyousuf.github.com/smart-dao/site/index.html

Thank you,

- Imran

On Tue, Apr 7, 2009 at 9:23 AM, Imran M Yousuf  wrote:
> Hi,
>
> I was just checking the commands generated by git changelog and I
> noticed that it does not respect the path, whereas it is very easy to
> integrate it, mentioning a simple '.' at the end of the 'git
> whatchanged' command does the trick and thats what the attached patch
> does.
>
> I would be grateful if this would be integrated with the current
> version as this change has a grave positive effect on maven site's
> changelog report.
>
> Thank you,
>
> --
> Imran M Yousuf
> Entrepreneur & Software Engineer
> Smart IT Engineering
> Dhaka, Bangladesh
> Email: im...@smartitengineering.com
> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> Mobile: +880-1711402557
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

RE: Re: accurev provider

[Rodriguez, Pedro]

The plugin version submitted by Grant (JIRA SCM-445) is already more
completed than the current available version. 

I'm currently using the release plugin with it and it works!

The url change was required to implement the additional accurev
commands. No sure about compatibility with previous version (if this is
what you meant by "effect of the new URL syntax").  

In fact, I was only able to use the plugin release with Accurev after
Grant contribution.

Pedro



 Original Message ----

Subject: Re: accurev provider

Date: Wed, 1 Apr 2009 01:56:19 +1100

From: Brett Porter 

To: scm-dev@maven.apache.org



Do the authors of the original provider, or other users here, have an

opinion on this? I like that it is more complete (functionally, and in

docs and tests), however am not an accurev user myself.



What effect does the URL syntax change have?



Also Grant, I haven't seen the CLA yet?



- Brett

Re: accurev provider

[Grant Gardner]

I faxed in the CLA today. Also uploaded a new version to the JIRA that
fixes a few bugs under Windows.

Grant.


On Wed, 1 Apr 2009 01:56:19 +1100, Brett Porter  wrote:
> Do the authors of the original provider, or other users here, have an
> opinion on this? I like that it is more complete (functionally, and in
> docs and tests), however am not an accurev user myself.
> 
> What effect does the URL syntax change have?
> 
> Also Grant, I haven't seen the CLA yet?
> 
> - Brett
> 
> On 17/03/2009, at 11:58 PM, Grant Gardner wrote:
> 
>>
>>
>> I've created the jira with attached code. Let me know if there's
>> anything
>> else I need to do.
>> http://jira.codehaus.org/browse/SCM-445
>>
>> Will do the CLA when I find myself conveniently located near a fax or
>> scanner.
>>

Re: A probable bug in git scm provider for maven-scm-plugin

[Imran M Yousuf]

On Wed, Apr 1, 2009 at 1:48 PM, Mark Struberg  wrote:
>
> cool, I've attached a patch in SCM-454.
> Can you please test this?
>

Yup, that works as well :).

Thanks,

Imran

> txs and LieGrue,
> strub
>
> --- Imran M Yousuf  schrieb am Mi, 1.4.2009:
>
>> Von: Imran M Yousuf 
>> Betreff: Re: A probable bug in git scm provider for maven-scm-plugin
>> An: scm-dev@maven.apache.org
>> Datum: Mittwoch, 1. April 2009, 9:45
>> On Wed, Apr 1, 2009 at 12:39 PM, Mark
>> Struberg 
>> wrote:
>> >
>> > Hi Imran!
>> >
>> > I did almost the same changes yesterday evening, but
>> hadn't got a chance to send them yet them.
>> >
>> > I've additionally added the missing branch handling
>> and will add the patch to the corresponding JIRA.
>> >
>>
>> Great, let me know when its in trunk, I will update and
>> test it.
>>
>> Thank you,
>>
>> Imran
>>
>> > LieGrue,
>> > strub
>> >
>> > --- Imran M Yousuf 
>> schrieb am Mi, 1.4.2009:
>> >
>> >> Von: Imran M Yousuf 
>> >> Betreff: Re: A probable bug in git scm provider
>> for maven-scm-plugin
>> >> An: scm-dev@maven.apache.org
>> >> CC: "Mark Struberg" 
>> >> Datum: Mittwoch, 1. April 2009, 6:50
>> >> Hi,
>> >>
>> >> I have made the required changes to gitexe
>> implementation
>> >> and
>> >> corresponding test case and also tested it with my
>> scenario
>> >> and it
>> >> works fine. Please have a look at it and let me
>> know what
>> >> you think.
>> >>
>> >> Best regards,
>> >>
>> >> Imran
>> >>
>> >> On Tue, Mar 31, 2009 at 3:39 PM, Imran M Yousuf
>> 
>> >> wrote:
>> >> > On Tue, Mar 31, 2009 at 2:57 PM, Mark
>> Struberg 
>> >> wrote:
>> >> >>
>> >> >> Hi Imran!
>> >> >>
>> >> >> I recently changed the command back from
>> git-log
>> >> to git-whatchanged because I originally programmed
>> the
>> >> output consumer to fit git-whatchanged. Don't know
>> anymore
>> >> when we did this, but the git-log output hasn't
>> been
>> >> parseable with the GitLogConsumer for a while :(
>> >> >>
>> >> >> From the man git-whatchanged
>> (git-1.6.0.6) --since
>> >> should be supported:
>> >> >>> git whatchanged --since="2 weeks ago"
>> -- gitk
>> >> >>
>> >> >
>> >> > Right, this is an example in the man pages,
>> but as I
>> >> said --since
>> >> > expects date or date like expressions
>> (probably) but
>> >> not tags or
>> >> > revision sha1. I have tried it several times
>> >> unfortunately and that
>> >> > also with both 1.5.6 and 1.6.2.1.
>> >> >
>> >> > Please let me know what you think about the
>> changes I
>> >> sent you,
>> >> > because I believe they will solve the issue.
>> >> >
>> >> > Thank you,
>> >> >
>> >> > Imran
>> >> >
>> >> >> If you look at the git code it should
>> take the
>> >> --since and --until!
>> >> >> This is also backed up with the comment
>> in the man
>> >> page:
>> >> >>> The command internally invokes
>> git-rev-list
>> >> piped to
>> >> >>> git-diff-tree, and takes command line
>> options
>> >> for both
>> >> >>> of these commands.
>> >> >>
>> >> >> So imho --since and --until should work.
>> >> >>
>> >> >> Can you please try the git-whatchanged on
>> the
>> >> commandline again and play with the since date to
>> see if the
>> >> output changes? - txs!
>> >> >>
>> >> >> But maybe we trapped another error the
>> code
>> >> suffers from!
>> >> >>
>> >> >> LieGrue,
>> >> >> strub
>> >> >>
>> >> >>
>> >> >> --- Imran M Yousuf 
>> >> schrieb am Di, 31.3.2009:
>> >> >>
>> >> >>> Von: Imran M Yo

Re: A probable bug in git scm provider for maven-scm-plugin

[Mark Struberg]

cool, I've attached a patch in SCM-454.
Can you please test this?

txs and LieGrue,
strub

--- Imran M Yousuf  schrieb am Mi, 1.4.2009:

> Von: Imran M Yousuf 
> Betreff: Re: A probable bug in git scm provider for maven-scm-plugin
> An: scm-dev@maven.apache.org
> Datum: Mittwoch, 1. April 2009, 9:45
> On Wed, Apr 1, 2009 at 12:39 PM, Mark
> Struberg 
> wrote:
> >
> > Hi Imran!
> >
> > I did almost the same changes yesterday evening, but
> hadn't got a chance to send them yet them.
> >
> > I've additionally added the missing branch handling
> and will add the patch to the corresponding JIRA.
> >
> 
> Great, let me know when its in trunk, I will update and
> test it.
> 
> Thank you,
> 
> Imran
> 
> > LieGrue,
> > strub
> >
> > --- Imran M Yousuf 
> schrieb am Mi, 1.4.2009:
> >
> >> Von: Imran M Yousuf 
> >> Betreff: Re: A probable bug in git scm provider
> for maven-scm-plugin
> >> An: scm-dev@maven.apache.org
> >> CC: "Mark Struberg" 
> >> Datum: Mittwoch, 1. April 2009, 6:50
> >> Hi,
> >>
> >> I have made the required changes to gitexe
> implementation
> >> and
> >> corresponding test case and also tested it with my
> scenario
> >> and it
> >> works fine. Please have a look at it and let me
> know what
> >> you think.
> >>
> >> Best regards,
> >>
> >> Imran
> >>
> >> On Tue, Mar 31, 2009 at 3:39 PM, Imran M Yousuf
> 
> >> wrote:
> >> > On Tue, Mar 31, 2009 at 2:57 PM, Mark
> Struberg 
> >> wrote:
> >> >>
> >> >> Hi Imran!
> >> >>
> >> >> I recently changed the command back from
> git-log
> >> to git-whatchanged because I originally programmed
> the
> >> output consumer to fit git-whatchanged. Don't know
> anymore
> >> when we did this, but the git-log output hasn't
> been
> >> parseable with the GitLogConsumer for a while :(
> >> >>
> >> >> From the man git-whatchanged
> (git-1.6.0.6) --since
> >> should be supported:
> >> >>> git whatchanged --since="2 weeks ago"
> -- gitk
> >> >>
> >> >
> >> > Right, this is an example in the man pages,
> but as I
> >> said --since
> >> > expects date or date like expressions
> (probably) but
> >> not tags or
> >> > revision sha1. I have tried it several times
> >> unfortunately and that
> >> > also with both 1.5.6 and 1.6.2.1.
> >> >
> >> > Please let me know what you think about the
> changes I
> >> sent you,
> >> > because I believe they will solve the issue.
> >> >
> >> > Thank you,
> >> >
> >> > Imran
> >> >
> >> >> If you look at the git code it should
> take the
> >> --since and --until!
> >> >> This is also backed up with the comment
> in the man
> >> page:
> >> >>> The command internally invokes
> git-rev-list
> >> piped to
> >> >>> git-diff-tree, and takes command line
> options
> >> for both
> >> >>> of these commands.
> >> >>
> >> >> So imho --since and --until should work.
> >> >>
> >> >> Can you please try the git-whatchanged on
> the
> >> commandline again and play with the since date to
> see if the
> >> output changes? - txs!
> >> >>
> >> >> But maybe we trapped another error the
> code
> >> suffers from!
> >> >>
> >> >> LieGrue,
> >> >> strub
> >> >>
> >> >>
> >> >> --- Imran M Yousuf 
> >> schrieb am Di, 31.3.2009:
> >> >>
> >> >>> Von: Imran M Yousuf 
> >> >>> Betreff: A probable bug in git scm
> provider
> >> for maven-scm-plugin
> >> >>> An: scm-dev@maven.apache.org
> >> >>> CC: strub...@yahoo.de
> >> >>> Datum: Dienstag, 31. März 2009,
> 6:17
> >> >>> Hi,
> >> >>>
> >> >>> When I use the
> tag in
> >> changelog
> >> >>> configuration (its at the
> >> >>> end of the email), it uses the
> following query
> >> for
> >> >>> generating the
> >> >>> changeset -
> >>

Re: A probable bug in git scm provider for maven-scm-plugin

[Imran M Yousuf]

On Wed, Apr 1, 2009 at 12:39 PM, Mark Struberg  wrote:
>
> Hi Imran!
>
> I did almost the same changes yesterday evening, but hadn't got a chance to 
> send them yet them.
>
> I've additionally added the missing branch handling and will add the patch to 
> the corresponding JIRA.
>

Great, let me know when its in trunk, I will update and test it.

Thank you,

Imran

> LieGrue,
> strub
>
> --- Imran M Yousuf  schrieb am Mi, 1.4.2009:
>
>> Von: Imran M Yousuf 
>> Betreff: Re: A probable bug in git scm provider for maven-scm-plugin
>> An: scm-dev@maven.apache.org
>> CC: "Mark Struberg" 
>> Datum: Mittwoch, 1. April 2009, 6:50
>> Hi,
>>
>> I have made the required changes to gitexe implementation
>> and
>> corresponding test case and also tested it with my scenario
>> and it
>> works fine. Please have a look at it and let me know what
>> you think.
>>
>> Best regards,
>>
>> Imran
>>
>> On Tue, Mar 31, 2009 at 3:39 PM, Imran M Yousuf 
>> wrote:
>> > On Tue, Mar 31, 2009 at 2:57 PM, Mark Struberg 
>> wrote:
>> >>
>> >> Hi Imran!
>> >>
>> >> I recently changed the command back from git-log
>> to git-whatchanged because I originally programmed the
>> output consumer to fit git-whatchanged. Don't know anymore
>> when we did this, but the git-log output hasn't been
>> parseable with the GitLogConsumer for a while :(
>> >>
>> >> From the man git-whatchanged (git-1.6.0.6) --since
>> should be supported:
>> >>> git whatchanged --since="2 weeks ago" -- gitk
>> >>
>> >
>> > Right, this is an example in the man pages, but as I
>> said --since
>> > expects date or date like expressions (probably) but
>> not tags or
>> > revision sha1. I have tried it several times
>> unfortunately and that
>> > also with both 1.5.6 and 1.6.2.1.
>> >
>> > Please let me know what you think about the changes I
>> sent you,
>> > because I believe they will solve the issue.
>> >
>> > Thank you,
>> >
>> > Imran
>> >
>> >> If you look at the git code it should take the
>> --since and --until!
>> >> This is also backed up with the comment in the man
>> page:
>> >>> The command internally invokes git-rev-list
>> piped to
>> >>> git-diff-tree, and takes command line options
>> for both
>> >>> of these commands.
>> >>
>> >> So imho --since and --until should work.
>> >>
>> >> Can you please try the git-whatchanged on the
>> commandline again and play with the since date to see if the
>> output changes? - txs!
>> >>
>> >> But maybe we trapped another error the code
>> suffers from!
>> >>
>> >> LieGrue,
>> >> strub
>> >>
>> >>
>> >> --- Imran M Yousuf 
>> schrieb am Di, 31.3.2009:
>> >>
>> >>> Von: Imran M Yousuf 
>> >>> Betreff: A probable bug in git scm provider
>> for maven-scm-plugin
>> >>> An: scm-dev@maven.apache.org
>> >>> CC: strub...@yahoo.de
>> >>> Datum: Dienstag, 31. März 2009, 6:17
>> >>> Hi,
>> >>>
>> >>> When I use the tag in
>> changelog
>> >>> configuration (its at the
>> >>> end of the email), it uses the following query
>> for
>> >>> generating the
>> >>> changeset -
>> >>>
>> >>> git whatchanged --since=0.3 --until=HEAD
>> --date=iso
>> >>>
>> >>> While 'git help whatchanged' says nothing
>> about '--since'
>> >>> but the 'git
>> >>> help log' says that '--since' is to be a date,
>> thus IMHO,
>> >>> the
>> >>> implementation should have been something like
>> -
>> >>>
>> >>> git whatchanged 0.3...HEAD --date=iso
>> >>>
>> >>> I also checked the source code of the
>> changelog and it is
>> >>> using the
>> >>> following method-
>> >>>
>> >>> changeLog(ScmRepository repository, ScmFileSet
>> fileSet,
>> >>> ScmVersion
>> >>> startVersion, ScmVersion endVersion)
>> >>> http://maven.apache.org/scm/projects/apidocs/org/apache/maven/scm/provid

Re: A probable bug in git scm provider for maven-scm-plugin

[Mark Struberg]

Hi Imran!

I did almost the same changes yesterday evening, but hadn't got a chance to 
send them yet them.

I've additionally added the missing branch handling and will add the patch to 
the corresponding JIRA.

LieGrue,
strub

--- Imran M Yousuf  schrieb am Mi, 1.4.2009:

> Von: Imran M Yousuf 
> Betreff: Re: A probable bug in git scm provider for maven-scm-plugin
> An: scm-dev@maven.apache.org
> CC: "Mark Struberg" 
> Datum: Mittwoch, 1. April 2009, 6:50
> Hi,
> 
> I have made the required changes to gitexe implementation
> and
> corresponding test case and also tested it with my scenario
> and it
> works fine. Please have a look at it and let me know what
> you think.
> 
> Best regards,
> 
> Imran
> 
> On Tue, Mar 31, 2009 at 3:39 PM, Imran M Yousuf 
> wrote:
> > On Tue, Mar 31, 2009 at 2:57 PM, Mark Struberg 
> wrote:
> >>
> >> Hi Imran!
> >>
> >> I recently changed the command back from git-log
> to git-whatchanged because I originally programmed the
> output consumer to fit git-whatchanged. Don't know anymore
> when we did this, but the git-log output hasn't been
> parseable with the GitLogConsumer for a while :(
> >>
> >> From the man git-whatchanged (git-1.6.0.6) --since
> should be supported:
> >>> git whatchanged --since="2 weeks ago" -- gitk
> >>
> >
> > Right, this is an example in the man pages, but as I
> said --since
> > expects date or date like expressions (probably) but
> not tags or
> > revision sha1. I have tried it several times
> unfortunately and that
> > also with both 1.5.6 and 1.6.2.1.
> >
> > Please let me know what you think about the changes I
> sent you,
> > because I believe they will solve the issue.
> >
> > Thank you,
> >
> > Imran
> >
> >> If you look at the git code it should take the
> --since and --until!
> >> This is also backed up with the comment in the man
> page:
> >>> The command internally invokes git-rev-list
> piped to
> >>> git-diff-tree, and takes command line options
> for both
> >>> of these commands.
> >>
> >> So imho --since and --until should work.
> >>
> >> Can you please try the git-whatchanged on the
> commandline again and play with the since date to see if the
> output changes? - txs!
> >>
> >> But maybe we trapped another error the code
> suffers from!
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >> --- Imran M Yousuf 
> schrieb am Di, 31.3.2009:
> >>
> >>> Von: Imran M Yousuf 
> >>> Betreff: A probable bug in git scm provider
> for maven-scm-plugin
> >>> An: scm-dev@maven.apache.org
> >>> CC: strub...@yahoo.de
> >>> Datum: Dienstag, 31. März 2009, 6:17
> >>> Hi,
> >>>
> >>> When I use the tag in
> changelog
> >>> configuration (its at the
> >>> end of the email), it uses the following query
> for
> >>> generating the
> >>> changeset -
> >>>
> >>> git whatchanged --since=0.3 --until=HEAD
> --date=iso
> >>>
> >>> While 'git help whatchanged' says nothing
> about '--since'
> >>> but the 'git
> >>> help log' says that '--since' is to be a date,
> thus IMHO,
> >>> the
> >>> implementation should have been something like
> -
> >>>
> >>> git whatchanged 0.3...HEAD --date=iso
> >>>
> >>> I also checked the source code of the
> changelog and it is
> >>> using the
> >>> following method-
> >>>
> >>> changeLog(ScmRepository repository, ScmFileSet
> fileSet,
> >>> ScmVersion
> >>> startVersion, ScmVersion endVersion)
> >>> http://maven.apache.org/scm/projects/apidocs/org/apache/maven/scm/provider/ScmProvider.html#changeLog(org.apache.maven.scm.repository.ScmRepository,%20org.apache.maven.scm.ScmFileSet,%20org.apache.maven.scm.ScmVersion,%20org.apache.maven.scm.ScmVersion)
> >>>
> >>> Which IMHO, is the correct one to use. I will
> try to check
> >>> the gitexe
> >>> code today to see whether I can fix it or not.
> Please let
> >>> me know what
> >>> you think about the problem.
> >>>
> >>> Thank you,
> >>>
> >>> --
> >>> Imran M Yousuf
> >>> Entrepreneur & Software Engineer
> >>> Smart IT Engineering
> >>> Dhaka, Bangladesh
> >>> Email: im...@smartitengineering.com
> >>> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> >>> Mobile: +880-1711402557
> >>>
> >>
> >>
> >>
> >>
> >
> >
> >
> > --
> > Imran M Yousuf
> > Entrepreneur & Software Engineer
> > Smart IT Engineering
> > Dhaka, Bangladesh
> > Email: im...@smartitengineering.com
> > Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> > Mobile: +880-1711402557
> >
> 
> 
> 
> -- 
> Imran M Yousuf
> Entrepreneur & Software Engineer
> Smart IT Engineering
> Dhaka, Bangladesh
> Email: im...@smartitengineering.com
> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> Mobile: +880-1711402557
> 

Re: A probable bug in git scm provider for maven-scm-plugin

[Imran M Yousuf]

Hi,

I have made the required changes to gitexe implementation and
corresponding test case and also tested it with my scenario and it
works fine. Please have a look at it and let me know what you think.

Best regards,

Imran

On Tue, Mar 31, 2009 at 3:39 PM, Imran M Yousuf  wrote:
> On Tue, Mar 31, 2009 at 2:57 PM, Mark Struberg  wrote:
>>
>> Hi Imran!
>>
>> I recently changed the command back from git-log to git-whatchanged because 
>> I originally programmed the output consumer to fit git-whatchanged. Don't 
>> know anymore when we did this, but the git-log output hasn't been parseable 
>> with the GitLogConsumer for a while :(
>>
>> From the man git-whatchanged (git-1.6.0.6) --since should be supported:
>>> git whatchanged --since="2 weeks ago" -- gitk
>>
>
> Right, this is an example in the man pages, but as I said --since
> expects date or date like expressions (probably) but not tags or
> revision sha1. I have tried it several times unfortunately and that
> also with both 1.5.6 and 1.6.2.1.
>
> Please let me know what you think about the changes I sent you,
> because I believe they will solve the issue.
>
> Thank you,
>
> Imran
>
>> If you look at the git code it should take the --since and --until!
>> This is also backed up with the comment in the man page:
>>> The command internally invokes git-rev-list piped to
>>> git-diff-tree, and takes command line options for both
>>> of these commands.
>>
>> So imho --since and --until should work.
>>
>> Can you please try the git-whatchanged on the commandline again and play 
>> with the since date to see if the output changes? - txs!
>>
>> But maybe we trapped another error the code suffers from!
>>
>> LieGrue,
>> strub
>>
>>
>> --- Imran M Yousuf  schrieb am Di, 31.3.2009:
>>
>>> Von: Imran M Yousuf 
>>> Betreff: A probable bug in git scm provider for maven-scm-plugin
>>> An: scm-dev@maven.apache.org
>>> CC: strub...@yahoo.de
>>> Datum: Dienstag, 31. März 2009, 6:17
>>> Hi,
>>>
>>> When I use the tag in changelog
>>> configuration (its at the
>>> end of the email), it uses the following query for
>>> generating the
>>> changeset -
>>>
>>> git whatchanged --since=0.3 --until=HEAD --date=iso
>>>
>>> While 'git help whatchanged' says nothing about '--since'
>>> but the 'git
>>> help log' says that '--since' is to be a date, thus IMHO,
>>> the
>>> implementation should have been something like -
>>>
>>> git whatchanged 0.3...HEAD --date=iso
>>>
>>> I also checked the source code of the changelog and it is
>>> using the
>>> following method-
>>>
>>> changeLog(ScmRepository repository, ScmFileSet fileSet,
>>> ScmVersion
>>> startVersion, ScmVersion endVersion)
>>> http://maven.apache.org/scm/projects/apidocs/org/apache/maven/scm/provider/ScmProvider.html#changeLog(org.apache.maven.scm.repository.ScmRepository,%20org.apache.maven.scm.ScmFileSet,%20org.apache.maven.scm.ScmVersion,%20org.apache.maven.scm.ScmVersion)
>>>
>>> Which IMHO, is the correct one to use. I will try to check
>>> the gitexe
>>> code today to see whether I can fix it or not. Please let
>>> me know what
>>> you think about the problem.
>>>
>>> Thank you,
>>>
>>> --
>>> Imran M Yousuf
>>> Entrepreneur & Software Engineer
>>> Smart IT Engineering
>>> Dhaka, Bangladesh
>>> Email: im...@smartitengineering.com
>>> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
>>> Mobile: +880-1711402557
>>>
>>
>>
>>
>>
>
>
>
> --
> Imran M Yousuf
> Entrepreneur & Software Engineer
> Smart IT Engineering
> Dhaka, Bangladesh
> Email: im...@smartitengineering.com
> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> Mobile: +880-1711402557
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557
# This patch file was generated by NetBeans IDE
# Following Index: paths are relative to: /home/imyousuf/projects/maven-scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe
# This patch can be applied using context Tools: Patch action on respective folder.
# It uses platform neutral UTF-8 encoding and \n newlines.
# Above lines and this line are ignored by the patching process.
Index: src/main/java/org/apache/maven/scm/provider/git/gitexe/command/changelog/GitChangeLogCommand.java
--- src/main/java/org/apache/maven/scm/provider/git/gitexe/command/changelog/GitChangeLogCommand.java Base (BASE)
+++ src/main/java/org/apache/maven/scm/provider/git/gitexe/command/changelog/GitChangeLogCommand.java Locally Modified (Based On LOCAL)
@@ -110,30 +110,32 @@
 
 Commandline cl = GitCommandLineUtils.getBaseGitCommandLine( workingDirectory, "whatchanged" );
 
-if ( startVersion != null )
+if ( startVersion != null || endVersion != null )
 {
-cl.createArg().setValue( "--since=" + StringUtils.escape( startVersion.getName() ) );
+StringBuilder builder = new StringBuilder();
+	if ( startV

Re: accurev provider

[Brett Porter]

Do the authors of the original provider, or other users here, have an  
opinion on this? I like that it is more complete (functionally, and in  
docs and tests), however am not an accurev user myself.


What effect does the URL syntax change have?

Also Grant, I haven't seen the CLA yet?

- Brett

On 17/03/2009, at 11:58 PM, Grant Gardner wrote:




I've created the jira with attached code. Let me know if there's  
anything

else I need to do.
http://jira.codehaus.org/browse/SCM-445

Will do the CLA when I find myself conveniently located near a fax or
scanner.

On Mon, 9 Mar 2009 05:02:15 +1100, Brett Porter   
wrote:

1) Create a JIRA ticket under SCM
2) you might like to submit a CLA - you can do it regardless, and if
the work is accepted such a large chunk would probably require it  
(see

http://www.apache.org/licenses/
 and specifically http://www.apache.org/licenses/icla.txt)

Thanks!

- Brett

On 07/03/2009, at 12:50 PM, Grant Gardner wrote:




Hi, I've got my AccuRev provider to a point where both the release
plugin
and Continuum are working (for me).

Includes unit tests and tck tests for all the implemented commands.

How do I go about contributing the code?.

Grant.




--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/

Re: A probable bug in git scm provider for maven-scm-plugin

[Imran M Yousuf]

On Tue, Mar 31, 2009 at 2:57 PM, Mark Struberg  wrote:
>
> Hi Imran!
>
> I recently changed the command back from git-log to git-whatchanged because I 
> originally programmed the output consumer to fit git-whatchanged. Don't know 
> anymore when we did this, but the git-log output hasn't been parseable with 
> the GitLogConsumer for a while :(
>
> From the man git-whatchanged (git-1.6.0.6) --since should be supported:
>> git whatchanged --since="2 weeks ago" -- gitk
>

Right, this is an example in the man pages, but as I said --since
expects date or date like expressions (probably) but not tags or
revision sha1. I have tried it several times unfortunately and that
also with both 1.5.6 and 1.6.2.1.

Please let me know what you think about the changes I sent you,
because I believe they will solve the issue.

Thank you,

Imran

> If you look at the git code it should take the --since and --until!
> This is also backed up with the comment in the man page:
>> The command internally invokes git-rev-list piped to
>> git-diff-tree, and takes command line options for both
>> of these commands.
>
> So imho --since and --until should work.
>
> Can you please try the git-whatchanged on the commandline again and play with 
> the since date to see if the output changes? - txs!
>
> But maybe we trapped another error the code suffers from!
>
> LieGrue,
> strub
>
>
> --- Imran M Yousuf  schrieb am Di, 31.3.2009:
>
>> Von: Imran M Yousuf 
>> Betreff: A probable bug in git scm provider for maven-scm-plugin
>> An: scm-dev@maven.apache.org
>> CC: strub...@yahoo.de
>> Datum: Dienstag, 31. März 2009, 6:17
>> Hi,
>>
>> When I use the tag in changelog
>> configuration (its at the
>> end of the email), it uses the following query for
>> generating the
>> changeset -
>>
>> git whatchanged --since=0.3 --until=HEAD --date=iso
>>
>> While 'git help whatchanged' says nothing about '--since'
>> but the 'git
>> help log' says that '--since' is to be a date, thus IMHO,
>> the
>> implementation should have been something like -
>>
>> git whatchanged 0.3...HEAD --date=iso
>>
>> I also checked the source code of the changelog and it is
>> using the
>> following method-
>>
>> changeLog(ScmRepository repository, ScmFileSet fileSet,
>> ScmVersion
>> startVersion, ScmVersion endVersion)
>> http://maven.apache.org/scm/projects/apidocs/org/apache/maven/scm/provider/ScmProvider.html#changeLog(org.apache.maven.scm.repository.ScmRepository,%20org.apache.maven.scm.ScmFileSet,%20org.apache.maven.scm.ScmVersion,%20org.apache.maven.scm.ScmVersion)
>>
>> Which IMHO, is the correct one to use. I will try to check
>> the gitexe
>> code today to see whether I can fix it or not. Please let
>> me know what
>> you think about the problem.
>>
>> Thank you,
>>
>> --
>> Imran M Yousuf
>> Entrepreneur & Software Engineer
>> Smart IT Engineering
>> Dhaka, Bangladesh
>> Email: im...@smartitengineering.com
>> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
>> Mobile: +880-1711402557
>>
>
>
>
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

Re: A probable bug in git scm provider for maven-scm-plugin

[Imran M Yousuf]

On Tue, Mar 31, 2009 at 10:17 AM, Imran M Yousuf  wrote:
> Hi,
>
> When I use the tag in changelog configuration (its at the
> end of the email), it uses the following query for generating the
> changeset -
>
> git whatchanged --since=0.3 --until=HEAD --date=iso
>
> While 'git help whatchanged' says nothing about '--since' but the 'git
> help log' says that '--since' is to be a date, thus IMHO, the
> implementation should have been something like -
>
> git whatchanged 0.3...HEAD --date=iso
>
> I also checked the source code of the changelog and it is using the
> following method-
>
> changeLog(ScmRepository repository, ScmFileSet fileSet, ScmVersion
> startVersion, ScmVersion endVersion)
> http://maven.apache.org/scm/projects/apidocs/org/apache/maven/scm/provider/ScmProvider.html#changeLog(org.apache.maven.scm.repository.ScmRepository,%20org.apache.maven.scm.ScmFileSet,%20org.apache.maven.scm.ScmVersion,%20org.apache.maven.scm.ScmVersion)
>
> Which IMHO, is the correct one to use. I will try to check the gitexe
> code today to see whether I can fix it or not. Please let me know what
> you think about the problem.
>

I already worked on it but was not able to compile and test it, but
this is just for RFC. Please have a look and let me know what you
think. I missed the configuration that caused the error adding it as
follows:


org.apache.maven.plugins
maven-changelog-plugin
${changelog.version}
false


org.codehaus.plexus
plexus-utils
${plexus-utils.version}




attach-changelog
install

changelog









org.apache.maven.plugins
maven-changelog-plugin
${changelog.version}

tag

0.3

HEAD







Thank you,

Imran

> Thank you,
>
> --
> Imran M Yousuf
> Entrepreneur & Software Engineer
> Smart IT Engineering
> Dhaka, Bangladesh
> Email: im...@smartitengineering.com
> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> Mobile: +880-1711402557
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557
113c113
< if ( startVersion != null || endVersion != null )
---
> if ( startVersion != null )
115,124c115
< StringBuilder builder = new StringBuilder();
<   if ( startVersion != null ) {
< builder.append(startVersion.getName());
<   builder.append("...");
< }
< if ( endVersion != null )
<   {
<   builder.append(endVersion.getName());
<   }
<   cl.createArg().setValue( StringUtils.escape( builder.toString() ) );
---
> cl.createArg().setValue( "--since=" + StringUtils.escape( 
> startVersion.getName() ) );
131a123,130
> }
> 
> if ( endVersion != null )
> {
> cl.createArg().setValue( "--until=" + StringUtils.escape( 
> endVersion.getName() ) );
> }
> else
> {
138d136
< 
package org.apache.maven.scm.provider.git.gitexe.command.changelog;

/*
 * Licensed to the Apache Software Foundation (ASF) under one
 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing,
 * software distributed under the License is distributed on an
 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */

import org.apache.maven.scm.ScmBranch;
import org.apache.maven.scm.ScmException;
import org.apache.maven.scm.ScmFileSet;
import org.apache.maven.scm.ScmVersion;
import org.apache.maven.scm.command.changelog.AbstractChangeLogCommand;
import org.apache.maven.scm.command.changelog.ChangeLogScmResult;
import org.apache.maven.scm.command.changelog.ChangeLogSet;
import org.apache.maven.scm.provider.ScmProviderRepository;
import org.apac

Re: NPE with maven-changelog-plugin and git

[Imran M Yousuf]

On Mon, Mar 30, 2009 at 5:23 PM, Mark Struberg  wrote:
>
> Hi Imran!
>
> Having only looked over your log quickly, it seems to me that this is not a 
> git-scm problem:
>
>> java.lang.NoSuchMethodError: 
>> org.codehaus.plexus.util.cli.Commandline.createArg()Lorg/codehaus/plexus/util/cli/Arg;
>> org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.getBaseGitCommandLine(GitCommandLineUtils.java:82)
>
> Looks like this function is not in the plexus-utils-1.1 the changelog uses in 
> your setup?
>> [DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.6:compile (removed - 
>> nearer found: 1.1)
> hmm, why does it take the 1.1 instead of the 1.5.6? Idea, anyone?
>

Hi Mark!

If I add the following to the plugin -

org.codehaus.plexus
plexus-utils
${plexus-utils.version}


Where verison is 1.5.6 it works fine with both 2.1 and the
2.2-SNAPSHOT and I can exclude the gitexe as dependency from the
plugin.

Thanks,

Imran


>
> LieGrue,
> strub
>
>
>
> --- Imran M Yousuf  schrieb am Mo, 30.3.2009:
>
>> Von: Imran M Yousuf 
>> Betreff: NPE with maven-changelog-plugin and git
>> An: scm-dev@maven.apache.org
>> Datum: Montag, 30. März 2009, 4:55
>> Hi,
>>
>> I am getting NPE when I issue  the following
>> configuration and
>> command 'mvn changelog:changelog' in scm version 1.1. When
>> I use scm
>> verison 1.2 I get No Such Method Error. I am pretty sure I
>> am doing
>> something wrong but I am unable to determine it. Please
>> help! I have
>> attached the relevant outputs as attachment -
>> git-log.out - Output of the git log command issued to build
>> the log
>> maven-changelog-npe.out - Output including debug info for
>> the NPE
>> maven-scm-error-1.2.out - No such method error with 1.2.
>>
>> I am compressing them to reduce the size of the attachment.
>> I would be
>> deeply grateful if you would be kind enough to point me in
>> right
>> direction.
>>
>>
>>             
>>
>> scm:git:git://repo.or.cz/smart-dao.git
>>
>> scm:git:ssh://imyou...@repo.or.cz/srv/git/smart-dao.git
>>             
>>
>>             
>>
>> org.apache.maven.plugins
>>
>> maven-scm-plugin
>>
>> ${scm.version}
>>             
>>             
>>
>> org.apache.maven.plugins
>>
>> maven-changelog-plugin
>>
>> 2.1
>>
>> 
>>
>>     
>>
>>
>> org.apache.maven.scm
>>
>>
>> maven-scm-provider-gitexe
>>
>>
>> ${scm.version}
>>
>>     
>>
>> 
>>             
>>     
>>
>> 2.3
>>
>> 0.2-SNAPSHOT
>>
>> 0.4-SNAPSHOT
>>
>> 1.1
>>     
>>
>> Thank you,
>>
>> --
>> Imran M Yousuf
>> Entrepreneur & Software Engineer
>> Smart IT Engineering
>> Dhaka, Bangladesh
>> Email: im...@smartitengineering.com
>> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
>> Mobile: +880-1711402557
>>
>
>
>
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

Re: AW: NPE with maven-changelog-plugin and git

[Imran M Yousuf]

On Tue, Mar 31, 2009 at 12:01 AM, Olivier Lamy  wrote:
> Hi,
> Can you try with last maven-changelog-plugin 2.2-SNAPSHOT version ?
> I have just deployed a SNAPSHOT which use scm 1.2 released version.
>

Changing the version straight forward did not work :(, but after I
checked out the code of changelog and 'mvn install' it, the stuffs
worked perfectly :).

Thanks,

Imran

> Thanks,
> --
> Olivier
>
> 2009/3/30 Benjamin Bentmann :
>> Mark Struberg wrote:
>>
 [DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.6:compile (removed -
 nearer found: 1.1)
>>>
>>> hmm, why does it take the 1.1 instead of the 1.5.6? Idea, anyone?
>>
>> Looks like http://jira.codehaus.org/browse/MCHANGELOG-89. The plugin POM is
>> missing plexus-utils as a direct dependency which triggers a backward-compat
>> mode in Maven 2.x that adds plexus-utils:1.1 to the plugin dependencies.
>> This injected direct dependency on plexus-utils:1.1 wins over the
>> plexus-utils used by the SCM stuff due to the nearest conflict resolution.
>>
>>
>> Benjamin
>>
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

Re: AW: NPE with maven-changelog-plugin and git

[Imran M Yousuf]

On Mon, Mar 30, 2009 at 6:27 PM, Brett Porter  wrote:
> What version of Maven? I think prior to Maven 2.0.7 it was hardcoded to p-u
> 1.1.
>

$ mvn -version
Apache Maven 2.1.0 (r755702; 2009-03-19 01:10:27+0600)
Java version: 1.6.0_01
Java home: /opt/jdk1.6.0_01/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.24-23-generic" arch: "i386" Family: "unix"


Thank you,

Imran

> - Brett
>
> On 30/03/2009, at 10:23 PM, Mark Struberg wrote:
>
>>
>> Hi Imran!
>>
>> Having only looked over your log quickly, it seems to me that this is not
>> a git-scm problem:
>>
>>> java.lang.NoSuchMethodError:
>>> org.codehaus.plexus.util.cli.Commandline.createArg()Lorg/codehaus/plexus/util/cli/Arg;
>>>
>>> org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.getBaseGitCommandLine(GitCommandLineUtils.java:82)
>>
>> Looks like this function is not in the plexus-utils-1.1 the changelog uses
>> in your setup?
>>>
>>> [DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.6:compile (removed -
>>> nearer found: 1.1)
>>
>> hmm, why does it take the 1.1 instead of the 1.5.6? Idea, anyone?
>>
>>
>> LieGrue,
>> strub
>>
>>
>>
>> --- Imran M Yousuf  schrieb am Mo, 30.3.2009:
>>
>>> Von: Imran M Yousuf 
>>> Betreff: NPE with maven-changelog-plugin and git
>>> An: scm-dev@maven.apache.org
>>> Datum: Montag, 30. März 2009, 4:55
>>> Hi,
>>>
>>> I am getting NPE when I issue  the following
>>> configuration and
>>> command 'mvn changelog:changelog' in scm version 1.1. When
>>> I use scm
>>> verison 1.2 I get No Such Method Error. I am pretty sure I
>>> am doing
>>> something wrong but I am unable to determine it. Please
>>> help! I have
>>> attached the relevant outputs as attachment -
>>> git-log.out - Output of the git log command issued to build
>>> the log
>>> maven-changelog-npe.out - Output including debug info for
>>> the NPE
>>> maven-scm-error-1.2.out - No such method error with 1.2.
>>>
>>> I am compressing them to reduce the size of the attachment.
>>> I would be
>>> deeply grateful if you would be kind enough to point me in
>>> right
>>> direction.
>>>
>>>
>>>            
>>>
>>> scm:git:git://repo.or.cz/smart-dao.git
>>>
>>>
>>> scm:git:ssh://imyou...@repo.or.cz/srv/git/smart-dao.git
>>>            
>>>
>>>            
>>>
>>> org.apache.maven.plugins
>>>
>>> maven-scm-plugin
>>>
>>> ${scm.version}
>>>            
>>>            
>>>
>>> org.apache.maven.plugins
>>>
>>> maven-changelog-plugin
>>>
>>> 2.1
>>>
>>> 
>>>
>>>    
>>>
>>>
>>> org.apache.maven.scm
>>>
>>>
>>> maven-scm-provider-gitexe
>>>
>>>
>>> ${scm.version}
>>>
>>>    
>>>
>>> 
>>>            
>>>    
>>>
>>> 2.3
>>>
>>> 0.2-SNAPSHOT
>>>
>>> 0.4-SNAPSHOT
>>>
>>> 1.1
>>>    
>>>
>>> Thank you,
>>>
>>> --
>>> Imran M Yousuf
>>> Entrepreneur & Software Engineer
>>> Smart IT Engineering
>>> Dhaka, Bangladesh
>>> Email: im...@smartitengineering.com
>>> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
>>> Mobile: +880-1711402557
>>>
>>
>>
>>
>
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

Re: AW: NPE with maven-changelog-plugin and git

[Olivier Lamy]

Hi,
Can you try with last maven-changelog-plugin 2.2-SNAPSHOT version ?
I have just deployed a SNAPSHOT which use scm 1.2 released version.

Thanks,
--
Olivier

2009/3/30 Benjamin Bentmann :
> Mark Struberg wrote:
>
>>> [DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.6:compile (removed -
>>> nearer found: 1.1)
>>
>> hmm, why does it take the 1.1 instead of the 1.5.6? Idea, anyone?
>
> Looks like http://jira.codehaus.org/browse/MCHANGELOG-89. The plugin POM is
> missing plexus-utils as a direct dependency which triggers a backward-compat
> mode in Maven 2.x that adds plexus-utils:1.1 to the plugin dependencies.
> This injected direct dependency on plexus-utils:1.1 wins over the
> plexus-utils used by the SCM stuff due to the nearest conflict resolution.
>
>
> Benjamin
>

Re: AW: NPE with maven-changelog-plugin and git

[Benjamin Bentmann]

Mark Struberg wrote:


[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.6:compile (removed - nearer 
found: 1.1)

hmm, why does it take the 1.1 instead of the 1.5.6? Idea, anyone?


Looks like http://jira.codehaus.org/browse/MCHANGELOG-89. The plugin POM 
is missing plexus-utils as a direct dependency which triggers a 
backward-compat mode in Maven 2.x that adds plexus-utils:1.1 to the 
plugin dependencies. This injected direct dependency on plexus-utils:1.1 
wins over the plexus-utils used by the SCM stuff due to the nearest 
conflict resolution.



Benjamin

Re: AW: NPE with maven-changelog-plugin and git

[Mark Struberg]

from the log Imran posted:
> Apache Maven 2.1.0 (r755702; 2009-03-19 01:10:27+0600)

That's why I was wondering about plexus-utils-1.1 ...

txs,
strub

--- Brett Porter  schrieb am Mo, 30.3.2009:

> Von: Brett Porter 
> Betreff: Re: AW: NPE with maven-changelog-plugin and git
> An: scm-dev@maven.apache.org
> Datum: Montag, 30. März 2009, 14:27
> What version of Maven? I think prior
> to Maven 2.0.7 it was hardcoded to p-u 1.1.
> 
> - Brett
> 
> On 30/03/2009, at 10:23 PM, Mark Struberg wrote:
> 
> > 
> > Hi Imran!
> > 
> > Having only looked over your log quickly, it seems to
> me that this is not a git-scm problem:
> > 
> >> java.lang.NoSuchMethodError:
> org.codehaus.plexus.util.cli.Commandline.createArg()Lorg/codehaus/plexus/util/cli/Arg;
> >>
> org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.getBaseGitCommandLine(GitCommandLineUtils.java:82)
> > 
> > Looks like this function is not in the
> plexus-utils-1.1 the changelog uses in your setup?
> >>
> [DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.6:compile
> (removed - nearer found: 1.1)
> > hmm, why does it take the 1.1 instead of the 1.5.6?
> Idea, anyone?
> > 
> > 
> > LieGrue,
> > strub
> > 
> > 
> > 
> > --- Imran M Yousuf 
> schrieb am Mo, 30.3.2009:
> > 
> >> Von: Imran M Yousuf 
> >> Betreff: NPE with maven-changelog-plugin and git
> >> An: scm-dev@maven.apache.org
> >> Datum: Montag, 30. März 2009, 4:55
> >> Hi,
> >> 
> >> I am getting NPE when I issue  the following
> >> configuration and
> >> command 'mvn changelog:changelog' in scm version
> 1.1. When
> >> I use scm
> >> verison 1.2 I get No Such Method Error. I am
> pretty sure I
> >> am doing
> >> something wrong but I am unable to determine it.
> Please
> >> help! I have
> >> attached the relevant outputs as attachment -
> >> git-log.out - Output of the git log command issued
> to build
> >> the log
> >> maven-changelog-npe.out - Output including debug
> info for
> >> the NPE
> >> maven-scm-error-1.2.out - No such method error
> with 1.2.
> >> 
> >> I am compressing them to reduce the size of the
> attachment.
> >> I would be
> >> deeply grateful if you would be kind enough to
> point me in
> >> right
> >> direction.
> >> 
> >> 
> >>         
>    
> >> 
> >>
> scm:git:git://repo.or.cz/smart-dao.git
> >> 
> >> scm:git:ssh://imyou...@repo.or.cz/srv/git/smart-dao.git
> >>         
>    
> >> 
> >>         
>    
> >> 
> >>
> org.apache.maven.plugins
> >> 
> >>
> maven-scm-plugin
> >> 
> >> ${scm.version}
> >>         
>    
> >>         
>    
> >> 
> >>
> org.apache.maven.plugins
> >> 
> >>
> maven-changelog-plugin
> >> 
> >> 2.1
> >> 
> >> 
> >> 
> >>     
> >> 
> >> 
> >>
> org.apache.maven.scm
> >> 
> >> 
> >>
> maven-scm-provider-gitexe
> >> 
> >> 
> >> ${scm.version}
> >> 
> >>     
> >> 
> >> 
> >>         
>    
> >>     
> >> 
> >>
> 2.3
> >> 
> >>
> 0.2-SNAPSHOT
> >> 
> >>
> 0.4-SNAPSHOT
> >> 
> >> 1.1
> >>     
> >> 
> >> Thank you,
> >> 
> >> --Imran M Yousuf
> >> Entrepreneur & Software Engineer
> >> Smart IT Engineering
> >> Dhaka, Bangladesh
> >> Email: im...@smartitengineering.com
> >> Blog: http://imyousuf-tech.blogs.smartitengineering.com/
> >> Mobile: +880-1711402557
> >> 
> > 
> > 
> > 
> 
> 

Re: AW: NPE with maven-changelog-plugin and git

[Brett Porter]

What version of Maven? I think prior to Maven 2.0.7 it was hardcoded  
to p-u 1.1.


- Brett

On 30/03/2009, at 10:23 PM, Mark Struberg wrote:



Hi Imran!

Having only looked over your log quickly, it seems to me that this  
is not a git-scm problem:


java.lang.NoSuchMethodError:  
org.codehaus.plexus.util.cli.Commandline.createArg()Lorg/codehaus/ 
plexus/util/cli/Arg;
org 
.apache 
.maven 
.scm 
.provider 
.git 
.gitexe 
.command 
.GitCommandLineUtils.getBaseGitCommandLine(GitCommandLineUtils.java: 
82)


Looks like this function is not in the plexus-utils-1.1 the  
changelog uses in your setup?
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.6:compile  
(removed - nearer found: 1.1)

hmm, why does it take the 1.1 instead of the 1.5.6? Idea, anyone?


LieGrue,
strub



--- Imran M Yousuf  schrieb am Mo, 30.3.2009:


Von: Imran M Yousuf 
Betreff: NPE with maven-changelog-plugin and git
An: scm-dev@maven.apache.org
Datum: Montag, 30. März 2009, 4:55
Hi,

I am getting NPE when I issue  the following
configuration and
command 'mvn changelog:changelog' in scm version 1.1. When
I use scm
verison 1.2 I get No Such Method Error. I am pretty sure I
am doing
something wrong but I am unable to determine it. Please
help! I have
attached the relevant outputs as attachment -
git-log.out - Output of the git log command issued to build
the log
maven-changelog-npe.out - Output including debug info for
the NPE
maven-scm-error-1.2.out - No such method error with 1.2.

I am compressing them to reduce the size of the attachment.
I would be
deeply grateful if you would be kind enough to point me in
right
direction.




scm:git:git://repo.or.cz/smart-dao.git

scm:git:ssh://imyou...@repo.or.cz/srv/git/smart-dao.git 






org.apache.maven.plugins

maven-scm-plugin

${scm.version}



org.apache.maven.plugins

maven-changelog-plugin

2.1






org.apache.maven.scm


maven-scm-provider-gitexe


${scm.version}







2.3

0.2-SNAPSHOT

0.4-SNAPSHOT

1.1


Thank you,

--
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: im...@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

Re: [RESULT] [VOTE] Release Maven Release plugin version 2.0-beta-9 and scm 1.2

[Olivier Lamy]

Hi,
I have use the nexus ui to promote artifacts.
The release plugin is on central repo but not scm artifacts !!
Can someone have a look ?
Other issue : one day after site deploy on p.a.o sites are not yet
sync (release plugin and scm site)

Thanks!
--
Olivier

2009/3/27 Olivier Lamy :
> Hi,
> The votes has passed with the following result :
> +1 (binding) : Arnaud HERITIER, Jason van Zyl,Emmanuel Venisse, Olivier Lamy
> +1 (non-binding) : Marc Struberg
>
> I will move artifacts to central repo and publish the site.
>
> Thanks,
> --
> Olivier
>

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: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9

[Jason Chaffee]

Subversion 1.6.0 was just released at the end of last week.  Not sure if it has 
been tested against 1.6.0 or not, but I have already ran into issues with other 
software and Subversion 1.6.0just for your info.  :) 

-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier 
Lamy
Sent: Monday, March 23, 2009 3:56 PM
To: Maven Developers List; scm-dev@maven.apache.org
Subject: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9

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: release maven-scm

[Jason van Zyl]

I'll be awake so just ping me in IRC and we'll stage them together  
together :-)


On 23-Mar-09, at 9:53 AM, Olivier Lamy wrote:


Sounds a good idea.
I will be on irc ~21H PM (Paris Time).
Thanks in advance for your help,
--
Olivier

2009/3/23 Jason van Zyl :
You can stage maven scm and the release plugin if you want people  
to try
them together. I can help you with that if you like. We can make it  
easy for
people to test by pointing at particular nexus group which will  
pull in both
tools staged together so it's used in the same way it would be when  
it's

released.

On 23-Mar-09, at 9:45 AM, Olivier Lamy wrote:


release means staging first :-)

2009/3/23 Mark Struberg :


Any staging out there I can run a quick test with?
Snapshot works for me so far (but didn't used it for releasing)

LieGrue,
strub

--- Olivier Lamy  schrieb am Mo, 23.3.2009:


Von: Olivier Lamy 
Betreff: release maven-scm
An: scm-dev@maven.apache.org, "Maven Developers List"

Datum: Montag, 23. März 2009, 17:03
Hi,
I'd like to release maven-scm 1.2.
No objections ?
It's mandatory to release maven-release-plugin (and the
famous issue
with svn > 1.5.0)

Thanks,
--
Olivier








Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--

the course of true love never did run smooth ...

 -- Shakespeare




Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--

To do two things at once is to do neither.

 -—Publilius Syrus, Roman slave, first century B.C.

Re: svnjava provider and maven scm

[Olivier Lamy]

done. there is now only a README.TXT
(https://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/README.TXT)

--
Olivier

2009/3/21 Brett Porter :
> On 21/03/2009, at 9:05 AM, Olivier Lamy wrote:
>
>> So I have moved back the provider to sandbox and start a fork here [1]
>> If someone want to have karma ping me.
>
> I suggest we just remove the provider from the sandbox then rather than have
> the ambiguity.
>
> - Brett
>
> --
> Brett Porter
> br...@apache.org
> http://blogs.exist.com/bporter/
>
>

Re: svnjava provider and maven scm

[Brett Porter]

On 21/03/2009, at 9:05 AM, Olivier Lamy wrote:


So I have moved back the provider to sandbox and start a fork here [1]
If someone want to have karma ping me.


I suggest we just remove the provider from the sandbox then rather  
than have the ambiguity.


- Brett

--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/

Re: svnjava provider and maven scm

[Brett Porter]

On 21/03/2009, at 6:38 AM, Jason van Zyl wrote:


Brett,

There is no way we accept the Sleepcat license, it's viral. It is  
also heavily recommend against using because it can force you to  
have to redistribute your source code. That from our IP lawyer who  
deals with every day. Please don't dispense legal advice. Everything  
in law is in interpretation but there are some accepted  
interpretation. It's also unlikely that those contracts are  
identical unless they are verbatim and originate from the same  
country.




I'm not quite sure what you're saying exactly. We seem to have the  
same understanding of the license at least (that's exactly what I said  
in the issue), it is totally viral and forces you to redistribute your  
source code if you use it (it is based on distribution). My suggestion  
was how we could offer our source code, without the library, and give  
suitable warning on the impact of turning it on as an optional bit of  
Maven SCM for those that can use the license.


Regardless, I closed the issue since Olivier moved it out.

- Brett

--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/

Re: svnjava provider and maven scm

[Olivier Lamy]

So I have moved back the provider to sandbox and start a fork here [1]
If someone want to have karma ping me.

--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/

2009/3/20 Jason van Zyl :
> Brett,
>
> There is no way we accept the Sleepcat license, it's viral. It is also
> heavily recommend against using because it can force you to have to
> redistribute your source code. That from our IP lawyer who deals with every
> day. Please don't dispense legal advice. Everything in law is in
> interpretation but there are some accepted interpretation. It's also
> unlikely that those contracts are identical unless they are verbatim and
> originate from the same country.
>
> On 20-Mar-09, at 8:02 AM, Olivier Lamy wrote:
>
>> only maven-scm-provider-svnjava
>>
>> --
>> Olivier
>>
>> 2009/3/20 Jason van Zyl :
>>>
>>> That's an old fork of svnkit, not sure you want to put it there. That
>>> project is essentially dead.
>>>
>>> On 20-Mar-09, at 1:46 AM, Olivier Lamy wrote:
>>>
 Hi,
 Not in mojo but here : http://xircles.codehaus.org/projects/svn4j  ?

 a new path : https://svn.codehaus.org/svn4j/maven-scm-provider-svnjava/

 --
 Olivier

 2009/3/20 Brett Porter :
>
> On 20/03/2009, at 2:17 AM, Olivier Lamy wrote:
>
>> So the Brett proposal looks fine too.
>> I can mark the svnjava provider as optionnal and explain why on the
>> scm site and explain how to use it.
>
> That was all my opinion, so we should get it confirmed before release.
> Note
> that under the current FAQ the Sleepycat license (which this is
> equivalent
> to), is not allowed for inclusion.
>
> I filed: https://issues.apache.org/jira/browse/LEGAL-45, and added a
> couple
> more points on the list about how we can avoid it getting used without
> being
> aware of the license - putting it in a separate build profile and
> making
> sure it is not in the aggregating POM.
>
> It can always go to mojo, but I think it'd be a shame to have to
> separate
> it, so it's worth asking.
>
> - Brett
>
> --
> Brett Porter
> br...@apache.org
> http://blogs.exist.com/bporter/
>
>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> --
>>> Jason van Zyl
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> --
>>>
>>> People develop abstractions by generalizing from concrete examples.
>>> Every attempt to determine the correct abstraction on paper without
>>> actually developing a running system is doomed to failure. No one
>>> is that smart. A framework is a resuable design, so you develop it by
>>> looking at the things it is supposed to be a design of. The more examples
>>> you look at, the more general your framework will be.
>>>
>>>  -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>>>
>>>
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> --
>
> the course of true love never did run smooth ...
>
>  -- Shakespeare
>
>

Re: svnjava provider and maven scm

[Jason van Zyl]

Brett,

There is no way we accept the Sleepcat license, it's viral. It is also  
heavily recommend against using because it can force you to have to  
redistribute your source code. That from our IP lawyer who deals with  
every day. Please don't dispense legal advice. Everything in law is in  
interpretation but there are some accepted interpretation. It's also  
unlikely that those contracts are identical unless they are verbatim  
and originate from the same country.


On 20-Mar-09, at 8:02 AM, Olivier Lamy wrote:


only maven-scm-provider-svnjava

--
Olivier

2009/3/20 Jason van Zyl :

That's an old fork of svnkit, not sure you want to put it there. That
project is essentially dead.

On 20-Mar-09, at 1:46 AM, Olivier Lamy wrote:


Hi,
Not in mojo but here : http://xircles.codehaus.org/projects/svn4j  ?

a new path : https://svn.codehaus.org/svn4j/maven-scm-provider-svnjava/

--
Olivier

2009/3/20 Brett Porter :


On 20/03/2009, at 2:17 AM, Olivier Lamy wrote:


So the Brett proposal looks fine too.
I can mark the svnjava provider as optionnal and explain why on  
the

scm site and explain how to use it.


That was all my opinion, so we should get it confirmed before  
release.

Note
that under the current FAQ the Sleepycat license (which this is
equivalent
to), is not allowed for inclusion.

I filed: https://issues.apache.org/jira/browse/LEGAL-45, and  
added a

couple
more points on the list about how we can avoid it getting used  
without

being
aware of the license - putting it in a separate build profile and  
making

sure it is not in the aggregating POM.

It can always go to mojo, but I think it'd be a shame to have to  
separate

it, so it's worth asking.

- Brett

--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/




Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more  
examples

you look at, the more general your framework will be.

 -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks




Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--

the course of true love never did run smooth ...

 -- Shakespeare

Re: svnjava provider and maven scm

[Brett Porter]

On 20/03/2009, at 2:17 AM, Olivier Lamy wrote:


So the Brett proposal looks fine too.
I can mark the svnjava provider as optionnal and explain why on the
scm site and explain how to use it.


That was all my opinion, so we should get it confirmed before release.  
Note that under the current FAQ the Sleepycat license (which this is  
equivalent to), is not allowed for inclusion.


I filed: https://issues.apache.org/jira/browse/LEGAL-45, and added a  
couple more points on the list about how we can avoid it getting used  
without being aware of the license - putting it in a separate build  
profile and making sure it is not in the aggregating POM.


It can always go to mojo, but I think it'd be a shame to have to  
separate it, so it's worth asking.


- Brett

--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/

Re: svnjava provider and maven scm

[Jason van Zyl]

On 19-Mar-09, at 8:17 AM, Olivier Lamy wrote:


So the Brett proposal looks fine too.
I can mark the svnjava provider as optionnal and explain why on the
scm site and explain how to use it.


The svn library is not optional for this component to work. You  
require it to run.


SVNKit and that's not LGPL, it's a license we've never validated here.  
It's a custom license called the TMate Open Source License.


Brett's proposal is not fine.

You may not like the way the legal process is here but you can't end- 
run the safe guards in place by saying something is optional when it  
clearly is not. And then trying to draw an analogy to a project where  
the license isn't even the same and a completely custom one at that.


Ask Apache legal. Explain to them you're marking optional what isn't  
and show them the TMate license and see what they tell you.



--
Olivier

2009/3/19 Jason van Zyl :

From my experience asking anyone about anything legal has never been
resolved in any timely manner.

Whether grand fathered or anything else. Discussions have gone on  
for a very

long time.

Olivier if you want to release it then I would just taking it to  
mojo and

then there are no issues.

On 19-Mar-09, at 5:12 AM, Brett Porter wrote:



On 19/03/2009, at 7:29 PM, Jason van Zyl wrote:


On 19-Mar-09, at 1:25 AM, Olivier Lamy wrote:


Hi,
Ok. It's was not really clear for me.



There is precedent - we grandfathered in Checkstyle which is LGPL  
as it is

just a dependency of a plugin, which we don't actually distribute.

The general talk - though not confirmed - is that optional  
dependencies
that the user must obtain themselves could be ok. There isn't a  
legal

problem with the combination, but rather a policy one that you don't
distribute something that is essentially useless without a  
dependency of a

stronger license.

We should ask, but I personally think this is ok, as long as:
- it is not made the default provider
- instructions on the site about how to use it spell out that it  
requires

the dependency and that it is not under the AL
- we don't bundle and distribute



Technically we are not redistributing anything and we can ask the  
board
for clarification because in the strictest sense we do not  
redistribute. But
I think folks here would interpret a dependency in your POM as  
being

equivalent.


No need to ask the board, you can file a request here:
https://issues.apache.org/jira/browse/LEGAL

Cheers,
Brett

--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/



Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--





Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--

Re: svnjava provider and maven scm

[Brett Porter]

On 19/03/2009, at 7:29 PM, Jason van Zyl wrote:


On 19-Mar-09, at 1:25 AM, Olivier Lamy wrote:


Hi,
Ok. It's was not really clear for me.



There is precedent - we grandfathered in Checkstyle which is LGPL as  
it is just a dependency of a plugin, which we don't actually distribute.


The general talk - though not confirmed - is that optional  
dependencies that the user must obtain themselves could be ok. There  
isn't a legal problem with the combination, but rather a policy one  
that you don't distribute something that is essentially useless  
without a dependency of a stronger license.


We should ask, but I personally think this is ok, as long as:
- it is not made the default provider
- instructions on the site about how to use it spell out that it  
requires the dependency and that it is not under the AL

- we don't bundle and distribute



Technically we are not redistributing anything and we can ask the  
board for clarification because in the strictest sense we do not  
redistribute. But I think folks here would interpret a dependency in  
your POM as being equivalent.


No need to ask the board, you can file a request here: 
https://issues.apache.org/jira/browse/LEGAL

Cheers,
Brett

--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/

Re: unsubscribe

[Mark Struberg]

write a mail to

scm-dev-unsubscr...@maven.apache.org


LieGrue,
strub

--- Christian Schlaefcke  schrieb am Do, 19.3.2009:

> Von: Christian Schlaefcke 
> Betreff: Re: unsubscribe
> An: cschlaef...@wms-network.de
> CC: scm-dev@maven.apache.org
> Datum: Donnerstag, 19. März 2009, 10:51
> Hmm, did not work...
> 
> How can unsubscribe from this list?
> 
> Sorry for that...
> 
> Regards,
> 
> Christian
> 
> 

Re: svnjava provider and maven scm

[Mark Struberg]

In fact we are not 'packaging' it, but we 'distribute' it via download links. 
So from the de iure point this is really edgy. 

The easiest thing would be to simply ask svnkit folks to give us a consensus 
letter that we are allowed to use it for maven-scm or even better a general 
clearance for using it in Apache projects.

LieGrue,
strub

--- Jason van Zyl  schrieb am Do, 19.3.2009:

> Von: Jason van Zyl 
> Betreff: Re: svnjava provider and maven scm
> An: scm-dev@maven.apache.org
> Datum: Donnerstag, 19. März 2009, 9:29
> On 19-Mar-09, at 1:25 AM, Olivier
> Lamy wrote:
> 
> > Hi,
> > Ok. It's was not really clear for me.
> > 
> 
> Technically we are not redistributing anything and we can
> ask the board for clarification because in the strictest
> sense we do not redistribute. But I think folks here would
> interpret a dependency in your POM as being equivalent.
> 
> > Thanks for clarification,
> > --
> > Olivier
> > 
> > 2009/3/19 Jason van Zyl :
> >> If the license is not one that the ASF accepts
> then we can't really dodge
> >> the issue by saying that it's only in the POM.
> >> 
> >> On 18-Mar-09, at 5:22 PM, Olivier Lamy wrote:
> >> 
> >>> Hi,
> >>> As we don't distribute the svnkit (it's only a
> dependency available in
> >>> the central repo), why we can't make a release
> of this provider ?
> >>> Any objections to move the sandbox module in
> trunk ?
> >>> 
> >>> Thanks,
> >>> --
> >>> Olivier
> >> 
> >> Thanks,
> >> 
> >> Jason
> >> 
> >>
> --
> >> Jason van Zyl
> >> Founder,  Apache Maven
> >> http://twitter.com/jvanzyl
> >>
> --
> >> 
> >> To do two things at once is to do neither.
> >> 
> >>  -—Publilius Syrus, Roman slave, first
> century B.C.
> >> 
> >> 
> 
> Thanks,
> 
> Jason
> 
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> --
> 
> 
> 

Re: svnjava provider and maven scm

[Jason van Zyl]

If the license is not one that the ASF accepts then we can't really  
dodge the issue by saying that it's only in the POM.


On 18-Mar-09, at 5:22 PM, Olivier Lamy wrote:


Hi,
As we don't distribute the svnkit (it's only a dependency available in
the central repo), why we can't make a release of this provider ?
Any objections to move the sandbox module in trunk ?

Thanks,
--
Olivier


Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--

To do two things at once is to do neither.

 -—Publilius Syrus, Roman slave, first century B.C.

Re: git SCM JIRA questions

[Olivier Lamy]

done but assigned to me as I can't assign to you.

--
Olivier

2009/3/17 Mark Struberg :
>
> sorry topic missing...
>
>
> --- Mark Struberg  schrieb am Di, 17.3.2009:
>
>> Von: Mark Struberg 
>> Betreff:
>> An: scm-dev@maven.apache.org
>> Datum: Dienstag, 17. März 2009, 10:28
>>
>> Olivier,
>>
>>
>> I found a few git issues which are not assigned to the
>> right component:
>>
>> http://jira.codehaus.org/browse/SCM-441
>> http://jira.codehaus.org/browse/SCM-444
>>
>>
>>
>> Can you please correct the component to
>> maven-scm-provider-git and assign them to me?
>>
>> And also assign me the following JIRAs:
>>
>> http://jira.codehaus.org/browse/SCM-442
>>
>>
>> txs and LieGrue,
>> strub
>>
>>
>>
>>
>>
>
>
>
>

Re:

[Olivier Lamy]

Hi,
I cannot assign this to you but I have assigned this to me.
If you can provide patch I will be happy to commit them :-)

Thanks,
--
Olivier

2009/3/17 Mark Struberg :
>
> Olivier,
>
>
> I found a few git issues which are not assigned to the right component:
>
> http://jira.codehaus.org/browse/SCM-441
> http://jira.codehaus.org/browse/SCM-444
>
>
>
> Can you please correct the component to maven-scm-provider-git and assign 
> them to me?
>
> And also assign me the following JIRAs:
>
> http://jira.codehaus.org/browse/SCM-442
>
>
> txs and LieGrue,
> strub
>
>
>
>
>

Re: accurev provider

[Grant Gardner]

I've created the jira with attached code. Let me know if there's anything
else I need to do.
http://jira.codehaus.org/browse/SCM-445

Will do the CLA when I find myself conveniently located near a fax or
scanner.

On Mon, 9 Mar 2009 05:02:15 +1100, Brett Porter  wrote:
> 1) Create a JIRA ticket under SCM
> 2) you might like to submit a CLA - you can do it regardless, and if
> the work is accepted such a large chunk would probably require it (see
> http://www.apache.org/licenses/
>   and specifically http://www.apache.org/licenses/icla.txt)
> 
> Thanks!
> 
> - Brett
> 
> On 07/03/2009, at 12:50 PM, Grant Gardner wrote:
> 
>>
>>
>> Hi, I've got my AccuRev provider to a point where both the release
>> plugin
>> and Continuum are working (for me).
>>
>> Includes unit tests and tck tests for all the implemented commands.
>>
>> How do I go about contributing the code?.
>>
>> Grant.
>>
>>
> 
> --
> Brett Porter
> br...@apache.org
> http://blogs.exist.com/bporter/

Re: accurev provider

[Brett Porter]

1) Create a JIRA ticket under SCM
2) you might like to submit a CLA - you can do it regardless, and if  
the work is accepted such a large chunk would probably require it (see http://www.apache.org/licenses/ 
 and specifically http://www.apache.org/licenses/icla.txt)


Thanks!

- Brett

On 07/03/2009, at 12:50 PM, Grant Gardner wrote:




Hi, I've got my AccuRev provider to a point where both the release  
plugin

and Continuum are working (for me).

Includes unit tests and tck tests for all the implemented commands.

How do I go about contributing the code?.

Grant.




--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/

Re: accurev provider

[Grant Gardner]

Hi, I've got my AccuRev provider to a point where both the release plugin
and Continuum are working (for me).

Includes unit tests and tck tests for all the implemented commands.

How do I go about contributing the code?.

Grant.

Re: AW: new provider (accurev) - isPersistCheckout

[ggardner]

for these providers the "client spec", "workspace" etc IS the meta
information.

ie by that definition  "non persistent checkout" == "export".

The difference being that the meta data isn't stored within the
source tree so it doesn't get in the way of the tarball anyway

The corollary with this approach is that you can't allow a
checkout within a subdirectory of another checkout.

It would have been cleaner IMHO to
1) enhance export to support relativePathProjectDirectory concept
   or move that concept to the repository.
2) add a repository flag - shouldUseExportForNonPersistentCheckout()
3) change the release plugin to test this flag, rather than setting
something.

All the downstream systems had to change to setIsPersistCheckout(true)
in order to support Clearcase and Perforce properly which could
have been avoided.

The providers that don't have this issue would still not be required
to implement export.

Should I raise a JIRA (with patches) to suggest the above?.
Alternatively we'll need to either change the default to "true" OR
change the tcktests to use setPersistCheckout() appropriately.

On Mon, 19 Jan 2009 10:47:35 + (GMT), Mark Struberg 
wrote:
> The export command is usually used to create a tarball or zip so there
will
> be no SCM meta information at all.
> The command is btw not implemented in all scm providers (e.g. git doesn't
> support exports natively).
>
> On the other hand (according to SCM-113) isPersistCheckout() is only
about
> removing the client spec after a normal checkout.
>
> LieGrue,
> strub
>
> --- lwoggardner  schrieb am Mo, 19.1.2009:
>
>> Von: lwoggardner 
>> Betreff: new provider (accurev) - isPersistCheckout
>> An: "Scm dev" 
>> Datum: Montag, 19. Januar 2009, 11:25
>> Hi all,
>>
>> As per my previous post I'm in the process of
>> implementing an extended
>> AccuRev
>> provider.
>>
>> AccuRev, apparently like Perforce and Clearcase, keeps
>> track of user
>> checkouts
>> in "workspaces". These workspaces are uniquely
>> named across the repository,
>> and
>> the physical filesystem locations are not permitted to
>> overlap.
>>
>> Consequently the release plugin's checkout to the
>> target/checkout
>> sub-directory
>> is problematic. It looks like the
>> "isPersistCheckout()" method from SCM-113
>> is
>> intended to resolve this very issue, but I have a few
>> questions on that.
>>
>> 1) Why is the default "false".
>>   - It appears that the previous behaviour was more
>> equivalent to "true".
>>   - The tck-tests (eg the checkin/tag tck tests) assume by
>> their behaviour
>> that
>> the default is "true".
>>   - The only downstream use that sets "false" is
>> the release plugin.
>> Everything
>> else sets it explicitly to "true" (of course
>> I can't search for things
>> that
>> don't set it explicitly, so there might be others)
>>
>> 2) What is the difference between isPersistCheckout ==
>> false, and the
>> "export"
>>command?
>>
>>   - Both seem to extract a set of files to a directory,
>> without the
>> intention of
>> updating or committing back.
>>   - It feels strange that downstream users have to set a
>> flag in the
>> provider
>> repository which is otherwise "owned" by the
>> provider.
>>
>> Thanks,
>>  Grant.
>
>
>

RE: SCM plugin project

[Todd Thiessen]

Thanks Mark. I will do that.

---
Todd Thiessen
 

> -Original Message-
> From: Mark Struberg [mailto:strub...@yahoo.de] 
> Sent: Monday, January 19, 2009 9:37 AM
> To: scm-dev@maven.apache.org
> Subject: RE: SCM plugin project
> 
> Open a Jira, ship the patch, and I bet you'll get response.
> 
> LieGrü,
> strub
> 
> 
> --- Todd Thiessen  schrieb am Mo, 19.1.2009:
> 
> > Von: Todd Thiessen 
> > Betreff: RE: SCM plugin project
> > An: scm-dev@maven.apache.org
> > Datum: Montag, 19. Januar 2009, 15:16
> > Are there any further comments regarding this? Do we need 
> to open the 
> > discussion to a wider audience to get some traction on it?
> > 
> > ---
> > Todd Thiessen
> >  
> > 
> > > -Original Message-
> > > From: Thiessen, Todd (BVW:9T16)
> > > Sent: Thursday, January 15, 2009 10:49 AM
> > > To: 'scm-dev@maven.apache.org'
> > > Subject: RE: SCM plugin project
> > > 
> > > Yes it occurs in a standard SVN installation. This is
> > done by
> > > using svn hooks which is precisely what we have. 
> > Anyone can
> > > change the output of the svn log command (ie: no
> > change to
> > > svn source is required).  So yes I definiately
> > consider this
> > > standard.  It isn't considered "default"
> > behaviour, but I
> > > would definitely describe it as standard.
> > > 
> > > It is my opinion that this fix should be in the main
> > repo. 
> > > Individual users/companies should not have to maintain
> > their
> > > own copy of it. It makes synchronizing changes between
> > the
> > > main repo and all others an extra chore that
> > shouldn't be necessary.
> > > 
> > > We should also take note that Subversion does not make
> > any
> > > guarantees regarding the format of the svn log author
> > output. 
> > > They could very well change this "default"
> > behaviour to
> > > something that doesn't match what is currently
> > being parsed. 
> > > So the fix I am proposing makes the code base more
> > robust,
> > > which is always a good thing.
> > > 
> > > ---
> > > Todd Thiessen
> > >  
> > > 
> > > > -Original Message-
> > > > From: Mark Struberg [mailto:strub...@yahoo.de]
> > > > Sent: Thursday, January 15, 2009 10:30 AM
> > > > To: scm-dev@maven.apache.org
> > > > Subject: RE: SCM plugin project
> > > > 
> > > > Humm, so this SVN behaviour cannot occur in a
> > standard SVN
> > > > installation? Or can this also be achieved by
> > anyone? If
> > > not, there is
> > > > imho little chance of getting your changes into
> > the upstream repo.
> > > > 
> > > > Do you have a parent pom for your projects? Have
> > you tried
> > > to override
> > > > the dependency on maven-scm-provider-svnexe for
> > your build to a
> > > > locally patched version via
> >  ?
> > > > 
> > > > I assume you have something like archiva,
> > mavenproxy or nexus setup
> > > > and also have a company-internal plugin
> > repository, isn't?
> > > > 
> > > > So you could easily make the release process work
> > for your company
> > > > without having to release your changes to the
> > public repo.
> > > > 
> > > > LieGrue,
> > > > strub
> > > > 
> > > > 
> > > > --- Todd Thiessen 
> > schrieb am Do, 15.1.2009:
> > > > 
> > > > > Von: Todd Thiessen
> > 
> > > > > Betreff: RE: SCM plugin project
> > > > > An: scm-dev@maven.apache.org
> > > > > Datum: Donnerstag, 15. Januar 2009, 15:33
> > > > >
> > http://www.mail-archive.com/scm-dev@maven.apache.org/msg01173.html
> > > > > 
> > > > > It seems I wasn't actually subscribed to
> > scm-dev so I
> > > > didn't' get this
> > > > > response right away. Thanks for the response
> > Mark.
> > > > > 
> > > > > I have actually tested this and have seen it
> > fail. We have made
> > > > > modifications to SVN to print out the author
> > differently.
> > > > > I noticed the
> > > > > problem when I tried running the changelog
> > report and got
> > > > no output.  
> > > > > I was bashing my head on my desk trying to
> > figure out why for the
> > > > > longest time ;-).
> > > > > 
> > > > > I have also already made the modifications
> > to the
> > > > > maven-scm-provider-svnexe project and added
> > all appropriate test
> > > > > cases.
> > > > > My initial plan was to simply store a copy
> > of the source
> > > in our svn
> > > > > repo. However, I now have permission to
> > submit this to the proper
> > > > > place.
> > > > > 
> > > > > I will raise a JIRA to track the issue and
> > then I would
> > > > like to submit
> > > > > a patch for all appropriate personnel to
> > review.  Do I
> > > > simply attach
> > > > > an SVN patch to this mailing list?
> > > > > 
> > > > > ---
> > > > > Todd Thiessen
> > > > 
> > > > 
> > > >   
> > > > 
> > >
> 
> 
>   
> 

RE: SCM plugin project

[Mark Struberg]

Open a Jira, ship the patch, and I bet you'll get response.

LieGrü,
strub


--- Todd Thiessen  schrieb am Mo, 19.1.2009:

> Von: Todd Thiessen 
> Betreff: RE: SCM plugin project
> An: scm-dev@maven.apache.org
> Datum: Montag, 19. Januar 2009, 15:16
> Are there any further comments regarding this? Do we need to
> open the
> discussion to a wider audience to get some traction on it?
> 
> ---
> Todd Thiessen
>  
> 
> > -Original Message-
> > From: Thiessen, Todd (BVW:9T16) 
> > Sent: Thursday, January 15, 2009 10:49 AM
> > To: 'scm-dev@maven.apache.org'
> > Subject: RE: SCM plugin project
> > 
> > Yes it occurs in a standard SVN installation. This is
> done by 
> > using svn hooks which is precisely what we have. 
> Anyone can 
> > change the output of the svn log command (ie: no
> change to 
> > svn source is required).  So yes I definiately
> consider this 
> > standard.  It isn't considered "default"
> behaviour, but I 
> > would definitely describe it as standard.
> > 
> > It is my opinion that this fix should be in the main
> repo. 
> > Individual users/companies should not have to maintain
> their 
> > own copy of it. It makes synchronizing changes between
> the 
> > main repo and all others an extra chore that
> shouldn't be necessary.
> > 
> > We should also take note that Subversion does not make
> any 
> > guarantees regarding the format of the svn log author
> output. 
> > They could very well change this "default"
> behaviour to 
> > something that doesn't match what is currently
> being parsed. 
> > So the fix I am proposing makes the code base more
> robust, 
> > which is always a good thing.
> > 
> > ---
> > Todd Thiessen
> >  
> > 
> > > -Original Message-
> > > From: Mark Struberg [mailto:strub...@yahoo.de]
> > > Sent: Thursday, January 15, 2009 10:30 AM
> > > To: scm-dev@maven.apache.org
> > > Subject: RE: SCM plugin project
> > > 
> > > Humm, so this SVN behaviour cannot occur in a
> standard SVN 
> > > installation? Or can this also be achieved by
> anyone? If 
> > not, there is 
> > > imho little chance of getting your changes into
> the upstream repo.
> > > 
> > > Do you have a parent pom for your projects? Have
> you tried 
> > to override 
> > > the dependency on maven-scm-provider-svnexe for
> your build to a 
> > > locally patched version via
>  ?
> > > 
> > > I assume you have something like archiva,
> mavenproxy or nexus setup 
> > > and also have a company-internal plugin
> repository, isn't?
> > > 
> > > So you could easily make the release process work
> for your company 
> > > without having to release your changes to the
> public repo.
> > > 
> > > LieGrue,
> > > strub
> > > 
> > > 
> > > --- Todd Thiessen 
> schrieb am Do, 15.1.2009:
> > > 
> > > > Von: Todd Thiessen
> 
> > > > Betreff: RE: SCM plugin project
> > > > An: scm-dev@maven.apache.org
> > > > Datum: Donnerstag, 15. Januar 2009, 15:33 
> > > >
> http://www.mail-archive.com/scm-dev@maven.apache.org/msg01173.html
> > > > 
> > > > It seems I wasn't actually subscribed to
> scm-dev so I
> > > didn't' get this
> > > > response right away. Thanks for the response
> Mark.
> > > > 
> > > > I have actually tested this and have seen it
> fail. We have made 
> > > > modifications to SVN to print out the author
> differently.
> > > > I noticed the
> > > > problem when I tried running the changelog
> report and got
> > > no output.  
> > > > I was bashing my head on my desk trying to
> figure out why for the 
> > > > longest time ;-).
> > > > 
> > > > I have also already made the modifications
> to the 
> > > > maven-scm-provider-svnexe project and added
> all appropriate test 
> > > > cases.
> > > > My initial plan was to simply store a copy
> of the source 
> > in our svn 
> > > > repo. However, I now have permission to
> submit this to the proper 
> > > > place.
> > > > 
> > > > I will raise a JIRA to track the issue and
> then I would
> > > like to submit
> > > > a patch for all appropriate personnel to
> review.  Do I
> > > simply attach
> > > > an SVN patch to this mailing list?
> > > > 
> > > > ---
> > > > Todd Thiessen
> > > 
> > > 
> > >   
> > > 
> >

RE: SCM plugin project

[Todd Thiessen]

Are there any further comments regarding this? Do we need to open the
discussion to a wider audience to get some traction on it?

---
Todd Thiessen
 

> -Original Message-
> From: Thiessen, Todd (BVW:9T16) 
> Sent: Thursday, January 15, 2009 10:49 AM
> To: 'scm-dev@maven.apache.org'
> Subject: RE: SCM plugin project
> 
> Yes it occurs in a standard SVN installation. This is done by 
> using svn hooks which is precisely what we have.  Anyone can 
> change the output of the svn log command (ie: no change to 
> svn source is required).  So yes I definiately consider this 
> standard.  It isn't considered "default" behaviour, but I 
> would definitely describe it as standard.
> 
> It is my opinion that this fix should be in the main repo. 
> Individual users/companies should not have to maintain their 
> own copy of it. It makes synchronizing changes between the 
> main repo and all others an extra chore that shouldn't be necessary.
> 
> We should also take note that Subversion does not make any 
> guarantees regarding the format of the svn log author output. 
> They could very well change this "default" behaviour to 
> something that doesn't match what is currently being parsed. 
> So the fix I am proposing makes the code base more robust, 
> which is always a good thing.
> 
> ---
> Todd Thiessen
>  
> 
> > -Original Message-
> > From: Mark Struberg [mailto:strub...@yahoo.de]
> > Sent: Thursday, January 15, 2009 10:30 AM
> > To: scm-dev@maven.apache.org
> > Subject: RE: SCM plugin project
> > 
> > Humm, so this SVN behaviour cannot occur in a standard SVN 
> > installation? Or can this also be achieved by anyone? If 
> not, there is 
> > imho little chance of getting your changes into the upstream repo.
> > 
> > Do you have a parent pom for your projects? Have you tried 
> to override 
> > the dependency on maven-scm-provider-svnexe for your build to a 
> > locally patched version via  ?
> > 
> > I assume you have something like archiva, mavenproxy or nexus setup 
> > and also have a company-internal plugin repository, isn't?
> > 
> > So you could easily make the release process work for your company 
> > without having to release your changes to the public repo.
> > 
> > LieGrue,
> > strub
> > 
> > 
> > --- Todd Thiessen  schrieb am Do, 15.1.2009:
> > 
> > > Von: Todd Thiessen 
> > > Betreff: RE: SCM plugin project
> > > An: scm-dev@maven.apache.org
> > > Datum: Donnerstag, 15. Januar 2009, 15:33 
> > > http://www.mail-archive.com/scm-dev@maven.apache.org/msg01173.html
> > > 
> > > It seems I wasn't actually subscribed to scm-dev so I
> > didn't' get this
> > > response right away. Thanks for the response Mark.
> > > 
> > > I have actually tested this and have seen it fail. We have made 
> > > modifications to SVN to print out the author differently.
> > > I noticed the
> > > problem when I tried running the changelog report and got
> > no output.  
> > > I was bashing my head on my desk trying to figure out why for the 
> > > longest time ;-).
> > > 
> > > I have also already made the modifications to the 
> > > maven-scm-provider-svnexe project and added all appropriate test 
> > > cases.
> > > My initial plan was to simply store a copy of the source 
> in our svn 
> > > repo. However, I now have permission to submit this to the proper 
> > > place.
> > > 
> > > I will raise a JIRA to track the issue and then I would
> > like to submit
> > > a patch for all appropriate personnel to review.  Do I
> > simply attach
> > > an SVN patch to this mailing list?
> > > 
> > > ---
> > > Todd Thiessen
> > 
> > 
> >   
> > 
> 

RE: SCM plugin project

[Todd Thiessen]

Yes it occurs in a standard SVN installation. This is done by using svn
hooks which is precisely what we have.  Anyone can change the output of
the svn log command (ie: no change to svn source is required).  So yes I
definiately consider this standard.  It isn't considered "default"
behaviour, but I would definitely describe it as standard.

It is my opinion that this fix should be in the main repo. Individual
users/companies should not have to maintain their own copy of it. It
makes synchronizing changes between the main repo and all others an
extra chore that shouldn't be necessary.

We should also take note that Subversion does not make any guarantees
regarding the format of the svn log author output. They could very well
change this "default" behaviour to something that doesn't match what is
currently being parsed. So the fix I am proposing makes the code base
more robust, which is always a good thing.

---
Todd Thiessen
 

> -Original Message-
> From: Mark Struberg [mailto:strub...@yahoo.de] 
> Sent: Thursday, January 15, 2009 10:30 AM
> To: scm-dev@maven.apache.org
> Subject: RE: SCM plugin project
> 
> Humm, so this SVN behaviour cannot occur in a standard SVN 
> installation? Or can this also be achieved by anyone? If not, 
> there is imho little chance of getting your changes into the 
> upstream repo.
> 
> Do you have a parent pom for your projects? Have you tried to 
> override the dependency on maven-scm-provider-svnexe for your 
> build to a locally patched version via  ? 
> 
> I assume you have something like archiva, mavenproxy or nexus 
> setup and also have a company-internal plugin repository, isn't?
> 
> So you could easily make the release process work for your 
> company without having to release your changes to the public repo.
> 
> LieGrue,
> strub
> 
> 
> --- Todd Thiessen  schrieb am Do, 15.1.2009:
> 
> > Von: Todd Thiessen 
> > Betreff: RE: SCM plugin project
> > An: scm-dev@maven.apache.org
> > Datum: Donnerstag, 15. Januar 2009, 15:33 
> > http://www.mail-archive.com/scm-dev@maven.apache.org/msg01173.html
> > 
> > It seems I wasn't actually subscribed to scm-dev so I 
> didn't' get this 
> > response right away. Thanks for the response Mark.
> > 
> > I have actually tested this and have seen it fail. We have made 
> > modifications to SVN to print out the author differently.
> > I noticed the
> > problem when I tried running the changelog report and got 
> no output.  
> > I was bashing my head on my desk trying to figure out why for the 
> > longest time ;-).
> > 
> > I have also already made the modifications to the 
> > maven-scm-provider-svnexe project and added all appropriate test 
> > cases.
> > My initial plan was to simply store a copy of the source in our svn 
> > repo. However, I now have permission to submit this to the proper 
> > place.
> > 
> > I will raise a JIRA to track the issue and then I would 
> like to submit 
> > a patch for all appropriate personnel to review.  Do I 
> simply attach 
> > an SVN patch to this mailing list?
> > 
> > ---
> > Todd Thiessen
> 
> 
>   
> 

RE: SCM plugin project

[Mark Struberg]

Humm, so this SVN behaviour cannot occur in a standard SVN installation? Or can 
this also be achieved by anyone? If not, there is imho little chance of getting 
your changes into the upstream repo.

Do you have a parent pom for your projects? Have you tried to override the 
dependency on maven-scm-provider-svnexe for your build to a locally patched 
version via  ? 

I assume you have something like archiva, mavenproxy or nexus setup and also 
have a company-internal plugin repository, isn't?

So you could easily make the release process work for your company without 
having to release your changes to the public repo.

LieGrue,
strub


--- Todd Thiessen  schrieb am Do, 15.1.2009:

> Von: Todd Thiessen 
> Betreff: RE: SCM plugin project
> An: scm-dev@maven.apache.org
> Datum: Donnerstag, 15. Januar 2009, 15:33
> http://www.mail-archive.com/scm-dev@maven.apache.org/msg01173.html
> 
> It seems I wasn't actually subscribed to scm-dev so I
> didn't' get this
> response right away. Thanks for the response Mark.
> 
> I have actually tested this and have seen it fail. We have
> made
> modifications to SVN to print out the author differently. 
> I noticed the
> problem when I tried running the changelog report and got
> no output.  I
> was bashing my head on my desk trying to figure out why for
> the longest
> time ;-).
> 
> I have also already made the modifications to the
> maven-scm-provider-svnexe project and added all appropriate
> test cases.
> My initial plan was to simply store a copy of the source in
> our svn
> repo. However, I now have permission to submit this to the
> proper place.
> 
> I will raise a JIRA to track the issue and then I would
> like to submit a
> patch for all appropriate personnel to review.  Do I simply
> attach an
> SVN patch to this mailing list?
> 
> ---
> Todd Thiessen

RE: SCM plugin project

[Todd Thiessen]

http://www.mail-archive.com/scm-dev@maven.apache.org/msg01173.html

It seems I wasn't actually subscribed to scm-dev so I didn't' get this
response right away. Thanks for the response Mark.

I have actually tested this and have seen it fail. We have made
modifications to SVN to print out the author differently.  I noticed the
problem when I tried running the changelog report and got no output.  I
was bashing my head on my desk trying to figure out why for the longest
time ;-).

I have also already made the modifications to the
maven-scm-provider-svnexe project and added all appropriate test cases.
My initial plan was to simply store a copy of the source in our svn
repo. However, I now have permission to submit this to the proper place.

I will raise a JIRA to track the issue and then I would like to submit a
patch for all appropriate personnel to review.  Do I simply attach an
SVN patch to this mailing list?

---
Todd Thiessen

RE: SCM plugin project

[Mark Struberg]

If one can use such names (never tried that myself) then I totally aggree.
What happens if the Author has 3 names, e.g. "Mark Emil Struberg" ...

The simplest thing would be to setup a svn repo, add a change with such a user 
and do a 'svn log > src/test/resources/svn/changelog/svnlog_username.txt'

Then add a small test case in
maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/changelog/SvnChangeLogConsumerTest.java



LieGrue,
strub


--- Todd Thiessen  schrieb am Mi, 14.1.2009:

> Von: Todd Thiessen 
> Betreff: RE: SCM plugin project
> An: scm-dev@maven.apache.org
> Datum: Mittwoch, 14. Januar 2009, 15:08
> b). So I am moving this over to scm-dev ;-).
> 
> Ok, here are some of the details.
> 
> The problem is actually with the maven-scm-provider-svnexe
> project. More
> specifically, the changelog consumer
> (SvnChangeLogConsumer).
> 
> This class has a couple of regular expressions to parse the
> header of
> the svn log output. This regular expression isn't as
> robust as it could
> be.
> 
> The SvnChangeLogConsumer expects the author to be in a very
> specific
> format. Here is a snippet of the author regular expression.
> 
> (\\(\\S+\\s+\\S+\\)|\\S+)
> 
> This fits two basic formats for author:
> 
> (firstname lastname)
> 
> or
> 
> username
> 
> But what happens if the first or last name contains spaces?
> The entire
> header does not match and the changelog returns nothing.
> 
> Further, Subversion does not guarantee the format of the
> author. Hooks
> can be added to subversion to modify the author again
> resulting in an
> empty changelog.
> 
> The change log consumer should simply consume whatever is
> in the author
> section of the output to keep these kind of mismatches from
> happening.
> This allows for a header match to be found and the
> scm:changelog command
> to produce reasonable output.
> 
> So I recommend that we change the parsing of the author to
> pull in
> anything.
> 
> ---
> Todd Thiessen
>  
> 
> > -Original Message-
> > From: Mark Struberg [mailto:strub...@yahoo.de] 
> > Sent: Tuesday, January 13, 2009 5:49 PM
> > To: Maven Users List
> > Subject: RE: SCM plugin project
> > 
> > Hi Todd!
> > 
> > Is it a) an enhancement to the maven-scm-plugin
> itself?
> > Or b) does it dig deeper into maven-scm and we have to
> change 
> > the scm-API too?
> > 
> > For both options you'd probably file a Jira [1]
> which 
> > describes the motivation and the changes you like to
> do 
> > first. Then you may attach a patch or provide your
> changes 
> > via a online repo.
> > I personally would prefer git ;)
> > 
> > For option b) we should definitely switch over to the
> scm-dev 
> > list again.
> > 
> > LieGrue,
> > strub
> > 
> > [1] http://jira.codehaus.org/browse/SCM
> > 
> >

RE: SCM plugin project

[Todd Thiessen]

b). So I am moving this over to scm-dev ;-).

Ok, here are some of the details.

The problem is actually with the maven-scm-provider-svnexe project. More
specifically, the changelog consumer (SvnChangeLogConsumer).

This class has a couple of regular expressions to parse the header of
the svn log output. This regular expression isn't as robust as it could
be.

The SvnChangeLogConsumer expects the author to be in a very specific
format. Here is a snippet of the author regular expression.

(\\(\\S+\\s+\\S+\\)|\\S+)

This fits two basic formats for author:

(firstname lastname)

or

username

But what happens if the first or last name contains spaces? The entire
header does not match and the changelog returns nothing.

Further, Subversion does not guarantee the format of the author. Hooks
can be added to subversion to modify the author again resulting in an
empty changelog.

The change log consumer should simply consume whatever is in the author
section of the output to keep these kind of mismatches from happening.
This allows for a header match to be found and the scm:changelog command
to produce reasonable output.

So I recommend that we change the parsing of the author to pull in
anything.

---
Todd Thiessen
 

> -Original Message-
> From: Mark Struberg [mailto:strub...@yahoo.de] 
> Sent: Tuesday, January 13, 2009 5:49 PM
> To: Maven Users List
> Subject: RE: SCM plugin project
> 
> Hi Todd!
> 
> Is it a) an enhancement to the maven-scm-plugin itself?
> Or b) does it dig deeper into maven-scm and we have to change 
> the scm-API too?
> 
> For both options you'd probably file a Jira [1] which 
> describes the motivation and the changes you like to do 
> first. Then you may attach a patch or provide your changes 
> via a online repo.
> I personally would prefer git ;)
> 
> For option b) we should definitely switch over to the scm-dev 
> list again.
> 
> LieGrue,
> strub
> 
> [1] http://jira.codehaus.org/browse/SCM
> 
> 

RE: SCM plugin project

[Todd Thiessen]

I haven't gotten a response from an SCM plugin development person.
Perhaps someone on the Maven list could guide me in the right direction.
I would like contribute a fix to the SCM plugin. I am trying to build
the project but I have questions/issues.  Who can I talk to regarding
these?

Thanks all. And sorry for creating some noise on the Maven list.

---
Todd Thiessen
 

> -Original Message-
> From: Thiessen, Todd (BVW:9T16) 
> Sent: Friday, January 09, 2009 5:13 PM
> To: 'scm-dev@maven.apache.org'
> Cc: 'Maven Users List'
> Subject: SCM plugin project
> 
> I have downloaded the source for this project have and have a 
> number questions/concerns.
> 
> Most of the code seems be under the scm directory. ie:
> 
> http://svn.apache.org/repos/asf/maven/scm
> 
> There is a POM at the highest level, with an artifact ID of 
> maven-scm, which indicates many sub-directories as sub-modules.
> 
> However, there is one sub-module that confuses me: 
> maven-scm-plugin. You would normally expect the parent for 
> this pom to be the parent in the higher directory.
> 
> However, this isn't the case. Its parent is maven-plugins 
> which is a different artifact altogether. This really seems 
> to make building and versioning of the entire project confusing.
> 
> Do you release the maven-scm project or the maven-scm-plugin 
> project? I naturally expected to release the maven-scm 
> project but the maven-scm-plugin stands out in that it 
> doesn't define maven-scm as the parent and it also includes 
> all the maven-scm submodule projects as dependancies by 
> explicitly specifying their version. How are the version 
> numbers of all these dependencies incremented when a new 
> version of the plugin is released?
> 
> ---
> Todd Thiessen
> 

RE: SCM plugin project

[Todd Thiessen]

Thanks for the response Mark.

Are you considered an SCM committer/developer? I have a fix/enchancement
I would like to submit and am seeking some guidance.

If we should take this strictly to the scm-dev list that is fine too. I
don't want to create unnessary noice on the Maven list although there
may be others would are looking to do this too.

---
Todd Thiessen
 

> -Original Message-
> From: Mark Struberg [mailto:strub...@yahoo.de] 
> Sent: Tuesday, January 13, 2009 3:06 PM
> To: scm-dev@maven.apache.org; Maven Users List
> Subject: RE: SCM plugin project
> 
> Hi Todd!
> 
> maven-scm defines a SPI + a few plugins for various SCMs.   
> But although the name of the project is maven-scm it is not 
> only intended to be used with maven only. There are other 
> projecs (e.g. continuum) which use maven-scm for accessing 
> SCMs without maven.
> 
> The maven-scm-plugin on the other side is really a 
> maven-plugin! And maven-scm-plugin uses maven-scm to access 
> the SCM you are using.
> 
> That's the reason why maven-scm-plugin uses the common parent 
> pom used for all maven-plugins (see maven-plugin-plugin for 
> more details) and maven-scm doesn't.
> 
> 
> LieGrue,
> strub
> 
> --- Todd Thiessen  schrieb am Di, 13.1.2009:
> 
> > Von: Todd Thiessen 
> > Betreff: RE: SCM plugin project
> > An: scm-dev@maven.apache.org
> > CC: "Maven Users List" 
> > Datum: Dienstag, 13. Januar 2009, 18:47 I haven't gotten a response 
> > from an SCM plugin development person.
> > Perhaps someone on the Maven list could guide me in the right 
> > direction.
> > I would like contribute a fix to the SCM plugin. I am 
> trying to build 
> > the project but I have questions/issues.  Who can I talk to 
> regarding 
> > these?
> > 
> > Thanks all. And sorry for creating some noise on the Maven list.
> > 
> > ---
> > Todd Thiessen
> >  
> > 
> > > -Original Message-
> > > From: Thiessen, Todd (BVW:9T16)
> > > Sent: Friday, January 09, 2009 5:13 PM
> > > To: 'scm-dev@maven.apache.org'
> > > Cc: 'Maven Users List'
> > > Subject: SCM plugin project
> > > 
> > > I have downloaded the source for this project have and
> > have a
> > > number questions/concerns.
> > > 
> > > Most of the code seems be under the scm directory. ie:
> > > 
> > > http://svn.apache.org/repos/asf/maven/scm
> > > 
> > > There is a POM at the highest level, with an artifact
> > ID of
> > > maven-scm, which indicates many sub-directories as
> > sub-modules.
> > > 
> > > However, there is one sub-module that confuses me: 
> > > maven-scm-plugin. You would normally expect the parent
> > for
> > > this pom to be the parent in the higher directory.
> > > 
> > > However, this isn't the case. Its parent is
> > maven-plugins
> > > which is a different artifact altogether. This really
> > seems
> > > to make building and versioning of the entire project
> > confusing.
> > > 
> > > Do you release the maven-scm project or the
> > maven-scm-plugin
> > > project? I naturally expected to release the maven-scm
> > 
> > > project but the maven-scm-plugin stands out in that it
> > 
> > > doesn't define maven-scm as the parent and it also
> > includes
> > > all the maven-scm submodule projects as dependancies
> > by
> > > explicitly specifying their version. How are the
> > version
> > > numbers of all these dependencies incremented when a
> > new
> > > version of the plugin is released?
> > > 
> > > ---
> > > Todd Thiessen
> > > 
> > 
> > 
> -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail:
> > users-h...@maven.apache.org
> 
> 
>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

Re: accurev provider

[Mark Struberg]

> Via the command line.

fine, just 2 make sure that we don't get license troubles.

LieGrue,
strub


--- Ivan Luzyanin  schrieb am Di, 13.1.2009:

> Von: Ivan Luzyanin 
> Betreff: Re: accurev provider
> An: scm-dev@maven.apache.org
> Datum: Dienstag, 13. Januar 2009, 12:04
> Via the command line.
> 
> 
> struberg wrote:
> > 
> > slightly OT: the JDK1.5 question also applies to the
> native Java
> > implementation of maven-scm-providers-git.
> > 
> > This is now even more interesting as Shawn changed the
> license of egit
> > from LGPL to BSD a while ago. This means we have no
> license problems
> > anymore.
> > 
> > Grant, I've not yet looked at the accurev code,
> but how does it invoke the
> > SCM? Via API or via command line?
> > 
> > LieGrue,
> > strub 
> > 
> > 
> > --- ggardner  schrieb
> am Di, 13.1.2009:
> > 
> >> Von: ggardner 
> >> Betreff: Re: accurev provider
> >> An: scm-dev@maven.apache.org
> >> Datum: Dienstag, 13. Januar 2009, 11:14
> >> Thanks, I wanted an excuse to try out a coverage
> tool. 6
> >> more lines in the
> >> pom and Cobertura tells me 90% coverage.
> >> 
> >> Though one immediate question is whether it is
> acceptable
> >> for one provider
> >> to require JDK 1.5. If not I'll have to remove
> JDK 1.5
> >> dependancies
> >> (generics, JMock, JUnit4) that were useful for
> putting it
> >> all together in a
> >> TDD fashion.
> >> 
> >> Grant.
> >> 
> >> On Mon, 12 Jan 2009 12:21:15 -0800, Jason van Zyl
> >> 
> >> wrote:
> >> > If you got code then you need to accompany it
> with
> >> complete tests or
> >> > we're likely not to look at it.
> >> > 
> >> > On 12-Jan-09, at 4:51 AM, ggardner wrote:
> >> > 
> >> >>
> >> >> Hi all,
> >> >>
> >> >> I've been working on extending the
> AccuRev
> >> provider implementation
> >> >> to be
> >> >> fully compatible with the maven release
> plugin.
> >> >> (ie update, status, checkin, tag,
> checkout, add)
> >> >>
> >> >> I think I'm pretty close with the
> necessary
> >> commands implemented and
> >> >> the
> >> >> tck tests passing against an AccuRev
> evaluation
> >> install.
> >> >>
> >> >> Assuming someone here is interested
> I'll have
> >> a bunch of questions
> >> >> about
> >> >> how I might go about contributing this
> code.
> >> >>
> >> >> Cheers,
> >> >> Grant.
> >> >>
> >> >>
> >> >>
> >> > 
> >> > Thanks,
> >> > 
> >> > Jason
> >> > 
> >> >
> >>
> --
> >> > Jason van Zyl
> >> > Founder,  Apache Maven
> >> > jason at sonatype dot com
> >> >
> >>
> --
> >> > 
> >> > What matters is not ideas, but the people who
> have
> >> them. Good people
> >> > can fix bad ideas, but good ideas can't
> save bad
> >> people.
> >> > 
> >> >   -- Paul Graham
> > 
> > 
> > 
> > 
> > 
> 
> -- 
> View this message in context:
> http://www.nabble.com/accurev-provider-tp21413963p2149.html
> Sent from the Maven - SCM mailing list archive at
> Nabble.com.

Re: accurev provider

[Ivan Luzyanin]

Via the command line.


struberg wrote:
> 
> slightly OT: the JDK1.5 question also applies to the native Java
> implementation of maven-scm-providers-git.
> 
> This is now even more interesting as Shawn changed the license of egit
> from LGPL to BSD a while ago. This means we have no license problems
> anymore.
> 
> Grant, I've not yet looked at the accurev code, but how does it invoke the
> SCM? Via API or via command line?
> 
> LieGrue,
> strub 
> 
> 
> --- ggardner  schrieb am Di, 13.1.2009:
> 
>> Von: ggardner 
>> Betreff: Re: accurev provider
>> An: scm-dev@maven.apache.org
>> Datum: Dienstag, 13. Januar 2009, 11:14
>> Thanks, I wanted an excuse to try out a coverage tool. 6
>> more lines in the
>> pom and Cobertura tells me 90% coverage.
>> 
>> Though one immediate question is whether it is acceptable
>> for one provider
>> to require JDK 1.5. If not I'll have to remove JDK 1.5
>> dependancies
>> (generics, JMock, JUnit4) that were useful for putting it
>> all together in a
>> TDD fashion.
>> 
>> Grant.
>> 
>> On Mon, 12 Jan 2009 12:21:15 -0800, Jason van Zyl
>> 
>> wrote:
>> > If you got code then you need to accompany it with
>> complete tests or
>> > we're likely not to look at it.
>> > 
>> > On 12-Jan-09, at 4:51 AM, ggardner wrote:
>> > 
>> >>
>> >> Hi all,
>> >>
>> >> I've been working on extending the AccuRev
>> provider implementation
>> >> to be
>> >> fully compatible with the maven release plugin.
>> >> (ie update, status, checkin, tag, checkout, add)
>> >>
>> >> I think I'm pretty close with the necessary
>> commands implemented and
>> >> the
>> >> tck tests passing against an AccuRev evaluation
>> install.
>> >>
>> >> Assuming someone here is interested I'll have
>> a bunch of questions
>> >> about
>> >> how I might go about contributing this code.
>> >>
>> >> Cheers,
>> >> Grant.
>> >>
>> >>
>> >>
>> > 
>> > Thanks,
>> > 
>> > Jason
>> > 
>> >
>> --
>> > Jason van Zyl
>> > Founder,  Apache Maven
>> > jason at sonatype dot com
>> >
>> --
>> > 
>> > What matters is not ideas, but the people who have
>> them. Good people
>> > can fix bad ideas, but good ideas can't save bad
>> people.
>> > 
>> >   -- Paul Graham
> 
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/accurev-provider-tp21413963p2149.html
Sent from the Maven - SCM mailing list archive at Nabble.com.

Re: accurev provider

[Mark Struberg]

slightly OT: the JDK1.5 question also applies to the native Java implementation 
of maven-scm-providers-git.

This is now even more interesting as Shawn changed the license of egit from 
LGPL to BSD a while ago. This means we have no license problems anymore.

Grant, I've not yet looked at the accurev code, but how does it invoke the SCM? 
Via API or via command line?

LieGrue,
strub 


--- ggardner  schrieb am Di, 13.1.2009:

> Von: ggardner 
> Betreff: Re: accurev provider
> An: scm-dev@maven.apache.org
> Datum: Dienstag, 13. Januar 2009, 11:14
> Thanks, I wanted an excuse to try out a coverage tool. 6
> more lines in the
> pom and Cobertura tells me 90% coverage.
> 
> Though one immediate question is whether it is acceptable
> for one provider
> to require JDK 1.5. If not I'll have to remove JDK 1.5
> dependancies
> (generics, JMock, JUnit4) that were useful for putting it
> all together in a
> TDD fashion.
> 
> Grant.
> 
> On Mon, 12 Jan 2009 12:21:15 -0800, Jason van Zyl
> 
> wrote:
> > If you got code then you need to accompany it with
> complete tests or
> > we're likely not to look at it.
> > 
> > On 12-Jan-09, at 4:51 AM, ggardner wrote:
> > 
> >>
> >> Hi all,
> >>
> >> I've been working on extending the AccuRev
> provider implementation
> >> to be
> >> fully compatible with the maven release plugin.
> >> (ie update, status, checkin, tag, checkout, add)
> >>
> >> I think I'm pretty close with the necessary
> commands implemented and
> >> the
> >> tck tests passing against an AccuRev evaluation
> install.
> >>
> >> Assuming someone here is interested I'll have
> a bunch of questions
> >> about
> >> how I might go about contributing this code.
> >>
> >> Cheers,
> >> Grant.
> >>
> >>
> >>
> > 
> > Thanks,
> > 
> > Jason
> > 
> >
> --
> > Jason van Zyl
> > Founder,  Apache Maven
> > jason at sonatype dot com
> >
> --
> > 
> > What matters is not ideas, but the people who have
> them. Good people
> > can fix bad ideas, but good ideas can't save bad
> people.
> > 
> >   -- Paul Graham

Re: accurev provider

[ggardner]

Thanks, I wanted an excuse to try out a coverage tool. 6 more lines in the
pom and Cobertura tells me 90% coverage.

Though one immediate question is whether it is acceptable for one provider
to require JDK 1.5. If not I'll have to remove JDK 1.5 dependancies
(generics, JMock, JUnit4) that were useful for putting it all together in a
TDD fashion.

Grant.

On Mon, 12 Jan 2009 12:21:15 -0800, Jason van Zyl 
wrote:
> If you got code then you need to accompany it with complete tests or
> we're likely not to look at it.
> 
> On 12-Jan-09, at 4:51 AM, ggardner wrote:
> 
>>
>> Hi all,
>>
>> I've been working on extending the AccuRev provider implementation
>> to be
>> fully compatible with the maven release plugin.
>> (ie update, status, checkin, tag, checkout, add)
>>
>> I think I'm pretty close with the necessary commands implemented and
>> the
>> tck tests passing against an AccuRev evaluation install.
>>
>> Assuming someone here is interested I'll have a bunch of questions
>> about
>> how I might go about contributing this code.
>>
>> Cheers,
>> Grant.
>>
>>
>>
> 
> Thanks,
> 
> Jason
> 
> --
> Jason van Zyl
> Founder,  Apache Maven
> jason at sonatype dot com
> --
> 
> What matters is not ideas, but the people who have them. Good people
> can fix bad ideas, but good ideas can't save bad people.
> 
>   -- Paul Graham

Re: accurev provider

[Jason van Zyl]

If you got code then you need to accompany it with complete tests or  
we're likely not to look at it.


On 12-Jan-09, at 4:51 AM, ggardner wrote:



Hi all,

I've been working on extending the AccuRev provider implementation  
to be

fully compatible with the maven release plugin.
(ie update, status, checkin, tag, checkout, add)

I think I'm pretty close with the necessary commands implemented and  
the

tck tests passing against an AccuRev evaluation install.

Assuming someone here is interested I'll have a bunch of questions  
about

how I might go about contributing this code.

Cheers,
Grant.





Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
--

What matters is not ideas, but the people who have them. Good people  
can fix bad ideas, but good ideas can't save bad people.


 -- Paul Graham

RE: Issues for 1.1.1

[Banck, Arent-Jan]

Hi,
Not sure what the status is of 1.1.1, but hope SCM-415
(http://jira.codehaus.org/browse/SCM-415) can be scheduled for 1.1.1.
This case has a patch attached. It fixes a 1.1 regression breaking
Perforce usage.

Thanks,

Arent-Jan

-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 04, 2008 3:26 AM
To: scm-dev@maven.apache.org
Subject: Issues for 1.1.1

Hi folks,

I reduced the number of issues for 1.1.1 (scheduled in September). If
someone wants specific issues, please ask!
Here is the actual release note:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14522&styleName
=Text&projectId=10527&Create=Create

BTW SCM-406 seems to be a none issue.

Cheers,

Vincent

Re: Error with new SCM provider

[subhashgo]

Thanks,

But I am almost sure this is not the issue. I specified the plexus javadoc
tags correctly and the installed provider jar does have a similar
components.xml under META-INF/plexus

Subhash


Alexey Kakunin-3 wrote:
> 
> Hi!I cannot be sure 100% I'm right, since I'm not maven-scm developer, but
> it I've got same error then plexus component manager, used for creating
> provider class but specified scm name cannot find it.
> 
> Possible solution: Add into your project META-INF folder folder plexus,
> and
> file components.xml into it like followed:
> http://www.emforge.org/project/ExtendedMavenSCM/browser/maven-scm-provider-hg/src/main/resources/META-INF/plexus/components.xml
> 
> (of course don't forget to change it to your scm name and class)
> 
> Hope it will help!
> 
> Not sure 100% but it looks like
> 
> 2008/10/21 subhashgo <[EMAIL PROTECTED]>
> 
>>
>> I tried to replicate the steps from
>> http://maven.apache.org/scm/guide/new_provider.html but keep hitting the
>> same error while executing "mvn scm:list"
>>
>> org.apache.maven.scm.manager.NoSuchScmProviderException: No such
>> provider:
>> 'myown'.
>>
>> I looked up this forum for clues and found
>> http://www.nabble.com/Custom-SCM-Provider-td13305922.html but that seems
>> outdated since the dependencies etc. mentioned in the pom differ so much
>>
>> Here are the steps I followed:
>> 1. Create a maven project with the name maven-scm-provider-myown
>> 2. Replicate pom.xml, MyScmProvider and MyScmProviderRepository from the
>> tutorial page above
>> 3. Run "mvn install" on the above project. The jar seems to be created
>> fine
>> in the repository
>> 4. Run "mvn scm:list" on a different project with connection
>> scm:myown:...
>>
>> Please help me understand what I am doing wrong here.
>>
>> Thanks in advance,
>> Subhash
>> --
>> View this message in context:
>> http://www.nabble.com/Error-with-new-SCM-provider-tp20078538p20078538.html
>> Sent from the Maven - SCM mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> With best regards,
> Alexey Kakunin
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Error-with-new-SCM-provider-tp20078538p20079017.html
Sent from the Maven - SCM mailing list archive at Nabble.com.

Re: Error with new SCM provider

[Alexey Kakunin]

OK - as I said - I'm not maven-scm developer to be sure in my suggestion

2008/10/21 subhashgo <[EMAIL PROTECTED]>

>
> Thanks,
>
> But I am almost sure this is not the issue. I specified the plexus javadoc
> tags correctly and the installed provider jar does have a similar
> components.xml under META-INF/plexus
>
> Subhash
>
>
> Alexey Kakunin-3 wrote:
> >
> > Hi!I cannot be sure 100% I'm right, since I'm not maven-scm developer,
> but
> > it I've got same error then plexus component manager, used for creating
> > provider class but specified scm name cannot find it.
> >
> > Possible solution: Add into your project META-INF folder folder plexus,
> > and
> > file components.xml into it like followed:
> >
> http://www.emforge.org/project/ExtendedMavenSCM/browser/maven-scm-provider-hg/src/main/resources/META-INF/plexus/components.xml
> >
> > (of course don't forget to change it to your scm name and class)
> >
> > Hope it will help!
> >
> > Not sure 100% but it looks like
> >
> > 2008/10/21 subhashgo <[EMAIL PROTECTED]>
> >
> >>
> >> I tried to replicate the steps from
> >> http://maven.apache.org/scm/guide/new_provider.html but keep hitting
> the
> >> same error while executing "mvn scm:list"
> >>
> >> org.apache.maven.scm.manager.NoSuchScmProviderException: No such
> >> provider:
> >> 'myown'.
> >>
> >> I looked up this forum for clues and found
> >> http://www.nabble.com/Custom-SCM-Provider-td13305922.html but that
> seems
> >> outdated since the dependencies etc. mentioned in the pom differ so much
> >>
> >> Here are the steps I followed:
> >> 1. Create a maven project with the name maven-scm-provider-myown
> >> 2. Replicate pom.xml, MyScmProvider and MyScmProviderRepository from the
> >> tutorial page above
> >> 3. Run "mvn install" on the above project. The jar seems to be created
> >> fine
> >> in the repository
> >> 4. Run "mvn scm:list" on a different project with connection
> >> scm:myown:...
> >>
> >> Please help me understand what I am doing wrong here.
> >>
> >> Thanks in advance,
> >> Subhash
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Error-with-new-SCM-provider-tp20078538p20078538.html
> >> Sent from the Maven - SCM mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > With best regards,
> > Alexey Kakunin
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Error-with-new-SCM-provider-tp20078538p20079017.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
>


-- 
With best regards,
Alexey Kakunin

Re: Error with new SCM provider

[Alexey Kakunin]

Hi!I cannot be sure 100% I'm right, since I'm not maven-scm developer, but
it I've got same error then plexus component manager, used for creating
provider class but specified scm name cannot find it.

Possible solution: Add into your project META-INF folder folder plexus, and
file components.xml into it like followed:
http://www.emforge.org/project/ExtendedMavenSCM/browser/maven-scm-provider-hg/src/main/resources/META-INF/plexus/components.xml

(of course don't forget to change it to your scm name and class)

Hope it will help!

Not sure 100% but it looks like

2008/10/21 subhashgo <[EMAIL PROTECTED]>

>
> I tried to replicate the steps from
> http://maven.apache.org/scm/guide/new_provider.html but keep hitting the
> same error while executing "mvn scm:list"
>
> org.apache.maven.scm.manager.NoSuchScmProviderException: No such provider:
> 'myown'.
>
> I looked up this forum for clues and found
> http://www.nabble.com/Custom-SCM-Provider-td13305922.html but that seems
> outdated since the dependencies etc. mentioned in the pom differ so much
>
> Here are the steps I followed:
> 1. Create a maven project with the name maven-scm-provider-myown
> 2. Replicate pom.xml, MyScmProvider and MyScmProviderRepository from the
> tutorial page above
> 3. Run "mvn install" on the above project. The jar seems to be created fine
> in the repository
> 4. Run "mvn scm:list" on a different project with connection scm:myown:...
>
> Please help me understand what I am doing wrong here.
>
> Thanks in advance,
> Subhash
> --
> View this message in context:
> http://www.nabble.com/Error-with-new-SCM-provider-tp20078538p20078538.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
>


-- 
With best regards,
Alexey Kakunin