Re: core-integration-testing-maven-3-jdk-1.7 - Build # 1687 - Still Failing

2016-01-25 Thread Christian Schulte

Hi,

can someone take a look at that build node, please. Jenkins is currently 
sending out emails about failing ITs not failing locally here. I think 
the root cause for this is the following exception right at the start of 
the ITs. Setting -Djava.io.tmpdir to point to somewhere inside the 
workspace may help if that issue occurs repeatedly, so that the Jenkins 
UI can be used to try to delete that file.


java.io.IOException: File /tmp/bootstrap/stderr.log unable to be deleted.
	at 
org.apache.maven.shared.utils.io.FileUtils.forceDelete(FileUtils.java:1155)
	at 
org.apache.maven.shared.utils.io.FileUtils.cleanDirectory(FileUtils.java:1357)
	at 
org.apache.maven.shared.utils.io.FileUtils.deleteDirectory(FileUtils.java:1315)
	at 
org.apache.maven.it.util.ResourceExtractor.simpleExtractResources(ResourceExtractor.java:49)
	at 
org.apache.maven.it.MavenITBootstrapTest.testBootstrap(MavenITBootstrapTest.java:48)


Regards,
--
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Robert Scholte

Hi,

I really wonder why it is useful to add a skip-parameter to the packaging  
plugin? The goal for every Maven project is to end up with some (packaged)  
artifact, right?
A skip-parameter because a lot of other plugins have it as well is IMHO  
not a good reason, so what would be a valid usecase here?


thanks,
Robert

Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA)  
:




 [  
https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel  
]


Karl Heinz Marbaise closed MWAR-350.

Resolution: Fixed
  Assignee: Karl Heinz Marbaise

