April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-638?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-638: ------------------------------- Description: We need instructions for how to uninstall JBDS-IS included in the Install Guide. This should be reviewed by QE as the correct method to remove the installation from the machine and then a new revision history entry should be added to the guide. Misha will push this public once it is reviewed and ready. > JBDS-IS: Add uninstall instructions to the Install Guide > -------------------------------------------------------- > > Key: TOOLSDOC-638 > URL: https://issues.jboss.org/browse/TOOLSDOC-638 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > We need instructions for how to uninstall JBDS-IS included in the Install Guide. This should be reviewed by QE as the correct method to remove the installation from the machine and then a new revision history entry should be added to the guide. Misha will push this public once it is reviewed and ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-638: ---------------------------------- Summary: JBDS-IS: Add uninstall instructions to the Install Guide Key: TOOLSDOC-638 URL: https://issues.jboss.org/browse/TOOLSDOC-638 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-638?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-638: ------------------------------- Sprint: 2015/S9 (27-Apr > 10-May) (was: 2015/S10 (11-May -> 24-May) 2) > JBDS-IS: Add uninstall instructions to the Install Guide > -------------------------------------------------------- > > Key: TOOLSDOC-638 > URL: https://issues.jboss.org/browse/TOOLSDOC-638 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-638?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-638: ---------------------------------- Assignee: Supriya Bharadwaj (was: Misha Ali) > JBDS-IS: Add uninstall instructions to the Install Guide > -------------------------------------------------------- > > Key: TOOLSDOC-638 > URL: https://issues.jboss.org/browse/TOOLSDOC-638 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-615) Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-615?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-615: ------------------------------- Sprint: 2015/S10 (11-May -> 24-May) 2 (was: 2015/S9 (27-Apr > 10-May)) > Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0 > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-615 > URL: https://issues.jboss.org/browse/TOOLSDOC-615 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Getting Started Guide > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > > Requirements: > * Use the current Start Developing Guide to test content > * Review contents and determine if this would be better as a new series of articles rather than a document for 9.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-595) Update Install doc when offline zip is finalized

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-595?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-595: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr), 2015/S10 (11-May -> 24-May) 2 (was: 2015/S7 (30-Mar > 12-Apr), 2015/S9 (27-Apr > 10-May)) > Update Install doc when offline zip is finalized > ------------------------------------------------ > > Key: TOOLSDOC-595 > URL: https://issues.jboss.org/browse/TOOLSDOC-595 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Installation Guide > Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.2.2.Final, 4.2.3.Beta1 > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.3.CR1 > > > See JBDS-3361. > Right now the 8.1 install doc states that you need 2 .zip files for installing JBDS BYOE when offline. This might be changed to 1 .zip or the 2 .zips might be downloadable from the same URL. This doc will need updating to reflect the outcome. > Also affects offline install of JBDS-IS in Eclipse - so that install doc needs updating to reflect the outcome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3308) Promote JBoss Tools CAT in JBT/JBDS About box

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3308?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3308: --------------------------------- Sprint: (was: Sprint #3 May 2015) > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBDS-3308 > URL: https://issues.jboss.org/browse/JBDS-3308 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Optional > Fix For: 9.0.0.Beta1 > > Attachments: about-jbds.png > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3308) Promote JBoss Tools CAT in JBT/JBDS About box

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3308?page=com.atlassian.jira.plugin.... ] Mickael Istria closed JBDS-3308. -------------------------------- Resolution: Rejected Rejecting as it seems that this wouldn't improve anything. We need to find other more visible ways to promote JBoss Tools CAT. > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBDS-3308 > URL: https://issues.jboss.org/browse/JBDS-3308 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Optional > Fix For: 9.0.0.Beta1 > > Attachments: about-jbds.png > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1234) Installer could check OS architecture

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-1234: -------------------------------------- [~dgolovin] Let's just close this issue as rejected. The installer and JBDS do support all supported OS correctly, so there is nothing to improve there. > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19718) No source zip produced when buildinfo.json can't be resolved

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19718?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19718: ---------------------------------------- Your PR was merged. I'm also suggested a few improvements, the most valuable one is to set a defaultValue for the property. https://github.com/jbosstools/jbosstools-maven-plugins/pull/40 > No source zip produced when buildinfo.json can't be resolved > ------------------------------------------------------------ > > Key: JBIDE-19718 > URL: https://issues.jboss.org/browse/JBIDE-19718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > From the latest master build: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... > {code} > [INFO] --- repository-utils:0.22.1-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.site.core --- > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ser... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jst... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-aer... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jav... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-web... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-vpe... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-arq... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-for... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-liv... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-cen... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/freemarker/... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bir... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... > [INFO] Building zip: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/org.jboss.tools.site.core-4.3.0-SNAPSHOT.zip > {code} > Seems the problem is twofold: > a) when no json files are found, we should fall back to another URL. (I think I might have an open PR for this.) > For example, instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... we should be looking at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > b) the generated sources zip needs to exist even it's empty (?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19718) No source zip produced when buildinfo.json can't be resolved

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19718?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19718: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-maven-plugins/pull/39, https://github.com/jbosstools/jbosstools-maven-plugins/pull/40 (was: https://github.com/jbosstools/jbosstools-maven-plugins/pull/39) > No source zip produced when buildinfo.json can't be resolved > ------------------------------------------------------------ > > Key: JBIDE-19718 > URL: https://issues.jboss.org/browse/JBIDE-19718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > From the latest master build: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... > {code} > [INFO] --- repository-utils:0.22.1-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.site.core --- > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ser... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jst... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-aer... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jav... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-web... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-vpe... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-arq... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-for... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-liv... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-cen... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/freemarker/... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bir... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... > [INFO] Building zip: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/org.jboss.tools.site.core-4.3.0-SNAPSHOT.zip > {code} > Seems the problem is twofold: > a) when no json files are found, we should fall back to another URL. (I think I might have an open PR for this.) > For example, instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... we should be looking at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > b) the generated sources zip needs to exist even it's empty (?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-637) JBDS-IS 8.0.2 - Installation Guide: Add information about Fuse Installer

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-637?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-637: ------------------------------- Description: Fuse Transformation Tooling [1] for Fuse 6.2 will be installed via JBDS-IS 8.0.2. Document how. [1] https://github.com/fabric8io/data-mapper > JBDS-IS 8.0.2 - Installation Guide: Add information about Fuse Installer > ------------------------------------------------------------------------ > > Key: TOOLSDOC-637 > URL: https://issues.jboss.org/browse/TOOLSDOC-637 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Fuse Transformation Tooling [1] for Fuse 6.2 will be installed via JBDS-IS 8.0.2. Document how. > [1] https://github.com/fabric8io/data-mapper -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-637) JBDS-IS 8.0.2 - Installation Guide: Add information about FTT Installation

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-637?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-637: ------------------------------- Summary: JBDS-IS 8.0.2 - Installation Guide: Add information about FTT Installation (was: JBDS-IS 8.0.2 - Installation Guide: Add information about Fuse Installer) > JBDS-IS 8.0.2 - Installation Guide: Add information about FTT Installation > -------------------------------------------------------------------------- > > Key: TOOLSDOC-637 > URL: https://issues.jboss.org/browse/TOOLSDOC-637 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Fuse Transformation Tooling [1] for Fuse 6.2 will be installed via JBDS-IS 8.0.2. Document how. > [1] https://github.com/fabric8io/data-mapper -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-637) JBDS-IS 8.0.2 - Installation Guide: Add information about Fuse Installer

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-637: ---------------------------------- Summary: JBDS-IS 8.0.2 - Installation Guide: Add information about Fuse Installer Key: TOOLSDOC-637 URL: https://issues.jboss.org/browse/TOOLSDOC-637 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2625) Provide on-line installer launchable via JNLP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2625?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2625: -------------------------------- Story Points: 1 > Provide on-line installer launchable via JNLP > --------------------------------------------- > > Key: JBDS-2625 > URL: https://issues.jboss.org/browse/JBDS-2625 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 7.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.x > > > Instead of always downloading offline installer and then run installation manually, would be good to have online version of installer that would let: > # start installer via JNLP > # select if EAP/WildFly should be installed too > (1) Should be easy to implement, because it requires only excluding update site bits from jar, provide URL for update site and create JNLP configuration; > (2) Requires EAP download integration into IzPack (would be good if IzPack has supported online installation itself) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3213) Installer hangs at P2 director when command prompt is disabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3213?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3213: -------------------------------- Story Points: 13 > Installer hangs at P2 director when command prompt is disabled > -------------------------------------------------------------- > > Key: JBDS-3213 > URL: https://issues.jboss.org/browse/JBDS-3213 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.GA > Environment: Windows 7 Ultimate with group policy "Prevent access to the command prompt" enabled > Reporter: Richard Hands > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Trying to install JBDS 8.0.0.GA in a customer locked down environment, on a windows machine which has the group policy for locking out the cmd prompt enabled causes the installer to hang at the P2 Director stage. Running with -DTRACE=TRUE shows that it gets to running java -jar ...JBDS.....jar but is trying to use some mechanism which on windows invokes the command prompt, and we end up with, in the console, the message > The command prompt has been disabled by your administrator. > Press any key to continue . . . > but this is hidden when not running in -DTRACE=TRUE mode, and even in trace mode, you can't hit a key as the installer has focus and not the console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19631: ---------------------------------- Story Points: 1 > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19631 > URL: https://issues.jboss.org/browse/JBIDE-19631 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[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: ---------------------------------- Story Points: 34 > 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.3.0.Beta1 > > 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.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3428) On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3428?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3428: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3428 > URL: https://issues.jboss.org/browse/JBDS-3428 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Target directory location should be checked for .app suffix and it should be added if missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3428) On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3428?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3428: -------------------------------- Description: Target directory location should be checked for .app suffix and it should be added if missing. Target Release: 9.0.0.GA Story Points: 8 > On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3428 > URL: https://issues.jboss.org/browse/JBDS-3428 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Target directory location should be checked for .app suffix and it should be added if missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3428) On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3428?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3428: -------------------------------- Fix Version/s: 9.0.0.Beta1 > On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3428 > URL: https://issues.jboss.org/browse/JBDS-3428 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3428) On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3428: ----------------------------------- Summary: On Mac OS X installer should create .app package in /Application/${appName}.app folder and use ~/Library/Application Management/${appName} for user's files Key: JBDS-3428 URL: https://issues.jboss.org/browse/JBDS-3428 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.0.0.Alpha2 Environment: Mac OS X Reporter: Denis Golovin Assignee: Denis Golovin -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3427) Filter installed graphical files per OS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3427?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3427: -------------------------------- Story Points: 3 > Filter installed graphical files per OS > --------------------------------------- > > Key: JBDS-3427 > URL: https://issues.jboss.org/browse/JBDS-3427 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > > Installer should not copy .ico files on Mac and Linux, also some .png files included installed on every supported OS are never used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3427) Filter installed graphical files per OS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3427?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3427: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > Filter installed graphical files per OS > --------------------------------------- > > Key: JBDS-3427 > URL: https://issues.jboss.org/browse/JBDS-3427 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > > Installer should not copy .ico files on Mac and Linux, also some .png files included installed on every supported OS are never used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3427) Filter installed graphical files per OS

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3427: ----------------------------------- Summary: Filter installed graphical files per OS Key: JBDS-3427 URL: https://issues.jboss.org/browse/JBDS-3427 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.0.0.Beta1 Reporter: Denis Golovin Assignee: Denis Golovin Installer should not copy .ico files on Mac and Linux, also some .png files included installed on every supported OS are never used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2877) Upgrade to use izpack 5

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2877?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2877: -------------------------------- Story Points: 13 > Upgrade to use izpack 5 > ----------------------- > > Key: JBDS-2877 > URL: https://issues.jboss.org/browse/JBDS-2877 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Over the years we have done various hacks to izpack 3 and 4 panels to make it behave well/as we wanted. > izpack 5 is rumored to have many of these fixes properly integrated thus it make sense to try and investigate if we should upgrade to izpack 5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3396) Online installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3396?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3396: -------------------------------- Story Points: 1 > Online installer > ----------------- > > Key: JBDS-3396 > URL: https://issues.jboss.org/browse/JBDS-3396 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.x > > > Online installer would contains only p2 director and install JBDS product from remote p2 repository -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2954) Embed p2director inside installer JVM instead communicating with external process through streams

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2954?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2954: ----------------------------- CDW devel_ack: (was: +) > Embed p2director inside installer JVM instead communicating with external process through streams > ------------------------------------------------------------------------------------------------- > > Key: JBDS-2954 > URL: https://issues.jboss.org/browse/JBDS-2954 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 6.0.1.GA, 7.0.0.GA, 7.0.1.GA, 7.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.x > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2954) Embed p2director inside installer JVM instead communicating with external process through streams

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2954?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2954: -------------------------------- CDW devel_ack: + Story Points: 13 > Embed p2director inside installer JVM instead communicating with external process through streams > ------------------------------------------------------------------------------------------------- > > Key: JBDS-2954 > URL: https://issues.jboss.org/browse/JBDS-2954 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 6.0.1.GA, 7.0.0.GA, 7.0.1.GA, 7.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.x > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2954) Embed p2director inside installer JVM instead communicating with external process through streams

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2954?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2954: -------------------------------- Sprint: Sprint #3 May 2015 > Embed p2director inside installer JVM instead communicating with external process through streams > ------------------------------------------------------------------------------------------------- > > Key: JBDS-2954 > URL: https://issues.jboss.org/browse/JBDS-2954 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 6.0.1.GA, 7.0.0.GA, 7.0.1.GA, 7.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.x > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3379: -------------------------------- CDW devel_ack: + (was: ?) Story Points: 1 > Error message in JBDS when installing into existing folder needs work > --------------------------------------------------------------------- > > Key: JBDS-3379 > URL: https://issues.jboss.org/browse/JBDS-3379 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > Attachments: over-the-top-message-JBDS8.1Beta1.png > > > Got an error message trying to install JBDS into an existing JBDS folder: > {quote}You can't upgrade by installing over the top (sic){quote} > !over-the-top-message-JBDS8.1Beta1.png! > We should consider fixing this message in JBDS 9. Perhaps something like this? > {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2635: -------------------------------- Sprint: Sprint 20141112, Sprint to CR1 Release (was: Sprint 20141112, Sprint to CR1 Release, Sprint #3 May 2015) > Installation sometimes fail with bundle was not found on Windows > ---------------------------------------------------------------- > > Key: JBDS-2635 > URL: https://issues.jboss.org/browse/JBDS-2635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 7.0.0.Beta1 > Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log > > > For the first time JBDS 7.0.0.Beta1 failed on windows8: > {code} > An error occurred while installing the items > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found. > Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17281: ---------------------------------- Story Points: 1 > parent/pom.xml build/plugins should reference plugins defined build/pluginManagement > ------------------------------------------------------------------------------------ > > Key: JBIDE-17281 > URL: https://issues.jboss.org/browse/JBIDE-17281 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Fix For: 4.3.x > > > The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and dcluttering in jbosstools modules like: > - remove <version>${tychoVersion}</version> > - move jacoco plugin to tests/pom.xml > - move update site manipulations to site/pom.xml > - etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19335: ---------------------------------- Story Points: 5 > org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19335 > URL: https://issues.jboss.org/browse/JBIDE-19335 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, runtime-detection > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Environment: Linux > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3359: -------------------------------- Story Points: 13 > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.1.1.GA > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3308) Promote JBoss Tools CAT in JBT/JBDS About box

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3308?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3308: -------------------------------- Story Points: 1 > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBDS-3308 > URL: https://issues.jboss.org/browse/JBDS-3308 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Optional > Fix For: 9.0.0.Beta1 > > Attachments: about-jbds.png > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3408: ----------------------------------- Assignee: Nick Boldt (was: Denis Golovin) Assigning to Nick, who has volunteered to check the problem :) > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19590: ---------------------------------- Story Points: 3 > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19474) org.jboss.tools.foundation.help.ui is not included into foundation feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19474?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19474: ---------------------------------- Story Points: 1 > org.jboss.tools.foundation.help.ui is not included into foundation feature > -------------------------------------------------------------------------- > > Key: JBIDE-19474 > URL: https://issues.jboss.org/browse/JBIDE-19474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18815) Include freemarker.jar in FreeMarker IDE as maven dependency

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18815?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18815: ---------------------------------- Story Points: 1 > Include freemarker.jar in FreeMarker IDE as maven dependency > ------------------------------------------------------------ > > Key: JBIDE-18815 > URL: https://issues.jboss.org/browse/JBIDE-18815 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.2.0.Final > Reporter: Daniel Dekany > Assignee: Denis Golovin > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3390) Create test to verify offline installation for JBoss Developer Studio installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3390?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3390: -------------------------------- Story Points: 1 > Create test to verify offline installation for JBoss Developer Studio installer > ------------------------------------------------------------------------------- > > Key: JBDS-3390 > URL: https://issues.jboss.org/browse/JBDS-3390 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Should be possible to implement using java policies to disable internet access for JVM instance and run installer in automated mode. > It should be running at integration-tests phase and should fail in case of installer failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3425) Disable Unintsaller generation for Mac OS X

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3425?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3425: -------------------------------- Story Points: 1 > Disable Unintsaller generation for Mac OS X > ------------------------------------------- > > Key: JBDS-3425 > URL: https://issues.jboss.org/browse/JBDS-3425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Uninstaller doesn't make sense for Mac platform, because it is literally just removing .app package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3411: -------------------------------- Story Points: 5 > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3410) devstudio not reading jbdevstudio.ini on osx

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3410?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3410: -------------------------------- Story Points: 1 > devstudio not reading jbdevstudio.ini on osx > -------------------------------------------- > > Key: JBDS-3410 > URL: https://issues.jboss.org/browse/JBDS-3410 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > When starting on OSX it has noticable larger fonts than previous versions. > It seems to be ignoring -Dorg.eclipse.swt.internal.carbon.smallFonts set in jbdevstudio.ini. > comparing jbdevstudio8 vs 9 I see that in 8 the location was: > studio/jbdevstudio.app/Contents/MacOS/jbdevstudio.ini > but in 9 we have it at > studio/jbdevstudio.ini > so that could explain why it wont get picked up ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[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 20141112, Sprint to CR1 Release, Sprint #4 May 2015 (was: Sprint 20141112, 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.3.0.Beta1 > > 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.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3425) Disable Unintsaller generation for Mac OS X

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3425?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3425: -------------------------------- Fix Version/s: 9.0.0.Beta1 > Disable Unintsaller generation for Mac OS X > ------------------------------------------- > > Key: JBDS-3425 > URL: https://issues.jboss.org/browse/JBDS-3425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Uninstaller doesn't make sense for Mac platform, because it is literally just removing .app package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19631: ---------------------------------- Sprint: Sprint #4 May 2015 > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19631 > URL: https://issues.jboss.org/browse/JBIDE-19631 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3411: -------------------------------- Sprint: Sprint #2 April 2015 > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3070) Mixed fonts in installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3070?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3070: -------------------------------- Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015, Sprint #3 May 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015) > Mixed fonts in installer > ------------------------ > > Key: JBDS-3070 > URL: https://issues.jboss.org/browse/JBDS-3070 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.x, 9.0.x > > > since JBDS-3036 its become very obvious in the installer that the fonts are scrwed. > See http://screencast.com/t/ebR5zm1Cmmmw > On here is at least 3 or 4 different fonts. > Should use same clean fonts IMO -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19590: ---------------------------------- Sprint: Sprint #3 May 2015 > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3408: -------------------------------- Sprint: Sprint #3 May 2015 > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3308) Promote JBoss Tools CAT in JBT/JBDS About box

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3308?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3308: -------------------------------- Sprint: Sprint #3 May 2015 > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBDS-3308 > URL: https://issues.jboss.org/browse/JBDS-3308 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Optional > Fix For: 9.0.0.Beta1 > > Attachments: about-jbds.png > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19474) org.jboss.tools.foundation.help.ui is not included into foundation feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19474?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19474: ---------------------------------- Sprint: Sprint #2 April 2015 > org.jboss.tools.foundation.help.ui is not included into foundation feature > -------------------------------------------------------------------------- > > Key: JBIDE-19474 > URL: https://issues.jboss.org/browse/JBIDE-19474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19474) org.jboss.tools.foundation.help.ui is not included into foundation feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19474?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19474: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > org.jboss.tools.foundation.help.ui is not included into foundation feature > -------------------------------------------------------------------------- > > Key: JBIDE-19474 > URL: https://issues.jboss.org/browse/JBIDE-19474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19474) org.jboss.tools.foundation.help.ui is not included into foundation feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19474?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19474: ---------------------------------- Fix Version/s: 4.3.0.Alpha2 > org.jboss.tools.foundation.help.ui is not included into foundation feature > -------------------------------------------------------------------------- > > Key: JBIDE-19474 > URL: https://issues.jboss.org/browse/JBIDE-19474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18815) Include freemarker.jar in FreeMarker IDE as maven dependency

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18815?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18815: ---------------------------------- Sprint: Sprint #2 April 2015 > Include freemarker.jar in FreeMarker IDE as maven dependency > ------------------------------------------------------------ > > Key: JBIDE-18815 > URL: https://issues.jboss.org/browse/JBIDE-18815 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.2.0.Final > Reporter: Daniel Dekany > Assignee: Denis Golovin > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19335: ---------------------------------- Sprint: Sprint #3 May 2015 > org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19335 > URL: https://issues.jboss.org/browse/JBIDE-19335 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, runtime-detection > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Environment: Linux > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3359: -------------------------------- Sprint: Sprint #3 May 2015 > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.1.1.GA > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17281: ---------------------------------- Sprint: Sprint #3 May 2015 > parent/pom.xml build/plugins should reference plugins defined build/pluginManagement > ------------------------------------------------------------------------------------ > > Key: JBIDE-17281 > URL: https://issues.jboss.org/browse/JBIDE-17281 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Fix For: 4.3.x > > > The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and dcluttering in jbosstools modules like: > - remove <version>${tychoVersion}</version> > - move jacoco plugin to tests/pom.xml > - move update site manipulations to site/pom.xml > - etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3004) UnInstaller should have the same application icon as JBoss Developer Studio and appropriate name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3004?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3004: -------------------------------- Sprint: Sprint 20141112, Sprint to CR1 Release (was: Sprint 20141112, Sprint to CR1 Release, Sprint #2 April 2015) > UnInstaller should have the same application icon as JBoss Developer Studio and appropriate name > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3004 > URL: https://issues.jboss.org/browse/JBDS-3004 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.x > > > See linked Jira about installer icon. I think we should apply the same to Uninstaller icon. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3410) devstudio not reading jbdevstudio.ini on osx

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3410?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3410: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 8.0.0.Alpha2) > devstudio not reading jbdevstudio.ini on osx > -------------------------------------------- > > Key: JBDS-3410 > URL: https://issues.jboss.org/browse/JBDS-3410 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > When starting on OSX it has noticable larger fonts than previous versions. > It seems to be ignoring -Dorg.eclipse.swt.internal.carbon.smallFonts set in jbdevstudio.ini. > comparing jbdevstudio8 vs 9 I see that in 8 the location was: > studio/jbdevstudio.app/Contents/MacOS/jbdevstudio.ini > but in 9 we have it at > studio/jbdevstudio.ini > so that could explain why it wont get picked up ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3410) devstudio not reading jbdevstudio.ini on osx

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3410?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3410: -------------------------------- Sprint: Sprint #2 April 2015 > devstudio not reading jbdevstudio.ini on osx > -------------------------------------------- > > Key: JBDS-3410 > URL: https://issues.jboss.org/browse/JBDS-3410 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > When starting on OSX it has noticable larger fonts than previous versions. > It seems to be ignoring -Dorg.eclipse.swt.internal.carbon.smallFonts set in jbdevstudio.ini. > comparing jbdevstudio8 vs 9 I see that in 8 the location was: > studio/jbdevstudio.app/Contents/MacOS/jbdevstudio.ini > but in 9 we have it at > studio/jbdevstudio.ini > so that could explain why it wont get picked up ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3426) eclipse freezes after first start

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3426?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3426: -------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: Tools (JBoss Tools)) Key: JBDS-3426 (was: JBIDE-19582) Workflow: CDW v1 (was: GIT Pull Request workflow ) Affects Version/s: 9.0.0.Alpha2 (was: 4.3.0.Alpha2) Component/s: installer (was: common/jst/core) Docs QE Status: NEW > eclipse freezes after first start > --------------------------------- > > Key: JBDS-3426 > URL: https://issues.jboss.org/browse/JBDS-3426 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Environment: Mac OS X Yosemite 10.10.1, Java 1.7 > Reporter: Denis Golovin > Assignee: Denis Golovin > > {code}Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode): > "Attach Listener" daemon prio=5 tid=0x00000001021be800 nid=0x108bf runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Provisioning Event Dispatcher" daemon prio=5 tid=0x00000008e07a4000 nid=0xe24b in Object.wait() [0x00000008e2400000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Worker-5" prio=5 tid=0x00000001020b0000 nid=0xc803 in Object.wait() [0x00000008e2676000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) > - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52) > "Worker-3" prio=5 tid=0x0000000101b68000 nid=0xc613 in Object.wait() [0x00000008e166d000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) > - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52) > "EventAdmin Async Event Dispatcher Thread" daemon prio=5 tid=0x000000010138c800 nid=0x8c2b in Object.wait() [0x00000008e0ed3000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:200) > - locked <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4754) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212) > at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.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) > "Timer-0" daemon prio=5 tid=0x00000008e05d9000 nid=0x653b runnable [0x00000008e0dcf000] > java.lang.Thread.State: RUNNABLE > at java.util.regex.Pattern$BnM.optimize(Pattern.java:5334) > at java.util.regex.Pattern.compile(Pattern.java:1678) > at java.util.regex.Pattern.<init>(Pattern.java:1337) > at java.util.regex.Pattern.compile(Pattern.java:1022) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:82) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:66) > at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.<init>(MonitoredHostProvider.java:59) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:214) > at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:143) > 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.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:507) > - locked <0x0000000112421e68> (a org.jboss.tools.common.jdt.debug.tools.internal.Tools) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:517) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:150) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > "[ThreadPool Manager] - Idle Thread" daemon prio=5 tid=0x00000001008f8000 nid=0x8b5f in Object.wait() [0x00000008e0b65000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106) > - locked <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) > "Java indexing" daemon prio=5 tid=0x0000000100a09800 nid=0xb867 in Object.wait() [0x00000008dfd0f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:382) > - locked <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) > at java.lang.Thread.run(Thread.java:722) > "Bundle File Closer" daemon prio=5 tid=0x00000008e01a6000 nid=0xb78b in Object.wait() [0x00000008df592000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "EMF Reference Cleaner" daemon prio=5 tid=0x00000001010d1800 nid=0x9503 in Object.wait() [0x00000008df3de000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at org.eclipse.emf.common.util.CommonUtil$1ReferenceClearingQueuePollingThread.run(CommonUtil.java:70) > "Worker-JM" prio=5 tid=0x0000000100a66000 nid=0x932b in Object.wait() [0x00000008df99d000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939c88> (a java.util.ArrayList) > at org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:59) > - locked <0x0000000112939c88> (a java.util.ArrayList) > "[Timer] - Main Queue Handler" daemon prio=5 tid=0x0000000101271800 nid=0x9027 in Object.wait() [0x00000008df868000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939e18> (a java.lang.Object) > at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:141) > - locked <0x0000000112939e18> (a java.lang.Object) > at java.lang.Thread.run(Thread.java:722) > "Start Level: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x000000010115d000 nid=0x8f03 in Object.wait() [0x00000008df2db000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Framework Event Dispatcher: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x0000000100a96000 nid=0x8d0f in Object.wait() [0x00000008df1d8000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Active Thread: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" prio=5 tid=0x0000000100a2f800 nid=0x8e07 waiting on condition [0x00000008dedff000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x0000000112523618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > "Service Thread" daemon prio=5 tid=0x00000001010a5000 nid=0x5b03 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread1" daemon prio=5 tid=0x00000001010a4000 nid=0x5a03 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" daemon prio=5 tid=0x000000010109f800 nid=0x5907 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" daemon prio=5 tid=0x0000000100851000 nid=0x570f runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" daemon prio=5 tid=0x0000000101092000 nid=0x5503 in Object.wait() [0x00000008db873000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:177) > "Reference Handler" daemon prio=5 tid=0x000000010108b800 nid=0x5403 in Object.wait() [0x00000008db770000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000001125353b0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:503) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133) > - locked <0x00000001125353b0> (a java.lang.ref.Reference$Lock) > "main" prio=5 tid=0x000000010200b800 nid=0x130f runnable [0x00007fff5fbfc000] > java.lang.Thread.State: RUNNABLE > at org.eclipse.core.commands.common.HandleObject.hashCode(HandleObject.java:137) > at org.eclipse.core.internal.commands.util.Util.hashCode(Util.java:266) > at org.eclipse.core.commands.ParameterizedCommand.hashCode(ParameterizedCommand.java:615) > at java.util.HashMap.hash(HashMap.java:351) > at java.util.HashMap.getEntry(HashMap.java:443) > at java.util.HashMap.get(HashMap.java:405) > at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor(BindingManager.java:1161) > at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor1(BindingManager.java:1210) > at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1275) > at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1265) > at org.eclipse.jface.action.ExternalActionManager$CommandCallback.getAcceleratorText(ExternalActionManager.java:323) > at org.eclipse.jface.action.ActionContributionItem.update(ActionContributionItem.java:907) > at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859) > at org.eclipse.jface.action.SubMenuManager.update(SubMenuManager.java:343) > at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859) > at org.eclipse.ui.internal.Workbench.updateActiveWorkbenchWindowMenuManager(Workbench.java:3373) > at org.eclipse.ui.internal.Workbench.access$0(Workbench.java:3359) > at org.eclipse.ui.internal.Workbench$1.bindingManagerChanged(Workbench.java:3354) > at org.eclipse.jface.bindings.BindingManager.fireBindingManagerChanged(BindingManager.java:901) > at org.eclipse.jface.bindings.BindingManager.setActiveBindings(BindingManager.java:2178) > at org.eclipse.jface.bindings.BindingManager.recomputeBindings(BindingManager.java:1743) > at org.eclipse.jface.bindings.BindingManager.contextManagerChanged(BindingManager.java:690) > at org.eclipse.core.commands.contexts.ContextManager.fireContextManagerChanged(ContextManager.java:165) > at org.eclipse.core.commands.contexts.ContextManager.setActiveContextIds(ContextManager.java:295) > at org.eclipse.e4.ui.services.ContextServiceAddon$1.changed(ContextServiceAddon.java:47) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110) > at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:333) > at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:347) > at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:191) > at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$3.widgetDisposed(ShellActivationListener.java:182) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1471) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1308) > at org.eclipse.swt.widgets.Control.release(Control.java:2867) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671) > at org.eclipse.jface.window.Window.close(Window.java:334) > at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:990) > at org.eclipse.jface.dialogs.MessageDialog.buttonPressed(MessageDialog.java:204) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:330) > at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:360) > at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:455) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:186) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$2(RemoteJavaApplicationLaunchShortcut.java:183) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$2.run(RemoteJavaApplicationLaunchShortcut.java:116) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > - locked <0x000000011293a5a8> (a org.eclipse.swt.widgets.RunnableLock) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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) > "VM Thread" prio=5 tid=0x000000010200c000 nid=0x5303 runnable > "GC task thread#0 (ParallelGC)" prio=5 tid=0x0000000100832000 nid=0x4f03 runnable > "GC task thread#1 (ParallelGC)" prio=5 tid=0x0000000101054800 nid=0x5003 runnable > "GC task thread#2 (ParallelGC)" prio=5 tid=0x000000010104f800 nid=0x5103 runnable > "GC task thread#3 (ParallelGC)" prio=5 tid=0x000000010105d800 nid=0x5203 runnable > "VM Periodic Task Thread" prio=5 tid=0x0000000100851800 nid=0x5c03 waiting on condition > JNI global references: 911{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3426) eclipse freezes after first start

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3426?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3426. ------------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Duplicate Issue > eclipse freezes after first start > --------------------------------- > > Key: JBDS-3426 > URL: https://issues.jboss.org/browse/JBDS-3426 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Environment: Mac OS X Yosemite 10.10.1, Java 1.7 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > {code}Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode): > "Attach Listener" daemon prio=5 tid=0x00000001021be800 nid=0x108bf runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Provisioning Event Dispatcher" daemon prio=5 tid=0x00000008e07a4000 nid=0xe24b in Object.wait() [0x00000008e2400000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Worker-5" prio=5 tid=0x00000001020b0000 nid=0xc803 in Object.wait() [0x00000008e2676000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) > - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52) > "Worker-3" prio=5 tid=0x0000000101b68000 nid=0xc613 in Object.wait() [0x00000008e166d000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) > - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool) > at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52) > "EventAdmin Async Event Dispatcher Thread" daemon prio=5 tid=0x000000010138c800 nid=0x8c2b in Object.wait() [0x00000008e0ed3000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:200) > - locked <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4754) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212) > at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.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) > "Timer-0" daemon prio=5 tid=0x00000008e05d9000 nid=0x653b runnable [0x00000008e0dcf000] > java.lang.Thread.State: RUNNABLE > at java.util.regex.Pattern$BnM.optimize(Pattern.java:5334) > at java.util.regex.Pattern.compile(Pattern.java:1678) > at java.util.regex.Pattern.<init>(Pattern.java:1337) > at java.util.regex.Pattern.compile(Pattern.java:1022) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:82) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:66) > at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.<init>(MonitoredHostProvider.java:59) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:214) > at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:143) > 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.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:507) > - locked <0x0000000112421e68> (a org.jboss.tools.common.jdt.debug.tools.internal.Tools) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:517) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:150) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > "[ThreadPool Manager] - Idle Thread" daemon prio=5 tid=0x00000001008f8000 nid=0x8b5f in Object.wait() [0x00000008e0b65000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106) > - locked <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) > "Java indexing" daemon prio=5 tid=0x0000000100a09800 nid=0xb867 in Object.wait() [0x00000008dfd0f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:382) > - locked <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) > at java.lang.Thread.run(Thread.java:722) > "Bundle File Closer" daemon prio=5 tid=0x00000008e01a6000 nid=0xb78b in Object.wait() [0x00000008df592000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "EMF Reference Cleaner" daemon prio=5 tid=0x00000001010d1800 nid=0x9503 in Object.wait() [0x00000008df3de000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at org.eclipse.emf.common.util.CommonUtil$1ReferenceClearingQueuePollingThread.run(CommonUtil.java:70) > "Worker-JM" prio=5 tid=0x0000000100a66000 nid=0x932b in Object.wait() [0x00000008df99d000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939c88> (a java.util.ArrayList) > at org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:59) > - locked <0x0000000112939c88> (a java.util.ArrayList) > "[Timer] - Main Queue Handler" daemon prio=5 tid=0x0000000101271800 nid=0x9027 in Object.wait() [0x00000008df868000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112939e18> (a java.lang.Object) > at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:141) > - locked <0x0000000112939e18> (a java.lang.Object) > at java.lang.Thread.run(Thread.java:722) > "Start Level: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x000000010115d000 nid=0x8f03 in Object.wait() [0x00000008df2db000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Framework Event Dispatcher: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x0000000100a96000 nid=0x8d0f in Object.wait() [0x00000008df1d8000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at java.lang.Object.wait(Object.java:503) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) > - locked <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) > "Active Thread: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" prio=5 tid=0x0000000100a2f800 nid=0x8e07 waiting on condition [0x00000008dedff000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x0000000112523618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > "Service Thread" daemon prio=5 tid=0x00000001010a5000 nid=0x5b03 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread1" daemon prio=5 tid=0x00000001010a4000 nid=0x5a03 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" daemon prio=5 tid=0x000000010109f800 nid=0x5907 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" daemon prio=5 tid=0x0000000100851000 nid=0x570f runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" daemon prio=5 tid=0x0000000101092000 nid=0x5503 in Object.wait() [0x00000008db873000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:177) > "Reference Handler" daemon prio=5 tid=0x000000010108b800 nid=0x5403 in Object.wait() [0x00000008db770000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000001125353b0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:503) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133) > - locked <0x00000001125353b0> (a java.lang.ref.Reference$Lock) > "main" prio=5 tid=0x000000010200b800 nid=0x130f runnable [0x00007fff5fbfc000] > java.lang.Thread.State: RUNNABLE > at org.eclipse.core.commands.common.HandleObject.hashCode(HandleObject.java:137) > at org.eclipse.core.internal.commands.util.Util.hashCode(Util.java:266) > at org.eclipse.core.commands.ParameterizedCommand.hashCode(ParameterizedCommand.java:615) > at java.util.HashMap.hash(HashMap.java:351) > at java.util.HashMap.getEntry(HashMap.java:443) > at java.util.HashMap.get(HashMap.java:405) > at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor(BindingManager.java:1161) > at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor1(BindingManager.java:1210) > at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1275) > at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1265) > at org.eclipse.jface.action.ExternalActionManager$CommandCallback.getAcceleratorText(ExternalActionManager.java:323) > at org.eclipse.jface.action.ActionContributionItem.update(ActionContributionItem.java:907) > at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859) > at org.eclipse.jface.action.SubMenuManager.update(SubMenuManager.java:343) > at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859) > at org.eclipse.ui.internal.Workbench.updateActiveWorkbenchWindowMenuManager(Workbench.java:3373) > at org.eclipse.ui.internal.Workbench.access$0(Workbench.java:3359) > at org.eclipse.ui.internal.Workbench$1.bindingManagerChanged(Workbench.java:3354) > at org.eclipse.jface.bindings.BindingManager.fireBindingManagerChanged(BindingManager.java:901) > at org.eclipse.jface.bindings.BindingManager.setActiveBindings(BindingManager.java:2178) > at org.eclipse.jface.bindings.BindingManager.recomputeBindings(BindingManager.java:1743) > at org.eclipse.jface.bindings.BindingManager.contextManagerChanged(BindingManager.java:690) > at org.eclipse.core.commands.contexts.ContextManager.fireContextManagerChanged(ContextManager.java:165) > at org.eclipse.core.commands.contexts.ContextManager.setActiveContextIds(ContextManager.java:295) > at org.eclipse.e4.ui.services.ContextServiceAddon$1.changed(ContextServiceAddon.java:47) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110) > at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:333) > at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:347) > at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:191) > at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$3.widgetDisposed(ShellActivationListener.java:182) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1471) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1308) > at org.eclipse.swt.widgets.Control.release(Control.java:2867) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671) > at org.eclipse.jface.window.Window.close(Window.java:334) > at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:990) > at org.eclipse.jface.dialogs.MessageDialog.buttonPressed(MessageDialog.java:204) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:330) > at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:360) > at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:455) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:186) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$2(RemoteJavaApplicationLaunchShortcut.java:183) > at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$2.run(RemoteJavaApplicationLaunchShortcut.java:116) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > - locked <0x000000011293a5a8> (a org.eclipse.swt.widgets.RunnableLock) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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) > "VM Thread" prio=5 tid=0x000000010200c000 nid=0x5303 runnable > "GC task thread#0 (ParallelGC)" prio=5 tid=0x0000000100832000 nid=0x4f03 runnable > "GC task thread#1 (ParallelGC)" prio=5 tid=0x0000000101054800 nid=0x5003 runnable > "GC task thread#2 (ParallelGC)" prio=5 tid=0x000000010104f800 nid=0x5103 runnable > "GC task thread#3 (ParallelGC)" prio=5 tid=0x000000010105d800 nid=0x5203 runnable > "VM Periodic Task Thread" prio=5 tid=0x0000000100851800 nid=0x5c03 waiting on condition > JNI global references: 911{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3410) devstudio not reading jbdevstudio.ini on osx

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3410?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3410: -------------------------------- Fix Version/s: (was: 9.0.0.Beta1) > devstudio not reading jbdevstudio.ini on osx > -------------------------------------------- > > Key: JBDS-3410 > URL: https://issues.jboss.org/browse/JBDS-3410 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > When starting on OSX it has noticable larger fonts than previous versions. > It seems to be ignoring -Dorg.eclipse.swt.internal.carbon.smallFonts set in jbdevstudio.ini. > comparing jbdevstudio8 vs 9 I see that in 8 the location was: > studio/jbdevstudio.app/Contents/MacOS/jbdevstudio.ini > but in 9 we have it at > studio/jbdevstudio.ini > so that could explain why it wont get picked up ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3410) devstudio not reading jbdevstudio.ini on osx

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3410?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3410: -------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 9.0.0.Beta2) > devstudio not reading jbdevstudio.ini on osx > -------------------------------------------- > > Key: JBDS-3410 > URL: https://issues.jboss.org/browse/JBDS-3410 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > When starting on OSX it has noticable larger fonts than previous versions. > It seems to be ignoring -Dorg.eclipse.swt.internal.carbon.smallFonts set in jbdevstudio.ini. > comparing jbdevstudio8 vs 9 I see that in 8 the location was: > studio/jbdevstudio.app/Contents/MacOS/jbdevstudio.ini > but in 9 we have it at > studio/jbdevstudio.ini > so that could explain why it wont get picked up ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1234) Installer could check OS architecture

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1234: -------------------------------- Sprint: (was: Sprint #2 April 2015) > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work with remote server docs missing

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-620: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May) (was: 2015/S8 (13-Apr > 26-Apr)) > How to work with remote server docs missing > ------------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-636) JBDS-IS: Create a FAQ article and add to the splash page

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-636?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-636: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May) (was: 2015/S8 (13-Apr > 26-Apr)) > JBDS-IS: Create a FAQ article and add to the splash page > -------------------------------------------------------- > > Key: TOOLSDOC-636 > URL: https://issues.jboss.org/browse/TOOLSDOC-636 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create a frequently asked questions article and add it to the splash page for JBDS-IS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3379: -------------------------------- Sprint: Sprint #3 May 2015 > Error message in JBDS when installing into existing folder needs work > --------------------------------------------------------------------- > > Key: JBDS-3379 > URL: https://issues.jboss.org/browse/JBDS-3379 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > Attachments: over-the-top-message-JBDS8.1Beta1.png > > > Got an error message trying to install JBDS into an existing JBDS folder: > {quote}You can't upgrade by installing over the top (sic){quote} > !over-the-top-message-JBDS8.1Beta1.png! > We should consider fixing this message in JBDS 9. Perhaps something like this? > {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-562) OpenShift How To: Add final section to First OS App for viewing created app in browser

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-562?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-562: ------------------------------- Sprint: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec), 2014/S23 (8-Dec > 21-Dec), 2014/S24 (22-Dec > 04-Jan), 2015/S1 (05-Jan > 18-Jan), 2015/S2+3 (19-Jan > 15-Feb), 2015/S4 (16-Feb > 01-Mar), 2015/S5 (02-Mar > 15-Mar), 2015/S6 (16-Mar > 29-Mar), 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May) (was: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec), 2014/S23 (8-Dec > 21-Dec), 2014/S24 (22-Dec > 04-Jan), 2015/S1 (05-Jan > 18-Jan), 2015/S2+3 (19-Jan > 15-Feb), 2015/S4 (16-Feb > 01-Mar), 2015/S5 (02-Mar > 15-Mar), 2015/S6 (16-Mar > 29-Mar), 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr)) > OpenShift How To: Add final section to First OS App for viewing created app in browser > -------------------------------------------------------------------------------------- > > Key: TOOLSDOC-562 > URL: https://issues.jboss.org/browse/TOOLSDOC-562 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > > See: http://tools.jboss.org/documentation/howto/openshift_firstapp.html > Source: https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... > Before 'Terminology', add a new section with instructions for viewing the application in a browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-621) Rework and Finalize Article about Generating a HTML5 Web App

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-621?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-621: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May) (was: 2015/S7 (30-Mar > 12-Apr), 2015/S8 (13-Apr > 26-Apr)) > Rework and Finalize Article about Generating a HTML5 Web App > ------------------------------------------------------------ > > Key: TOOLSDOC-621 > URL: https://issues.jboss.org/browse/TOOLSDOC-621 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-623: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr), 2015/S9 (27-Apr > 10-May) (was: 2015/S8 (13-Apr > 26-Apr)) > Add FeedHenry Information to Existing Article about Hybrid Mobile Apps > ---------------------------------------------------------------------- > > Key: TOOLSDOC-623 > URL: https://issues.jboss.org/browse/TOOLSDOC-623 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Burr Sutter > Assignee: Supriya Bharadwaj > Fix For: 4.2.3.Final > > > Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 > Description: https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3390) Create test to verify offline installation for JBoss Developer Studio installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3390?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3390: -------------------------------- Sprint: Sprint #2 April 2015 > Create test to verify offline installation for JBoss Developer Studio installer > ------------------------------------------------------------------------------- > > Key: JBDS-3390 > URL: https://issues.jboss.org/browse/JBDS-3390 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Should be possible to implement using java policies to disable internet access for JVM instance and run installer in automated mode. > It should be running at integration-tests phase and should fail in case of installer failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1234) Installer could check OS architecture

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1234: -------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1234) Installer could check OS architecture

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1234: -------------------------------- Sprint: Sprint #2 April 2015 > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1696) seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1696?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-1696: ------------------------------------- Nick, can we close this? It seems to be really dated issue. > seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that? > ---------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1696 > URL: https://issues.jboss.org/browse/JBDS-1696 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 4.1.0.CR2, 5.0.0.M2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > An error like this is thrown EVERY TIME I install JBDS onto Fedora 12 32-bit. > Is this a problem @ my end or something we can fix or at least suppress? > $ java -jar jbdevstudio-product-linux-gtk-5.0.0.v201106180702R-H3-M2.jar > Jun 20, 2011 12:06:03 PM com.sun.corba.se.impl.ior.IORImpl getProfile > WARNING: "IOP00511201: (INV_OBJREF) IOR must have at least one IIOP profile" > org.omg.CORBA.INV_OBJREF: vmcid: SUN minor code: 1201 completed: No > at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:473) > at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:495) > at com.sun.corba.se.impl.ior.IORImpl.getProfile(IORImpl.java:334) > at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:787) > at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:761) > at com.sun.corba.se.impl.encoding.CDRInputStream.read_Object(CDRInputStream.java:231) > at com.sun.corba.se.impl.resolver.INSURLOperationImpl.getIORFromString(INSURLOperationImpl.java:120) > at com.sun.corba.se.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:130) > at com.sun.corba.se.impl.orb.ORBImpl.string_to_object(ORBImpl.java:836) > at org.GNOME.Accessibility.AccessUtil.getRegistryObject(AccessUtil.java:143) > at org.GNOME.Accessibility.JavaBridge.registerApplication(JavaBridge.java:1099) > at org.GNOME.Accessibility.JavaBridge.<init>(JavaBridge.java:364) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:786) > at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:875) > at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:480) > at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249) > at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at javax.swing.SwingUtilities.loadSystemClass(SwingUtilities.java:1875) > at javax.swing.UIManager.setLookAndFeel(UIManager.java:573) > at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller.init(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller.<init>(Unknown Source) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at com.izforge.izpack.installer.Installer.main(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1696) seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1696?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-1696: ----------------------------------- Assignee: Nick Boldt (was: Denis Golovin) > seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that? > ---------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1696 > URL: https://issues.jboss.org/browse/JBDS-1696 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 4.1.0.CR2, 5.0.0.M2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > An error like this is thrown EVERY TIME I install JBDS onto Fedora 12 32-bit. > Is this a problem @ my end or something we can fix or at least suppress? > $ java -jar jbdevstudio-product-linux-gtk-5.0.0.v201106180702R-H3-M2.jar > Jun 20, 2011 12:06:03 PM com.sun.corba.se.impl.ior.IORImpl getProfile > WARNING: "IOP00511201: (INV_OBJREF) IOR must have at least one IIOP profile" > org.omg.CORBA.INV_OBJREF: vmcid: SUN minor code: 1201 completed: No > at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:473) > at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:495) > at com.sun.corba.se.impl.ior.IORImpl.getProfile(IORImpl.java:334) > at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:787) > at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:761) > at com.sun.corba.se.impl.encoding.CDRInputStream.read_Object(CDRInputStream.java:231) > at com.sun.corba.se.impl.resolver.INSURLOperationImpl.getIORFromString(INSURLOperationImpl.java:120) > at com.sun.corba.se.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:130) > at com.sun.corba.se.impl.orb.ORBImpl.string_to_object(ORBImpl.java:836) > at org.GNOME.Accessibility.AccessUtil.getRegistryObject(AccessUtil.java:143) > at org.GNOME.Accessibility.JavaBridge.registerApplication(JavaBridge.java:1099) > at org.GNOME.Accessibility.JavaBridge.<init>(JavaBridge.java:364) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:786) > at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:875) > at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:480) > at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249) > at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at javax.swing.SwingUtilities.loadSystemClass(SwingUtilities.java:1875) > at javax.swing.UIManager.setLookAndFeel(UIManager.java:573) > at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller.init(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller.<init>(Unknown Source) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at com.izforge.izpack.installer.Installer.main(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2044: ------------------------------------- It seems not right approach to override what is inside .eclipse product file because it is used here http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... to search for writable configuration location. > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19532: ------------------------------------- Note for future: Denis has put a path that is functionally identical to serverhome in the base-directory text field. Efforts should be made to warn here if the given folder does not have the expected folders such as configuration , data, log, tmp, etc. > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3276: ------------------------------------- Asigning to [~pleacu], because installer side work is done and released to master. > JBDS-IS Installer > ----------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3276: ----------------------------------- Assignee: Paul Leacu (was: Denis Golovin) > JBDS-IS Installer > ----------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19665) hibernate New and Noteworthy for 4.3.0.Alpha2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19665?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19665. --------------------------------------- Resolution: Rejected > hibernate New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19665 > URL: https://issues.jboss.org/browse/JBIDE-19665 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Alexey Kazakov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If hibernate is not listed here check if there are issues that should be added and add them. > Document the ones relevant for hibernate by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19682) JBoss Central New and Noteworthy for 4.3.0.Alpha2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19682?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19682: ----------------------------------- Assignee: Max Rydahl Andersen (was: Fred Bricon) > JBoss Central New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------------- > > Key: JBIDE-19682 > URL: https://issues.jboss.org/browse/JBIDE-19682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Alexey Kazakov > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19049: --------------------------------------------- Fuse should not override this - they should not prevent usage of a newer (or older) Java runtime for running their servers if that is what the users need to do. If the UI is clear about this then this works just as everything else in eclipse as opposed to now it behaves differently by reducing the list for "alternate jre". It is even better since it gives you a warning. > Enable JBoss servers to run with java 9 > --------------------------------------- > > Key: JBIDE-19049 > URL: https://issues.jboss.org/browse/JBIDE-19049 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > Fix For: 4.3.0.Beta1 > > > I briefly tried to use java 9 for our tooling and to run servers. > I downloaded it from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > I use OS X 10.10 Yosemite. > There are a couple of problems: > 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that. > 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all. > {code} > nattura:bin rasp$ ./standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final > JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18772: --------------------------------------------- I reread the links the last time, I also reread them again and I still have the same question. About copy-or-rename stuff, we do we even have such step ? why don't we actually produce what we want/need ? The links just shows to me how we currently are doing it which seems to be there just because thats what its been like in the past, not because its the simplest and most maintainable way. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Valentin Baciu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ] Valentin Baciu updated JBIDE-19720: ----------------------------------- Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17" > NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath > ---------------------------------------------------------------------------- > > Key: JBIDE-19720 > URL: https://issues.jboss.org/browse/JBIDE-19720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.3.Final > Environment: Mac OS X 10.10.3, java full version "1.8.0_25-b17" > Reporter: Valentin Baciu > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.0.Beta1 > > > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) > at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) > at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) > at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) > at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) > at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Another code path: > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17103: ------------------------------------- I've just investigated this for a bit. The solution I have in my mind requires changes to an API interface: IRuntimeDetectorDelegate The problem with this method is twofold: 1) It enforces a workflow where we have each detector initialize a group of definitions, so we have no feedback to know how many were created 2) The existing method initializeRuntimes(List<RuntimeDefinition> runtimeDefinitions); is a void return with no exceptions at all. An API change would be required to commit this. I'll make a PR just in case, but no promises on it being accepted. > No warning/error is shown when detected runtime fails to be added > ----------------------------------------------------------------- > > Key: JBIDE-17103 > URL: https://issues.jboss.org/browse/JBIDE-17103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19720: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath > ---------------------------------------------------------------------------- > > Key: JBIDE-19720 > URL: https://issues.jboss.org/browse/JBIDE-19720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.3.Final > Reporter: Valentin Baciu > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.0.Beta1 > > > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) > at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) > at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) > at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) > at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) > at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Another code path: > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19720: ----------------------------------- Sprint: Sprint #3 May 2015 > NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath > ---------------------------------------------------------------------------- > > Key: JBIDE-19720 > URL: https://issues.jboss.org/browse/JBIDE-19720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.3.Final > Reporter: Valentin Baciu > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.0.Beta1 > > > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) > at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) > at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) > at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) > at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) > at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Another code path: > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19720?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19720: -------------------------------------- Assignee: Viacheslav Kabanovich > NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath > ---------------------------------------------------------------------------- > > Key: JBIDE-19720 > URL: https://issues.jboss.org/browse/JBIDE-19720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.3.Final > Reporter: Valentin Baciu > Assignee: Viacheslav Kabanovich > Priority: Minor > > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) > at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) > at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) > at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) > at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) > at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) > at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) > at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) > at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) > at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Another code path: > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) > at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) > at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) > at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) > at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19720) NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath

