September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12410) Seam tools model does not support multiple web content folders

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12410: -------------------------------------- Summary: Seam tools model does not support multiple web content folders Key: JBIDE-12410 URL: https://issues.jboss.org/browse/JBIDE-12410 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.4.0.M1 1. Create a seam project. 2. Create a new folder <project>/NewWebContent 3. Open .settings/org.eclipse.wst.common.component 4. Add the new web content folder there: {code} <wb-resource deploy-path="/" source-path="/NewWebContent"> <wb-resource deploy-path="/" source-path="/WebContent" tag="defaultRootSource"/> {code} 5. Save the file. 6. Open components.xml 7. Add the following components there: {code} <component name="test" class="broken"></component> <component name="test" class="broken"></component> {code} 8. Save the file. 9. There should be error markers on the components. But now it's not working since Seam Tools don't recognize WebContent folder as a web root. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4418) A configuration with this name already exists

by Krasimir Goutcev (JIRA)

A configuration with this name already exists ---------------------------------------------- Key: JBIDE-4418 URL: https://jira.jboss.org/jira/browse/JBIDE-4418 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M1 Environment: Galileo RC2 Night build H221 Reporter: Krasimir Goutcev -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5418) Provide xulrunner eclipse bundle for OSX cocoa x86_64

by Maxim Areshkau (JIRA)

Provide xulrunner eclipse bundle for OSX cocoa x86_64 ----------------------------------------------------- Key: JBIDE-5418 URL: https://jira.jboss.org/jira/browse/JBIDE-5418 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.next Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa 64 bit To get it worked we need xulrunner bundle for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

10
41
0 / 0

[JBoss JIRA] (JBIDE-9912) NPE when moving mouse over a tag

by Alexey Kazakov (Created) (JIRA)

NPE when moving mouse over a tag -------------------------------- Key: JBIDE-9912 URL: https://issues.jboss.org/browse/JBIDE-9912 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M4 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.3.0.M4 EXECUTE: Import tck project from o.j.t.cdi.core.test plug-in EXECUTE: Open home.xhtml EXECUTE: Move mouse over <h:graphicImage value="/img/seamlogo.png" alt="Seam logo"/> (line #22 - "/img/seamlogo.png") FAILURE: See Eclipse log: {code} java.lang.NullPointerException at org.eclipse.jst.jsf.facelet.core.internal.cm.ElementCMAdapter.getLength(ElementCMAdapter.java:109) at org.eclipse.wst.xml.core.internal.contentmodel.basic.CMNamedNodeMapImpl.<init>(CMNamedNodeMapImpl.java:40) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.getCMAttributeDeclaration(XMLTagInfoHoverProcessor.java:206) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeTagAttValueHelp(XMLTagInfoHoverProcessor.java:135) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeRegionHelp(XMLTagInfoHoverProcessor.java:111) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeHoverHelp(XMLTagInfoHoverProcessor.java:86) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.getHoverInfo(XMLTagInfoHoverProcessor.java:257) at org.eclipse.jst.jsf.facelet.ui.internal.hover.FaceletHover.getHoverInfo(FaceletHover.java:58) at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:145) at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:132) at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

8
12
0 / 0

[JBoss JIRA] (JBIDE-12411) Can't edit the file in JBT XML Editor after editing web root folder settings

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12411: -------------------------------------- Summary: Can't edit the file in JBT XML Editor after editing web root folder settings Key: JBIDE-12411 URL: https://issues.jboss.org/browse/JBIDE-12411 Project: Tools (JBoss Tools) Issue Type: Bug Components: XML Structured Editor Affects Versions: 3.4.0.M1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.4.0.M1 1. Create a seam project 2. Create a new folder <project>/NewWebContent 3. Open components.xml with JBT XML Editor 4. Try to edit the file. It works. 5. Open .settings/org.eclipse.wst.common.component 6. Add the new web content folder there: {code} <wb-resource deploy-path="/" source-path="/NewWebContent"> <wb-resource deploy-path="/" source-path="/WebContent" tag="defaultRootSource"/> {code} 7. Save the file. 8. Try to edit the components.xml againg. 9. It's not working anymore. 10. Close the editor. Open again. 11. Now I can edit it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1628) 3rd party cert: jslint 1.5

