cbi-dev http://dev.eclipse.org/mhonarc/lists/cbi-dev/maillist.html cbi-dev en-us Sat, 25 May 2013 01:00:19 GMT Sat, 25 May 2013 01:00:19 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) cbi-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/cbi-dev/maillist.html [cbi-dev] Released CBI Plugins 1.0.3 http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01003.html Hi Everyone, I released a new cbi-plugins-1.0.3 version which is now available on repo.eclipse.org. It contains 1 fix [1] for API Generation. I thought it was a little confusing that each plugin in the repo had a different version so I picked the plugin w... Hi Everyone,

I released a new cbi-plugins-1.0.3 version which is now available on repo.eclipse.org. It contains 1 fix [1] for API Generation.

I thought it was a little confusing that each plugin in the repo had a different version so I picked the plugin with the highest version, incremented it and set all other plugins to the same since we release all cbi-plugins together.

[1] http://git.eclipse.org/c/cbi/org.eclipse.cbi.maven.plugins.git/commit/?id=734d4039a7fb0c814a6ef189badcf02fbe56b397


Thanh
]]> Sat, 25 May 2013 01:00:01 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01003.html thanh.ha@xxxxxxx (Thanh Ha) [cbi-dev] please test staged tycho 0.18.0 http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01002.html Tycho milestone release 0.18.0 has been staged. This is mostly a bugfix release with fixes required by projects on the Kepler release train. For details of new features and bugfixes, see release notes [1]. Please help by testing the staged milestone build.... Tycho milestone release 0.18.0 has been staged. This is mostly a bugfix release with fixes required by projects on the Kepler release train. For details of new features and bugfixes, see release notes [1]. Please help by testing the staged milestone build. To use it, change your tycho version to 0.18.0 and add snippet [2] to your pom. We plan to promote this release on Wed May 29th. Regards, Tycho team [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.18 [2] <pluginRepositories> <pluginRepository> <id>tycho-staged</id> <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-053/</url> </pluginRepository> </pluginRepositories> ]]> Fri, 24 May 2013 13:03:55 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01002.html jan.sievers@xxxxxxx (Sievers, Jan) Re: [cbi-dev] [tycho-dev] 0.18.0 release date? http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01001.html _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev _______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxx http://dev.eclipse.org... the only critical fix (according to p2 developers) we are still waiting for is https://bugs.eclipse.org/bugs/show_bug.cgi?id=407972 Unfortunately this is currently blocked by p2 regression https://bugs.eclipse.org/bugs/show_bug.cgi?id=408691 as soon as we have that sorted out we can stage 0.18.0 Regards, Jan From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Thanh Ha Sent: Donnerstag, 23. Mai 2013 13:59 To: cbi-dev@xxxxxxxxxxx Subject: Re: [cbi-dev] [tycho-dev] 0.18.0 release date? What's the planned release schedule for 0.18.0? The 5/24 date David mentioned is tomorrow and Bug 407972 [1] is still open (Bug 404515 [2] is still open too but probably not as important for us). We'd like to switch over soon so that there's enough time to test the build with it before the final release. In case it's useful, David and I are tracking bugs needed by Eclipse Platform in Bug 407424 [3]. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407972 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=404515 [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407424 Thanh On 03/05/13 07:22 AM, David M Williams wrote: This sounds good to me. As long as you mean "as late as possible" is only a few weeks away :) Our (Platform's) RC2 +0 date is 5/24, so it'd be best to have a "versioned" release for that, which means we would need it by 5/21 to consume for our final RC2 builds. Admittedly, we do usually have to rebuild after that (for RC3, at least) but try real hard for absolute minimal changes after that. Of course, we are willing to be flexible ... especially if it means getting that pesky Mac Icon bug fixed :) ... but, 5/21 would be best for us. Thanks for attending to this. From:        "Sievers, Jan" <jan.sievers@xxxxxxx> To:        "pascal@xxxxxxxxxxxxx" <pascal@xxxxxxxxxxxxx>, Tycho developers list <tycho-dev@xxxxxxxxxxx>, Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>, Date:        05/03/2013 03:17 AM Subject:        Re: [cbi-dev] [tycho-dev] 0.18.0 release date? Sent by:        cbi-dev-bounces@xxxxxxxxxxx ________________________________________ there are other patches for the platform build of the kepler release pending in the meantime [1]. we do need a tycho release in time for the final kepler build for build reproducibility reasons. things are still moving now and I don't want to do a release only to find out there's another last minute stopper for the eclipse platform build. Currently I'm thinking it's best for the platform build to move to 0.18.0-SNAPSHOT and we'll do a tycho release from 0.18.0-SNAPSHOT as late as possible before the final kepler build. What do you think? Jan [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465 -----Original Message----- From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault Sent: Mittwoch, 1. Mai 2013 02:18 To: tycho-dev@xxxxxxxxxxx Subject: Re: [tycho-dev] 0.18.0 release date? I don't need a specific tycho fix, but rather I would need to have a new version of p2 to be consumed. More specifically I've committed a change to the publisher [1] that allows to identify product IUs. This simple change is key to make sure that p2 remediation mechanism does not remove the current product when something incompatible is installed (for an example of this situation see (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406947)). We currently have a workaround in the platform build (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406960) but generally speaking I think the issue is important enough that we want to make sure that we make the fix availble to the mass through tycho by the time Kepler is released. In addition to that, there is also the problem where Mac builds don't have an icon and there are people working on a fix in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=406942. I realize that I've asked for a 0.18 build, but I'm completely happy with a 0.17.1 that just includes a new version of p2. [1] http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=11c1ab663154efe0e0be72945607a9fe45ffc679 Pascal On Tue, April 30, 2013 10:55, Oberlies, Tobias wrote: > Usually, we do a release every four months [1], so this wouldn't be in > time for Kepler. But we could do an extra release for Kepler. > > What is the impact for you? Is there anything particular of the new things > in 0.18.0 [2] are you interested in? > > Regards > Tobias > > [1] http://wiki.eclipse.org/Tycho/Release_Notes > [2] > https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.18.0&order=bug_id&list_id=5315632 > > >> -----Original Message----- >> From: tycho-dev-bounces@xxxxxxxxxxx >> [mailto:tycho-dev-bounces@xxxxxxxxxxx] >> On Behalf Of Pascal Rapicault >> Sent: Dienstag, 30. April 2013 15:50 >> To: tycho-dev@xxxxxxxxxxx >> Cc: platform-releng-dev@xxxxxxxxxxx >> Subject: [tycho-dev] 0.18.0 release date? >> >> Hi, >> >> I would like to know if 0.18.0 will be released in time to build Kepler >> with it? >> >> Thx >> >> Pascal >> >> _______________________________________________ >> tycho-dev mailing list >> tycho-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/tycho-dev > _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev _______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/cbi-dev _______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/cbi-dev ]]> Thu, 23 May 2013 12:10:56 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01001.html jan.sievers@xxxxxxx (Sievers, Jan) Re: [cbi-dev] [tycho-dev] 0.18.0 release date? http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01000.html
What's the planned release schedule for 0.18.0?

