November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13109) BrowserSim Android skin - incorrect background highlighting of buttons

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-13109: ----------------------------------- Summary: BrowserSim Android skin - incorrect background highlighting of buttons Key: JBIDE-13109 URL: https://issues.jboss.org/browse/JBIDE-13109 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 4.0.0.Beta1 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.0.0.CR1 Attachments: square-buttons.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-11592) SIGSEGV when tried JBT 3.3.0.Beta2 on Juno

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11592: ------------------------------------ Summary: SIGSEGV when tried JBT 3.3.0.Beta2 on Juno Key: JBIDE-11592 URL: https://issues.jboss.org/browse/JBIDE-11592 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta2 Environment: JBT 3.3.0.Beta2, Eclipse Juno 4.2.M6 JEE Package, Linux 64, JDK 1.6_31 Reporter: Jiri Peterka Assignee: Nick Boldt Priority: Blocker Fix For: 3.3.0.Beta3 SIGSEGV when tried JBT 3.3.0.Beta2 (withon Juno JEE M6). It's not supported configuration so feel free to lower priority and postpone Fix version. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f779563f830, pid=2460, tid=140152133580544 # # JRE version: 6.0_31-b04 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.6-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libmozjs.so+0x73830] unsigned+0xc20 # # An error report file with more information is saved as: # /home/jpeterka/ide/test/jbttrunk-juno/eclipse/hs_err_pid2460.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

8
26
0 / 0

[JBoss JIRA] (JBIDE-12529) Use refactoring API to delete converted dependencies

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12529: ----------------------------------- Summary: Use refactoring API to delete converted dependencies Key: JBIDE-12529 URL: https://issues.jboss.org/browse/JBIDE-12529 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.0.0.Alpha1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Alpha2 As a follow up on JBIDE-12527 and JBIDE-8973, we should be able to also convert any jar in the project explorer to maven dependencies. Use case : select multiple lib dependencies, then right click and choose "Convert to Maven dependencies...". The "Convert to Maven dependencies..." wizard is shown with a 2nd page displaying a preview of the selected maven dependencies with a copy to clipoard button. If the containing project is a maven project, an "update pom.xml" button will also be displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-13000) NPE occurs after editing an unknown dependency

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13000: ----------------------------------- Summary: NPE occurs after editing an unknown dependency Key: JBIDE-13000 URL: https://issues.jboss.org/browse/JBIDE-13000 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Beta2 If, during a maven conversion, an unidentified jar is manually modified (dbl click, set GAV), the dependency still appears unidentified, as an underlying NPE occurs, preventing the maven resolution -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-13119) Code generation doesn't work when Hibernate 4.0 is used

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13119: ------------------------------------ Summary: Code generation doesn't work when Hibernate 4.0 is used Key: JBIDE-13119 URL: https://issues.jboss.org/browse/JBIDE-13119 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.0.0.CR1 Environment: JBDS 6.0.0.CR1 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Priority: Blocker Fix For: 4.0.0.CR1 {code} org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.launchExporters(ConsoleExtension4_0.java:147) at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:270) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:855) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:704) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1047) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1251) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.tool.Version at org.hibernate.tool.hbm2x.TemplateHelper.setupContext(TemplateHelper.java:215) at org.hibernate.tool.hbm2x.AbstractExporter.setupContext(AbstractExporter.java:147) at org.hibernate.tool.hbm2x.POJOExporter.setupContext(POJOExporter.java:44) at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:94) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0$2.execute(ConsoleExtension4_0.java:201) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.jboss.tools.hibernate4_0.HibernateExtension4_0.execute(HibernateExtension4_0.java:211) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.runExporters(ConsoleExtension4_0.java:174) at org.jboss.tools.hibernate4_0.console.ConsoleExtension4_0.launchExporters(ConsoleExtension4_0.java:126) ... 6 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBDS-2397) When started using "java", Failing Central install shows no UI

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2397: ------------------------------------ Summary: When started using "java", Failing Central install shows no UI Key: JBDS-2397 URL: https://issues.jboss.org/browse/JBDS-2397 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 6.1.0.Alpha1 Reporter: Mickael Istria Assignee: Snjezana Peco Priority: Minor Fix For: 6.1.0.Alpha1 This was discovered while trying to debug some Installation Tests. We start Eclipse that way: https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scri... (java -jar ... -product ... -application org.eclipse.swtbot.swtbottestapplication -testProduct ... -testApplication ...). When running SWTBot to perform tests that install all Software from Central, when those are failing due to bad p2 plan; then there is no pop-up to warn about failing plan. When starting Eclipse normally, we can see a pop-up telling which "Problems occured". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] (JBIDE-13134) No adapter in Juno for Java EE - No update site works....

