April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22249) Do the CQ dance for m2e/m2e-wtp

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22249?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22249: -------------------------------- Story Points: 5 > Do the CQ dance for m2e/m2e-wtp > ------------------------------- > > Key: JBIDE-22249 > URL: https://issues.jboss.org/browse/JBIDE-22249 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: upstream > Affects Versions: 4.4.x > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.x > > > Need to create all relevant CQs for the Neon release of m2e/m2e-wtp. > So awesome. Hopefully this year should be less of a headache as the process has been simplified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22249) Do the CQ dance for m2e/m2e-wtp

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22249: ----------------------------------- Summary: Do the CQ dance for m2e/m2e-wtp Key: JBIDE-22249 URL: https://issues.jboss.org/browse/JBIDE-22249 Project: Tools (JBoss Tools) Issue Type: Task Components: upstream Affects Versions: 4.4.x Reporter: Fred Bricon Need to create all relevant CQs for the Neon release of m2e/m2e-wtp. So awesome. Hopefully this year should be less of a headache as the process has been simplified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3859: ----------------------------- Story Points: 5 Sprint: devex #113 April 2016 > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we: > * need to check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3859: ----------------------------- Fix Version/s: 10.0.0.Alpha1 > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we: > * need to check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3859: -------------------------------- Summary: Use SHA256sums to intelligently download latest CI builds into DP installer Key: JBDS-3859 URL: https://issues.jboss.org/browse/JBDS-3859 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: platform-installer Affects Versions: 10.0.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Per discussion with Denis today, we: * need to check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3859: ----------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Per discussion with Denis today, we: > * need to check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19838) Re-consider relationship between Central and Software/update page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19838?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19838: -------------------------------- Component/s: central-update (was: central) > Re-consider relationship between Central and Software/update page > ----------------------------------------------------------------- > > Key: JBIDE-19838 > URL: https://issues.jboss.org/browse/JBIDE-19838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Affects Versions: 4.3.0.Beta1 > Environment: JBT 4.3.0.Nightly, central feature version 2.0.0.Beta1-v20150520-1916-B702 > Reporter: Radim Hopp > Fix For: LATER > > > Now in new Central, there is big Add Tools button which switches central to Software/Update page. > Now, I can imagine some people struggling with switching back to Central form Software/Update page. The tabs on bottom are easy to overlook (when it's ones first encountering with central). It would be good IMHO to have some "back" button on Software/Update page. > With old central it was OK, because switching to Software/Update page required user to notice those tabs on the bottom. No one can be completely unaware of those. > What do you think? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16647) Allow to fully update application from central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16647?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16647: -------------------------------- Component/s: central-update (was: central) > Allow to fully update application from central > ---------------------------------------------- > > Key: JBIDE-16647 > URL: https://issues.jboss.org/browse/JBIDE-16647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > Software/Update tab should contain a more explicit way to update the whole application (same as "Check for Updates" menu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16647) Allow to fully update application from central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16647?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16647: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Allow to fully update application from central > ---------------------------------------------- > > Key: JBIDE-16647 > URL: https://issues.jboss.org/browse/JBIDE-16647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > Software/Update tab should contain a more explicit way to update the whole application (same as "Check for Updates" menu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16701) Arquillian not working with default maven settings from selecting the jboss-javaee6-webapp-archetype 7.1.3.Final

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16701?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16701: -------------------------------- Story Points: 1 Sprint: devex #113 April 2016 > Arquillian not working with default maven settings from selecting the jboss-javaee6-webapp-archetype 7.1.3.Final > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16701 > URL: https://issues.jboss.org/browse/JBIDE-16701 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, maven > Affects Versions: 4.1.1.Final > Reporter: Dirk Gerrit Oort > Assignee: Fred Bricon > Fix For: 4.3.1.Final > > > (see https://community.jboss.org/message/860583#860583) > Create maven project with archetype selecting the jboss-javaee6-webapp-archetype 7.1.3.Final > use arq-jbossas-managed > use jboss 7.1.1 > run maven test > deployment is done but after deployment the test 'hangs' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016