The 5/24 date David mentioned is tomorrow and Bug 407972 [1] is still open (Bug 404515 [2] is still open too but probably not as important for us). We'd like to switch over soon so that there's enough time to test the build with it before the final release.

In case it's useful, David and I are tracking bugs needed by Eclipse Platform in Bug 407424 [3].

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407972
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=404515
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407424


Thanh


On 03/05/13 07:22 AM, David M Williams wrote:
This sounds good to me. As long as you mean "as late as possible" is only a few weeks away :)
Our (Platform's) RC2 +0 date is 5/24, so it'd be best to have a "versioned" release for that, which means we would need it by 5/21 to consume for our final RC2 builds.

Admittedly, we do usually have to rebuild after that (for RC3, at least) but try real hard for absolute minimal changes after that. Of course, we are willing to be flexible ... especially if it means getting that pesky Mac Icon bug fixed :) ... but, 5/21 would be best for us.

Thanks for attending to this.





From:        "Sievers, Jan" <jan.sievers@xxxxxxx>
To:        "pascal@xxxxxxxxxxxxx" <pascal@xxxxxxxxxxxxx>, Tycho developers list <tycho-dev@xxxxxxxxxxx>, Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>,
Date:        05/03/2013 03:17 AM
Subject:        Re: [cbi-dev] [tycho-dev] 0.18.0 release date?
Sent by:        cbi-dev-bounces@xxxxxxxxxxx



