Hi.
>>> How do you think?
>>
>> I thinks its a normal practice to use "-parent" suffix.
>
> OK, so the proposal is "codemodel-parent", "codemodel", and
> "codemodel-annotation-compiler", right?
Yes, this looks fine.
>> Do I get it correctly that you're trying to move JAXB2 build onto
>> Maven2? This would be pretty cool. Let know if you need help.
>
> 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.
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