July 2014 - jbosstools-issues - Jboss List Archives

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

by Patrick Decat (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Patrick Decat commented on JBIDE-17724: --------------------------------------- Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update. Anyway, importing the sample project with m2e results the same. > 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, 4.2.0.CR1 > > 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-17724) Changes cause full redeployment of exploded WAR

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17724: --------------------------------------------- The example does not build cleanly, i've cloned it and pushed at https://github.com/maxandersen/JBIDE-17724 for now so can be used for testing. > 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, 4.2.0.CR1 > > 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-17724) Changes cause full redeployment of exploded WAR

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17724: --------------------------------------------- Please do not do step #2 - that is not supported by eclipse for *years* now. the output of this will *not* work. Please use m2e-wtp to import it. That said - I would like to see if we can detect it and warn. > 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, 4.2.0.CR1 > > 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] (JBTIS-292) Karaf cannot be started in debug

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-292?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-292: ------------------------------------------- moved to JBTIS which is where Fuse is bundled. > Karaf cannot be started in debug > -------------------------------- > > Key: JBTIS-292 > URL: https://issues.jboss.org/browse/JBTIS-292 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Affects Versions: 7.0.1.GA-JBDSIS > Environment: JBoss Fuse Server Extension Feature 7.2.1.v20140613-0455-H79-Final org.fusesource.ide.server.extensions.feature.feature.group JBoss by Red Hat > Reporter: Jason Shepherd > Priority: Minor > > Cannot start a Fuse server in DEBUG mode, see: > FUSETOOL-1132 > Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17965) Update stacks url (jdf is now jboss developer)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17965?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17965. --------------------------------- Resolution: Done pushed to cr1 > Update stacks url (jdf is now jboss developer) > ---------------------------------------------- > > Key: JBIDE-17965 > URL: https://issues.jboss.org/browse/JBIDE-17965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, common/jst/core, seam2, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > I'm not sure exactly which component is right here. > stacks.yaml is now on this location: > https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.yaml > It's no longer jdf, but jboss-developer. The old url still works through redirects, but it's probably a good idea to use the new one. > Reject this JIRA if this has already been done. -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17686: ----------------------------------- Component/s: upstream > 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 > 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17686: ---------------------------------------- Is this issue already reported to TCF and/or RSE ? > 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 > 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-17965) Update stacks url (jdf is now jboss developer)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17965?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17965: ------------------------------------- New PR: https://github.com/jbosstools/jbosstools-base/pull/308 Updates the client version to 1.0.3, fixes the pre-stacks default url by fetching from jar. Tested. Works. > Update stacks url (jdf is now jboss developer) > ---------------------------------------------- > > Key: JBIDE-17965 > URL: https://issues.jboss.org/browse/JBIDE-17965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, common/jst/core, seam2, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > I'm not sure exactly which component is right here. > stacks.yaml is now on this location: > https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.yaml > It's no longer jdf, but jboss-developer. The old url still works through redirects, but it's probably a good idea to use the new one. > Reject this JIRA if this has already been done. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3112) Karaf cannot be started in debug

by Jason Shepherd (JIRA)

[ https://issues.jboss.org/browse/JBDS-3112?page=com.atlassian.jira.plugin.... ] Jason Shepherd updated JBDS-3112: --------------------------------- Workaround Description: See https://access.redhat.com/solutions/249873 Workaround: Workaround Exists > Karaf cannot be started in debug > -------------------------------- > > Key: JBDS-3112 > URL: https://issues.jboss.org/browse/JBDS-3112 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration > Affects Versions: 7.1.1.GA > Environment: JBoss Fuse Server Extension Feature 7.2.1.v20140613-0455-H79-Final org.fusesource.ide.server.extensions.feature.feature.group JBoss by Red Hat > Reporter: Jason Shepherd > Priority: Minor > > Cannot start a Fuse server in DEBUG mode, see: > FUSETOOL-1132 > Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3112) Karaf cannot be started in debug

by Jason Shepherd (JIRA)

[ https://issues.jboss.org/browse/JBDS-3112?page=com.atlassian.jira.plugin.... ] Jason Shepherd edited comment on JBDS-3112 at 7/30/14 3:39 AM: --------------------------------------------------------------- Fixed by FUSETOOLS-1132 was (Author: jshepher): Fixed by > Karaf cannot be started in debug > -------------------------------- > > Key: JBDS-3112 > URL: https://issues.jboss.org/browse/JBDS-3112 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration > Affects Versions: 7.1.1.GA > Environment: JBoss Fuse Server Extension Feature 7.2.1.v20140613-0455-H79-Final org.fusesource.ide.server.extensions.feature.feature.group JBoss by Red Hat > Reporter: Jason Shepherd > Priority: Minor > > Cannot start a Fuse server in DEBUG mode, see: > FUSETOOL-1132 > Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. -- 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