there are other patches for the platform build of the kepler release pending in the meantime [1].
we do need a tycho release in time for the final kepler build for build reproducibility reasons.

things are still moving now and I don't want to do a release only to find out there's another last minute stopper for the eclipse platform build.
Currently I'm thinking it's best for the platform build to move to 0.18.0-SNAPSHOT and we'll do a tycho release from 0.18.0-SNAPSHOT as late as possible before the final kepler build.

What do you think?

Jan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465


-----Original Message-----
From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Mittwoch, 1. Mai 2013 02:18
To: tycho-dev@xxxxxxxxxxx
Subject: Re: [tycho-dev] 0.18.0 release date?

I don't need a specific tycho fix, but rather I would need to have a new
version of p2 to be consumed.
More specifically I've committed a change to the publisher [1] that allows
to identify product IUs. This simple change is key to make sure that p2
remediation mechanism does not remove the current product when something
incompatible is installed (for an example of this situation see
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=406947)). We currently have
a workaround in the platform build
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=406960) but generally
speaking I think the issue is important enough that we want to make sure
that we make the fix availble to the mass through tycho by the time Kepler
is released.

In addition to that, there is also the problem where Mac builds don't have
an icon and there are people working on a fix in bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=406942.

I realize that I've asked for a 0.18 build, but I'm completely happy with
a 0.17.1 that just includes a new version of p2.

[1]
http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=11c1ab663154efe0e0be72945607a9fe45ffc679

Pascal

On Tue, April 30, 2013 10:55, Oberlies, Tobias wrote:
> Usually, we do a release every four months [1], so this wouldn't be in
> time for Kepler. But we could do an extra release for Kepler.
>
> What is the impact for you? Is there anything particular of the new things
> in 0.18.0 [2] are you interested in?
>
> Regards
> Tobias
>
> [1] http://wiki.eclipse.org/Tycho/Release_Notes
> [2]
> https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.18.0&order=bug_id&list_id=5315632
>
>
>> -----Original Message-----
>> From: tycho-dev-bounces@xxxxxxxxxxx
>> [mailto:tycho-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of Pascal Rapicault
>> Sent: Dienstag, 30. April 2013 15:50
>> To: tycho-dev@xxxxxxxxxxx
>> Cc: platform-releng-dev@xxxxxxxxxxx
>> Subject: [tycho-dev] 0.18.0 release date?
>>
>> Hi,
>>
>> I would like to know if 0.18.0 will be released in time to build Kepler
>> with it?
>>
>> Thx
>>
>> Pascal
>>
>> _______________________________________________
>> tycho-dev mailing list
>> tycho-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-dev
>


_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-dev
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev

 


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev

]]> Thu, 23 May 2013 11:59:28 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01000.html thanh.ha@xxxxxxx (Thanh Ha) Re: [cbi-dev] [tycho-dev] 0.18.0 release date? http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00999.html in things Kepler _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev _______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxx http:... This sounds good to me. As long as you mean "as late as possible" is only a few weeks away :)
Our (Platform's) RC2 +0 date is 5/24, so it'd be best to have a "versioned" release for that, which means we would need it by 5/21 to consume for our final RC2 builds.

Admittedly, we do usually have to rebuild after that (for RC3, at least) but try real hard for absolute minimal changes after that. Of course, we are willing to be flexible ... especially if it means getting that pesky Mac Icon bug fixed :) ... but, 5/21 would be best for us.

Thanks for attending to this.





