September 2013 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-391) Add plug-in books to customer portal under 7.0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-391?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-391: ------------------------------------- Parent: TOOLSDOC-382 Issue Type: Sub-task (was: Task) > Add plug-in books to customer portal under 7.0 > ---------------------------------------------- > > Key: TOOLSDOC-391 > URL: https://issues.jboss.org/browse/TOOLSDOC-391 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Although not changed, the plug-in books for 6.0 need to be relabelled for 7.0 and put on the RH JBDS customer portal page. -- 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] (TOOLSDOC-390) Update book versions for 7.1/4.2

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-390?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-390: ------------------------------------- Parent: (was: TOOLSDOC-382) Issue Type: Task (was: Sub-task) > Update book versions for 7.1/4.2 > -------------------------------- > > Key: TOOLSDOC-390 > URL: https://issues.jboss.org/browse/TOOLSDOC-390 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Update Book_Info.xml & Revision History with 7.1. > Update pom.xml with 4.2.0 > Also incorporate TOOLSDOC-313 (moving doc version out of master.xml and into pom.xml). -- 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] (TOOLSDOC-390) Update book versions for 7.1/4.2

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-390?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-390: ------------------------------------------ Done for plug-in books jbosstools-hibernate: https://github.com/jbosstools/jbosstools-hibernate/pull/27 jbosstools-javaee: https://github.com/jbosstools/jbosstools-javaee/pull/143 jbosstools-portlet: https://github.com/jbosstools/jbosstools-portlet/pull/16 jbosstools-webservices: https://github.com/jbosstools/jbosstools-webservices/pull/85 jbosstools-central: https://github.com/jbosstools/jbosstools-central/pull/155/ Still need to do for core books (via CCMS). > Update book versions for 7.1/4.2 > -------------------------------- > > Key: TOOLSDOC-390 > URL: https://issues.jboss.org/browse/TOOLSDOC-390 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Update Book_Info.xml & Revision History with 7.1. > Update pom.xml with 4.2.0 > Also incorporate TOOLSDOC-313 (moving doc version out of master.xml and into pom.xml). -- 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] (TOOLSDOC-390) Update book versions for 7.1/4.2

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-390?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-390: ------------------------------------- Summary: Update book versions for 7.1/4.2 (was: Add plug-in books to customer portal under 7.0) > Update book versions for 7.1/4.2 > -------------------------------- > > Key: TOOLSDOC-390 > URL: https://issues.jboss.org/browse/TOOLSDOC-390 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Although not changed, the plug-in books for 6.0 need to be relabelled for 7.0 and put on the RH JBDS customer portal page. -- 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] (TOOLSDOC-390) Update book versions for 7.1/4.2

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-390?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-390: ------------------------------------- Description: Update Book_Info.xml & Revision History with 7.1. Update pom.xml with 4.2.0 Also incorporate TOOLSDOC-313 (moving doc version out of master.xml and into pom.xml). was:Although not changed, the plug-in books for 6.0 need to be relabelled for 7.0 and put on the RH JBDS customer portal page. > Update book versions for 7.1/4.2 > -------------------------------- > > Key: TOOLSDOC-390 > URL: https://issues.jboss.org/browse/TOOLSDOC-390 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Update Book_Info.xml & Revision History with 7.1. > Update pom.xml with 4.2.0 > Also incorporate TOOLSDOC-313 (moving doc version out of master.xml and into pom.xml). -- 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] (TOOLSDOC-391) Add plug-in books to customer portal under 7.0

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-391: ---------------------------------------- Summary: Add plug-in books to customer portal under 7.0 Key: TOOLSDOC-391 URL: https://issues.jboss.org/browse/TOOLSDOC-391 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: General documentation issues Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.1.0 Although not changed, the plug-in books for 6.0 need to be relabelled for 7.0 and put on the RH JBDS customer portal page. -- 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] (TOOLSDOC-390) Add plug-in books to customer portal under 7.0

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-390: ---------------------------------------- Summary: Add plug-in books to customer portal under 7.0 Key: TOOLSDOC-390 URL: https://issues.jboss.org/browse/TOOLSDOC-390 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Security Level: Public (Everyone can see) Components: General documentation issues Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.1.0 Although not changed, the plug-in books for 6.0 need to be relabelled for 7.0 and put on the RH JBDS customer portal page. -- 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-15484) Provide support for scaled app when tailing log files

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15484?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-15484: -------------------------------------------- Nice! Glad this will be fixed :) > Provide support for scaled app when tailing log files > ----------------------------------------------------- > > Key: JBIDE-15484 > URL: https://issues.jboss.org/browse/JBIDE-15484 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Alpha2, 4.2.x > > > Seems like it's simply a matter of adding a '--gears' parameter in the ssh command when the application is scalable. > The dialog could provide a checkbox (enabled by default) to let the user choose whether she wants to grab all logs or just those on the HA-Proxy > See [~lincolnthree]'s blog post on the subject: http://ocpsoft.org/jboss/openshift-pro-tip-scaling-tail-server-logs-on-al... -- 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-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2623 at 9/12/13 4:16 PM: ----------------------------------------------------------- First kick at the can: https://github.com/jbosstools/jbosstools-discovery/pull/35 However it fails with this error: {code} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions (default-cli) on project jbtcentral-multiple: Execution default-cli of goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions failed: Failed to load p2 repository with ID 'http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0...' from location http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0...: The p2 repository at http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... * contains units from an old style update site which cannot be used for dependency resolution * {code} [~mickael_istria] Do you have any advice for how to work around this? was (Author: nickboldt): First kick at the can: https://github.com/jbosstools/jbosstools-discovery/pull/35 However it fails with this error: {code} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions (default-cli) on project jbtcentral-multiple: Execution default-cli of goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions failed: Failed to load p2 repository with ID 'http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0...' from location http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0...: The p2 repository at http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... * contains units from an old style update site which cannot be used for dependency resolution * {code} > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2623 at 9/12/13 4:16 PM: ----------------------------------------------------------- First kick at the can: https://github.com/jbosstools/jbosstools-discovery/pull/35 However it fails with this error: {code} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions (default-cli) on project jbtcentral-multiple: Execution default-cli of goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions failed: Failed to load p2 repository with ID 'http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0...' from location http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0...: The p2 repository at http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... * contains units from an old style update site which cannot be used for dependency resolution * {code} was (Author: nickboldt): https://github.com/jbosstools/jbosstools-discovery/pull/35 > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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