[Design of JBoss Build System] - Circular dependencies in release
by pete.muir@jboss.org
I have an SVN structure like this:
ri/trunk/api
| ri/trunk/impl
| ri/trunk/dist
| ri/trunk/spi
|
| examples/trunk/...
|
| tck/trunk/api
| tck/trunk/impl
and also off in jbossas/projects
webbeans-ri-int/trunk/jbossas
| webbeans-ri-int/trunk/mc
| webbeans-ri-int/trunk/deployer
| webbeans-ri-int/trunk/ejb
| |
| | To release, I need to things in this order:
| |
| | * install a release of ri/trunk/api and ri/trunk/spi locally
| | * update to RI API and SPI version and install
| | * update to the above API version and install
| | * install a release of the RI locally
| | * update to RI API and tag examples
| | * tag tck
| | * tag ri-int
| | * do some more tags for modules without deps
| | * build dist and tag
| |
| | Now, if I did the release manually, this would be possible, but because the release plugin tags as I go, I don't see how to do this. Ideally, I want to use the release plugin to install locally only in the first 4 steps, and then go back and tag later.
| |
| | Any suggestions?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212456#4212456
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212456
15 years, 2 months