June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11033) Drools plugin uses deprecated hash symbol # for comments in newly created .drl files

by Jiri Svitak (JIRA)

Jiri Svitak created JBIDE-11033: ----------------------------------- Summary: Drools plugin uses deprecated hash symbol # for comments in newly created .drl files Key: JBIDE-11033 URL: https://issues.jboss.org/browse/JBIDE-11033 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Reporter: Jiri Svitak Assignee: Kris Verlaenen Eclipse plugin uses deprecated hash symbol # for comments in newly created .drl files. Setting # to be deprecated might cause large refactoring work in existing .drl files, because Eclipse plugin used this type of comment as a default setting. Newly created .drl file in Eclipse looks like this: #created on: Feb 22, 2012 package com.sample #list any import classes here. #declare any global variables here rule "Your First Rule" when #conditions then #actions end Users should now use // for single comments and /* */ for block comments. But Eclipse plugin should not confuse them with #. -- 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, 9 months

8
62
0 / 0

[JBoss JIRA] (JBIDE-10720) Include new Drools in JBT / JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10720: ---------------------------------- Summary: Include new Drools in JBT / JBDS Key: JBIDE-10720 URL: https://issues.jboss.org/browse/JBIDE-10720 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1 As discussed on today's call, it's time to move up from Drools 5.2 to something newer. We pull Drools tooling from upstream: https://repository.jboss.org/nexus/content/groups/public/org/drools/org.d... https://repository.jboss.org/nexus/content/groups/public/org/drools/org.d... via these jobs: http://hudson.qa.jboss.com/hudson/job/jbosstools-drools-5.2_trunk/ http://hudson.qa.jboss.com/hudson/job/jbosstools-drools-5.2_stable_branch/ which publish to the staging area: http://download.jboss.org/jbosstools/builds/staging/ Once there, it is composited into a site for JBoss Tools 3.3.trunk and 3.3.latest-stable-milestone: http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli... http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli... Then, from the composite, we build the JBT aggregate update site: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/... And the JBDS site: https://svn.jboss.org/repos/devstudio/trunk/product-soa/site/site.xml -- 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, 9 months

6
13
0 / 0

[JBoss JIRA] (JBDS-2183) EAP6 installed with JBDS should have "jboss-eap-6" in Servers view instead of "jboss-as"

by Denis Golovin (JIRA)

Denis Golovin created JBDS-2183: ----------------------------------- Summary: EAP6 installed with JBDS should have "jboss-eap-6" in Servers view instead of "jboss-as" Key: JBDS-2183 URL: https://issues.jboss.org/browse/JBDS-2183 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.CR1 Reporter: Denis Golovin Assignee: Snjezana Peco Fix For: 5.0.0.CR1 -- 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, 9 months

5
16
0 / 0

[JBoss JIRA] (JBIDE-11980) Wrong jBPM version in feature description

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11980: ------------------------------------ Summary: Wrong jBPM version in feature description Key: JBIDE-11980 URL: https://issues.jboss.org/browse/JBIDE-11980 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, jbpm Affects Versions: 3.3.0.Beta2-SOA Environment: JBDS 5.0.Beta3 + SOA-P beta2 Reporter: Jiri Peterka Assignee: Nick Boldt Fix For: 3.3.0.Beta3-SOA Attachments: jbpm3-jbpm4.png There is a wrong jBPM version in feature description, feature refers to jbpm3 and description for jbpm4, I guess it should be version 3 for all (see screenshot) -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] (JBDS-2124) CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2124?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-2124. ------------------------------ > CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null > ------------------------------------------------------------------------------------ > > Key: JBDS-2124 > URL: https://issues.jboss.org/browse/JBDS-2124 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.Beta1-SOA > Environment: JBDS 5.0 Beta 3 with SOA-tooling Beta 1 > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Blocker > Fix For: 5.0.0.Beta2-SOA > > > When I get to this step in the XML Data File import wizard (executed via the Consume Web Service action set, step generate relational models from WSDL), and I select a couple of attributes to be transformed into relational columns, I cannot proceed due to the wizard's claim that my xQuery is empty or null. > The source XML file is attached. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2124) CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null

by Paul Nittel (JIRA)

