Aleksei Valikov wrote:
>> Yes. We are trying to start with smaller sub-projects and gradually go
>> up the ladder to the JAXB RI.
>
> I'm not sure if it's the correct strategy.
> What I usually do when mavenizing is:
> 1. Define the master pom.xml for the whole project.
> 2. Defined the pom.xml for the sub-project, add this as module.
> 3. Make sure this works.
> 4. Go on with the further modules.
Ah, but the point is that codemodel is not a module of the JAXB RI, just
like xsom is not. They are really an independent library.
I agree with you that when it comes time to switch the JAXB RI project
itself, we need to convert the whole runtime, xjc, etc at once, not
individually.
> I prefer defining the dependencies (with version) in dependencyManagement of the
> parent pom. Modules then don't need to declare the versions, just
> groupId/artifactId.
>
> The biggest problems I had in my project when mavenizing were:
>
> 1. Figuring out correct versions of dependencies.
> 2. Finding out which artifacts should I use instead of my jars.
> www.mvnrepository.com was very helpful.
> 3. Restructuring directories (src -> src/main/java, src/main/resources) etc.
> 4. Sometimes I had to rework my approaches to unit testing.
>
> Bye.
> /lexi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: dev-help_at_jaxb.dev.java.net
>
>
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com