February 2012 - jbosstools-issues

[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-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

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

6
11
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, 10 months

13
27
0 / 0

[JBoss JIRA] Created: (JBIDE-8413) Savara->Generate->WSDL action does nothing when invoked on Choreography Description file (.cdm)

by Denis Golovin (JIRA)

Savara->Generate->WSDL action does nothing when invoked on Choreography Description file (.cdm) ----------------------------------------------------------------------------------------------- Key: JBIDE-8413 URL: https://issues.jboss.org/browse/JBIDE-8413 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Denis Golovin Only warnings reported in console: {noformat} Feb 11, 2011 1:45:12 PM org.pi4soa.common.util.PropertyUtil loadXML INFO: Located pi4soa XML configuration Feb 11, 2011 1:45:12 PM org.pi4soa.cdl.interfaces.InterfaceFactory <clinit> WARNING: Failed to find interface introspector: org.pi4soa.wsdl.interfaces.WSDLInterfaceIntrospector {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8415) Savara Preferences Page layout impovements

by Denis Golovin (JIRA)

Savara Preferences Page layout impovements ------------------------------------------- Key: JBIDE-8415 URL: https://issues.jboss.org/browse/JBIDE-8415 Project: Tools (JBoss Tools) Issue Type: Bug Components: Savara Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Attachments: screenshot15.png !screenshot15.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
12
0 / 0

[JBoss JIRA] (JBIDE-10363) Materialize Library : Remove the gradle nature when materializing com.springsource.sts.gradle.classpathcontainer

by Fred Bricon (Created) (JIRA)

Materialize Library : Remove the gradle nature when materializing com.springsource.sts.gradle.classpathcontainer ---------------------------------------------------------------------------------------------------------------- Key: JBIDE-10363 URL: https://issues.jboss.org/browse/JBIDE-10363 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common/jst/core Affects Versions: 3.3.0.M5 Environment: STS 2.8.1 Reporter: Fred Bricon Assignee: Alexey Kazakov Priority: Minor Fix For: 3.3.0.Beta1 Materializing the Gradle Library works fine, but we'd need to also remove the gradle nature and display a warning when doing so (similar to what we do with [Maven|JBIDE-9878]). -- 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

4
5
0 / 0

[JBoss JIRA] (JBIDE-10930) For EAR projects, Run As > Run on Server should open the 1st webapp using the context root in application.xml

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-10930: ----------------------------------- Summary: For EAR projects, Run As > Run on Server should open the 1st webapp using the context root in application.xml Key: JBIDE-10930 URL: https://issues.jboss.org/browse/JBIDE-10930 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Fred Bricon Assignee: Rob Stryker Attachments: non.default.context.root.zip For EAR projects, Run As > Run on Server opens the webapp url using the context root defined on the webapp project, not the value of the context root in application.xml, which obviously leads to a 404 error page. {quote} (09:53:24) rawbdor: fbricon, EarArtifactAdapter (09:53:36) rawbdor: takes the first web project in the ear (09:53:48) rawbdor: and simply returns whatever the web artifact adapter would do for that app {quote} When lauching, we could maybe use a IModuleArtifact decorator that provides the correct url to be opened in the browser? -- 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

4
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 February 2012