August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18116) Update Thym release on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18116?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18116: ----------------------------------- Description: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* JBDS Central only *Type of dependency:* build *List of bundles added/removed:* was: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* Yes *Type of dependency:* build *List of bundles added/removed:* > Update Thym release on TP > ------------------------- > > Key: JBIDE-18116 > URL: https://issues.jboss.org/browse/JBIDE-18116 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* JBDS Central only > *Type of dependency:* build > *List of bundles added/removed:* -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18116) Update Thym release on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18116?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18116: ----------------------------------- Component/s: discovery > Update Thym release on TP > ------------------------- > > Key: JBIDE-18116 > URL: https://issues.jboss.org/browse/JBIDE-18116 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: discovery, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* JBDS Central only > *Type of dependency:* build > *List of bundles added/removed:* -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3122) Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3122?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3122: -------------------------------------- Component/s: ui/branding > Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin > ------------------------------------------------------------------------------------------ > > Key: JBDS-3122 > URL: https://issues.jboss.org/browse/JBDS-3122 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ui/branding > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Attachments: fc20-mate-result.png > > > Based on stats and general crazy interests dark themes like provided by http://marketplace.eclipse.org/content/eclipse-moonrise-ui-theme and basic Eclipse Luna dark theme we should check if we have some obvious glitches when eclipse is switched to dark theme. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18116) Update Thym release on TP

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18116?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18116: -------------------------------------- It should be good for CR1.. It should addresses all known thym issues targeted for CR1, with some luck we will not need a refresh. > Update Thym release on TP > ------------------------- > > Key: JBIDE-18116 > URL: https://issues.jboss.org/browse/JBIDE-18116 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* Yes > *Type of dependency:* build > *List of bundles added/removed:* -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18116) Update Thym release on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18116?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-18116: -------------------------------------- Assignee: Mickael Istria > Update Thym release on TP > ------------------------- > > Key: JBIDE-18116 > URL: https://issues.jboss.org/browse/JBIDE-18116 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* Yes > *Type of dependency:* build > *List of bundles added/removed:* -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18112) vpe version should be 3.6, not 3.5.100

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18112?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18112: --------------------------------------------- this should be done before/at the time of CR1 codefreeze IMO. much less confusion and we ensure anyone dependent on the vpe versions are not surprised during respins. > vpe version should be 3.6, not 3.5.100 > -------------------------------------- > > Key: JBIDE-18112 > URL: https://issues.jboss.org/browse/JBIDE-18112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > As VPE for Luna includes new features/plugins [1] it should be upversioned to 3.6, not left as a maintenance version 3.5.100. > [1] http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... > New IUs include: > * org.jboss.tools.vpe.browsersim.debugger > * org.jboss.tools.vpe.browsersim.javafx.mock > * org.jboss.tools.vpe.preview > * org.jboss.tools.vpe.preview.core > * org.jboss.tools.vpe.preview.editor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-2720: -------------------------------------------- Since we don't control the actual eclipse binaries used i think there is very little chance of us patching via dll injection or anything else for that matter. With respect to getting intel or MS to fix their dll's I wouldn't even know where to start asking for it - its not like they got a public jira to request such things ;) btw. if your workflow is just around HTML (not jsf/xhtml) then you should be fine using our html preview that does not rely on xulrunner. Have you tried that ? > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18116) Update Thym release on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18116?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18116: ----------------------------------- Description: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* Yes *Type of dependency:* build *List of bundles added/removed:* was: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots *JBoss mirror:* *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* Yes *Type of dependency:* build *List of bundles added/removed:* > Update Thym release on TP > ------------------------- > > Key: JBIDE-18116 > URL: https://issues.jboss.org/browse/JBIDE-18116 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* Yes > *Type of dependency:* build > *List of bundles added/removed:* -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18094: ---------------------------------------- Labels: affects_documentation new_and_noteworthy (was: affects_documentation) > Do not force restart modules when server is run in debug mode > ------------------------------------------------------------- > > Key: JBIDE-18094 > URL: https://issues.jboss.org/browse/JBIDE-18094 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: affects_documentation, new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: initialsuggestionfor_hotcodefailurereplace.bmml, initialsuggestionfor_hotcodefailurereplace.png, JBIDE-18094.png, JBIDE-18094_dialog.png, serversetting.bmml, serversetting.png, update_dialog_based_on_existing_hcr.bmml, update_dialog_based_on_existing_hcr.png > > > The request is that modules should not force-restart when a server is in debug mode. More often than not, a change to a .class file, when the server is in debug mode, does not require any special action or force-restart of the module. The changes to the .class file will be picked up automatically. > Ideally, we would also detect a hotcode replace failure, and then force-restart the module if possible. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18094: ---------------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Do not force restart modules when server is run in debug mode > ------------------------------------------------------------- > > Key: JBIDE-18094 > URL: https://issues.jboss.org/browse/JBIDE-18094 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: affects_documentation, new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: initialsuggestionfor_hotcodefailurereplace.bmml, initialsuggestionfor_hotcodefailurereplace.png, JBIDE-18094.png, JBIDE-18094_dialog.png, serversetting.bmml, serversetting.png, update_dialog_based_on_existing_hcr.bmml, update_dialog_based_on_existing_hcr.png > > > The request is that modules should not force-restart when a server is in debug mode. More often than not, a change to a .class file, when the server is in debug mode, does not require any special action or force-restart of the module. The changes to the .class file will be picked up automatically. > Ideally, we would also detect a hotcode replace failure, and then force-restart the module if possible. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2014