Re: [cross-project-issues-dev] M6 in danger

[Eike Stepper]

I just found the cause of the problem and could work around it. Please expect my M6 build early today. Because of the 
API breakage in EMF Compare it might be necessary to coordinate my contribution with Laurent. I already pinged him 
privately...


The original problem is very odd, though, and my work-around is not a permanent 
solution. Here's the short summary:

Buckminster is always one release behind ;-(

For example when we build for Luna there's only a Kepler Buckminster available and that "works best" with a Kepler 
Platform/p2.


That would still be acceptable but:

A) Our build also uses two self-made tools for extended version management and API report generation. These tools are 
installed from our own integration p2 repository which was built previously against Luna.


B) This (our) p2 repo also contains a p2 feature. Not that I'm happy about that, but we build p2-based products and with 
a feature-based product build I see no way to exclude these dependencies from our own repo.


In effect my Buckminster installation "sees" p2 in three different locations:

1) The Buckminster headless repo (4.3)
2) The Platform repo (must be 4.3, because there's no Bucky 4.4)
3) Our own repo (here we have a p2 4.4!!!)

My current work-around is to disable all our own tools during the build (and not install them), so that the Buckminster 
installation can use only Kepler repos.


I'm not sure if anyone could follow til here but I see two options for the 
future:

1) I continue NOT to use my own tools in my build (although Ed and I have spent 
weeks to develop them).
2) Buckminster starts to produce builds for the CURRENT release train (whether 
contributed to it or not).

Needless to say that I favor option 2, but maybe someone else sees more options?

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Am 11.03.2014 20:00, schrieb Eike Stepper:

Hi all,

Our Buckminster-based build keeps failing with varying errors that all seem to 
be caused by mismatches between/within
Buckminster and p2. And maybe because the 
http://download.eclipse.org/tools/buckminster/headless-4.3 repo contains old
versions of p2. But this is all guessing. In the end I have no clue what's 
going on.

Here's a new error that seems to indicate a problem between different parts of 
p2 (publisher and core):

  [java] 
org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;
  [java] Caused by: java.lang.NoSuchMethodError:
org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;
  [java] at 
org.eclipse.equinox.p2.publisher.AdviceFileAdvice.loadAdviceMap(AdviceFileAdvice.java:118)
  [java] at 
org.eclipse.equinox.p2.publisher.AdviceFileAdvice.(AdviceFileAdvice.java:71)
  [java] at 
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.createAdviceFileAdvice(FeaturesAction.java:166)
  [java] at 
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.generateFeatureIUs(FeaturesAction.java:407)
  [java] at 
org.eclipse.buckminster.pde.tasks.FeaturesAction.generateFeatureIUs(FeaturesAction.java:274)

I can't spend more time on this tonight. I'm aware that EMF Compare seems to 
push me to contribute an M6 that uses their
new APIs. But at this point I can not guarantee that my M5 will be replaced 
tomorrow.

All ideas are welcome!

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] M6 in danger

[Thomas Hallgren]

Hi Eike,

I don't know what's up with your build. I tried to build a full site using our headless-4.3 repository and had no 
problems doing so. I even rebuilt both our update site and headless site and verified again. I'm unable to find any 
problems with the Buckminster sites.


When did your problems start? Could it be that your buckminster installation is somehow corrupted so that it doesn't 
update itself properly?


The p2 version that Buckminster uses (the one that is present at our headless site) is from Kepler SR2. Judging from 
your attached stacktrace, that's not the case with the one used in your build. These are the relevant bundles that what 
ought to be there:


org.eclipse.equinox.p2.publisher_1.3.0.v20140129-1405.jar
org.eclipse.equinox.p2.publisher.eclipse_1.1.200.v20130516-1953.jar

Could it be that you have tried with Luna stuff and then have stuff lingering?

- thomas


On 2014-03-11 20:00, Eike Stepper wrote:

Hi all,

Our Buckminster-based build keeps failing with varying errors that all seem to 
be caused by mismatches between/within
Buckminster and p2. And maybe because the 
http://download.eclipse.org/tools/buckminster/headless-4.3 repo contains old
versions of p2. But this is all guessing. In the end I have no clue what's 
going on.

Here's a new error that seems to indicate a problem between different parts of 
p2 (publisher and core):

  [java] 
org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;
  [java] Caused by: java.lang.NoSuchMethodError:
org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;
  [java] at 
org.eclipse.equinox.p2.publisher.AdviceFileAdvice.loadAdviceMap(AdviceFileAdvice.java:118)
  [java] at 
org.eclipse.equinox.p2.publisher.AdviceFileAdvice.(AdviceFileAdvice.java:71)
  [java] at 
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.createAdviceFileAdvice(FeaturesAction.java:166)
  [java] at 
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.generateFeatureIUs(FeaturesAction.java:407)
  [java] at 
org.eclipse.buckminster.pde.tasks.FeaturesAction.generateFeatureIUs(FeaturesAction.java:274)

I can't spend more time on this tonight. I'm aware that EMF Compare seems to 
push me to contribute an M6 that uses their
new APIs. But at this point I can not guarantee that my M5 will be replaced 
tomorrow.

