> -----Original Message----- > From: Martin Skopp [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 17, 2003 10:49 AM > To: Maven Developers List > Subject: RE: deploying java sources and javadocs to repository > > On Tue, 2003-06-17 at 10:20, Michal Maczka wrote: > > I am thinking about deploying java sources and javadocs to repository. > > > > Any idea about naming convention of those artifacts? With maven-new it > > will be easy to control, with maven-old it is not so easy. > > > > I am thinking about: > > > > /${groupId}/apis/${artitifactId}_api-${version}.jar (for javadocs) > > /${groupId}/srcs/${artitifactId}_src-${version}.jar (for sources). > > > > Any better ideas? > > > > Other question is where is the best place for such functionality? > > I think for javadoc it is javadoc plugin. But for sources? > > Isn't the "dist" plugin doing the job already? >
I think it does different thing. I just want to distribute subset of sources - java sources. I am looking towards such scenario (not quite possible at the moment): When I do: maven eclipse:generate-classpath The eclipse plugin will download also src and javadocs associated with every "jar" dependency (if they are available). So in you IDE you will have at your fingerprints: javadoc documentation of libraries you use and if you want also the source code of those libraries for debugging. The same I guess can be done for other IDEs [...] > ... dist plugin IMHO builds "zip" archives, which are more suitable than > jar e.g. for javadoc. > Somebody knows how compression level of zip compares to jar. I thought that they are quite similar... Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
