Latest Locus 1.2 build is here:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-loc...
So... since the artifacts include the BUILD_NUMBER and BUILD_ID in them,
it therefore follows that each build will have uniquely versioned
artifacts, even if bitwise they're the same as the previous B76 build.
Is that what you mean by "producing different content between releases" ?
If so, do we need to change the builds so they omit the timestamp and
build number in their qualifiers, and just use 1.3.0.Final instead of
1.3.0.Final-v20150430-1349-B77?
On 05/05/2015 03:11 PM, Max Rydahl Andersen wrote:
Locus shouldn't be producing different content between releases
So that
sounds weird too...
/max
http://about.me/maxandersen
On 05 May 2015, at 20:08, Mickael Istria <mistria(a)redhat.com
<mailto:mistria@redhat.com>> wrote:
> On 05/05/2015 07:51 PM, Paul Leacu wrote:
>> Which is causing a failure with conflicting mockito builds when I pull from
the new locus area (B58, B77).
> Do you mean you're also adding mockito in your target-platform, but
> with another version? If yes, then you should simply remove it to make
> sure you're using the same version as JBoss Tools.
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
> My blog <
http://mickaelistria.wordpress.com> - My Tweets
> <
http://twitter.com/mickaelistria>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com