Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.4.1, 2.0-RC2
-
None
-
None
-
Ivy 1.4.1 and 2.0.0-rc2, Windows, Ant 1.7.1
Description
Sometimes during publish stage you don't have all necessary artifacts you want to publish (i.e. test results); so you'll probably want to publish some dumb artifact and republish it when results are known. ivy:publish with conf attribute would work perfectly for this, but it has a drawback: if some dependent module already requested this conf, dumb artifact won't be updated in ivy cache dir after republishing. As a workaround you need to publish all your artifacts even if only one of them has been changed.