All ideas are welcome!

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] M6 in danger

[Eike Stepper]

Hi all,

Our Buckminster-based build keeps failing with varying errors that all seem to be caused by mismatches between/within 
Buckminster and p2. And maybe because the http://download.eclipse.org/tools/buckminster/headless-4.3 repo contains old 
versions of p2. But this is all guessing. In the end I have no clue what's going on.


Here's a new error that seems to indicate a problem between different parts of 
p2 (publisher and core):

 [java] 
org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;
 [java] Caused by: java.lang.NoSuchMethodError: 
org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;

 [java] at 
org.eclipse.equinox.p2.publisher.AdviceFileAdvice.loadAdviceMap(AdviceFileAdvice.java:118)
 [java] at 
org.eclipse.equinox.p2.publisher.AdviceFileAdvice.(AdviceFileAdvice.java:71)
 [java] at 
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.createAdviceFileAdvice(FeaturesAction.java:166)
 [java] at 
org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.generateFeatureIUs(FeaturesAction.java:407)
 [java] at 
org.eclipse.buckminster.pde.tasks.FeaturesAction.generateFeatureIUs(FeaturesAction.java:274)

I can't spend more time on this tonight. I'm aware that EMF Compare seems to push me to contribute an M6 that uses their 
new APIs. But at this point I can not guarantee that my M5 will be replaced tomorrow.


All ideas are welcome!

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] EMF Compare M6 delayed

[Eike Stepper]

Hi releng experts,

Maybe you can help me with this problem in our CDO build:

 [java] INFO:  [start 
org.eclipse.emf.cdo.site:eclipse.feature$4.2.100.qualifier#site.p2]
 [java] org.eclipse.core.runtime.CoreException: 
org.eclipse.buckminster.pde.tasks.ProductVersionPatcher.getConfigurationProperties(Ljava/lang/String;Ljava/lang/String;)Ljava/util/Map;

 [java] at 
org.eclipse.buckminster.pde.internal.actor.P2SiteGenerator.run(P2SiteGenerator.java:345)
 [java] at 
org.eclipse.buckminster.pde.internal.actor.P2SiteGenerator.internalPerform(P2SiteGenerator.java:443)
 [java] at 
org.eclipse.buckminster.core.actor.AbstractActor.perform(AbstractActor.java:195)
 [java] 	at 
org.eclipse.buckminster.core.internal.actor.PerformManager$DirectActionInvocation.execute(PerformManager.java:143)

 [java] at 
org.eclipse.buckminster.core.internal.actor.PerformManager.internalPerform(PerformManager.java:454)
 [java] at 
org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:293)
 [java] at 
org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:305)
 [java] at 
org.eclipse.buckminster.core.commands.Perform.internalRun(Perform.java:108)
 [java] at 
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(WorkspaceCommand.java:86)
 [java] at 
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(AbstractCommand.java:200)
 [java] at 
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:343)
 [java] at 
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:284)
 [java] at 
