The documentation regarding the syntax of the - operator for conf mapping is
unnecessarily confusing and in fact contradicts itself. IMHO, it needs to
better define what it means by the master configuration and what is the
dependency configuration.
Documentation is located here and the relevent
Ok, after looking at it some more I think what that section needs is just a
subtle change to this sentence:
A good way to remember which side is for the master configuration (i.e. the
configuration of the module defining the dependency) and which side is for
the dependency configuration is to
Yeah, I think I am just reading it oddly. When you say The ivy file defining
the dependency you are meaning the ivy file where the relationship to the
dependency is defined whereas I was reading it as the ivy file defining the
artifact of the dependency (i.e. the other ivy.xml file).
I think
Cool... if someone read it wrong then by definition it's confusing and can
be improved.
-Archie
On Tue, May 4, 2010 at 4:33 PM, mjparme mjparme...@west.com wrote:
Yeah, I think I am just reading it oddly. When you say The ivy file
defining
the dependency you are meaning the ivy file where
The problem is that the word dependency is often used to mean
dependent module, i.e. the target of the dependency. For example
just yesterday there was build a dependency from source control,
which of course was about building a dependent module, not building
a dependency relationship.
I always
Niklas Matthies wrote:
The problem is that the word dependency is often used to mean
dependent module, i.e. the target of the dependency. For example
just yesterday there was build a dependency from source control,
which of course was about building a dependent module, not building
a dependency
Greetings all,
I am trying to run an XSLT transform on my ivy.xml file before publish.
Because of the metadata I am inserting, it must be after resolve and
build of the module, however.
From reading the documentation, it sounds like I need to manually run
the ivy:deliver task instead of
Hi All,
Just wondering has anyone use Ivy to resolve XSLT file dependency, and
generate the reports?
Say I have bunch of XSLT files, and one import the other one, and import
the other one. blah blah,
Can Ivy generate a report about these dependency?
I think Ivy needs to look at the tag:
If I understand you correctly, you're asking if Ivy can look at some
arbitrary XSLT files you've got, find the xsl:import/ elements, and
generate information about which files (or rather, which URIs) include
which other files?
If so, then no. This is not at all what Ivy does, and not what it
Thanks Michael. yes, that's what I want. I need something can generate a
XSLT dependency report for our project, because there are two many XSLT
files in our project. Sometimes, updated one file and forgot to update
the others causing a lot of issues
Hmm.. I saw the beautiful graph report
10 matches
Mail list logo
