August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17696: ---------------------------------- Sprint: Sprint to CR1 Release > Enabling Maven Dependency Management job waits forever > ------------------------------------------------------ > > Key: JBIDE-17696 > URL: https://issues.jboss.org/browse/JBIDE-17696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.Beta2 > Environment: OpenJDK 1.7, 64b > Ubuntu 12.04, 64b > Reporter: Rastislav Wagner > Assignee: Denis Golovin > Fix For: 4.2.0.CR1 > > Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png > > > I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario: > 1. Create Dynamic Web Project > 2. Convert to maven project (using Configure -> Convert to maven..) > 3. Add some dependency > 4. check if proper facet was enabled > 5. delete project and repeat > After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers". > JVM thread dump attached. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3026) Provide better default JRE path in universal installer on Mac OS X

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3026?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3026: -------------------------------- Sprint: Sprint to CR1 Release > Provide better default JRE path in universal installer on Mac OS X > ------------------------------------------------------------------ > > Key: JBDS-3026 > URL: https://issues.jboss.org/browse/JBDS-3026 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Reporter: Michelle Murray > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > > Max OS X, universal installer, step 4 - choose JVM > When installer is launched from command line, the Default JVM path is correct - /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home > ^ great :D > When installer is launched by double-clicking .jar file, the Default JVM path is not right - /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home > ^ can we provide a better default value when installer is launched by this method? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17728: ---------------------------------- Sprint: Sprint to CR1 Release > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: ActionSheet.png, ActionSheetWizBan.png, Content.png, ContentWizBan.png, ionic.png, IonicButton.png, IonicButtonBar.png, IonicButtonBarWizBan.png, IonicButtonWizBan.png, IonicCheckbox.png, IonicCheckboxWizBan.png, IonicPopup.png, IonicPopupWizBan.png, IonicRadio.png, IonicRadioWizBan.png, IonicRange.png, IonicRangeWizBan.png, IonicRefresher.png, IonicRefresherWizBan.png, IonicSelect.png, IonicSelectWizBan.png, IonicTab.png, IonicTabs.png, IonicTabsWizBan.png, IonicTabWizBan.png, IonicToggle.png, IonicToggleWizBan.png, List.png, ListWizBan.png, scr.png, Scroll.png, ScrollWizBan.png, SlideBox.png, SlideBoxWizBan.png, SlideMenu.png, SlideMenuWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17889) Provide AngularJS Eclipse IDE through JBoss Central Early Access

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17889?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17889: ---------------------------------- Sprint: Sprint to CR1 Release > Provide AngularJS Eclipse IDE through JBoss Central Early Access > ---------------------------------------------------------------- > > Key: JBIDE-17889 > URL: https://issues.jboss.org/browse/JBIDE-17889 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.0.CR1 > > > AngularJS Eclipse IDE have no frozen API to depend on, so we have to lock version avoid installation/update to newest version from external update. We also should make sure it works with tern bundles included into JBossTools target platform. > Proposed name for new Feature/Bundle is org.jboss.tools.jst.angularjs.editor'. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17992) Show Tern Modules configuration under different preferences category

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17992?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17992: ---------------------------------- Sprint: Sprint to CR1 Release > Show Tern Modules configuration under different preferences category > -------------------------------------------------------------------- > > Key: JBIDE-17992 > URL: https://issues.jboss.org/browse/JBIDE-17992 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.2.0.CR1 > > > Tern modules configuration should be visible to let disable/enable specific modules. At the same time we should still not show JavaScript Engine configuration preferences. > Should be possible by creating new category and assigning tern modules preference page class to it. > Should test if it works with both original and new category visible. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17687) create savara features overview for tools.jboss.org

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17687?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17687: ---------------------------------- Sprint: Sprint to Beta3 Release (was: Sprint Beta2 CF, Sprint to Beta3 Release) > create savara features overview for tools.jboss.org > --------------------------------------------------- > > Key: JBIDE-17687 > URL: https://issues.jboss.org/browse/JBIDE-17687 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Gary Brown > Fix For: 4.2.x > > > Create a features/savara.adoc in jbosstools-website describing the main/cool features > We are refreshing jboss.org/tools (new name: tools.jboss.org) and one of the areas on the new website is a features overview page to let visitors know what features are actually covered in jboss tools. > You can see the current list at http://tools-stg.jboss.org/features/ following the pattern of component/project logo + component name + "tag line". > And then individual pages like http://tools-stg.jboss.org/features/openshift.html which follows the pattern of alternating paragraph + image/screenshot with title/tagline + description for each main feature. > It would be great if you could help create this page for your component. > The process is as follows: > git@github.com:jbosstools/jbosstools-website.git > cd jbosstools-website/features > create componentname.adoc (use i.e. openshift.adoc as inspiration with respect to header names) > Submit this page and related images as pullrequest > The expected launch of the site is end of march so the sooner the better :) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15474) "Further Configuration" for JAX-RS Facet should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15474?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15474: ---------------------------------- Sprint: Sprint to Beta3 Release (was: Sprint Beta2 CF, Sprint to Beta3 Release) > "Further Configuration" for JAX-RS Facet should be optional > ----------------------------------------------------------- > > Key: JBIDE-15474 > URL: https://issues.jboss.org/browse/JBIDE-15474 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream, webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > - library configuration should be optional, since users may work with Maven > - web.xml configuration (servlet mapping) should be optional as well, since it has not been required since JavaEE6. > Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=431081 to track this request at the Eclipse WTP level. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9179) Bad behaviour of the JAX-RS Capabilities popup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9179?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-9179: --------------------------------- Sprint: Sprint to Beta3 Release (was: Sprint Beta2 CF, Sprint to Beta3 Release) > Bad behaviour of the JAX-RS Capabilities popup > ----------------------------------------------- > > Key: JBIDE-9179 > URL: https://issues.jboss.org/browse/JBIDE-9179 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 3.3.0.M1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Labels: JAX-RS, upstream > Fix For: 4.2.0.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > When setting the JAX-RS Facet on a dynamic web project, a popup window requires to choose the JAX-RS implementation library for the project, and optionally to specify the servlet class name to update the web.xml deployment descriptor accordingly. When choosing 'Disable library configuration' or 'Pure JEE6 implementation', the 'Servlet Information' panel is not disabled as expected. This is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=338898 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17591: ---------------------------------- Sprint: Sprint to Beta3 Release (was: Sprint Beta2 CF, Sprint to Beta3 Release) > org.jboss.tools.common.el.core.test fails on Max OS X Mavericks > --------------------------------------------------------------- > > Key: JBIDE-17591 > URL: https://issues.jboss.org/browse/JBIDE-17591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.Beta2 > Environment: Mac OS X Mavericks > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.2.0.CR1 > > Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt > > > {code}junit.framework.AssertionFailedError > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertNotNull(Assert.java:256) > at junit.framework.Assert.assertNotNull(Assert.java:248) > at junit.framework.TestCase.assertNotNull(TestCase.java:417) > at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86) > at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2876) Include EAP 6.3 in bundled JBDS+EAP universal installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2876?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2876: -------------------------------- Sprint: Sprint to Beta3 Release (was: Sprint Beta2 CF, Sprint to Beta3 Release) > Include EAP 6.3 in bundled JBDS+EAP universal installer > ------------------------------------------------------- > > Key: JBDS-2876 > URL: https://issues.jboss.org/browse/JBDS-2876 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer, requirements > Reporter: Michelle Murray > Assignee: Nick Boldt > Priority: Blocker > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 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 August 2014