Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » RCP Testing Tool » Update site for 2.5.1 contains actually 2.5.1-M3?
Update site for 2.5.1 contains actually 2.5.1-M3? [message #1847706] Thu, 04 November 2021 09:28
Stefan Winkler is currently offline Stefan WinklerFriend
Messages: 307
Registered: July 2009
Location: Germany
Senior Member
Hi,

we have run into a problem which could be nailed down to
http://download.eclipse.org/rcptt/release/2.5.1/repository
containing plugins with the qualifier 2.5.1-M3
whereas the artifacts available via Maven (e.g., https://mvnrepository.com/artifact/org.eclipse.rcptt.runner/rcptt.runner/2.5.1) have the qualifier 2.5.1-202002051038

If for some reason (in our case it has to do with using the Maven Runner in combination with site injection where the injected site contains RCPTT artifacts for dependency reasons) artifacts from both places end up in the p2 pool, the AUT will be unable to resolve the RCPTT bundles, because:

org.osgi.framework.BundleException: Could not resolve module: org.eclipse.rcptt.core.ecl.debug [527]
- Unresolved requirement: Require-Bundle: org.eclipse.rcptt.tesla.ecl.impl; bundle-version="[2.5.1,3.0.0)" -> Bundle-SymbolicName: org.eclipse.rcptt.tesla.ecl.impl; bundle-version="2.5.1.202002051038"; singleton:="true" org.eclipse.rcptt.tesla.ecl.impl [591] 
- Unresolved requirement: Require-Bundle: org.eclipse.rcptt.ecl.data; bundle-version="[2.5.1,3.0.0)" -> Bundle-SymbolicName: org.eclipse.rcptt.ecl.data; bundle-version="2.5.1.M3"; singleton:="true" org.eclipse.rcptt.ecl.data [554]
- Unresolved requirement: Require-Bundle: org.eclipse.rcptt.tesla.ecl; bundle-version="[2.5.1.M3,3.0.0)"


Currently, I don't need help fixing the resolution error (using 2.5.1-M3 as version for the Maven Runner or even removing the additional dependencies from the injection site will most likely fix this), but I wonder why the update site labelled as release actually contains milestone versions, whereas the maven artifacts with the same label do not.

Is that a bug/forgotten update? Or is it by intention?

Thanks for clarifying!

Best,
Stefan


Previous Topic:Authentication of injection site failed
Next Topic:Java && Operator Not Working
Goto Forum:
  


Current Time: Mon Jul 22 06:12:15 GMT 2024

Powered by FUDForum. Page generated in 0.04079 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top