October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15788: -------------------------------- Attachment: install_folder_must_exist.png > Download runtime wizard shouldn't complain if install folder doesn't exist > -------------------------------------------------------------------------- > > Key: JBIDE-15788 > URL: https://issues.jboss.org/browse/JBIDE-15788 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.1.Alpha2 > Reporter: Fred Bricon > Fix For: 4.1.1.CR1 > > Attachments: install_folder_must_exist.png > > > If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary) > - assert no EAP/AS7 are installed > - create a new html5 project from central > - click download and install for the server requirement > - enter a non-existing location for the install folder -- 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, 6 months

1
0
0 / 0

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

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15789: ----------------------------------- Summary: 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.1.1.CR1 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-15788: ----------------------------------- Summary: Download runtime wizard shouldn't complain if install folder doesn't exist Key: JBIDE-15788 URL: https://issues.jboss.org/browse/JBIDE-15788 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: server Affects Versions: 4.1.1.Alpha2 Reporter: Fred Bricon Fix For: 4.1.1.CR1 If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary) - assert no EAP/AS7 are installed - create a new html5 project from central - click download and install for the server requirement - enter a non-existing location for the install folder -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15787) Wildfly Server Adapter does not move to "started" state

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15787: ------------------------------------- Summary: Wildfly Server Adapter does not move to "started" state Key: JBIDE-15787 URL: https://issues.jboss.org/browse/JBIDE-15787 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.Beta1 Reporter: Xavier Coulon Running on MacOSX. Server is Wildfly 8.0.0.Beta1 I created a server adapter, deployed a sample web application and when I start the server, I can see in the logs that the server started and deployed my application, but the server adapter seems blocked, waiting for server startup (see status bar on screenshot). After a few minutes of waiting, the server adapter fails and stops the Wildfly server. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15750) AS7.1 requirement is not met when its downloaded and installed from IDE

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15750?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15750: --------------------------------------- The issue can be reproduced with the HTML5 wizard. The PR fixes it. > AS7.1 requirement is not met when its downloaded and installed from IDE > ----------------------------------------------------------------------- > > Key: JBIDE-15750 > URL: https://issues.jboss.org/browse/JBIDE-15750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: HTML5_missing_req.png > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15765) JPP 6.1 recognized as AS 7.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15765: ------------------------------------- I would like to note the following. While ER-3 has only 1 match for JBoss-Product-Release-Name on a search through the entire modules directory, ga has 2. such matches. And they conflict. [rob@rawbdor modules]$ grep -R "JBoss-Product-Release-Name" * system/layers/base/org/jboss/as/product/eap/dir/META-INF/MANIFEST.MF:JBoss-Product-Release-Name: EAP system/layers/gatein/org/jboss/as/product/jpp/dir/META-INF/MANIFEST.MF:JBoss-Product-Release-Name: Portal Platform The first match is incorrect. The second match seems correct, but it is in a location that violates the spec we were told would be honored. The correct match seems to live in system/layers/{LAYER}/org/jboss/as/product/{SLOT}/dir/META-INF/MANIFEST.MF. > JPP 6.1 recognized as AS 7.2 > ---------------------------- > > Key: JBIDE-15765 > URL: https://issues.jboss.org/browse/JBIDE-15765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: jpp 6.1 recognized as AS 72.jpg > > > JBoss Portal 6.1.0 Final is recognized as AS 7.2 in JBoss Runtime Detection (Type: AS, Version: 7.2). However, JPP 6.1.0 Beta is recognized correctly as JPP 6.1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15765) JPP 6.1 recognized as AS 7.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15765: ------------------------------------- JBossTools detects servers based on a set of assumptions, specifically file layout. It was our understanding that all of our assumptions were actual contracts, not just assumptions. I will list the assumptions below: 1) any eap-based product will have a slot listed in bin/product.conf 2) any eap-based product will have a list of layers in modules/layers.conf 3) A manifest.mf file may be found for your slot's information at "modules/system/layers/base/org/jboss/as/product/" + slot + "/dir/META-INF" 4) A manifest.mf file may be found for each layer at: "modules/system/layers/" + layer + "/org/jboss/as/product/" + layer + "/dir/META-INF" It's possible these assumptions only hold true for official slots and layers, and that other system paths may be used for extensions not contributed by JBoss. But for this I'm unaware, and we never fully spec'd it out. It was our assumption that in these folders, there would be manifest.mf files that would give specific details about the release, such as the release name and version. For example, JPP 6.1 ER3 had the following contents at path: jboss-jpp-6.1.0.ER03.zip.expanded/jboss-jpp-6.1/modules/system/layers/base/org/jboss/as/product/jpp/dir/META-INF/MANIFEST.MF: JBoss-Product-Release-Name: Portal Platform JBoss-Product-Release-Version: 6.1.0.ER03 JBoss-Product-Console-Slot: jpp Today, that folder does not exist, and has instead been replaced with jboss-jpp-6.1.0.ER03.zip.expanded/jboss-jpp-6.1/modules/system/layers/base/org/jboss/as/product/eap/dir/META-INF/MANIFEST.MF The contents of this new folder are: JBoss-Product-Release-Name: EAP JBoss-Product-Release-Version: 6.1.1.GA JBoss-Product-Console-Slot: eap > JPP 6.1 recognized as AS 7.2 > ---------------------------- > > Key: JBIDE-15765 > URL: https://issues.jboss.org/browse/JBIDE-15765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: jpp 6.1 recognized as AS 72.jpg > > > JBoss Portal 6.1.0 Final is recognized as AS 7.2 in JBoss Runtime Detection (Type: AS, Version: 7.2). However, JPP 6.1.0 Beta is recognized correctly as JPP 6.1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15771) Duplicate and missing menu item for Markers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15771?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15771: ------------------------------------- Fix Version/s: 4.1.1.Beta1 > Duplicate and missing menu item for Markers > ------------------------------------------- > > Key: JBIDE-15771 > URL: https://issues.jboss.org/browse/JBIDE-15771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.1.1.Beta1 > > Attachments: duplicate.png > > > There are 2 menu items for "Configure Markers..." in Project explorer context menu of the project and in the Package explorer is missing menu item for "Configure Markers..." see attached image. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15771) Duplicate and missing menu item for Markers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15771?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15771: --------------------------------------- +1 on PR, it works great. > Duplicate and missing menu item for Markers > ------------------------------------------- > > Key: JBIDE-15771 > URL: https://issues.jboss.org/browse/JBIDE-15771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.1.1.Beta1 > > Attachments: duplicate.png > > > There are 2 menu items for "Configure Markers..." in Project explorer context menu of the project and in the Package explorer is missing menu item for "Configure Markers..." see attached image. -- 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, 6 months

1
0
0 / 0

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

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Vlado Pakan commented on JBDS-2709: ----------------------------------- Who should decide? QA or PM or somebody else? For QA it's ok to add it to JBoss Central. It's working fine. > 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, 6 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