well when I worked on this I added in some core.actions to do some of
this kinda logic
* 1) project groups have default build definitions
* 2) if project has default build definition, that overrides
project group definition
* 3) changing parent default build definition does not effect
Hey all,
I mentioned this on IRC and felt it should be sent ot the list.
The notion of default build def is really wierd, now that groups are
there.
In particular, can the "default build def" for a project be a group
def, or only a project def. The UI for this is also crapped out, as
Actually, To Emannuel's point about building with clean checkout or
update, I'm working on such a thing, and should have a patch this
weekend. It'll also include the per-group/per-project/per-build-def
working directories, per my conversation with Kenney, and the "do you
force a build on change,
On 17 Oct 06, at 6:15 PM 17 Oct 06, Jesse McConnell wrote:
well, I am working on finishing up some lingering project group
functionality now, but once I knock it off my list I'll work on the
testing some. I'll need to get up to speed on the latest integration
testing work you have been working
well, I am working on finishing up some lingering project group
functionality now, but once I knock it off my list I'll work on the
testing some. I'll need to get up to speed on the latest integration
testing work you have been working on jason, and emm mentioned on irc
a while back that he was g
On 17 Oct 06, at 2:34 PM 17 Oct 06, Brett Porter wrote:
I agree with Emmanuel. IIRC, the profiles are already in the model,
and basic choice of which JDK and maven/ant installation to use
should be straightforward and extremely useful. I agree that making
it more pervasive and using the to
