Hi Kevin, I have a theory as to why you always see this issue.
The pom.xml at the root references the framework (in core/pom.xml), and the 2 examples apps (ex/app/helloworld/pom.xml and ex/app/simpleapp/pom.xml). The latter two are reverse engineered into the 2 corresponding archetypes (in ex/archetype/*), and it is these that are released along with the core framework. There are three source .zip files available, one for each of these release products. There are therefore three source zip files. Each one can only be used to build the corresponding artefact it relates to. It also means that you shouldn't expect to download any one of them and build from the root directory. If you download the source zip for the core, then you should unzip and cd into core, then build from there. If you attempted to build from root then you would find that the two ex/app/* probably wouldn't build because they would still have -SNAPSHOT versions and may or may not reference a -SNAPSHOT of isis; basically the state of those directories is underined in the core's zip. Similarly, if you were to download either of the .zip files for the two archetypes, then these can only be used to build their respective archetypes, eg cd ex/archetype/helloworld. If you attempted to build the core framework with one of these zip's then you'll find yourself building next -SNAPSHOT, of the core (because the archetypes are released after core). So, in summary, to rebuild the framework from core, you need to: - download the core's source zip file (as listed in the release vote email) - unzip - cd core - mvn clean install If you don't do "cd core" then bad things are gonna happen. Does that make sense? And is there docs we have that are wrong/need improving? Thx Dan On Sun, 7 Jan 2018 at 15:58 Kevin Meyer <ke...@kmz.co.za> wrote: > Hi Dan, > > On Sun, January 7, 2018 14:23, Dan Haywood wrote: > > Also, I know we've discussed previously and didn't resolve, but when you > > say "I still find that the build process tries to download Isis artifacts > > ...", > > what step in the verification process are you actually performing here? > > > > > If I "rm -rf ~/.m2/repository/org/apache/isis" (working from memory here, > please forgive typos), then when I build the Isis release sources: > i.e. "mvn clean install", I see many attempts to download build artifacts: > > e.g. > > > kevin@adell:isis-1.16.0$ mvn clean install > [INFO] Scanning for projects... > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Build Order: > [INFO] > [INFO] Apache Isis > [INFO] Apache Isis Schemas > [INFO] Apache Isis Unit Test Support > .... <snip> ... > [INFO] Apache Isis Maven Dependencies for Webapp > [INFO] Apache Isis Maven Dependencies for Testing > [INFO] > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Apache Isis 1.16.0 > [INFO] > ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ isis --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (validate-enforce) @ isis > --- > [INFO] > [INFO] --- maven-remote-resources-plugin:1.5:process > (process-resource-bundles) @ isis --- > [INFO] > [INFO] --- maven-remote-resources-plugin:1.5:process > (process-remote-resources) @ isis --- > Downloading: > > https://repo.maven.apache.org/maven2/org/apache/isis/core/isis-core-schema/1.16.0/isis-core-schema-1.16.0.jar > Downloading: > > https://repository.apache.org/org/apache/isis/core/isis-core-schema/1.16.0/isis-core-schema-1.16.0.jar > Downloading: > > https://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/isis/core/isis-core-schema/1.16.0/isis-core-schema-1.16.0.jar > > Likewise, the "mvn dependency:go-offline" fails: > > [INFO] <<< maven-dependency-plugin:2.10:go-offline (default-cli) < > :resolve-plugins @ isis-core-applib <<< > Downloading: > > https://repo.maven.apache.org/maven2/org/apache/isis/core/isis-core-unittestsupport/1.16.0/isis-core-unittestsupport-1.16.0.jar > ... <snip> ... > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Isis ........................................ SUCCESS [ > 3.354 s] > [INFO] Apache Isis Schemas ................................ SUCCESS [ > 0.990 s] > [INFO] Apache Isis Unit Test Support ...................... SUCCESS [ > 0.420 s] > [INFO] Apache Isis AppLib ................................. FAILURE [ > 10.611 s] > [INFO] Apache Isis Log4j Impls ............................ SKIPPED > > ... <snip> .... > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 17.337 s > [INFO] Finished at: 2018-01-07T16:45:17+01:00 > [INFO] Final Memory: 33M/259M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project isis-core-applib: Could not > resolve dependencies for project > org.apache.isis.core:isis-core-applib:jar:1.16.0: The following artifacts > could not be resolved: org.apache.isis.core:isis-core-schema:jar:1.16.0, > org.apache.isis.core:isis-core-unittestsupport:jar:1.16.0: Failure to find > org.apache.isis.core:isis-core-schema:jar:1.16.0 in > https://repo.maven.apache.org/maven2 was cached in the local repository, > resolution will not be reattempted until the update interval of central > has elapsed or updates are forced -> [Help 1] > > > I'm using Maven version: > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; > 2017-10-18T09:58:13+02:00) > Maven home: /opt/maven/apache-maven-3.5.2 > > > Cheers, > Kevin > > > > > Thx > > Dan > > > > > > On Sat, 6 Jan 2018 at 15:11 Kevin Meyer <ke...@kmz.co.za> wrote: > > > > > >> Happy New Year everyone! > >> > >> > >> +1 > >> > >> > >> Only comments (in case it helps someone else), for the "Simple App" > >> archetype, the online instructions do not work: "cd myapp ; mvn clean > >> install -o && mvn -pl jetty:run -o" > >> > >> I had to: > >> "cd myapp ; mvn clean install -o ; cd webapp ; mvn jetty:run -o" > >> > >> > >> > >> I still find that the build process tries to download Isis artifacts > >> that it is about to build if there are missing 3rd party dependencies. > >> But once all 3rd party maven dependencies have been downloaded an > >> offline "mvn install -o" does work, so I guess it is just the usual > >> failure of Maven to realise that some of the artifacts are in the build > >> queue. > >> > >> Cheers, > >> Kevin > >> > >> > >> > >> On Thu, January 4, 2018 20:30, Dan Haywood wrote: > >> > >>> Hi folks > >>> > >>> > >>> > >>> and a happy new year! > >>> > >>> I've cut a release for Apache Isis Core and the two archetypes: > >>> > >>> > >>> > >>> * Core 1.16.0 > >>> * HelloWorld Archetype 1.16.0 > >>> * SimpleApp Archetype 1.16.0 > >>> > >>> > >>> > >>> The source code artifacts have been uploaded to staging repositories > >>> on repository.apache.org: > >>> > >>> > >>> > >>> * > >>> > >>> > >> http://repository.apache.org/content/repositories/orgapacheisis-1062/or > >> g/a > >>> pache/isis/core/isis/1.16.0/isis-1.16.0-source-release.zip * > >>> > >> http://repository.apache.org/content/repositories/orgapacheisis-1063/or > >> g/a > >>> pache/isis/archetype/helloworld-archetype/1.16.0/helloworld-archetype > >>> -1.1 > >>> 6.0-source-release.zip > >>> * > >>> > >>> > >> http://repository.apache.org/content/repositories/orgapacheisis-1063/or > >> g/a > >>> pache/isis/archetype/simpleapp-archetype/1.16.0/simpleapp-archetype-1 > >>> .16. > >>> 0-source-release.zip > >>> > >>> > >>> > >>> For each zip there is a corresponding signature file (append .asc to > >>> the zip's url). > >>> > >>> In the source code repo the code has been tagged as isis-1.16.0-RC1, > >>> helloworld-archetype-1.16.0-RC1 and simpleapp-archetype-1.16.0-RC1; > >>> see https://github.com/apache/isis/tags > >>> > >>> > >>> > >>> For instructions on how to verify the release (build from binaries > >>> and/or use in Maven directly), see > >>> > >> https://isis.apache.org/guides/cgcom/cgcom.html#_cgcom_verifying-releas > >> es > >>> > >>> > >>> Please verify the release and cast your vote. The vote will be open > >>> for a minimum of 72 hours. > >>> > >>> [ ] +1 > >>> [ ] 0 > >>> [ ] -1 > >>> > >>> > >>> > >> > >> > >> -- > >> Kevin Meyer > >> Ljubljana, Slovenia > >> > >> > >> > >> > > > > > -- > Kevin Meyer > Ljubljana, Slovenia > > >