[ANN] Apache Maven Shade Plugin 3.2.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shade Plugin, version 3.2.1 Repackages the project classes together with their dependencies into a single uber-jar, optionally renaming classes or removing unused classes. https://maven.apache.org/plugins/maven-shade-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-shade-plugin 3.2.1 Release Notes - Apache Maven Shade Plugin - Version 3.2.1 Bug * [MSHADE-302] maven-shade-plugin fails to minimize JAR with Java 11 * [MSHADE-291] shadedPattern applied multiples times when relocating the contents of META-INF/services files Improvement * [MSHADE-303] Suppress module-info.class warning if the file if filtered Task * [MSHADE-301] java11 support * [MSHADE-299] Upgrade maven-dependency-tree to 3.0.1 Enjoy, -The Apache Maven team
Re: Testing Release Candidates
Karl, some answers inline, thank you for answers Il ven 12 ott 2018, 16:28 Karl Heinz Marbaise ha scritto: > Hi Enrico, > > > On 12/10/18 10:36, Enrico Olivelli wrote: > > Hi, > > I would like to test Maven Plugins Release Candidates. > > Great that you like to help... > Maven is at the core of most of every java project in the world, for me it is vital. I wonder why there is not so much help from the comunity. Just doing my best to help. Time is limited unfortunately. :) > > > > I know there is a brief guide > > https://maven.apache.org/guides/development/guide-testing-releases.html > > But I think this is not very complete and/or it is outdated. > > It might be if so we need to update/enhance it as needed... > > > > > The summary of the guide is to run > > mvn verify > > For instance this is not true for Surefire. > > Yes there are some of the release which need different approach usually > documented in README.md (I'm not sure if all have a README.md...or need > one)...for Maven Core this not enough (mvn clean install) and test the > resulting core with different project of your own choice... > > > > > > Can someone explain better how is it expected to run a check on an RC ? > > First we don't do RC's ...what we sometimes do is to release Milestones > (for example with maven-install, maven-deploy-plugin).. > But in the end we release usual release something like "3.0.0" or > "3.2.0" > > If it happens that a release has issues we remove the tags and drop the > staging repository and spin a new release with the same version... > > > For Maven core we do not use the same version we continue with the next > one... > > > > > In other Apache projects that I know/work on usual checks are: > > - try to build and run tests on the propostes source artifacts. > > Usually you should at least run the build on the source artifacts which > includes IT's ...something like: > > mvn -Prun-its clean verify for plugins and > for components: > > mvn clean verify > > > > - apache-rat/licensing issues > > Is already checked by the builds (see above).. > This may be wrong, if the build for some human error does not run rat anymore you won't see it, IMHO a human should review manually the voted artifacts. > > - check signatures/shasums.. > Usually compare the checksums in email with them which can be downloaded > from the staging repositories... > > > > - check proposed maven artifacts > > ?? In which way? > Try them, this seems simple to me, if the release manager sets up the staging repository on repository.apache.org, I think this is already in the guide > > > > Usually voters when the give their '+1' add an explanation about the > > tests the performed on the RC, I see this is not very common practice > > in Maven VOTE threads. > > Sometimes yes sometimes not...usually we don't do it if nothing has been > found...but if we find something than we do to find the itch.. > > > > > Second question, in Maven what is really 'released' ? > > Are you releasing the SOURCE ZIP ? or something else ? > > > As far as I know in Apache we are 'releasing' the source code and we > > are providing binaries for > > convenience to users. I understand that Maven is somehow a very special > case. > > Not really. The real releases are the source artifacts (*.zip)... > The binaries which are transfered to Central is as already mentioned > convenience... > > > Much to explain..that looks like we need to enhance the release > procedure description... > > > > > > My questions are just to understand better in order to give a more > > significant contribution to the project, I am pointing out problems. > > Yeah really great... > > Kind regards > Karl Heinz Marbaise > > > > Thank you all for carrying on Maven Project ! > > > > Cheers > > Enrico > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- -- Enrico Olivelli
Re: [maven-parent] 02/02: [maven-release-plugin] rollback the release of maven-parent-TEST-34
sorry, I completely did fail my tests, which should never had been pushed to
Apache master...
:(
Regards,
Hervé
Le dimanche 11 novembre 2018, 20:36:43 CET hbout...@apache.org a écrit :
> This is an automated email from the ASF dual-hosted git repository.
>
> hboutemy pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/maven-parent.git
>
> commit 9782eabad3cc07473924723d9ecfdc8b821b01a9
> Author: Hervé Boutemy
> AuthorDate: Sun Nov 11 20:36:40 2018 +0100
>
> [maven-release-plugin] rollback the release of maven-parent-TEST-34
> ---
> apache-resource-bundles/pom.xml | 2 +-
> doxia-tools/pom.xml | 2 +-
> maven-plugins/pom.xml | 2 +-
> maven-shared-components/pom.xml | 2 +-
> maven-skins/pom.xml | 2 +-
> pom.xml | 8
> 6 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/apache-resource-bundles/pom.xml
> b/apache-resource-bundles/pom.xml index cd3e116..cb4aa0d 100644
> --- a/apache-resource-bundles/pom.xml
> +++ b/apache-resource-bundles/pom.xml
> @@ -25,7 +25,7 @@
>
> org.apache.maven
> maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
> ../pom.xml
>
>
> diff --git a/doxia-tools/pom.xml b/doxia-tools/pom.xml
> index 7218ca9..145cd95 100644
> --- a/doxia-tools/pom.xml
> +++ b/doxia-tools/pom.xml
> @@ -25,7 +25,7 @@ under the License.
>
> org.apache.maven
> maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
> ../pom.xml
>
>
> diff --git a/maven-plugins/pom.xml b/maven-plugins/pom.xml
> index 8d1c687..b224c86 100644
> --- a/maven-plugins/pom.xml
> +++ b/maven-plugins/pom.xml
> @@ -24,7 +24,7 @@ under the License.
>
> org.apache.maven
> maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
> ../pom.xml
>
>
> diff --git a/maven-shared-components/pom.xml
> b/maven-shared-components/pom.xml index cfd3245..d96a5a5 100644
> --- a/maven-shared-components/pom.xml
> +++ b/maven-shared-components/pom.xml
> @@ -25,7 +25,7 @@ under the License.
>
> org.apache.maven
> maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
> ../pom.xml
>
>
> diff --git a/maven-skins/pom.xml b/maven-skins/pom.xml
> index fd0df50..1ec4d66 100644
> --- a/maven-skins/pom.xml
> +++ b/maven-skins/pom.xml
> @@ -25,7 +25,7 @@ under the License.
>
> org.apache.maven
> maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
> ../pom.xml
>
>
> diff --git a/pom.xml b/pom.xml
> index 19dd2f3..454f589 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -32,7 +32,7 @@ under the License.
>
>org.apache.maven
>maven-parent
> - TEST-35-SNAPSHOT
> + 34-SNAPSHOT
>pom
>
>Apache Maven
> @@ -847,9 +847,9 @@ under the License.
>
>
>
> -
> scm:git:https://github.com/hboutemy/maven-parent.git n> -
> scm:git:https://github.com/hboutemy/maven-parent.git developerConnection> -
> https://github.com/hboutemy/maven-parent/tree/${project.scm.tag}
> +
> scm:git:https://gitbox.apache.org/repos/asf/maven-parent.git onnection> +
> scm:git:https://gitbox.apache.org/repos/asf/maven-pare
> nt.git +
> https://github.com/apache/maven-parent/tree/${project.scm.tag}
> HEAD
>
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Shade Plugin version 3.2.1
+1 Regards, Hervé Le jeudi 8 novembre 2018, 06:25:21 CET Olivier Lamy a écrit : > Hi, > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344059&styl > eName=Text&projectId=12317921 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MSHADE/issues/MSHADE-259?filter=allo > penissues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1467 > https://repository.apache.org/content/repositories/maven-1467/org/apache/mav > en/plugins/maven-shade-plugin/3.2.1/maven-shade-plugin-3.2.1-source-release. > zip > > Source release checksum(s): > maven-shade-plugin-3.2.1-source-release.zip.sha512: > > 6916f93db460b6c8e87dcc10a9f12fe789bfb6c81f7f77365bdcfad9c2fb04139808ca6bf2d5 > 6d160de0d29a01393cb3cfd233cace88f83dc6db978c14bc3f86 > > Staging site: > https://maven.apache.org/plugins-archives/maven-shade-plugin-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-- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
