OK, I'm finally getting back to this. I've run the tests in my local M2
repo and, using the (slightly modified, see below) recipe below, I've
managed to get it to work as expected.
To get this show on the road I will subscribe to repository@ and ask for
some guidance. Will post back here
Whats the state of play with this - I was just about to do the release
for Chain 1.1 - it has been modified to have
groupIdorg.apache.commons/groupId - is it OK to release with this
or should I revert to groupIdcommons-chain/groupId?
Niall
On 6/5/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Niall Pemberton wrote:
Whats the state of play with this - I was just about to do the release
for Chain 1.1 - it has been modified to have
groupIdorg.apache.commons/groupId - is it OK to release with this
or should I revert to groupIdcommons-chain/groupId?
Niall,
I haven't had time yet to
AFAIK maven1 repo is simply a rewriteRule on maven2 repo, so that new
artifacts under org.apache.commons groupId in maven2 repo will be
available in maven1 repo under org.apache.commons/jars/artifact.jar
This may suggest to use a more specific groupId for commons, like
Brett,
any comments on this?
cheers
--
Torsten
On 6/6/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Brett, I did the test that you suggested.
1. Installed commons-lang 1.0.1 into my local repo with
groupId=org.apache.commons
mvn install:install-file -DgroupId=org.apache.commons
AFAIK there is a way in maven repo to relocate dependencies, so that a
POM for any commons can be published at commons-xxx groupId, that
relocates to org.apache.commons groupId.
Servletapi for example is now under javax.servlet
You are right. This would involve copying all the old group sutff to
the new group and add the relocation poms.
On 6/7/06, Nicolas De Loof [EMAIL PROTECTED] wrote:
AFAIK there is a way in maven repo to relocate dependencies, so that a
POM for any commons can be published at commons-xxx
So, in the simple example below, covering commons-lang, the procedure
would be:
1. Copy all files from /commons-lang/ to
/org/apache/commons/commons-lang/ in the *Apache* repo
2. Change the groupId of all the pom files under
/org/apache/commons/commons-lang/ so that they use the
Are you thinking about doing it in the m1 or m2 repo?
see below
On 6/7/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
So, in the simple example below, covering commons-lang, the procedure
would be:
1. Copy all files from /commons-lang/ to
/org/apache/commons/commons-lang/ in the *Apache* repo
Carlos Sanchez wrote:
Are you thinking about doing it in the m1 or m2 repo?
I really don't have a clue. Since I have not acted as release manager
for any component, I haven't really done my homework on what the
difference between the two is. I know about the M1 an M2 repos at
ibiblio, and
Brett, I did the test that you suggested.
1. Installed commons-lang 1.0.1 into my local repo with
groupId=org.apache.commons
mvn install:install-file -DgroupId=org.apache.commons
-DartifactId=commons-lang -Dversion=1.0.1 -Dpackaging=jar
-Dfile=/path/to/commons-lang-1.0.1.jar
2. Created
an extensive test should be something along the lines of:
project A depends on commons-lang:commons-lang 2.1
project B depends on o.a.c:commons-lang 1.0
project C is a webapp that depends on A and B
webapp should have only one commons-lang.
You could do this with your own repository (and
Since I see these are all being changed now, I thought it would be a
good idea to check if anyone did the test I mentioned to make sure it
will work?
- Brett
Brett Porter wrote:
In Maven 2.1, it will be able to correlate between the two, but
currently they'll end up in there twice.
I'd
Hi Brett
Sorry, I misunderstood you regarding when to do the testing. So, no I
haven't done the test, yet. Can you elaborate a bit more on what needs
to be tested? Perhaps you know of an artifact that has been relocated
that we can have a look at, to see how they have done.
--
Dennis
Henri Yandell wrote:
On 5/18/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
On 5/13/06, robert burrell donkin
[EMAIL PROTECTED]
wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio
(httpclient
On Thu, 2006-05-18 at 11:02 +1000, Torsten Curdt wrote:
Opening this up again.
groupId: org.apache.commons
+1!!
ditto
- robet
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Henri Yandell wrote:
On 5/13/06, robert burrell donkin [EMAIL PROTECTED]
wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio
(httpclient
beeing an exception)
So could the next RC be uploaded to
On 5/18/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
On 5/13/06, robert burrell donkin [EMAIL PROTECTED]
wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio
(httpclient
beeing an exception)
On 5/18/06, Henri Yandell [EMAIL PROTECTED] wrote:
On 5/18/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
On 5/13/06, robert burrell donkin [EMAIL PROTECTED]
wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars
Sources and javadocs are great for maven users because when maven
generates the IDE projects it will check the repo for them, download
and link inside the IDE, enabling debugging through third party
sources or reading the javadocs while coding.
On 5/18/06, Phil Steitz [EMAIL PROTECTED] wrote:
It's also good for providing a standard way of doing things.
Our .zip files are terribly unstandard. We have source in /src/
/src/java /src/share and /src/main (at least), and javadoc in /api
/apidocs /api/docs and others.
I was under the understanding that regardless of maven usage, the src
On 5/13/06, robert burrell donkin [EMAIL PROTECTED] wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio (httpclient
beeing an exception)
So could the next RC be uploaded to
Opening this up again.
groupId: org.apache.commons
+1!!
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 5/17/06, Henri Yandell [EMAIL PROTECTED] wrote:
On 5/13/06, robert burrell donkin [EMAIL PROTECTED]
wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio
(httpclient
beeing an exception)
So could the next RC be
On Sun, 2006-05-14 at 12:32 -0700, Phil Steitz wrote:
On 5/14/06, robert burrell donkin [EMAIL PROTECTED] wrote:
On Sat, 2006-05-13 at 15:21 -0700, Henri Yandell wrote:#
snip
I feel that we should be using ACL's on
the maven repository on minotaur such that only a PMC can release
On 5/15/06, robert burrell donkin [EMAIL PROTECTED] wrote:
On Sun, 2006-05-14 at 12:32 -0700, Phil Steitz wrote:
On 5/14/06, robert burrell donkin [EMAIL PROTECTED] wrote:
be a good thing to move to henk's system of key management as well.
What is that system?
many months ago, henk penning
On Sat, 2006-05-13 at 15:21 -0700, Henri Yandell wrote:#
snip
I feel that we should be using ACL's on
the maven repository on minotaur such that only a PMC can release
their code onto the maven repository - but there hasn't seemed much
interest in trying to do such.
IMHO bit pointless ATM.
On 5/14/06, robert burrell donkin [EMAIL PROTECTED] wrote:
On Sat, 2006-05-13 at 15:21 -0700, Henri Yandell wrote:#
snip
I feel that we should be using ACL's on
the maven repository on minotaur such that only a PMC can release
their code onto the maven repository - but there hasn't seemed
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio (httpclient
beeing an exception)
So could the next RC be uploaded to
http://cvs.apache.org/maven-snapshot-repository/ ?
Please also consider using the new groupId
robert burrell donkin wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio (httpclient
beeing an exception)
So could the next RC be uploaded to
http://cvs.apache.org/maven-snapshot-repository/ ?
Please also consider
On 5/13/06, robert burrell donkin [EMAIL PROTECTED]
wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio (httpclient
beeing an exception)
So could the next RC be uploaded to
On 5/13/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
robert burrell donkin wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio (httpclient
beeing an exception)
So could the next RC be uploaded to
On Sat, 2006-05-13 at 11:30 -0700, Martin Cooper wrote:
On 5/13/06, robert burrell donkin [EMAIL PROTECTED]
wrote:
On Thu, 2006-04-06 at 08:51 +0200, Nicolas De Loof wrote:
I agree about NOT making non-final jars available on ibiblio (httpclient
beeing an exception)
So could the
In Maven 2.1, it will be able to correlate between the two, but
currently they'll end up in there twice.
I'd suggest when a release first does this, it's going to need to move
all the old versions to the new group ID, and add a relocation for the
original group IDs to get it to work, as
34 matches
Mail list logo
