May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11553) QualifiedNameEditor Should Propose Valid Qualified Names

by Dan Florian (JIRA)

Dan Florian created JBIDE-11553: ----------------------------------- Summary: QualifiedNameEditor Should Propose Valid Qualified Names Key: JBIDE-11553 URL: https://issues.jboss.org/browse/JBIDE-11553 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Affects Versions: 3.3.0.Beta3 Reporter: Dan Florian Assignee: Dan Florian Fix For: 3.3.0.Beta3 The QualifiedNameEditor is used in multiple places in support of the JCR CND editor. It would be nice if the user was offered valid proposals for the unqualified name. For instance, if a namespace prefix of "nt" was selected in the QualifiedNameEditor; then valid proposals would be "base", "unstructured", "hierachyNode", "file", etc. As the user typed in more characters the number of valid proposals would get smaller. Required types and super types are two places this would be very useful. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11095) Tracking Bug 797194 - Overriden Translator name is reset to original Traslator name when synchronize called

by Johnathon Lee (JIRA)

Johnathon Lee created JBIDE-11095: ------------------------------------- Summary: Tracking Bug 797194 - Overriden Translator name is reset to original Traslator name when synchronize called Key: JBIDE-11095 URL: https://issues.jboss.org/browse/JBIDE-11095 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.4.x Reporter: Johnathon Lee Assignee: Barry LaFond Overriden Translator name is reset to original Traslator name when synchronize called How reproducible: - create translator override in the vdb editor - change a model and save - in the vdb editor, sync all - the translator override is reset See Bug 797194 (https://bugzilla.redhat.com/show_bug.cgi?id=797194) for more details For Bug 786561 (https://bugzilla.redhat.com/show_bug.cgi?id=786561) a fix has been backported: Committed r2305 to https://svn.jboss.org/repos/tdesigner/branches/7.4.x -- 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, 10 months

5
5
0 / 0

[JBoss JIRA] (JBIDE-12056) Exception Adding/Editing Property Definition's Value Constraint In CND Editor

by Dan Florian (JIRA)

Dan Florian created JBIDE-12056: ----------------------------------- Summary: Exception Adding/Editing Property Definition's Value Constraint In CND Editor Key: JBIDE-12056 URL: https://issues.jboss.org/browse/JBIDE-12056 Project: Tools (JBoss Tools) Issue Type: Bug Components: modeshape Affects Versions: 3.3.0.Beta3 Reporter: Dan Florian Assignee: Dan Florian Priority: Critical Fix For: 3.3.0.CR1 In CND Editor, if you select a property in the Properties Section table, and double-click the table row or click the editor toolbar button, the Property Definition Editor dialog opens. In the property dialog, if you Add or Edit a value constraint, a Value Editor dialog is displayed. If the user types in the textfield an error occurs and the OK button can never be enabled. Here is the error from the log: java.lang.UnsupportedOperationException at java.util.AbstractList.add(AbstractList.java:131) at java.util.AbstractList.add(AbstractList.java:91) at org.jboss.tools.modeshape.jcr.ui.cnd.PropertyDialog$31$1.validate(PropertyDialog.java:1193) at org.jboss.tools.modeshape.jcr.ui.cnd.StringValueEditorDialog.updateState(StringValueEditorDialog.java:185) at org.jboss.tools.modeshape.jcr.ui.cnd.StringValueEditorDialog.handleValueChanged(StringValueEditorDialog.java:172) at org.jboss.tools.modeshape.jcr.ui.cnd.StringValueEditorDialog$1.modifyText(StringValueEditorDialog.java:149) -- 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, 10 months

5
10
0 / 0

[JBoss JIRA] (JBIDE-11533) include source plugins/features in aggregate sites

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11533: ---------------------------------- Summary: include source plugins/features in aggregate sites Key: JBIDE-11533 URL: https://issues.jboss.org/browse/JBIDE-11533 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.Beta1-SOA, 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1-SOA, 3.3.0.Beta3 http://download.jboss.org/jbosstools/updates/nightly/core/trunk/plugins/ has no source plugins. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/features/ has no source plugins. 1. Add the missing source features to the aggregate sites: core (site) soa-tooling (soa-site) webtools coretests soatests 2. Remove this folder and associated Jenkins job(s): ~/trunk/build/aggregate/site/sources/ 3. Add source features/plugins to JBDS sites too: product product-soa extras -- 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, 10 months

3
8
0 / 0

