Hi
Christian,
It is my
fault. After a few tries I forgot to check the top level element
(Papyrus-RT).
It works
now.
Thanks.
Are
all of his projects referencing the same Neon stream? Did he make sure to
choose Neon for the "Target Platform” setup variable? And also a Neon
version of the product on which to base the entire installation?
Mixing in any wrong
version of any of these components could lead to this problem.
cW
On 2 May, 2016 at 14:17:28, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Young-Soo tells me he's tried it now 3-4 times, and it's still
not working. Now it has this:
ERROR: org.eclipse.equinox.p2.director code=0 Software being installed:
artificial_root 1.0.0.v1462212810657
ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement:
artificial_root 1.0.0.v1462212810657 requires
'org.eclipse.papyrusrt.feature.feature.group 0.0.0' but it could not be
found
The strange thing is I tried it and it works for me.
I don't know what people working on tooling would prefer, but from the
codegen side, I think using the latest stable milestone build of Papyrus is
good enough.
Hi,
Some
Papyrus Neon bundles are version 1.2 because they don’t have API-breaking
changes and others are at 2.0 because they have API-breaking changes.
This
is probably just the usual case of trying to run the Oomph setup to pull
content from a p2 repository that is in the process of being replaced.
While the Papyrus build is publishing its repository, the repository is at
least partially non-existent and so an update from it will fail like
this.
If
the problem still occurs on a re-try ten minutes later, then maybe there’s a
problem in the Oomph set-up.
But,
the Oomph setup is currently referencing the Papyrus nightly build
repositories on the assumption that we need to keep up-to-date with Papyrus
development as closely as possible, given the intimate nature of our
dependency on that project. If Papyrus had a policy of publishing
weekly integration builds as many Eclipse projects do, that would help a lot
because then then we wouldn’t have these repositories that are temporarily
unavailable several times a day. Or, if the Papyrus-RT development
team is content with only picking up the latest stable milestone build of
Papyrus, we can change the setup model accordingly.
We seem to have a problem with the Oomph setup. See the
problem below.
Barry also had a very similar problem, but the error was a bit
different (see below after Young-Soo's e-mail).
They are both on Windows, and in both cases it seems like it's
trying to get Papyrus plugins with version 1.2.
Any ideas?
---------- Forwarded message --------- From:
Young-Soo Roh <youngsoo.roh@xxxxxxxxxxxxx> Date: Mon, May 2, 2016
at 1:00 PM Subject: Eclipse installer Papyrus RT dev installation
problem for Neon To: Ernesto Posse <eposse@xxxxxxxxxxxxx>
Following error was
occurred during the installation.
I followed steps from the wiki so wondering
if what is the problem.
Installation was done from Windows 10 64 bit
environment.
Checked options with Ernesto before starting
the installation.
ERROR: org.eclipse.equinox.p2.engine code=0 session context
was:(profile=""
phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null
--> [R]org.eclipse.papyrus.uml.ui.feature.feature.jar
1.2.0.201603231318,
action="">
ERROR: org.eclipse.equinox.p2.touchpoint.eclipse code=0 The
artifact file for
org.eclipse.update.feature,org.eclipse.papyrus.uml.ui.feature,1.2.0.201603231318
was not found.
Regards,
------ Barry's error trace -------
ERROR: org.eclipse.equinox.p2.director
code=0 Software being installed: artificial_root
1.0.0.v1462029709410
ERROR: org.eclipse.equinox.p2.director
code=0 Missing requirement: Customization Manager 1.2.0.201604300154
(org.eclipse.papyrus.customization
1.2.0.201604300154) requires 'bundle org.eclipse.pde [3.12.0,4.0.0)' but
it could not be found
ERROR: org.eclipse.equinox.p2.director
code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director
code=0 From: artificial_root 1.0.0.v1462029709410
ERROR: org.eclipse.equinox.p2.director
code=0 To: org.eclipse.papyrus.extra.dsml.validation.feature.feature.group
0.0.0
ERROR: org.eclipse.equinox.p2.director
code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director
code=0 From: Papyrus DSML Validation wizard (Incubation)
1.2.0.201604300154 (org.eclipse.papyrus.dsml.validation.wizard
1.2.0.201604300154)
ERROR: org.eclipse.equinox.p2.director
code=0 To: bundle org.eclipse.papyrus.customization
1.2.0
ERROR: org.eclipse.equinox.p2.director
code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director
code=0 From: Papyrus DSML Validation Feature (Incubation)
1.2.0.201604300154 (org.eclipse.papyrus.extra.dsml.validation.feature.feature.group
1.2.0.201604300154)
ERROR: org.eclipse.equinox.p2.director
code=0 To: org.eclipse.papyrus.dsml.validation.wizard
[1.2.0.201604300154]
--
Ernesto
Posse
Zeligsoft
_______________________________________________ papyrus-rt-dev
mailing list papyrus-rt-dev@xxxxxxxxxxx To change your delivery
options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list papyrus-rt-dev@xxxxxxxxxxx To change
your delivery options, retrieve your password, or unsubscribe from this list,
visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
No virus found in this
message. Checked by AVG - www.avg.com Version: 2016.0.7596 / Virus
Database: 4563/12151 - Release Date: 05/02/16
|