robert burrell donkin wrote:
i'm still a little unsure about the plan. AIUI we have a mavenised build on the MAVEN branch which has the changes made to trunk ported into it. so it's currently the same as trunk but uses maven. is this right?
Exactly.
what's stopping copying MAVEN into trunk ATM?
I see no problem in using the MAVEN branch for some days, until it is ready for Gump. I remember that we broke the Gump builds of about hundred projects, because one important project (don't remember exactly which, maybe dom4j or something similar) depends on us and a real lot of projects depended on that. We should really try to avoid the situation.
To me, the important part is that we are able to work on a common branch, because that minimizes the work, which is spent for merging. As Nacho has reached so far, we are able to do that now.
is the plan to alter the gump meta-data so that it uses the MAVEN branch first and then change it to use trunk later?
I'd suggest to create a new meta data descriptor in Gump, which uses the MAVEN branch. No other projects depend on it, so one can work on it without ruffle. As soon as the new meta data descriptor builds successfully, we can replace the old meta data descriptor with the new one and make the MAVEN branch the trunk.
i should have said: it'll be a few days once i have the mavenised build running reliably on my machine :-/
No problems here. As for the "running reliably": My impression is, that Nacho uses another Maven version than we do (1.0.2). I've had a hard time yesterday to get it all working, but it seems to be working fine now for me.
Jochen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
