[
https://issues.jboss.org/browse/LOCUS-13?page=com.atlassian.jira.plugin.s...
]
Mickael Istria commented on LOCUS-13:
-------------------------------------
{quote}when I used other builds using reproducible version qualifiers it was not possible
to build without committing all code first. Very tedious to work with.{quote}
This is not really an issue with reproducible version qualifier, but with Git-based
timestamps, that we've already been using for a year and half in Locus, so this is a
separate thing.
{quote}For me SNAPSHOT makes perfect sense for a build for testing, but when doing the
release we shouldn't ever have SNAPSHOT in this so not sure I follow the
problem.{quote}
The principle of reproducible version qualifier is that they also reuse artifacts from
baseline when available.
https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers
If we put SNAPSHOT in testing, then testing won't consume artifacts from baseline
(that wouldn't be SNASPHOTs), and the output would be too far from the output of a
release.
Build number in qualifier are against reproducible version qualifier
--------------------------------------------------------------------
Key: LOCUS-13
URL:
https://issues.jboss.org/browse/LOCUS-13
Project: JBoss Tools Locus
Issue Type: Enhancement
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Critical
Fix For: 1.2.0
We did set up git-based reproducible qualifiers but in the other end, we have the
qualifier always changing because it contains the BUILD_NUMBER.
Those metadata should not be part of the qualifier, but should instead be in a future
index.html, or attached to the Maven artifact.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)