From:        "Sievers, Jan" <jan.sievers@xxxxxxx>
To:        "pascal@xxxxxxxxxxxxx" <pascal@xxxxxxxxxxxxx>, Tycho developers list <tycho-dev@xxxxxxxxxxx>, Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>,
Date:        05/03/2013 03:17 AM
Subject:        Re: [cbi-dev] [tycho-dev] 0.18.0 release date?
Sent by:        cbi-dev-bounces@xxxxxxxxxxx



there are other patches for the platform build of the kepler release pending in the meantime [1].
we do need a tycho release in time for the final kepler build for build reproducibility reasons.

things are still moving now and I don't want to do a release only to find out there's another last minute stopper for the eclipse platform build.
Currently I'm thinking it's best for the platform build to move to 0.18.0-SNAPSHOT and we'll do a tycho release from 0.18.0-SNAPSHOT as late as possible before the final kepler build.

What do you think?

Jan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465


-----Original Message-----
From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Mittwoch, 1. Mai 2013 02:18
To: tycho-dev@xxxxxxxxxxx
Subject: Re: [tycho-dev] 0.18.0 release date?

I don't need a specific tycho fix, but rather I would need to have a new
version of p2 to be consumed.
More specifically I've committed a change to the publisher [1] that allows
to identify product IUs. This simple change is key to make sure that p2
remediation mechanism does not remove the current product when something
incompatible is installed (for an example of this situation see
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=406947)). We currently have
a workaround in the platform build
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=406960) but generally
speaking I think the issue is important enough that we want to make sure
that we make the fix availble to the mass through tycho by the time Kepler
is released.

In addition to that, there is also the problem where Mac builds don't have
an icon and there are people working on a fix in bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=406942.

I realize that I've asked for a 0.18 build, but I'm completely happy with
a 0.17.1 that just includes a new version of p2.

[1]
http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=11c1ab663154efe0e0be72945607a9fe45ffc679

Pascal

