On Jul 6, 2006, at 7:14 PM, Matthew Inger wrote:
> I've begun migrating the ant-contrib code to subversion.
> It's been a while since I've had time to work on this stuff,
> but i'd like to start cleaning up the code, and addressing
> the open bugs.
> I've also rewritten the build scripts to be a bit simpler
> than they were, and have started using ivy for dependency
> management, though all the dependent libs are still checked
> into the repository, as they previously were.
Maven 2 addresses dependency analysis, plus provides documentation
generation, code metrics, etc. I don't think we can abandon Ant
builds (particularly for an Ant add it(, but creating a Maven 2 build
and rearranging the source tree to adhere to its standard layout and
then getting the Ant build in sync might be desirable.
> I'd also like to migrate the cpptasks project as well, but
> I'm not sure what kind of activity it has seen lately, and
> wanted to check with Curt, and others who might be actively
> working on the cpptasks.
If I have any uncommitted tweaks in my CVS, I can port them over the
Subversion fairly quickly. I had been hoping to move to Subversion,
but the SourceForge migration page had disabled the direct CVS to SVN
migration option. If you want to move the cpptasks code base over, I
would appreciate it.
> The trunk can be found at:
> Please let me know if this causes any problems.
I think that I would have inverted the trunk and ant-contrib and made
it /ant-contrib/ant-contrib/trunk and /ant-contrib/cpptasks/trunk,
since it is unlikely that the ant-contrib and cpptasks would be
branched or tagged together. Fortunately SVN makes it real easy to
rename or move directories. I'd suggest a layout like: