Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 271077 - Galileo build fails due to org.eclipse.emf.activities
Summary: Galileo build fails due to org.eclipse.emf.activities
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Cross-Project (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Cross-Project issues CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-02 23:15 EDT by David Williams CLA
Modified: 2009-04-06 10:23 EDT (History)
2 users (show)

See Also:


Attachments
Patch with my changes (3.21 KB, patch)
2009-04-05 17:32 EDT, Dave Steinberg CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2009-04-02 23:15:10 EDT
Specifically:
 Unable to find plug-in: org.eclipse.emf.activities_0.0.0. Please check the error log for more details.


The main build (sequence of director calls) finishes, and then error pops up while trying to "build a product". 

Only difference from previous runs (that worked) and this one was the inclusion of buckminster ... and I doubt they are specifying this specific bundle. :) 

So ... I suspect something else changed ... on an emf update site?
Comment 1 David Williams CLA 2009-04-02 23:32:22 EDT
I see now that "davidms" change the galileo map file, plugin.xml, and feature.xml

!*** EMF Capabilities *************************************************************
plugin@org.eclipse.emf.activities=HEAD,:pserver:anonymous@dev.eclipse.org:/cvsroot/modeling,,org.eclipse.emf/org.eclipse.emf/examples/org.eclipse.emf.activities



Hmmm, I wonder which part of "do not change anything" is not clear. 

Dave, do you read the cross-project list? 
If not, please do. At least my posts :) 
That's our communication channel for build related matters and anyone releasing to galileo is required to subscribe. 

Thanks, 



Comment 2 David Williams CLA 2009-04-02 23:42:24 EDT
BTW, I'm sure you'll notice, I reverted all these activity related changes. 

Please keep them around for when we give "new content" signal ... hopefully mid next week. 

Thanks. 

Comment 3 Dave Steinberg CLA 2009-04-03 10:33:49 EDT
David,

Apologies.

Yup, I read your every utterance on the cross-project list, and when you requested no more changes, I asked Nick to disable EMF's automatic per-build contributions. So there's no good explanation for why that request slipped my mind yesterday.

Once again, sorry for causing you trouble.
Comment 4 David Williams CLA 2009-04-04 23:26:56 EDT
Dave, if you are working this weekend, feel free to re-commit your capabilities. 

If not (that is, if you read this on Monday) maybe best to supply them here as a patch so they can be applied at a time when not much else is being tested. 

I'm not sure why it failed the first time, so be sure to double check everything. But, honestly, I'm not sure exactly how this build works, so might have been a timing issue (that is, one project that required it was checked out after the project that provides it). 

Comment 5 Dave Steinberg CLA 2009-04-05 17:32:09 EDT
Created attachment 130951 [details]
Patch with my changes

Here are the changes that broke Galileo last week. I double checked and I don't see anything obviously wrong. But then, I'm just following a receipe (http://wiki.eclipse.org/Galileo_Capabilities), so I don't have any particular insights.

Looking at the log for the failed build, I see that the first related error appears in fetchElement:

[exec] [eclipse.fetch] Missing directory entry: plugin@org.eclipse.emf.activities.
[exec] [eclipse.fetch] Missing directory entry: bundle@org.eclipse.emf.activities.

Then I see there's no FetchFromCVS that gets the plug-in, whereas for org.eclipse.rse.ui.capabilities, for example, which works, there is.

And then, of course, failing to get the plug-in from CVS no doubt causes the real error:

[exec] /opt/public/galileo/build/galileo/basebuilder/eclipse/plugins/org.eclipse.pde.build_3.5.0.v20090312-1500/scripts/genericTargets.xml:96: Unable to find plug-in: org.eclipse.emf.activities_0.0.0. Please check the error log for more details.
Comment 6 Dave Steinberg CLA 2009-04-05 17:41:32 EDT
David,

I guess I'll just try committing again and kicking off a build. Maybe it was just a timing issue, as you suggested?
Comment 7 Dave Steinberg CLA 2009-04-05 17:50:04 EDT
Well, that was quick.
https://build.eclipse.org/hudson/job/galileo.build/204/artifact/galileo.build.log.txt

Umm...okay, who knows what they're doing?  (Not me, clearly.)
Comment 8 David Williams CLA 2009-04-06 02:56:45 EDT
(In reply to comment #7)
> Well, that was quick.
> https://build.eclipse.org/hudson/job/galileo.build/204/artifact/galileo.build.log.txt
> 
> Umm...okay, who knows what they're doing?  (Not me, clearly.)
> 

Did you run "generate" first? I did, and then hit "build" and it completed fine, including emf.activities. 

I have to say though ... if you want to be consistent, shouldn't that be "capabilities"? 

Comment 9 Dave Steinberg CLA 2009-04-06 10:16:19 EDT
Thanks David. I'm glad it's not breaking anything anymore.

Regarding the name, we already had a previously existing activities/capabilities example plug-in with that name, and I just adapted it slightly for Galileo. It didn't seem particularly important to change the ID to be consistent. Do you think it is?
Comment 10 David Williams CLA 2009-04-06 10:23:07 EDT
(In reply to comment #9)
> Thanks David. I'm glad it's not breaking anything anymore.
> 
> Regarding the name, we already had a previously existing
> activities/capabilities example plug-in with that name, and I just adapted it
> slightly for Galileo. It didn't seem particularly important to change the ID to
> be consistent. Do you think it is?
> 

Nah, not very important. Not if it already existed. Just my opinion. Other opinions welcome.