On 05/03/2008, at 5:18 AM, Olivier Lamy wrote:

2008/3/4, Brett Porter <[EMAIL PROTECTED]>:

On 04/03/2008, at 10:47 AM, Olivier Lamy wrote:

Agree on this.
Currently there is a blocking issue with xml-rpc CONTINUUM-1590 which
prevent using xml-rpc :-(.

Cool - shall we just start using the 1.2 bucket in JIRA? There are
only 14 issues there now so maybe we could keep that to 20-30 issues
all together and release it.


ok, I'll get my stuff in there

I found these changes on trunk that are not on the branch: r617400.
(The rest is documentation)

I found these changes on the branch that are not on trunk: r627196,
r620613, r620612, r620611

I think we should just merge all those from the branch to trunk, set
it as v1.2, and close the branch for now?

+1. (Perso, I don't really like the idea of starting a parrallel
branch/trunk "a la" mvn 2.1 :-) )

I'll merge the changes to trunk - but will wait to hear other's opinions on this too before changing the branch

If no objections, I will change root pom to not have anymore maven pom
as parent.

Sounds good - do you think we should have a Continuum parent POM like
we do for Archiva?

https://svn.apache.org/repos/asf/continuum/parent/trunk ?
A new pom without parent ? (I can certainly copy some contents from
the maven parent pom)

With an ASF parent instead of the Maven one, yep.

Question : do we have to change the groupId in the poms :
org.apache.maven.continuum -> org.apache.continuum ( java package too
? looks a big bang)

I don't see any downside to doing this :)

- Brett

Brett Porter

Reply via email to