July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15313) Handle Wildfly multi-plexing possibility

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15313: ----------------------------------- Summary: Handle Wildfly multi-plexing possibility Key: JBIDE-15313 URL: https://issues.jboss.org/browse/JBIDE-15313 Project: Tools (JBoss Tools) Issue Type: Task Components: server Affects Versions: 4.1.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.1.Final, 4.2.0.Alpha1 While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen. This jira will investigate what's necessary and what may need to change. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15312) Update all AS versions AND manifest.mf dependency version ranges

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15312: ----------------------------------- Summary: Update all AS versions AND manifest.mf dependency version ranges Key: JBIDE-15312 URL: https://issues.jboss.org/browse/JBIDE-15312 Project: Tools (JBoss Tools) Issue Type: Task Components: server Affects Versions: 4.1.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.1.Final, 4.2.0.Alpha1 API has been added in both branch and master. THis requires an update of version ranges. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13242) Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13242?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBIDE-13242: --------------------------------------- OK, so I understand it like we need to have Project Facet type for seam-gen generated project, is that correct? > Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-13242 > URL: https://issues.jboss.org/browse/JBIDE-13242 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, upstream > Affects Versions: 4.0.0.Beta2 > Environment: Seam.2.3.0, JBDS 5.0.1.GA or JBDS 6.0.0.Beta2a > Reporter: Marek Novotny > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta1 > > > After importing and building a Seam 2.3 seam-gen generated project in JBDS, it reports missing files referenced from view-id in pages.xml and in somEntity.page.xml files. > This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS. > How reproducible: > Import a seam-gen generated EAR project, check pages.xml. > Steps to Reproduce: > 1. Create a seam-gen EAR project. > 2. Import into JBDS. > 3. Open pages.xml, make a change (to trigger build). > > Actual results: > On lines referencing a view-id, like > <redirect view-id="/home.xhtml"/> > JBDS shows an error saying: > Cannot find target resource: "/home.xhtml" -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12915) Kitchensink quickstart is missing .cheatsheet.xml

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12915?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-12915: --------------------------------------- I have updated the PR. Now, it uses the commands introduced by https://issues.jboss.org/browse/JBIDE-14333 This cheatsheet will work with a project example based on an archetype if you copy a project to the workspace and import it or rename the project. The following are the main changes: 1) At the beginning of the cheatsheet, you will see the following command: <command required="true" returns="currentProject" serialization="org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet"/> The command is obliged because it sets the currentProject variable. After that, the currentProject variable is used instead of the hard-coded project name. For instance: <command required="true" serialization="org.jboss.tools.project.examples.cheatsheet.openFileInEditor(path=/${currentProject}/src/main/webapp/WEB-INF/templates/default.xhtml,fromLine=22,toLine=26 or <action pluginId="org.jboss.tools.project.examples.cheatsheet" class="org.jboss.tools.project.examples.cheatsheet.actions.RunOnServer" param1="${currentProject}"/> Within the action, it is possible to use a variable like param1="${currentProject}" but is not possible to use a variable as paramN="/${currentProject}/src/main/webapp/WEB-INF/templates/default.xhtml" The currentProject variable in the paramN attribute won't be translated which means the openFileInEditor command must be used instead of the org.jboss.tools.project.examples.cheatsheet.actions.OpenFileInEditor action. We also need to add the runOnServer and launchJUnitTest command. > Kitchensink quickstart is missing .cheatsheet.xml > ------------------------------------------------- > > Key: JBIDE-12915 > URL: https://issues.jboss.org/browse/JBIDE-12915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Beta1 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.0.0.CR1 > > > After importing Kitchensink example from section "JBoss Developer Framework Quickstarts" in JBoss Central, user is prompted to > {noformat}Show '/jboss-as-kitchensink/.cheatsheet.xml' for further instructions{noformat} > but /jboss-as-kitchensink/.cheatsheet.xml does not exist. > Imported quickstart is named "kitchensink" instead of jboss-as-kitchensink and it has README.md instead of .cheatsheet.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15311) Error in validation of jboss-deployment-structure.xml

by Marek Novotny (JIRA)

Marek Novotny created JBIDE-15311: ------------------------------------- Summary: Error in validation of jboss-deployment-structure.xml Key: JBIDE-15311 URL: https://issues.jboss.org/browse/JBIDE-15311 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Version: 7.0.0.GA Build id: GA-v20130720-0044-B364 Build date: 20130720-0044 WFK 2.3.0.GA, Seam 2.3.1.Final-redhat-2 Reporter: Marek Novotny Wrong validation error on jboss-deployment-structure.xml file: {code:XML} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0"> <deployment> <dependencies> <module name="org.hibernate" export="true"/> <module name="javax.faces.api" export="true" /> <module name="com.sun.jsf-impl" export="true"/> <module name="org.dom4j" export="true"/> <module name="org.hibernate.validator" export="true"/> </dependencies> </deployment> </jboss-deployment-structure> {code} Validation error: {noformat} cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml {noformat} The error says exactly what is in jboss-deployment-structure.xml - we have there deployment, so this is valid and not invalid 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15310) JPP6.1 needs strict serverbean detector

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15310: ----------------------------------- Summary: JPP6.1 needs strict serverbean detector Key: JBIDE-15310 URL: https://issues.jboss.org/browse/JBIDE-15310 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: server Affects Versions: 4.1.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.1.Final While JBDS-2703 fixes the issue of jpp-6.1 being incorrectly recognized, it'd be better if there was a strict detector for identifying 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15286) Increment service version of jbosstools-base/usage submodule

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15286?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15286: ------------------------------------------ ok, I didnt spot this, it definitely makes sense. I updated my PR accordingly. > Increment service version of jbosstools-base/usage submodule > ------------------------------------------------------------ > > Key: JBIDE-15286 > URL: https://issues.jboss.org/browse/JBIDE-15286 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha1 > > > Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.100 according http://wiki.eclipse.org/Version_Numbering. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Meng Bo <bmeng(a)redhat.com> made a comment on [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] Move bug to verified. > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Meng Bo <bmeng(a)redhat.com> changed the Status of [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] from ON_QA to VERIFIED > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-380) Technical Review of 7.0 Installation Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-380?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-380: ------------------------------------------ Updated anchors: * 1.1. About Red Hat JBoss Developer Studio * 2.1. System Requirements Overview * 3.2. Install JBoss Developer Studio * 3.3. Install JBoss Developer Studio BYOE * 5.1. Upgrade Methods * 5.3. Upgrade JBoss Developer Studio BYOE * 6.2. Uninstall JBoss Developer Studio * 6.3. Uninstall JBoss Developer Studio BYOE A.1. Determine Default Java Developer Kit of the System > Technical Review of 7.0 Installation Guide > ------------------------------------------ > > Key: TOOLSDOC-380 > URL: https://issues.jboss.org/browse/TOOLSDOC-380 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Conduct a post release technical review of 7.0 Installation Guide to catch any previously missed technical or copy errors. -- 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, 8 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 July 2013