org.eclipse.buckminster.cmdline.Headless.start(Headless.java:358)
 [java] at 
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
 [java] at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
 [java] at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
 [java] at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
 [java] at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
 [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [java] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 [java] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 [java] at java.lang.reflect.Method.invoke(Method.java:606)
 [java] at 
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
 [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
 [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
 [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
 [java] Caused by: java.lang.AbstractMethodError: 
org.eclipse.buckminster.pde.tasks.ProductVersionPatcher.getConfigurationProperties(Ljava/lang/String;Ljava/lang/String;)Ljava/util/Map;

 [java] at 
org.eclipse.equinox.p2.publisher.eclipse.ProductFileAdvice.getProperties(ProductFileAdvice.java:111)
 [java] at 
org.eclipse.buckminster.pde.tasks.ProductAction.hasOtherInstanceAreaAdvice(ProductAction.java:260)
 [java] at 
org.eclipse.buckminster.pde.tasks.ProductAction.createActions(ProductAction.java:228)
 [java] at 
org.eclipse.equinox.p2.publisher.eclipse.ProductAction.perform(ProductAction.java:96)
 [java] at 
org.eclipse.buckminster.pde.tasks.ProductAction.perform(ProductAction.java:219)
 [java] at 
org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
 [java] 	at 
org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1345)

 [java] at 
org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
 [java] at 
org.eclipse.buckminster.pde.internal.actor.P2SiteGenerator.run(P2SiteGenerator.java:343)
 [java] ... 25 more
 [java] 
org.eclipse.buckminster.pde.tasks.ProductVersionPatcher.getConfigurationProperties(Ljava/lang/String;Ljava/lang/String;)Ljava/util/Map;
 [java] Caused by: java.lang.AbstractMethodError: 
org.eclipse.buckminster.pde.tasks.ProductVersionPatcher.getConfigurationProperties(Ljava/lang/String;Ljava/lang/String;)Ljava/util/Map;

 [java] at 
org.eclipse.equinox.p2.publisher.eclipse.ProductFileAdvice.getProperties(ProductFileAdvice.java:111)
 [java] at 
org.eclipse.buckminster.pde.tasks.ProductAction.hasOtherInstanceAreaAdvice(ProductAction.java:260)
 [java] at 
org.eclipse.buckminster.pde.tasks.ProductAction.createActions(ProductAction.java:228)
 [java] at 
org.eclipse.equinox.p2.publisher.eclipse.ProductAction.perform(ProductAction.java:96)
 [java] at 
org.eclipse.buckminster.pde.tasks.

[cross-project-issues-dev] EMF Compare M6 delayed

[Laurent Goubet]

Hi,

EMF Compare switches from 2.2 to 3.0 for its M6 version... though that 
breaks a few adopters.


The build is ready but adding it to the aggregation would make it fail 
until CDO can update its own contribution to M6... and disabling CDO for 
the time being ripples through a few other projects.


Eike is currently encountering a few issues on his build, so we're 
delaying the contribution of EMF Compare M6 until tomorrow in the hopes 
that these issues will be solved in the meantime.


Laurent Goubet
Obeo
<>___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Xtext 2.6.0M6

[Dennis Hübner]

Hi all,
Xtext Luna M6 contribution will be late today.

Best regards,
Dennis Hübner

Xtext Commiter / Build Engineer


Mobile: +49 (0) 151 / 17 39 67 07
Telefon: +49 (0) 431 / 990 268 70
Fax: +49 (0) 431 / 990 268 72

itemis AG
Niederlassung Kiel
Am Germaniahafen 1
24143 Kiel
http://www.itemis.de/

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens 
Trompeter, Sebastian Neus

Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] build.eclipse.org

[Fred Bricon]

Thanks Denis!


On Tue, Mar 11, 2014 at 4:12 PM, Denis Roy  wrote:

>  I've started the signing web service.
>
> Denis
>
>
> On 03/11/2014 10:57 AM, Fred Bricon wrote:
>
> Matt, the signing service is apparently down. I get errors like :
>
>  [ERROR] Failed to execute goal 
> org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.0.1:sign (sign) on 
> project org.eclipse.m2e.wtp.overlay: Could not sign artifact 
> org.eclipse.m2e.wtp:org.eclipse.m2e.wtp.overlay:eclipse-plugin:1.1.0-SNAPSHOT:
>  Connection to http://build.eclipse.org:31338 refused: Connection refused -> 
> [Help 1]
>
>  Fred
>
>
>
> On Tue, Mar 11, 2014 at 3:45 PM, Webmaster(Matt Ward) <
> webmas...@eclipse.org> wrote:
>
>> Hi Folks,
>>
>>   Build.eclipse.org is now back in service.
>>
>> -Matt.
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
>  --
> "Have you tried turning it off and on again" - The IT Crowd
>
>
> ___
> cross-project-issues-dev mailing 
> listcross-project-issues-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>


-- 
"Have you tried turning it off and on again" - The IT Crowd
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] build.eclipse.org

[Denis Roy]

I've started the signing web service.

Denis

On 03/11/2014 10:57 AM, Fred Bricon wrote:

Matt, the signing service is apparently down. I get errors like :

[ERROR] Failed to execute goal 
org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.0.1:sign (sign) on project 
org.eclipse.m2e.wtp.overlay: Could not sign artifact 
org.eclipse.m2e.wtp:org.eclipse.m2e.wtp.overlay:eclipse-plugin:1.1.0-SNAPSHOT: 
Connection tohttp://build.eclipse.org:31338    
refused: Connection refused -> [Help 1]
Fred


On Tue, Mar 11, 2014 at 3:45 PM, Webmaster(Matt Ward) 
mailto:webmas...@eclipse.org>> wrote:


Hi Folks,

Build.eclipse.org  is now back in service.

-Matt.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




--
"Have you tried turning it off and on again" - The IT Crowd


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] jdk1.7.0-latest symlink on /shared/common updated to jdk1.7.0_51

[Thanh Ha]

Hi Everyone,

Just wanted to make sure projects are aware that we updated the 
jdk1.7.0-latest symlink today per bug 429926 [1] to point to the newer 
jdk1.7.0_51 version. If you still require the older JDK for your builds 
it is still available at /shared/common/jdk1.7.0_25.



Thanh

[1] https://bugs.eclipse.org/429926

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] build.eclipse.org

[Fred Bricon]

Matt, the signing service is apparently down. I get errors like :

[ERROR] Failed to execute goal
org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.0.1:sign
(sign) on project org.eclipse.m2e.wtp.overlay: Could not sign artifact
org.eclipse.m2e.wtp:org.eclipse.m2e.wtp.overlay:eclipse-plugin:1.1.0-SNAPSHOT:
Connection to http://build.eclipse.org:31338 refused: Connection
refused -> [Help 1]


Fred



On Tue, Mar 11, 2014 at 3:45 PM, Webmaster(Matt Ward)  wrote:

> Hi Folks,
>
>   Build.eclipse.org is now back in service.
>
> -Matt.
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] build.eclipse.org

[Webmaster(Matt Ward)]

Hi Folks,

  Build.eclipse.org is now back in service.

-Matt.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev