[jdom-interest] Re: TODO.TXT: jdom.jar main method and class

[Matthew MacKenzie]

I think it would be useful to have the Main-Class just parse the file
referenced in argv[0] and print it back out.  That way it would be
possible to validate a file really quick without writing any code.
Failing that, maybe there could be a release.xml file included in every
release containing build metadata, and the main class could just print the
contents of that file.

my $0.02 CAD


--
Matthew MacKenzie
VP Research & Development
XML Global Technologies, Inc.

-----Original Message-----
From: jdom-interest-admin at jdom.org
[mailto:jdom-interest-admin at jdom.org]On Behalf Of Joseph Bowbeer
Sent: February 22, 2001 8:42 PM
To: jdom-interest at jdom.org
Subject: [jdom-interest] Re: TODO.TXT: jdom.jar main method and class


I'm wondering about the idea of making jdom.jar executable.

I wouldn't expect anything in my /lib/ext to be executable, and I'm a
little
concerned about adding a Main class to the default package in every JDOM
user's classpath.

Applets have a description method, and beans have BeanInfo.  Is there not
some standard way for packages to describe themselves?  (Could we just add
some extra information to the manifest?)

The most standard thing I can find is package-level documentation.

http://java.sun.com/j2se/javadoc/writingapispecs/index.html#package

In this scheme, we'd add package.html to src/java/org/jdom and subdirs.

Failing that, would it be preferable to put Main in *some* package?  For
example: org.jdom.info

--
Joe Bowbeer



_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourh
ost.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2879 bytes
Desc: not available
Url : http://jdom.org/pipermail/jdom-interest/attachments/20010222/eda7a502/smime.bin