Something must have gone really wrong. After more closely inspecting the contents of https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.2.0/org.apache.sling.ide.p2update-1.2.0.zip <https://dist.apache.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?
> On 18. Jan 2018, at 16:43, Konrad Windszus <konra...@gmx.de> wrote: > > I am facing several issues with the p2 repo from > https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.2.0/org.apache.sling.ide.p2update-1.2.0.zip > > <https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.2.0/org.apache.sling.ide.p2update-1.2.0.zip> > > Two of them I reported via > - https://issues.apache.org/jira/browse/SLING-7402 > <https://issues.apache.org/jira/browse/SLING-7402> and > - https://issues.apache.org/jira/browse/SLING-7403 > <https://issues.apache.org/jira/browse/SLING-7403> > > But I also don't see the "JCR Properties" view or the category "Sling" within > the dialog "Show View". > > I tested two times with a brand new Eclipse Oxygen .2 (EE) installed via the > Eclipse Installer and added there the p2 repo referenced above. > Could it be that the signing process somehow destroyed the plugins? > > Could someone else verify as well? > Thanks, > Konrad > > > >> On 18. Jan 2018, at 14:11, Robert Munteanu <romb...@apache.org >> <mailto:romb...@apache.org>> wrote: >> >> On Thu, 2018-01-18 at 14:00 +0100, Konrad Windszus wrote: >>> The versioning seems fishy within https://dist.apache.org/repos/dist/ >>> <https://dist.apache.org/repos/dist/> >>> dev/sling <https://dist.apache.org/repos/dist/dev/sling >>> <https://dist.apache.org/repos/dist/dev/sling>>. >>> It contains org.apache.sling.ide.source-bundle-1.2.0.zip <https://dis >>> <https://dis/> >>> t.apache.org/repos/dist/dev/sling/ide-tooling- >>> <http://t.apache.org/repos/dist/dev/sling/ide-tooling-> >>> 1.2.0/org.apache.sling.ide.source-bundle-1.2.0.zip> and >>> org.apache.sling.ide.p2update-1.0.2.zip <https://dist.apache.org/repo >>> s/dist/dev/sling/ide-tooling-1.2.0/org.apache.sling.ide.p2update- >>> 1.0.2.zip> >>> I guess the version number of p2update is wrong. Does that contain >>> the full build p2repo? Would testing make more sense based on that? >>> Does that include already the signed plugins? >> >> Good catch ; too much copy-paste I guess :-) >> >> It contains the full p2 repo, including the signed artifacts. Feel free >> to test on that if you prefer. >> >> Robert >> >>> >>> Konrad >>> >>>> On 17. Jan 2018, at 22:38, Robert Munteanu <romb...@apache.org >>>> <mailto:romb...@apache.org>> >>>> wrote: >>>> >>>> Hi, >>>> >>>> We solved 30 issues in this release: >>>> https://issues.apache.org/jira/browse/SLING/fixforversion/12334907 >>>> <https://issues.apache.org/jira/browse/SLING/fixforversion/12334907> >>>> >>>> There are still some outstanding issues: >>>> https://issues.apache.org/jira/browse/SLING/component/12320908 >>>> >>>> The release candidate has been uploaded at >>>> https://dist.apache.org/repos/dist/dev/sling, The release artifact >>>> is >>>> the source bundle - org.apache.sling.ide.source-bundle-1.2.0.zip - >>>> which can be used to build the project using >>>> >>>> mvn clean package >>>> >>>> The resulting binaries can be installed into an Eclipse instance >>>> from >>>> the update site which is found at p2update/target/repository after >>>> building the project. >>>> >>>> You can use this UNIX script to download the release and verify the >>>> signatures: >>>> http://svn.apache.org/repos/asf/sling/trunk/tooling/ide/check_stage >>>> d_re >>>> lease.sh >>>> >>>> Usage: >>>> sh check_staged_release.sh 1.2.0 /tmp/sling-staging >>>> >>>> Please vote to approve this release: >>>> >>>> [ ] +1 Approve the release >>>> [ ] 0 Don't care >>>> [ ] -1 Don't release, because ... >>>> >>>> This majority vote is open for at least 72 hours >>>> >>>> Thanks, >>>> >>>> Robert >>> >>> >> >
