| Re: [tycho-user] Consuming tycho results in non-tycho builds - reloaded |
Hi,
Here is another episode of incompatibilities between versioning
schemes, it seems:
We have a non-OSGi application, that uses some OSGi artifacts
for its runtime. Those artifacts are built using tycho.
Using the b3 aggregator with Maven mapping enabled, I produced
a repository that contains, e.g.,:
org.eclipse.emf:org.eclipse.emf.ecore:2.9.1.v20130827-0309
The application build ran fine, until last Friday, on which day
someone uploaded the following to maven central:
org.eclipse.emf:org.eclipse.emf.ecore:2.9.1-v20130827-0309
Can some Maven expert on this list explain the following:
since that upload to Maven central, our application build no
longer finds the org.eclipse.emf.ecore artifact (and others).
I seem to understand the following, please correct if I'm wrong:
- the variant produced by tycho and b3 is a snapshot version
using the qualifier from the OSGi version as its timestamp.
- the variant found on Maven central is a release version (of
the same bits), using the timestamp as a "classifier".
- both versions are in some conflict with each other.
Can tycho & b3 produce artifacts that can reliably be consumed,
independent of any uploads of like named artifacts?
Can I tell Maven to continue using the '.' version, even if a '-'
version exists?
any hints appreciated,
Stephan
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user