Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365752 - Build succeeds when using "require bundle" but fails when using "import package"
Summary: Build succeeds when using "require bundle" but fails when using "import package"
Status: RESOLVED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-06 10:33 EST by Davy Meers CLA
Modified: 2021-04-28 16:54 EDT (History)
0 users

See Also:

Attachments
Failing minimal project that uses import package (3.89 KB, application/octet-stream)
2011-12-06 10:55 EST, Davy Meers CLA 		no flags Details
Succeeding minimal project that uses require bundle (8.62 KB, application/octet-stream)
2011-12-06 10:55 EST, Davy Meers CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Davy Meers CLA 2011-12-06 10:33:38 EST 
Build Identifier: 20110916-0149

When using "import package" to specify a dependency the build fails with a resolution error.

When building the same project but using "require bundle" instead the build succeeds.

I created a minimal example that shows the problem.
For this example i use an implicit target platform but the problem also occurs when using an explicit target platform file.

Reproducible: Always
Comment 1 Tobias Oberlies CLA 2011-12-06 10:46:56 EST 
p2 bug 360659?

We really need to fix the debug output - everything is a "resolution error"...
Comment 2 Davy Meers CLA 2011-12-06 10:55:08 EST 
Created attachment 207998 [details]
Failing minimal project that uses import package
Comment 3 Davy Meers CLA 2011-12-06 10:55:49 EST 
Created attachment 207999 [details]
Succeeding minimal project that uses require bundle
Comment 4 Davy Meers CLA 2011-12-06 10:58:57 EST 
I think it is indeed that p2 bug.
Comment 5 Davy Meers CLA 2011-12-06 11:06:09 EST 
(In reply to comment #4)
> I think it is indeed that p2 bug.

Update: It is indeed that bug. By adding the attribute "core" to the import package that build succeeds too.



This bug can be closed.
Comment 6 Tobias Oberlies CLA 2011-12-09 03:26:23 EST 
This still is a Tycho problem (because Tycho includes p2), but if you are satisfied with the explanation, we could close this issue as "invalid". It's definately not "fixed".
Comment 7 Davy Meers CLA 2011-12-12 07:42:35 EST 
(In reply to comment #5)
> Update: It is indeed that bug. By adding the attribute "core" to the import
> package that build succeeds too.

As a follow-up: in the end adding the attribute was not a solution and i had to use require bundle.

(In reply to comment #6)
> This still is a Tycho problem (because Tycho includes p2), but if you are
> satisfied with the explanation, we could close this issue as "invalid". It's
> definately not "fixed".

I am satisfied with the explanation.
It would be useful if tycho could provide a more descriptive error message.
Do you want me to create a bug for that?

ps: The selection of Resolved / Fixed was by accident.
Comment 8 Tobias Oberlies CLA 2011-12-13 05:37:30 EST 
(In reply to comment #7)
> It would be useful if tycho could provide a more descriptive error message.
> Do you want me to create a bug for that?
Yes, this would be useful, thanks!