If it help to improve git support : go for it !
The most important IMHO is to be backward compatible and support the
current git url which are supported :
scm:git:git://github.com/olamy/scm-git-test-one-module.git
scm:git:g...@github.com:olamy/scm-git-test-one-module.git
--
Olivi
On 2009-10-02, at 11:05 AM, two...@bluestemsoftware.com wrote:
Got it. I'm on my own as far as documentation is concerned. To
clarify ... if I can no longer check out a specific revision of
components/trunk, as far as source code is concerned, my only
options are to use a tagged release
Got it. I'm on my own as far as documentation is concerned. To
clarify ... if I can no longer check out a specific revision of
components/trunk, as far as source code is concerned, my only options
are to use a tagged release or begin coding against maven-3/trunk.
I'd like to delay the latter
On 2009-10-02, at 8:43 AM, two...@bluestemsoftware.com wrote:
Thanks Jason. Because it has changed so much, would migrating my
code from 2.1-SNAPSHOT to the components/tags/maven-3.0-alpha-2
release be a good intermediate step, i.e. in anticipation of Maven
3.0?
No, you're on your own
Thanks Jason. Because it has changed so much, would migrating my code
from 2.1-SNAPSHOT to the components/tags/maven-3.0-alpha-2 release be a
good intermediate step, i.e. in anticipation of Maven 3.0?
Quoting Jason van Zyl :
On 2009-10-02, at 4:22 AM, two...@bluestemsoftware.com wrote:
> Hi
On 2009-10-02, at 6:35 AM, Paul Gier wrote:
Brian Fox wrote:
On Fri, Oct 2, 2009 at 5:57 AM, Paul Gier wrote:
Why would everyone need to use both repos? If the legacy
repository is done
correctly, the vast majority of users would never need to hit it,
or even
know about it at all.
Note
On 2009-10-02, at 4:22 AM, two...@bluestemsoftware.com wrote:
Hi,
I embedded maven into a product. The version used, at the time, was
2.1-SNAPSHOT, checked out and built from components/trunk on 7/9/2008.
I am about to resume development and was hoping to pick up where I
left off with a
Brian Fox wrote:
On Fri, Oct 2, 2009 at 5:57 AM, Paul Gier wrote:
Why would everyone need to use both repos? If the legacy repository is done
correctly, the vast majority of users would never need to hit it, or even
know about it at all.
Note that this idea is different than creating a new cl
On Fri, Oct 2, 2009 at 5:57 AM, Paul Gier wrote:
> Why would everyone need to use both repos? If the legacy repository is done
> correctly, the vast majority of users would never need to hit it, or even
> know about it at all.
>
> Note that this idea is different than creating a new clean reposit
Why would everyone need to use both repos? If the legacy repository is done
correctly, the vast majority of users would never need to hit it, or even know
about it at all.
Note that this idea is different than creating a new clean repository. This
would be a new repository just for the garba
Hi,
I embedded maven into a product. The version used, at the time, was
2.1-SNAPSHOT, checked out and built from components/trunk on 7/9/2008.
I am about to resume development and was hoping to pick up where I left off
with a released version which uses the embedder. I read through the posti
11 matches
Mail list logo
