Hi Mark,
I fixed this in the last WB release - I still need to update the readme:
The order is approx:
* release version-matrix
* release parent
* release api
* release spi
* release tck
etc.
On 23 Mar 2009, at 11:34, Mark Struberg wrote:
Hi!
Just a minor proposal to the current SVN topology:
Don't you think it's a good time to move the JSR-299 API out to an
own SVN module completely on it's own?
I suggest this, because currently one cannot simply build the parent
modules, but dig deeper and release the sub modules on it's own. You
will also experience problems if you try to release the current
module structure on a fresh system because of quasi cyclic
dependencies.
.) the tck/trunk/pom.xml cannot be built without the API from ri/trunk
.) the ri/trunk/pom.xml cannot be build without the TCK from tck/trunk
So why not move the JSR-299 API out to api/trunk or something?
The build order would then be
api/trunk/pom.xml
tck/trunk/pom.xml
ri/trunk/pom.xml
(haven't analysed where the test-harness fits into, but shouldn't be
a problem).
txs and LieGrue,
strub
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete