Bug 569943 - Target platform configuration <executionEnvironment>none</executionEnvironment> never used
Summary: Target platform configuration <executionEnvironment>none</executionEnvironmen...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-28 08:26 EST by Romain Bioteau 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 Romain Bioteau CLA 2020-12-28 08:26:21 EST
https://bugs.eclipse.org/bugs/show_bug.cgi?id=565298 introduce a new 'none' executionEnvironment but this environment is never used as 'none' executionEnvironment is also considered a custom profile.
See https://github.com/eclipse/tycho/blob/master/tycho-core/src/main/java/org/eclipse/tycho/core/ee/ExecutionEnvironmentConfigurationImpl.java#L129

Either adding 'none' as a known profile or check for 'ignoreExecutionEnvironment()' before 'isCustomProfile()' should fix the issue.
Comment 1 Mickael Istria CLA 2021-01-04 08:38:56 EST
(In reply to Romain Bioteau from comment #0)
> Either adding 'none' as a known profile or check for
> 'ignoreExecutionEnvironment()' before 'isCustomProfile()' should fix the
> issue.

Please submit a patch about this.
However, I'm not sure what you're trying to achieve is valid. In most cases, like building a bundle, an execution environment is useful or necessary because it's used to infer package capabilities and so on.
You typically need to only configure executionEnvironment=none for your eclipse-repository module only. EPP does that and it's working well.
Comment 2 Mickael Istria CLA 2021-04-08 18:13:54 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.