On 17/05/2009, at 9:49 PM, Andrus Adamchik wrote:
We definitely need to remove it from "cayenne-jdk1.5-unpublished" to
avoid inclusion of this HTML in cayenne jars. "docs/doc/src/main/
resources" seems like a better place (and then we need to figure out
a way to sync it to the website).
Syncing it easy since I've already got a script which regenerates the
javadocs each night, plus it uploads the schema XSD file at the same
time. Just one more thing to do.
I'll move the docs soon as I get a chance tonight. What about the xsd
file? Do you prefer it where it is or should it move as well? I feel
it makes sense to be inside the package.
Using Oxygen is a smaller concern to me. We can just remove these
docs if for some reason we are unable to use Oxygen in the future.
One thing I'd check is what does the Oxygen license says about
redistributing generated docs and XSD. I wouldn't imagine there are
any strings attached, still worth a look.
I looked but couldn't find anything. Since the whole point of the tool
is to generate docs, I can't see a problem. Apache would qualify for a
very cheap (about $60 instead of $300) license, but there isn't a free
open source one. And there is no command line generator.
(I've actually just now noticed that we already had a DTD file I
never saw before in another location - anyhow it looks a bit old
and out of date, so this replacement of it is probably useful)
It's been maintained till recently, but since we have a schema now,
we should remove it.
I looked through it and it was a bit out of date in places. But it
seems that some maven magic is putting it into the built jars in the
manifest. Would you be able to do that for the XSD instead?
Ari
-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