[ https://issues.jboss.org/browse/JBDS-2124?page=com.atlassian.jira.plugin.... ] Paul Nittel commented on JBDS-2124: ----------------------------------- This has been fixed and may be closed. > CLONE - XML Data File Import options: Have an xquery, but am told it's empty or null > ------------------------------------------------------------------------------------ > > Key: JBDS-2124 > URL: https://issues.jboss.org/browse/JBDS-2124 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.Beta1-SOA > Environment: JBDS 5.0 Beta 3 with SOA-tooling Beta 1 > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Blocker > Fix For: 5.0.0.Beta2-SOA > > > When I get to this step in the XML Data File import wizard (executed via the Consume Web Service action set, step generate relational models from WSDL), and I select a couple of attributes to be transformed into relational columns, I cannot proceed due to the wizard's claim that my xQuery is empty or null. > The source XML file is attached. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1886) "New JBoss ESB Runtime" dialog does not automatically select runtime version based on ESB install dir for ESB 4.10

by Len DiMaggio (Created) (JIRA)

"New JBoss ESB Runtime" dialog does not automatically select runtime version based on ESB install dir for ESB 4.10 ------------------------------------------------------------------------------------------------------------------ Key: JBDS-1886 URL: https://issues.jboss.org/browse/JBDS-1886 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 4.1.1.M2 Environment: Version: 4.1.1.M2 Build id: v20111006-0040-H1061-M2 Build date: 20111006-0040 Reporter: Len DiMaggio Fix For: LATER See attached screenshots - JBDS is not automatically discovering the version # based on the install dir for ESB 4.10 - but it does work for 4.9 [ldimaggi@ldimaggi ~]$ ll /jboss/local/book_downloads/jbossesb-4.10 total 40 -rw-r--r--. 1 ldimaggi ldimaggi 625 Jul 6 22:36 Contributors.txt drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Jul 6 22:36 docs drwxr-xr-x. 7 ldimaggi ldimaggi 4096 Jul 6 22:34 install drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Jul 6 22:34 javadocs drwxr-xr-x. 13 ldimaggi ldimaggi 12288 Jul 6 22:37 lib -rw-r--r--. 1 ldimaggi ldimaggi 583 Jul 6 22:36 README_FIRST.txt drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Jul 6 22:36 samples drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Jul 6 22:34 xml [ldimaggi@ldimaggi ~]$ ll /jboss/local/book_downloads/jbossesb-4.9 total 52 -rw-r--r--. 1 ldimaggi ldimaggi 625 Aug 9 2010 Contributors.txt drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Aug 9 2010 docs drwxr-xr-x. 6 ldimaggi ldimaggi 4096 Apr 14 21:16 install drwxr-xr-x. 4 ldimaggi ldimaggi 4096 Aug 9 2010 javadocs -rw-r--r--. 1 ldimaggi ldimaggi 8533 Aug 9 2010 JBossEULA.txt drwxr-xr-x. 13 ldimaggi ldimaggi 12288 Aug 9 2010 lib -rw-r--r--. 1 ldimaggi ldimaggi 583 Aug 9 2010 README_FIRST.txt drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Aug 9 2010 samples drwxr-xr-x. 3 ldimaggi ldimaggi 4096 Aug 9 2010 xml -- 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, 9 months

6
11
0 / 0

[JBoss JIRA] (JBDS-2125) http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta1.soa-tooling/ - includes reference to jBPM4

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2125: ---------------------------------- Summary: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta1.soa... - includes reference to jBPM4 Key: JBDS-2125 URL: https://issues.jboss.org/browse/JBDS-2125 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.Beta1-SOA Reporter: Len DiMaggio Assignee: Nick Boldt Priority: Blocker Fix For: 5.0.0.Beta1-SOA Attachments: Screenshot-1.png See the attached screenshot - the reference to jBPM4 should be removed. -- 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, 9 months

4
14
0 / 0

[JBoss JIRA] (JBIDE-10562) Unable to connect to the Teiid Server

by Pavol Srna (Created) (JIRA)

Unable to connect to the Teiid Server ------------------------------------- Key: JBIDE-10562 URL: https://issues.jboss.org/browse/JBIDE-10562 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.3.0.M5 Reporter: Pavol Srna Assignee: Barry LaFond Priority: Trivial Fix For: 3.3.0.M5 -- 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, 9 months

13
27
0 / 0

[JBoss JIRA] (JBDS-2095) ESB new project wizard is not recognizing defined Runtime Environments

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2095: ---------------------------------- Summary: ESB new project wizard is not recognizing defined Runtime Environments Key: JBDS-2095 URL: https://issues.jboss.org/browse/JBDS-2095 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.Beta3-SOA Environment: Version: 5.0.0.Beta3 Build id: v20120417-1223-H2024-Beta3 Build date: 20120417-1223 SOA "Abridged" installed from: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... Reporter: Len DiMaggio Assignee: Snjezana Peco Fix For: 5.0.0.Beta3-SOA Attachments: Runtime.png See attached screenshot and steps to reproduce. -- 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, 9 months

3
8
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 June 2012