by Nick Boldt (JIRA)

3rd party cert: jslint 1.5 -------------------------- Key: JBDS-1628 URL: https://issues.jboss.org/browse/JBDS-1628 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification Affects Versions: 5.0.0.M1 Reporter: Nick Boldt Fix For: 5.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
7
0 / 0

[JBoss JIRA] (JBDS-2286) Eclipse Juno dir path length bug breaks ESB examples

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2286: ---------------------------------- Summary: Eclipse Juno dir path length bug breaks ESB examples Key: JBDS-2286 URL: https://issues.jboss.org/browse/JBDS-2286 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 6.0.0.Alpha1-SOA Environment: Eclipse Juno JBosstools - from trunk - http://svn.jboss.org/repos/jbosstools Reporter: Len DiMaggio Assignee: Douglas Palmer Priority: Blocker Fix For: LATER This eclipse Juno bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193 Which shows up as: at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:188) at java.lang.ProcessImpl.start(ProcessImpl.java:132) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021) ... 10 more Note - The real issue is that the classpath is too long, not the dir path. The problem is preventing the ESB examples from running. To recreate the issue, open the eclipse/tools UI with a CLI command such as: cmd.exe /X /C ""C:\Program Files\Java\jdk1.7.0\jre\bin\java.exe" -Dosgi.noShutdown=false -Dosgi.os=win32 -Dosgi.ws=win32 -Dosgi.arch=x86_64 -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -Djbosstools.test.jbossesb.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jbossesb-4.11 -Djbosstools.test.jbosssoa.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jboss-soa-p-5/jboss-as -Dswtbot.test.properties.file=./org.jboss.tools.esb.ui.bot.test.properties -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -jar C:\Users\jbossqa\.m2\repository\p2\osgi\bundle\org.eclipse.equinox.launcher\1.3.0.v20120522-1813\org.eclipse.equinox.launcher-1.3.0.v20120522-1813.jar -data C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\data -dev file:/C:/Users/jbossqa/jbosstools/trunk/esb/tests/org.jboss.tools.esb.ui.bot.test/target/dev.properties -install C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work -configuration C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\configuration -application org.eclipse.ui.ide.workbench " Then import any of the ESB examples and attempt to run one of the clients (such as SendJMSMessage). Automated tests for this are here: Error #1 - http://machydra.brq.redhat.com:8080/job/esb.bot.tests.ldimaggi.matrixtest/ -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2221) remove mylyn from com.jboss.jbds.subclipse.feature; move into new com.jboss.jbds.subclipse.mylyn.feature

by Nick Boldt (JIRA)

13 years, 6 months

3
16
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-243) Update Getting Started Guide to reference EAP6

by Nick Boldt (JIRA)

Update Getting Started Guide to reference EAP6 ---------------------------------------------- Key: TOOLSDOC-243 URL: https://issues.jboss.org/browse/TOOLSDOC-243 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Getting Started Guide Affects Versions: 3.3.0.Final Reporter: Nick Boldt Assignee: Isaac Rooskov Fix For: 3.3.0.Final (From JBDS-1814 - see https://issues.jboss.org/browse/JBDS-1814?focusedCommentId=12623742&page=...) Concerning the Getting Started Guide content: * for JBDS/enterprise, please update this to be EAP - and make note of how someone acquires EAP, either from their subscription via the Customer Portal or from an evaluation at www.jboss.com/downloads - at this moment we only point out the AS 4.2.3 at jboss.org -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-12629) Improve process to publish/consumes m2e-wtp

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12629: -------------------------------------- Summary: Improve process to publish/consumes m2e-wtp Key: JBIDE-12629 URL: https://issues.jboss.org/browse/JBIDE-12629 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: target-platform, UpStream Reporter: Mickael Istria Assignee: Nick Boldt Fix For: 4.0.0.Beta1 m2e gets pushed to the updates/requirements/m2e-wtp.juno url, whose content get overridden. However, published target-platform still depends on old content until they get modified. We should find a better process that prevent target platforms from being broken, and that would make build reproducible. A solution would be to keep old versions of m2e-wtp under the m2e-wtp.juno folder (1 child folder for each version), and to modify target-platform on request to use 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

13 years, 6 months

2
12
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 2012