[ https://issues.jboss.org/browse/JBIDE-11677?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-11677:
------------------------------------
To help better track what needs to be kept...
https://docs.google.com/spreadsheet/ccc?key=0AmGcQy-AtllqdG9XWEYxaldRTnZM...
> clean up http://download.jboss.org/jbosstools/updates/requirements/ - move all the m2e children under the m2eclipse folder and ensure all links are correct
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11677
> URL: https://issues.jboss.org/browse/JBIDE-11677
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, maven, updatesite
> Affects Versions: 3.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.1.0.Alpha1
>
> Attachments: cleaning-up-m2e-stuff.png
>
>
> http://download.jboss.org/jbosstools/updates/requirements/ contains an increasingly long list of m2e-related builds. Let's clean that up a bit.
> 1. move all the m2e children under the m2eclipse folder
> 2. ensure all links are correct (from composite sites, build.xml files, jenkins jobs, etc.)
--
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
[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2437:
------------------------------------
Andrej - which version of the SOA tools did you install?
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBDS-2437
> URL: https://issues.jboss.org/browse/JBDS-2437
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.2.GA
> Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 5.0.2.GA
>
> Attachments: deploy_error.png
>
>
> Cannot deploy a bpel project.
--
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
[ https://issues.jboss.org/browse/JBDS-2284?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2284:
-------------------------------------
Right, that's strange. I only noticed because I was cleaning up my inbox and saw this JIRA and checked their website.
> Investigate use of Findbugs 2.0.2 (was 2.0.1) in JBoss Central
> ---------------------------------------------------------------
>
> Key: JBDS-2284
> URL: https://issues.jboss.org/browse/JBDS-2284
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, central
> Affects Versions: 6.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 6.0.0.Beta1
>
>
> Bits mirrored here:
> http://download.jboss.org/jbosstools/updates/requirements/findbugs/2.0.1....
--
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
[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13307:
------------------------------------
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin is way awesome. Not sure I see the value in the guard/rescue scenario for us, but defining retries, sequences, parallel branches, and being able to pass params between jobs? VERY COOL.
> 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: Max Rydahl Andersen
> 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
[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-12850:
-------------------------------
Summary: Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream (was: Investigate usage of Jenkins Build Pipeline for our build stream)
> 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
>
>
> 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