Hi Mark, Prins, drs. M.C. (Mark) wrote:
> ----Original Message---- > From: Ludovico Cavedon [mailto:[email protected]] On > Behalf Of Ludovico Cavedon > Sent: Monday, June 28, 2010 4:17 AM > To: [email protected] > Cc: [email protected] > Subject: [mojo-user] Copyright holders? > >> Hi, >> I am packaging javacc-maven-plugin for Debian. > > Why?? Maven will just download it when specified in a project's pom... It > is already packaged, as a maven plugin; packaging it in yet another way > seems very un-"maven like", counter-intuitive, waste-of-time-ish,.... Why > does debian need a different way of packaging?? This is not Debian only. A lot of Linux distributions follow here their own rules and the discussion has a religious tendency regarding Java artifacts in common. Therefore it's pointless to start the discussion here again. >> Before I can upload the package I need to know who are the copyright >> holders. >> >> I need an explicit list of names, which I could not find in >> the SVN nor >> on the website. >> >> I have a second question: do you distribute a tarball for the sources, >> or the only way to get the source code is by checking it out from the >> SVN repository? > > As you can see here: > http://repo2.maven.org/maven2/org/codehaus/mojo/javacc-maven-plugin/ the > sources are published as a jar file for each release. No, the sources jar simply contains the sources for the jar, but it's not a source distribution, since you cannot build the plugin from this. Therefore all Apache projects provide an additional src artifact that can be used to build the result again. For most Mojos (all?) you have to checkout the sources from the tag to rebuild the release. - Jörg --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
