Hello,
I discovered some new blurring.
As I make heavy use of dynamic jarfile loading with my applications, I have to
rely on the values from jars Manifest.
At jar-creation I build a classpath from all dependencies and write that into
Manifest. So when I have to load that jar, I know the dependencies and can
resolve them.
Now I realized, that gradle renames the jarfiles after creation, when it is
referenced from another project. That results in incontinent filenames in the
Manifests classpath and in the library name from dependencies.
As I already wrote, the version is not respected in jarfiles, which are
referenced by other subprojects from the same project. So the libFW-Prj-1 has
an artifact of libFR-Prj-1.jar (and not as expected
libFW-Prj-1-0.1.215-20100328113340.jar). So the libFW-Prj-2 (which depends on
libFW-Prj-1) has an classpath entry of "lib/libFR-Prj-1.jar".
In the Application-1 project (another top-level project), that depends on that
both libraries, they come into play as libFR-Prj-1-0.1.215-20100328113340.jar
and libFR-Prj-2-0.1.215-20100328113340.jar, but the latter stil has the
Manifest classpath entry of libFR-Prj-1.jar, which now does not exists ...
Any idea, how I could solve that problem?
kind regards
Geronimo
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
