I suspect you have set up your profiles so that they are exclusive, or to
put it another way, activating profile2 will revert the changes in profile1
and profile2 is later in the pom so wins out.
what you could do is cheat the reactor.
Maven will execute goals and phases against each module in tu
This does not seem to do the job.
It only seems to run the second profile.
Any other ideas?
On Fri, Sep 13, 2013 at 2:23 PM, Baptiste Mathus wrote:
> Try -Pprofile1,profile2
> Le 13 sept. 2013 14:16, "Philippe Cambien" a
> écrit :
>
> I tried it with maven clean install -Pprofile1 -Pprofile2
Try -Pprofile1,profile2
Le 13 sept. 2013 14:16, "Philippe Cambien" a
écrit :
> I tried it with maven clean install -Pprofile1 -Pprofile2 but he didn't
> seem to run the first profile.
>
>
> On Fri, Sep 13, 2013 at 2:15 PM, Baptiste Mathus wrote:
>
>> Can't you just activate both profiles in a go?
I tried it with maven clean install -Pprofile1 -Pprofile2 but he didn't
seem to run the first profile.
On Fri, Sep 13, 2013 at 2:15 PM, Baptiste Mathus wrote:
> Can't you just activate both profiles in a go?
> Le 13 sept. 2013 10:07, "Philippe Cambien" a
> écrit :
>
>> Hello,
>>
>> We have a
Can't you just activate both profiles in a go?
Le 13 sept. 2013 10:07, "Philippe Cambien" a
écrit :
> Hello,
>
> We have a Maven profile which contains a lot of long tests.
> Before we run these tests, we want to make sure that all dependencies are
> met ie. all systems are up and running.
> How
Hello,
We have a Maven profile which contains a lot of long tests.
Before we run these tests, we want to make sure that all dependencies are
met ie. all systems are up and running.
How can I configure a single job to run a Maven profile first and then the
main profile?
The main profile shouldn't s
