[ 
http://issues.apache.org/jira/browse/OPENJPA-29?page=comments#action_12430349 ] 
            
Bryan Noll commented on OPENJPA-29:
-----------------------------------

Comments originally on the dev list:

from myself:

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? 


>From David Blevins in response (was inline):

I very well could have them backwards.  As I said, "There's a naming convention 
for this kind of thing, hope I've got it right." 

The classes from the third party jars would also have been extracted into the 
jar. 

That'd be possible.  You'd have to have one maven module for each jar and poke 
at the assembly plugin setup to not use the default name of 
<artifactId>-<version>-<assemblyName>.<archiveType>.  The maven guys may know a 
better way. 



> Create aggregate jars of OpenJPA
> --------------------------------
>
>                 Key: OPENJPA-29
>                 URL: http://issues.apache.org/jira/browse/OPENJPA-29
>             Project: OpenJPA
>          Issue Type: Task
>            Reporter: David Blevins
>
> Right now, we have a ton of jars, most of which are needed to actually run 
> OpenJPA. For real users, we should create aggregates of these jars, for 
> example:
> - *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 |

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to