On Tue, April 30, 2013 10:55, Oberlies, Tobias wrote:
> Usually, we do a release every four months [1], so this wouldn't be in
> time for Kepler. But we could do an extra release for Kepler.
>
> What is the impact for you? Is there anything particular of the new things
> in 0.18.0 [2] are you interested in?
>
> Regards
> Tobias
>
> [1] http://wiki.eclipse.org/Tycho/Release_Notes
> [2]
> https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.18.0&order=bug_id&list_id=5315632
>
>
>> -----Original Message-----
>> From: tycho-dev-bounces@xxxxxxxxxxx
>> [mailto:tycho-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of Pascal Rapicault
>> Sent: Dienstag, 30. April 2013 15:50
>> To: tycho-dev@xxxxxxxxxxx
>> Cc: platform-releng-dev@xxxxxxxxxxx
>> Subject: [tycho-dev] 0.18.0 release date?
>>
>> Hi,
>>
>> I would like to know if 0.18.0 will be released in time to build Kepler
>> with it?
>>
>> Thx
>>
>> Pascal
>>
>> _______________________________________________
>> tycho-dev mailing list
>> tycho-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-dev
>


_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-dev
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
]]> Fri, 03 May 2013 11:22:52 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00999.html david_williams@xxxxxxx (David M Williams) Re: [cbi-dev] [tycho-dev] 0.18.0 release date? http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00998.html _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev there are other patches for the platform build of the kepler release pending in the meantime [1]. we do need a tycho release in time for the final kepler build for build reproducibility reasons. things are still moving now and I don't want to do a release only to find out there's another last minute stopper for the eclipse platform build. Currently I'm thinking it's best for the platform build to move to 0.18.0-SNAPSHOT and we'll do a tycho release from 0.18.0-SNAPSHOT as late as possible before the final kepler build. What do you think? Jan [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465 -----Original Message----- From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault Sent: Mittwoch, 1. Mai 2013 02:18 To: tycho-dev@xxxxxxxxxxx Subject: Re: [tycho-dev] 0.18.0 release date? I don't need a specific tycho fix, but rather I would need to have a new version of p2 to be consumed. More specifically I've committed a change to the publisher [1] that allows to identify product IUs. This simple change is key to make sure that p2 remediation mechanism does not remove the current product when something incompatible is installed (for an example of this situation see (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406947)). We currently have a workaround in the platform build (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406960) but generally speaking I think the issue is important enough that we want to make sure that we make the fix availble to the mass through tycho by the time Kepler is released. In addition to that, there is also the problem where Mac builds don't have an icon and there are people working on a fix in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=406942. I realize that I've asked for a 0.18 build, but I'm completely happy with a 0.17.1 that just includes a new version of p2. [1] http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=11c1ab663154efe0e0be72945607a9fe45ffc679 Pascal On Tue, April 30, 2013 10:55, Oberlies, Tobias wrote: > Usually, we do a release every four months [1], so this wouldn't be in > time for Kepler. But we could do an extra release for Kepler. > > What is the impact for you? Is there anything particular of the new things > in 0.18.0 [2] are you interested in? > > Regards > Tobias > > [1] http://wiki.eclipse.org/Tycho/Release_Notes > [2] > https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.18.0&order=bug_id&list_id=5315632 > > >> -----Original Message----- >> From: tycho-dev-bounces@xxxxxxxxxxx >> [mailto:tycho-dev-bounces@xxxxxxxxxxx] >> On Behalf Of Pascal Rapicault >> Sent: Dienstag, 30. April 2013 15:50 >> To: tycho-dev@xxxxxxxxxxx >> Cc: platform-releng-dev@xxxxxxxxxxx >> Subject: [tycho-dev] 0.18.0 release date? >> >> Hi, >> >> I would like to know if 0.18.0 will be released in time to build Kepler >> with it? >> >> Thx >> >> Pascal >> >> _______________________________________________ >> tycho-dev mailing list >> tycho-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/tycho-dev > _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev ]]> Fri, 03 May 2013 07:15:14 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00998.html jan.sievers@xxxxxxx (Sievers, Jan) [cbi-dev] Fw: [platform-releng-dev] I20130501-0800 - BUILD FAILED - re-try at 11 AM (Eastern) ... http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00997.html Our Eclipse platform build is currently blocked by this apparent Tycho bug. We are trying to finish M7 so if any Tycho experts can jump in on the bug it will be greatly appreciated: https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465 John ----- Forwarded ... Our Eclipse platform build is currently blocked by this apparent Tycho bug. We are trying to finish M7 so if any Tycho experts can jump in on the bug it will be greatly appreciated:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465

John

----- Forwarded by John Arthorne/Ottawa/IBM on 05/01/2013 10:49 AM -----

From:        David M Williams <david_williams@xxxxxxxxxx>
To:        "Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>,
Date:        05/01/2013 10:24 AM
Subject:        [platform-releng-dev] I20130501-0800 - BUILD FAILED - re-try at 11        AM (Eastern) ...
Sent by:        platform-releng-dev-bounces@xxxxxxxxxxx



Team, this is still bug

Bug 406465 - Build fails during pack, if bundle already signed

At this point, I recommend just trying to build again, and see if we can demonstrate that its a semi-random bug ... since does seem to work sometimes, even if jdt.core has not been touched.

I'm going to schedule another build for 11 AM (Eastern) and recommend that JDT (still) not touch anything, and see if it fails/succeeds ... if it fails during that 11:00 build, then probably should try touching jdt.core ... though no one, still, knows what the exact problem is.

Other suggestions welcome.

Thanks,




From:        e4Builder@xxxxxxxxxxx
To:        platform-releng-dev@xxxxxxxxxxx,
Date:        05/01/2013 10:02 AM
Subject:        [platform-releng-dev] 4.3.0 I-Build: I20130501-0800 - BUILD FAILED
Sent by:        platform-releng-dev-bounces@xxxxxxxxxxx



