Side-note - https://builds.apache.org/view/All/job/Jena_Development_Test/ doesn't have any special profiles it activates, so as it stands with my new pull request, jena-osgi-test would not be tested by Jenkins.
(Perhaps activation by either -Papache-release or -Pall-tests ? ) On 2 February 2015 at 13:26, Stian Soiland-Reyes <[email protected]> wrote: > So the jena-osgi-test is not needed for *building* any artifacts > (except itself, which probably we should find a way to avoid pushing > to Maven central). It is not required for anything else. The test is > only run during the integration-test phase. > > It seems to still be run if you do -DskipTests -Papache-release - so perhaps > > If only enabling it through -Papache-release is not enough, perhaps we > could just leave it there, uncommented from the parent - and then > someone (I guess myself) would have to remember to run it for every > release candidate? > > On 2 February 2015 at 13:11, Andy Seaborne <[email protected]> wrote: >> On 02/02/15 11:33, Stian Soiland-Reyes wrote: >>>> >>>> 2/ There is a LGPL dependency (scope test) which needs investigation. >>>> >(I would have appreciated that having been pointed out first) >>> >>> Sorry, I didn't mention this outside the pom.xml as it was a >>> build/test dependency, which I thought would be OK - given: >>> https://www.apache.org/legal/resolved.html#prohibited >>> >>> The eosgi-maven-plugin Maven plugin is also LGPL. >> >> >> That's not what resolved.html#prohibited is referring to. That is general >> principles, not java specific. >> >> An Apache release must be reproducible; it's not just code. >> >> The source-resource that is the formal release must be buildable by a >> down-stream user. Jena ships our repo (the Apache parent does the work). >> >> The down-stream user must be able to build the same artifacts; they may wish >> to check against any binaries in maven, or to modify them. Just maven >> -sources is not enough. maven central is not n Apache hardware. >> >> As far as I know, we can not ship source-release that pulls in LGPL, even to >> test, without the user making an explicit act to knowingly do that and work >> without it. >> >> How do other projects do testing? >> >> Andy >> >> >> >> > > > > -- > Stian Soiland-Reyes, eScience Lab > School of Computer Science > The University of Manchester > http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
