January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2874: ----------------------------- CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? > Support updating JBDS via BYOE (update site) w/o having to update product too > ----------------------------------------------------------------------------- > > Key: JBDS-2874 > URL: https://issues.jboss.org/browse/JBDS-2874 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png > > > I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. > Do we want this? I'll attach a PR showing how it's possible to make this happen. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2874 at 1/16/14 11:38 AM: ------------------------------------------------------------ The old way - if you asked to update JBDS Core Features (BYOE) you would be forced to update the Branded Product feature too: !update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png! Now, with a change like this in site/*.p2.inf (for JBDS 8.0.0.Alpha1)... {code:title=site/com.jboss.jbds.p2.inf} # JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself requires.1.namespace = org.eclipse.equinox.p2.iu requires.1.name = com.jboss.jbds.product.feature.feature.group requires.1.range = [8.0.0, 9.0.0) {code} we get this: *Help > About > Installation Details > Installation History BEFORE UPDATE* !update-BYOE-without-updating-product_BEFORE.png! *Help > About > Installation Details > Installation History AFTER UPDATE* !update-BYOE-without-updating-product_result.png! For JBDS 8.0.0.Alpha2, the code is slightly different due to refactorings done in JBDS-2669: {code:title=site/com.jboss.devstudio.core.p2.inf} # JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself requires.1.namespace = org.eclipse.equinox.p2.iu requires.1.name = com.jboss.devstudio.core.feature.feature.group requires.1.range = [8.0.0, 9.0.0) {code} was (Author: nickboldt): The old way - if you asked to update JBDS Core Features (BYOE) you would be forced to update the Branded Product feature too: !update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png! Now, with a change like this in site/*.p2.inf (for JBDS 8.0.0.Alpha1)... {code:title=site/com.jboss.jbds.p2.inf} # JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself requires.1.namespace = org.eclipse.equinox.p2.iu requires.1.name = com.jboss.jbds.product.feature.feature.group requires.1.range = [8.0.0, 9.0.0) {code} we get this: !update-BYOE-without-updating-product_BEFORE.png! !update-BYOE-without-updating-product_result.png! For JBDS 8.0.0.Alpha2, the code is slightly different due to refactorings done in JBDS-2669: {code:title=site/com.jboss.devstudio.core.p2.inf} # JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself requires.1.namespace = org.eclipse.equinox.p2.iu requires.1.name = com.jboss.devstudio.core.feature.feature.group requires.1.range = [8.0.0, 9.0.0) {code} > Support updating JBDS via BYOE (update site) w/o having to update product too > ----------------------------------------------------------------------------- > > Key: JBDS-2874 > URL: https://issues.jboss.org/browse/JBDS-2874 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png > > > I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. > Do we want this? I'll attach a PR showing how it's possible to make this happen. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2874: ----------------------------- Attachment: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png update-BYOE-without-updating-product_result.png update-BYOE-without-updating-product_BEFORE.png The old way - if you asked to update JBDS Core Features (BYOE) you would be forced to update the Branded Product feature too: !update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png! Now, with a change like this in site/*.p2.inf (for JBDS 8.0.0.Alpha1)... {code:title=site/com.jboss.jbds.p2.inf} # JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself requires.1.namespace = org.eclipse.equinox.p2.iu requires.1.name = com.jboss.jbds.product.feature.feature.group requires.1.range = [8.0.0, 9.0.0) {code} we get this: !update-BYOE-without-updating-product_BEFORE.png! !update-BYOE-without-updating-product_result.png! For JBDS 8.0.0.Alpha2, the code is slightly different due to refactorings done in JBDS-2669: {code:title=site/com.jboss.devstudio.core.p2.inf} # JBDS-2874 this allows us to update a JBDS product via BYOE feature w/o updating the product (package definition) itself requires.1.namespace = org.eclipse.equinox.p2.iu requires.1.name = com.jboss.devstudio.core.feature.feature.group requires.1.range = [8.0.0, 9.0.0) {code} > Support updating JBDS via BYOE (update site) w/o having to update product too > ----------------------------------------------------------------------------- > > Key: JBDS-2874 > URL: https://issues.jboss.org/browse/JBDS-2874 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png > > > I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. > Do we want this? I'll attach a PR showing how it's possible to make this happen. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2874: -------------------------------- Summary: Support updating JBDS via BYOE (update site) w/o having to update product too Key: JBDS-2874 URL: https://issues.jboss.org/browse/JBDS-2874 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nick Boldt I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both. Do we want this? I'll attach a PR showing how it's possible to make this happen. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16367) Drop sourceforge.net archiving?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16367?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16367: --------------------------------------------- note to that is that http://www.jboss.org/tools/download/stable/4_1 are "clicks on that link"-stats, not stats for actual downloads. > Drop sourceforge.net archiving? > ------------------------------- > > Key: JBIDE-16367 > URL: https://issues.jboss.org/browse/JBIDE-16367 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 4.2.x > > > We currently do archive stuff on sf.net. This adds an extra piece in build process and infrastructure, which does not seem to provide additional value upon keeping binaries on download.jboss.org. > I'd be in favour of abandoning sf.net to find something which is more comfortable for us to use (download.jboss.org is IMO the best candidate). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on JBDS-2734: --------------------------------------- AFAIK this won't be affected. The user may have additional JDK/JREs installed. JDK 7 should only be used to run Eclipse. > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > > Is Forge 2 ready to be included in 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2872) https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2872?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2872. ---------------------------- Resolution: Done Pages are live. Reopen if you have concerns or to attach a PR for changes. > https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2872 > URL: https://issues.jboss.org/browse/JBDS-2872 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.1.GA > > Attachments: new-jbds-7x-dl-page.png, new-jbds-7x-dl-page_v2.png > > > https://devstudio.jboss.com/download/7.x.html should direct users to https://www.jboss.org/products/devstudio.html instead of the old JBDS PE / JBDS Eval process. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Karel Piwko commented on JBDS-2734: ----------------------------------- Forge requires JDK 7. Does it mean that JBDS 8 will require JDK 7 to run? If so, does it anyhow affect ability to: * make JDK 6 a target platform of a project * start something using JDK 6 - server backend, unified push server, etc > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > > Is Forge 2 ready to be included in 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16317) Tag projects for jbosstools-4.2.0.Alpha1

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16317?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-16317. ------------------------------------ Assignee: Nick Boldt Resolution: Done All necessary components are tagged now. > Tag projects for jbosstools-4.2.0.Alpha1 > ---------------------------------------- > > Key: JBIDE-16317 > URL: https://issues.jboss.org/browse/JBIDE-16317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Alpha1 > > > Project leads, please tag your projects! > {code} > co jbosstools-4.2.0.Alpha1x > git tag jbosstools-4.2.0.Alpha1 > git push origin jbosstools-4.2.0.Alpha1 > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16366) Tag jbosstools-4.2.0.Alpha1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16366?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16366: ------------------------------------- done for server > Tag jbosstools-4.2.0.Alpha1 > --------------------------- > > Key: JBIDE-16366 > URL: https://issues.jboss.org/browse/JBIDE-16366 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Alpha1 > > > Please tag the commit of your component that was built and aggregated into JBoss Tools 4.2.0.Alpha1. > See parent issue for details. -- 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, 3 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 January 2014