On 15/01/14 15:21, Ian Dickinson wrote:
Oh, and I've added a copy of the LICENSE file from the main project.
I'm not sure what else I need to put in there - do I need to
acknowledge the contribution from Shane St Clair that was submitted
via Jira?
Ian
Do either of the the top-level LICENCE or NOTICE files need to change to
reflect dependencies of jena-maven-tools? These need to cover
everything in trunk and ideally the project.
See
http://www.apache.org/legal/3party.html
esp category B
dependency:tree -->
+- org.apache.maven:maven-plugin-api:jar:3.1.1:compile
| +- org.apache.maven:maven-model:jar:3.1.1:compile
| \- org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.0.0.M5:compile
| +- javax.enterprise:cdi-api:jar:1.0:compile
| | +- javax.annotation:jsr250-api:jar:1.0:compile
| | \- javax.inject:javax.inject:jar:1:compile
| +- com.google.guava:guava:jar:10.0.1:compile
| | \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
| +- org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0:compile
| | \- aopalliance:aopalliance:jar:1.0:compile
| +- org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.0.0.M5:compile
| +- org.codehaus.plexus:plexus-component-annotations:jar:1.5.5:compile
| \- org.codehaus.plexus:plexus-classworlds:jar:2.4:compile
org.eclipse.sisu caught my attention and there are others that I don't
know the status of. At that point I didn't know enough to sort it out
at the time.
Acknowledgements are different - common ways include putting in a
README, ReleaseNotes or ACKNOWLEDGEMENTS file for the module.
Andy
