Bug 467216 - Add a wildcard syntax for adding reactor projects to the target platform
Summary: Add a wildcard syntax for adding reactor projects to the target platform
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 393053
  Show dependency tree
 
Reported: 2015-05-13 09:41 EDT by Tobias Oberlies CLA
Modified: 2021-04-28 16:52 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Oberlies CLA 2015-05-13 09:41:58 EDT
There are cases in which we cannot automatically detect that a Tycho project needs to have a certain other reactor project in its target platform. Examples:
* An eclipse-feature includes a bundle, but that bundle is built with a different technology, e.g. the maven-bundle-plugin
* An eclipse-repository wants to include bundles with a query based on attributes that are not known yet at build order time.

To still get these reactor projects into the current project's target platform, one can declare a POM dependency. However this may be inconvenient in case of large reactors.

So instead (or additionally), there should be an Tycho-specific syntax for "adding reactor projects to the target platform". This syntax should allow wildcards, e.g. to get all artifacts for a certain groupId or all artifacts of a certain packaging type.
Comment 1 Mickael Istria CLA 2021-04-08 18:11:41 EDT
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse/tycho/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.