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 /mav
y, 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 :
&g
Hi olivier!
what was the reason for the following change?
-assertEquals( "cd3c0dfacb65955e6fbb35c56cc5b1bf8ce4f767",
result.getInfoItems().get( 0 ).getRevision() );
+assertEquals( "d42193018c2fc462a103ef6440cd162d73595c53",
result.getInfoItems().get( 0 ).getRevision() );
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 Clarkso
- 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-provi
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
Hi Thomas!
Have you searched maven-scm JIRA [1] for a respective issue?
If you can't find it there, it most probably hasn't been started yet.
LieGrue,
strub
[1] http://jira.codehaus.org/browse/SCM
--- Lageson, Thomas (STP) schrieb am Do, 18.6.2009:
> Von: Lageson, Thomas (STP)
> Betreff: M
Hi!
I'm currently implementing the maven-scm-providers-jgit and like to know how
others did handle e.g. CheckOutScmResult for Java implemented SCM connectors.
Especially what to do if an Exception occurred? How do you transport this
nested Exception? fill only e.getMessage() or is there a tric
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 i
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
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
> ver
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
mran 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
>
> 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!
> >
> > Hav
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.
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
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 u
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
&
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:
ht
+1
I'm currently working on SCM-403, should be rdy till tomorrow.
LieGrue,
strub
--- Olivier Lamy schrieb am So, 15.3.2009:
> Von: Olivier Lamy
> Betreff: SCM-262 and next scm release version number
> An: scm-dev@maven.apache.org
> Datum: Sonntag, 15. März 2009, 13:58
> Hi,
> As SCM-262 will
d 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.
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
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
; 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 ou
> 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.
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 accu
> And why you don't want to use this structure ?.
I guess the main argument is that eclipse cannot nest projects, so there's no
way to edit your parent pom (+ parent site, etc) with eclipse (instead you have
to vi + svn commit on the command line).
BUT: My gut feeling tells me that this is no m
I assume this is also a problem within maven-scm-1.0, isn't?
So releasing maven-scm-1.1 doesn't make it worse, and we should address this
issue in 1.1.1
Only my private opinion, but as someone already mentioned, if we wait for all
errors to be fixed, then we'll never get anything released.
LieG
+1
LieGrü,
strub
--- Olivier Lamy <[EMAIL PROTECTED]> schrieb am Sa, 23.8.2008:
> Von: Olivier Lamy <[EMAIL PROTECTED]>
> Betreff: [VOTE] Release Maven Scm 1.1 (take 3)
> An: "Maven Developers List" <[EMAIL PROTECTED]>, scm-dev@maven.apache.org
> Datum: Samstag, 23. August 2008, 20:23
> Hi,
> T
+1 from me
A few broken links as Vince said, but the rest looks ok at the first glance.
additional question: I hope it's ok that I updated the SCM Matrix @ codehaus? I
added the git features, but acurev are still missing there...
I wrote the "available since maven-scm-1.1" as comment as it is c
Hi folks!
Since there has been a discussion about the maven-scm-1.1 due date in
http://jira.codehaus.org/browse/SCM-182
, I'd like to ask if you guys (and girls if any) have something in mind with
maven-scm-1.1?
Is there a chance to get it released and packaged with maven-2.0.10?
Aditional ques
-fetch tag [tagname]
Summary: all is ok if using the latest versions, but it may not work with older
maven versions.
LieGrü,
strub
PS: Brett, thanks for applying the patch and fixing the test!
--- Mark Struberg <[EMAIL PROTECTED]> schrieb:
> Hi Brett!
> I'm currently working on a
> New Revision: 645182
> >
> > URL: http://svn.apache.org/viewvc?rev=645182&view=rev
> > Log:
> > SCM-182: Adding a GIT provider
> > Submitted by: mark struberg and eugene kuleshov
>
> The other commit reminded me. Given the size of this contribution, I
> thin
Hi folks!
I hope we soon have the git provider finally up and running in Subversion.
So, since I today wrote my first 'Jiraffe' on this topic, I now have an orga
Question:
First, when should we create an own component for this provider in the JIRA SCM
Project, and whom
may I ask to do it?
2nd:
34 matches
Mail list logo