[JBoss JIRA] (JBIDE-18878) Eclipse livelock(?) at startup with hibernate builder in stacktrace
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18878?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-18878.
--------------------------------
Verified with JBDS 8.1.0.GA, L64
> Eclipse livelock(?) at startup with hibernate builder in stacktrace
> -------------------------------------------------------------------
>
> Key: JBIDE-18878
> URL: https://issues.jboss.org/browse/JBIDE-18878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Fix For: 4.2.3.Beta1
>
> Attachments: jstack-output.txt
>
>
> See attached [^jstack-output.txt]
> Console out is:
> {code}sh ./jbt420final.sh
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
> org.eclipse.m2e.logback.configuration: Logback config file: /home/eskimo/workspace/420cr2-test1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.5.0.20140606-0033.xml
> org.eclipse.m2e.logback.configuration: Initializing logback
> java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
> at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
> at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Dec 05, 2014 3:41:58 PM org.hibernate.eclipse.HibernatePlugin start
> INFO: HibernatePlugin Started{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-16478) Fixing Eclipse/Luna
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16478?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-16478.
--------------------------------
Resolved or moved to Mars JIRA - JBIDE-18722
> Fixing Eclipse/Luna
> -------------------
>
> Key: JBIDE-16478
> URL: https://issues.jboss.org/browse/JBIDE-16478
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: upstream
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.2.0.Final
>
>
> "container" issue for issues related to fixes important to get into Luna.
> Please link your Eclipse/Kepler issue to this one instead of using subtasks (edit this description).
> Current open WTP bugs with patches waiting to be applied :
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: 3.6.3
> * -https://bugs.eclipse.org/bugs/show_bug.cgi?id=398599 target: WTP Common Tools 3.6M6- Applied
> * -https://bugs.eclipse.org/bugs/show_bug.cgi?id=399099 target: 3.6 M7- Fixed in Luna
> * -https://bugs.eclipse.org/bugs/show_bug.cgi?id=399523 target: Dali JPA 3.2.3- Fixed in Kepler/Luna
> * -https://bugs.eclipse.org/bugs/show_bug.cgi?id=431970 runtime hyperlink incorrectly negated- Fixed in Luna 3.6 M7
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 show in console. target: none
> * -https://bugs.eclipse.org/bugs/show_bug.cgi?id=432788 error msg for canStart()- Fixed in Luna 3.6 M7
> * -https://bugs.eclipse.org/bugs/show_bug.cgi?id=432580 save editor first- Fixed in Luna 3.6 M7
> * -https://bugs.eclipse.org/bugs/show_bug.cgi?id=431973 no access to command manager- Fixed in Luna
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-10155) JavaScript content assist issue with jQuery, but likely more
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10155?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-10155.
-------------------------------
Verified with JBDS 8.1.0.GA-v20150327-1349-B467
> JavaScript content assist issue with jQuery, but likely more
> ------------------------------------------------------------
>
> Key: JBIDE-10155
> URL: https://issues.jboss.org/browse/JBIDE-10155
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 3.3.0.M4
> Reporter: Jay Balunas
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: jsdt
> Fix For: 4.2.2.Final
>
> Attachments: jboss-as-poh5-archetype.zip, jQueryWithTern.png
>
>
> Content assist with JavaScript with jQuery not working, or respecting namespaces. Most JavaScript content assist was fine.
> {code:JavaScript}
> <script type="text/javascript">
> $(document).ready(function() {
> //Fetches the initial member table
> updateMemberTable();
> //Register a event listener on the sumbit action
> $('#reg').submit(function(event) {
> event.preventDefault();
> var formValues = $(this).serialize();
> registerMember(formValues);
> });
> });
> </script>
> {code}
> Any call to "$('foo')." does not show any content assist. Using "jquery('foo'." instead of $ partially worked, but still not 100%. Not all the expected values are there. This makes me think there is two issues.
> To see the problem import the project I attached and try out desktop.html, or app.js.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-16502) FrameworkEvent ERROR after JBT installation (tracker for upstream issue)
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16502?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-16502.
--------------------------------
Verified with JBDS 8.1.0.GA, L64
> FrameworkEvent ERROR after JBT installation (tracker for upstream issue)
> ------------------------------------------------------------------------
>
> Key: JBIDE-16502
> URL: https://issues.jboss.org/browse/JBIDE-16502
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Alpha2
> Environment: JBT 4.2.0.Alpha2, L64, Fedora 19, OpenJDK 1.7
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.3.Beta1
>
>
> After Eclipse Luna M5 JEE + JBT 4.2.0.Alpha2 installation there is:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.jpt.dbws.eclipselink.ui [388]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0))))
> |
> provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"]
> Chain 2:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0))))
> |
> provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6"
> org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"]
> import: (osgi.wiring.package=javax.xml.bind)
> |
> export: osgi.wiring.package: javax.xml.bind
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445)
> 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)
> Caused by: org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0))))
> |
> provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"]
> Chain 2:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0))))
> |
> provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6"
> org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"]
> import: (osgi.wiring.package=javax.xml.bind)
> |
> export: osgi.wiring.package: javax.xml.bind
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1286)
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1078)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:249)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> ... 7 more
> Root exception:
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0))))
> |
> provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"]
> Chain 2:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0))))
> |
> provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6"
> org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"]
> import: (osgi.wiring.package=javax.xml.bind)
> |
> export: osgi.wiring.package: javax.xml.bind
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1286)
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1078)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:249)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445)
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ]
Vlado Pakan edited comment on JBDS-3262 at 3/31/15 9:09 AM:
------------------------------------------------------------
Where should be added Deprecation section please clarify?
I did not find any such message in JBDS when trying to open JSF page on Linux. Is there any message in JBDS saying JSF preview is deprecated?
was (Author: vpakan):
Where should be added Deprecation section please clarify?
I did not find any such message in JBDS when trying open JSF page on Linux. Is there any message in JBDS saying JSF preview is deprecated?
> Deprecate Visual JSF Preview & Editing
> --------------------------------------
>
> Key: JBDS-3262
> URL: https://issues.jboss.org/browse/JBDS-3262
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, visual-page-editor-core
> Reporter: Burr Sutter
> Assignee: Konstantin Marmalyukov
> Labels: new_and_noteworthy
>
> Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs.
> This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263
> http://screencast.com/t/zur1sCXmZ
> http://screencast.com/t/wettTf6s6cU
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months