Eclipse downloads: http://download.eclipse.org/eclipse/downloads/drops4/I20130501-0800/_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
]]> Wed, 01 May 2013 14:50:38 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00997.html John_Arthorne@xxxxxxx (John Arthorne) Re: [cbi-dev] Maven Windows Signing Plugin for Eclipse http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00996.html It seems similar to the jar signing problem. The artifact to be signed is generally something that is produced during the build. So really it needs to be done as a step at the end of the build rather than at the beginning. The platform executable is the ra... It seems similar to the jar signing problem. The artifact to be signed is generally something that is produced during the build. So really it needs to be done as a step at the end of the build rather than at the beginning. The platform executable is the rare exception where the branded executable is in our source tree. For everyone else, the executable will be transformed during the build to insert the icon for the given product being built. Since the most common case is that the executable is altered during the Tycho build, the signing needs to come in after that. Even in the platform build I wouldn't want to bake in the assumption that the executable won't be altered in some way during the product build.

I imagine the executable signing service being much like the current jar signing service. It would be a very simple process where the branded, unsigned executable is passed in, and the signed executable comes out. Where it comes from and what happens to the result wouldn't be the signing service's concern.

I guess the tricky part is that you need to support the case of standalone builds run by third parties that won't have access to the signing service, as well as builds done within the build.eclipse.org and LTS forges where signing is available. That same problem exists with the jar signing, so hopefully whatever technique was used there could be used here too (can't remember if it was a profile or system property).


John



From:        Thanh Ha <thanh.ha@xxxxxxxxxxx>
To:        Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>,
Date:        04/30/2013 09:57 AM
Subject:        [cbi-dev] Maven Windows Signing Plugin for Eclipse
Sent by:        cbi-dev-bounces@xxxxxxxxxxx



Hi Everyone,

We have some students working on creating a winsigner maven plugin [1] to take advantage of the new windows signing service we setup at the foundation [2].

Ultimately we want to be able to sign the Eclipse Platform Windows exes but I'm not sure how best to approach this problem.

On one hand we could design the winsigner to be very simplistic and simply sign an exe in a single project so that it would work for executables outside of the Eclipse Platform too. But in this case where would we put the signed executables so that CBI Platform build can get them? do we stuff it in the rt.equinox.binaries repo too just like the unsigned?

I'm not familiar with how the executables in rt.equinox.binaries are produced and released into there so maybe understanding this would be useful.


Another thought I had is we could parse the root_configuration.zip files Tycho produces (rcp.config project comes to mind [3]) find the windows exes, push to the signing service, then repack them. But I think this method would be too specific to one project.

Maybe we could even parse artifacts (jar, zip, tar.gz?) produced by Maven / Tycho and unpack/repack them after signing?


I hope someone can point us in the right direction here.


[1] https://bugs.eclipse.org/406157
[2] http://wiki.eclipse.org/IT_Infrastructure_Doc#Web_service_.28Instant.29
[3] http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.tychoeclipsebuilder/rcp.config


Thanh

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
]]> Tue, 30 Apr 2013 18:48:11 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00996.html John_Arthorne@xxxxxxx (John Arthorne) [cbi-dev] Maven Windows Signing Plugin for Eclipse http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00995.html Hi Everyone, We have some students working on creating a winsigner maven plugin [1] to take advantage of the new windows signing service we setup at the foundation [2]. Ultimately we want to be able to sign the Eclipse Platform Windows exes but I'm not su... Hi Everyone,

We have some students working on creating a winsigner maven plugin [1] to take advantage of the new windows signing service we setup at the foundation [2].

Ultimately we want to be able to sign the Eclipse Platform Windows exes but I'm not sure how best to approach this problem.

On one hand we could design the winsigner to be very simplistic and simply sign an exe in a single project so that it would work for executables outside of the Eclipse Platform too. But in this case where would we put the signed executables so that CBI Platform build can get them? do we stuff it in the rt.equinox.binaries repo too just like the unsigned?

I'm not familiar with how the executables in rt.equinox.binaries are produced and released into there so maybe understanding this would be useful.


Another thought I had is we could parse the root_configuration.zip files Tycho produces (rcp.config project comes to mind [3]) find the windows exes, push to the signing service, then repack them. But I think this method would be too specific to one project.