by Valentin Baciu (JIRA)

Valentin Baciu created JBIDE-19720: -------------------------------------- Summary: NPE in org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath Key: JBIDE-19720 URL: https://issues.jboss.org/browse/JBIDE-19720 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.2.3.Final Reporter: Valentin Baciu Priority: Minor java.lang.NullPointerException at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) at org.jboss.tools.common.model.util.EclipseResourceUtil.updateLibs(EclipseResourceUtil.java:535) at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:417) at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:40) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:71) at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:38) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:193) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:143) at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330) at org.jboss.tools.jst.web.kb.internal.KbProject.addKbProject(KbProject.java:216) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.validateProjectDependencies(ClassPathMonitor.java:154) at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:347) at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315) at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:100) at org.jboss.tools.jst.web.kb.KbProjectFactory$1KbBuilderEx.build(KbProjectFactory.java:107) at org.jboss.tools.jst.web.kb.KbProjectFactory$1.run(KbProjectFactory.java:122) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Another code path: java.lang.NullPointerException at org.jboss.tools.common.model.util.EclipseResourceUtil.getJREClassPath(EclipseResourceUtil.java:711) at org.jboss.tools.common.model.filesystems.impl.Libs.getNewPaths(Libs.java:141) at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:108) at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:73) at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:116) at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.<init>(JSF2ProjectBuilder.java:71) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:261) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:247) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:254) at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project$1.run(JSF2Project.java:172) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17314) Much UI from JVM Monitor documentation is missing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17314?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17314. --------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.x) Resolution: Out of Date This issue is out of date and the comments have ranged all over the place. The UI has changed substantially since then (introduction of JMX groups). > Much UI from JVM Monitor documentation is missing > ------------------------------------------------- > > Key: JBIDE-17314 > URL: https://issues.jboss.org/browse/JBIDE-17314 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Paul Leacu > Fix For: 4.2.1.Final > > Attachments: create-conn.png, ss-pref-tools.png, ss1.png > > > Much of the UI from http://www.jvmmonitor.org/doc/index.html#Monitoring_JVM_on_remote_host is missing and disabled. We must discover where it's gone, why it's disabled, and whether it can be re-activated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17545) Can't Full Publish project to WildFly (8.0 or 8.1)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17545?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17545. --------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.x) Resolution: Duplicate Issue Rejecting as a duplicate issue. No new feedback or replicatations in 6 months. > Can't Full Publish project to WildFly (8.0 or 8.1) > -------------------------------------------------- > > Key: JBIDE-17545 > URL: https://issues.jboss.org/browse/JBIDE-17545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Lincoln Baxter III > Assignee: Rob Stryker > Fix For: 4.2.1.Final > > > The following error is logged and publishing fails when attempting to Full Publish this project: > https://github.com/forgeide/forgeide > {code} > Publishing failed > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1118502157688228046.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/forge-javassist-2.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1738236936180964755.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jboss-modules-1.3.0.Final-forge.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp2320075067441042997.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jgrapht-0.8.3.jar. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19719: ------------------------------------ Assignee: Gorkem Ercan > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19719: ------------------------------------ Summary: "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 Key: JBIDE-19719 URL: https://issues.jboss.org/browse/JBIDE-19719 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Attachments: jbosstools-diagnostics-20150427143128.zip This issue is related to JBIDE-19716 Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Attachment: jbosstools-diagnostics-20150427143128.zip > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19688) Eclipse m2e, workspace resolution and Wildfly deployment issues

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19688?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-19688. --------------------------------- Resolution: Rejected So the problem is your manager-test-bean project has the Web Facet. As a jar dependency, it should have the Utility Facet. To fix your problem, delete the projects from your workspace, remove .project, .classpath and .settings/ then reimport them as Maven projects. The proper Facets will be added. Then you'll see manager-test-bean deployed as a jar archive, whenever you deploy the web app to a WTP server. > Eclipse m2e, workspace resolution and Wildfly deployment issues > --------------------------------------------------------------- > > Key: JBIDE-19688 > URL: https://issues.jboss.org/browse/JBIDE-19688 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server > Reporter: Sylvain Paillé > Assignee: Fred Bricon > Attachments: manager-test-ko.zip > > > Hello ! > I just found on Wildfly a Jboss (resolved ?) related bug. > See : https://issues.jboss.org/browse/AS7-4704 > When using Eclipse and m2e plugin, deploy with "workspace resolution" make WEB-INF/lib/ jar to be exploded into directories ... > Wildfly simply ignore them when running app. > Disabling Workspace resolution is a workaround. > Have you met a similar bug ? > Thx -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19716: -------------------------------------- Assignee: Gorkem Ercan (was: Mickael Istria) > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19190: -------------------------------------- True, I referred my old repo before. PR for the removal from jbdevstudio-qa repo created https://github.com/jbdevstudio/jbdevstudio-qa/pull/55. Once Nick confirms his jobs are set to a new location and working it can be applied. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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 April 2015