[jbosstools-issues] [JBoss JIRA] (JBIDE-10690) deprecate & remove all refs to ~/trunk/build/build.xml

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668817#comment-12668817 ] 

Mickael Istria commented on JBIDE-10690:
----------------------------------------

A better script would be:
{code}
if [ ! -d target/surefire-reports ]; then
   mkdir -p target/surefire-reports/
   touch target/surefire-reports/TEST-dummy.xml
fi
{code}
that would prevent all builds to become orange even when all tests pass. (build gets orange since JUnit plugin cannot parse TEST-dummy).

This approach (dummy file in fileset) is indeed even better if we want Blue builds.

About the debate Blue vs Orange, I tend to prefer Orange since a build that does not run tests is not stable.

I also created this request to Jenkins, since I think this issue is actually a limitation in Jenkins plugin: https://issues.jenkins-ci.org/browse/JENKINS-12815
                
> deprecate & remove all refs to ~/trunk/build/build.xml
> ------------------------------------------------------
>
>                 Key: JBIDE-10690
>                 URL: https://issues.jboss.org/browse/JBIDE-10690
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 3.3.0.Beta1
>
>
> Pretty sure this old ant script is no longer needed. It should be removed, albeit carefully.

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