Howdy, yes, we discussed this with Guillaume, and the turn we want to take is something along these lines: - once alpha-13 out, we need new resolver release (there is a cycle there, but only for "demos" and suppliers). Some classes from resolver need to be dropped, things redirected to classes present in alpha-13. - lean onto plugin migration to v4 API - this will probably generate a feedback of changes back into v4 API - and yes, this means we should slowly going for 'betas"
But this was just generally discussed by the two of us. On Thu, Mar 7, 2024 at 9:06 AM Maarten Mulders <mthmuld...@apache.org> wrote: > +1 > > I agree with Romain, isn't it about time we move to beta or milestone > releases? I think it may give us two benefits: > > 1. likely to attract more early-bird testers, which can give us valuable > feedback. > 2. hopefully convince third-party plugin maintainers to start working on > Maven 4 compatibility. > > > Thanks, > > Maarten > > On 07/03/2024 08:37, Romain Manni-Bucau wrote: > > +1 > > > > (side note for future releases: we can move to milestone versioning more > > than alpha since we are not alpha at all it seems, are we?) > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://rmannibucau.metawerx.net/> | Old Blog > > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > < > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > > > > Le jeu. 7 mars 2024 à 00:08, Karl Heinz Marbaise > <khmarba...@gmx.de.invalid> > > a écrit : > > > >> Hi, > >> > >> I see the following with 4.0.0-alpha-13 with a test project (spring > >> boot based 3.3.0-M2): > >> > >> [INFO] Unable to find the root directory. Create a .mvn directory in the > >> root directory or add the root="true" attribute on the root project's > >> model to identify it. > >> [INFO] Scanning for projects... > >> [WARNING] > >> [WARNING] Some problems were encountered while building the effective > >> model for 'com.soebes.spring.example:employee:jar:0.0.1-SNAPSHOT' > >> [WARNING] Ignored POM import for: > >> org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.7.0@compile > >> as already imported > >> > org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.10.2@compile. > >> Add a the conflicting managed dependency directly to the > >> dependencyManagement section of the POM. @ > >> org.springframework.boot:spring-boot-dependencies:3.3.0-M2, > >> > >> > /Users/khm/.m2/repository/org/springframework/boot/spring-boot-dependencies/3.3.0-M2/spring-boot-dependencies-3.3.0-M2.pom > >> [WARNING] > >> [WARNING] It is highly recommended to fix these problems because they > >> threaten the stability of your build. > >> [WARNING] > >> [WARNING] For this reason, future Maven versions might no longer support > >> building such malformed projects. > >> [WARNING] > >> > >> The given bom file contains also a pluginManagement section with a > >> number of plugins defined in .... > >> > >> > >> The interesting part is that 4.0.0-alpha-12 does not produce such > >> warning at all: > >> > >> [INFO] Unable to find the root directory. Create a .mvn directory in the > >> root directory or add the root="true" attribute on the root project's > >> model to identify it. > >> [INFO] Scanning for projects... > >> [INFO] > >> [INFO] ------------------------------------------< > >> com.soebes.spring.example:employee > >> >------------------------------------------ > >> [INFO] Building Employee Demo Application 0.0.1-SNAPSHOT > >> [INFO] from pom.xml > >> [INFO] ---------------------------------------------------------[ jar > >> ]---------------------------------------------------------- > >> [INFO] > >> [INFO] --- clean:3.3.2:clean (default-clean) @ employee --- > >> [INFO] Deleting > >> /Users/khm/ws-git-soebes/examples/spring-boot-plus-spring-data/target > >> [INFO] > >> > >> Any ideas what happens? > >> > >> > >> Kind regards > >> Karl Heinz Marbaise > >> > >> On 06.03.24 21:42, Tamás Cservenák wrote: > >>> Howdy, > >>> > >>> This is a vote to release Apache Maven 4.0.0-alpha-13. > >>> > >>> We solved 32 issues: > >>> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354062 > >>> > >>> There are still some issues in JIRA: > >>> https://issues.apache.org/jira/projects/MNG/issues > >>> > >>> Release candidates: > >>> https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-13/ > >>> > >>> Staging repository: > >>> https://repository.apache.org/content/repositories/maven-2068/ > >>> > >>> Source release SHA512: > >>> - apache-maven-4.0.0-alpha-13-src.zip > >>> > >> > 5e997e382ad7e5021009b74a6a80b9c9076282a3a71260636efc99c28ffad2c4d093d896364e705d853015f6c7d949523fc78c4ebb6aa55edeb43e383f084e3d > >>> - apache-maven-4.0.0-alpha-13-src.tar.gz > >>> > >> > 59cc1b312b240e93e9f51ab9549c69385e12ccf5453b8e6238470437fce8ca802bda0eddc66ca94c5d6d05c02e44c0f78d0d7d2038998559a61df6e5c599da10 > >>> > >>> Staging site: > >>> https://maven.apache.org/ref/4-LATEST/ > >>> Note: site publishing (execution time of `mvn scm-publish:publish-scm`) > >> now > >>> takes 32 minutes! We need to do something about this... > >>> > >>> Guide to testing staged releases: > >>> > https://maven.apache.org/guides/development/guide-testing-releases.html > >>> > >>> Vote open for 72 hours. > >>> > >>> [ ] +1 > >>> [ ] +0 > >>> [ ] -1 > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
