August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2722: ----------------------------- CDW devel_ack: + (was: ?) > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > > Kepler SR1 has bugfixes - we should include it in upcoming release. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2722: ----------------------------- CDW qa_ack: ? > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > > Kepler SR1 has bugfixes - we should include it in upcoming release. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2742) Create target platform from Kepler SR1 (RC) dependencies

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2742?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2742: ----------------------------- CDW pm_ack: ? > Create target platform from Kepler SR1 (RC) dependencies > -------------------------------------------------------- > > Key: JBDS-2742 > URL: https://issues.jboss.org/browse/JBDS-2742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > > Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0. > [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1 > There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items. > For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2742) Create target platform from Kepler SR1 (RC) dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2742?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2742: ----------------------------- CDW release: ? Status: New (was: New) Target Release: 7.1.0.GA > Create target platform from Kepler SR1 (RC) dependencies > -------------------------------------------------------- > > Key: JBDS-2742 > URL: https://issues.jboss.org/browse/JBDS-2742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Mickael Istria > > Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0. > [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1 > There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items. > For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-129) Create SY bot test from existing jBPM5

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-129?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-129: ------------------------------------ Fix Version/s: 4.1.2 > Create SY bot test from existing jBPM5 > -------------------------------------- > > Key: JBTIS-129 > URL: https://issues.jboss.org/browse/JBTIS-129 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.2 > > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-2722: -------------------------------- Assignee: Nick Boldt > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > > Kepler SR1 has bugfixes - we should include it in upcoming release. -- 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

10 years, 10 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: ? > 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: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha1 > > > 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

10 years, 10 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2741: ----------------------------- CDW release: ? Status: New (was: New) Target Release: 7.1.0.GA > 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: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha1 > > > 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

10 years, 10 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2741: ----------------------------- Summary: Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files (was: Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-regenerated composite*.xml files) > 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: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha1 > > > 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

10 years, 10 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2741: ----------------------------- Docs QE Status: (was: NEW) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-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: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha1 > > > 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

10 years, 10 months

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 August 2013