December 2010 - jbosstools-issues

[JBoss JIRA] Resolved: (JBDS-1437) Bundle org.jboss.tools.equinox.transforms.xslt@1:start not found.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1437?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-1437. --------------------------------- > Bundle org.jboss.tools.equinox.transforms.xslt@1:start not found. > ----------------------------------------------------------------- > > Key: JBDS-1437 > URL: https://issues.jboss.org/browse/JBDS-1437 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Reporter: Dmitry Geraskov > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.0.0.CR1 > > > To reproduce: > download and install jbdevstudio-eap-win32-4.0.0.v201011220647N-H191-Beta2.jar (I use Windows XP) > Run jbds on empty workspace. > There are 2 errors in Error log without stacktraces: > Bundle org.jboss.tools.equinox.transforms.xslt@1:start not found. > and https://jira.jboss.org/browse/TEIIDDES-725 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-1436) Aggregator build no longer collects child component zips

by Nick Boldt (JIRA)

Aggregator build no longer collects child component zips -------------------------------------------------------- Key: JBDS-1436 URL: https://jira.jboss.org/browse/JBDS-1436 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: Build Affects Versions: 4.0.0.Beta2 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 4.0.0.CR1 Since moving to a single URL from which to build the aggregate site [1], the component zip aggregator no longer works and therefore the zips published for use w/ JBDS are not kept fresh. This specifically affects the following zips: /updates/staging/3.2_stable_branch/jbosstools-drools-5.2-Update.zip + /updates/staging/3.2_stable_branch/esb-Update.zip /updates/staging/3.2_stable_branch/jbpm-Update.zip /updates/staging/3.2_stable_branch/modeshape-Update.zip /updates/staging/3.2_stable_branch/usage-Update.zip as pulled from these jobs: http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosst... + http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosst... [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/pom.xml -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7739) Use DriverInstance#getJarListAsArray() instead of getJarList() and manual parsing.

by Dmitry Geraskov (JIRA)

Use DriverInstance#getJarListAsArray() instead of getJarList() and manual parsing. ---------------------------------------------------------------------------------- Key: JBIDE-7739 URL: https://jira.jboss.org/browse/JBIDE-7739 Project: Tools (JBoss Tools) Issue Type: Quality Risk Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Minor Fix For: 3.2.0.CR1 ConnectionProfileUtil calls DriverInstance#getJarList() and calling classes should parser returned string to get jar list. There is existing DriverInstance#getJarListAsArray() method which returns drivers like an array. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7821) Booking22 Example requires JDK5

by Dominik Pospisil (JIRA)

Booking22 Example requires JDK5 ------------------------------- Key: JBIDE-7821 URL: https://jira.jboss.org/browse/JBIDE-7821 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.0.Beta2 Reporter: Dominik Pospisil Assignee: Snjezana Peco Booking22 Example is hard-coded to rely on JDK5. As EAP5 is supported only with JDK6 and the example runs fine on JDK6, this constrain should be removed. Also, is there any reason, why not to fix JBIDE-7172 ? I would really like to see working out-of-the-box exerience with JBDS4 and bundled EAP5. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7791) Apply entered text in Query Parameters View on focus change

by Dmitry Geraskov (JIRA)

Apply entered text in Query Parameters View on focus change ----------------------------------------------------------- Key: JBIDE-7791 URL: https://jira.jboss.org/browse/JBIDE-7791 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.0.CR1 In Query Parameters View for named parameter enter value in text field and press "..." button. The entered text value will be cancelled, but it is better if it would be applied. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7179) Projects with references to other projects created by m2eclipse fail to publish with NPE

by Pete Muir (JIRA)

Projects with references to other projects created by m2eclipse fail to publish with NPE ---------------------------------------------------------------------------------------- Key: JBIDE-7179 URL: https://jira.jboss.org/browse/JBIDE-7179 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud, JBossAS Affects Versions: 3.2.0.M2 Reporter: Pete Muir Priority: Critical If I import a war using m2eclipse that refers to another project (which builds as a JAR) as a project reference, then I get this NPE when I try to deploy using deltacloud tools: java.lang.NullPointerException at java.io.File.<init>(File.java:262) at org.eclipse.rse.internal.services.local.files.LocalFileService.createFolder(LocalFileService.java:993) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:70) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler.makeDirectoryIfRequired(RSERemotePublishHandler.java:65) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:188) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:93) at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1025) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1115) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:948) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2889) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) If I switch this to a normal jar dep, then the NPE goes away and the project deploys successfully. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7311) ELValidator tests failure

by Alexey Kazakov (JIRA)

ELValidator tests failure ------------------------- Key: JBIDE-7311 URL: https://jira.jboss.org/browse/JBIDE-7311 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 Failed tests: testUnknownELVariable(org.jboss.tools.jsf.test.validation.ELValidatorTest) testRevalidationUnresolvedELs(org.jboss.tools.jsf.test.validation.ELValidatorTest) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7291) MyFaces 2.0: look for myfaces-metadata.xml resources in the complete classpath

by Viacheslav Kabanovich (JIRA)

MyFaces 2.0: look for myfaces-metadata.xml resources in the complete classpath ------------------------------------------------------------------------------ Key: JBIDE-7291 URL: https://jira.jboss.org/browse/JBIDE-7291 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Beta1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.2.0.Beta2 We should be consistent in how resource lookups are done so if someone decides to unzip classes or import src are not seeing different behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-127) Ensure JBT nightly doc builds are......building

by Isaac Rooskov (JIRA)

Ensure JBT nightly doc builds are......building ----------------------------------------------- Key: TOOLSDOC-127 URL: https://jira.jboss.org/browse/TOOLSDOC-127 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Max Andersen Assignee: Isaac Rooskov Priority: Critical For a while now the JBT nightly doc builds have not been working. If I remember correctly, this started because of space unavailability issues on the Hudson server. Currently I am unsure if this is still an issue. This task issue is to track the progress of getting this valuable resource up and running again. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-129) [Teiid Developer User Guide] Document layout does not follow standard JBoss style.

by Isaac Rooskov (JIRA)

[Teiid Developer User Guide] Document layout does not follow standard JBoss style. ---------------------------------------------------------------------------------- Key: TOOLSDOC-129 URL: https://issues.jboss.org/browse/TOOLSDOC-129 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: LATER Reporter: Andrew Ross Assignee: Isaac Rooskov The document does use numbers for sub-sections. Sub-sections do not use the default font size. JBoss_Developer_Studio-Teiid_Designer_User_Guide-4.0-web-en-US-4.0.0-8.el5 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 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 December 2010