This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [BC] Patch: Cached class map


On Thu, 2004-11-04 at 11:40, Andrew Haley wrote:
> Bryce McKinlay writes:
>  > Shouldn't we put jv_dbtool in a package - say, gnu.gcj.tools or gnu.gcj ?
> 
> Well, I was about to rename it anyway, so I'm interested in
> suggestions.  What would be better if I did this?

Hurray! Finally a technical discussion about the BC-branch where I can
give my opinion :)

For GNU Classpath Tools (javah, javap, gjdoc, serialver, etc.) we use
gnu.classpath.tools. So I would suggest that general tools go into a
subpackage of gnu.classpath.tools (and are maintained in the appropriate
GNU Classpath CVS submodule) and that gcj specific tools go into a
subpackage of gnu.gcj.tools and are maintained inside GCC cvs. Maybe you
want to have a new subdirectory libjcj-tools which is build after libgcj
proper is build?

Currently the rmic tools are not following the above convention. I would
like to move them from gnu.java.rmi.rmic to gnu.classpath.tools.rmi and
maintain them in the GNU Classpath Tools (cp-tools) CVS submodule in the
future. What do you think?

Cheers,

Mark

> (As an aside: shouldn't it be org.gnu.*  ?)
http://www.gnu.org/software/java/packages.html#why-just-gnu

As an aside: Who currently maintains the
http://www.gnu.org/software/java/ pages?

Attachment: signature.asc
Description: This is a digitally signed message part


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]