Rolf and Jason, I made a quick first pass at the 4 poms for your updated files. They're at the new dropbox address <a href="https://www.dropbox.com/home/jdom#:::66844801">https://www.dropbox.com/home/jdom#:::66844801</a><div>
<div><br></div><div>I copied them from the .zip file, not git. Couldn't make it work and only now see why. Should be clone, not pull. </div><div>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.</div>
<div><br></div><div>imac:Dropbox Brad$ git pull <a href="https://github.com/hunterhacker/jdom" target="_blank">https://github.com/hunterhacker/jdom</a> jdom<div>fatal: Not a git repository (or any of the parent directories): .git</div>
<div><br></div><div>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.</div>
<div><br></div><div>To try it out, type "mvn install" in the root. That works in the subdirs too and builds only that subdir.</div><div><br></div><div>Let me know if you want to go further with this.</div><div>
<br>
</div><div>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.</div><div><br></div><div><div>compile.core:</div><div> [javac] /Users/Brad/Dropbox/jdom/build.xml:196: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds</div>
<div> [javac] Compiling 62 source files to /Users/Brad/Dropbox/jdom/build/core</div><div> [javac] /Users/Brad/Dropbox/jdom/build/core/org/jdom2/adapters/JAXPDOMAdapter.java:97: warning: non-varargs call of varargs method with inexact argument type for last parameter;</div>
<div> [javac] cast to java.lang.Class for a varargs call</div><div> [javac] cast to java.lang.Class[] for a non-varargs call and to suppress this warning</div><div> [javac] factoryClass.getMethod("newInstance", null);</div>
<div> [javac] ^</div><div> [javac] /Users/Brad/Dropbox/jdom/build/core/org/jdom2/adapters/JAXPDOMAdapter.java:98: warning: non-varargs call of varargs method with inexact argument type for last parameter;</div>
</div><div><br></div><div>and so forth, 4-5 screenfulls.</div>
<br><div class="gmail_quote">On Wed, Sep 14, 2011 at 11:42 AM, Brad Cox <span dir="ltr"><<a href="mailto:bcox@virtualschool.edu" target="_blank">bcox@virtualschool.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div>On Wed, Sep 14, 2011 at 10:46 AM, Rolf <span dir="ltr"><<a href="mailto:jdom@tuis.net" target="_blank">jdom@tuis.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<ul><li>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: <a href="https://github.com/hunterhacker/jdom" target="_blank">https://github.com/<u></u>hunterhacker/jdom</a></li>
</ul></blockquote></div><div>Great! Will pull those tonight (don't have git at work) and retrofit the poms. </div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<ul><li>
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.</li>
</ul></blockquote></div><div>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</div>
<div>"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.</div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<ul><li>So, for 1.1.2 the goal is to do the minimal changes possible and yet still have a maven artifact at the end.</li></ul></blockquote></div><div>I'll take a shot at a no-impact pom tonight.</div><div> -- </div></div>
Cell: <a href="tel:703-594-1883" value="+17035941883" target="_blank">703-594-1883</a><br>
Blog: <a href="http://bradjcox.blogspot.com" target="_blank">http://bradjcox.blogspot.com</a><br>Web: <a href="http://virtualschool.edu" target="_blank">http://virtualschool.edu</a><br>Manassas VA 20111<br><br></blockquote>
</div><br>
</div>
</div>