So... I saw that David created the following two JIRA's, so I wanted to
follow up on the thread.
http://issues.apache.org/jira/browse/OPENJPA-29
http://issues.apache.org/jira/browse/OPENJPA-30
Regarding OPENJPA-29:
openjpa-0.9.0-full.jar // contains all openjpa code, openjpa-*.jars
merged
openjpa-0.9.0-nodep.jar // contains all openjpa code and all third
party dependency jars
Do you have your descriptions backwards or am I misunderstanding what
you're saying? Seems like 'nodep' would mean "no dependencies for this
project are bundled into this jar" to me.
IIUC (which I'm not sure that I do, so please correct me) then...
openjpa-0.9.0-nodep.jar would extract to:
- org/apache/openjpa/*/**.class
- META-INF/* ............ (we still need to resolve the 'merge multiple
files of the same name and locations (eg.. ProductDerivations) problem
for this)
openjpa-0.9.0-full.jar would extract to:
- org/apache/openjpa/*/**.class
- thirdPartyJars.jar (many of these)
- META-INF/* .......... (same issue as above)
Like I said, not sure this is actually correct. Would the openjpa-*.jar
files be there instead of the unpacked classes? Can someone with a bit
more classloading acuity speak to that? Should the names actually be
openjpa-nodep-0.9.0-SNAPSHOT.jar and openjpa-full-0.9.0-SNAPSHOT.jar?
-----
Regarding OPENJPA-30:
- I saw that Marc got the newly named SNAPSHOT jars up to a repo....
good stuff.
- The next step would have one jar somewhere like
http://people.apache.org/repo/m2-snapshot-repository/org/apache/openjpa/openjpa/0.9.0-SNAPSHOT/
for people to depend on, instead of many, correct?
- David... if you catch this... I would be glad to help (translation...
observe and learn) you get the thing publishing nightly from the apache
continuum server you spoke of.
Thanks...
Bryan
David Blevins wrote:
On Aug 15, 2006, at 7:42 AM, Craig L Russell wrote:
On Aug 15, 2006, at 6:38 AM, Patrick Linskey wrote:
Check out the Assembly plugin and it's predefined
"jar-with-dependencies" descriptor[1]. I'm pretty sure that
most people
using Maven will just have a runtime dependency on the core OpenJPA
library and be done with it, but it's always nice for Ant users.
Exactly -- mvn users will use the dependencies, but people who want to
download and use the distribution directly may not want a billion
little
jars.
Yes, my experience says it's ok to have 10 dependencies on e.g.
commons-logger, antlr, etc. but having 10 dependencies on
openjpa-kernel4, openjpa-kernel5, openjpa-api, openjpa-blah is annoying.
So if possible, I'd also like to have a jar with all the stuff in it.
That'd be nice. Some jar that contains all the openjpa-*.jar files is
perfect for my needs. The good news is that the maven-assembly-plugin
allows you to define several assembly xml files and build multiple
archives containing whatever you like. So if people want, we could have:
openjpa-0.9.0-full.jar // contains all openjpa code, openjpa-*.jars
merged
openjpa-0.9.0-nodep.jar // contains all openjpa code and all third
party dependency jars
There's a naming convention for this kind of thing, hope I've got it
right.
-David
Craig
-Patrick
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the
individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
