Hi Andreas, You are right about the first error. Launchers' bundles list dependencies can't be managed with maven release plugin like the rest of regular maven dependencies, so the versions of the bundles have to be changed manually when preparing the releasing. It seems that commons.web.sparql SNAPSHOT dependency slip away of that manual process and I didn't replace the SNAPSHOT version by the 1.0.0 version. It should be building anyway because 1.0.0-SNAPSHOT versions should be available at apache snapshots repositories.
Anyway, I can fix it by directly changing the version in the tag and committing the change because launchers are not being deployed so the release shouldn't be affected. About the test errors, I have run them several times and also current jenkins build is finishing ok, so I'm not sure which could be the problem Thanks for reporting! Rafa On Tue, Sep 27, 2016 at 7:19 AM Andreas Kuckartz <a.kucka...@ping.de> wrote: > The mvn build process still is not as resilient as I would like it to be. > > I checked out the sources executing "svn co > https://svn.apache.org/repos/asf/stanbol/tags/apache-stanbol-1.0.0/"; > > "mvn install" resulted in a number of errors which I was able to reduce > to these two: > > 1. > > [ERROR] Failed to execute goal on project > org.apache.stanbol.launchers.mini-war: Could not resolve dependencies > for project > org.apache.stanbol:org.apache.stanbol.launchers.mini-war:war:1.0.0: > Could not find artifact > org.apache.stanbol:org.apache.stanbol.commons.web.sparql:jar:1.0.0-SNAPSHOT > in apache.snapshots (https://repository.apache.org/snapshots) ... > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > > 2. > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test > (default-test) on project > org.apache.stanbol.entityhub.indexing.source.jenatdb: There are test > failures. > [ERROR] > [ERROR] Please refer to > > /home/andreas/stanbol/apache-stanbol-1.0.0/entityhub/indexing/source/jenatdb/target/surefire-reports > for the individual test results. > ... > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > > The surefire report with the failures is appended. > > Very similar or the same failures occured a few years ago. > > > openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-8u102-b14.1-2-b14) > OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode) > > SMP Debian 4.7.4-2 (2016-09-19) x86_64 GNU/Linux > > > I suppose that I missed something. Any suggestions? > > Cheers, > Andreas > --- > > Andreas Kuckartz wrote: > > I am having problems building the package. I will investigate and report > > before tomorrow. > > > > Cheers, > > Andreas > > --- > > > > > > Rafa Haro wrote: > >> Hi devs, > >> > >> Please vote on wether to release Apache Stanbol 1.0.0 RC0. This is the > >> first 1.x.x release and the first release since version 0.12 (more than > 2 > >> years ago). Therefore, it is not easy to summarize all the changes since > >> then. Please refer to https://issues.apache.org/jira/browse/STANBOL > for an > >> exhaustive list of issues fixed in this version. > >> > >> The release source code can be found at the following tag: > >> > >> http://svn.apache.org/repos/asf/stanbol/tags/apache-stanbol-1.0.0/ > >> > >> The release includes the complete Apache Stanbol stack with all > components. > >> The release artifacts are staged at: > >> > >> > https://repository.apache.org/content/repositories/orgapachestanbol-1009/ > >> > >> and the source packages here: > >> > >> https://dist.apache.org/repos/dist/dev/stanbol/1.0.0/ > >> > >> You can check the staged Maven artifacts using the script in 'releasing' > >> ./check_staged_release.sh 1009 [tmp-directory] > >> > >> PGP release singing keys are available at: > >> > >> https://people.apache.org/keys/group/stanbol.asc > >> > >> The vote will be open for 72 hours > >> > > > > >