[JBoss JIRA] (JBDS-2007) set SOA Tooling jobs in _stable_branch to source from trunk, but build against Core from M5

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2007: -------------------------------- Summary: set SOA Tooling jobs in _stable_branch to source from trunk, but build against Core from M5 Key: JBDS-2007 URL: https://issues.jboss.org/browse/JBDS-2007 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, SOA Tooling / Platform Affects Versions: 5.0.0.SOA Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 5.0.0.SOA Here's a diff showing what you have to change to migrate the jobs over to the new mechanism (using M5 target platform, reqs mirror, JBT Core bits, and SOA Tooling sources/binaries from trunk). You'll want to do the same w/ the other 6 SOA Tooling component builds w/ _stable_branch in their name. And you'll want to ensure the Drools contribution is 5.3, not 5.2. {code} --- /qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2011-12-23_06-58-39/config.xml +++ /qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-09_10-03-09/config.xml @@ -7,13 +7,13 @@  <h2><a style="color:blue" href="http://download.jboss.org/jbosstools/builds/cascade/3.3.indigo... Job Cascade &amp; Results</a></h2>  -Currently building 3.3.0.M5</description> +Currently building 3.3.0.Beta1-pre</description> <logRotator> <daysToKeep>5</daysToKeep> <numToKeep>5</numToKeep> @@ -41,47 +41,47 @@ -q :: quieter output</pre> </description> - <defaultValue>clean install -B -U -fae -P hudson,jbosstools-nightly-staging-composite,local.site,local.composite -Dmaven.repo.local=${WORKSPACE}/m2-repository</defaultValue> + <defaultValue>clean install -B -U -fae -P hudson,jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site,local.composite -Dmaven.repo.local=${WORKSPACE}/m2-repository</defaultValue> </hudson.model.StringParameterDefinition> <hudson.model.ChoiceParameterDefinition> <name>RELEASE</name> @@ -71,77 +70,76 @@ <scm class="hudson.scm.SubversionSCM"> <locations> <hudson.scm.SubversionSCM_-ModuleLocation> - <remote>http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.0.M5/build</remote> + <remote>http://anonsvn.jboss.org/repos/jbosstools/trunk/build</remote> <local>sources</local> </hudson.scm.SubversionSCM_-ModuleLocation> </locations> @@ -88,94 +87,93 @@ </scm> <assignedNode>RHEL&&!ia64</assignedNode> <canRoam>false</canRoam> - <disabled>true</disabled> + <disabled>false</disabled> <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding> <blockBuildWhenUpstreamBuilding>true</blockBuildWhenUpstreamBuilding> <jdk>java16_default</jdk> @@ -107,112 +106,125 @@ <mavenName>maven-3.0.3</mavenName> <jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m</jvmOptions> <pom>aggregate/soa-site/pom.xml</pom> + <properties>BUILD_ALIAS=Beta1-pre + +# define correct URLs for upstream M5 bits +jbosstools-target-site=http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/latest/ +local.site=/home/hudson/static_build_env/jbds/target-platform_3.3.indigo/e371-wtp331.target/ +jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/ +local.composite=file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/3.3.indigo/ +jboss-requirements-composite-mirror=http://download.jboss.org/jbosstools/updates/indigo/SR1/ +jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ +jboss-requirements-composite-extras-mirror=http://download.jboss.org/jbosstools/updates/indigo/extras/SR1a/ + +# pull SOA Tooling bits from trunk instead of 3.3.indigo +jbosstools-nightly-staging-composite-soa-tooling=http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooling/trunk/ +jbosstools-nightly-soa-tooling=http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/</properties> <usePrivateRepository>false</usePrivateRepository> </hudson.tasks.Maven> <hudson.tasks.Shell> {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, 10 months

3
2
0 / 0

[JBoss JIRA] (JBDS-2000) JBDS does not party like it's...

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2000: -------------------------------- Summary: JBDS does not party like it's... Key: JBDS-2000 URL: https://issues.jboss.org/browse/JBDS-2000 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 5.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt See JIRA #. -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-11902) bpel build broken due to xmlunit dependency in new bot plugin

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11902: ---------------------------------- Summary: bpel build broken due to xmlunit dependency in new bot plugin Key: JBIDE-11902 URL: https://issues.jboss.org/browse/JBIDE-11902 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.3.0.Beta2-SOA Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta2-SOA Cannot build BPEL component due to new bot test plugin and its dependency on xmlunit. Simplest solution is to build an osgi plugin wrapper for xmlunit (as apodhrad has started) and to add that plugin to the tests/pom.xml; this is a stopgap to allow a quick Beta2 build to be achievable. However, a longer-term solution might be to depend directly on the maven artifact, eg by adding this to bpel/tests/org.jboss.tools.bpel.ui.bot.test/pom.xml: {code} + <dependencies> + <dependency> + <groupId>xmlunit</groupId> + <artifactId>xmlunit</artifactId> + <version>1.3</version> + <scope>test</scope> + </dependency> + </dependencies> {code} or else to provide this org.custommonkey.xmlunit plugin via a target platform or on the JBT composite requirements site. -- 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, 10 months

2
7
0 / 0

[JBoss JIRA] (JBIDE-11836) The autocomplete feature in the Drools eclipse plugin is broken

by Paul Ryan (JIRA)

Paul Ryan created JBIDE-11836: --------------------------------- Summary: The autocomplete feature in the Drools eclipse plugin is broken Key: JBIDE-11836 URL: https://issues.jboss.org/browse/JBIDE-11836 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.3.0.Beta2, 3.2.2.Final Environment: Multiple systems (windows, linux, os x) all with eclipse (indigo or helios) Reporter: Paul Ryan Assignee: Kris Verlaenen The drools auto-completion feature seems to have been disabled or is just no longer working. There is mail archives floating about around this you can see these at http://drools.46999.n3.nabble.com/rules-users-Eclipse-plugin-autocomplete.... For complex rule systems this integration needs to work to make drools a goto tool for development. -- 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, 10 months

5
19
0 / 0

[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, 10 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, 10 months

6
13
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 2012