Adding extra "scope" type metadata to dependencies?
Hello! I'd like to be able to add extra metadata to dependencies in a POM file. Specifically: 1. I'd like to be able to specify whether a dependency goes on the class or module path rather than have Maven decide for me. 2. I'd like to be able to specify that a dependency _doesn't_ go on either path (possibly because it's going to be added manually elsewhere during deployment as an OSGi bundle, or as part of a dynamically created module layer, or something similar). Ideally, the second point would be handled properly by IDEs such that clicking "Run" wouldn't result in artifacts being added to the classpath/modulepath of the program the IDE runs. I remember reading (possibly over a year ago now) that there might be some possibility of an extension that allows for adding extra information to a element, but I'm now unable to find any evidence this existed. Is there some way to do this today? If not... Will there be some way in Maven 4.0.0+? -- Mark Raynsford | https://www.io7m.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Resolver 1.9.0
Howdy, We solved 18 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12351593 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues Staging repo: https://repository.apache.org/content/repositories/maven-1821/ Source release SHA512: 18cb7eb11361996822f2d08b389346774bf1364bbfe699346f23774e5438cf22c91e12639aa21ddc91f4db000756d54a1c115b518ffb34f060cb78bef171 Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1
[VOTE] Release Maven Indexer 7.0.0
Howdy, We solved 17 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12342224 There are still couple of issues left in JIRA: https://issues.apache.org/jira/projects/MINDEXER/issues Staging repo: https://repository.apache.org/content/repositories/maven-1820/ Source release SHA512: b77ad67c8e9ad7dd81d7af2288a8b32da257a63f6cb7269bc6838c63d88bc9c92cdaf213da5f936bcac9cb7102a91b09892f00eb36ac98924b9817b2a4d25b17 Staging site: https://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1
Re: [VOTE] Release Apache Maven 4.0.0-alpha-2
There are known issues that will be fixed in the next milestone. This problem in particular has already been fixed in [1]. The flatten plugin is still relevant, as the goal for maven 4.0 is to be compatible with maven 3 apart from the removal of things that have been deprecated since ages. [1] https://github.com/apache/maven/pull/836 Le mar. 8 nov. 2022 à 07:11, Delany a écrit : > Hi. I noticed the vote passed for alpha-2, but I'm still getting this > issue. Can someone comment? > Is the flatten plugin still relevant in Maven 4? > > Thanks, > Delany > > On Thu, 20 Oct 2022 at 09:26, Delany wrote: > > > hi. I just changed .mvn/wrapper/maven-wrapper.properties to > > distributionUrl= > > > https://repository.apache.org/service/local/repositories/maven-1811/content/org/apache/maven/apache-maven/4.0.0-alpha-2/apache-maven-4.0.0-alpha-2-bin.zip > > > > The options now require an equals: --threads=1C, but the help page still > > shows a space: -T,--threads > > > > After fixing that it fails with > > [ERROR] Failed to execute goal > > org.codehaus.mojo:flatten-maven-plugin:1.3.0:flatten (flatten) on project > > maven-super: Execution flatten of goal > > org.codehaus.mojo:flatten-maven-plugin:1.3.0:flatten failed: An API > > incompatibility was encountered while executing > > org.codehaus.mojo:flatten-maven-plugin:1.3.0:flatten: > > java.lang.NoSuchMethodError: 'void > > > org.apache.maven.model.interpolation.MavenBuildTimestamp.(java.util.Date, > > java.util.Properties)' > > [ERROR] - > > [ERROR] realm =plugin>org.codehaus.mojo:flatten-maven-plugin:1.3.0 > > [ERROR] strategy = > > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > > [ERROR] urls[0] = > > > file:/home/sol/.m2/repository/org/codehaus/mojo/flatten-maven-plugin/1.3.0/flatten-maven-plugin-1.3.0.jar > > [ERROR] urls[1] = > > > file:/home/sol/.m2/repository/org/apache/maven/shared/maven-dependency-tree/3.2.0/maven-dependency-tree-3.2.0.jar > > [ERROR] urls[2] = > > > file:/home/sol/.m2/repository/org/codehaus/plexus/plexus-utils/3.4.2/plexus-utils-3.4.2.jar > > [ERROR] urls[3] = > > > file:/home/sol/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar > > [ERROR] urls[4] = > > > file:/home/sol/.m2/repository/javax/enterprise/cdi-api/1.0/cdi-api-1.0.jar > > [ERROR] urls[5] = > > > file:/home/sol/.m2/repository/javax/annotation/jsr250-api/1.0/jsr250-api-1.0.jar > > [ERROR] urls[6] = > > > file:/home/sol/.m2/repository/org/eclipse/sisu/org.eclipse.sisu.inject/0.3.0.M1/org.eclipse.sisu.inject-0.3.0.M1.jar > > [ERROR] urls[7] = > > > file:/home/sol/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar > > [ERROR] urls[8] = > > > file:/home/sol/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar > > [ERROR] urls[9] = > > > file:/home/sol/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar > > [ERROR] urls[10] = > > > file:/home/sol/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar > > [ERROR] urls[11] = > > > file:/home/sol/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar > > [ERROR] urls[12] = > > > file:/home/sol/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar > > [ERROR] urls[13] = > > > file:/home/sol/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.0.0/plexus-component-annotations-2.0.0.jar > > [ERROR] urls[14] = > > > file:/home/sol/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.1.0/maven-common-artifact-filters-3.1.0.jar > > [ERROR] urls[15] = > > > file:/home/sol/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar > > [ERROR] urls[16] = > > > file:/home/sol/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar > > [ERROR] Number of foreign imports: 1 > > [ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: > > null]] > > > > Regards, > > Delany > > > > On Sat, 15 Oct 2022 at 02:19, Guillaume Nodet wrote: > > > >> I've staged a release candidate at > >> https://repository.apache.org/content/repositories/maven-1811 > >> > >> The binaries are available at: > >> > >> > >> > https://repository.apache.org/service/local/repositories/maven-1811/content/org/apache/maven/apache-maven/4.0.0-alpha-2/ > >> > >> The tag is available at: > >> https://github.com/apache/maven/tree/maven-4.0.0-alpha-2 > >> > >> Please review and vote ! > >> > >> Cheers, > >> Guillaume Nodet > >> > > > -- Guillaume Nodet
Re: Releases notes ... Jira, GitHub
wt., 8 lis 2022 o 01:16 Olivier Lamy napisał(a): > well I just see GH release note as a cherry on the cake. > as long as the rest is done. Just compare the result of generated dependabot PRs > no GH release notes > https://github.com/eclipse/jetty.project/pull/8853 > with GH release notes > https://github.com/eclipse/jetty.project/pull/7727 > I tend to find the second (e.g with GH release note auto generated) > more human readable and directly accessible (no need to go somewhere > else and there is even a link to the PR of the changelog entry). but > yeah maybe it's only me > > Yes, you are right. To be honest I also like GH release notes, and I think that is more readable. It is also used by other tools like dependabot. Moreover, I think that most users can not reach release notes in Jira - it is visible for logged users. But we should have a fresh cherry with a new cake :-) For me the biggest issue is that we can have slightly different release notes for the same version, or missing release notes on GitHub for the new version. Regarding "each change must be done by PR", for some reasons we can’t > really make it mandatory but let's be honest in real life everybody > does it :) > At the end, if release drafter is configured it's just one click, and > if not it's 2 clicks or one command line if using github cli tool gh > > I did an experiment for Plugin Tools - https://github.com/apache/maven-plugin-tools/releases/tag/maven-plugin-tools-3.7.0 - Copy release notes in html from jira - use online html to markdown converter - paste to GitHub so also not many "clicks" On a more general discussion, we are a very large project with plenty > of sub projects (maintained by different people who are not > maintaining every project) and we can be happy having few people > maintaining those during their spare time. So not sure it's a very > good idea to have too strict policies/procedures especially when it > comes to adding a nice to have cherry on the top for users > Especially when the rest of our long procedure has been done. > > I'm not for strict procedure - rather discussion is about good practices > > > On Tue, 8 Nov 2022 at 09:00, Slawomir Jaranowski > wrote: > > > > Hi, > > I start a discussion ... as beginning - some my loose thoughts > > > > We use Jira (for most of) as our primary issues management system. > > We manage release notes in Jira - it is the source for announcements. > > > > In some projects we have GitHub releases notes. > > In some cases we use release-drafter for preparing GitHub releases notes. > > Some of release notes on GH - it is not actual > > > > Challenge: > > - make both release notes to have the same information > > - minimal additional manual work > > > > Release - drafter is fine, but > > - requires correct labeling on PR > > - eache change must be done by PR > > - each PR must be merged on GH with merged status > > - no additional issues > > > > > > -- > > Sławomir Jaranowski > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
