On Tue, 7 May 2002, Daniel Rall wrote:
Heya Dirk. The MM.MySQL driver was recently LGPL'd by the author,
Mark Matthews. If the documentation which comes with it still states
that it is GPL'd, that documentation is out of date -- contacting Mark
ought to resolve the issue (and yes I tried
On Thu, 14 Mar 2002, Peter Donald wrote:
They still include the jaxp source code, in xml-commons.
But it's a clean-room implementation, made directly from the spec.
The directly from the spec is where the problem lies. It uses suns IP and
thus must the TCK. We don't and thus we are in
The BCL states that you cannot make a distribution of the .jar file outside
of your product. In other words, if you want to distribute the single .jar
file, you can't do that.
(i) distribute the Software complete and unmodified and only bundled as
part of your Programs
What about a dummy
On 23 Feb 2002, Pete Chown wrote:
The other thing I would like to push is gcj. It doesn't seem to be very
well known. For people who haven't come across it, it is part of gcc
and it is an ahead-of-time compiler for Java. It also includes a
bytecode interpreter so it can deal with
Does anyone knows how to subscribe to a mailing list to 'write-only' mode
( and if it is possible ) ?
Some lists have web-based archives, and the trafic is quite big
( too big for a yahoo account anyway ). However posting is not possible
if you are not subscribed.
Thanks,
Costin
Thanks Sam,
If this mail will reach general@ without going to moderator, then the
trick worked :-)
If anyone else is interested: I sent a mail to:
[EMAIL PROTECTED]
Costin
On Wed, 10 Oct 2001, Sam Ruby wrote:
Costin Manolache wrote:
Does anyone knows how to subscribe to a mailing
On Mon, 1 Oct 2001, Sam Ruby wrote:
Updates:
1) xsltc and velocity appear to be compatible with the latest BCEL.
2) BCEL's build.xml has minor errors - I'll post details to BCEL's mailing
list.
3) BCEL includes and depends on gnu regexp. The dependency does not appear
to be deep.
It
On Fri, 11 May 2001, Sam Ruby wrote:
It would be nice if the tomcat3 and ant communities could look into getting
tomcat to be buildable again using a dist build of ant from cvs. And if
tomcat3 build works fine - Gump reports a failure that was fixed 2
weeks ago. ( the report is on a line
On Thu, 12 Apr 2001, Sam Ruby wrote:
Costin Manolache wrote:
One compromise may be to use a separate CVS only for binaries, with the
latest "released" version of each product.
This is not a solution for all versioning or cvs/binaries problems.
Xerces, Xalan, Ant are used and checked in
On Wed, 14 Mar 2001, GOMEZ Henri wrote:
Still no response for this sub-project proposal.
A big +1
This will also reduce the pressure on making changes in the "stable" code.
If a bug is found in the connector - we can just make a new release of the
connector ( both sides ), without a need to
On Fri, 9 Mar 2001, Nael Mohammad wrote:
I for one would like to see mod_webapp
Same for me - the automatic configuration is great for most users.
Having this "common" project would be great because it'll allow the
development of a connector that combines the best features of mod_jk and
Say I'd propose to move the org.apache.tools.tar and
org.apache.tools.mail packages from Ant to the commons repository -
which I'll probably do - these are very small thingies that don't
really need separate mailing lists at all.
+1 !!
And maybe parts of ProjectHelper ( turned into a
Remy Maucherat wrote:
I'm a bit disappointed by that list, which doesn't include Costin.
Before questioning the people that came up with this list, perhaps first
you should ask Costin if this is an opportunity he would be interested in.
And my answer would be no, I am not.
But I am
My hope is that the "library" project will be organized in a way that
allows multiple "books" in each collection.
I agree, it's important to allow different ideas to flower rather than impose
a "one true way" philosophy. But I also think it's important to keep strong
quality control on
My own hope is that each component be treated like a book, with it's own
publication date, edition count, and set of authors and editors.
And again - we'll act as librarians and make sure the book is available,
not as censors or authors of competing books.
For this branch, we probably need
The project should _host_ and maintain code that is shared by projects,
not _develop_ utils that may be needed ( like CPAN, or alexandria ).
How can that work in the current "project committer" model? I agree
that it should be open to accept projects from the 'outside', but I
think
If someone chooses to duplicate a piece of code, maybe the problem is with
the way the code is written and shared.
I think in some cases, its bacause people aren't aware that the stuff
exists. Go through the Jakarta project sites, and find the number of
places that offer a separate,
Hi Sam,
I (think ) I got gump to work, it's not updating/building. There are few
issues/sugestions. I tried to find the alexandria list ( I assume the
discussion on gump happens on alexandria ), I'm sure it is somewhere and
I'll keep searching :-)
Anyway - it would be possible to switch
Others can run builds with stable dependencies. They are permitted, and
even encouraged to do so using Gump. The runs I have been making are to
determine the impact of changes - something that I think that has not
received enough attention, and so that's why I have been and will continue
Ted Husted wrote:
may we please have a interim Jakarta "libary" mailing
list for the purpose of formaling the details of a
proposal for this subproject.
Are you sure that you want to call it that. ;-)
Beyond the typo...the name of the mailing list should match the name of the
I'll try again:
1. As someone said, "community is more important than code"
2. I think the real problem here is not "code sharing" - the fact that
people are reticent to reuse code developed in other projects is just an
effect
3. I think the real problem is that each project has it's own
And Tomcat 3.3 probably wouldn't have a ratified release plan or nearly as
many volunteers to support it.
+1.
Costin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
What about starting the "reuse" quest by reusing the jakarta-tools
repository ?
Wouldn't that break the "old" version of Watchdog ("jakarta-watchdog") that still
has dependencies here?
In what way ? By adding new directories and tools the old one shouldn't be
affected. Watchdog is using
23 matches
Mail list logo
