[jbosstools-issues] [JBoss JIRA] (JBTIS-28) produce a JBTIS unit tests update site (aggregate or composite)

[Andrej Podhradsky (JIRA)]

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

Andrej Podhradsky commented on JBTIS-28:
----------------------------------------

Hi Nick, I had a look at it and found the following problems:

1. new soa feature are not built (commented out)
2. category.xml requires soa features, that's why old bpel test is used (1.2.100.Alpha1)
3. your script doesn't use profile 'soa' (see tests/pom.xml)

I tried to fix it, see https://github.com/apodhrad/jbosstools-integration-tests/compare/JBTIS-28?expand=1 (not merged yet because I'm not sure if it is correct)
but this fix counts with building soa features, so you need to add the profile 'soa' to your script.

In case we don't want to build also soa features, we need to edit category.xml file (I don't know to add soa feature only if soa profile is activated).

Question: does somebody know why old category.xml defined all features (forge.test.feature, bpel.test.feature, etc...)?
                
> produce a JBTIS unit tests update site (aggregate or composite)
> ---------------------------------------------------------------
>
>                 Key: JBTIS-28
>                 URL: https://issues.jboss.org/browse/JBTIS-28
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: distribution, ESB, releng, target-platform
>    Affects Versions: 4.0.0
>            Reporter: Nick Boldt
>             Fix For: 4.0.0
>
>
> JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
> However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example. 
> So, either you 
> * need to publish a site from which these can be resolved [1]
> ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
> * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
> ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
> [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
> [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbosstools/site/compositeArtifacts.xml
> [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/ 
> [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbosstools/site/ is 404'd
> Both options would work... but I suggest that building a new aggregate might be better.
> If you agree, you'll want to therefore migrate the code in 
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/soatests-site 
> to a folder under
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jbosstools/

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