[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 commented on JBDS-4132:
----------------------------------
CI build is available for testing: http://download.jboss.org/jbosstools/neon/snapshots/builds/tern.java-1.1....
> 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-4131) Can't import example project after RPM installation on RHEL 7
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Snjezana Peco edited comment on JBDS-4131 at 10/28/16 11:29 AM:
----------------------------------------------------------------
It is possible you have a problem with the workspace.
Try to start JBDS in a new workspace.
was (Author: snjeza):
It is possible you have a problem the workspace.
Try to start JBDS in a new workspace.
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-lucene-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-wagon-provider-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132.png, import_wizard.png, maven-wizard-devstudio10.2-rpm-busted.png, maven.importer.error.log, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Snjezana Peco commented on JBDS-4131:
-------------------------------------
It is possible you have a problem the workspace.
Try to start JBDS in a new workspace.
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-lucene-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-wagon-provider-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132.png, import_wizard.png, maven-wizard-devstudio10.2-rpm-busted.png, maven.importer.error.log, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4131:
----------------------------------
Still getting the above java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer error with latest RPM; also getting this new error:
{code}
!ENTRY org.jboss.tools.project.examples 4 2 2016-10-28 10:39:23.494
!MESSAGE Problems occurred when invoking code from plug-in: "org.jboss.tools.project.examples".
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$6.resetCheatSheet(ProjectExamplesActivator.java:945)
at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$6.done(ProjectExamplesActivator.java:932)
at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106)
at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144)
at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
!!! FAILED TO STOP EXECUTOR !!!
Start VM: /opt/rh/rh-eclipse46/root/usr/lib/jvm/java/bin/java
-Dosgi.requiredJavaVersion=1.8
-Xms512m
-Xmx1024m
-Dorg.eclipse.swt.browser.UseWebKitGTK=true
-Dhelp.lucene.tokenizer=standard
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
-XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates,instantiateTemplate
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage,addBinding
-XX:CompileCommand=exclude,org/python/pydev/editor/codecompletion/revisited/PythonPathHelper,isValidSourceFile
-XX:CompileCommand=exclude,org/eclipse/tycho/core/osgitools/EquinoxResolver,newState
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/opt/rh/rh-eclipse46/root/usr/share/eclipse/dropins
-Dp2.fragments=/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets,/opt/rh/rh-eclipse46/root/usr/lib64/eclipse/droplets
-Declipse.p2.skipMovedInstallDetection=true
-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension
-jar /opt/rh/rh-eclipse46/root/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.200.v20160920-1429.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /opt/rh/rh-eclipse46/root/usr/lib64/eclipse//plugins/org.eclipse.platform_4.6.1.v20160920-1429/splash.bmp
-launcher /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/eclipse
-name Eclipse
--launcher.library /opt/rh/rh-eclipse46/root/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.400.v20160920-1429/eclipse_1617.so
-startup /opt/rh/rh-eclipse46/root/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.200.v20160920-1429.jar
-protect master
--launcher.appendVmargs
-exitdata 18e0011
-consolelog
-console
-debug
-vm /opt/rh/rh-eclipse46/root/usr/lib/jvm/java/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms512m
-Xmx1024m
-Dorg.eclipse.swt.browser.UseWebKitGTK=true
-Dhelp.lucene.tokenizer=standard
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
-XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates,instantiateTemplate
-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage,addBinding
-XX:CompileCommand=exclude,org/python/pydev/editor/codecompletion/revisited/PythonPathHelper,isValidSourceFile
-XX:CompileCommand=exclude,org/eclipse/tycho/core/osgitools/EquinoxResolver,newState
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/opt/rh/rh-eclipse46/root/usr/share/eclipse/dropins
-Dp2.fragments=/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets,/opt/rh/rh-eclipse46/root/usr/lib64/eclipse/droplets
-Declipse.p2.skipMovedInstallDetection=true
-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension
-jar /opt/rh/rh-eclipse46/root/usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.200.v20160920-1429.jar
{code}
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-lucene-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-wagon-provider-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132.png, import_wizard.png, maven-wizard-devstudio10.2-rpm-busted.png, maven.importer.error.log, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBIDE-23413) use Import-Package instead of Require-Bundle for slf4j.api [hibernate]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23413?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23413 at 10/28/16 10:39 AM:
---------------------------------------------------------------
Thanks, I've kicked your job so it'll aggregate down into devstudio.
Currently I'm getting this error when running the latest RPM (before this fix):
{code}
org.osgi.framework.BundleException: Could not resolve module: org.hibernate.eclipse [974]
Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.7.2"
... then several errors like this one ...
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.hibernate.ui [1069]
Unresolved requirement: Require-Bundle: org.hibernate.eclipse; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse; bundle-version="5.1.2.v20160915-1030"; singleton:="true"
org.hibernate.eclipse [974]
Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.7.2"
Unresolved requirement: Require-Bundle: org.hibernate.eclipse.console; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse.console; bundle-version="5.1.2.v20160926-1506"; singleton:="true"
org.hibernate.eclipse.console [975]
Unresolved requirement: Require-Bundle: org.hibernate.eclipse; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse; bundle-version="5.1.2.v20160915-1030"; singleton:="true"
{code}
was (Author: nickboldt):
Thanks, I've kicked your job so it'll aggregate down into devstudio.
Currently I'm getting this error when running the latest RPM (before this fix):
{code}
org.osgi.framework.BundleException: Could not resolve module: org.hibernate.eclipse [974]
Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.7.2"
then
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.hibernate.ui [1069]
Unresolved requirement: Require-Bundle: org.hibernate.eclipse; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse; bundle-version="5.1.2.v20160915-1030"; singleton:="true"
org.hibernate.eclipse [974]
Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.7.2"
Unresolved requirement: Require-Bundle: org.hibernate.eclipse.console; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse.console; bundle-version="5.1.2.v20160926-1506"; singleton:="true"
org.hibernate.eclipse.console [975]
Unresolved requirement: Require-Bundle: org.hibernate.eclipse; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse; bundle-version="5.1.2.v20160915-1030"; singleton:="true"
{code}
> use Import-Package instead of Require-Bundle for slf4j.api [hibernate]
> ----------------------------------------------------------------------
>
> Key: JBIDE-23413
> URL: https://issues.jboss.org/browse/JBIDE-23413
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, rpm
> Affects Versions: 4.4.2.AM2
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.4.2.AM3
>
> Attachments: org.hibernate.eclipse.unresolved.req.txt
>
>
> Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora.
> Here's the line that is causing the problem:
> https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or...
> We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used.
> More info in JBDS-4136
> See also:
> http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa...
> http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa...
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBIDE-23413) use Import-Package instead of Require-Bundle for slf4j.api [hibernate]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23413?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23413:
------------------------------------
Thanks, I've kicked your job so it'll aggregate down into devstudio.
Currently I'm getting this error when running the latest RPM (before this fix):
{code}
org.osgi.framework.BundleException: Could not resolve module: org.hibernate.eclipse [974]
Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.7.2"
then
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.hibernate.ui [1069]
Unresolved requirement: Require-Bundle: org.hibernate.eclipse; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse; bundle-version="5.1.2.v20160915-1030"; singleton:="true"
org.hibernate.eclipse [974]
Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.7.2"
Unresolved requirement: Require-Bundle: org.hibernate.eclipse.console; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse.console; bundle-version="5.1.2.v20160926-1506"; singleton:="true"
org.hibernate.eclipse.console [975]
Unresolved requirement: Require-Bundle: org.hibernate.eclipse; bundle-version="5.0.0"
-> Bundle-SymbolicName: org.hibernate.eclipse; bundle-version="5.1.2.v20160915-1030"; singleton:="true"
{code}
> use Import-Package instead of Require-Bundle for slf4j.api [hibernate]
> ----------------------------------------------------------------------
>
> Key: JBIDE-23413
> URL: https://issues.jboss.org/browse/JBIDE-23413
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, rpm
> Affects Versions: 4.4.2.AM2
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.4.2.AM3
>
> Attachments: org.hibernate.eclipse.unresolved.req.txt
>
>
> Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora.
> Here's the line that is causing the problem:
> https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or...
> We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used.
> More info in JBDS-4136
> See also:
> http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa...
> http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa...
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months