Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Re: Oomph setup --> lots of compiler issues
Re: Oomph setup --> lots of compiler issues [message #1653963] Fri, 06 March 2015 13:17
Christian Damus is currently offline Christian DamusFriend
Messages: 1270
Registered: July 2009
Location: Canada
Senior Member

Hi, Johan,

Thanks for taking an interest in getting involved with Papyrus and the
setup model.

I have copied the Oomph newsgroup on my reply to see whether the
experts there can be of help. Find other responses in-line, below.

HTH,

Christian


On 2015-03-06 12:24:13 +0000, Johan Van Noten said:

> Short description:
> When I use the Oomph setup to create a Luna development environment,
> everything goes smoothly. After a restart of the environment, a rebuild
> is triggered and results in >600.000 errors.
> The only way I found to fix it, is a reload of the target platform.

Re-load in what way? Run the Targlet configuration task again, or just
hit the "Reload" button in the PDE Target preference page?


> After the next restart, the scenario repeats itself.
>
> My guess was that Oomph results in a fully functional development environment.

It does seem to work for most of us, but I'm not sure how up-to-date we
are Oomph-wise. I suppose you're on the very latest public build of
Oomph?


> So, either I do something wrong or the Papyrus Setup model for Oomph
> shows some hiccups.
>
> Longer description: (reproduction scenario)
> (I first deleted my bundle pool c:\users\myname\.p2 to avoid 'bad history')

Is that even safe to do? I've never tried doing that.


> * Download the Oomph installer (I use version 1.1.0 Build 941 on Win x64)
> * Select "Eclipse Standard" (I also tried "Eclipse Modeling Tools" to
> no avail.)

Either of these should provide a good basis for a Papyrus development
environment (I usually take the standard package, myself, because then
I only get what I really need for Papyrus).


> * Fill variables:
> - Product version "Latest Release (Luna)" 64-bit
> - VM: ... jdk8 (a 64-bit version)
> * Next
> * Select Papyrus | Main | all subprojects
> * Verify that all are on the stream "streams/1.0-maintenance (Luna/1.0.x)"

All good.


> * Next
> * Fill variables (show all variables):
> - Installation location = d:\Prog\OomphLuna
> - Workspace location = d:\Local\Dev\OomphLuna

Not C: drive? My Windows experience is so long ago now that I vaguely
recall some tools behave strangely on assumptions of paths being in the
C: drive, but I wouldn't expect Oomph to exhibit any such trouble.


> - Target Platform = Luna

Yep.


> - Eclipse UserID etc (Authenticate returns that my password is
> invalid, but I can perfectly signon with these credentials on
> https://dev.eclipse.org/site_login/)
> * Next
> * All Bootstrap tasks are ticked.
> * Additionally, only "Mirrors" at the bottom is ticked.
> * Finish
> * After some time, without any issues, Eclipse launches
> * Finish the bootstrap.
> * Close the new Eclipse's Welcome screen
> * Click the two revolving arrows in front of "Executing Startup Tasks"
> to show progress
> * Wait... wait a bit more...
> * This completes without errors. Click Finish.
> * The active Eclipse starts building the workspace.
> * You now hit bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=461492,
> causing 1 error.
> Fix it by putting the following in the affected manifest.mf file:
> Bundle-ManifestVersion: 2
> Bundle-Name: Facet Custom Editor
> Bundle-SymbolicName:
> org.eclipse.papyrus.emf.facet.custom.metamodel.editor.doc;singleton:=true
>
> Bundle-Version: 1.0.2.qualifier
> Require-Bundle: org.eclipse.help
> Bundle-Vendor: Eclipse Modeling Project
> * Build now completely succeeds

This all sounds peachy.


> * Restart the current session (File | Restart)
> * Some activities start automatically: Setup check , Removing lots of
> projects from "Xtext index", Building workspace
> * Finally, end up with 611.302 errors (and quite some warnings)

I don't see how anything in the setup model could cause this. It
shouldn't be possible even for a misconfigured setup model to break the
PDE. Hopefully somebody in the Oomph forum recognizes this problem and
can help!


> * Optional: Clean all workspace projects - rebuild starts - same result
> * Go to Window | Preferences | Plug-in development | target platform
> * Currently "Modular Target" is listed as active.
> * Select it, Reload, Ok

Ah, that answers that.


> * Message box appears:
> "You have selected a target with a newer version than your current
> Eclipse installation. This can cause unexpected behaviour in PDE.
> Please use a newer version of Eclipse."

That doesn't make sense. You've based your Oomph installation on Luna
and you've imported the Luna stream of the setup model, so everything
in your PDE Target should be Luna.

Perhaps this is the problem.

Can you confirm that your org.eclipse.core.resources and
org.eclipse.pde.core plug-ins in your install and in your PDE Target
are both the Luna version?


> * Press ok
> * Rebuild starts
> * No more build errors
>
> * Do File | Restart and you are back to 611.302 errors after a rebuild.
Previous Topic:Add a new project in Catalog
Next Topic:Help cloning git repo
Goto Forum:
  


Current Time: Tue Sep 24 09:21:53 GMT 2024

Powered by FUDForum. Page generated in 0.02679 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top