Glad to hear there's interest. Actually I've already done the work if it can be called that. There was nothing more to it than moving jdom-contrib, jdom-src and jdom-test into a common parent (jdom), moving src/* to src/main/java inside each, and writing four simple poms for each folder. Didn't chase any corner cases but the simple pom was all I needed to feel right at home.<div>
<br></div><div>Absolutely right about maven as cross-IDE representation. I sincerely encourage using it. If I can help with the learning curve, just ask. Maven is simpler than it seems at first.</div><div><br></div><div>
Let me know if you want the changes.<br>
<br><div class="gmail_quote">On Mon, Aug 8, 2011 at 12:23 PM, Joe Bowbeer <span dir="ltr"><<a href="mailto:joe.bowbeer@gmail.com">joe.bowbeer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I've been switching over to maven for my cross-IDE projects recently, and in fact was just converting some of mine from native NetBeans projects to Maven projects -- which is the only cross-IDE project representation that I'm aware of. (Maven projects are the easiest for everyone to consume, assuming that everyone is using different IDEs or the command line.)<br>
<br><div>That said, I build jdom extremely rarely, so I have no case of my own.</div><div><br><div class="gmail_quote">On Mon, Aug 8, 2011 at 7:12 AM, Rolf wrote:<div><div></div><div class="h5"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi Paul.<br>
<br>
Couple of things.... I've found that git's 'mv' tracking is somewhat<br>
problematic, it's not as easy to track an item's history than before the<br>
move.... you have to specify --follow for the 'git log' request.<br>
<br>
Neither eclipse nor github appear to apply the --follow logic to the moved<br>
files' history... It would be nicer if they did, since all the classes have<br>
moved once already (jdom -> jdom2).<br>
<br>
I acknowledge that the current system of dumping the supporting jars in<br>
the repo is 'crude', but, it has some other advantages. Having everyone<br>
using the same jar versions for the JDOM2 development would reduce the<br>
number of 'head-scratching' problems. This is up for discussion, but it<br>
seems that eliminating inconsistencies at this point in the development<br>
would be useful.<br>
<br>
Finally, I am in the habit of using ant and eclipse (call me 'old<br>
fashioned'), and I have the habit of throwing in an 'eclipse' target for<br>
ant build.xml files. I have added this target to the jdom build file.<br>
<br>
Running 'ant eclipse' and refreshing your eclipse project (f5) will set<br>
up/update your eclipse source folders, and library dependencies in a way<br>
that makes it all 'just work'.<br>
<br>
I normally have a 'smarter' eclipse target that uses the ant classpath to<br>
set up eclipse, but, in this case, I have it hard-coded at the moment. I<br>
see that it's missing the xml-apis.jar file, so it needs an update anyway.<br>
I'll make it dynamic based on the ant compile classpath instead.<br>
<br>
Obviously the demand for 'Mavenization' is growing... perhaps the most<br>
important question is 'how important' is it? I have always worked in an<br>
environment where build dependencies are more tightly controlled than what<br>
maven would allow, and the dependency-loading nature of maven would be<br>
'wrong'.<br>
<br>
If you can make a convincing argument to 'Mavenize' then the actual commit<br>
process would have to be very tightly coordinated, and it would interrupt<br>
the actual JDOM2 coding as things stabilize. Further, it would also benefit<br>
from having the comprehensive unit testing in order to confirm that nothing<br>
has broken in 'the wash'.<br>
<br>
As for a full Maven re-structure, I am hesitant... and I think Jason will<br>
have to weigh in with the final word on that. It's more far-reaching than<br>
just JDOM2...<br>
<br>
Rolf<br>
<br>
On Mon, 8 Aug 2011 15:25:31 +0200, Paul Libbrecht <<a href="mailto:paul@hoplahup.net" target="_blank">paul@hoplahup.net</a>><br>
wrote:<br>
> I think Brad's offer was to do it.<br>
> It does involve an amount of move around but it brings a few advantages<br>
> for people to take things up.<br>
><br>
> Except for being able to transparently depend on jdom if it makes its<br>
way<br>
> into the maven repo (that's somewhat further), it allows to open in<br>
Eclipse<br>
> and IntelliJ IDEA directly, classpath and sourcepath all set.<br>
><br>
> Brad, have you tried using the IntelliJ IDEA or Eclipse git checkout<br>
> methods (IntelliJ had me locate a Git executable which I had to<br>
download,<br>
> about 3 minutes)? If using this rearranging there will then nicely keep<br>
> history the same way an svn mv would do.<br>
><br>
> paul<br>
><br>
> Le 8 août 2011 à 14:52, jdom a écrit :<br>
<div>><br>
>><br>
>> Hi Brad<br>
>><br>
>> In the short term it is unlikely that the JDOM repo will be converted<br>
to<br>
>> a<br>
>> maven-style build. I simply do not use maven at all, and I do not know<br>
>> the<br>
>> maven 'paradigm'.<br>
>><br>
>> I know that the possibility is there to produe the maven co-ordinates<br>
for<br>
>> the JDOM releases, but it woul dmake sense to first get something<br>
usable<br>
>> out of JDOM2 before we go publishing it as a maven resource.<br>
>><br>
>> Bottom line is that, if it happens, it will be one of the last things<br>
to<br>
>> go through. Probably only after the alpha/beta/final stages of JDOM2<br>
are<br>
>> settled.<br>
>><br>
>> Still, JDOM is all about 'Java manipulation of XML made easy', so, it<br>
>> should be considered, and I've updated the wiki page<br>
>> <a href="https://github.com/hunterhacker/jdom/wiki/JDOM-2.0" target="_blank">https://github.com/hunterhacker/jdom/wiki/JDOM-2.0</a> to reflect that<br>
Maven<br>
>> artifacts should be a possible goal of JDOM2.<br>
>><br>
>> Pleased to see the mounting excitement for JDOM2.<br>
>><br>
>> Rolf<br>
>><br><br></div></blockquote></div></div></div></div>
<br>_______________________________________________<br>
To control your jdom-interest membership:<br>
<a href="http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com" target="_blank">http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com</a><br></blockquote></div><br><br clear="all"><br>
-- <br>Cell: 703-594-1883<br>Blog: <a href="http://bradjcox.blogspot.com">http://bradjcox.blogspot.com</a><br>Web: <a href="http://virtualschool.edu">http://virtualschool.edu</a><br>Manassas VA 20111<br><br>
</div>