The ATL project will be participating in the Luna simultaneous release.
The release record can be found here [1]. ATL has an offset of +2.
[1] https://projects.eclipse.org/projects/modeling.mmt.atl/releases/3.5.0
Best regards,
attachment:
Hi all,
I send this email to announce and confirm that Papyrus will be part of the Luna
train. BTW, in this context, I want to let you know that Papyrus shall leave
the incubation phase and the team is targeting a version 1.0.
Best... Sébastien.
ok thanks :-)
On Tue, Sep 17, 2013 at 11:58 AM, Doug Schaefer dschae...@qnx.com wrote:
I get the same thing. So I gave up and made the changes directly to the
files using the text editor. Not good by any means.
From: Mark Russell mrruss...@google.com
Reply-To: Cross project issues
See
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg09818.html
I've tried the Kepler version and it seems to work fine. You need to use
near SR1 version of Eclipse SDK (and EGit, I'd assume) and the repo at
http://download.eclipse.org/modeling/emft/b3/updates-4.3 .
Was
I have a new machine since my last aggregation build for WindowBuilder. I'm
following
http://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build to
set up the simrel B3 Aggregation.
Everytime I try to install B3 I get this error:
Cannot complete the install because one or more
I get the same thing. So I gave up and made the changes directly to the files
using the text editor. Not good by any means.
From: Mark Russell mrruss...@google.commailto:mrruss...@google.com
Reply-To: Cross project issues
Hi,
The QVTO project will be participating in the Luna simultaneous release.
The release record can be found here [1]. QVTO has an offset of +2.
[1] http://projects.eclipse.org/projects/modeling.mmt.qvt-oml/releases/3.4.0
Best regards,
Sergey Boyko
Thanks for the tip! The patch scope is not set to a range in our repository
metadata.
patchScope
scope
requires size='1'
required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.jst.enterprise_ui.feature.feature.group' range='0.0.0'/
Konstantin,
We are doing something similar with patches in our product. I just did a few
quick tests and everything seems to work as expected for me with Kepler SR1
RC3. With a feature installed in a different version than targeted by our
patch - both higher or lower - the patch is rejected.
On
On 17.09.2013 20:59, Konstantin Komissarchik wrote:
Since the issue is still not fixed in p2 (seriously!?), what did you do for
a workaround in your patches?
Since I needed a fix quickly at that time, I patched our Buckminster-based
toolchain using the fix I attached to that bug.
I kind of
10 matches
Mail list logo
