July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17934) cordova-3.5.0.jar missing when exporting andriod project

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17934?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-17934: ------------------------------------------- Fix Version/s: 4.2.0.CR1 > cordova-3.5.0.jar missing when exporting andriod project > -------------------------------------------------------- > > Key: JBIDE-17934 > URL: https://issues.jboss.org/browse/JBIDE-17934 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Affects Versions: 4.2.0.Beta2 > Environment: Mac OSx 10.9.4, Eclipse Luna (4.4.0), Jboss Tools for Luna (4.2.0.Beta2), with Jboss Hybrid Mobile Tools + CordovaSim. > Reporter: Asif Kilwani > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > > When trying to test "run on Andriod device" or export native platform project > Error generating the native android project > /Users/Administrator/.cordova/lib/android/cordova/3.5.0/framework/cordova-3.5.0.jar (No such file or directory) > I deleted framework and downloaded again from properties, but same. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17724. --------------------------------- Fix Version/s: (was: 4.2.0.CR1) Resolution: Done I've opened https://issues.jboss.org/browse/JBIDE-18002 to track this case. Closing this issue here as resolved in b3, since it was. > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta3 > > Attachments: JBIDE-17724-JBossEAP5-testcase.tar.bz2, workspace.zip > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18002) Changes to files in nested utility project need not always restart module

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18002?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18002: -------------------------------- Fix Version/s: 4.2.0.CR1 > Changes to files in nested utility project need not always restart module > ------------------------------------------------------------------------- > > Key: JBIDE-18002 > URL: https://issues.jboss.org/browse/JBIDE-18002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Labels: affects_documentation > Fix For: 4.2.0.CR1 > > > Changes to a .class file inside a nested utility project currently marks the module as requiring a restart, because the application server won't pick up those changes without a restart. > When running in debug mode, though, the debugger will use the new classes as changed in the workspace, so a restart of a module is slow and costly. > The fix (for now) would be to only restart the web module if the publish is a full publish, or, if the nested archive's deployment name matches the strings in the server editor's restart-module regex clause. > Example project replicating the bug can be found at https://github.com/maxandersen/JBIDE-17724 > Unzip the attached project structure (stripped down from an existing project) > Run 'mvn clean install eclipse:clean eclipse:eclipse' at the root > Import existing projects into eclipse luna with JBoss Tools > Deploy to a "JBoss Enterprise Application Platform 5.x" runtime > Make a change to MyController.java inside the project-war webapp => the change is hot deployed > Make a change to MySecondController.java inside the project-module dependency => the full WAR is undeployed then redeployed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18002) Changes to files in nested utility project need not always restart module

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18002?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18002: -------------------------------- Labels: affects_documentation (was: ) > Changes to files in nested utility project need not always restart module > ------------------------------------------------------------------------- > > Key: JBIDE-18002 > URL: https://issues.jboss.org/browse/JBIDE-18002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Labels: affects_documentation > Fix For: 4.2.0.CR1 > > > Changes to a .class file inside a nested utility project currently marks the module as requiring a restart, because the application server won't pick up those changes without a restart. > When running in debug mode, though, the debugger will use the new classes as changed in the workspace, so a restart of a module is slow and costly. > The fix (for now) would be to only restart the web module if the publish is a full publish, or, if the nested archive's deployment name matches the strings in the server editor's restart-module regex clause. > Example project replicating the bug can be found at https://github.com/maxandersen/JBIDE-17724 > Unzip the attached project structure (stripped down from an existing project) > Run 'mvn clean install eclipse:clean eclipse:eclipse' at the root > Import existing projects into eclipse luna with JBoss Tools > Deploy to a "JBoss Enterprise Application Platform 5.x" runtime > Make a change to MyController.java inside the project-war webapp => the change is hot deployed > Make a change to MySecondController.java inside the project-module dependency => the full WAR is undeployed then redeployed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18002) Changes to files in nested utility project need not always restart module

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-18002: ----------------------------------- Summary: Changes to files in nested utility project need not always restart module Key: JBIDE-18002 URL: https://issues.jboss.org/browse/JBIDE-18002 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: server Affects Versions: 4.2.0.Beta3 Reporter: Rob Stryker Changes to a .class file inside a nested utility project currently marks the module as requiring a restart, because the application server won't pick up those changes without a restart. When running in debug mode, though, the debugger will use the new classes as changed in the workspace, so a restart of a module is slow and costly. The fix (for now) would be to only restart the web module if the publish is a full publish, or, if the nested archive's deployment name matches the strings in the server editor's restart-module regex clause. Example project replicating the bug can be found at https://github.com/maxandersen/JBIDE-17724 Unzip the attached project structure (stripped down from an existing project) Run 'mvn clean install eclipse:clean eclipse:eclipse' at the root Import existing projects into eclipse luna with JBoss Tools Deploy to a "JBoss Enterprise Application Platform 5.x" runtime Make a change to MyController.java inside the project-war webapp => the change is hot deployed Make a change to MySecondController.java inside the project-module dependency => the full WAR is undeployed then redeployed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-17686 at 7/30/14 10:10 AM: -------------------------------------------------------------- Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=440782 upstream to track this issue. was (Author: nickboldt): https://bugs.eclipse.org/bugs/show_bug.cgi?id=440782 > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.3.x > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17686: ------------------------------- Fix Version/s: 4.3.x (was: 4.2.0.CR1) > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.3.x > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-17686: ---------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.x > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17686: ------------------------------------ https://bugs.eclipse.org/bugs/show_bug.cgi?id=440782 > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17968) Application wizard: take less less screen height

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17968?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17968: ------------------------------------- Attachment: openshift-wizard-title-area.png > Application wizard: take less less screen height > ------------------------------------------------ > > Key: JBIDE-17968 > URL: https://issues.jboss.org/browse/JBIDE-17968 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta2 > Environment: Fedora, 1440x900 resolution screen > Reporter: Catherine Robson > Assignee: Andre Dietisheim > Labels: application_wizard, uxtest > Fix For: 4.2.0.CR1 > > Attachments: app-config-wizard-page.png, openshift-wizard-title-area.png, shortened-application-wizard.png, wizard-too-tall.png > > > For users with small screen sizes, the OpenShift create application wizard is very tall and might overflow their screen real-estate. Many of the dialogs in this wizard have lots of wasted space, so we should see if we can reduce the size of these dialogs as much as possible. > The height of the dialog is ~870px high. The most common resolution people run these days is 1366x768 - meaning we're already too high for people's viewable screen. > !wizard-too-tall.png! > ---------------- > Screen by screen analysis > ---------------- > Sign in dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/baf765b4-cee1-470c-88a0-1afd237868... > Existing or new application dialog - ~145px wasted height: https://www.evernote.com/shard/s230/sh/d76f10b6-fb40-455d-bef6-d1b1ea44b0... > Name, domain, and embedded cartridges dialog - ~200px wasted height: https://www.evernote.com/shard/s230/sh/04381c6a-e9d7-4c6a-bd47-15b5b83a8e... > Configure project dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/4932fd92-12b3-456f-8f9c-a25548f4f6... > Clone settings, processing dialog - ~480px wasted height: https://www.evernote.com/shard/s230/sh/0d921581-6d12-4ba0-8c99-dc4c904e90... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014