Everybody,
Sorry about the slowness of the response... I've been traveling and
had to stop forwarding mailing lists to my blackberry because the
poor little thing got overwhelmed. :-) Anyway, on to the issues.
As far as the naming/directory structure goes, I modeled what I did
after the maven projects. For example, take a look at maven-script
(
http://svn.apache.org/viewvc/maven/components/trunk/maven-
script/ ). The maven-script project is a sub-project of maven and
maven-script-ant is a subproject of maven-script. Hence, codemodel-
annotation-compiler is named as a subproject of codemodel...
As far as the whole -parent suffix thing goes, I'm not a fan. I
think that it was something that was was created to appease the old
maven 1.x-style project inheritance which used a separate directory
(e.g. codemodel-annotation-compiler and codemodel-parent would be on
the same level). In fact, it looks like the maven people deprecated
it for 2.x in their own projects. And while there's nothing to say
that it's wrong to call the top-level directory codemodel-parent, it
seems awkward to me to have a codemodel directory under a codemodel-
parent directory given the naming convention that I just cited.
Finally, I chose codemodel-core because that suffix seems to be the
standard among active maven 2.x projects. (
http://mvnrepository.com/
search.html?query=-core ).
As far as the whole conversion process goes, I think that everybody's
on the same page with it. In fact, that's why I branched codemodel.
While I probably could have gotten away with doing the changes in the
trunk as Kohsuke originally suggested, I wanted to get a little
practice with the branching/merging so that the logistics of
converting the more sizable, more complex JAXB won't be an issue and
it can be done in one fell swoop.
Anyway, let me know what you guys think of all so that we can settle
it and maybe see if the results of this discussion can get pushed
into
http://maven.apache.org/guides/mini/guide-naming-conventions.html .
Gregory Kick
http://kickstyle.net/
p.s. I'm moving the mailing list over to gmail so I'll be a little
snappier in the responses. Sorry again.
On Oct 19, 2006, at 11:41 am, Kohsuke Kawaguchi wrote:
> 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