I went through and made some minor changes to the build files so that they would work correctly when run from build.xml in the root directory. There were several relative path problems.
Also added build scripts. Got the tests all running, but there are several failing tests in the extensions, i18n, and naming sub-projects. cli and io both pass. 99% of the subproject build files are identical. I think this is what you were talking about below, but if is possible to combine these build files somehow that would be nice to do soonwhile they are still in synch. Cheers, Leif Peter Donald wrote: > Hi, > > Okay - almost finished reorganization basics. Heres how it looks (or will > look). Each product has its own hierarchy and can be built independently of > the main tree (except those products that have inter-dependencies). I have so > far converted across the cli, naming, i18n, io and extension components. I > did these as they are the ones I needed imediately ;) > > I would love it if other people could convert across other products as they > start to use them. If you want to keep the history of the product and don't > feel confident hacking CVS repository directly then feel free to ask me to do > it. Ideally all the examples would be moved into coresponding projects so > that we would have things like > > altprofile/examples/... > > etc. > > I would also appreciate keeping the same format for structure and build files > - at least as far as is possible. The reason is if you look at the build > files they are 90% identical. Long term I hope to use some form of templating > technology in combination with ant so that project files just look like > > <project name="cli" > package="org.apache.avalon.excalibur.cli" > dir="cli"> > > <src>src/java</src> > > <junit>src/test</junit> > > <rmic>org.apache.avalon.SomeObject</rmic> > > <xdocs>src/xdocs</xdocs> > > <depends> > <product name="xml-xerces"/> > <product name="jakarta-ant"/> > </depends> > > </project> > > This will make maintaining all the separate products much easier. There is > already an effort to do this at Apache for the turbine projects (look at > jakarta-turbine-mavern) but to be honest I haven't looked at it close enough > to asses if it will fit our needs. Hopefully it will or we can make it fit > our needs and thus all will be good. > > BTW the next gump will probably fail - ignore it for the time being ;) > > Things still to be done. > * add in readmes to different products and at least some minimal documentation > * add in building of xdocs for products > * convert the rest of the products > * suck products from other avalon CVS repos that should be in excalibur but > arent't (such as jmx stuff in phoenix). > * start documenting which release level of each component > * do a distribution of all the little products > > Feel free to jump in and do any of those things ;) > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
