[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [papyrus-rt-dev] Papyrus-RT Installer ready to use
|
Thanks for getting on this so quickly, Ernesto!
This error looks like a problem in the setup. And in the first launch of this installer, I would expect you to see only one Papyrus-RT product, which is still 0.7. I suspect somehow it is picking up the wrong index for you.
There's a new feature now available in the hamburger menu that lets you switch to another index. Can you look in there to see which index you have and, which product catalogues you have selected in that index, and if it's not the Papyus-RT index then what happens if you switch to that?
cW
On October 20, 2016 at 16:28:23, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Looks very nice! I gave it a spin (on mac) but I ran
into trouble:
1) There are two identical "Papyrus-RT" entries in the main
menu, I don't know if they are duplicates or they are supposed to
be different.
2) I tried both and ran into the same error: Failed to
install:
[2016-10-20 16:25:28] ERROR: org.eclipse.equinox.p2.director
code=10053 Cannot complete the install because one or more required
items could not be found.
at
org.eclipse.oomph.util.OomphPlugin.coreException(OomphPlugin.java:280)
at
org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.resolve(ProfileTransactionImpl.java:425)
at
org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.commit(ProfileTransactionImpl.java:337)
at
org.eclipse.oomph.setup.p2.impl.P2TaskImpl.perform(P2TaskImpl.java:729)
at
org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3151)
at
org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3079)
at
org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3060)
at
org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:2960)
at
org.eclipse.oomph.setup.internal.installer.SimpleVariablePage.installPerform(SimpleVariablePage.java:1271)
at
org.eclipse.oomph.setup.internal.installer.SimpleVariablePage.access$31(SimpleVariablePage.java:1148)
at
org.eclipse.oomph.setup.internal.installer.SimpleVariablePage$20.run(SimpleVariablePage.java:1093)
ERROR: org.eclipse.equinox.p2.director code=0 Software
being installed: artificial_root 1.0.0.v1476995126661
ERROR: org.eclipse.equinox.p2.director code=0 Missing
requirement: artificial_root 1.0.0.v1476995126661 requires
'org.eclipse.emf.compare.egit.feature.group 0.0.0' but it could not
be found
PS: The icon is not that bad ;)
Hi, Team,
In our release readiness call earlier this week,
I opined that I did not feel the Oomph-based Papyrus-RT Installer
was ready for prime time. However, since then, several
further developments have occurred:
- Ed Merks fixed our most significant issues
with customization of window title, icon, and menu action branding
for Papyrus-RT in the Eclipse Installer (in the Oomph project)
- I implemented signing of the Mac installer
RCP to satisfy the MacOS Gatekeeper
- I implemented creation of the self-extracting
executable installer for Windows platform, also signed with the
Eclipse Foundation certificate
I also determined that the problems I was seeing with the Mac
installer showing no information in the About dialog and wanting an
unnecessary software self-update were caused by the new App
Translocation feature in the MacOS Sierra version of the
Gatekeeper. This affects all self-updating software
(including native apps using frameworks like Sparkle) and, of
course, all EPPs and other RCPs provided by Eclipse. And it
is easily evaded after download anyways. Therefore, this in
no way hinders any publication of this installer.
So, I think now the installer is ready for
general use, but of course it won’t have the 0.8 Papyrus-RT release
yet in its catalogue because that doesn’t exist. It does,
however, have the 0.7.x releases and seems to be able to install
them.
To take the installer for a spin, download
the variant appropriate to your platform from
A word of caution: try to avert your
eyes from the installer app icon. I hacked it together,
myself, and it is hideous. I am no artist.
Note also that the Windows installer binary
currently shows the Eclipse Installer icon, not the Papyrus-RT
installer, in the Windows Explorer. This is because so far we
are re-using the extractor binary from the Eclipse Installer and it
isn’t worth trying to figure out how to replace it until we have a
good icon.
If we are interested in promoting this
installer as a distribution method for the 0.8 release, then I
should note that it is currently built on pre-release nightlies of
the Oomph installer framework because the latest release does not
provide the customizability that we need (neither in branding nor
managing custom indices). So we should understand that this
isn’t a “release build” of the installer and I don’t know when the
next Eclipse Installer release will be on which we can base a
“release” of our installer.
_______________________________________________
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