Peter Donald wrote:
>
> At 01:40 1/3/01 -0500, Geir Magnusson Jr. wrote:
> >One way to solve this since the Commons idea is a good one, and
> >different in deliverables than 'regular' jakarta projects, we could look
> >at changing whatever Avalon's charter really is to include the
> >productized component project there (Library).
> >
> >Of course, this would be a decision by the Avalon folk to change their
> >model of dealing with components. I only bring this up because I get the
> >sense that the Avalon folk are interested.
>
> I think there is interest in it. It is something I have wanted to do since
> Jon mentioned the CJAN idea - it has also been mentioned with regards to
> another Enterprise Application super-server built on top of Phoenix. So if
> the infrastructure was there people would definetly be willing to do it I
> suspect.
Just to be clear, what I am suggesting is Avalon being a home for
component projects that are managed by their own set of committers -
each is an independant project with their own deliverables,
documentation, examples, jars. I assume that the individuals that
comprise the Avalon committers would be a part of each out of their
interest this stuff, but it wouldn't be the default or required.
This doesn't mean I am advocating changing what[ever] Avalon is now -
but rather just bolting an 'addition' onto the side, so to speak.
I think that is a little different than CJAN.
Or I am too tired to think now. Have a good evening, everyone. :)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
