February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-12850. -------------------------------- Resolution: Done Resolving. Future work, if anything, can be done in JBIDE-13307. > Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream > ------------------------------------------------------------------------------------- > > Key: JBIDE-12850 > URL: https://issues.jboss.org/browse/JBIDE-12850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Labels: f2f2012 > Fix For: 4.1.x > > Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png > > > In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13307: ------------------------------------ 6 new flows set up: {code} (1) Base \-> (2) Forge|Freemarker|GWT (parallel) \-> (3) Server>(webtools.aggregate|WS|OS) (server first, rest in parallel) \-> (4) (Hibernate>BIRT)|(Xulrunner>VPE>JST) (two parallel series of builds) \-> (5) JavaEE>Portlet>Central (series) \-> (6) JBT.aggregate>(JBT.tests|JBDS) {code} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... Flow.1 is configured to run some time on Sat or Sun between midnight and 9am. The rest should cascade down in sequence. Results / progress can be seen from this view: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Set up the "All JBoss Tools" build+test > --------------------------------------- > > Key: JBIDE-13307 > URL: https://issues.jboss.org/browse/JBIDE-13307 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12850: ------------------------------------ 6 new flows set up: {code} (1) Base \-> (2) Forge|Freemarker|GWT (parallel) \-> (3) Server>(webtools.aggregate|WS|OS) (server first, rest in parallel) \-> (4) (Hibernate>BIRT)|(Xulrunner>VPE>JST) (two parallel series of builds) \-> (5) JavaEE>Portlet>Central (series) \-> (6) JBT.aggregate>(JBT.tests|JBDS) {code} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... Flow.1 is configured to run some time on Sat or Sun between midnight and 9am. The rest should cascade down in sequence. Results / progress can be seen from this view: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream > ------------------------------------------------------------------------------------- > > Key: JBIDE-12850 > URL: https://issues.jboss.org/browse/JBIDE-12850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Labels: f2f2012 > Fix For: 4.1.x > > Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png > > > In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13308) Remove cascading and rename trunk jobs to follow new naming scheme

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13308. -------------------------------- Resolution: Done Jobs refactored. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... for new job names. Cascading removed in all 4.1_trunk and 7.0_trunk (now _master or _trunk) jobs. Only linkages still set up are: * jbosstools-buildflow.X_master jobs, for X = 1..6 (see JBIDE-12850 or https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...) * jbosstools-cleanup -> devstudio-cleanup * jbosstools-install-grinder_master -> jbosstools-install-grinder.install-tests.matrix_master Note that devstudio jobs retain their _trunk suffix instead of _master as they still source from SVN. > Remove cascading and rename trunk jobs to follow new naming scheme > ------------------------------------------------------------------ > > Key: JBIDE-13308 > URL: https://issues.jboss.org/browse/JBIDE-13308 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > Unlink job by disabling cascading/blocked by upstream. That will make us able to het faster feedback and consume/depend on less Jenkins resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13475) Update/correct/fix tests in https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/esb/tests/org.jboss.tools.esb.ui.bot.test

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13475?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13475: ------------------------------------------- Looks fine to me. I'm not an expert on SWTBot either, but if these make the tests run better (i.e. more/better coverage) I'm all for it. > Update/correct/fix tests in https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/esb/test... > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13475 > URL: https://issues.jboss.org/browse/JBIDE-13475 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: esb > Affects Versions: 3.3.2.Final-SOA > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 3.3.3.Final-SOA > > Attachments: Editing.java.patch, ESBActionFactory.java.patch, ESBAllBotTests.java.patch, ESBListener.java.patch, NewProjectUsingBundledInSOA.java.patch, Notifier.java.patch, pom.xml.patch > > > The tests for https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/esb/test... > Require updates - they are currently failing on Jenkins: > http://machydra.brq.redhat.com:8080/job/esb.bot.tests.ldimaggi > The changes - see attached .patch files are: > M org.jboss.tools.esb.ui.bot.test/src/org/jboss/tools/esb/ui/bot/tests/Editing.java > ------> Added missing tests > M org.jboss.tools.esb.ui.bot.test/src/org/jboss/tools/esb/ui/bot/tests/editor/ESBActionFactory.java > ------> Added missing tests > M org.jboss.tools.esb.ui.bot.test/src/org/jboss/tools/esb/ui/bot/tests/editor/ESBListener.java > ------> Added missing tests > M org.jboss.tools.esb.ui.bot.test/src/org/jboss/tools/esb/ui/bot/tests/editor/action/Notifier.java > ------> Added missing tests > M org.jboss.tools.esb.ui.bot.test/src/org/jboss/tools/esb/ui/bot/tests/ESBAllBotTests.java > ------> Added missing test for creating project with embedded SOA server (JBDS-2394) > M org.jboss.tools.esb.ui.bot.test/src/org/jboss/tools/esb/ui/bot/tests/NewProjectUsingBundledInSOA.java > ------> Updated to reflect SOA 5.3 > M org.jboss.tools.esb.ui.bot.test/pom.xml > ------> Updated to download required runtimes (ESB/SOA) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13209) Need to add ESB 4.12 option with constraints

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13209?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-13209. -------------------------------- Verified in the January 28 build http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > Need to add ESB 4.12 option with constraints > -------------------------------------------- > > Key: JBIDE-13209 > URL: https://issues.jboss.org/browse/JBIDE-13209 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: esb > Reporter: Tom Cunningham > Assignee: Brian Fitzpatrick > Fix For: 3.3.2, 4.1.0.Alpha1, 4.0.x > > Attachments: JBIDE-13209.patch > > > SOA-P 5.3.1 is coming out soon and will require an ESB "4.12" option to be added to the ESB versions. > Additionally, it may or may not have a new jUDDI version, which would require a different constraint to verify the AS has ESB 4.12 - or a removal of the constraints altogether. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13328) as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8, 4, 9, 4.10, 4.11, 4.12

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13328?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-13328. -------------------------------- Verified in the January 28 build http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to... > as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12 > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13328 > URL: https://issues.jboss.org/browse/JBIDE-13328 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > > The following JIRAs showcase how ass-backwards the implementation of ESB detection/support in as.core's plugin.xml is: > JBIDE-13209 > JBDS-2365 > JBDS-2394 > JBDS-1889 > JBDS-2431 > Would it be possible to have the various servers simply support 4.x instead of needing to keep updating as.core's plugin.xml every time a new version of ESB 4.x comes out? (4.11 is currently not supported properly, and 4.12 is forthcoming. Can we make this better in JBDS 7, then maybe backport that magic to JBDS 5 and 6? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2446) ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2446?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2446: ------------------------------- Summary: ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS (was: ESB Editor removes "http-client-property" property) > ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2446 > URL: https://issues.jboss.org/browse/JBDS-2446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.GA-SOA > Environment: RHEL 6.1 > java version "1.6.0_25" > SOA-P 5.0 > Reporter: William Siqueira > Assignee: Douglas Palmer > Priority: Critical > > When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way. > When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"> > <http-client-property name="file" value="httpclient.properties" /> > </property> > </action> > </actions> > </service> > </services> > </jbossesb> > Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited) > <?xml version="1.0"?> > <jbossesb parameterReloadSecs="5" > xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> > <services> > <service category="c1" description="d1" name="s1-edited"> > <actions> > <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> > <property name="wsdl" value="someWsdl"/> > <property name="SOAPAction" value="noAction"/> > <property name="endpointUrl" value="http://host/servername"/> > </action> > </actions> > </service> > </services> > </jbossesb> > One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13336: ------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.1.x) > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13336. -------------------------------- Resolution: Done > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
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 2013