[jbosstools-dev] Re: State of SVN and build

[Max Rydahl Andersen]

>> as/trunk/
>>    branches/
>>
>> hibernate/trunk
>>           branches
>>
> Ugh no yuck ;) I agree with you. You need to be able to check out all
> from trunk.  But what I'm saying is what's in TRUNK might all be
> targeting different things. I as a component lead would like to be able
> to move forward my future dev in the "trunk/as" section, and just inform
> marshall that jboss tools, which is merely an aggragator, should use
> "branches/components/as/jbosstools2.1_maintenance" for the current builds.
>
> But of course this also means that if someone does check out trunk,
> there is no guarantee it will all compile together as each of the trunk
> portions of the component could be targeting different drivers. So to
> get a successful build, they'd have to check out all from trunk and then
> replace the ones that have moved forward with their branches that
> stopped at current dev.
>
> Obviously this is just as complicated and what you're trying to avoid.

yes.

> I can be swayed to keep my HEAD at current jbds driver levels and do my
> future dev in a branch, SO LONG AS the branches folder is neat and
> organized and I have my own component folder there
> (branches/components/as/futureDevGanymede) for example.  This way I
> don't have to worry about coliding with other obscure names that may
> follow no apparent convention =P

yes. That is what i'm saying.

/max