On 1/24/24 6:31 AM, Konrad Windszus wrote:
Ping, does anyone have any input on this? Would be much appreciated,
Thanks,
Konrad
On 8. Jan 2024, at 19:16, Konrad Windszus wrote:
Hi,
According to https://maven.apache.org/pom/maven/#the-format-profile the git
commits created through applying
Ping, does anyone have any input on this? Would be much appreciated,
Thanks,
Konrad
> On 8. Jan 2024, at 19:16, Konrad Windszus wrote:
>
> Hi,
>
> According to https://maven.apache.org/pom/maven/#the-format-profile the git
> commits created through applying the spotless formatting should be ig
Hi,
According to https://maven.apache.org/pom/maven/#the-format-profile the git
commits created through applying the spotless formatting should be ignored via
a .git-blame-ignore-revs file. This file is automatically evaluated by GitHub
blame view. This doesn’t work well if the formatting also
https://jira.codehaus.org/browse/MRELEASE-723
> From: mfriedenha...@gmail.com
> Date: Tue, 20 Dec 2011 21:14:59 +0100
> Subject: Re: maven-release-plugin: using git where do I see the tag used to
> build the release in the pom?
> To: dev@maven.apache.org
>
> Hello,
>
Hello,
I erroneously opened the issue in the SCM plugin
(https://jira.codehaus.org/browse/SCM-655), however it is an issue of
MRELEASE probably. Would someone with the according rights move it to
http://jira.codehaus.org/browse/MRELEASE, please?
Best regards Mirko
On Mon, Dec 19, 2011 at 22:56,
Then it will have to be the tag name so...
On 19 December 2011 21:28, Mirko Friedenhagen wrote:
> Hm, this will be a hard one. I know detected, that the rewrite of the
> SCM section happens in the maven-release-plugin
> (org.apache.maven.shared.release.phase.RewritePomsForReleasePhase).
> Two pro
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
(org.apache.maven.shared.release.phase.RewritePomsForReleasePhase).
Two problemes I encountered now:
- The maven-scm-plugin does not seem to implement the equivalent of
"scm:info" (
some scm providers have something implemented.
for git it's : git rev-parse --verify HEAD
for svn: svn info
for hg: hg id
more details on those providers in various Info command impls.
2011/12/19 Stephen Connolly :
> On 19 December 2011 10:45, Mirko Friedenhagen wrote:
>> As discussed on the us
On 19 December 2011 10:45, Mirko Friedenhagen wrote:
> As discussed on the user-list:
>
>>> > > > On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
>>> > > > wrote:
>>> > > > > Hello,
>>> > > > >
>>> > > > > I know that with SVN the developerConnection and connection are
>>> > > > > updated to th
As discussed on the user-list:
>> > > > On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
>> > > > wrote:
>> > > > > Hello,
>> > > > >
>> > > > > I know that with SVN the developerConnection and connection are
>> > > > > updated to the "real" URL, that is when I invoke release:prepare
>> > > > >
Milos, with all respect: Unless Nigel is an employee of or paid by
Microsoft, IBM, or whoever might have a professional interest in the
decline of NetBeans, I do think that's a valid expression of an
opinion.
On Mon, May 11, 2009 at 8:12 AM, Milos Kleint wrote:
> On Wed, Apr 29, 2009 at 10:34 PM
On Wed, Apr 29, 2009 at 10:34 PM, Nigel Magnay wrote:
> > My vote does not really count here, but Sun aggressively
> supports
> > Mercurial in NetBeans. Based on reviews, Mercurial seemed to initially
> have
> > a technical edge whereas GIT had a loyal following. They do compete
> > aggressively
> My vote does not really count here, but Sun aggressively supports
> Mercurial in NetBeans. Based on reviews, Mercurial seemed to initially have
> a technical edge whereas GIT had a loyal following. They do compete
> aggressively and GIT has fixed many of its issues.
>
> NetBeans works better wi
in context:
http://www.nabble.com/Using-GIT-as-the-canonical-repository-for-Maven-3.x-tp23201420p23301063.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr
ntony Stubbs
Reply-to: "Maven Developers List"
To: dev@maven.apache.org
Subject: Re: Using GIT as the canonical repository for Maven 3.x
Date: Fri, 24 Apr 2009 17:57:51 -0700 (PDT)
multiple branches in 1 repo (in hg
last time i looked you have to create a new copy to checkout a d
> Do you see that Google choose Mercurial rather than Git ?
>
> Mercurial support for Project Hosting on Google Code
> http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html
>
> Analysis of Git and Mercurial
> http://code.google.com/p/support/wiki/DVCSAnalysis
>
2009/4/27 Rémy Sanlaville
> Do you see that Google choose Mercurial rather than Git ?
>
well, they didn't exactly choose one over the other - they decided to
implement Mercurial support first because it fitted better (at the time)
with GoogleCode hosting - I wouldn't be surprised to see Git supp
Do you see that Google choose Mercurial rather than Git ?
Mercurial support for Project Hosting on Google Code
http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html
Analysis of Git and Mercurial
http://code.google.com/p/support/wiki/DVCSAnalysis
Rémy
The gitexe has already the full maven-sm-test TCK suite implemented. So all the
things like a prepackaged git repo for the TCK is already there.
LieGrue,
strub
--- Brian Fox schrieb am Sa, 25.4.2009:
> Von: Brian Fox
> Betreff: Re: Using GIT as the canonical repository for Maven 3.
If you like me to help then simply ping me, I'd be honoured to help.
I didn't dive into the testing structure in place there, but if it
doesn't exist already, some external ITs would be awesome. Something we
could run against the multiple implementations to guarantee compatibility.
---
d the need) to start to
implement the jgit part.
But it should be really easy to add it.
If you like me to help then simply ping me, I'd be honoured to help.
LieGrue,
strub
--- Brian Fox schrieb am Sa, 25.4.2009:
> Von: Brian Fox
> Betreff: Re: Using GIT as the canonical repo
a separate directory.
-
___
http://stubbisms.wordpress.com http://stubbisms.wordpress.com
--
View this message in context:
http://www.nabble.com/Using-GIT-as-the-canonical-repository-for-Maven-3.x-tp23201420p23227239.html
Sent from the Maven Developers mailing list a
y a clean checkout into a separate directory.
> >
>
>
> -
> ___
>
> http://stubbisms.wordpress.com http://stubbisms.wordpress.com
> --
> View this message in context:
> http://www.nabble.com/Using-GIT-a
all rubbish from
.gitignore left in your working directory. And this may affect the build ...
LieGrue,
strub
--- Antony Stubbs schrieb am Sa, 25.4.2009:
> Von: Antony Stubbs
> Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> An: dev@maven.apache.org
> Datum: Samsta
n't checked in or ignored but
> somehow affect the compile or test outcome. This may imho only be
> guaranteed by a clean checkout into a separate directory.
>
-
___
http://stubbisms.wordpress.com http://stubbisms.wordpress.com
--
View this message i
; Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> --
>>>
>>> In short, man creates for himself a new religion of a rational
>>> and technical order to justify his
ail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
> --
> Arnaud
>
>
-
___
http://stubbisms.wordpress.com http://stubbisms.wordpress.com
--
View this messa
On 24-Apr-09, at 11:17 AM, Robert Burrell Donkin wrote:
Correct. The model that Android uses I would say is optimal for an
open source project. People can take real copies and derive all the
benefit from that, but they push to a gatekeeper where submissions
are
vetted. Gerrit represents som
> If developers here were truly interested they would ask and I'm
always > happy to answer specific questions.
I'd just like to point out one thing: it's not necessarily lack of
interest that can keep developers out of the picture, but also an
inability to keep up. Too much project velocity c
Yes I agree. Only the canonical code can be used to produce official
maven builds and those tags are pushed back to the master. No different
really than what happens today.
On 4/24/2009 4:53 PM, John Casey wrote:
There is one very important issue with dscm:
To be in line with our goals for Ma
There is one very important issue with dscm:
To be in line with our goals for Maven in general - especially
reproducibility - the tag created from a release MUST be available for
others to grab and rebuild from. This means that a git push is
absolutely necessary to finish off the release proce
ectory?
isn't the scm tag supposed to give you the relative path to the pom's
parent folder?
could we not just parse the scm URL to get the git root relative path
to the pom
LieGrue,
strub
--- Brian Fox schrieb am Fr, 24.4.2009:
Von: Brian Fox
Betreff: Re: U
not a technical one. Gerrit may
also check for a 'ASL2 license granted' flag like it's solved in
issues.apache.org for patches.
LieGrue,
strub
--- Robert Burrell Donkin schrieb am Fr,
24.4.2009:
> Von: Robert Burrell Donkin
> Betreff: Re: Using GIT as the canonical reposito
On 4/24/09, Jason van Zyl wrote:
>
> On 24-Apr-09, at 7:55 AM, Robert Burrell Donkin wrote:
>
>> On Fri, Apr 24, 2009 at 3:46 PM, Jason van Zyl
>> wrote:
>>> On 24-Apr-09, at 7:36 AM, Robert Burrell Donkin wrote:
>>>
>
> Is sounds like the process used by our release plugin doesn't
>
On 24-Apr-09, at 7:55 AM, Robert Burrell Donkin wrote:
On Fri, Apr 24, 2009 at 3:46 PM, Jason van Zyl
wrote:
On 24-Apr-09, at 7:36 AM, Robert Burrell Donkin wrote:
Is sounds like the process used by our release plugin doesn't
really
match
the way git works, so maybe we can change the w
On Fri, Apr 24, 2009 at 3:46 PM, Jason van Zyl wrote:
> On 24-Apr-09, at 7:36 AM, Robert Burrell Donkin wrote:
>
>>>
>>> Is sounds like the process used by our release plugin doesn't really
>>> match
>>> the way git works, so maybe we can change the way the release plugin
>>> works
>>> instead of
I have been starting to play with git for the jetty @ eclipse source
base, still backed by svn but just to get a feel for how it
works...and its pretty neat.
that said, I would say that maven3 is the prime mvn target to iron out
the mvn issues with release plugins and all the other core toolchain
On 24-Apr-09, at 7:36 AM, Robert Burrell Donkin wrote:
Is sounds like the process used by our release plugin doesn't
really match
the way git works, so maybe we can change the way the release
plugin works
instead of trying to fit git into our model. Do we really need to
do a
clean checko
On Fri, Apr 24, 2009 at 3:20 PM, Paul Gier wrote:
> Mark Struberg wrote:
>>
>> Hi!
>>
>> I thought in a similar direction. I think we can even let the maven-scm as
>> it is.
>> The problematic usecase is if we have a multi-module build and like to
>> release only one of the sub modules.
>>
>> John
On 24-Apr-09, at 10:20 , Paul Gier wrote:
Mark Struberg wrote:
Is sounds like the process used by our release plugin doesn't really
match the way git works, so maybe we can change the way the release
plugin works instead of trying to fit git into our model. Do we
really need to do a clea
y.
> process doesn't really match the way git works
I have the gut feeling that there are quite a few SCMs out there (accurev, hg,
PVCS, git,..) which work that way and they only got not enough love yet ;)
LieGrue,
strub
--- Paul Gier schrieb am Fr, 24.4.2009:
> Von: Paul Gier
> Be
Mark Struberg wrote:
Hi!
I thought in a similar direction. I think we can even let the maven-scm as it is.
The problematic usecase is if we have a multi-module build and like to release
only one of the sub modules.
John Casey prepared an example for this use case:
$> git-clone http://www.co
On 24-Apr-09, at 4:24 AM, Raphaël Piéroni wrote:
Hi folks,
Thinking of distributed SCM, why choosing GIT over Mercurial or over
Bazaar
?
For one of the biggest reasons is that there is an extremely good
implementation in Java. The other proof point is that this is
successfully being
he right project directory?
LieGrue,
strub
--- Brian Fox schrieb am Fr, 24.4.2009:
> Von: Brian Fox
> Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> An: dev@maven.apache.org
> Datum: Freitag, 24. April 2009, 1:21
>
>
> Mark Struberg wrote:
> > tec
We have already a long thread with lot of things so I won't repeat some
questions.
I'm +0 to move to GIT but -1 to go outside of the Apache infrastucture.
Emmanuel
On Thu, Apr 23, 2009 at 7:00 PM, Jason van Zyl wrote:
> Hi,
>
> Maven was the first project at Apache to use JIRA and though there
Hi folks,
Thinking of distributed SCM, why choosing GIT over Mercurial or over Bazaar
?
They use GIT: http://git-scm.com/ (linux kernel)
They use Mercurial:
http://www.selenic.com/mercurial/wiki/index.cgi/ProjectsUsingMercurial(openJDK)
They use Bazaar: http://bazaar-vcs.org/WhoUsesBzr (MySQL)
N
Here is a more complete summary of why I think GIT, and more
specifically JGIT is the best thing going for the SCM:
http://www.sonatype.com/people/2009/04/git-the-sweetest-scm-around/
On 23-Apr-09, at 10:00 AM, Jason van Zyl wrote:
Hi,
Maven was the first project at Apache to use JIRA and t
; 2009/4/24 Mark Struberg
>
> >
> > answers inside
> >
> > --- Daniel Kulp schrieb am Fr, 24.4.2009:
> >
> > > Von: Daniel Kulp
> > > Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> > > An: dev@maven.apache.org
> > >
Struberg
>
> answers inside
>
> --- Daniel Kulp schrieb am Fr, 24.4.2009:
>
> > Von: Daniel Kulp
> > Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> > An: dev@maven.apache.org
> > CC: "Mark Struberg"
> > Datum: Freitag, 24. April 2009
answers inside
--- Daniel Kulp schrieb am Fr, 24.4.2009:
> Von: Daniel Kulp
> Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> An: dev@maven.apache.org
> CC: "Mark Struberg"
> Datum: Freitag, 24. April 2009, 2:51
> On Thu April 23 2009 5:46
2009/4/24 Brian Fox
>
>
> Mark Struberg wrote:
>
>> technically there is no git repo which is 'better' than the other. This
>> hierarchy is an orga one.
>> If you can pull from my repo and from Jasons, from whom will you pull your
>> master mainly? Bet you will pull from Jasons. And I also bet al
On 23-Apr-09, at 7:50 PM, Wendy Smoak wrote:
On Thu, Apr 23, 2009 at 10:00 AM, Jason van Zyl
wrote:
Maven was the first project at Apache to use JIRA and though there
was a
great deal of concern/noise about using JIRA it ultimately proved
to be a
decent system and now lots of projects
On 23-Apr-09, at 6:17 PM, Brett Porter wrote:
There are points on either side of this for me. In summary, I'm in
favour of greater exploration of using GIT, but not a wholesale
switch today.
On 24/04/2009, at 3:00 AM, Jason van Zyl wrote:
I'd be happy if everyone here wanted
On Thu, Apr 23, 2009 at 10:00 AM, Jason van Zyl wrote:
> Maven was the first project at Apache to use JIRA and though there was a
> great deal of concern/noise about using JIRA it ultimately proved to be a
> decent system and now lots of projects are using JIRA.
>
> I'm not particularly intereste
On 23-Apr-09, at 5:33 PM, Daniel Kulp wrote:
Personally, I'm +0 on the idea moving to git.I really don't care
one way
or the other if its svn or git.
However, I'm -1 to anything that involves pulling the code outside
of the ASF
unless it would get the "blessing" from infrastructure a
There are points on either side of this for me. In summary, I'm in
favour of greater exploration of using GIT, but not a wholesale switch
today.
On 24/04/2009, at 3:00 AM, Jason van Zyl wrote:
I'd be happy if everyone here wanted to use GIT but I do believe
that I have a bet
2) On a more serious note: this is EXACTLY the issue. Jason is no more
special than I am or anyone else on the Maven PMC. That is why there is a
centralized storage for the repo. Anyone on the PMC (actually, any
committer) MUST have access to entire repo for the project and be able to do
rrell Donkin schrieb am Do,
23.4.2009:
> > Von: Robert Burrell Donkin
> > Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> > An: "Maven Developers List"
> > Datum: Donnerstag, 23. April 2009, 23:27
> > On Thu, Apr 23, 2009 at 6:33 PM, Mark
> &
Personally, I'm +0 on the idea moving to git.I really don't care one way
or the other if its svn or git.
However, I'm -1 to anything that involves pulling the code outside of the ASF
unless it would get the "blessing" from infrastructure and/or the board. If
you want to invest some time/
I have two concerns:
1. Is GIT firewall friendly? At work I could never get to the CVS
repository because my employer's firewall pretty much only allows http
traffic. GIT would need to support that.
2. Is this OK with infra? Last I checked all Apache software had to be
under subversion.
No
o merge radical
contributions into the Maven documentation set.
On Thu, Apr 23, 2009 at 4:48 PM, Vincent Siveton
wrote:
Hi,
GIT is already proposed by infrastructure in read only mode
http://git.apache.org/
Using GIT in write mode sounds like a normal step.
Does Maven SCM support *fully* GIT? I thin
http://git.apache.org/
> Using GIT in write mode sounds like a normal step.
>
> Does Maven SCM support *fully* GIT? I think specially for some plugins
> like the release plugin
>
> Cheers,
>
> Vincent
>
>
> 2009/4/23 Jason van Zyl :
> > Hi,
> >
> >
Mark Struberg wrote:
technically there is no git repo which is 'better' than the other.
This hierarchy is an orga one.
If you can pull from my repo and from Jasons, from whom will you pull your
master mainly? Bet you will pull from Jasons. And I also bet all contributors
will try to get th
Hi Vincent!
> http://git.apache.org/
> Using GIT in write mode sounds like a normal step.
These are only git mirrors of our SVN and not intended to push to them but to
use dcommit.
So this is cool for quickly download/going offline with the whole project
history but not enough fo
Hi,
GIT is already proposed by infrastructure in read only mode
http://git.apache.org/
Using GIT in write mode sounds like a normal step.
Does Maven SCM support *fully* GIT? I think specially for some plugins
like the release plugin
Cheers,
Vincent
2009/4/23 Jason van Zyl :
> Hi,
>
&
nges being pulled by Jason and published in his repo
at the end of the day.
LieGrue,
strub
--- Robert Burrell Donkin schrieb am Do,
23.4.2009:
> Von: Robert Burrell Donkin
> Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> An: "Maven Developers List"
> Datum
tics:
> Basically the location of the repo is just wurscht! It doesn't make any
> difference, since any repo is simply a clone of each other.
how is the code provenance control going to work using GIT?
- robert
-
To u
+0I never used GIT but I'm hearing a lot of good things about it and it is
already used by many opensources projects.
I would prefer to not have another drama with infra team if possible.
Perhaps we could help them to set it up if necessary ?
If you have tools for GIT on MacOS, do not hesitate to s
On the release plugin I believe John Smart has that working. And
having our release toolchain tested before switching is a completely
reasonable criterion.
That's my primary concern, that the tools support it, or we experiment
first to find out _how_ they work. It seems like from the maven
Git a little bit for utility projects and to
check out other open source projects from time to time, and I love
the way it works. I'd love to give it a try; I think it'll help Git
users that also use Maven if Maven starts using Git and works out
any kinks along the way.
I will say tha
other open source projects from time to time, and I love the
way it works. I'd love to give it a try; I think it'll help Git users
that also use Maven if Maven starts using Git and works out any kinks
along the way.
I will say that the maven-scm Git support - and the way it works wi
ecide whether it's a good idea and go from there.
I think it would be great for the community in making it easier to
share.
The git-svn thing just sucks and is just hindrance to using GIT
properly.
On 23-Apr-09, at 10:33 AM, Paul Gier wrote:
I'm fine with moving to Git. When you sa
gt; Betreff: Using GIT as the canonical repository for Maven 3.x
> An: "Maven Developers List"
> Datum: Donnerstag, 23. April 2009, 19:00
> Hi,
>
> Maven was the first project at Apache to use JIRA and
> though there was a great deal of concern/noise about using
> JIRA
I'm fine with moving to Git. When you say it will start with Maven 3.x, what
does that include? Will all the trunks switch over or just components/trunk to
start with?
Jason van Zyl wrote:
Hi,
Maven was the first project at Apache to use JIRA and though there was a
great deal of concern/no
Excellent. I do not have a long history with Git but from the projects I
used I'm always annoyed when I have to the projects I develop using SVN. So,
if my vote counts anyway I'm +1. We started using it for OI4J and everyone
getting accustom is loving it. Soon, I hope, all OPS4J projects will be on
Hi,
Maven was the first project at Apache to use JIRA and though there was
a great deal of concern/noise about using JIRA it ultimately proved to
be a decent system and now lots of projects are using JIRA.
I'm not particularly interested in mandating everything in Maven to
use GIT but I w
On Wed, Nov 12, 2008 at 12:39 PM, Imran M Yousuf <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a project (http://repo.or.cz/w/smart-dao.git) where I have 2
> working branches (master and release-0.3). Now I want to make a
> maintenance release (release-0.3) so I am doing it from the
> appropriate bra
Hi,
I have a project (http://repo.or.cz/w/smart-dao.git) where I have 2
working branches (master and release-0.3). Now I want to make a
maintenance release (release-0.3) so I am doing it from the
appropriate branch. Now when I do 'mvn release:prepare' it succeeds.
But when I do 'mvn release:perfor
You should google for egit...it's only in 0.3, IIRC, but seems to
work relatively well for the basics of commit, update, add, remove, etc.
-john
On Nov 13, 2007, at 9:15 AM, Paul Gier wrote:
Jason van Zyl wrote:
On 12 Nov 07, at 4:21 PM 12 Nov 07, Mark Struberg wrote:
--- Johan Kindgren <[
On 13 Nov 07, at 9:15 AM 13 Nov 07, Paul Gier wrote:
Jason van Zyl wrote:
On 12 Nov 07, at 4:21 PM 12 Nov 07, Mark Struberg wrote:
--- Johan Kindgren <[EMAIL PROTECTED]> schrieb:
Maybe it's better to make things easier for the
committers? I've been following this list for a couple of months,
Jason van Zyl wrote:
On 12 Nov 07, at 4:21 PM 12 Nov 07, Mark Struberg wrote:
--- Johan Kindgren <[EMAIL PROTECTED]> schrieb:
Maybe it's better to make things easier for the
committers? I've been following this list for a couple of months, and
it seems to be a reoccuring issue that patches ar
On 12 Nov 07, at 4:21 PM 12 Nov 07, Mark Struberg wrote:
--- Johan Kindgren <[EMAIL PROTECTED]> schrieb:
Maybe it's better to make things easier for the
committers? I've been following this list for a couple of months, and
it seems to be a reoccuring issue that patches are available but it
tak
--- Johan Kindgren <[EMAIL PROTECTED]> schrieb:
> Maybe it's better to make things easier for the
> committers? I've been following this list for a couple of months, and
> it seems to be a reoccuring issue that patches are available but it
> takes a (more or less) long time before they are applied.
Just a thought on your comment on making things easy for the
contributors: Maybe it's better to make things easier for the
committers? I've been following this list for a couple of months, and
it seems to be a reoccuring issue that patches are available but it
takes a (more or less) long time befor
On 12 Nov 07, at 9:17 AM 12 Nov 07, Jochen Wiedmann wrote:
On Nov 12, 2007 2:57 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Authors retain copyright and it's GPL'd. I don't think Linus much
cares beyond that, but I imagine Redhat does.
After all the SCO hazzle, rest assure he does. See, fo
On Nov 12, 2007 2:57 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Authors retain copyright and it's GPL'd. I don't think Linus much
> cares beyond that, but I imagine Redhat does.
After all the SCO hazzle, rest assure he does. See, for example
http://searchenterpriselinux.techtarget.com/q
On 12 Nov 07, at 7:50 AM 12 Nov 07, Jochen Wiedmann wrote:
On Nov 12, 2007 1:40 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
I might be misunderstanding, but this sounds like the answer to my
other question about getting contributors changes into trunk - what I
was asking here is how after som
On 12 Nov 07, at 3:38 AM 12 Nov 07, Mark Struberg wrote:
--- Brett Porter <[EMAIL PROTECTED]> schrieb:
Next, how can other committers get visibility into what the
contributors contributed? Much like a patch, it all gets committed
under one ID, but in that case we have the original contribution
> > All the information from the contributor should now be available in
> > the main repo as well.
> - what I
> was asking here is how after someone has merged the changes, we can
> keep track of where they came from (relying on an external repo url
> is not realistic for this, in case it
On Nov 12, 2007 1:40 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> I might be misunderstanding, but this sounds like the answer to my
> other question about getting contributors changes into trunk - what I
> was asking here is how after someone has merged the changes, we can
> keep track of where
On 12/11/2007, at 3:38 AM, Mark Struberg wrote:
--- Brett Porter <[EMAIL PROTECTED]> schrieb:
Next, how can other committers get visibility into what the
contributors contributed? Much like a patch, it all gets committed
under one ID, but in that case we have the original contribution in
JIRA.
--- Brett Porter <[EMAIL PROTECTED]> schrieb:
> > Next, how can other committers get visibility into what the
> > contributors contributed? Much like a patch, it all gets committed
> > under one ID, but in that case we have the original contribution in
> > JIRA. Is there a way we'll be able t
Jason - any thoughts on the 3 questions below?
On 06/11/2007, at 6:24 PM, Brett Porter wrote:
Firstly - you mentioned in your original post [1] that you were
setting up a legal framework for the contributions. What was the
resolution to this in general?
Next, how can other committers get v
s into the SVN repos for legal muck.
txs in advance and br,
strub
--- Jason van Zyl <[EMAIL PROTECTED]> schrieb:
Just finished a first round trip using GIT, the published Maven
repositories, and pushing back to SVN. Other then something I hosed
up
with the .svn entries it was a pai
be called automatically after each push and create all
the info needed for
cloning the repo over http via
git-clone http://git.sonatype.org/maven-2.1.git
txs in advance and br,
strub
--- Jason van Zyl <[EMAIL PROTECTED]> schrieb:
> Just finished a first round trip using GIT, the published Mav
I just built it from source using ports.
It builds in 25 seconds.
On 6 Nov 07, at 2:48 PM 6 Nov 07, Jason Dillon wrote:
Are there Mac OS X .dmg images for GIT somewhere?
--jason
On Nov 6, 2007, at 12:50 AM, Jason van Zyl wrote:
Hi,
Just finished a first round trip using GIT, the
On 06/11/2007, at 9:50 PM, Jason van Zyl wrote:
Anyone who wants to try and contribute more I highly recommend
using GIT. It's actually nice to use and I would say it was a success.
This is interesting - it's something I've wanted to try for a while
and it's a good id
Are there Mac OS X .dmg images for GIT somewhere?
--jason
On Nov 6, 2007, at 12:50 AM, Jason van Zyl wrote:
Hi,
Just finished a first round trip using GIT, the published Maven
repositories, and pushing back to SVN. Other then something I hosed
up with the .svn entries it was a painless
Hi,
Just finished a first round trip using GIT, the published Maven
repositories, and pushing back to SVN. Other then something I hosed up
with the .svn entries it was a painless experience. Had to wire up a
couple scripts but not a big deal. I did the SVN clone locally and
rsync'd
99 matches
Mail list logo
