August 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-3626) Gutter indicator for area covered by if and foreach in FreeMarker

by Francisco Jose Peredo Noguez (JIRA)

Gutter indicator for area covered by if and foreach in FreeMarker ----------------------------------------------------------------- Key: JBIDE-3626 URL: https://jira.jboss.org/jira/browse/JBIDE-3626 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: FreeMarker Reporter: Francisco Jose Peredo Noguez In .ftl (freemarker) files it is really hard to see where <#if> and <#foreach> end, because indentation affects the output, and therefore it can not be used. In xhtml files, if I put the cursor inside a tag the gutter of the editor make it easy to see where the tag end because it changes its color to a darker gray. This works even if indentation is messed up. Therefore I want this gutter indicators for the FreeMarker editor. -- 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

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3625) Option to Expand/Collapse (Code Folding?) for <#if> and <#foreach> keywords in FreeMarker editor

by Francisco Jose Peredo Noguez (JIRA)

Option to Expand/Collapse (Code Folding?) for <#if> and <#foreach> keywords in FreeMarker editor ------------------------------------------------------------------------------------------------ Key: JBIDE-3625 URL: https://jira.jboss.org/jira/browse/JBIDE-3625 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: FreeMarker Reporter: Francisco Jose Peredo Noguez Option to Expand/Collapse (Code Folding?) for <#if> and <#foreach> keywords in FreeMarker editor -- 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

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2765) Create updatesite for nightly builds

by Max Rydahl Andersen (JIRA)

Create updatesite for nightly builds ------------------------------------ Key: JBIDE-2765 URL: https://jira.jboss.org/jira/browse/JBIDE-2765 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Max Rydahl Andersen Fix For: LATER Creating an updatesite at http://download.jboss.org/jbosstools/updates/nightly would be good for early adopters. The nightly build could automatically create the artifacts and update it accordingly. -- 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

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-2766) Use eclipses "timestamp" postfix versioning scheme for plugins

by Max Rydahl Andersen (JIRA)

Use eclipses "timestamp" postfix versioning scheme for plugins -------------------------------------------------------------- Key: JBIDE-2766 URL: https://jira.jboss.org/jira/browse/JBIDE-2766 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Max Rydahl Andersen Fix For: LATER Allow us to have alway incremental plugin versions - no overlap. We should though still try and keep the beta, alpha, GA part in the postfix so it is still identifiable. -- 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

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-736) Process project creation wizard in JBDS 2.0 fails to create a complete sample project a jBPM runtime as provided in SOA-P 4.3CP01

by Len DiMaggio (JIRA)

Process project creation wizard in JBDS 2.0 fails to create a complete sample project a jBPM runtime as provided in SOA-P 4.3CP01 --------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-736 URL: https://jira.jboss.org/jira/browse/JBDS-736 Project: Developer Studio Issue Type: Bug Components: integration Affects Versions: 2.0.0.GA Reporter: Len DiMaggio The jBPM process project creation wizard in JBDS 2.0 (I'm using Version: 2.0.0.CR1) fails to create a complete sample project a jBPM runtime as provided in SOA-P 4.3CP01. The wizard expects to find activation.jar here - but the file is not part of CP01 jboss-soa-p.4.3.0/jbpm-jpdl/lib/activation.jar The wizard reports this error and fails to create a processdefinition.xml file. -- 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

14 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4769) The Warning resource marker is to be added to the project indicating that the KB-nature and KB-builder are not specified on the project.

by Victor Rubezhny (JIRA)

The Warning resource marker is to be added to the project indicating that the KB-nature and KB-builder are not specified on the project. ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4769 URL: https://jira.jboss.org/jira/browse/JBIDE-4769 Project: JBoss Tools Issue Type: Sub-task Reporter: Victor Rubezhny Assignee: Viacheslav Kabanovich -- 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

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3499) Model for JBoss ESB configuration

by John Graham (JIRA)

Model for JBoss ESB configuration --------------------------------- Key: JBIDE-3499 URL: https://jira.jboss.org/jira/browse/JBIDE-3499 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.GA Reporter: John Graham Assignee: John Graham Fix For: LATER We need a domain model (perhaps EMF based) for JBoss ESB configuration files. This model should be versioned, as the JBoss ESB configuration file is likely to evolve in future releases. This model would then be used by tools interacting with JBoss ESB configuration, including service editors, testing tools, impact analysis, and so on. Need to consider extensibility dimensions for actions. -- 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

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2399) Validation of ESB files for specific SOA-P versions

by John Graham (JIRA)

Validation of ESB files for specific SOA-P versions --------------------------------------------------- Key: JBIDE-2399 URL: http://jira.jboss.com/jira/browse/JBIDE-2399 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: John Graham Assigned To: John Graham Given that the SOA-P run time will change from release to release, we need some generic way of validating ESB files in Eclipse projects for specific run time versions. This might be done at the package level (that is, when creating a deployment package), but ideally would be done "live:" as the user makes changes, warnings/errors would appear in the Eclipse Problems view. To accomplish this, we would need to set a (minimum? probably not, because backward compatibility is not supported) "SOA-P run time level" (like the JVM level) and have a validation model for checking. The idea is to avoid simple compatibility errors appearing at run time where they could have been noticed at design time. (This is related to, but larger than, the ESB reference tracking work.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4295) JUnit test for ESB services

by John Graham (JIRA)

JUnit test for ESB services --------------------------- Key: JBIDE-4295 URL: https://jira.jboss.org/jira/browse/JBIDE-4295 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.GA Reporter: John Graham Assignee: John Graham Fix For: LATER A wizard that inspects a chosen JBoss ESB configuration file and produces 1 or more JUnit tests that invoke the services, similar to the test stubs that appear in the ESB Quick Starts. -- 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

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4732) The summary of BPEL validator issue

by Denny Xu (JIRA)

The summary of BPEL validator issue ----------------------------------- Key: JBIDE-4732 URL: https://jira.jboss.org/jira/browse/JBIDE-4732 Project: JBoss Tools Issue Type: Bug Components: bpm Affects Versions: 3.1.0.M3 Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.1.0.M3 so far, the bpel validator still has the following issues not get fixed: 1. before validate bpel resource, the validator is unable to delete all bpel problem markers which created by bpel validator, it only delete the related markers in .bpel files, but it should not be the right logic, when validating a bpel file, it validates all the bpel file referenced other types of files, such .wsdl and .xsd file, so that if validate the same file *n* times, the same bpel problem markers will have *n* records in the problem view. 2. after validate bpel resource, only the markers of .bpel file can be located to the accurate line number position when double click relevant markers. 3. when checking xpath function, the return type of those functions are *Integer*, such as the function concat(string str1, string str2) , then it generates a type un-compatible warning message. 4. it seems the validator doesn't support to validate xpath2.0 -- 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

14 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2009