I propose we remove the "test" module.
+1. If you are going to don the build-monkey-suit, do you want to go
ahead and remove it?
The extension model is a bit hokey at the moment requiring users to
create new or modify existing profiles which basically means
duplicating the installation every time. We've had this view for a
while that extensions should be dynamically and automatically
loaded based on intent and for the 1.0 timeframe I think we should
provide that. However, this really requires the Contribution
service be fully working to we can match intent to extension and I
don't think that will be ready soon.
Raymond and Luciano, you guys started work on this. Is this something
you feel could be ready over the next couple of weeks?
We do support a very primitive extension mechanism where users can
add them by modifying the system scdl (which is now externalized as
a text file). I'm OK with releasing an alpha version like that with
the intent-based support coming later (i.e. 1.0 beta or final).
For an alpha, I think this is fine.
I think we need to do some clean-up on the poms. As Sebastien
pointed out, there is a lot of dependency cruft in the SCA pom
which should be stripped out - we can probably reduce that to just
the configuration of checkstyle etc. I'm happy to don my build-
monkey hat again and clean that up.
+1
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
