Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355797 - [Releng] Build of 0.8.X branch is performed with trunk plugins
Summary: [Releng] Build of 0.8.X branch is performed with trunk plugins
Status: CLOSED INVALID
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.0   Edit
Hardware: All All
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Vincent Hémery CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-25 03:27 EDT by Vincent Hémery CLA
Modified: 2011-08-25 04:59 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Hémery CLA 2011-08-25 03:27:03 EDT
Integration build of 0.8.X branch does not rely on the branch's plugins, but downloads trunk plugins instead.

After a plugin has been integrated on the branch only, the build failed with the following error :
     [java] ERROR   [0234] : No suitable provider for component org.eclipse.papyrus.modelexplorer.resourceloading:osgi.bundle was found in resourceMap file:/opt/users/hudsonbuild/workspace/cbi-papyrus-0.7-nightly/releng/org.eclipse.mdt.papyrus.releng.buckminster/build.rmap
     [java]   ERROR   [0234] : No suitable provider for component org.eclipse.papyrus.modelexplorer.resourceloading:osgi.bundle was found in searchPath sources
     [java]     ERROR   [0234] : Rejecting provider svn({0}/modeling/org.eclipse.mdt.papyrus/trunk/plugins/core/{1}?moduleAfterTag&moduleAfterBranch[file:///svnroot/modeling/org.eclipse.mdt.papyrus/trunk/plugins/core/org.eclipse.papyrus.modelexplorer.resourceloading?moduleAfterTag&moduleAfterBranch]): No component match was found

This error indicates that plugin is looked for on the trunk. Moreover, looking at the releng plugins in the 0.8.X branch, there is no doubt that most references are still to the trunk instead of the SVN branch.
Comment 1 Vincent Hémery CLA 2011-08-25 04:59:49 EDT
The error was due to a bad integration.