[jdom-interest] JDOM2 Update - maven

Brad Cox bcox at virtualschool.edu
Wed Sep 14 14:37:37 PDT 2011

Rolf and Jason, I made a quick first pass at the 4 poms for your updated
files. They're at the new dropbox address

I copied them from the .zip file, not git. Couldn't make it work and only
now see why. Should be clone, not pull.
Hopefully the zip files will do. I didn't change anything except adding the
4 poms, so they should work if you need to move them elsewhere.

imac:Dropbox Brad$ git pull https://github.com/hunterhacker/jdom jdom
fatal: Not a git repository (or any of the parent directories): .git

The poms contain <sourceDirectory> commands to adapt to your source
conventions. However at this stage the build products aren't produced in
/jdom/build but in /jdom/subcomponent/target which is the maven convention.
I could match your build conventions too but that was more than I could
tackle tonight.

To try it out, type "mvn install" in the root. That works in the subdirs too
and builds only that subdir.

Let me know if you want to go further with this.

I did get some build errors with the ant build; I'm assuming they can be
ignored. (?) I don't know ant well enough to diagnose.

    [javac] /Users/Brad/Dropbox/jdom/build.xml:196: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set
to false for repeatable builds
    [javac] Compiling 62 source files to /Users/Brad/Dropbox/jdom/build/core
warning: non-varargs call of varargs method with inexact argument type for
last parameter;
    [javac] cast to java.lang.Class for a varargs call
    [javac] cast to java.lang.Class[] for a non-varargs call and to suppress
this warning
    [javac]                 factoryClass.getMethod("newInstance", null);
    [javac]                                                       ^
warning: non-varargs call of varargs method with inexact argument type for
last parameter;

and so forth, 4-5 screenfulls.

On Wed, Sep 14, 2011 at 11:42 AM, Brad Cox <bcox at virtualschool.edu> wrote:

> On Wed, Sep 14, 2011 at 10:46 AM, Rolf <jdom at tuis.net> wrote:
>>    - The setup we now have for JDOM (all versions) is now in github, and
>>    the three 'components' (core, test, contrib) are all in the same git
>>    repository: https://github.com/**hunterhacker/jdom<https://github.com/hunterhacker/jdom>
>> Great! Will pull those tonight (don't have git at work) and retrofit the
> poms.
>>    - The most immediate goal in applying maven is to get the 1.1.2 final
>>    build artifacts published on maven-central, and that source branch needs to
>>    be as stable as possible. Moving files (and especially renaming/moving
>>    directories) would be very, very disruptive to keeping a clean version
>>    history. We can be more liberal with those sorts of changes in the JDOM2
>>    branch if we need to.
>> Afraid that's the part I'd be of the least help with. No current
> experience with central repos, but doubt its hard to learn. But if you can
> scare up someone who's done it before, might be quicker to just stick with
> ant and save the build with mvn part for later. The existing 1.1 org.jdom
> release
> "SHOULDN'T" be a problem since you're using 1.1.2, but that's the kind of
> question I'd need to research too. Not been there so far.
>>    - So, for 1.1.2 the goal is to do the minimal changes possible and yet
>>    still have a maven artifact at the end.
>> I'll take a shot at a no-impact pom tonight.
>  --
> Cell: 703-594-1883
> Blog: http://bradjcox.blogspot.com
> Web: http://virtualschool.edu
> Manassas VA 20111
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.jdom.org/pipermail/jdom-interest/attachments/20110914/16e4cc7d/attachment.html>

More information about the jdom-interest mailing list