October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15789) Renaming HTML file doesn't change editor title

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15789?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15789: ----------------------------------- Fix Version/s: 4.2.x (was: 4.1.1.CR1) > Renaming HTML file doesn't change editor title > ---------------------------------------------- > > Key: JBIDE-15789 > URL: https://issues.jboss.org/browse/JBIDE-15789 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Linux KDE > Reporter: Vlado Pakan > Fix For: 4.2.x > > > 1. Create project with HTML file > 2. Open HTML file in VPE > 3. Rename HTML file in Package Explorer > ASSERT: File is renamed in Package Explorer > ERROR: Editor title of opened HTML file is not 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15789) Renaming HTML file doesn't change editor title

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15789?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15789: ----------------------------------- Component/s: (was: visual-page-editor-core) > Renaming HTML file doesn't change editor title > ---------------------------------------------- > > Key: JBIDE-15789 > URL: https://issues.jboss.org/browse/JBIDE-15789 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Linux KDE > Reporter: Vlado Pakan > Fix For: 4.2.x > > > 1. Create project with HTML file > 2. Open HTML file in VPE > 3. Rename HTML file in Package Explorer > ASSERT: File is renamed in Package Explorer > ERROR: Editor title of opened HTML file is not 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15789) Renaming HTML file doesn't change editor title

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15789?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-15789: -------------------------------------- Assignee: Victor Rubezhny > Renaming HTML file doesn't change editor title > ---------------------------------------------- > > Key: JBIDE-15789 > URL: https://issues.jboss.org/browse/JBIDE-15789 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Linux KDE > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.2.x > > > 1. Create project with HTML file > 2. Open HTML file in VPE > 3. Rename HTML file in Package Explorer > ASSERT: File is renamed in Package Explorer > ERROR: Editor title of opened HTML file is not 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2709: ---------------------------------- As of PM call this week, decision is to wait until SVNKit drops their .Final bits (not Beta2) before adding this to Central. > Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central > ---------------------------------------------------------- > > Key: JBDS-2709 > URL: https://issues.jboss.org/browse/JBDS-2709 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.1.0.Beta1 > > > As reported here: > https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=... > {quote} > Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN. > http://subclipse.tigris.org/update_1.10.x > Local repository compatibility between these tools and JBDS is very nice to have. > Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question. > {quote} > http://www.svnkit.com/download.php > Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2709: ----------------------------- Fix Version/s: 7.1.0.GA (was: 7.1.0.Beta1) > Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central > ---------------------------------------------------------- > > Key: JBDS-2709 > URL: https://issues.jboss.org/browse/JBDS-2709 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.1.0.GA > > > As reported here: > https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=... > {quote} > Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN. > http://subclipse.tigris.org/update_1.10.x > Local repository compatibility between these tools and JBDS is very nice to have. > Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question. > {quote} > http://www.svnkit.com/download.php > Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-411) Add silent install option to the Installation Options in the docs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-411?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-411: ------------------------------------- New suggestion for how to implement the script & documentation: https://issues.jboss.org/browse/JBDS-2768?focusedCommentId=12825077&page=... [~maxandersen] [~mmusaji] [~mmurray] WDYT? > Add silent install option to the Installation Options in the docs > ----------------------------------------------------------------- > > Key: TOOLSDOC-411 > URL: https://issues.jboss.org/browse/TOOLSDOC-411 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Mustafa Musaji > Assignee: Michelle Murray > Fix For: 4.1.1 > > > See the published knowledge base article for instructions on how to do this and the information that should be included [1]. > This needs to be checked by engineering to ensure it's compatible across all platforms. > [1] https://access.redhat.com/site/solutions/44667 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-411) Add silent install option to the Installation Options in the docs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-411?page=com.atlassian.jira.plug... ] Nick Boldt edited comment on TOOLSDOC-411 at 10/25/13 12:30 PM: ---------------------------------------------------------------- New suggestion for how to implement the script & documentation: https://issues.jboss.org/browse/JBDS-2768?focusedCommentId=12825077&page=... [~maxandersen] [~mmusaji] [~mmurray] WDYT? (Tweaks to copy, language, etc. are welcome.) was (Author: nickboldt): New suggestion for how to implement the script & documentation: https://issues.jboss.org/browse/JBDS-2768?focusedCommentId=12825077&page=... [~maxandersen] [~mmusaji] [~mmurray] WDYT? > Add silent install option to the Installation Options in the docs > ----------------------------------------------------------------- > > Key: TOOLSDOC-411 > URL: https://issues.jboss.org/browse/TOOLSDOC-411 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Mustafa Musaji > Assignee: Michelle Murray > Fix For: 4.1.1 > > > See the published knowledge base article for instructions on how to do this and the information that should be included [1]. > This needs to be checked by engineering to ensure it's compatible across all platforms. > [1] https://access.redhat.com/site/solutions/44667 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2768 at 10/25/13 12:27 PM: ------------------------------------------------------------- Here's what I propose, and what users will see if we apply https://github.com/jbdevstudio/jbdevstudio-website/pull/41 and push it to the server: !JBDS2768_simplified.png! [~maxandersen] [~mmusaji] [~mmurray] [~ldimaggio] Can you +1/-1 the above suggestion? None of the more advanced headless install options are mentioned, linked or acknowledged anywhere anymore. :) was (Author: nickboldt): Here's what I propose, and what users will see if we apply PR 41: !JBDS2768_simplified.png! > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Attachments: JBDS2768_simplified.png > > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > And that links to instructions on community site: > http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2768: ----------------------------- Attachment: JBDS2768_simplified.png Here's what I propose, and what users will see if we apply PR 41: !JBDS2768_simplified.png! > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Attachments: JBDS2768_simplified.png > > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > And that links to instructions on community site: > http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2768: ----------------------------- CDW release: + (was: ?) > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > And that links to instructions on community site: > http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 5 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 October 2013