[jbosstools-issues] [JBoss JIRA] (JBIDE-11714) Replace requirements folder & requirements bootstrap job by "self-hosted" content in pom.xml ?

Nick Boldt (JIRA) jira-events at lists.jboss.org
Fri May 11 14:07:17 EDT 2012


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

Nick Boldt commented on JBIDE-11714:
------------------------------------

Many of these runtime requirement builders use a shared script, only passing in different properties:

http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbeap/
http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbossas-4.2.3.GA/
http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbossas-7.1.1.Final/
etc.

Deviations from the "use generic/common downloader" approach are for the cases where a single req fetcher/builder is made to handle more than one download:

http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/soap/
http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/jbossas/

Or where the fetching process requires some special steps:

http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.0.1.GA/
http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.3.0/

Because of differences, I question the benefit to porting all this to maven simply so that a single component can bootstrap itself. This already happens via the test harness. If a requirements.properties file is found, those requirement builders fire locally, fetch what's needed, and the tests proceed. In Jenkins, however, they can benefit from a pre-bootstrapped cache of these files so the download's faster/easier.

Simply switching to maven to fetch zips (and unpack them)... what would the gain be? Sounds a bit like "I don't like American, let's speak English instead": same conversation, but with slightly different words. :)


                
> Replace requirements folder & requirements bootstrap job by "self-hosted" content in pom.xml ?
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-11714
>                 URL: https://issues.jboss.org/browse/JBIDE-11714
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Minor
>             Fix For: 3.3.0.CR1
>
>
> Currently, jobs depdend on the requirement folder to perform tests (requirement contains scripts aimed to retrieving runtimes for tests). Instead, we should think about creating a Maven Mojo or something more convenient so that test pom.xml could directly contain their setup.

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

        


More information about the jbosstools-issues mailing list