If all of wicketstuff was branched/tagged together, this would work and you could let the release plugin automagically change it for you. But, since they all have their own lifecycle (their own trunk/branches/tags), then you need to configure them individually.
On Tue, Nov 18, 2008 at 12:12 PM, Jeremy Thomerson <[EMAIL PROTECTED]> wrote: > Oh, gotcha! I'll try a test with one of my projects and see, but I think > you're right. > > If so, I am still willing to add the SCM info to each pom if necessary - but > I still want approval of the crowd since those aren't my projects to alter. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > On Tue, Nov 18, 2008 at 11:07 AM, James Carman > <[EMAIL PROTECTED]>wrote: > >> I'm talking about the SCM url itself. It needs to change in the child >> when a branch/tag is created (because it now lives in a different >> place). Of course it would be able to find its parent (as long as >> it's in the local repository). >> >> On Tue, Nov 18, 2008 at 12:04 PM, Jeremy Thomerson >> <[EMAIL PROTECTED]> wrote: >> > I don't think it would if you defined it like this in each child... >> right? >> > >> > <parent> * * <groupId>*org.apache.wicket*</groupId> >> > * * <artifactId>*wicket-parent*</artifactId> >> > * * <version>*1.4-SNAPSHOT*</version> >> > * * </parent> >> > >> > Because it doesn't have a relative path, Maven just looks up the parent >> pom >> > like it looks up any other dependency. If you had a relative path, like >> > wicket does to its parent pom, then it would mess up. >> > >> > -- >> > Jeremy Thomerson >> > http://www.wickettraining.com >> > >> > >> > On Tue, Nov 18, 2008 at 10:59 AM, James Carman >> > <[EMAIL PROTECTED]>wrote: >> > >> >> The problem is that the entire tree isn't copied over together, so the >> >> SCM links get messed up when you do that. >> >> >> >> On Tue, Nov 18, 2008 at 11:57 AM, Jeremy Thomerson >> >> <[EMAIL PROTECTED]> wrote: >> >> > Tough to be sure - we could experiment. >> >> > >> >> > On Tue, Nov 18, 2008 at 10:50 AM, James Carman >> >> > <[EMAIL PROTECTED]>wrote: >> >> > >> >> >> When you create a tag/branch of the child, the SCM setup wouldn't >> >> >> inherit correctly, though. Right? >> >> >> >> >> >> On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst >> >> >> <[EMAIL PROTECTED]> wrote: >> >> >> > Could you structure the parent pom such that it sets up all child >> poms >> >> >> > correctly? Then it is just a matter of inheriting from the parent >> pom >> >> >> > for all projects. >> >> >> > >> >> >> > Martijn >> >> >> > >> >> >> > On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson >> >> >> > <[EMAIL PROTECTED]> wrote: >> >> >> >> Devs, >> >> >> >> In response to the problems with TeamCity and Sourceforge, I >> >> installed >> >> >> a >> >> >> >> Continuum instance on my server last night. I added Wicket and >> >> several >> >> >> >> Wicket Stuff projects. It seems to be running fine, except that >> most >> >> >> >> projects are missing the SCM tag from their POM, or have it >> >> incorrectly >> >> >> >> configured. >> >> >> >> >> >> >> >> I don't mind going in and fixing or adding the SCM tag on all of >> the >> >> >> >> projects that are currently on TeamCity and setting them up on >> this >> >> >> >> Continuum server. But since those aren't my projects, I wanted to >> >> run >> >> >> it >> >> >> >> past the group first. What do you think? We could do this and >> let >> >> it >> >> >> run >> >> >> >> for a while as a test. >> >> >> >> >> >> >> >> http://www.wickettraining.com/continuum >> >> >> >> >> >> >> >> -- >> >> >> >> Jeremy Thomerson >> >> >> >> http://www.wickettraining.com >> >> >> >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Become a Wicket expert, learn from the best: >> >> http://wicketinaction.com >> >> >> > Apache Wicket 1.3.4 is released >> >> >> > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> >> >> > >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Jeremy Thomerson >> >> > http://www.wickettraining.com >> >> > >> >> >> > >> >
