Once the headers are fixed, +1 - Joakim
Daniel Kulp wrote: > Jason, > > The files still don't have the proper Apache header on them. You added > the old style (with the copyright date) instead of the new style > documented at: > http://www.apache.org/legal/src-headers.html > Those need to change. > > Also, the pom.xml files need to have the header as well. Note: there is > a bug in maven/jdom that may discard the header at deploy time. Thus, > it may need to go INSIDE the <project> tag. > > The other files in "src" also need it (fml/faq.fml for example, possibly > the properties files as well). > > Dan > > > On Wednesday November 29 2006 10:38 am, Jason van Zyl wrote: > >> Hi, >> >> This is a group release to attempt to deal with the licensing >> resources that need to be packaged up in all the archives we >> distribute. This is, in particular, and attempt to deal with the JARs >> we release. Namely the binary, source, and javadoc JARs we create >> with the JAR, Source, and JavaDoc plugins respectively. >> >> I have created the Remote Resources Plugin which is documented here: >> >> http://people.apache.org/~jvanzyl/maven-remote-resources-plugin/ >> >> And I have created a diagram of the process that is currently >> happening as a result of the changes I have made to the Source, and >> JavaDoc plugins: >> >> http://idisk.maven.org/jvanzyl/Public/RemoteResourcesHandling.png >> >> Essentially the remote resources plugins creates a directory of >> resources and modifies the POM at runtime so it carries with it the >> information about this directory. The other archiving plugins then >> look for this resource and insert it into the archives they create if >> found. Ideally the Resource element should have a unique id but the >> directory name will do for now. >> >> You can see here that I've created a profile which will enable the >> remote resources plugins and pull down the bundle that contains the >> standard license and notice files: >> >> http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml >> >> And I have deployed all the plugins above with this tool chain so you >> can see them here: >> >> http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/ >> plugins/maven-remote-resources-plugin/1.0-SNAPSHOT/ >> http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/ >> plugins/maven-source-plugin/2.0.2-SNAPSHOT/ >> http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/ >> plugins/maven-javadoc-plugin/2.2-SNAPSHOT/ >> >> If I can release these plugins then I think we can solve most of the >> licensing/resource doldrums. >> >> Jason. >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
