Gregory Kick wrote:
> I'd like to first say thanks for including me in this project. I
> just moved from L.A. to Chicago this past weekend so I haven't been
> doing much work, but I'm excited to get JAXB building with Maven.
Thank you very much for your help. Welcome onboard!
> My plan is to create a branch in cvs and just start rearranging the
> project structure, creating poms and creating plugins until it
> works. As Kohsuke suggested, I'll start with some of the smaller
> projects and build upwards.
Sounds good to me. Generally speaking, the only thing I'd caution
against is to shuffle the directory layouts, especially on CVS
repositories. We'll have to maintain branches for some time to come (for
JavaSE6), and as much as we like $HOME/src/java, it's just too painful
if you think about merging changes between branches.
I think the first candidate should be codemodel.
I'd like to first move codemodel to
http://codemodel.dev.java.net/ from
jaxb2-sources.dev.java.net
This subversion repository has been created some time ago, and there was
initial sync. I just copied over the source from the 2.1 branch to this
new module. It even has some preliminary Maven1 POM.
Codemodel has been fairly quiet for the past few months (just 2 commits
in the past 2 months), so I think we should be able to handle the
transition painlessly.
We also probably need a maven plugin to invoke the annotation compiler
(and we'll want to keep Ant version since this is used in other projects
that are still building on Ant.)
Once we have a working codeoodel maven build, we can kill codemodel
portion from the JAXB RI (And I love deleting code!)
There are some other Sun projects that are building the whole RI from
scratch, so I think this would be also a good way to get them exposed to
Maven, to make sure they are ready for a bigger change.
Anyway, please take a look at codemodel.dev.java.net svn repository. You
should already have a committer access. Feel free to play in the trunk.
> The ultimate goal would be a full maven-based build system in order
> to simplify deployment (both independently and to maven repositories)
> and dependency management.
Yep. This would also has the nice effect of allowing people to use any
IDE they like. It would also be a good way to get various Sun
infrastructure updated to work better with Maven.
> Anyway, I hope to really start working on it towards the end of the
> week and would appreciate any input from the developers that are
> experienced with the jaxb architecture ( i am but a lowly user :-) )
> and the current build process.
I think codemodel build is straightforward enough. We'll deal with
bigger beasts later, one at a time...
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com