Community
Participate
Working Groups
We use version in form of "6.3.0-featureName-SNAPSHOT" in maven pom for feature branches. There is no way to specify this in Bundle-version. Tycho checks the bundle version for ".qualifier" ending for snapshots and everything else should be numbers split by ".". There is no way to specify an additional featureName suffix. This have to be fixed. For release versions it works fine, because tycho just checks version strings for equality in such case.
I lean towards closing this as WONTFIX. Fancy bundle qualifier strings like featureName-20130401-1234 will result in surprising/undesired build results if artifacts with different qualifier patterns are installed in local repository. Problems like this will be very hard to troubleshoot and ultimately result in additional support traffic for tycho developers.
"6.3.0-featureName-SNAPSHOT" (or even "arbitrarystring-SNAPSHOT") seems to be interpreted by Maven as snapshot version. So as long as the part before the "-SNAPSHOT" can be fit into the OSGi versioning scheme, we could theoretically allow it in Tycho. In the build result, bundle version of a module with "6.3.0-featureName-SNAPSHOT" Maven version would be "6.3.0.featurename-<buildqualifier>" (or possibly with a dot instead of the dash). But what should be the version in the sources? "6.3.0.qualifier" or "6.3.0.featurename-qualifier"? (In reply to comment #0) > This have to be fixed. I disagree. If we implement this, this would be an enhancement. Tycho never promised to support arbitrary Maven versions. We can leave this open as enhancement, but don't expect that this will be addressed by the committers any time soon. Related: Bug 382482
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.
