I was thinking I would use inheritence to set other options. The plugins I was working on make all the various options for stuff like FindBugs clickable - so theres a bunch there you could configure and inherit.
I can do the work around for now, I wouldn't rush into an inheritence design. It definently sounds like something that needs a lot of thought and your solution of copying the projects would be fine for me for a while.
On 1/29/07, Kohsuke Kawaguchi <Kohsuke.Kawaguchi@xxxxxxx> wrote:
Kohsuke Kawaguchi wrote:
> Inheritance seems to be a fairly popular notion among other tools but
> giving it a decent GUI is rather hard. Somehow you have to differentiate
> overridden values and default values (and it has to survive during the
> form submission round-trip), and you have to let people revert the setting.
>
> For systems that don't provide GUI, it's pretty easy, but for us, well...
I guess another thing is that so far it sounds like you don't really
need the inheritance. For example, in issue #257 you say that your group
enforces the directory layout where you put artifacts in build/, so you
don't really need to let people override it.
I agree that it would be nice to do something in this area, but I'm
trying to avoid doing inheritance, I guess...
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi@xxxxxxx
--
- Eric
| 