May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7799) Could not parse process L/ddd/src/main/rules/ruleflow.rf

by Libor Zoubek (JIRA)

Could not parse process L/ddd/src/main/rules/ruleflow.rf -------------------------------------------------------- Key: JBIDE-7799 URL: https://jira.jboss.org/browse/JBIDE-7799 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.Beta2 Environment: soa-p 4.3 Reporter: Libor Zoubek Assignee: Kris Verlaenen -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
21
0 / 0

[JBoss JIRA] Commented: (JBIDE-8242) Change the ModeShape Eclipse plugin to enable resource versioning in the repository.

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8242?page=com.atlassian.jira.plugin... ] Dan Florian commented on JBIDE-8242: ------------------------------------ Yes this will make it in. I'm just waiting for the final release of ModeShape 2.5.0 which is scheduled to be released by the end of month. All my coding is done. > Change the ModeShape Eclipse plugin to enable resource versioning in the repository. > ------------------------------------------------------------------------------------ > > Key: JBIDE-8242 > URL: https://issues.jboss.org/browse/JBIDE-8242 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: modeshape > Affects Versions: 3.2.0.Beta2 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 3.2.1.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Based on MODE-1027, the Eclipse plugin needs to be changed to enable versioning of resouces in the repository. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-8482) Hook up the Forge tools into the main JBT build.

by Koen Aers (JIRA)

Hook up the Forge tools into the main JBT build. ------------------------------------------------ Key: JBIDE-8482 URL: https://issues.jboss.org/browse/JBIDE-8482 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Reporter: Koen Aers Assignee: Nick Boldt I have created pom.xml files as I thought it was appropriate. I'll leave the rest in the hands of buildmaster extraordinaire. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Issue Comment Edited: (JBIDE-8242) Change the ModeShape Eclipse plugin to enable resource versioning in the repository.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8242?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen edited comment on JBIDE-8242 at 5/25/11 3:02 AM: --------------------------------------------------------------------- When can this be resolved ? will it make it in time for JBIDE 3.2.1 (codefreeze on 30th May) ? (comment edited to correct the date :) was (Author: maxandersen): When can this be resolved ? will it make it in time for JBIDE 3.2.1 (codefreeze on 30th June) ? > Change the ModeShape Eclipse plugin to enable resource versioning in the repository. > ------------------------------------------------------------------------------------ > > Key: JBIDE-8242 > URL: https://issues.jboss.org/browse/JBIDE-8242 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: modeshape > Affects Versions: 3.2.0.Beta2 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 3.2.1.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Based on MODE-1027, the Eclipse plugin needs to be changed to enable versioning of resouces in the repository. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-8242) Change the ModeShape Eclipse plugin to enable resource versioning in the repository.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8242?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8242: -------------------------------------------- When can this be resolved ? will it make it in time for JBIDE 3.2.1 (codefreeze on 30th June) ? > Change the ModeShape Eclipse plugin to enable resource versioning in the repository. > ------------------------------------------------------------------------------------ > > Key: JBIDE-8242 > URL: https://issues.jboss.org/browse/JBIDE-8242 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: modeshape > Affects Versions: 3.2.0.Beta2 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 3.2.1.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Based on MODE-1027, the Eclipse plugin needs to be changed to enable versioning of resouces in the repository. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBDS-1579) Give the Designer's .log file a real name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/JBDS-1579?page=com.atlassian.jira.plugin.... ] Barry LaFond resolved JBDS-1579. -------------------------------- Assignee: Barry LaFond (was: Dan Florian) Resolution: Rejected The .log file in question is a standard Eclipse output log file. Will not fix. > Give the Designer's .log file a real name > ----------------------------------------- > > Key: JBDS-1579 > URL: https://issues.jboss.org/browse/JBDS-1579 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Environment: All > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 4.1.0.CR1, LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > (I called this a Feature since it's been this way for years and we've not recorded it as a defect before. However, Bernd Groh pointed out this issue, so I'm recording it on his behalf.) > The MetaMatrix and Teiid Designers have always created a .log file in the .metadata directory. The name is not easy to find and is a nuisance to use (for example, when attaching the log file to an email message). > Please incorporate a "real" name, like "designer.log". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-8992) [Runtime Detection] Servers are created to deploy to jboss folder by default

by Libor Zoubek (JIRA)

[Runtime Detection] Servers are created to deploy to jboss folder by default ---------------------------------------------------------------------------- Key: JBIDE-8992 URL: https://issues.jboss.org/browse/JBIDE-8992 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.2.1.CR1 Reporter: Libor Zoubek Assignee: Snjezana Peco I think this is a bug. By default server should be setup to deploy to workspace. Or at least it should be setup same way like when I add the runtime by hand. If I add server the old way (adding server + runtime by hand) I have server configured to deploy to workspace. This issue should be fixed for other server types/versions too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Resolved: (JBIDE-8453) Richfaces 4 new tag names not compatible with JBoss Tools

by Denis Maliarevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8453?page=com.atlassian.jira.plugin... ] Denis Maliarevich resolved JBIDE-8453. -------------------------------------- Resolution: Done Resolved. > Richfaces 4 new tag names not compatible with JBoss Tools > --------------------------------------------------------- > > Key: JBIDE-8453 > URL: https://issues.jboss.org/browse/JBIDE-8453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Visual Page Editor Templates > Affects Versions: 3.2.0.CR1 > Environment: Tomcat 7.0.8/ Mojarra 2.0.4 > Reporter: Flávio Henrique > Assignee: Denis Maliarevich > Priority: Minor > Fix For: 3.2.1.CR1, 3.3.0.M2 > > > This tag names has changed in Richfaces 4: > toolBar -> RF4: toolbar > toolBarGroup -> RF4: toolbarGroup > toolTip -> RF4: tooltip > Maybe more, so far I found only these. > The change is fine, but brought some problens in a IDE environment and in migration: > 1 - you can still use the old name in JBoss Tools, but the IDE can´t detected that this is wrong for RF4; > 2 - JBoss Tools can only render the preview for the old tag name not for the new tag name; > 3 - this can lead to mistakes for people migratin from 3.X branch like me. > Since JBoss Tools 3.2 CR1 is out, it would be nice that CR2 has the ability to handle this changes. I first post this here, because I don´t know if RF team will take another action to solve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-8931) Searching for runtimes dialog incorrectly resizes

by Libor Zoubek (JIRA)

Searching for runtimes dialog incorrectly resizes ------------------------------------------------- Key: JBIDE-8931 URL: https://issues.jboss.org/browse/JBIDE-8931 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.2.1.M1 Reporter: Libor Zoubek Assignee: Snjezana Peco Attachments: 2011-05-11-135833.png -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8128) [JBossTools Runtimes] Allow user to select what runtime types to be added

by Libor Zoubek (JIRA)

[JBossTools Runtimes] Allow user to select what runtime types to be added -------------------------------------------------------------------------- Key: JBIDE-8128 URL: https://issues.jboss.org/browse/JBIDE-8128 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, integration Affects Versions: 3.2.0.CR1 Reporter: Libor Zoubek Assignee: Rob Stryker If user searches for a runtime(s) he adds folder wich contains typically EAP or SOA. But EAP or SOA contains several runtimes, which are added if user decides to add the runtime as whole. Runtimes that will be added are printed in description section. User shlould have the right to decide what runtimes will be added. I suggest to display found runtime as tree with checkboxes. For example SOA runtime should look like: - /opt/soa-5.0 |- Server runtime 5.0 |- Drools 5.1 |- Seam 2.2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
9
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 May 2011