You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Carlos Rovira <ca...@apache.org> on 2018/04/21 06:31:43 UTC
Fwd: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
Hi,
seems this commit is making the build fail
*Commit 38553fd81db44b72e8debae1669950fc30a0ee9b by carlosrovira
<https://builds.apache.org/user/carlosrovira/>*
make maven use latest version of maven-war-plugin (currently 3.2.0)
don't know why, since maven build works localy :?
I could revert it since I think that change really was not impact in what
made AMF to work again, was just one of the steps to get it, but seems not
good when we can't upgrade plugins to latest versions due to Jenkins
failing cause of it.
---------- Forwarded message ----------
From: Apache Jenkins Server <je...@builds.apache.org>
Date: 2018-04-21 0:43 GMT+02:00
Subject: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
To: harbs@in-tools.com, carlosrovira@apache.org, aharui@apache.org,
pent@apache.org, commits@royale.apache.org
The Apache Jenkins build system has built Royale-asjs (build #661)
Status: Still Failing
Check console output at https://builds.apache.org/job/Royale-asjs/661/ to
view the results.
--
Carlos Rovira
http://about.me/carlosrovira
Re: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
will try to see now how I can reconnect while maintain the actual output
and see if that fix the build
thanks for guessing what could be the problems
2018-04-22 8:09 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
> My interpretation of the build output is that disconnecting from the
> parent pom caused the build to break because now sampleamfwebapp doesn't
> know where to deploy the artifacts. The Maven CI build runs the deploy
> target. It used to pick up the snapshot server from the main pom, but now
> it won't. I also expect when we do a release that the disconnected parent
> pom will mean that the version numbers in sampleamfwebapp may not get
> updated by Maven release tools
>
> HTH,
> -Alex
>
> On 4/20/18, 11:46 PM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org>
> wrote:
>
> This was first try before detaching from parent pom, that was that
> really
> fix mainly the problem. But another thing that scares me is that
> maven-war-plugin actual version (2.6.0) is get from some transitive
> dependency we have...
>
> About disconnecting from the parent pom, we should revisit it at a
> later
> time to wire it again, but as we have time. I prefer the way we had
> before.
>
>
> 2018-04-21 8:38 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
>
> > I was thinking it was another commit where you commented out the
> parent
> > pom. I think there is some dependencyManagement settings in an
> upper pom
> > that now need to be copied to the sampleamfwebapp pom since there is
> no
> > longer a parent relationship.
> >
> > -Alex
> >
> > On 4/20/18, 11:32 PM, "carlos.rovira@gmail.com on behalf of Carlos
> > Rovira" <carlos.rovira@gmail.com on behalf of
> carlosrovira@apache.org>
> > wrote:
> >
> > Hi,
> >
> > seems this commit is making the build fail
> >
> > *Commit 38553fd81db44b72e8debae1669950fc30a0ee9b by carlosrovira
> > <https://na01.safelinks.protection.outlook.com/?url=
> > https%3A%2F%2Fbuilds.apache.org%2Fuser%2Fcarlosrovira%2F&
> > data=02%7C01%7Caharui%40adobe.com%7C0f425d1bcbef403d2ea108d5a751
> 9c02%
> > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636598891379545572&sdata=
> > OoYNa7NybAJ0i3kaRGraCJGokas5C6UE9cT6TlIDimI%3D&reserved=0>*
> >
> > make maven use latest version of maven-war-plugin (currently
> 3.2.0)
> >
> >
> > don't know why, since maven build works localy :?
> >
> > I could revert it since I think that change really was not
> impact in
> > what
> > made AMF to work again, was just one of the steps to get it, but
> seems
> > not
> > good when we can't upgrade plugins to latest versions due to
> Jenkins
> > failing cause of it.
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: Apache Jenkins Server <je...@builds.apache.org>
> > Date: 2018-04-21 0:43 GMT+02:00
> > Subject: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
> > To: harbs@in-tools.com, carlosrovira@apache.org,
> aharui@apache.org,
> > pent@apache.org, commits@royale.apache.org
> >
> >
> > The Apache Jenkins build system has built Royale-asjs (build
> #661)
> >
> > Status: Still Failing
> >
> > Check console output at https://na01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
> data=02%7C01%7Caharui%40adobe.com%7C681b5d5d425340b2b1be08d5a7538b53%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598899681397993&sdata=
> Daq7LM4tDkcalcmNtOOo2FOWmzwsXzJuTcNVnJdaJEo%3D&reserved=0.
> > protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.
> > org%2Fjob%2FRoyale-asjs%2F661%2F&data=02%7C01%7Caharui%40adobe.com%
> > 7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636598891379545572&sdata=0gYGuDvbuD5ROTeol%
> > 2FBQXaXOAxBeL%2BgDugnqqIh9XxQ%3D&reserved=0 to
> > view the results.
> >
> >
> >
> > --
> > Carlos Rovira
> > https://na01.safelinks.protection.outlook.com/?url=
> > http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%
> 40adobe.com%
> > 7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636598891379545572&sdata=
> Rz7ikCQqKkHcVAefxgWqQ2zHrk65vC
> > EgRD52ViZquFg%3D&reserved=0
> >
> >
> >
>
>
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> 7C681b5d5d425340b2b1be08d5a7538b53%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636598899681397993&sdata=xLKVMCsCIS6EdY5F6Afac9drpWd%
> 2B5smrdNqtj7XLMuQ%3D&reserved=0
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
Posted by Alex Harui <ah...@adobe.com.INVALID>.
My interpretation of the build output is that disconnecting from the parent pom caused the build to break because now sampleamfwebapp doesn't know where to deploy the artifacts. The Maven CI build runs the deploy target. It used to pick up the snapshot server from the main pom, but now it won't. I also expect when we do a release that the disconnected parent pom will mean that the version numbers in sampleamfwebapp may not get updated by Maven release tools
HTH,
-Alex
On 4/20/18, 11:46 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira" <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
This was first try before detaching from parent pom, that was that really
fix mainly the problem. But another thing that scares me is that
maven-war-plugin actual version (2.6.0) is get from some transitive
dependency we have...
About disconnecting from the parent pom, we should revisit it at a later
time to wire it again, but as we have time. I prefer the way we had before.
2018-04-21 8:38 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
> I was thinking it was another commit where you commented out the parent
> pom. I think there is some dependencyManagement settings in an upper pom
> that now need to be copied to the sampleamfwebapp pom since there is no
> longer a parent relationship.
>
> -Alex
>
> On 4/20/18, 11:32 PM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org>
> wrote:
>
> Hi,
>
> seems this commit is making the build fail
>
> *Commit 38553fd81db44b72e8debae1669950fc30a0ee9b by carlosrovira
> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fbuilds.apache.org%2Fuser%2Fcarlosrovira%2F&
> data=02%7C01%7Caharui%40adobe.com%7C0f425d1bcbef403d2ea108d5a7519c02%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598891379545572&sdata=
> OoYNa7NybAJ0i3kaRGraCJGokas5C6UE9cT6TlIDimI%3D&reserved=0>*
>
> make maven use latest version of maven-war-plugin (currently 3.2.0)
>
>
> don't know why, since maven build works localy :?
>
> I could revert it since I think that change really was not impact in
> what
> made AMF to work again, was just one of the steps to get it, but seems
> not
> good when we can't upgrade plugins to latest versions due to Jenkins
> failing cause of it.
>
>
>
> ---------- Forwarded message ----------
> From: Apache Jenkins Server <je...@builds.apache.org>
> Date: 2018-04-21 0:43 GMT+02:00
> Subject: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
> To: harbs@in-tools.com, carlosrovira@apache.org, aharui@apache.org,
> pent@apache.org, commits@royale.apache.org
>
>
> The Apache Jenkins build system has built Royale-asjs (build #661)
>
> Status: Still Failing
>
> Check console output at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&data=02%7C01%7Caharui%40adobe.com%7C681b5d5d425340b2b1be08d5a7538b53%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598899681397993&sdata=Daq7LM4tDkcalcmNtOOo2FOWmzwsXzJuTcNVnJdaJEo%3D&reserved=0.
> protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.
> org%2Fjob%2FRoyale-asjs%2F661%2F&data=02%7C01%7Caharui%40adobe.com%
> 7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636598891379545572&sdata=0gYGuDvbuD5ROTeol%
> 2FBQXaXOAxBeL%2BgDugnqqIh9XxQ%3D&reserved=0 to
> view the results.
>
>
>
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> 7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636598891379545572&sdata=Rz7ikCQqKkHcVAefxgWqQ2zHrk65vC
> EgRD52ViZquFg%3D&reserved=0
>
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C681b5d5d425340b2b1be08d5a7538b53%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598899681397993&sdata=xLKVMCsCIS6EdY5F6Afac9drpWd%2B5smrdNqtj7XLMuQ%3D&reserved=0
Re: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
Posted by Carlos Rovira <ca...@apache.org>.
This was first try before detaching from parent pom, that was that really
fix mainly the problem. But another thing that scares me is that
maven-war-plugin actual version (2.6.0) is get from some transitive
dependency we have...
About disconnecting from the parent pom, we should revisit it at a later
time to wire it again, but as we have time. I prefer the way we had before.
2018-04-21 8:38 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
> I was thinking it was another commit where you commented out the parent
> pom. I think there is some dependencyManagement settings in an upper pom
> that now need to be copied to the sampleamfwebapp pom since there is no
> longer a parent relationship.
>
> -Alex
>
> On 4/20/18, 11:32 PM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org>
> wrote:
>
> Hi,
>
> seems this commit is making the build fail
>
> *Commit 38553fd81db44b72e8debae1669950fc30a0ee9b by carlosrovira
> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fbuilds.apache.org%2Fuser%2Fcarlosrovira%2F&
> data=02%7C01%7Caharui%40adobe.com%7C0f425d1bcbef403d2ea108d5a7519c02%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598891379545572&sdata=
> OoYNa7NybAJ0i3kaRGraCJGokas5C6UE9cT6TlIDimI%3D&reserved=0>*
>
> make maven use latest version of maven-war-plugin (currently 3.2.0)
>
>
> don't know why, since maven build works localy :?
>
> I could revert it since I think that change really was not impact in
> what
> made AMF to work again, was just one of the steps to get it, but seems
> not
> good when we can't upgrade plugins to latest versions due to Jenkins
> failing cause of it.
>
>
>
> ---------- Forwarded message ----------
> From: Apache Jenkins Server <je...@builds.apache.org>
> Date: 2018-04-21 0:43 GMT+02:00
> Subject: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
> To: harbs@in-tools.com, carlosrovira@apache.org, aharui@apache.org,
> pent@apache.org, commits@royale.apache.org
>
>
> The Apache Jenkins build system has built Royale-asjs (build #661)
>
> Status: Still Failing
>
> Check console output at https://na01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.
> org%2Fjob%2FRoyale-asjs%2F661%2F&data=02%7C01%7Caharui%40adobe.com%
> 7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636598891379545572&sdata=0gYGuDvbuD5ROTeol%
> 2FBQXaXOAxBeL%2BgDugnqqIh9XxQ%3D&reserved=0 to
> view the results.
>
>
>
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> 7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636598891379545572&sdata=Rz7ikCQqKkHcVAefxgWqQ2zHrk65vC
> EgRD52ViZquFg%3D&reserved=0
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I was thinking it was another commit where you commented out the parent pom. I think there is some dependencyManagement settings in an upper pom that now need to be copied to the sampleamfwebapp pom since there is no longer a parent relationship.
-Alex
On 4/20/18, 11:32 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira" <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
Hi,
seems this commit is making the build fail
*Commit 38553fd81db44b72e8debae1669950fc30a0ee9b by carlosrovira
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fuser%2Fcarlosrovira%2F&data=02%7C01%7Caharui%40adobe.com%7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598891379545572&sdata=OoYNa7NybAJ0i3kaRGraCJGokas5C6UE9cT6TlIDimI%3D&reserved=0>*
make maven use latest version of maven-war-plugin (currently 3.2.0)
don't know why, since maven build works localy :?
I could revert it since I think that change really was not impact in what
made AMF to work again, was just one of the steps to get it, but seems not
good when we can't upgrade plugins to latest versions due to Jenkins
failing cause of it.
---------- Forwarded message ----------
From: Apache Jenkins Server <je...@builds.apache.org>
Date: 2018-04-21 0:43 GMT+02:00
Subject: [MAVEN-BUILD] Royale-asjs - Build # 661 - Still Failing
To: harbs@in-tools.com, carlosrovira@apache.org, aharui@apache.org,
pent@apache.org, commits@royale.apache.org
The Apache Jenkins build system has built Royale-asjs (build #661)
Status: Still Failing
Check console output at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-asjs%2F661%2F&data=02%7C01%7Caharui%40adobe.com%7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598891379545572&sdata=0gYGuDvbuD5ROTeol%2FBQXaXOAxBeL%2BgDugnqqIh9XxQ%3D&reserved=0 to
view the results.
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C0f425d1bcbef403d2ea108d5a7519c02%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636598891379545572&sdata=Rz7ikCQqKkHcVAefxgWqQ2zHrk65vCEgRD52ViZquFg%3D&reserved=0