This brings in other configuration requirements.
e.g. the jbossportal federation only wants jbossas as binaries, whereas the
jbosscache federation wants it as source.
So we need a configuration option that makes this explicit:
| <project>
| <info id="portal"
| description="JBoss Portal"
| repository="http://repository.jboss.com"
| cvsroot="cvs.forge.jboss.com/cvsroot/portal"
| </info>
| <extends name="jbossas" type="binary"/>
| <component name="bb"/>
| <component name="wiki"/>
| etc.
| </project>
|
There are other requirements where the extension will be of mixed type,
e.g.
1) Portal wants to include the license information, docs from jbossas
2) Portal does not want to run all the unit tests for jbossas when they run
their unit tests
Getting more complicated, the custom cache federation will probably only
want to run tests for components where cache is actually used?
You could even imagine the cache project wanting to make a workspace
that "automagically" includes all the components/builds where the cache module is imported. Which would be good for cutting down the regression testing overhead
but would be bad for people "fixing" tests rather than fixing the problem.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878075#3878075
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878075
|
