I suppose downloading the src .zip file directly from Github would actually be easier than going out to Sonatype [?], since that's where the actual src code is hosted. Seems more intuitive to me. For example: https://github.com/Jasig/cas/tags
For javadocs, could we take advantage of maven-github plugins to generate the project site under the new "gh-pages" branch? Here's a sample of what the plugin could create: http://unicon.github.com/cas-addons/index.html Essentially, it's the generated maven site on github. -Misagh > -----Original Message----- > From: jleleu [mailto:[email protected]] > Sent: Friday, August 24, 2012 8:50 AM > To: [email protected] > Subject: [cas-dev] Source & javadoc > > Hi team, > > The snapshot artefacts we deployed on Sonatype repository (from continuous > build) have no source (nor javadoc) attached. It can be painful if someone > needs to debug source code. > > Shouldn't we add maven-source-plugin and maven-javadoc-plugin to our > parent > pom.xml ? Maybe only for a specific profile to avoid everybody using them > for > each build ? > > How do we do when releasing ? > > Thanks, > Jérôme > > -- > You are currently subscribed to [email protected] as: > [email protected] To unsubscribe, change settings or access archives, > see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