Fixed in [r1726671|http://svn.apache.org/r1726671]


Add Skip Parameter to Skip the process
--

Key: MWAR-350
URL: https://issues.apache.org/jira/browse/MWAR-350
Project: Maven WAR Plugin
 Issue Type: New Feature
   Affects Versions: 2.6
Environment: Maven 3.3.3
maven-war-plugin 2.6
   Reporter: Keshan De Silva
   Assignee: Karl Heinz Marbaise
   Priority: Trivial
Fix For: 3.0.0

Attachments: Maven_War_Skip.patch


* It will be usefull if maven-war plugin has a skip configuration as in  
most of the plugins have.

{code:xml}
org.apache.maven.plugins
maven-war-plugin
2.6

true

{code}
(I have attached a patch file)





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Aldrin Leal
There are cases where one could use a profile to build a custom assembly of
the war (say, like with jetty runner to run under a given paas), and
attaching just the relevant classes / assets, thus saving time.


--
-- Aldrin Leal,  / http://about.me/aldrinleal

On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte 
wrote:

> Hi,
>
> I really wonder why it is useful to add a skip-parameter to the packaging
> plugin? The goal for every Maven project is to end up with some (packaged)
> artifact, right?
> A skip-parameter because a lot of other plugins have it as well is IMHO
> not a good reason, so what would be a valid usecase here?
>
> thanks,
> Robert
>
> Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA) <
> j...@apache.org>:
>
>
>>  [
>> https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Karl Heinz Marbaise closed MWAR-350.
>> 
>> Resolution: Fixed
>>   Assignee: Karl Heinz Marbaise
>>
>> Fixed in [r1726671|http://svn.apache.org/r1726671]
>>
>> Add Skip Parameter to Skip the process
>>> --
>>>
>>> Key: MWAR-350
>>> URL: https://issues.apache.org/jira/browse/MWAR-350
>>> Project: Maven WAR Plugin
>>>  Issue Type: New Feature
>>>Affects Versions: 2.6
>>> Environment: Maven 3.3.3
>>> maven-war-plugin 2.6
>>>Reporter: Keshan De Silva
>>>Assignee: Karl Heinz Marbaise
>>>Priority: Trivial
>>> Fix For: 3.0.0
>>>
>>> Attachments: Maven_War_Skip.patch
>>>
>>>
>>> * It will be usefull if maven-war plugin has a skip configuration as in
>>> most of the plugins have.
>>> {code:xml}
>>> org.apache.maven.plugins
>>> maven-war-plugin
>>> 2.6
>>> 
>>> true
>>> 
>>> {code}
>>> (I have attached a patch file)
>>>
>>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread jieryn
UAT module which is war for easy overlay of the main WAR module but
without double-pushing your (fat) war into the upstream repository?

On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte  wrote:
> Hi,
>
> I really wonder why it is useful to add a skip-parameter to the packaging
> plugin? The goal for every Maven project is to end up with some (packaged)
> artifact, right?
> A skip-parameter because a lot of other plugins have it as well is IMHO not
> a good reason, so what would be a valid usecase here?
>
> thanks,
> Robert
>
> Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA)
> :
>
>>
>>  [
>> https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Karl Heinz Marbaise closed MWAR-350.
>> 
>> Resolution: Fixed
>>   Assignee: Karl Heinz Marbaise
>>
>> Fixed in [r1726671|http://svn.apache.org/r1726671]
>>
>>> Add Skip Parameter to Skip the process
>>> --
>>>
>>> Key: MWAR-350
>>> URL: https://issues.apache.org/jira/browse/MWAR-350
>>> Project: Maven WAR Plugin
>>>  Issue Type: New Feature
>>>Affects Versions: 2.6
>>> Environment: Maven 3.3.3
>>> maven-war-plugin 2.6
>>>Reporter: Keshan De Silva
>>>Assignee: Karl Heinz Marbaise
>>>Priority: Trivial
>>> Fix For: 3.0.0
>>>
>>> Attachments: Maven_War_Skip.patch
>>>
>>>
>>> * It will be usefull if maven-war plugin has a skip configuration as in
>>> most of the plugins have.
>>> {code:xml}
>>> org.apache.maven.plugins
>>> maven-war-plugin
>>> 2.6
>>> 
>>> true
>>> 
>>> {code}
>>> (I have attached a patch file)
>>>
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>
>
> -
> 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



Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Robert Scholte

Op Mon, 25 Jan 2016 20:55:09 +0100 schreef jieryn :


UAT module which is war for easy overlay of the main WAR module but
without double-pushing your (fat) war into the upstream repository?



Both install:install and deploy:deploy have skip parameters for that  
reason. AFAIK overlay still needs the war.


Robert


On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte   
wrote:

Hi,

I really wonder why it is useful to add a skip-parameter to the  
packaging
plugin? The goal for every Maven project is to end up with some  
(packaged)

artifact, right?
A skip-parameter because a lot of other plugins have it as well is IMHO  
not

a good reason, so what would be a valid usecase here?

thanks,
Robert

Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA)
:



 [
https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise closed MWAR-350.

Resolution: Fixed
  Assignee: Karl Heinz Marbaise

Fixed in [r1726671|http://svn.apache.org/r1726671]


Add Skip Parameter to Skip the process
--

Key: MWAR-350
URL: https://issues.apache.org/jira/browse/MWAR-350
Project: Maven WAR Plugin
 Issue Type: New Feature
   Affects Versions: 2.6
Environment: Maven 3.3.3
maven-war-plugin 2.6
   Reporter: Keshan De Silva
   Assignee: Karl Heinz Marbaise
   Priority: Trivial
Fix For: 3.0.0

Attachments: Maven_War_Skip.patch


* It will be usefull if maven-war plugin has a skip configuration as  
in

most of the plugins have.
{code:xml}
org.apache.maven.plugins
maven-war-plugin
2.6

true

{code}
(I have attached a patch file)





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)



-
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


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Robert Scholte
Op Mon, 25 Jan 2016 20:54:20 +0100 schreef Aldrin Leal  
:


There are cases where one could use a profile to build a custom assembly  
of

the war (say, like with jetty runner to run under a given paas), and
attaching just the relevant classes / assets, thus saving time.


Custom assembly profile, that sounds like abuse of profiles.
Be aware that we've decided some behavior of both the install and deploy  
plugins, see MavenProject with only attachments must have packaging "pom"  
[1][2].

It looks like here's an example which used to rely on that behavior.
Is the effect the same as 'mvn compile jetty:run'?

thanks,
Robert

[1] https://issues.apache.org/jira/browse/MINSTALL-118
[2] https://issues.apache.org/jira/browse/MDEPLOY-205




--
-- Aldrin Leal,  / http://about.me/aldrinleal

On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte 
wrote:


Hi,

I really wonder why it is useful to add a skip-parameter to the  
packaging
plugin? The goal for every Maven project is to end up with some  
(packaged)

artifact, right?
A skip-parameter because a lot of other plugins have it as well is IMHO
not a good reason, so what would be a valid usecase here?

thanks,
Robert

Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA) <
j...@apache.org>:



 [
https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise closed MWAR-350.

Resolution: Fixed
  Assignee: Karl Heinz Marbaise

Fixed in [r1726671|http://svn.apache.org/r1726671]

Add Skip Parameter to Skip the process

--

Key: MWAR-350
URL: https://issues.apache.org/jira/browse/MWAR-350
Project: Maven WAR Plugin
 Issue Type: New Feature
   Affects Versions: 2.6
Environment: Maven 3.3.3
maven-war-plugin 2.6
   Reporter: Keshan De Silva
   Assignee: Karl Heinz Marbaise
   Priority: Trivial
Fix For: 3.0.0

Attachments: Maven_War_Skip.patch


* It will be usefull if maven-war plugin has a skip configuration as  
in

most of the plugins have.
{code:xml}
org.apache.maven.plugins
maven-war-plugin
2.6

true

{code}
(I have attached a patch file)





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)



-
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 pull request: MNG-3092: Adds version range result filter beh...

2016-01-25 Thread michael-o
Github user michael-o commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-174656884
  
Can we make any progress here?


---
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



[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2016-01-25 Thread michael-o
Github user michael-o commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-174671286
  
This is what I have expected you to say ;-)
@barthel or anyone else, can you craft up an IT for that?


---
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



Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Romain Manni-Bucau
2016-01-25 21:39 GMT+01:00 Robert Scholte :

> Op Mon, 25 Jan 2016 21:05:58 +0100 schreef Romain Manni-Bucau <
> rmannibu...@gmail.com>:
>
> Nothing prevents to build 2 or more wars with slightly different resources.
>> Being able to skip one would be useful.
>>
>
> That should mean different artifactIds (and groupIds or versions?), so
> different projects/modules. And you always have the option to decide which
> modules to build.
>
>
having several modules for that is most of the time overkill or enforce to
use overlays which are slow and can be avoided. Builderhelper plugin is a
better approach most of the time.


> I think that for every example where people want to skip the packaging of
> an artifact, we have (or should have) a better pattern to accomplish that.
>
>
And if you consider maven-war-plugin as a real plugin and not the packaging
of your pom - which is already doable today?


> thanks,
> Robert
>
>
> Le 25 janv. 2016 20:58, "Robert Scholte"  a écrit :
>>
>> Op Mon, 25 Jan 2016 20:55:09 +0100 schreef jieryn :
>>>
>>> UAT module which is war for easy overlay of the main WAR module but
>>>
 without double-pushing your (fat) war into the upstream repository?


 Both install:install and deploy:deploy have skip parameters for that
>>> reason. AFAIK overlay still needs the war.
>>>
>>> Robert
>>>
>>>
>>> On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte 
>>>
 wrote:

 Hi,
>
> I really wonder why it is useful to add a skip-parameter to the
> packaging
> plugin? The goal for every Maven project is to end up with some
> (packaged)
> artifact, right?
> A skip-parameter because a lot of other plugins have it as well is IMHO
> not
> a good reason, so what would be a valid usecase here?
>
> thanks,
> Robert
>
> Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA)
> :
>
>
>  [
>>
>>
>> https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Karl Heinz Marbaise closed MWAR-350.
>> 
>> Resolution: Fixed
>>   Assignee: Karl Heinz Marbaise
>>
>> Fixed in [r1726671|http://svn.apache.org/r1726671]
>>
>> Add Skip Parameter to Skip the process
>>
>>> --
>>>
>>> Key: MWAR-350
>>> URL: https://issues.apache.org/jira/browse/MWAR-350
>>> Project: Maven WAR Plugin
>>>  Issue Type: New Feature
>>>Affects Versions: 2.6
>>> Environment: Maven 3.3.3
>>> maven-war-plugin 2.6
>>>Reporter: Keshan De Silva
>>>Assignee: Karl Heinz Marbaise
>>>Priority: Trivial
>>> Fix For: 3.0.0
>>>
>>> Attachments: Maven_War_Skip.patch
>>>
>>>
>>> * It will be usefull if maven-war plugin has a skip configuration as
>>> in
>>> most of the plugins have.
>>> {code:xml}
>>> org.apache.maven.plugins
>>> maven-war-plugin
>>> 2.6
>>> 
>>> true
>>> 
>>> {code}
>>> (I have attached a patch file)
>>>
>>>
>>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>
>>
>
> -
> 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


>>> -
>>> 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 pull request: MNG-3092: Adds version range result filter beh...

2016-01-25 Thread michael-o
Github user michael-o commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-174666838
  
@jvanzyl There are unit tests in the commit. Isn't that enough? Otherwise, 
I'd ask @barthel for it.


---
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



[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2016-01-25 Thread jvanzyl
Github user jvanzyl commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-174668942
  
For a feature like that there should be an integration test as well.


---
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



Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Michael Osipov

Am 2016-01-25 um 20:51 schrieb Robert Scholte:

Hi,

I really wonder why it is useful to add a skip-parameter to the
packaging plugin? The goal for every Maven project is to end up with
some (packaged) artifact, right?
A skip-parameter because a lot of other plugins have it as well is IMHO
not a good reason, so what would be a valid usecase here?


Building WAR files are a constant problem. I do have them myself.

Consider you have a WAR project you are using to develop within Eclipse. 
Now you need a different one for every deployment site/configuration. 
Only few files are different but you need separate WAR files. How to 
solve this?


They are obviously several ways and all have issues. The reporter of 
MWAR-350 tries to solve it.


We should probably create a documentation site which describes how to 
solve this problem. I have currently three different ways and none of 
them satisfy me.


Michael



Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA)
:



 [
https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise closed MWAR-350.

Resolution: Fixed
  Assignee: Karl Heinz Marbaise

Fixed in [r1726671|http://svn.apache.org/r1726671]


Add Skip Parameter to Skip the process
--

Key: MWAR-350
URL: https://issues.apache.org/jira/browse/MWAR-350
Project: Maven WAR Plugin
 Issue Type: New Feature
   Affects Versions: 2.6
Environment: Maven 3.3.3
maven-war-plugin 2.6
   Reporter: Keshan De Silva
   Assignee: Karl Heinz Marbaise
   Priority: Trivial
Fix For: 3.0.0

Attachments: Maven_War_Skip.patch


* It will be usefull if maven-war plugin has a skip configuration as
in most of the plugins have.
{code:xml}
org.apache.maven.plugins
maven-war-plugin
2.6

true

{code}
(I have attached a patch file)





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


-
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 pull request: MNG-3092: Adds version range result filter beh...

2016-01-25 Thread pSub
Github user pSub commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-174664718
  
I would appreciate a merge, too.


---
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



[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2016-01-25 Thread jvanzyl
Github user jvanzyl commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-174664828
  
If there are integration tests don't wait for me. 


---
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



[GitHub] maven-archetype pull request: Add properties to enable or disable ...

2016-01-25 Thread manouti
GitHub user manouti opened a pull request:

https://github.com/apache/maven-archetype/pull/9

Add properties to enable or disable generation of submodules.

By setting -DgenerateEnableProperties=true when calling the 
create-from-project goal, the plugin would create enabler properties for each 
child module in the form generate.module.X. When calling the generate goal 
thereafter, one can exclude a module by passing -Dgenerate.module.X=false.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/manouti/maven-archetype master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-archetype/pull/9.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 #9


commit 4eef51a828dd78a03ff3444d52502cadcf0c2b39
Author: manouti 
Date:   2016-01-25T22:01:16Z

Update DefaultArchetypeFactory.java

commit 8a3d43a87fd593ca26dbec037f06682b7d5587e8
Author: manouti 
Date:   2016-01-25T22:05:22Z

Update DefaultFilesetArchetypeGenerator.java

Add properties to enable/disable the generation of specific modules.

commit 38bea519c95bc194f03643c45e21502797418aaa
Author: manouti 
Date:   2016-01-25T22:06:20Z

Update FilesetArchetypeCreator.java

Add properties to enable/disable the generation of specific modules.

commit 69ee6e450847761729290921b391d6cff9e7043e
Author: manouti 
Date:   2016-01-25T22:10:10Z

Update Constants.java

Add properties to enable/disable the generation of specific modules.

commit a995f2930b751d1ef5d12e33b1319bf26d61bdeb
Author: manouti 
Date:   2016-01-25T22:12:03Z

Update CreateArchetypeFromProjectMojo.java

Add properties to enable/disable the generation of specific modules.

commit 94f044e73b970fdad4ad0dcd6032d0eecfbb2da7
Author: manouti 
Date:   2016-01-25T22:12:58Z

Update ArchetypeCreationRequest.java

Add properties to enable/disable the generation of specific modules.

commit 927d1c237c39629bcc5a66d0c809d462d5240a2d
Author: manouti 
Date:   2016-01-25T22:16:26Z

Update archetype-descriptor.mdo

Add properties to enable/disable the generation of specific modules.

commit 275527431b5636e2793fa9110f3d8f4fb2745abc
Author: manouti 
Date:   2016-01-25T22:22:38Z

Merge pull request #1 from manouti/manouti-module-enabler

Module enabler




---
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



Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Romain Manni-Bucau
Nothing prevents to build 2 or more wars with slightly different resources.
Being able to skip one would be useful.
Le 25 janv. 2016 20:58, "Robert Scholte"  a écrit :

> Op Mon, 25 Jan 2016 20:55:09 +0100 schreef jieryn :
>
> UAT module which is war for easy overlay of the main WAR module but
>> without double-pushing your (fat) war into the upstream repository?
>>
>>
> Both install:install and deploy:deploy have skip parameters for that
> reason. AFAIK overlay still needs the war.
>
> Robert
>
>
> On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte 
>> wrote:
>>
>>> Hi,
>>>
>>> I really wonder why it is useful to add a skip-parameter to the packaging
>>> plugin? The goal for every Maven project is to end up with some
>>> (packaged)
>>> artifact, right?
>>> A skip-parameter because a lot of other plugins have it as well is IMHO
>>> not
>>> a good reason, so what would be a valid usecase here?
>>>
>>> thanks,
>>> Robert
>>>
>>> Op Mon, 25 Jan 2016 20:28:39 +0100 schreef Karl Heinz Marbaise (JIRA)
>>> :
>>>
>>>
  [

 https://issues.apache.org/jira/browse/MWAR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

 Karl Heinz Marbaise closed MWAR-350.
 
 Resolution: Fixed
   Assignee: Karl Heinz Marbaise

 Fixed in [r1726671|http://svn.apache.org/r1726671]

 Add Skip Parameter to Skip the process
> --
>
> Key: MWAR-350
> URL: https://issues.apache.org/jira/browse/MWAR-350
> Project: Maven WAR Plugin
>  Issue Type: New Feature
>Affects Versions: 2.6
> Environment: Maven 3.3.3
> maven-war-plugin 2.6
>Reporter: Keshan De Silva
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: Maven_War_Skip.patch
>
>
> * It will be usefull if maven-war plugin has a skip configuration as in
> most of the plugins have.
> {code:xml}
> org.apache.maven.plugins
> maven-war-plugin
> 2.6
> 
> true
> 
> {code}
> (I have attached a patch file)
>
>


 --
 This message was sent by Atlassian JIRA
 (v6.3.4#6332)

>>>
>>>
>>> -
>>> 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
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [jira] [Closed] (MWAR-350) Add Skip Parameter to Skip the process

2016-01-25 Thread Christopher
On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte  wrote:
> Hi,
>
> I really wonder why it is useful to add a skip-parameter to the packaging
> plugin? The goal for every Maven project is to end up with some (packaged)
> artifact, right?
> A skip-parameter because a lot of other plugins have it as well is IMHO not
> a good reason, so what would be a valid usecase here?
>

I would argue that it's useful to be able to skip over arbitrary
plugins, regardless of what they do, simply for testing other parts of
the build.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] maven-plugins pull request: [MPMD-219] PMD processing errors shoul...

2016-01-25 Thread adangel
GitHub user adangel opened a pull request:

https://github.com/apache/maven-plugins/pull/80

[MPMD-219] PMD processing errors should fail build (skipPmdError=false)

This commit adds a "PmdCollectingRenderer" and uses it instead of
the report listener, as listeners are unfortunately not informed about
errors.
If the "skipPmdError" property is true (default),
then these processing errors are logged as warnings.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/adangel/maven-plugins MPMD-219

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/80.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 #80


commit d9c298f27c54c7f215fe58a78d87e1519d4dff1c
Author: Andreas Dangel 
Date:   2016-01-25T11:49:33Z

[MPMD-219] PMD processing errors should fail build (skipPmdError=false)
This commit adds a "PmdCollectingRenderer" and uses it instead of
the report listener, as listeners are unfortunately not informed about
errors.
If the "skipPmdError" property is true (default),
then these processing errors are logged as warnings.




---
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