[JBoss JIRA] (JBDS-1934) (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
by Paul Nittel (JIRA)
[ https://issues.jboss.org/browse/JBDS-1934?page=com.atlassian.jira.plugin.... ]
Paul Nittel commented on JBDS-1934:
-----------------------------------
Just tried it with JBDS 5.0 Beta 3 (H140 build) and it did NOT work as it should. Going to reopen.
Saved the transformation and the hint disappeared.
> (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1934
> URL: https://issues.jboss.org/browse/JBDS-1934
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform , teiid
> Affects Versions: 5.x
> Environment: JBoss Developer Studio 4.0
> JBoss Developer Studio 4.1
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 5.0.0.CR1-SOA
>
>
> /*+ cache */
> CREATE VIRTUAL PROCEDURE
> SELECT 'winning';
> BEGIN
> END
> The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation.
> com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314
> The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line:
> this.sqlText = sqlDisplayNode.toDisplayString();
--
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
[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
[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