On 04/03/2008, at 6:22 AM, Brian E. Fox wrote:
As I understand your proposal, the don't-append-marker would vanish
after
the first inheritance step, re-enabling the default behavior for all
descendant POMs?
You're right, it probably won't work that way. I was thinking the
behavior info would be available throughout the inheritance process,
but
removed after...but then you couldn't inherit from a deployed pom.
It's ugly, but there is a workaround for this now in respecifying the
URLs in the child POMs. It's a pain but it's not the end of the world
and I'd say better than adding even more voodoo.
I'd also like to take the time to apologise for adding this behaviour,
it seemed like a good idea at the time...
I'm not convinced adding a flag to the pom will help because we have
so
many different urls (site, scm, distro) and I don't think a global
switch for all of them is what people want.
In the attributes branch we have different model readers for different
versions and can presumably have different semantics as people update
through the versions. I would say that's the best way to go - keep
behaving the same way as now for 4.0.0 POMs, and come up with a better
solution for people that choose to use 4.1.0 POMs (once they are in
place).
My 2c.
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
