[JBoss JIRA] (JBDS-4137) JS editor fails to open
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4137?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4137:
-----------------------------
Fix Version/s: 10.2.0.AM3
> JS editor fails to open
> -----------------------
>
> Key: JBDS-4137
> URL: https://issues.jboss.org/browse/JBDS-4137
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: javascript, rpm, upstream
> Affects Versions: 10.2.0.AM2
> Reporter: Alexey Kazakov
> Fix For: 10.2.0.AM3
>
>
> JavaScript Editor is not working OOTB in Eclipse/devstudio installed via RPM. It fails because of missing JSDT/Equinox hook for Nashorn in eclipse.ini. See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn
> The same error occurs if JSDT installed to an existing Eclipse via p2. So it's rather an upstream issue.
> The following line added to eclipse.ini fixes the problem:
> {code}-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension{code}
> It works OOTB in devstudio installed via our installer because we have this hook in devstudio.ini
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4137) JS editor fails to open
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4137?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4137:
--------------------------------
Assignee: Nick Boldt
> JS editor fails to open
> -----------------------
>
> Key: JBDS-4137
> URL: https://issues.jboss.org/browse/JBDS-4137
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: javascript, rpm, upstream
> Affects Versions: 10.2.0.AM2
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
>
> JavaScript Editor is not working OOTB in Eclipse/devstudio installed via RPM. It fails because of missing JSDT/Equinox hook for Nashorn in eclipse.ini. See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn
> The same error occurs if JSDT installed to an existing Eclipse via p2. So it's rather an upstream issue.
> The following line added to eclipse.ini fixes the problem:
> {code}-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension{code}
> It works OOTB in devstudio installed via our installer because we have this hook in devstudio.ini
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4133:
--------------------------------
Assignee: Nick Boldt
> Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
>
> Snippet from log attached to JBDS-4131:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-21 14:55:03.519
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477058103380-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> And
> {code}
> !ENTRY org.eclipse.help.base 4 0 2016-10-21 14:32:21.719
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610121400 [389]. Please use an index built with Lucene 5 or higher.
> {code}
> then 100s of errors like this:
> {code}
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_ui_preferencePages.html cannot be opened.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4133:
-----------------------------
Parent: (was: JBDS-4131)
Issue Type: Bug (was: Sub-task)
> Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Fix For: 10.2.0.AM3
>
>
> Snippet from log attached to JBDS-4131:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-21 14:55:03.519
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477058103380-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> And
> {code}
> !ENTRY org.eclipse.help.base 4 0 2016-10-21 14:32:21.719
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610121400 [389]. Please use an index built with Lucene 5 or higher.
> {code}
> then 100s of errors like this:
> {code}
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_ui_preferencePages.html cannot be opened.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4134) missing require-bundles in rpm install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4134?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4134:
-----------------------------
Parent: (was: JBDS-4131)
Issue Type: Bug (was: Sub-task)
> missing require-bundles in rpm install
> --------------------------------------
>
> Key: JBDS-4134
> URL: https://issues.jboss.org/browse/JBDS-4134
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: rh-eclipse46-devstudio10.2.log.20161022-1233.grepped.txt, rh-eclipse46-devstudio10.2.log.20161022-1233.txt, unresolved-requirements.txt
>
>
> Digested from the log attached to JBDS-3141, here's a list of all the missing require-bundles as reported by Eclipse on startup of the rh-eclipse46-devstudio install. See attached.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4132) Could not load nodeJSInstall: node-v0.10.22-linux-x86_64
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4132?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4132:
-----------------------------
Parent: (was: JBDS-4131)
Issue Type: Bug (was: Sub-task)
> Could not load nodeJSInstall: node-v0.10.22-linux-x86_64
> --------------------------------------------------------
>
> Key: JBDS-4132
> URL: https://issues.jboss.org/browse/JBDS-4132
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 10.2.0.AM3
>
>
> Snippet from the log attached to JBDS-4131:
> {code}!ENTRY tern.eclipse.ide.server.nodejs.core 4 0 2016-10-21 14:34:24.958
> !MESSAGE Could not load nodeJSInstall: node-v0.10.22-linux-x86_64
> !STACK 0
> java.io.FileNotFoundException: /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64_1.1.0.201511082254/node-v0.10.22-linux-x86_64/LICENSE (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at tern.utils.ZipUtils.extract(ZipUtils.java:83)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstall.<init>(NodejsInstall.java:56)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.addNodejsInstalls(NodejsInstallManager.java:132)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.loadNodejsInstalls(NodejsInstallManager.java:117)
> at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.getNodejsInstalls(NodejsInstallManager.java:69)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.useBundledNodeJsInstall(TernNodejsCorePreferenceConstants.java:91)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.initializeDirectAccess(TernNodejsCorePreferenceConstants.java:70)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.initializeDefaultValues(TernNodejsCorePreferenceConstants.java:45)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceInitializer.initializeDefaultPreferences(TernNodejsCorePreferenceInitializer.java:24)
> at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper$1.run(PreferenceServiceRegistryHelper.java:298)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper.runInitializer(PreferenceServiceRegistryHelper.java:301)
> at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper.applyRuntimeDefaults(PreferenceServiceRegistryHelper.java:131)
> at org.eclipse.core.internal.preferences.PreferencesService.applyRuntimeDefaults(PreferencesService.java:370)
> at org.eclipse.core.internal.preferences.DefaultPreferences.applyRuntimeDefaults(DefaultPreferences.java:222)
> at org.eclipse.core.internal.preferences.DefaultPreferences.load(DefaultPreferences.java:276)
> at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:370)
> at org.eclipse.core.internal.preferences.EclipsePreferences.internalNode(EclipsePreferences.java:623)
> at org.eclipse.core.internal.preferences.DefaultPreferences.node(DefaultPreferences.java:147)
> at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.getDefaultPreferences(PreferenceForwarder.java:134)
> at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.getString(PreferenceForwarder.java:663)
> at tern.eclipse.ide.core.preferences.PreferencesSupport.getWorkspacePreferencesValue(PreferencesSupport.java:115)
> at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferencesSupport.isNodejsRemoteAccess(TernNodejsCorePreferencesSupport.java:147)
> at tern.eclipse.ide.server.nodejs.internal.core.TernNodejsServerFactory.isRemoteAccess(TernNodejsServerFactory.java:67)
> at tern.eclipse.ide.server.nodejs.internal.core.TernNodejsServerFactory.create(TernNodejsServerFactory.java:35)
> at tern.eclipse.ide.internal.core.TernServerType.createServer(TernServerType.java:90)
> at tern.eclipse.ide.internal.core.resources.IDETernProject.getTernServer(IDETernProject.java:161)
> at tern.resources.TernFileSynchronizer.ensureSynchronized(TernFileSynchronizer.java:160)
> at tern.eclipse.ide.internal.ui.EditorActivationTracker$2.run(EditorActivationTracker.java:85)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY tern.eclipse.ide.core 4 0 2016-10-21 14:34:27.182
> !MESSAGE java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> !STACK 0
> tern.TernException: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> at tern.eclipse.ide.internal.core.resources.IDETernFileUploader$1.onError(IDETernFileUploader.java:133)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:131)
> at tern.eclipse.ide.internal.core.resources.IDETernFileUploader.run(IDETernFileUploader.java:124)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.server.nodejs.process.NodejsProcessException: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> at tern.server.nodejs.process.internal.NodejsProcess.start(NodejsProcess.java:245)
> at tern.server.nodejs.process.AbstractNodejsProcess.start(AbstractNodejsProcess.java:144)
> at tern.server.nodejs.NodejsTernServer.getBaseURL(NodejsTernServer.java:202)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:139)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> ... 2 more
> Caused by: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at tern.server.nodejs.process.internal.NodejsProcess.start(NodejsProcess.java:232)
> ... 6 more
> Caused by: java.io.IOException: error=2, No such file or directory
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
> at java.lang.ProcessImpl.start(ProcessImpl.java:134)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4136) Uses constraint violation - org.slf4j.api vs. slf4j.api
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4136?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4136:
-----------------------------
Parent: (was: JBDS-4131)
Issue Type: Bug (was: Sub-task)
> Uses constraint violation - org.slf4j.api vs. slf4j.api
> -------------------------------------------------------
>
> Key: JBDS-4136
> URL: https://issues.jboss.org/browse/JBDS-4136
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, target-platform
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
>
> Latest bit of rpm madness...
> This conflict occurred:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> Chain 1:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle: org.slf4j.api
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> Chain 2:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.7.2.v20121108-1250"; osgi.wiring.bundle="org.slf4j.api"
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bundle-version>=1.0.7)(!(bundle-version>=1.0.8))))
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.0.7.v20121108-1250"; osgi.wiring.bundle="ch.qos.logback.classic"
> ch.qos.logback.classic [osgi.identity; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"; osgi.identity="ch.qos.logback.classic"]
> import: (&(osgi.wiring.package=org.slf4j)(version>=1.7.0))
> |
> export: osgi.wiring.package: org.slf4j
> slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340){code}
> So, since slf4j.api is installed via 5 upstream projects (5 symlinks, actually, to rh-java-common):
> {code}
> $➔ find . -name "*slf4j.api*jar" -exec ls -l {} \;
> lrwxrwxrwx 1 root root 81 Oct 11 13:00 ./share/eclipse/droplets/jgit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 12 05:19 ./share/eclipse/droplets/linuxtools-docker/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-egit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 75 Oct 21 09:58 ./share/eclipse/droplets/mylyn-versions-git/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> {code}
> ... I removed it from the RPM in favour of the other bundle, which was already installed into the fedora/rhel eclipse.
> BUT... since this RH SCL rh-java-common *slf4j-api.jar* exports a different, incompatible bundle name:
> {code}Bundle-SymbolicName: slf4j.api{code}
> than the one in devstudio's update site / target platform
> {code}Bundle-SymbolicName: org.slf4j.api{code}
> NOW, I'm getting this:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"
> {code}
> Snjezana got this too in m2e.core:
> {code}BundleException: Could not resolve module: org.eclipse.m2e.core.ui [866]
> Unresolved requirement: Require-Bundle: org.eclipse.m2e.maven.runtime; bundle-version="[1.7.0,1.8.0)"
> -> Bundle-SymbolicName: org.eclipse.m2e.maven.runtime; bundle-version="1.7.0.20160603-1931"; singleton:="false"
> org.eclipse.m2e.maven.runtime [876]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"{code}
> So... not sure what to do to solve this. :(
> I suppose the best case would be for the m2e and w2e-wtp bundles to depend on the slf4j.api PACKAGES instead of BUNDLES, so that they can run on the fedora/rhel versions instead of those from the devstudio update site / target platform.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months