Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319472

Summary:	SDK build with source fails when branding plugin doesn't match feature plugin id
Product:	z_Archived	Reporter:	Miles Parker <milesparker>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Miles Parker

2010-07-10 17:07:12 EDT

This seems very similar to bug 302153. I'm trying to create a build that includes PDE generated source referenced from a feature. After excluding the source references with an advisorNode I get the build to work. But when generating the P2.site it then complains because (of course) it can't find the resource in the rmap. (As a work-around, I tried importing a different cquery that doesn't filter it but that doesn't work either.)

<code>INFO:  [end org.ascape.swing:eclipse.feature$5.6.0.qualifier#source.feature.jar]
org.ascape.swing.source:eclipse.feature: Using search path default
org.ascape.swing.source:eclipse.feature: Trying provider local(file:/Users/milesparker/.hudson/jobs/ascape/workspace/buckminster.output/org.ascape.swing_5.6.0-eclipse.feature/source.jar/[file:/Users/milesparker/.hudson/jobs/ascape/workspace/buckminster.output/org.ascape.swing_5.6.0-eclipse.feature/source.jar/])
org.ascape.swing.source:eclipse.feature: Found match 
org.ascape.swing.source:eclipse.feature: Using provider local(file:/Users/milesparker/.hudson/jobs/ascape/workspace/buckminster.output/org.ascape.swing_5.6.0-eclipse.feature/source.jar/[file:/Users/milesparker/.hudson/jobs/ascape/workspace/buckminster.output/org.ascape.swing_5.6.0-eclipse.feature/source.jar/])
org.ascape.swing.source:eclipse.feature: Resolution attempt ended with exception: Provider local(file:/Users/milesparker/.hudson/jobs/ascape/workspace/buckminster.output/org.ascape.swing_5.6.0-eclipse.feature/source.jar/): Missing CSpec source required by component type eclipse.feature
org.ascape.swing.source:eclipse.feature: No provider was found that could resolve the request
Doing full workspace refresh
Waiting for jobs to end
No suitable provider for component org.ascape.swing.source:eclipse.feature was found in resourceMap null
[0]No suitable provider for component org.ascape.swing.source:eclipse.feature was found in searchPath default
[0.2]Resolution attempt ended with exception: Provider local(file:/Users/milesparker/.hudson/jobs/ascape/workspace/buckminster.output/org.ascape.swing_5.6.0-eclipse.feature/source.jar/): Missing CSpec source required by component type eclipse.feature
Caused by: [0.2][0.2]Provider local(file:/Users/milesparker/.hudson/jobs/ascape/workspace/buckminster.output/org.ascape.swing_5.6.0-eclipse.feature/source.jar/): Missing CSpec source required by component type eclipse.feature
Archiving artifacts
Finished: FAILURE</code>

Comment 1 Miles Parker

2010-07-10 18:53:51 EDT

Some more information on this one. First the only thing unusual that I noticed that might be helpful is that the name of the branding plugin for one of my features is not the same as the name of the source feature. But that's pretty common I think. What might be messing something up is that the branding plugin has an internal segment different. So the feature is org.ascape.swing and the plugin is org.ascape.ui.swing.

Looking at the build output I found that the contents of the bad source feature org.ascape.swing contained the jar(s) from the previous build.

Seeing this, I added a buckminster.clean before the initial run and that solved the problem, so it looks like somehow the source build isn't getting rid of the prior builds correctly.

Comment 2 Miles Parker

2010-07-10 19:36:43 EDT

OK, I'm able to verify this with another build. I can confirm that the issue is that the branding plugin isn't the same name as the feature plugin. Changing name of bug to reflect.

As a note, this is not an uncommon usage..it's convenient to put branding information within an existing appropriate plugin, e.g. o.e.myproject.component.core for o.e.myproject.component feature instead of creating a seperate branding plugin for a small feature that might only have a few plugins total.