It looks like I'm going to have to write a custom Ivy resolver. I want to
consume modules that contain both a *.jar file and a *.src.zip file but
where the ivy.xml doesn't specify any publications. Unfortunately, these
modules are already published to a shared location and I can't just go and
blow
Just a thought... maybe instead you could write a resolver that contains a
nested, normal resolver, and applies a configured XLST stylesheet to all of
the ivy.xml files it downloads. Then what you want to do would be an easy
specific case.
-Archie
On Tue, Oct 18, 2011 at 12:27 PM, Mitch Gitman
Archie, thanks for the alternate approach. In case I still want to consider
the original approach--if anyone else knows about the particular place in
the code that I want to override, I'd love to hear.
Correction. I believe I meant ${ivy.module.name}.
Actually, this raises another question. How
Le 18 oct. 2011 à 23:00, Mitch Gitman a écrit :
Archie, thanks for the alternate approach. In case I still want to consider
the original approach--if anyone else knows about the particular place in
the code that I want to override, I'd love to hear.
Correction. I believe I meant
Great. Thanks, Nicolas.
Another IvyDE question comes up. There are some Ivy modules which I do
control, and those ones I'm trying to make more conventional, publishing a
*-source.jar artifact. Publish works fine. And I even make IvyDE resolve to
a special IvyDE-specific cache. And under that
Ah, I think I found a possible cause of my latest problem. I go to open up
the source JAR and all I see is .class files.
On Tue, Oct 18, 2011 at 3:01 PM, Mitch Gitman mgit...@gmail.com wrote:
Great. Thanks, Nicolas.
Another IvyDE question comes up. There are some Ivy modules which I do
