i'll try looking into it again - but if they have
seperate source directories without a common root, i'll be sad ;)


Currently every plugin is self contained and has own
source tree. But nothing prevents you to specify
source directory somewhere else ( say, under hibernate
source roor like:

src/core
src/hbm2java

k - so where is my etc directory for the hbm2java directory ? which is different than the core ?


The "über" layout i'm looking for is:

hibernate/modules/core
hibernate/modules/core/etc
hibernate/modules/core/src/java

hibernate/modules/hbm2java
hibernate/modules/hbm2java/etc
hibernate/modules/hbm2java/src/java



I'm fully aware of this - to remedy this currently
look at the VERSIONS file - it should list the correct ones!


Yep. It does lists, bit how can I be sure that you
followed this in CVS? :)



As i said, it's a remedy - not a cure ;) (but if that is the case - then report it as a bug)


I have implemented my own "maven" like (long before
Maven) that
supports self dependent project (both with or
without a common root) and
they define dependencies and collect them from a
common repository.
Major difference between Maven and my "maven" is
that it does not just
get the .jar files - it also get EVERYTHING else,
configuration, src, doc, help, etc. etc. so I don't need to have my
seperate installation of
xerces docs or similar - they are all placed a
common place on our developers harddisk on a "need-to-use"-basis and
thus allow them to disconnect their portable from the network and have
a full working setup with docs, src etc. ....that leg (and more) is
missing in Maven (IMHO)


there are local repositories, offline builds, jar
overriding etc... After all it's just a question of
discipline :)

eh ? i don't want a system that is a .jar (or any other type of artifact centric) - I want a COMPLETE copy of the distribution when I do a
<depends>
<project name="xerces" version="1.4.3"/>
</depends>


I want the complete contents of xerces ....if I ONLY want a subset of the artifcats from xerces then I would do something like:

<depends>
 <project name="xerces" version="1.4.3">
  <artifact name="xerces-jar"/>
 </project>
</depends>

Which would give just the artifact related to the "xerces-jar" name, and it should place the artifacts the exact same place (path location) as where it would be if i got the whole distribution.....why ? simply so I should not need to change any references in my build scripts...(this is also solvable by using logic names (like ${xerces.jar.location}) in the build files)

Does Maven have this ?

Well, I think this about to go "off-topic" - so let's continue any talk "off the list", ok ? ;)

/max
regards,

=====
----[ Konstantin Pribluda ( ko5tik ) ]----------------
Zu Verstärkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] für die Festanstellung. Arbeitsort: Mainz Skills: Programieren, Kentnisse in OpenSource-Bereich
----[ http://www.pribluda.de ]------------------------


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com



------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to