Hi, You're right the aggregate jar doesn't handle javadoc and source properly. The individual modules do have sources and javadoc, though. The source is available in apache-openjpa-1-2-1-source.zip, which isn't pulled down during a normal maven build.
IIRC we didn't go with the maven assembly plugin because we need to aggregate some services files. I suppose post processing the results of the assembly would also work, but I'd have to look into it a hit. Modifying the build for openjpa-all so that javadoc is pulled correctly should also work. If you don't mind opening a JIRA for the issue that would be a good first step. Thanks, -mike On Thu, Apr 2, 2009 at 1:58 AM, <[email protected]> wrote: > > Hi! > > Just want to mention that the openjpa-1.2.1-sources.jar does only contain > the META-INF but no actual sources. > > I've looked at the openjpa-all, and it should't be a big problem to do the > uberjar thingy for the sources also. > > Maybe we can migrate the uberjar mechanism to use the > maven-assembly-plugin. This would actually be more maven-like ;) > > Please let me know if I can help out with that. > > LieGrue, > strub > > > >
