moving the plugin to release profile, then have a release build different from the usual SNAPSHOT build does not look a good idea
if we need to avoid building with JDK 7 because JDK 8 is required, it's up to Jenkins file to select We already do that for Maven Artifact Transfer for example https://github.com/apache/maven-artifact-transfer/blob/master/Jenkinsfile Le dimanche 4 octobre 2020, 20:37:55 CEST [email protected] a écrit : > This is an automated email from the ASF dual-hosted git repository. > > michaelo pushed a change to branch master > in repository https://gitbox.apache.org/repos/asf/maven-resolver.git. > > > from aa5e9b1 [maven-release-plugin] prepare for next development > iteration add b85faae Move OSGi metadata generation to apache-release > profile > > No new revisions were added by this update. > > Summary of changes: > maven-resolver-api/pom.xml | 162 ++++++------- > maven-resolver-connector-basic/pom.xml | 240 ++++++++++---------- > maven-resolver-impl/pom.xml | 264 +++++++++++----------- > maven-resolver-spi/pom.xml | 159 ++++++------- > maven-resolver-synccontext-global/pom.xml | 36 +-- > maven-resolver-synccontext-redisson/pom.xml | 36 +-- > maven-resolver-test-util/pom.xml | 167 +++++++------- > maven-resolver-transport-classpath/pom.xml | 222 +++++++++--------- > maven-resolver-transport-file/pom.xml | 232 ++++++++++--------- > maven-resolver-transport-http/pom.xml | 338 > ++++++++++++++-------------- maven-resolver-transport-wagon/pom.xml | > 284 ++++++++++++----------- maven-resolver-util/pom.xml | > 169 +++++++------- > pom.xml | 25 +- > 13 files changed, 1208 insertions(+), 1126 deletions(-) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
