You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Alessio Soldano <as...@redhat.com> on 2013/01/25 09:34:39 UTC
2.7.x snapshots and JAXWS 2.2
Hi,
I've just noticed that the latest built 2.7.3-SNAPSHOT artifacts have
not been built using "jaxws22" maven profile. I assume that's a simply
oversight happened when the cxf-2.7-deploy Jenkins job was created at
the time we moved the trunk to 2.8.
I think I've fixed the cxf-2.7-deploy job now (by adding the "jaxws22"
profile in its configuration), results will soon be available... ;-)
Is the jenkins configuration stored anywhere on source control so that I
can persist the changes (if the results are good) ?
Thanks
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
Re: 2.7.x snapshots and JAXWS 2.2
Posted by Daniel Kulp <dk...@apache.org>.
On Jan 25, 2013, at 12:41 PM, Alessio Soldano <as...@redhat.com> wrote:
> On 01/25/2013 06:24 PM, Daniel Kulp wrote:
>>>
>>> Have the 2.7.x snapshots ever been jaxws22? My gut feeling is when we updated from Java5 (used for <=2.6) to Java6, we didn't add the jaxws22 flag. With <=2.6.x, jaxws22 would be the default when using Java5 (since we don't need to deal with the endorsed crap) so we may not have specified the jaxws22 profile. Once we moved to 2.6, we likely needed to add the profile, but forgot.
>>
>> Actually, never mind. When I setup the 2.7.x branch, I copied the 2.6.x-deploy Jenkins build as the starting point for the 2.7.x-deploy build (closer to similar SVN url's and such) and then didn't add the jaxws22 profile. My fault.
>>
>> Thanks for fixing it!
>
> no problem :-)
> So I assume changing the job config on Jenkins web page is enough,
> right? (the results are good now btw)
Yep. None of that stuff is persisted in SVN anywhere (that I'm aware of).
Dan
>
> Cheers
> Alessio
>
>
> --
> Alessio Soldano
> Web Service Lead, JBoss
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: 2.7.x snapshots and JAXWS 2.2
Posted by Alessio Soldano <as...@redhat.com>.
On 01/25/2013 06:24 PM, Daniel Kulp wrote:
>>
>> Have the 2.7.x snapshots ever been jaxws22? My gut feeling is when we updated from Java5 (used for <=2.6) to Java6, we didn't add the jaxws22 flag. With <=2.6.x, jaxws22 would be the default when using Java5 (since we don't need to deal with the endorsed crap) so we may not have specified the jaxws22 profile. Once we moved to 2.6, we likely needed to add the profile, but forgot.
>
> Actually, never mind. When I setup the 2.7.x branch, I copied the 2.6.x-deploy Jenkins build as the starting point for the 2.7.x-deploy build (closer to similar SVN url's and such) and then didn't add the jaxws22 profile. My fault.
>
> Thanks for fixing it!
no problem :-)
So I assume changing the job config on Jenkins web page is enough,
right? (the results are good now btw)
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
Re: 2.7.x snapshots and JAXWS 2.2
Posted by Daniel Kulp <dk...@apache.org>.
On Jan 25, 2013, at 12:21 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On Jan 25, 2013, at 3:34 AM, Alessio Soldano <as...@redhat.com> wrote:
>
>> Hi,
>> I've just noticed that the latest built 2.7.3-SNAPSHOT artifacts have
>> not been built using "jaxws22" maven profile. I assume that's a simply
>> oversight happened when the cxf-2.7-deploy Jenkins job was created at
>> the time we moved the trunk to 2.8.
>> I think I've fixed the cxf-2.7-deploy job now (by adding the "jaxws22"
>> profile in its configuration), results will soon be available... ;-)
>> Is the jenkins configuration stored anywhere on source control so that I
>> can persist the changes (if the results are good) ?
>
> Have the 2.7.x snapshots ever been jaxws22? My gut feeling is when we updated from Java5 (used for <=2.6) to Java6, we didn't add the jaxws22 flag. With <=2.6.x, jaxws22 would be the default when using Java5 (since we don't need to deal with the endorsed crap) so we may not have specified the jaxws22 profile. Once we moved to 2.6, we likely needed to add the profile, but forgot.
Actually, never mind. When I setup the 2.7.x branch, I copied the 2.6.x-deploy Jenkins build as the starting point for the 2.7.x-deploy build (closer to similar SVN url's and such) and then didn't add the jaxws22 profile. My fault.
Thanks for fixing it!
Dan
>
> In anycase, thanks for updating that build.
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: 2.7.x snapshots and JAXWS 2.2
Posted by Daniel Kulp <dk...@apache.org>.
On Jan 25, 2013, at 3:34 AM, Alessio Soldano <as...@redhat.com> wrote:
> Hi,
> I've just noticed that the latest built 2.7.3-SNAPSHOT artifacts have
> not been built using "jaxws22" maven profile. I assume that's a simply
> oversight happened when the cxf-2.7-deploy Jenkins job was created at
> the time we moved the trunk to 2.8.
> I think I've fixed the cxf-2.7-deploy job now (by adding the "jaxws22"
> profile in its configuration), results will soon be available... ;-)
> Is the jenkins configuration stored anywhere on source control so that I
> can persist the changes (if the results are good) ?
Have the 2.7.x snapshots ever been jaxws22? My gut feeling is when we updated from Java5 (used for <=2.6) to Java6, we didn't add the jaxws22 flag. With <=2.6.x, jaxws22 would be the default when using Java5 (since we don't need to deal with the endorsed crap) so we may not have specified the jaxws22 profile. Once we moved to 2.6, we likely needed to add the profile, but forgot.
In anycase, thanks for updating that build.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com