[hibernate-dev] Maven is not foobar, just fybar

[Max Rydahl Andersen]

>> I took a look at hibernate3 head today because Chris was claiming mvn 
>> eclipse:eclipse were broken.
>>
>> The short answer to that is that yes - maybe, it actually works 
>> (except for some "funny" things)
>>
>> I've updated http://hibernate.org/422.html to describe the few things 
>> I had to do to get maven to work on my new machine;
>> and it worked pretty well.
>>
>> svn co hibernate3, mvn eclipse:eclipse and I was basically ready to roll.
>>
>> But I did find some issues here in no particular order:
>> Why is checkstyle_checks.xml put in resources and thus end up int the 
>> classpath ? Previously it was just in the root of hibernate dir.
> I'd ask why checkstyle_checks.xml is there at all ;)

for the checkstyle nazi ;)

>> Why is the etc directory not inside hibernate-core as something that 
>> is put on the project as a class directory ? With this setup you would 
>> have to change the generated ide configurations every time to include 
>> it on the classpath. Without it the tests and other thing that dpeends 
>> on log4j and a cfg.xml doesn't run.
> Because I don't want them on the classpath ;)  The are in *etc*; they 
> are simply that, "extras".

But I can't access them from inside eclipse and I can't add it to 
anything easily since mvn eclipse:eclipse will just overwrite it.

If they were inside hibernate-core it would be available.

>> Is ther no way to avoid having xml-api.jars and other 
>> not-always-relevant jars to be added to the classpath ?
> We probably could just remove them as we now require jdk >= 1.4

also an option ;)

>> The documentation/ is "annoying" since you can't have both the docs 
>> and the tutorial included in eclipse
> don't understand this one.  can you be more explicit?  documentation/ 
> itself is nothing more than an aggregation project: it aggregates 
> tutorial/ and manual/

hmm...let me take a second look ;)

/max