I just created "buildconsumer" branch for Maven Archetype: https://github.com/apache/maven-archetype/tree/buildconsumer
CLI building with Maven 3.6.3 expectedly breaks: $ mvn verify -Drevlist=test [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] 'parent.version' is missing. @ line 26, column 11 [FATAL] 'parent.version' is missing. @ line 26, column 11 [FATAL] 'parent.version' is missing. @ line 26, column 11 [FATAL] 'parent.version' is missing. @ line 25, column 11 @ [ERROR] The build could not read 4 projects -> [Help 1] [ERROR] [ERROR] The project org.apache.maven.archetype:archetype-models:[unknown-version] (/home/herve/projets/maven/sources/plugins/tools/archetype/archetype-models/pom.xml) has 1 error [ERROR] 'parent.version' is missing. @ line 26, column 11 [ERROR] [ERROR] The project org.apache.maven.archetype:archetype-common:[unknown-version] (/home/herve/projets/maven/sources/plugins/tools/archetype/archetype-common/pom.xml) has 1 error [ERROR] 'parent.version' is missing. @ line 26, column 11 [ERROR] [ERROR] The project org.apache.maven.plugins:maven-archetype-plugin:[unknown-version] (/home/herve/projets/maven/sources/plugins/tools/archetype/maven-archetype-plugin/pom.xml) has 1 error [ERROR] 'parent.version' is missing. @ line 26, column 11 [ERROR] [ERROR] The project org.apache.maven.archetype:archetype-packaging:[unknown-version] (/home/herve/projets/maven/sources/plugins/tools/archetype/archetype-packaging/pom.xml) has 1 error [ERROR] 'parent.version' is missing. @ line 25, column 11 With 3.7.0-SNAPSHOT, most issues are gone, but 1 remains: $ mvn verify -Drevlist=test [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [ERROR] 'dependencies.dependency.version' for org.apache.maven.archetype:archetype-packaging:jar is missing. @ org.apache.maven.plugins:maven-archetype-plugin:[unknown-version], /home/herve/projets/maven/sources/plugins/tools/archetype/maven-archetype-plugin/pom.xml, line 81, column 17 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.apache.maven.plugins:maven-archetype-plugin:3.2.0-SNAPSHOT (/home/herve/projets/maven/sources/plugins/tools/archetype/maven-archetype-plugin/pom.xml) has 1 error [ERROR] 'dependencies.dependency.version' for org.apache.maven.archetype:archetype-packaging:jar is missing. @ org.apache.maven.plugins:maven-archetype-plugin:[unknown-version], /home/herve/projets/maven/sources/plugins/tools/archetype/maven-archetype-plugin/pom.xml, line 81, column 17 I suppose it is because of the test-scoped dependency that is not covered... I'll try creating such branch on other Maven multi-module builds to check if they build with CLI Then it will be about checking in IDE how well it work or not... Regards, Hervé Le dimanche 5 juillet 2020, 11:07:56 CEST Hervé BOUTEMY a écrit : > idea: why not create a branch in one or multiple Maven multi-module builds > that will show the new features (no parent version, no version for reactor, > and I don't know what else) > > I suppose creating such branches in maven-archetype, maven-plugin-tools, > Maven core itself, would not be hard and would bring examples to test both > on CLI (I expect the build to fail if the experimental feature is not > enabled), then in IDE > > Regards, > > Hervé > > Le samedi 4 juillet 2020, 10:12:24 CEST Robert Scholte a écrit : > > On 4-7-2020 08:08:00, Mark Derricutt <[email protected]> wrote: > > I thought I’d responded - this has been a long time coming, and has been > > discussed numerous times over the past few years, and I’m quite excited to > > give it a bash, and see how well it works, and see if/what any > > implications > > this has for our tiles-maven-plugin. > > > > I still need to find time to dig into this. > > > > Robert - is there anything specific one does to “enable” this currently - > > or is the current merge simply the machinery to take the build pom (even > > if > > its a 4.0.0 model) and produce the consumer pom. > > Robert Scholte: > > There is a feature toggle, see > > https://github.com/apache/maven/blob/master/maven-model-builder/src/main/j > > av a/org/apache/maven/feature/Features.java#L34 > > > > Here you see the name, which is still part of discussion because it is not > > that experimental anymore, and its default value. > > > > > > Currently I don’t see any diffs between my pom.xml, and the pom.xml that > > gets included inside the .jar file, I tried doing a “mvn deploy” to check > > the version that got deployed, but yields an missing class exception using > > 2.8.2: > > > > Robert Scholte: > > That is one one the next important steps that needs to be implemented: the > > archiver should include the consumer pom.xml, not the local pom. > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) > > on project smx3.reporting: Execution default-deploy of goal > > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy failed: A > > required class was missing while executing > > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy: > > org/eclipse/aether/transform/FileTransformer > > [ERROR] ----------------------------------------------------- > > [ERROR] realm = plugin>org.apache.maven.plugins:maven-deploy-plugin:2.8.2 > > > > Robert Scholte: > > Does this mean that the install:install did work? > > That would be interesting. > > I am not aware of that issue. Is there already a JIRA ticket for it, > > because this must be solved before the next release. > > > > > > (I’m unable to currently use 3.0.0-M1 for the same reason either). > > > > Hrm. > > Mark > > > > > > From: Jaroslav Tulach > > > > Reply: Maven Developers List > > Date: 4 July 2020 at 5:35:37 PM > > To: dev > > Cc: [email protected] , > > [email protected] , > > [email protected] , > > [email protected] > > Subject: Re: Maven moving to the next level: the build/consumer pom > > > > Hello Robert, > > I am not sure how to deal with your announcement and given no reaction on > > the dev@netbeans mailing list, I am probably not alone. Can you formulate > > --------------------------------------------------------------------- > 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]
