I while back you had requested that we (the Jython folks) try to
extract out the caching mechanism that Jython uses. I've done a rough
extraction (basically I replaced all of the PyList and other
pythonisms with Java List and other Java-isms and removed any links
into Jython's core. I've dummied out the class representing a
JavaPackage. This is very rough and is in no way threadsafe or for
that matter safe for any purpose :) -- but it does create the cache
files for jars the way Jython does. To try it out check it out from
here:
https://jython.svn.sourceforge.net/svnroot/jython/trunk/sandbox/wierzbicki/packagecache
It has a simple ant file that builds the java classes. It also has
two test directories, one for jython and one for jruby (src/jython and
src/jruby) with a test.py and test.rb. Both test directories contain
an empty "jars" directory. If you put some jars in the "jars"
directory and run the tests a "cachedir" gets generated and cache
files are produced from the jars. I haven't gotten around to testing
the mechanism for actually using the cache -- so that part could be
completely broken, but the cache files produced from the jars are
exactly the same (at least for the handful of jars that I studied) as
those produced by Jython.
-Frank
Frank! Excellent!
This is in a sense the first contribution in code to our common goals.
Perhaps this would be a good time to set up a respository in which to
store such things?
I will have a look at the cache, we would certainly find uses for it.
- Charlie
> Frank! Excellent!
>
> This is in a sense the first contribution in code to our common goals.
> Perhaps this would be a good time to set up a respository in which to
> store such things?
Yes I think it would be great to start such a repository. Even though
I live there and appreciate everything they have done for Jython, I
vote against sourceforge for such a repo :). Are you happy at
codehaus?
> I will have a look at the cache, we would certainly find uses for it.
Great!
-Frank
I think Codehaus would be less than ideal, since they have some
licensing restrictions. I'm open to suggestions.
java.net seems like a natural place, though we wouldn't want to use the
built-in bug tracker. But bug tracking wouldn't be the first thing we
need set up, and java.net at least has SVN working well.
Other suggestions?
- Charlie
>
> Other suggestions?
There is code.google.com -- but I have no experience with them (I have
heard positive things though). They also use svn.
-Frank
I use Google http://code.google.com/hosting/ . It's trivial to set the
project up and uptime has been 100% so far. They have a Wiki and a bug
tracker but I have not used either yet.
Hanni recently biled the service so they must be dioing something right:)
John Wilson
What's wrong with Codehaus?
And which licensing restrictions?
--
Guillaume Laforge
Groovy Project Manager
http://glaforge.free.fr/blog/groovy
Codehaus does not allow projects solely licensed under the GPL. No
decisions have been made on what the results of our efforts would use
for a license, but I'd like options to remain open.
And no, I don't want to get into a debate about the GPL :)
- Charlie
I don't think the Haus would accept this project at the moment:
"The Codehaus places a high bar on entry for projects. They should be
released or near it."
(from the Manifesto)
I think we really just need a sandbox site at the moment.
John Wilson
Ah well, but if I had a choice, I would really prefer using a really
open license like ASL 2, and not this viral GPL thingy ;-)
There are always exceptions to the rules.
> I think we really just need a sandbox site at the moment.
Then Google Code should be okay, despite the lack of good high-level
services (JIRA, FishEye, Confluence, etc...)
Looks like we are between java.net and code.google. Since you
originated all of this, you should probably have naming rights -- and
I have no preference between these two services. Do you want to
choose?
-Frank
I'm willing to give Google Code a try, and it seems to be (in most
circles) the least offensive of all services. And if we need to make a
move off it to java.net or codehaus or whatever in the future, I doubt
it would be a big deal.
I'll raise the licensing question (blech) in another thread.
- Charlie
Attila.
On Tue, 17 Jul 2007 23:01:46 +0200, Charles Oliver Nutter
-Frank