Jean-Sebastien Delfino wrote:
Simon Laws wrote:
I'm putting Sebastien's ant file generator into the build. The snag is
that
it builds ant files based on dependencies it finds at the module
level. We
ship a release excluding all but the latest level of dependencies.
Hence the
ant file may be looking for dependencies that we don't ship. My first
port
of call here is to look across the project and see if we can
rationalize our
dependencies so that the modules are looking for the latest version.
Failing
that we will have to have some kind of lookup that maps to the latest
version for each jar. I'm raising it here in the off chance that
someone has
already thought about this and knows a neat solution.
Regards
Simon
Happy new year.
I can try to help fix the problem, once I understand it. Can you point
me to a module and steps to reproduce it?
Thanks.
Have looked into it today, and still do not understand what you meant,
sorry :).
The Ant files are generated from the Maven POM model, which must be
referring to the correct dependencies otherwise our samples won't build
correctly with Maven. So I must be missing something...
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
