MNGSITE-167 - reopen, with patch?

2016-01-12 Thread Dan Rollo
I just attached a patch to the recently “auto closed" issue: MNGSITE-167 MNGSITE-167 Can that issue be reopened, and ideally, the doc patch applied? Thanks, Dan

[GitHub] maven-plugins pull request: [MSHADE-182] Service file should be re...

2016-01-12 Thread KostyaSha
GitHub user KostyaSha opened a pull request: https://github.com/apache/maven-plugins/pull/79 [MSHADE-182] Service file should be relocated. Fixes issue when service file content is relocated, but file itself didn't. Patch content provided by some person in jira ticket. You can m

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

2016-01-12 Thread Robert Scholte
Hi all, thanks for the support, the message is clear. I'll continue with the implementation. Robert Op Sat, 09 Jan 2016 18:04:40 +0100 schreef Robert Scholte : Hi, I've created MDEPLOY-205: MavenProject with only attachments must have packaging "pom"[1] If I apply such a change, tests

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

2016-01-12 Thread Arnaud Héritier
+1 On Tue, Jan 12, 2016 at 8:25 PM, Bing Shiao wrote: > +1 > On Jan 12, 2016 11:05 AM, "Dennis Lundberg" > wrote: > > > +1 > > Den 11 jan 2016 22:37 skrev "Robert Scholte" : > > > > > this might be the root cause: > > > > > > MINSTALL-41 [1]: > > > I have a project wich I need to build only spe

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

2016-01-12 Thread Bing Shiao
+1 On Jan 12, 2016 11:05 AM, "Dennis Lundberg" wrote: > +1 > Den 11 jan 2016 22:37 skrev "Robert Scholte" : > > > 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

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

2016-01-12 Thread Dennis Lundberg
+1 Den 11 jan 2016 22:37 skrev "Robert Scholte" : > 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 u

Re: Maven extensions

2016-01-12 Thread Jason van Zyl
User extensions could be used for something like logging maybe and that would be fine. User extensions that may knock out project extensions that are required to build are is an issue. A user installs a extension to colour the log output, so what. But the first binding discovered is what works,

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

2016-01-12 Thread Stephen Connolly
+1 On 11 January 2016 at 21:37, Robert Scholte wrote: > 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

Re: Maven extensions

2016-01-12 Thread Tamás Cservenák
+0 in general, but I think we should first check how multiple extensions will/may work, and see, what actually, was the original intention of extensions. We might miss some important reasons to NOT do this (maybe due to some technical reason?) For example, I use Takari smart builder, Takari concur

Re: Maven extensions

2016-01-12 Thread Stephen Connolly
+1 On Tuesday 12 January 2016, Hervé BOUTEMY wrote: > 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 thi