chicken and egg

[Charles Tassoni]

     I've got a chicken-and-egg problem.  I need to declare the jars 
created by my project inside project.xml-- otherwise I couldn't use maven to 
distribute them to the necessary ears, wars, etc.  And that means that when 
I build maven will load earlier versions of my jars into the repository, and 
that maven will include those jars in the classpath during compilation of my 
project.
    Sounds innocous, but now I'm building new jars based on outdated 
versions of those very same jars.  And it can happen that an incosistency 
between my project's jars in the repository and my current source can cause 
compilation to fail.  For example, sometime after my last build I moved one 
particular class into a different package.  Then, when it came time for the 
next production build, the now outdated project jars in the repository 
became part of the classpath, and compilation failed because the compiler 
still expected my class to be in the old package.
    This must be a fairly general problem.  Does anyone know what the 
solution is?

_________________________________________________________________
Worried about inbox overload? Get MSN Extra Storage now!  
http://join.msn.com/?PAGE=features/es

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]