Re: [ANN] Apache Maven Shade Plugin 2.4.3 Released

Tibor, you should rather add the plain text release notes. The HTML junk is unreadible now. Michael > Hi, > > The Apache Maven team is pleased to announce the release of the Apache > Maven Shade Plugin, version 2.4.3 > > The release contains 4 bug fixes. > Again we received contributions

Maven extensions

there are discussions lately on extensions, with 2 different meanings on this: - either *project* extensions, with the .mvn feature added in Maven 3.3.0 - or more generic extension, like classical *installation* extensions jars in ${maven.home}/lib/ext/ as configured in

[GitHub] maven-surefire pull request: Adding individual rerun times to XML ...

Github user lamyaa commented on the pull request: https://github.com/apache/maven-surefire/pull/96#issuecomment-170758490 @Tibor17 I merged the latest changes from master and resolved conflicts. I checked that it is still working as expected. Let me know if there is anything else I

Re: [ANN] Apache Maven Shade Plugin 2.4.3 Released

> I know but it has been done always this way, especially I adapted to this > style what I have seen on PMC members ??? AFAIK, announcements are always sent as text (see announce archive [1]), and that's the meaning of "(Copy Here Release Notes in Text Format from JIRA)" Looking at your

Re: Maven extensions

installation level need to point to user space, in a per-user location (~, or ${user.home} if you prefer this syntax): then the user space is filled or not, user per user multi-user installation is exactly the target use: with this user extensions feature, each user can customize its own

Re: Maven extensions

+1 Le mardi 12 janvier 2016, Hervé BOUTEMY a écrit : > there are discussions lately on extensions, with 2 different meanings on > this: > > - either *project* extensions, with the .mvn feature added in Maven 3.3.0 > > - or more generic extension, like classical

Re: Maven extensions

> > Then I think we are missing *user* extensions, that would be added in > ${maven.home}/bin/m2.conf the same way as installation extensions, but > pointing to ~/.m2/ext/*.jar > What would the benefit be of configuring this on installation level but keep the jar in user space? How would that

Re: [DISCUSS] MDEPLOY-205: MavenProject with only attachments must have packaging "pom"

this might be the root cause: MINSTALL-41 [1]: I have a project wich I need to build only specifying a classifier (in detail: a war project which I need to build with different profiles to include different configurations. So I set up different filters and the package produces different

Re: [ANN] Apache Maven Shade Plugin 2.4.3 Released

I know but it has been done always this way, especially I adapted to this style what I have seen on PMC members, but I am open for human readable text of course. Do we need to change something in release process or to Vote for this change, or just send it since now like Michael has proposed? In