Op Tue, 26 Jan 2016 14:29:15 +0100 schreef Paul Benedict
:
I'm more curious of the growth of "skip" parameters of plugins. Do they
exist really to skip the plugin, or are they really representative of the
desire to skip an entire phase?
On Jan 25, 2016 7:24 PM, "Christopher" wrote:
I'm cur
On Tue, Jan 26, 2016 at 8:29 AM Paul Benedict wrote:
> I'm more curious of the growth of "skip" parameters of plugins. Do they
> exist really to skip the plugin, or are they really representative of the
> desire to skip an entire phase?
>
> [snip]
I frequently disable a subset of plugins which r
Am 2016-01-26 um 12:05 schrieb Adrien Rivard:
Hi,
My opinon on that is that you do not need to build actual wars(neither jar
btw) at all when you are developping within Eclipse.
Jetty and tomcat can run on exploded was strucure, and most others servers
have some eclipse tooling.
With a combina
I'm more curious of the growth of "skip" parameters of plugins. Do they
exist really to skip the plugin, or are they really representative of the
desire to skip an entire phase?
On Jan 25, 2016 7:24 PM, "Christopher" wrote:
> On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte
> wrote:
> > Hi,
> >
>
Hi,
My opinon on that is that you do not need to build actual wars(neither jar
btw) at all when you are developping within Eclipse.
Jetty and tomcat can run on exploded was strucure, and most others servers
have some eclipse tooling.
With a combination of eclipse configuration mecanism,(launch c
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 we
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 g
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 artif
Op Mon, 25 Jan 2016 21:05:58 +0100 schreef Romain Manni-Bucau
:
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 a
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,
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
>> w
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
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, Rober
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
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 useca
15 matches
Mail list logo