Maybe we could even parse artifacts (jar, zip, tar.gz?) produced by Maven / Tycho and unpack/repack them after signing?


I hope someone can point us in the right direction here.


[1] https://bugs.eclipse.org/406157
[2] http://wiki.eclipse.org/IT_Infrastructure_Doc#Web_service_.28Instant.29
[3] http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.tychoeclipsebuilder/rcp.config


Thanh

]]> Tue, 30 Apr 2013 13:52:25 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00995.html thanh.ha@xxxxxxx (Thanh Ha) Re: [cbi-dev] Fwd: [jdt-core-dev] Cannot build JDT Core project http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00994.html See http://wiki.eclipse.org/Platform-releng/Platform_Build#Java_Server_Mode Szymon From: &quot;Sievers, Jan&quot; &lt;jan.sievers@xxxxxxx&gt; To: Common-build Developers discussion &lt;cbi-dev@xxxxxxxxxxx&gt; Date: 2013-04-18 12:42 Subject: Re: [cbi-dev] Fwd: [jdt-core-dev] Can... See http://wiki.eclipse.org/Platform-releng/Platform_Build#Java_Server_Mode Szymon From: "Sievers, Jan" <jan.sievers@xxxxxxx> To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx> Date: 2013-04-18 12:42 Subject: Re: [cbi-dev] Fwd: [jdt-core-dev] Cannot build JDT Core project Sent by: cbi-dev-bounces@xxxxxxxxxxx I can't find "-XX:-UseLoopPredicate" documented on [1] so maybe it's an unknown option and causing the JVM to exit. Jan [1] http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Webster Sent: Donnerstag, 18. April 2013 12:27 To: Common-build Developers discussion Subject: [cbi-dev] Fwd: [jdt-core-dev] Cannot build JDT Core project Has anybody seen this while building on windows?  To me it looks like a bad command line. Is there a profile to disable API generation? PW ---------- Forwarded message ---------- From: Sorra <dawnstar@xxxxxxx> Date: Wed, Apr 17, 2013 at 11:56 PM Subject: Re: [jdt-core-dev] Cannot build JDT Core project To: "Eclipse JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx> Thanks, it works for resolving dependecies. Buy after long time dowloading dependencies, I encounter this error: [INFO] Command line:         cmd.exe /X /C ""c:\Program Files\Java\jdk1.7.0_09\jre\bin\java.exe" -XX: -UseLoopPredicate -Dhelp.lucene.tokenizer=standard -jar C:\Users\hsorra\.m2 \repo sitory\p2\osgi\bundle\org.eclipse.equinox.launcher\1.3.0.v20120522-1813 \org.ecli pse.equinox.launcher-1.3.0.v20120522-1813.jar -install D:\opensource \eclipse.jdt .core\org.eclipse.jdt.annotation\target\work -configuration D:\opensource \eclips e.jdt.core\org.eclipse.jdt.annotation\target\work\configuration -data target/api build-workspace -application org.eclipse.ant.core.antRunner -buildfile target/.a pibuild.xml" Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] eclipse.jdt.core .................................. SUCCESS [0.434s] [INFO] org.eclipse.jdt.annotation ........................ FAILURE [48.956s] [INFO] org.eclipse.jdt.core .............................. SKIPPED ... ... Is it because of Java version? 2013-04-18 ________________________________________ From:Paul Webster Date:2013-04-18 01:38 Subject:Re: [jdt-core-dev] Cannot build JDT Core project To:"Eclipse JDT Core developers list."<jdt-core-dev@xxxxxxxxxxx> Cc: you would activate it as part of your mvn command.  ex: mvn -Pbuild-individual-bundles  clean verify -- Paul Webster Hi floor.  Make me a sammich! - GIR _______________________________________________ jdt-core-dev mailing list jdt-core-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jdt-core-dev -- Paul Webster Hi floor.  Make me a sammich! - GIR _______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/cbi-dev ]]> Thu, 18 Apr 2013 10:46:22 GMT http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00994.html szymon.ptaszkiewicz@xxxxxxx (Szymon Ptaszkiewicz)