March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16957) no difference between beta1 and beta1a updatesites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16957?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16957: ------------------------------------ I've kicked a new buildflow, which will respin and force republish the component and aggregate projects: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=9 > no difference between beta1 and beta1a updatesites > -------------------------------------------------- > > Key: JBIDE-16957 > URL: https://issues.jboss.org/browse/JBIDE-16957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Beta1 > > > something is funky here. > eclipse doesn't give me any updates for this new beta1a site. > Thus I tried running p2diff and browse via p2browser. The binary content except the category are identical. > See difference at https://gist.github.com/maxandersen/352153881b657fbe2ecb > none of the plugins like open shift or server has changed. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16957) no difference between beta1 and beta1a updatesites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16957?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16957: ------------------------------------ Caused by JBIDE-16953, which I fixed today when [~mmalina] pointed out the problem. https://github.com/jbosstools/jbosstools-build-ci/commits/master/publish > no difference between beta1 and beta1a updatesites > -------------------------------------------------- > > Key: JBIDE-16957 > URL: https://issues.jboss.org/browse/JBIDE-16957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Beta1 > > > something is funky here. > eclipse doesn't give me any updates for this new beta1a site. > Thus I tried running p2diff and browse via p2browser. The binary content except the category are identical. > See difference at https://gist.github.com/maxandersen/352153881b657fbe2ecb > none of the plugins like open shift or server has changed. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-449) Update explicit 7.1 text and figs references in docs for 8.0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-449?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-449: ------------------------------------------ Test updates complete - supported configs updates will be addressed in TOOLSDOC-467. [~sdorfiel], please complete the figure updates. Take new screen caps, editing them as necessary to achieve the desired result, then add to PG as new files and update the topics with the new image numbers. > Update explicit 7.1 text and figs references in docs for 8.0 > ------------------------------------------------------------ > > Key: TOOLSDOC-449 > URL: https://issues.jboss.org/browse/TOOLSDOC-449 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide > Reporter: Michelle Murray > Assignee: Suz Dorfield > Fix For: 4.2.0.Beta1 > > Original Estimate: 1 day, 30 minutes > Time Spent: 40 minutes > Remaining Estimate: 7 hours, 50 minutes > > _Text_ > *Installation Guide* > 2.2 Supported Operating Systems and Architectures > 2.3 Computer Memory > 2.4 Compatible Java Developer Kits > 3.2 Install JBoss Developer Studio > 3.3 Install JBoss Developer Studio BYOE > 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier > 5.3 Upgrade from JBoss Developer Studio 7.0 > B.1 Build the Universal Installer from Source > *Getting Started Guide* > 2.1 About Getting Started > 3.1 Installation Assumptions > 3.2 Install JBoss Developer Studio (shared with Install) > 4.3 Tutorial Assumptions > *Migration Guide* > 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install) > 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install) > 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *User Guide* > -- > _Figures_ > *Installation Guide* > 3.2 Installation Step 3: Select Target Folder > 3.3 Installation Step 4: Select Java VM > 3.5 Installation Step 7: Installation Progress in Finished State > 3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace > 3.7 Confirm Selected Features Window > 3.10 Work from an Online Website > 3.11 Work from a Local Copy of the Update .zip file > 3.12 Availalble Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse > *Getting Started Guide* > 3.2 Installation Step 3: Select Target Folder (shared with Install) > 3.3 Installation Step 4: Select Java VM (shared with Install) > 3.4 Installation Step 7: Installation Progress in Finished State (shared with Install) > *Migration Guide* > -- > *User Guide* > 2.4 JBoss Buzz > 2.22 Work from a Local Copy of the JBoss Central .zip File -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-451) Update explicit Kepler text and figs references in docs for 8.0 (Luna)

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-451?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-451: ------------------------------------------ Test updates complete - supported configs updates will be addressed in TOOLSDOC-467. [~sdorfiel], please complete the figure updates. Take new screen caps, editing them as necessary to achieve the desired result, then add to PG as new files and update the topics with the new image numbers. > Update explicit Kepler text and figs references in docs for 8.0 (Luna) > ---------------------------------------------------------------------- > > Key: TOOLSDOC-451 > URL: https://issues.jboss.org/browse/TOOLSDOC-451 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide > Reporter: Michelle Murray > Assignee: Suz Dorfield > Fix For: 4.2.0.Beta1 > > Original Estimate: 4 hours > Time Spent: 35 minutes > Remaining Estimate: 3 hours, 25 minutes > > _Text_ > *Installation Guide* > * 2.2 Supported Operating Systems and Architectures > * 3.3 Install JBoss Developer Studio BYOE > * 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier > * 5.3 Upgrade from JBoss Developer Studio 7.0 > * 6.3 Uninstall JBoss Developer Studio BYOE > *Getting Started Guide* > -- > *Migration Guide* > * 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install) > * 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)* 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *User Guide* > -- > _Figs_ > *Installation Guide* > * Fig 3.6 Ininstall JBoss Developer Studio BYOE via Eclipse Marketplace > * Fig 3.7 Confirm Selected Features Window > * Fig 6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace > * Fig 6.3 Confirm Selected Features Window > *Getting Started Guide* > -- > *Migration Guide* > -- > *User Guide* > -- -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16947) Beans are not automatically validated when beans.xml is changed

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16947?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16947: ----------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Beans are not automatically validated when beans.xml is changed > --------------------------------------------------------------- > > Key: JBIDE-16947 > URL: https://issues.jboss.org/browse/JBIDE-16947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Alexey Kazakov > Fix For: 4.2.x > > > When beans.xml file is changed we always have to run validation manually to reflect newest changes. Shouldn't this be done automatically after beans.xml is changed and saved? -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16947) Beans are not automatically validated when beans.xml is changed

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16947?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16947: ---------------------------------------- We do re-validate all related beans when beans.xml is changed but only for beans which use core features of JSR-299 spec (not extensions). <weld:exclude> is a CDI extension so it requires manual validation. Let's see what we can do here. > Beans are not automatically validated when beans.xml is changed > --------------------------------------------------------------- > > Key: JBIDE-16947 > URL: https://issues.jboss.org/browse/JBIDE-16947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta2 > > > When beans.xml file is changed we always have to run validation manually to reflect newest changes. Shouldn't this be done automatically after beans.xml is changed and saved? -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2881: ----------------------------- CDW release: ? > Make clear the distinction between update.zip and central.zip on access.redhat > ------------------------------------------------------------------------------ > > Key: JBDS-2881 > URL: https://issues.jboss.org/browse/JBDS-2881 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 7.1.1.GA > > > [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip. > update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation." > Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline." > Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline." -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2881: ----------------------------- CDW pm_ack: + (was: ?) > Make clear the distinction between update.zip and central.zip on access.redhat > ------------------------------------------------------------------------------ > > Key: JBDS-2881 > URL: https://issues.jboss.org/browse/JBDS-2881 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 7.1.1.GA > > > [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip. > update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation." > Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline." > Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline." -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2881: ----------------------------- CDW qa_ack: + (was: ?) > Make clear the distinction between update.zip and central.zip on access.redhat > ------------------------------------------------------------------------------ > > Key: JBDS-2881 > URL: https://issues.jboss.org/browse/JBDS-2881 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 7.1.1.GA > > > [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip. > update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation." > Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline." > Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline." -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2881: ----------------------------- CDW release: + (was: ?) > Make clear the distinction between update.zip and central.zip on access.redhat > ------------------------------------------------------------------------------ > > Key: JBDS-2881 > URL: https://issues.jboss.org/browse/JBDS-2881 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 7.1.1.GA > > > [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip. > update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation." > Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline." > Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline." -- 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

11 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 March 2014