I believe we are as complete as we are going to be, for Luna SR1 RC1, and
Mars M1.
I've disabled the aggregation jobs, until Friday, to avoid confusion while
EPP finishes up.
Remember that Mars M1 (.../releases/staging) will be promoted to
.../releases/mars, on Friday, approximately 9 or 10
Folks,
And we backed stuff out. The other issue is fixed, but another issue
came up! We'll try to get our CBI build working properly for RC2.
FWIW,
- Carl Anderson
WTP Build guy
|>
| From: |
|>
>
Folks,
We just updated the WTP contribution. Our initial attempt failed due
to bug 442169, but after a respin that issue appears to be fixed.
FWIW,
- Carl Anderson
WTP Build guy
|>
| From: |
|>
>-
I just re-enabled those GEF4 features that only depend on EMF/Xtext but not on
JavaFX. In case the e(fx)clipse contribution is yet added to the aggregation, I
assume you might safely re-enable the remaining 6 GEF4 features as well.
Cheers
Alexander
Am 20.08.2014 um 21:08 schrieb David M William
Hi Dave, the emf.transaction was a indeed a typo and you are correct with
your change.
The gmf.runtime M1 build was pushed at right around the same time you were
updating the b3aggrcon. I have just fixed with the correct b3aggrcon file.
Cheers...
Anthony
From: David M Williams
To: cro
Been a busy few days!
I think we are on the verge of getting some "green" builds again, but
wanted to be sure to mention some "hacks" I had to make:
For Luna
I disabled
mylyn-docs-intent.b3aggrcon
(I also removed "eclipselink" which I hope doesn't surprise them, as
they were not particip
Compiled 2014-08-20T12:07
build.eclipse.org
-> Usage exceeding 1GB for: Hudson master jobs and workspace (2014-08-20T10:00)
3.6G gef4-master
2.8G papyrus-trunk-extra-nightly-tests
2.4G papyrus-trunk-nightly
2.4G papyrus-master-tests-failures
2.1G osee-dev
1.6G emf-cdo-m
You need to create a release record in the PMI:
https://projects.eclipse.org/projects/technology.efxclipse/create-release
Wayne
On 20/08/14 04:46 AM, Tom Schindl wrote:
Hi,
e(fx)clipse would like to join the Mars release as a +3 component
because we depend on Xtext who is +2.
Our current pla
To move the code out of the project, you need to do a restructuring
review. Restructuring reviews are relatively simple affairs that require
you describe (as concisely as possible) what needs to to change and why.
To restructure by moving, you need a project to move the code into.
This could b
While you're at it, maybe it would be interesting to integrate e(fx)clipse
in a package? Maybe the Java package? A bug report at [1] could help
starting a discussion about this ;-)
[1]
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPP&component=java-package
Thanks,
Markus
On Wed, Aug 20, 2
Hi,
I'm fine with contributing our runtime-feature as +1 and the IDE-Feature
as +3.
Tom
On 20.08.14 14:06, Alexander Nyßen wrote:
> I added the following efxclipse.b3aggrcon to my local simrel build for
> testing purposes and validated that with the e(fx)clipse runtime feature
> in place, those
I added the following efxclipse.b3aggrcon to my local simrel build for testing
purposes and validated that with the e(fx)clipse runtime feature in place,
those GEF4 features depending on JavaFX could now indeed be resolved (i.e. the
aggregation could be validated).
http://www.omg.org/XMI";
x
Hi,
Memory Analyzer (tools.mat) will be participating in Mars.
The offset is like last year +3.
Release record: https://projects.eclipse.org/projects/tools.mat/releases/1.5.0
Krum
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclip
Hi,
ATL will be participating in Mars. The offset will be +2.
Release record:
https://projects.eclipse.org/projects/modeling.mmt.atl/releases/3.6.0
William
<>___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change yo
Hi,
We'll join as +3 but I can not promise we manage to contribute to M1
already because I need to make myself familiar with the process, ... .
Tom
On 20.08.14 10:28, Alexander Nyßen wrote:
> Tom,
>
> at what offset can we expect the e(fx)clipse contribution? Will you
> contribute something to
Hi,
e(fx)clipse would like to join the Mars release as a +3 component
because we depend on Xtext who is +2.
Our current plan is to contribute e(fx)clipse 2.0 because this is the
first time we are joining (I need to make myself familiar with the
process) I'm not sure we manage to contribute to M1
Tom,
at what offset can we expect the e(fx)clipse contribution? Will you contribute
something to M1?
Cheers
Alexander
Am 18.08.2014 um 21:59 schrieb Alexander Nyßen :
> I temporarily disabled all GEF4 features that (directly or indirectly) depend
> on JavaFX. I do not know what is the inten
Hi Wayne,
Thanks for the answer.
Their are several Git repositories within in the e4 project and I would
like to have the e4 tools Git repository available in the Mars update site.
Sounds like we would need to migrate e4 tools to a new project. Would it
be possible to move the e4 tools (they ha
18 matches
Mail list logo
