Circular dependencies in release

[pmuir]

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?

[pgier]

I don't think there is an easy solution.
You could just do part of the release manually, you should just have to update the info in and , and then use the release plugin for the rest.

If it's really a circular dependency, then maybe in the future you can factor out the parts that are causing the cycle. Maybe api should be separate?

[pmuir]

Thanks Paul, that was what I thought (feared) would be the case. I have to some refactor to the structure, so I'll incorporate these as well.