Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mdt-papyrus.dev] New problems installing Papyrus with Oomph
Hi. I think there is a problem with the papyrus.setup model for Oomph. The installer fails when attempting to install Papyrus>Extras>UML-RT.

What I try to do is the following:

1) Download the latest version of the Oomph installer
2) remove ~/.p2 and ~/.eclipse to ensure I have a clean slate
3) Run Oomph
4) Select Eclipse Standard/SDK and accept the defaults
5) Select Papyrus>Extras>UML-RT
6) Set the variables
7) Start the bootstrap

Then it fails (see the beginning of the exception attached; the full exception is *very* long). 

The exception always occurs after the line

[14:44:45] Downloading org.eclipse.epp.package.standard.feature

and it always points to a problem with a repository: (http://update.eclemma.org/plugins/com.mountainminds.eclemma.asm_2.3.1.201405111647.jar)

This problem does not occur if I don't select the UML-RT component, so the problem must be there. The strange thing is that yesterday it worked just fine. Has there been an update there? How can this be fixed?

Thanks



On Tue, Jul 29, 2014 at 12:21 PM, Christian W. Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Team,

The Eclipse Oomph Installer now provides a set-up model for Papyrus, making it easier than ever to get a complete Eclipse workbench up and running for development on the Papyrus source code.  Just download the Oomph Installer [1] and follow the simple wizard to create your IDE and import the Papyrus source projects that you want to work on.

Pick any product you like on the first page, but be sure it's the Luna release of that product.  On the second page, expand Eclipse.org / Papyrus to see the various components that you can import to work on.  Pick any combination of the leaf-level sub-(sub-)projects, even all of them if you like.  In the third page where you specify variables such as install location, workspace location, git clone, etc. be sure to choose "Luna" for the Target Platform.  This ensures that you will be set up to work on Papyrus Luna (SR1), which is the only development stream currently supported by the setup model (until Mars development gets under way).

Contributing your changes is easy because Oomph will clone the Papyrus Git repository for you and configure Gerrit push.

Amongst possibly other details, the setup model configures:

  • your IDE with all of the tools needed to edit and build the source projects you choose
  • your workspace with a Git clone and the source projects imported from it that you choose
  • a PDE target that includes all of the dependencies required by Papyrus plus the latest nightly build of Papyrus, itself, so that you can import only a subset of the (many) source projects but still run the complete Papyrus toolset in a run-time workbench
  • Mylyn queries for current open bugs and enhancements in the Papyrus bugzilla database
  • Mylyn queries for the status of the latest Papyrus automated builds, including tests
  • Mylyn queries for open Gerrit reviews
  • preferences enforcing the Papyrus standard compiler and code formatter/template settings

So, try it out!  And raise bugs if you see any problems in the setup configuration.

Thanks,

Christian


Pasted Graphic.tiff
Pasted Graphic 1.tiff

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev



--
Ernesto Posse
Zeligsoft.com

[13:39:34] An error was detected while performing the engine operation and the changes are being rolled back. See the log for details.
[13:39:34] ERROR: org.eclipse.equinox.p2.engine code=4 An error occurred while collecting items to be installed
  at org.eclipse.oomph.util.AbstractOomphPlugin.coreException(AbstractOomphPlugin.java:191)
  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl$1.commit(ProfileTransactionImpl.java:405)
  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.commit(ProfileTransactionImpl.java:309)
  at org.eclipse.oomph.setup.p2.impl.P2TaskImpl.perform(P2TaskImpl.java:692)
  at org.eclipse.oomph.internal.setup.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:2372)
  at org.eclipse.oomph.internal.setup.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:2328)
  at org.eclipse.oomph.internal.setup.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:2318)
  at org.eclipse.oomph.internal.setup.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:2258)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$7.run(ProgressPage.java:377)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9$1.run(ProgressPage.java:454)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
  ERROR: org.eclipse.equinox.p2.engine code=0 session context was:(profile=_Users_eposse_Experiments_Oomph_ides-root_ide0_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
  ERROR: org.eclipse.equinox.p2.transport.ecf code=1002 Unable to read repository at http://update.eclemma.org/plugins/com.mountainminds.eclemma.asm_2.3.1.201405111647.jar.

Back to the top