On Thu, 2018-01-18 at 23:33 +0200, Robert Munteanu wrote: > On Thu, 2018-01-18 at 18:28 +0200, Robert Munteanu wrote: > > Hi Konrad, > > > > On Thu, 2018-01-18 at 16:54 +0100, Konrad Windszus wrote: > > > Something must have gone really wrong. After more closely > > > inspecting > > > the contents of https://dist.apache.org/repos/dist/dev/sling/ide- > > > to > > > ol > > > ing-1.2.0/org.apache.sling.ide.p2update-1.2.0.zip <https://dist.a > > > pa > > > ch > > > e.org/repos/dist/dev/sling/ide-tooling- > > > 1.2.0/org.apache.sling.ide.p2update-1.2.0.zip> it seems that the > > > contained "org.apache.sling.ide.eclipse-core_1.2.0.jar" contains > > > the > > > plugin.xml from the m2e-ui module. Also the other JARs look > > > weird. > > > @Robert: Can you check again? > > > > It seems that the jar contents are correct, but the names are mixed > > up. > > I'll look into a fix. > > I have corrected the signing process and submitted the files with the > correct names in the zip file. > > I am not sure if we should respin the release, given that the > artifacts > are built from the exact same source code. At any rate, Konrad - can > you please retest with the new artifacts?
And BTW, if you're using the Eclipse installer, those bundles may be forever cached in your bundle pool ( ~/.p2/pool ), so I recommend either: - downloading an Eclipse instance and not using the Eclipse installer - removing ~/.p2/pool - manually removing the artifacts from ~/.p2/pool ( make sure to remove them from artifacts.xml as well ). Robert
