July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

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.2.0.CR1 > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17686: ------------------------------------ Assign to [~maxandersen] to reply to my question: {quote}Do you mean this should be installed as part of the JBoss Tools "Abridged" category / marketplace install, and preinstalled with the JBDS installer / Core Features BYOE install? Or do you mean this should be added to Central?{quote} > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17686: ------------------------------- Assignee: Max Rydahl Andersen > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17686: ------------------------------- Affects Version/s: 4.2.0.Beta2 > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17803) Remove GateIn quickstart extension point

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17803?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-17803. ------------------------------- Resolution: Rejected Rejecting as per Burr's comment > Remove GateIn quickstart extension point > ---------------------------------------- > > Key: JBIDE-17803 > URL: https://issues.jboss.org/browse/JBIDE-17803 > Project: Tools (JBoss Tools) > Issue Type: Task > Reporter: Peter Palaga > > This is motivated by the fact that GateIn quickstarts were abandoned. Only quickstarts for JBoss Portal are maintained as of JBoss Portal 6.2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17683) When running using Cmd-4 in Eclipse, log the actual forge commands used to an Eclipse console

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17683?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-17683: ------------------------------------ Fix Version/s: 4.2.0.CR1 > When running using Cmd-4 in Eclipse, log the actual forge commands used to an Eclipse console > --------------------------------------------------------------------------------------------- > > Key: JBIDE-17683 > URL: https://issues.jboss.org/browse/JBIDE-17683 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Pete Muir > Assignee: George Gastaldi > Priority: Minor > Fix For: 4.2.0.CR1 > > > It would be great to log all Forge commands that Cmd-4 executes to an eclipse console > Allow this log to be exported to a .fsh file -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15482: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17527) revise Early Access disclaimer copy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17527?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17527: ------------------------------- Labels: early-access respin-a (was: early-access) > revise Early Access disclaimer copy > ----------------------------------- > > Key: JBIDE-17527 > URL: https://issues.jboss.org/browse/JBIDE-17527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Labels: early-access, respin-a > Fix For: 4.2.0.Beta3 > > > Copy needs a bit of a rewrite. > Old: > {quote} > *Early Access Features* > Early Access features contains new functionality and fixes that are under development. You are encouraged to use these and give feedback but be aware: They are NOT officially supported, and NOT guaranteed to work correctly in your installation nor is it guaranteed it will end up in the final version. Use them at your own risk! > [ ] I understand those conditions, and I still want to access Early Access features. > {quote} > Proposed: > {quote} > *Early Access features* > Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! > [ ] I understand these conditions, and still want to enable Early Access features. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17527) revise Early Access disclaimer copy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17527?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17527: ------------------------------------ Too late for Beta3 so attach respin-a label and hope we get quorum here before next week. :) > revise Early Access disclaimer copy > ----------------------------------- > > Key: JBIDE-17527 > URL: https://issues.jboss.org/browse/JBIDE-17527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Labels: early-access, respin-a > Fix For: 4.2.0.Beta3 > > > Copy needs a bit of a rewrite. > Old: > {quote} > *Early Access Features* > Early Access features contains new functionality and fixes that are under development. You are encouraged to use these and give feedback but be aware: They are NOT officially supported, and NOT guaranteed to work correctly in your installation nor is it guaranteed it will end up in the final version. Use them at your own risk! > [ ] I understand those conditions, and I still want to access Early Access features. > {quote} > Proposed: > {quote} > *Early Access features* > Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! > [ ] I understand these conditions, and still want to enable Early Access features. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15609: ------------------------------------ Thanks. Slipping this to CR1. If you get it done sooner, feel free to bump it back :) > versionwatch should ignore when there's a folder & jar which are identical > -------------------------------------------------------------------------- > > Key: JBIDE-15609 > URL: https://issues.jboss.org/browse/JBIDE-15609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Fix For: 4.2.0.CR1 > > > A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. > Now, the vwatch tool complains when there's a folder and a jar present. > Two possible solutions to this come to mind: > a) ignore this - do not report as *{color:red}a problem{color}* > b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014