[
https://issues.apache.org/jira/browse/IVY-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yura Taras updated IVY-986:
---------------------------
Attachment: publish-with-conf-drawback.zip
Attached file contains sample 2-module projects. To reproduce a bug, do
following:
mod1> ant publish
It publishes dumb artifact for test configuration
mod2> ant use-test
It uses dumb artifact for test configuration:
[echo] Dumb test results
mod1> ant test
It publishes real test results
mod2> ant use-test
It still uses dumb artifact for test config:
[ivy-retrieve] 0 artifacts copied, 2 already retrieved (0kB/0ms)
[echo] Dumb test results
But I expect it to use real test results.
> When publishing only one configuration, it isn't updated in related modules
> ---------------------------------------------------------------------------
>
> Key: IVY-986
> URL: https://issues.apache.org/jira/browse/IVY-986
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 1.4.1, 2.0-RC2
> Environment: Ivy 1.4.1 and 2.0.0-rc2, Windows, Ant 1.7.1
> Reporter: Yura Taras
> Priority: Minor
> Attachments: publish-with-conf-drawback.zip
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
