From: "Sylvain Wallez" <[EMAIL PROTECTED]>
> >>One of their objectives seems to keep the library as small as possible.
> >>To achieve this, they could package the XML stuff in a separate jar
> >>(poi-xml.jar) so that people can use only poi.jar if they don't care
> >>about XML.
> >
> >Seems a valuable way to go for them.
> >
> >Any comments from the POI side?
> >
> Not up to now. And this makes me wonder even more about the support of
> these 100+ classes... I'm gonna bring this discussion to poi-dev. Gosh,
> one more mailing list :(
In a previous mail, I think I've defined possible concrete outcomes as
clearly as possible.
There has been no response to those points, only a suggestion of what
another project community should do for his good.
In case you didn't recieve the mail, I reminded that the POI community has
already decided not to have xml stuff in the repository; this requirement
was part of the proposal to jakarta, for being accepted in Apache.
Since there have been two votes done by these communities, all on donating
the code to Cocoon, the code has been put in the Cocoon repository, but by
no means this is written in stone. Communities can change their mind, as it
seems it's happening now, and this is a good thing as long as it doesn't
create unnecessary friction.
Now that the whole issue has come to a stall, we, the POI development team,
are deciding on how to deal with this without creating further problems for
our communities.
We will make our position clear in a mail that will be posted ASAP.
We are confident that the solution we are working on will please all.
Thank you for the patience.
Nicola Ken
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
