March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16965) Application menu not shown when browsersim is opened

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16965?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16965: ------------------------------------------------ Looksl ike upstream issue was fixed in 4.4.2, so fix may be accessible with 4.2.3.Final. Martin, if you have 10.9, could you please take a look? > Application menu not shown when browsersim is opened > ---------------------------------------------------- > > Key: JBIDE-16965 > URL: https://issues.jboss.org/browse/JBIDE-16965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1 > OS X Mavericks > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > Labels: upstream > Fix For: 4.3.x > > Attachments: browsersim-menu.png > > > *Upstream bug* https://bugs.eclipse.org/bugs/show_bug.cgi?id=426062 > When I open browsersim by clicking the icon in JBDS menu bar, browsersim is launched, I can see the app in the dock, the window is active, but for some reason the system menu bar stays locked in JBoss Developer Studio. But the menu is dead - the only way to get the Browsersim menu is to swich to some other app and then back to Browsersim. > !browsersim-menu.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19525) JPA project needs cleanup after second import

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19525?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19525: -------------------------------------- There are the error details: Description Resource Path Location Type Class "org.hibernate.ui.test.model.Address" is listed in the persistence.xml file, but is not annotated Address.java /mvn-jpa21-hibernate43/src/main/java/org/hibernate/ui/test/model line 6 JPA Problem Class "org.hibernate.ui.test.model.Order" is listed in the persistence.xml file, but is not annotated Order.java /mvn-jpa21-hibernate43/src/main/java/org/hibernate/ui/test/model line 9 JPA Problem Class "org.hibernate.ui.test.model.StrategyClient" is listed in the persistence.xml file, but is not annotated StrategyClient.java /mvn-jpa21-hibernate43/src/main/java/org/hibernate/ui/test/model line 9 JPA Problem Class "org.hibernate.ui.test.model.User" is listed in the persistence.xml file, but is not annotated User.java /mvn-jpa21-hibernate43/src/main/java/org/hibernate/ui/test/model line 8 JPA Problem > JPA project needs cleanup after second import > --------------------------------------------- > > Key: JBIDE-19525 > URL: https://issues.jboss.org/browse/JBIDE-19525 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.3.CR1 > Environment: JBDS 8.1.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Alpha2 > > Attachments: errors-after-2nd-import.png > > > After second import of the same project there are errors and clean project is needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19525) JPA project needs cleanup after second import

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19525?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19525: --------------------------------------------- your screenshot or description does not mention anything about what errors you are seeing ? > JPA project needs cleanup after second import > --------------------------------------------- > > Key: JBIDE-19525 > URL: https://issues.jboss.org/browse/JBIDE-19525 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.3.CR1 > Environment: JBDS 8.1.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Alpha2 > > Attachments: errors-after-2nd-import.png > > > After second import of the same project there are errors and clean project is needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19500: --------------------------------------------- this is not for me, its a feature request for common/foundation to consider - thus unassigning from me. > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-19500: ------------------------------------------- Assignee: (was: Max Rydahl Andersen) > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19333) Ensure all component jobs have access to java 5, 6, 7, and 8 via jre properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19333?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19333. ------------------------------ Closing. > Ensure all component jobs have access to java 5, 6, 7, and 8 via jre properties > ------------------------------------------------------------------------------- > > Key: JBIDE-19333 > URL: https://issues.jboss.org/browse/JBIDE-19333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Please ensure all jobs in master (and maybe Luna?) have access to the various java installations. This should be done similar to the files in https://github.com/jbdevstudio/jbdevstudio-ci/pull/146 > This will mostly involve adding the java17 and java18 variables to all jobs and the sysprops, but may involve cleaning up some jobs who do it incorrectly (such as web services, who puts it in the ${maven_flags} variable) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19357) NPE while installing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19357?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19357. ------------------------------ Resolution: Cannot Reproduce Bug Reporter cannot reproduce. > NPE while installing > -------------------- > > Key: JBIDE-19357 > URL: https://issues.jboss.org/browse/JBIDE-19357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: paolo antinori > Assignee: Nick Boldt > Labels: need-more-info, needs_information, needs_investigation > Fix For: 4.2.3.Final > > > Hi, I was trying to install JBoss Tools in Eclipse Luna. > I have manually added at new software source, providing this url: > http://download.jboss.org/jbosstools/updates/stable/luna/ > I have selected only this component: > {{ JBossAS Tools 3.0.1.Final-v20141209-0156-B106}} > And the installation process failed due to this error > {code} > An error occurred while collecting items to be installed > session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > java.lang.NullPointerException > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19473: ------------------------------- Fix Version/s: 4.3.0.Alpha2 > Central can't load Discovery catalog > ------------------------------------ > > Key: JBIDE-19473 > URL: https://issues.jboss.org/browse/JBIDE-19473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found. > The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content. > Log says > {quote} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar > {quote} > I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19473: ---------------------------------- Assignee: Nick Boldt > Central can't load Discovery catalog > ------------------------------------ > > Key: JBIDE-19473 > URL: https://issues.jboss.org/browse/JBIDE-19473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found. > The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content. > Log says > {quote} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar > {quote} > I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19473: ------------------------------------ Suspect the error is caused by the fact that we can only declare a category ONCE across all discovery plugins, but the category ref'd by the EA plugin is not in the Central plugin.xml > Central can't load Discovery catalog > ------------------------------------ > > Key: JBIDE-19473 > URL: https://issues.jboss.org/browse/JBIDE-19473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found. > The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content. > Log says > {quote} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar > {quote} > I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2015