Resolving properties in published poms
Hey all, Bit of a crazy, mad, deep-in-bowels-of-maven question for you all. In our locally published artifacts we've been declaring dependency versions in a property within our poms: ```xml 1.2.3 ... test test ${test.version} ``` and that all works fine. When we build projects that depend on such artifacts everything is fine, most likely due to the the property being defined IN the pom. However, we've started moving to/attempting to use a custom lifecycle extension that reads properties definitions from an external file, similar to the `properties-maven-plugin` but on more steroids, and I suspect that since the properties are no longer in the `pom.xml` file, this is the cause of the following exception that we see: ``` org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project smx3.featureset: Could not resolve dependencies for project smx3:smx3.featureset:jar:180-cr.17-SNAPSHOT: Failed to collect dependencies at smx3:smx3.statistics:jar:12.0.38-SNAPSHOT -> org.jooq:jooq:jar:[${jooq.version}] at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:245) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project smx3:smx3.featureset:jar:180-cr.17-SNAPSHOT: Failed to collect dependencies at smx3:smx3.statistics:jar:12.0.38-SNAPSHOT -> org.jooq:jooq:jar:[${jooq.version}] at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:180) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195) ... 23 more Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed to collect dependencies at smx3:smx3.statistics:jar:12.0.38-SNAPSHOT -> org.jooq:jooq:jar:[${jooq.version}] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:172) ... 24 more Caused by: org.eclipse.aether.resolution.VersionRangeResolutionException: No versions available for org.jooq:jooq:jar:[${jooq.version}] within specified range at org.eclipse.aether.internal.impl.DefaultDependencyCollector.filterVersions(DefaultDependencyCollector.java:648) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:394) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at
Re: [VOTE] Release Apache Maven JAR Plugin version 3.0.1
+1 On 7 June 2016 at 22:22, Anders Hammarwrote: > > > > Some findings: > > * pom.properties doesn't include time stamp row (exists in v3.0.0) > > * MANIFEST.MF does not include Archiver-Version element (exists in > v3.0.0) > > - seems to be an intentional change in plexus-archiver 3.3 > > > > Is the change to pom.properties intentional? > > > > I'll answer this myself: > MSHARED-494 of maven-archiver 3.1.0 did this change to provide for > reproducible builds. > > I'm changing my vote to +1. > > /Anders > > > > > > I vote 0. > > > > /Anders > > > > On Mon, Jun 6, 2016 at 10:10 PM, Karl Heinz Marbaise > > wrote: > > > >> Hi, > >> > >> We solved 4 issues: > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12335708 > >> > >> There are still a couple of issues left in JIRA: > >> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20XX%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-1276/ > >> > >> > https://repository.apache.org/content/repositories/maven-1276/org/apache/maven/plugins/maven-jar-plugin/3.0.1/maven-jar-plugin-3.0.1-source-release.zip > >> > >> Source release checksum(s): > >> maven-jar-plugin-3.0.1-source-release.zip sha1: > >> 195a324abe69bae09204bc8fefe11e1e11264155 > >> > >> Staging site: > >> http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/ > >> > >> Guide to testing staged releases: > >> http://maven.apache.org/guides/development/guide-testing-releases.html > >> > >> Vote open for 72 hours. > >> > >> [ ] +1 > >> [ ] +0 > >> [ ] -1 > >> > >> Kind regards > >> Karl Heinz Marbaise > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Maven Javadoc Plugin version 2.10.4
The patch I supplied for MJAVADOC-452, 451, 434 and 420 won't be considered for inclusion? I can recreate the patch off of the latest trunk if it would help Best regards, Richard Sent from my iPhone > On Jun 7, 2016, at 2:39 PM, Robert Scholtewrote: > > Hi, > > We solved 12 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12331967=Text > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317529%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1277/ > https://repository.apache.org/content/repositories/maven-1277/org/apache/maven/plugins/maven-javadoc-plugin/2.10.4/maven-javadoc-plugin-2.10.4-source-release.zip > Source release checksum(s): > maven-javadoc-plugin-2.10.4-source-release.zip sha1: > 9bd4cef08be14f6c313db68a6cd57b97e449e0aa > > Staging site: > http://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ > > Guide to testing staged releases: > http://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
[GitHub] maven-shared pull request #11: MJAR-223 - classpathLayoutType is not taken i...
GitHub user tomerc opened a pull request: https://github.com/apache/maven-shared/pull/11 MJAR-223 - classpathLayoutType is not taken into account when buildin⦠â¦g the classpath attribute in the manifest You can merge this pull request into a Git repository by running: $ git pull https://github.com/tomerc/maven-shared trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-shared/pull/11.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #11 commit 22c628264d8498f118397b17120ffc21844b0919 Author: Tomer CohenDate: 2016-06-07T22:44:48Z MJAR-223 - classpathLayoutType is not taken into account when building the classpath attribute in the manifest --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Apache Maven Javadoc Plugin version 2.10.4
Hi, We solved 12 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12331967=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317529%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1277/ https://repository.apache.org/content/repositories/maven-1277/org/apache/maven/plugins/maven-javadoc-plugin/2.10.4/maven-javadoc-plugin-2.10.4-source-release.zip Source release checksum(s): maven-javadoc-plugin-2.10.4-source-release.zip sha1: 9bd4cef08be14f6c313db68a6cd57b97e449e0aa Staging site: http://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ Guide to testing staged releases: http://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
[ANN] Apache Maven Shared Component: Maven Archiver Version 3.1.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Archiver Version 3.1.0. https://maven.apache.org/shared/maven-archiver/ The Maven Archiver is mainly used by plugins to handle packaging. The version numbers referenced in the Since column on this page are the version of the Maven Archiver component - not for any specific plugin. To see which version of Maven Archiver a plugin uses, go to the site for that plugin. Important Notes since Version 3.0.0: * Maven 3.X only * JDK 6 minimum requirement You should specify the version in your project's plugin configuration: org.apache.maven.shared maven-archiver 3.1.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-archiver/download.cgi Release Notes Maven Archiver 3.1.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12335563 Bugs: * [MSHARED-494] - Impossible to generate a reproducible build due to timestamp in pom.properties * [MSHARED-544] - Remove maven-fluido-skin from site descriptor Improvements: * [MSHARED-515] - Addition of xz compression support. * [MSHARED-522] - Upgrade maven-shared-components parent to version 30 * [MSHARED-539] - Upgrade plexus-utils to 3.0.24 * [MSHARED-540] - Upgrade plexus-interpolation to 1.22 * [MSHARED-541] - Upgrade maven-shared-utils to 3.0.1 * [MSHARED-542] - Upgrade plexus-archiver to 3.3 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Apache Maven Resources Plugin version 3.0.1
Hi, The vote has passed with the following result: +1 : Robert Scholte, Hervé Boutemy, Anders Hammar, Karl Heinz Marbaise PMC quorum: reached. I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin release?
Hi, shared component: maven-artifact-transfer not released yet...cause it's new... currently i'm testing other plugins which use it if works everything well... So we need to prepare maven-artifact-transfer first... On 6/7/16 2:24 PM, Olivier Lamy wrote: Hi I can have a look next week. I think there is a dependency to release as well. Cheers -- Olivier On 7 Jun 2016 01:25, "Jesse McConnell"wrote: We are looking to get Jetty building with java 9 now and are a touch stuck with the latest maven-assembly-plugin needing to be released for 3.0.0. We notice the issue we need resolved seems to have been fixed up last week and we are curious if there is a release date targeted? You might check if you could use the following temporary solution: ... maven-assembly-plugin 2.6 org.codehaus.plexus plexus-archiver 3.3 <...> Kind regards Karl Heinz Marbaise cheers, Jesse -- jesse mcconnell jesse.mcconn...@gmail.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin release?
excellent.. :) -- jesse mcconnell jesse.mcconn...@gmail.com On Tue, Jun 7, 2016 at 7:24 AM, Olivier Lamywrote: > Hi > I can have a look next week. I think there is a dependency to release as > well. > Cheers > -- > Olivier > On 7 Jun 2016 01:25, "Jesse McConnell" wrote: > > > We are looking to get Jetty building with java 9 now and are a touch > stuck > > with the latest maven-assembly-plugin needing to be released for 3.0.0. > We > > notice the issue we need resolved seems to have been fixed up last week > and > > we are curious if there is a release date targeted? > > > > cheers, > > Jesse > > > > -- > > jesse mcconnell > > jesse.mcconn...@gmail.com > > >
Re: maven-assembly-plugin release?
Hi I can have a look next week. I think there is a dependency to release as well. Cheers -- Olivier On 7 Jun 2016 01:25, "Jesse McConnell"wrote: > We are looking to get Jetty building with java 9 now and are a touch stuck > with the latest maven-assembly-plugin needing to be released for 3.0.0. We > notice the issue we need resolved seems to have been fixed up last week and > we are curious if there is a release date targeted? > > cheers, > Jesse > > -- > jesse mcconnell > jesse.mcconn...@gmail.com >
Re: [VOTE] Release Apache Maven JAR Plugin version 3.0.1
> > Some findings: > * pom.properties doesn't include time stamp row (exists in v3.0.0) > * MANIFEST.MF does not include Archiver-Version element (exists in v3.0.0) > - seems to be an intentional change in plexus-archiver 3.3 > > Is the change to pom.properties intentional? > I'll answer this myself: MSHARED-494 of maven-archiver 3.1.0 did this change to provide for reproducible builds. I'm changing my vote to +1. /Anders > > I vote 0. > > /Anders > > On Mon, Jun 6, 2016 at 10:10 PM, Karl Heinz Marbaise> wrote: > >> Hi, >> >> We solved 4 issues: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12335708 >> >> There are still a couple of issues left in JIRA: >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20XX%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-1276/ >> >> https://repository.apache.org/content/repositories/maven-1276/org/apache/maven/plugins/maven-jar-plugin/3.0.1/maven-jar-plugin-3.0.1-source-release.zip >> >> Source release checksum(s): >> maven-jar-plugin-3.0.1-source-release.zip sha1: >> 195a324abe69bae09204bc8fefe11e1e11264155 >> >> Staging site: >> http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/ >> >> Guide to testing staged releases: >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> Kind regards >> Karl Heinz Marbaise >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >
Re: [VOTE] Release Apache Maven JAR Plugin version 3.0.1
Some findings: * pom.properties doesn't include time stamp row (exists in v3.0.0) * MANIFEST.MF does not include Archiver-Version element (exists in v3.0.0) - seems to be an intentional change in plexus-archiver 3.3 Is the change to pom.properties intentional? I vote 0. /Anders On Mon, Jun 6, 2016 at 10:10 PM, Karl Heinz Marbaisewrote: > Hi, > > We solved 4 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12335708 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20XX%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1276/ > > https://repository.apache.org/content/repositories/maven-1276/org/apache/maven/plugins/maven-jar-plugin/3.0.1/maven-jar-plugin-3.0.1-source-release.zip > > Source release checksum(s): > maven-jar-plugin-3.0.1-source-release.zip sha1: > 195a324abe69bae09204bc8fefe11e1e11264155 > > Staging site: > http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Kind regards > Karl Heinz Marbaise > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >