September 2013 - jbosstools-issues

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

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2741: ------------------------------- CDW pm_ack: + (was: ?) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2736) Split Web and Mobile Development into 2 categories in JBT & JBDS Central

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2736: ------------------------------- Component/s: requirements > Split Web and Mobile Development into 2 categories in JBT & JBDS Central > ------------------------------------------------------------------------ > > Key: JBDS-2736 > URL: https://issues.jboss.org/browse/JBDS-2736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > http://screencast.com/t/7vsajdz9o > Now that Cordova tools have been proposed, we need to split Web & Mobile into there own categories on the Software/Update tab. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2736) Split Web and Mobile Development into 2 categories in JBT & JBDS Central

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2736: ----------------------------- CDW pm_ack: ? (was: +) > Split Web and Mobile Development into 2 categories in JBT & JBDS Central > ------------------------------------------------------------------------ > > Key: JBDS-2736 > URL: https://issues.jboss.org/browse/JBDS-2736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > http://screencast.com/t/7vsajdz9o > Now that Cordova tools have been proposed, we need to split Web & Mobile into there own categories on the Software/Update tab. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

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

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2741: ----------------------------- CDW pm_ack: ? (was: +) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

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

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2741: ------------------------------- Component/s: requirements > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2753) Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer"

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2753: ------------------------------- Component/s: requirements > Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer" > ------------------------------------------------------------------- > > Key: JBDS-2753 > URL: https://issues.jboss.org/browse/JBDS-2753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Attachments: 2013-09-04_1215.png > > > See screenshot. > Do we need to keep the two Google Web Toolkit options separate? They were separated because they came in at different intervals, now it is unclear to me if they need to remain separate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2745: ------------------------------- Component/s: requirements > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15012) Runtime download dialog cannot be stopped

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15012?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15012. --------------------------------- Verified in JBDS 7.1.0.Alpha1 B378 > Runtime download dialog cannot be stopped > ----------------------------------------- > > Key: JBIDE-15012 > URL: https://issues.jboss.org/browse/JBIDE-15012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.1.0.Beta2 > Environment: OS X Mountain Lion > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha1 > > > Go to Preferences -> JBoss Tools -> Runtime detection > and try to download a runtime using the Download button. > While the runtime is downloading, press Cancel/Stop to abort the download. Nothing will happen (at least in my case). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15436) Bump Webservices to version 1.5.1

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15436?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15436. ----------------------------------- Verified with JBDS 7.1.0 Alpha1-v20130909-0132-B378 > Bump Webservices to version 1.5.1 > --------------------------------- > > Key: JBIDE-15436 > URL: https://issues.jboss.org/browse/JBIDE-15436 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.1.1.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Alpha1 > > > Bump WebServices component version from 1.5.0 to 1.5.1 on jbosstools-4.1.x branch only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-169) Missing fuse runtime feature

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-169?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-169: ------------------------------------ Description: JBTIS 4.1.2 only these two fuse feature * org.fusesource.ide.camel.editor.feature * org.fusesource.ide.server.extensions.feature but the following one is missing * org.fusesource.ide.runtimes.feature All fuse features are available at http://download.jboss.org/jbosstools/updates/integration/kepler/soa-tooli... was: JBTIS 4.1.2 only these two fuse feature * org.fusesource.ide.camel.editor.feature * org.fusesource.ide.server.extensions.feature but the following one is missing * org.fusesource.ide.runtimes.feature All fuse feature are available at http://download.jboss.org/jbosstools/updates/integration/kepler/soa-tooli... > Missing fuse runtime feature > ---------------------------- > > Key: JBTIS-169 > URL: https://issues.jboss.org/browse/JBTIS-169 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Affects Versions: 4.1.2 > Reporter: Andrej Podhradsky > Priority: Blocker > > JBTIS 4.1.2 only these two fuse feature > * org.fusesource.ide.camel.editor.feature > * org.fusesource.ide.server.extensions.feature > but the following one is missing > * org.fusesource.ide.runtimes.feature > All fuse features are available at > http://download.jboss.org/jbosstools/updates/integration/kepler/soa-tooli... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 September 2013