[cross-project-issues-dev] To be able to install newly signed plug-in on Helios and Indigo
Hello, We are not able to install newly signed plug-ins on Helios, and Indigo. We get the following error (during the installation of a signed plug-in): Caused by: java.security.NoSuchAlgorithmException: No algorithm found for 2.16.840.1.101.3.4.2.1 at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.findDigest(PKCS7Pro cessor.java:87) at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.processSignerInfos( PKCS7Processor.java:311) at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.(PKCS7Process or.java:133) at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSig ner(SignatureBlockProcessor.java:93) at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(Si gnatureBlockProcessor.java:60) at org.eclipse.osgi.internal.signedcontent.SignedBundleFile.setBundleFile(Sig nedBundleFile.java:47) at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent( SignedBundleHook.java:247) This error happens because the class PKCS7Processor embedded in Helios and Indigo isnt able to deal with SHA-256. SHA-256 is used since Java-1.7 to sign [1]. I assume that the signing service has been updated to Java-1.7. >From the release train point of view this seems to be a good thing. But my company integrates EMF Facet and MoDisco into its own product and some of our clients are still using Helios and Java-1.5! Does anybody have any advice to be able to install newly signed plug-in on Helios and Indigo? Regards, Grégoire Dupé ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] EMF Facet participating in Mars release
Hello, An integration build of EMF Facet 1.0.0 is available in the following p2 repository : http://download.eclipse.org/facet/updates/integration/1.0.0/I201411271427/ The deprecated APIs are not included in this build. I recommend to use this build, as soon as possible, to identify compilation failures. Regards, Grégoire -Message d'origine- De : Grégoire Dupé [mailto:gd...@mia-software.com] Envoyé : jeudi 27 novembre 2014 10:07 À : Cross project issues Objet : Re: [cross-project-issues-dev] EMF Facet participating in Mars release Hello, We have chosen to graduate "EMF Facet" to the version 1.0.0. The version 0.5.0 will then not be released and the version 1.0.0 will be delivered into Mars. This graduation comes with an API break, all the deprecated APIs will be removed (the old version of the meta-model extension mechanism, the old version of customization mechanism, the table widget). The "cleaned" API is already available in the git branch 'rmDeprecated'. The "cleaned" API will be delivered into M4. I’ll build a first version of "cleaned" API and I'll declare it into the b3 files as soon as possible. I’ve updated the release page: https://projects.eclipse.org/projects/modeling.emft.emf-facet/releases/1.0.0 Regards, Grégoire Dupé - Mail original - De: "Grégoire Dupé" À: "Cross project issues" Envoyé: Jeudi 21 Août 2014 18:41:10 Objet: [cross-project-issues-dev] EMF Facet participating in Mars release Hello, EMF Facet will be participating in Mars. The offset will be +2. Release record: https://projects.eclipse.org/projects/modeling.emft.emf-facet/releases/0.5.0 Regards, Grégoire ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] EMF Facet participating in Mars release
Hello, We have chosen to graduate "EMF Facet" to the version 1.0.0. The version 0.5.0 will then not be released and the version 1.0.0 will be delivered into Mars. This graduation comes with an API break, all the deprecated APIs will be removed (the old version of the meta-model extension mechanism, the old version of customization mechanism, the table widget). The "cleaned" API is already available in the git branch 'rmDeprecated'. The "cleaned" API will be delivered into M4. I’ll build a first version of "cleaned" API and I'll declare it into the b3 files as soon as possible. I’ve updated the release page: https://projects.eclipse.org/projects/modeling.emft.emf-facet/releases/1.0.0 Regards, Grégoire Dupé - Mail original - De: "Grégoire Dupé" À: "Cross project issues" Envoyé: Jeudi 21 Août 2014 18:41:10 Objet: [cross-project-issues-dev] EMF Facet participating in Mars release Hello, EMF Facet will be participating in Mars. The offset will be +2. Release record: https://projects.eclipse.org/projects/modeling.emft.emf-facet/releases/0.5.0 Regards, Grégoire ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] EMF Facet participating in Mars release
Hello, EMF Facet will be participating in Mars. The offset will be +2. Release record: https://projects.eclipse.org/projects/modeling.emft.emf-facet/releases/0.5.0 Regards, Grégoire ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Where is com.google.common.base ?
Thanks a lot ! De : cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] De la part de Christian W. Damus Envoyé : mardi 8 avril 2014 18:31 À : Cross project issues Objet : Re: [cross-project-issues-dev] Where is com.google.common.base ? Hi, Grégoire, That package is provided by the com.google.guava bundle in Orbit. Cheers, Christian On Apr 8, 2014, at 12:28 PM, Grégoire Dupé wrote: Hello, While building MoDisco (luna verison), I get the following error : [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.eclipse.gmt.modisco.java.discoverer.benchmark 0.12.0.qualifier [ERROR] Missing requirement: org.eclipse.acceleo.common 3.5.0.201403120947 requires 'package com.google.common.base [12.0.0,13.0.0)' but it could not be found [ERROR] Cannot satisfy dependency: org.eclipse.acceleo.model 3.5.0.201403120947 depends on: bundle org.eclipse.acceleo.common 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.gmt.modisco.java.discoverer.benchmark 0.12.0.qualifier depends on: bundle org.eclipse.acceleo.model 0.8.1 Im using <http://download.eclipse.org/acceleo/updates/milestones/3.5/S201403120947> http://download.eclipse.org/acceleo/updates/milestones/3.5/S201403120947. (This is the repository declared in <http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/m2t-acc eleo.b3aggrcon> http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/m2t-acce leo.b3aggrcon). com.google.common.base is not available in <http://download.eclipse.org/tools/orbit/downloads/drops/R20140114142710/> http://download.eclipse.org/tools/orbit/downloads/drops/R20140114142710/. Can anybody tell me where I can found com.google.common.base ? Regards, Grégoire ___ cross-project-issues-dev mailing list <mailto:cross-project-issues-dev@eclipse.org> cross-project-issues-dev@eclipse.org <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> 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] Where is com.google.common.base ?
Hello, While building MoDisco (luna verison), I get the following error : [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.eclipse.gmt.modisco.java.discoverer.benchmark 0.12.0.qualifier [ERROR] Missing requirement: org.eclipse.acceleo.common 3.5.0.201403120947 requires 'package com.google.common.base [12.0.0,13.0.0)' but it could not be found [ERROR] Cannot satisfy dependency: org.eclipse.acceleo.model 3.5.0.201403120947 depends on: bundle org.eclipse.acceleo.common 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.gmt.modisco.java.discoverer.benchmark 0.12.0.qualifier depends on: bundle org.eclipse.acceleo.model 0.8.1 Im using http://download.eclipse.org/acceleo/updates/milestones/3.5/S201403120947. (This is the repository declared in http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/m2t-acce leo.b3aggrcon). com.google.common.base is not available in http://download.eclipse.org/tools/orbit/downloads/drops/R20140114142710/. Can anybody tell me where I can found com.google.common.base ? Regards, Grégoire ___ 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] The package 'org.eclipse.bpmn2 0.7.0' could not be found
Hello, I meet the following error to validate the aggregation. """ Error Tue Jan 28 18:34:13 CET 2014 Missing requirement: org.eclipse.bpmn2.modeler.runtime.example 1.0.2.201312131338 requires 'package org.eclipse.bpmn2 0.7.0' but it could not be found JavaPackage(org.eclipse.bpmn2 0.7.0) is required by: ValidationSet(main) Contribution(SOA-BPMN2 Modeler) MappedRepository(http://download.eclipse.org/bpmn2-modeler/updates/luna/1.0.2) Feature(org.eclipse.bpmn2.modeler.examples.feature.feature.group 1.0.2) InstallableUnit(org.eclipse.bpmn2.modeler.runtime.example 1.0.2.201312131338) """ Despite this problem, I've committed changes in org.eclipse.simrel.build (MoDisco and EMF Facet updates), because I will be out of the office tomorrow. As far as I know MoDisco and EMF Facet does not have any relationship with org.eclipse.bpmn2. I hope this problem could be fixed without me. However I'll tried to keep in touch, as much as possible. Regards, Grégoire ___ 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] EMF Facet Participation in Luna
Hi, The EMF Facet project will be participating in the Luna Simultaneous Release. EMF Facet has an offset of +2. The release record of the contribution can be found here: http://projects.eclipse.org/projects/modeling.emft.emf-facet/releases/0.4.0 Regards, Grégoire ___ 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] Status and Outlook for Luna M1
Hello I'm still waiting for Acceleo and ATL (may be more) to deliver MoDisco. It's quite late in Europe; I've to leave the office. I assume that MoDisco will not be included in Luna M1 :-( Regards, Grégoire - Original Message - From: "David M Williams" To: cross-project-issues-dev@eclipse.org Sent: Jeudi 22 Août 2013 10:13:05 Subject: [cross-project-issues-dev] Status and Outlook for Luna M1 Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc. So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help. Thanks, = = = = = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build ___ 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] Re : Re: Status and outlook for Luna M1
Hello, I'm waiting for Acceleo to deliver MoDisco in Luna. By the way, I get the following error : Missing requirement: MoDisco Java Server Pages Discoverer (Incubation) 0.12.0.201308191929 (org.eclipse.modisco.jee.jsp.discoverer 0.12.0.201308191929) requires 'bundle org.antlr.runtime [3.0.0,3.1.0)' but it could not be found Bundle(org.antlr.runtime [3.0.0,3.1.0)) is required by: ValidationSet(main) Contribution(MoDisco) MappedRepository(http://download.eclipse.org/modeling/mdt/modisco/updates/integration/0.12.0/I201308191929/) Feature(org.eclipse.modisco.sdk.feature.feature.group 0.12.0) InstallableUnit(org.eclipse.modisco.jee.feature.feature.group 0.12.0.201308191929) InstallableUnit(org.eclipse.modisco.jee.jsp.discoverer 0.12.0.201308191929) For Kepler, I haven't provided antlr in the MoDisco updates site. Must I for Luna ? If I must add antlr in the MoDisco update site, I won't be able to deliver MoDisco before tommorrow morning (Europe time). Regrads, Grégoire - Mail d'origine - De: Greg Watson À: Cross project issues Envoyé: Wed, 21 Aug 2013 21:48:44 +0200 (CEST) Objet: Re: [cross-project-issues-dev] Status and outlook for Luna M1 Thanks! On Aug 21, 2013, at 3:39 PM, David Dykstal wrote: > It exists now. > http://download.eclipse.org/tm/updates/3.6milestones/ > > -- David Dykstal, Architect - Rational Developer for i > > > > From:Greg Watson > To:Cross project issues , > Date:08/21/2013 01:45 PM > Subject:Re: [cross-project-issues-dev] Status and outlook for Luna M1 > Sent by:cross-project-issues-dev-boun...@eclipse.org > > > > Does TM have a luna repo somewhere? I can't seem to find one. > > Thanks, > Greg > > On Aug 21, 2013, at 1:14 PM, David Dykstal wrote: > > > I have enabled TM. > > > > Doug Schaefer wrote: > >> Sigh. RSE isn't enabled so CDT fails. > >> > > ___ > > 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 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
Re: [cross-project-issues-dev] Status and outlook for Luna M1
> EMF Validation was re-enabled this morning EST. Thanks ! I've delivered EMF Facet. Regards, Grégoire ___ 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] Status and outlook for Luna M1
Hello, I’m still not able to deliver EMF Facet and MoDisco because some dependences have not be re-enabled (at least org.eclipse.emf.validation). Regards, Grégoire ___ 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] EMF Facet in Luna will be late
Hello, I'm not able to deliver EMF Facet 0.4.0 in Luna on time, because EMF Facet uses org.eclipse.emf.validation which is not available yet. Regards, Grégoire ___ 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] simrel.kepler.runaggregator is failling
Hello, I can see the following error message: """ Build failed! Exception was org.eclipse.core.runtime.CoreException: Not all artifacts could be mirrored, see log for details """ But I do not found the line explaining which update site is causing the failure. Does any body can explain me where or what to search ? Regards, Grégoire ___ 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] MoDisco: small API break to be compatible with Helios
Hello, We have worked to get a version of MoDisco compatible with Helios. To reach this target, we had to introduce a small API break on the class 'org.eclipse.gmt.modisco.java.emf.util.JavaSwitch'. This class doesn’t extend the class 'org.eclipse.emf.ecore.util.Switch' anymore (EMF code generator evolution from Helios to Indigo). The API break should impact a very few users. If you get blocking trouble caused by this API do not hesitate to inform us. Regards, Grégoire Dupé ___ 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] Heads up ... org.junit4 is gone from M6
> Hope this short notice helps some of you (at least EMF Facet project :) Yes, this will help ! Thank you, Grégoire - Mail Original - De: "David M Williams" À: cross-project-issues-dev@eclipse.org Envoyé: Jeudi 7 Mars 2013 22h07:14 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] Heads up ... org.junit4 is gone from M6 Now that I've seen two projects have this problem ... thought it deserved mention to all, slightly ahead of time, that the "old" org.junit4 bundle was a quick trick to allow/transition to having org.junit version 3 and org.junit version 4 in the same stack (several releases ago), but, that's now been removed for Kepler, and only the official org.junit version 4 bundle is being included in the platform. Any fixes needed should be easy ... just change the name of any "require bundle" (in MANIFEST or feature.xml to org.junit and everything should still work as before. Hope this short notice helps some of you (at least EMF Facet project :) ___ 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
Re: [cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1
Hello, MoDisco is back to normal. Thanks to the Birt team. Regards, Grégoire - Mail Original - De: "Grégoire Dupé" À: "Cross project issues" Envoyé: Mardi 18 Décembre 2012 20h24:45 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1 Hello, When I try to build MoDisco, I get the following error : [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 [ERROR] Only one of the following can be installed at once: [com.ibm.icu 4.4.2.v20110823, com.ibm.icu 4.0.1.v20100112, com.ibm.icu 4.2.1.v20100412, com.ibm.icu 50.1.0.v20121116-2] [ERROR] Cannot satisfy dependency: org.eclipse.birt.chart.engine 4.2.1.v201209041636 depends on: bundle org.eclipse.birt.core [2.1.0,5.0.0) [ERROR] Cannot satisfy dependency: org.eclipse.birt.core 4.2.1.v201209121203 depends on: package com.ibm.icu.lang [3.4.4,5.0.0) [ERROR] Cannot satisfy dependency: org.eclipse.e4.rcp.feature.group 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4 depends on: com.ibm.icu [50.1.0.v20121116-2] [ERROR] Cannot satisfy dependency: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 depends on: org.eclipse.modisco.java.discoverer.benchmark.feature.feature.group 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 depends on: org.eclipse.rcp.feature.group 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.modisco.java.discoverer.benchmark 0.10.1.qualifier depends on: bundle org.eclipse.birt.chart.engine 2.5.1 [ERROR] Cannot satisfy dependency: org.eclipse.modisco.java.discoverer.benchmark.feature.feature.group 0.10.1.qualifier depends on: org.eclipse.modisco.java.discoverer.benchmark 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.rcp.feature.group 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP depends on: org.eclipse.e4.rcp.feature.group [1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4] [ERROR] [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.acceleo.common 3.3.0.v20120131-0422 to bundle com.google.collect 0.0.0.", "Unable to satisfy dependency from org.eclipse.acceleo.engine 3.3.0.v20111213-0806 to bundle com.google.collect 1.0.0.", "Unable to satisfy dependency from org.eclipse.acceleo.engine 3.3.0.v20120131-0422 to bundle com.google.collect 1.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] I assume that this error is related to the dependency from Birt to com.ibm.icu.lang. I'll have to wait the new build of Birt, I may be late to deliver MoDisco. Regards, Grégoire - Mail Original - De: "David M Williams" À: "Cross project issues (cross-project-issues-dev@eclipse.org)" Envoyé: Lundi 17 Décembre 2012 23h20:28 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1 We finally got a green build! Though, I did have to disable a few things, either there was a conflict, such as for ICU4J v50 vs 4.2, and many others because something else was disabled. There's the current status of enabled flag: Whole contribution disabled ... never enabled for Kepler. I'll remove these if I don't hear something soon. emf-query2.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build These have a feature or repository disabled, some disabled by "owners", since they knew they needed some work still, and a few disabled by me, based on what I could see using the b3 aggregator editor's "validate aggregation" function. Feel free to re-enable if/when you think ready. amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build (2 matches) egit.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build (2 matches) mat.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mmt-qvto.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build webtools.b3aggrcon - org.eclipse.simrel.build I've promoted what we had from this first green build to .../releases/staging. Don't forget to check the reports occasionally: http://build.eclipse.org/simrel/kepler/reporeports/ Thanks, ___ 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://d
Re: [cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1
Hello, When I try to build MoDisco, I get the following error : [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 [ERROR] Only one of the following can be installed at once: [com.ibm.icu 4.4.2.v20110823, com.ibm.icu 4.0.1.v20100112, com.ibm.icu 4.2.1.v20100412, com.ibm.icu 50.1.0.v20121116-2] [ERROR] Cannot satisfy dependency: org.eclipse.birt.chart.engine 4.2.1.v201209041636 depends on: bundle org.eclipse.birt.core [2.1.0,5.0.0) [ERROR] Cannot satisfy dependency: org.eclipse.birt.core 4.2.1.v201209121203 depends on: package com.ibm.icu.lang [3.4.4,5.0.0) [ERROR] Cannot satisfy dependency: org.eclipse.e4.rcp.feature.group 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4 depends on: com.ibm.icu [50.1.0.v20121116-2] [ERROR] Cannot satisfy dependency: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 depends on: org.eclipse.modisco.java.discoverer.benchmark.feature.feature.group 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 depends on: org.eclipse.rcp.feature.group 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.modisco.java.discoverer.benchmark 0.10.1.qualifier depends on: bundle org.eclipse.birt.chart.engine 2.5.1 [ERROR] Cannot satisfy dependency: org.eclipse.modisco.java.discoverer.benchmark.feature.feature.group 0.10.1.qualifier depends on: org.eclipse.modisco.java.discoverer.benchmark 0.0.0 [ERROR] Cannot satisfy dependency: org.eclipse.rcp.feature.group 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP depends on: org.eclipse.e4.rcp.feature.group [1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4] [ERROR] [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.acceleo.common 3.3.0.v20120131-0422 to bundle com.google.collect 0.0.0.", "Unable to satisfy dependency from org.eclipse.acceleo.engine 3.3.0.v20111213-0806 to bundle com.google.collect 1.0.0.", "Unable to satisfy dependency from org.eclipse.acceleo.engine 3.3.0.v20120131-0422 to bundle com.google.collect 1.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] I assume that this error is related to the dependency from Birt to com.ibm.icu.lang. I'll have to wait the new build of Birt, I may be late to deliver MoDisco. Regards, Grégoire - Mail Original - De: "David M Williams" À: "Cross project issues (cross-project-issues-dev@eclipse.org)" Envoyé: Lundi 17 Décembre 2012 23h20:28 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1 We finally got a green build! Though, I did have to disable a few things, either there was a conflict, such as for ICU4J v50 vs 4.2, and many others because something else was disabled. There's the current status of enabled flag: Whole contribution disabled ... never enabled for Kepler. I'll remove these if I don't hear something soon. emf-query2.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build These have a feature or repository disabled, some disabled by "owners", since they knew they needed some work still, and a few disabled by me, based on what I could see using the b3 aggregator editor's "validate aggregation" function. Feel free to re-enable if/when you think ready. amp.b3aggrcon - org.eclipse.simrel.build birt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build (2 matches) egit.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build (2 matches) mat.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mmt-qvto.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build webtools.b3aggrcon - org.eclipse.simrel.build I've promoted what we had from this first green build to .../releases/staging. Don't forget to check the reports occasionally: http://build.eclipse.org/simrel/kepler/reporeports/ Thanks, ___ 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
Re: [cross-project-issues-dev] EMF Facet 0.3.0M3 will be late
Hello, I've delivered EMF Facet 0.3.0M3. Regards, Grégoire - Mail Original - De: "Grégoire Dupé" À: "cross-project-issues-dev" Envoyé: Mardi 13 Novembre 2012 14h35:24 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] EMF Facet 0.3.0M3 will be late Hello, I will be late to deliver EMF Facet 0.3.0M3. I’ve meet some signing problems. According to the file /home/data/httpd/download-staging.priv/arch/signer.log, I assume this problem has been caused by a network error. For your information, here is a copy of a some lines from /home/data/httpd/download-staging.priv/arch/signer.log Processing /home/data/httpd/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip Extracting plugins/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar Running Repack Sign on /home/data/httpd/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/plugins/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar 2012-11-13 05:47:15: build(8306) SIGNER(3543): asked to sign /opt/public/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar 2012-11-13 05:47:15: build SIGNER(3543): Signing JAR file [/opt/public/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar] updating: META-INF/MANIFEST.MF jarsigner: unable to sign jar: no response from the Timestamping Authority. When connecting from behind a firewall then an HTTP proxy may need to be specified. Supply the following options to jarsigner: -J-Dhttp.proxyHost= -J-Dhttp.proxyPort= 2012-11-13 05:47:31: build SIGNER(3543): Finished signing /opt/public/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar Adding plugins/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar to /home/data/httpd/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip.temp - Regards, Grégoire ___ 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] EMF Facet 0.3.0M3 will be late
Hello, I will be late to deliver EMF Facet 0.3.0M3. I’ve meet some signing problems. According to the file /home/data/httpd/download-staging.priv/arch/signer.log, I assume this problem has been caused by a network error. For your information, here is a copy of a some lines from /home/data/httpd/download-staging.priv/arch/signer.log Processing /home/data/httpd/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip Extracting plugins/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar Running Repack Sign on /home/data/httpd/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/plugins/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar 2012-11-13 05:47:15: build(8306) SIGNER(3543): asked to sign /opt/public/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar 2012-11-13 05:47:15: build SIGNER(3543): Signing JAR file [/opt/public/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar] updating: META-INF/MANIFEST.MF jarsigner: unable to sign jar: no response from the Timestamping Authority. When connecting from behind a firewall then an HTTP proxy may need to be specified. Supply the following options to jarsigner: -J-Dhttp.proxyHost= -J-Dhttp.proxyPort= 2012-11-13 05:47:31: build SIGNER(3543): Finished signing /opt/public/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/temp_org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar Adding plugins/org.eclipse.emf.facet.widgets.table.doc.source_0.3.0.v201211130956.jar to /home/data/httpd/download-staging.priv/modeling/emft/facet/signingN/b1277a34-8a01-4cd3-a46e-e2d087b44ef8/signed/org.eclipse.emf.facet.updatesite-0.3.0.v201211130956.zip.temp - Regards, Grégoire ___ 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] Hudson appears to have hanged
Hello, Because of the trouble with Hudson, I didn’t have enough time to test the RC4 build of EMF Facet. If everybody agrees I won’t deliver a RC4 build for EMF Facet. To my mind this should not cause any trouble because: - No changes have been committed since RC3, so RC4 should be strictly equal to RC3. - The today build of EMF Facet (using dependencies declared in http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/) succeed. Regards, Grégoire - Mail Original - De: "Laurent Goubet" À: cross-project-issues-dev@eclipse.org Envoyé: Mardi 18 Septembre 2012 12h01:00 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [cross-project-issues-dev] Hudson appears to have hanged Same here, we cannot launch the SR1 +2 builds as hudson is seemingly down. On 18/09/2012 09:38, Matthias Sohn wrote: 2012/9/18 Konstantin Komissarchik < konstantin.komissarc...@oracle.com > I unable to reach hudson.eclipse.org , but I am able to reach www.eclipse.org . - Konstantin I also can't reach hudson, I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=389789 to track this problem -- Matthias ___ 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 mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] aggregation build failed: MoDisco and Papyrus
I've commited the update of mdt-modisco.b3aggrcon.
I'll launch a new Kepler aggregator build.
Regards,
Grégoire
- Mail Original -
De: "Grégoire Dupé"
À: "Cross project issues"
Envoyé: Mercredi 22 Août 2012 11h16:09 GMT +01:00 Amsterdam / Berlin / Berne /
Rome / Stockholm / Vienne
Objet: Re: [cross-project-issues-dev] aggregation build failed: MoDisco and
Papyrus
I've some difficulties to use Git.
Please, can anybody commit the following configuration in mdt-modisco.b3aggrcon
?
http://www.omg.org/XMI";
xmlns:aggregator="http://www.eclipse.org/b3/2011/aggregator/1.1.0";
label="MoDisco">
http://download.eclipse.org/modeling/mdt/modisco/updates/milestones/0.10/SR1_RC1";
description="MoDisco Milestones">
Regards,
Grégoire
- Mail Original -
De: "Grégoire Dupé"
À: "cross-project-issues-dev"
Envoyé: Mercredi 22 Août 2012 11h07:22 GMT +01:00 Amsterdam / Berlin / Berne /
Rome / Stockholm / Vienne
Objet: [cross-project-issues-dev] aggregation build failed: MoDisco and Papyrus
Hello,
I've seen that the aggregation failed because of the follwing problem:
Missing requirement: Papyrus properties XWT Projectors (Incubation)
0.9.0.v201208070918 (org.eclipse.papyrus.customization.properties.model.xwt
0.9.0.v201208070918) requires 'bundle org.eclipse.gmt.modisco.xml 0.9.0' but it
could not be found
I've havn't delivered MoDisco yet.
I'm trying the update of 'mdt-modisco.b3aggrcon'.
Regards,
Grégoire
___
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 mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] aggregation build failed: MoDisco and Papyrus
I've some difficulties to use Git. Please, can anybody commit the following configuration in mdt-modisco.b3aggrcon ? http://www.omg.org/XMI"; xmlns:aggregator="http://www.eclipse.org/b3/2011/aggregator/1.1.0"; label="MoDisco"> http://download.eclipse.org/modeling/mdt/modisco/updates/milestones/0.10/SR1_RC1"; description="MoDisco Milestones"> Regards, Grégoire - Mail Original - De: "Grégoire Dupé" À: "cross-project-issues-dev" Envoyé: Mercredi 22 Août 2012 11h07:22 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] aggregation build failed: MoDisco and Papyrus Hello, I've seen that the aggregation failed because of the follwing problem: Missing requirement: Papyrus properties XWT Projectors (Incubation) 0.9.0.v201208070918 (org.eclipse.papyrus.customization.properties.model.xwt 0.9.0.v201208070918) requires 'bundle org.eclipse.gmt.modisco.xml 0.9.0' but it could not be found I've havn't delivered MoDisco yet. I'm trying the update of 'mdt-modisco.b3aggrcon'. Regards, Grégoire ___ 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] aggregation build failed: MoDisco and Papyrus
Hello, I've seen that the aggregation failed because of the follwing problem: Missing requirement: Papyrus properties XWT Projectors (Incubation) 0.9.0.v201208070918 (org.eclipse.papyrus.customization.properties.model.xwt 0.9.0.v201208070918) requires 'bundle org.eclipse.gmt.modisco.xml 0.9.0' but it could not be found I've havn't delivered MoDisco yet. I'm trying the update of 'mdt-modisco.b3aggrcon'. Regards, Grégoire ___ 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] Status and readiness for Kepler M1
Hello, > emft-emffacet.b3aggrcon - org.eclipse.simrel.build I've unable EMF Facet, yesterday. I don't understand why it is still in the list. > mdt-modisco.b3aggrcon - org.eclipse.simrel.build Just one more test and I'll enable MoDisco. Regards, Grégoire - Mail Original - De: "David M Williams" À: cross-project-issues-dev@eclipse.org Envoyé: Mercredi 22 Août 2012 07h09:59 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] Status and readiness for Kepler M1 Still 26 projects not enabled for Kepler M1. Can some one explain to me what this is about? Some passive aggressive protest? Too many people take vacation all summer and don't even check Eclipse mailing lists? Are projects just indecisive and think a commitment now means it is a written in stone promise (which is never the case). I know one or two people have mentioned they have special problems that will likely prevent participation in M1, but, If I hear nothing, I'll assume the remaining 24 or so are dropping out, and will remove those files from the 'master' branch. For those projects to rejoin later will take an exception since there's a requirement for those participating to "keep participating" or else inform us all you no longer plan to. The M4 deadline only applies to branch new projects, others (in previous release) expected to be in M1. http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Integrate_Early_and_Often I should emphasize, if people do not want to be in sim. release, that's fine. It is a voluntary choice, and does take some amount of extra work. So, it doesn't mean you are a "bad project" or anything if you decide not to. But, it is only common courtesy to keep us informed explicitly. Thanks, amp.b3aggrcon - org.eclipse.simrel.build cdt.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build emf-query2.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build emft-emffacet.b3aggrcon - org.eclipse.simrel.build epp-mpc.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gyrex.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build mat.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mdt-papyrus.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build rap.b3aggrcon - org.eclipse.simrel.build recommenders.b3aggrcon - org.eclipse.simrel.build rtp.b3aggrcon - org.eclipse.simrel.build scout.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build tcf.b3aggrcon - org.eclipse.simrel.build tm.b3aggrcon - org.eclipse.simrel.build ___ 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
Re: [cross-project-issues-dev] Hudson: error 400
Hello, Hudson is back to normal !? Regards, Grégoire - Mail Original - De: "Zeb Ford-Reitz" À: "Cross project issues" Envoyé: Mardi 21 Août 2012 07h45:44 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [cross-project-issues-dev] Hudson: error 400 For what it's worth, I'm able to view the configuration at that URL with no problems. Perhaps Hudson was having some problems that have been resolved since your last e-mail. - Zeb On 21.08.2012 01:11, Grégoire Dupé wrote: > Now, the loading of the page > https://hudson.eclipse.org/hudson/job/emffacet-nightly/configure never > finish. > > Regards, > Grégoire > > 2012/8/21 Grégoire Dupé: >> Yes, with the web page. (I'm just clicking) >> >> But the page >> "https://hudson.eclipse.org/hudson/job/emffacet-nightly/build?delay=0sec"; >> never stop to download and the top banner is not displayed. I assume >> that this cause something wrong in the build page. >> >> Regards, >> Grégoire >> >> >> 2012/8/21 David M Williams: >>> I see it is a parameterized build I assume you are providing values for >>> all the parameters? >>> HTH >>> >>> >>> >>> >>> From:Grégoire Dupé >>> To:cross-project-issues-dev@eclipse.org, >>> Date:08/20/2012 06:10 PM >>> Subject:[cross-project-issues-dev] Hudson: error 400 >>> Sent by:cross-project-issues-dev-boun...@eclipse.org >>> >>> >>> >>> >>> Hello, >>> >>> I've some difficulties to use Hudson. When I try to launch a build I >>> get the following error: >>> >>> """ >>> HTTP ERROR 400 >>> >>> Problem accessing /hudson/job/emffacet-nightly/build. Reason: >>> >>> This page expects a form submission >>> """ >>> >>> Does anybody has the same problem ? >>> >>> I'm not sure to be on time to deliver EMF Facet tomorrow. :-( >>> >>> Regards, >>> Grégoire >>> ___ >>> 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 >>> >> >> >> -- >> Grégoire Dupé >> R&D Engineer >> >> Mia-Software >> 4, rue du chateau de l'Eraudière - BP 72 438 >> 44324 Nantes cedex 3 >> FRANCE >> >> tel: +33 (0) 2 40 18 52 82 >> fax: +33 (0) 2 40 50 35 78 >> >> e-mail: gd...@mia-software.com > > -- BREDEX GmbH Mauernstr. 33 38100 Braunschweig Tel.: +49-531-24330-0 Fax: +49-531-24330-99 http: www.bredex.de Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst Amtsgericht Braunschweig HRB 2450 ___ 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
Re: [cross-project-issues-dev] Hudson: error 400
Now, the loading of the page https://hudson.eclipse.org/hudson/job/emffacet-nightly/configure never finish. Regards, Grégoire 2012/8/21 Grégoire Dupé : > Yes, with the web page. (I'm just clicking) > > But the page > "https://hudson.eclipse.org/hudson/job/emffacet-nightly/build?delay=0sec"; > never stop to download and the top banner is not displayed. I assume > that this cause something wrong in the build page. > > Regards, > Grégoire > > > 2012/8/21 David M Williams : >> I see it is a parameterized build I assume you are providing values for >> all the parameters? >> HTH >> >> >> >> >> From:Grégoire Dupé >> To:cross-project-issues-dev@eclipse.org, >> Date:08/20/2012 06:10 PM >> Subject:[cross-project-issues-dev] Hudson: error 400 >> Sent by:cross-project-issues-dev-boun...@eclipse.org >> >> >> >> >> Hello, >> >> I've some difficulties to use Hudson. When I try to launch a build I >> get the following error: >> >> """ >> HTTP ERROR 400 >> >> Problem accessing /hudson/job/emffacet-nightly/build. Reason: >> >>This page expects a form submission >> """ >> >> Does anybody has the same problem ? >> >> I'm not sure to be on time to deliver EMF Facet tomorrow. :-( >> >> Regards, >> Grégoire >> ___ >> 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 >> > > > > -- > Grégoire Dupé > R&D Engineer > > Mia-Software > 4, rue du chateau de l'Eraudière - BP 72 438 > 44324 Nantes cedex 3 > FRANCE > > tel: +33 (0) 2 40 18 52 82 > fax: +33 (0) 2 40 50 35 78 > > e-mail: gd...@mia-software.com -- Grégoire Dupé R&D Engineer Mia-Software 4, rue du chateau de l'Eraudière - BP 72 438 44324 Nantes cedex 3 FRANCE tel: +33 (0) 2 40 18 52 82 fax: +33 (0) 2 40 50 35 78 e-mail: gd...@mia-software.com ___ 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] Hudson: error 400
Yes, with the web page. (I'm just clicking) But the page "https://hudson.eclipse.org/hudson/job/emffacet-nightly/build?delay=0sec"; never stop to download and the top banner is not displayed. I assume that this cause something wrong in the build page. Regards, Grégoire 2012/8/21 David M Williams : > I see it is a parameterized build I assume you are providing values for > all the parameters? > HTH > > > > > From:Grégoire Dupé > To:cross-project-issues-dev@eclipse.org, > Date:08/20/2012 06:10 PM > Subject:[cross-project-issues-dev] Hudson: error 400 > Sent by:cross-project-issues-dev-boun...@eclipse.org > > > > > Hello, > > I've some difficulties to use Hudson. When I try to launch a build I > get the following error: > > """ > HTTP ERROR 400 > > Problem accessing /hudson/job/emffacet-nightly/build. Reason: > >This page expects a form submission > """ > > Does anybody has the same problem ? > > I'm not sure to be on time to deliver EMF Facet tomorrow. :-( > > Regards, > Grégoire > ___ > 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 > -- Grégoire Dupé R&D Engineer Mia-Software 4, rue du chateau de l'Eraudière - BP 72 438 44324 Nantes cedex 3 FRANCE tel: +33 (0) 2 40 18 52 82 fax: +33 (0) 2 40 50 35 78 e-mail: gd...@mia-software.com ___ 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] Hudson: error 400
Hello, I've some difficulties to use Hudson. When I try to launch a build I get the following error: """ HTTP ERROR 400 Problem accessing /hudson/job/emffacet-nightly/build. Reason: This page expects a form submission """ Does anybody has the same problem ? I'm not sure to be on time to deliver EMF Facet tomorrow. :-( Regards, Grégoire ___ 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] List of files on Eclipse Mirror servers
Hello, Thanks you for this information. This helps me to clean the MoDisco and EMF Facet directories. How can we get an update of this list (to check if my modification are useful) ? Regards, Grégoire - Mail Original - De: "Denis Roy" À: "Cross project issues" Envoyé: Mardi 19 Juin 2012 16h33:27 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] List of files on Eclipse Mirror servers To help you clean up older builds and files from the Eclipse download server, I've compiled a list of files that are actually sync'ed to our mirrors. http://download.eclipse.org/technology/phoenix/download.eclipse.org-filelist.txt.gz I each project to look at the file list, and either remove files that are no longer needed, or move older releases[1] to the archives. Thanks, Denis [1] http://wiki.eclipse.org/IT_Infrastructure_Doc#Downloads ___ 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
Re: [cross-project-issues-dev] Failures in the Hudson Juno run.aggregator job?
Hello, In the first failing build (https://hudson.eclipse.org/hudson/job/juno.runAggregator/516/), we can see that the only change is the MoDisco 0.10.0 RC4 delivery. I'm not used to read the aggregator log. Does anyone understand what is the problem ? If MoDisco is causing the problem. We can switch back to the MoDisco 0.10.0 RC3 (no change in the source repository have been done since RC3). Regards, Grégoire - Mail Original - De: "Jeff Johnston" À: "Cross project issues" Envoyé: Mercredi 13 Juin 2012 17h33:04 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [cross-project-issues-dev] Failures in the Hudson Juno run.aggregator job? I noticed that the Juno run.aggregator job is failing on Hudson after a bunch of RC4 changes. Is someone assigned to each of the issues (other than David)? -- Jeff J. ___ 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