by James Gallagher (JIRA)

James Gallagher created JBIDE-13134: --------------------------------------- Summary: No adapter in Juno for Java EE - No update site works.... Key: JBIDE-13134 URL: https://issues.jboss.org/browse/JBIDE-13134 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Environment: Win 7 - 64 bit - Eclipse Juno for Java EE Reporter: James Gallagher Assignee: Rob Stryker Priority: Blocker I have downloaded Juno for Java EE and I am trying to get it set up with JBoss AS integration. Methods I have tried... 1. I go to servers window -~> new server -> adapters -> where JBoss AS used to be in indigo, it is no longer. 2. Juno -> Help -> Eclipse MarketPlace -> 'JBoss' -> JBoss Developer Studio (Juno) -> Install -> Error -> Unable to read repository at https://devstudio.jboss.com/updates/6.0-staging/content.xml. sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 3. Juno -> Help -> Eclipse MarketPlace -> 'JBoss' -> JBoss Tools (Juno) -> Install -> Unable to read repository at http://download.jboss.org/jbosstools/updates/development/juno. http://download.jboss.org/jbosstools/updates/development/juno is not a valid repository location. 4. Get update site for JBoss Developer Studio (Juno) from MarketPlace directly and try 'install new software' -> same site as method 2, same error 5. Get update site for JBoss Tools (Juno) from MarketPlace directly and try 'install new software' -> same site as method 3, same error 6. JBoss Community -> Can't install JBoss AS Server adapters from Juno JavaEE M3 -> Nick Boldt's Solution -> http://download.eclipse.org/webtools/downloads/drops/R3.4.0/I-3.4.0-20120... -> Error -> Could not find http://download.eclipse.org/webtools/downloads/drops/R3.4.0/I-3.4.0-20120... 7. community -> https://community.jboss.org/message/754415 -> points to same as method 6. 8. stackoverflow -> http://stackoverflow.com/questions/11982718/how-to-deploy-on-jboss-as-7-f... -> Solution: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -> Error -> Unable to read repository at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/. Unable to read repository at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ is not a valid repository location. Can someone please help with this issue. It appears to be leading me in circles... Can Juno work with JBoss? Thank you all in advance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
26
0 / 0

[JBoss JIRA] (JBIDE-12912) Identification of maven dependency should work behind proxies

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12912: ----------------------------------- Summary: Identification of maven dependency should work behind proxies Key: JBIDE-12912 URL: https://issues.jboss.org/browse/JBIDE-12912 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.CR1 When querying remote nexus repos or maven central for jar identification, the http connection doesn't use the Eclipse proxy settings, rendering the feature useless when working behind proxies. We'd need a dev proxy in order to dev/test against that sort of scenario -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-13039) Project is not managed by archives view even after fixed project archive descriptor

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-13039: ----------------------------------------- Summary: Project is not managed by archives view even after fixed project archive descriptor Key: JBIDE-13039 URL: https://issues.jboss.org/browse/JBIDE-13039 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.Beta2 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Fix For: 4.0.0.CR1, 4.0.x -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-13038) Illegal Argument Exception occurs when installing plugin from requirements.

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-13038: ---------------------------------------------- Summary: Illegal Argument Exception occurs when installing plugin from requirements. Key: JBIDE-13038 URL: https://issues.jboss.org/browse/JBIDE-13038 Project: Tools (JBoss Tools) Issue Type: Bug Components: GWT Environment: win 7 x64, jre 1.6.37 x86, JBDS from [here|https://devstudio.jboss.com/earlyaccess/] Reporter: Konstantin Marmalyukov Assignee: Denis Golovin Priority: Minor Google plugin installation failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

6
23
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 November 2012