StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>What I want to do is specify in my ivy.xml for each project that the Javadoc is published at some URL.</p> </blockquote> <p>I guess you should publish Javadoc's as any other artifacts and specify search pattern in ivysettings.xml. Example:</p> <pre><code><resolvers> <url name="repository"> <ivy pattern="${repository.url}/[module]/ivy-[revision].xml" /> <artifact pattern="${repository.url}/[module]/[artifact]-[revision].[ext]" /> <artifact pattern="${repository.url}/[module]/[artifact]-javadoc-[revision].[ext]" /> </filesystem> </resolvers> </code></pre> <blockquote> <p>In the end, I want the following: Project A has javadoc publish at <a href="http://someurl/A/javadoc" rel="nofollow">http://someurl/A/javadoc</a> Project B is dependent on A and it's javadoc is published at <a href="http://someurl/B/javadoc" rel="nofollow">http://someurl/B/javadoc</a> In Project B's javadoc where is use classes from Project A, I want it to link to the Project A url.</p> </blockquote> <p>As far as you publish Javadoc as artifact, it has its own ivy.xml and you can declare dependency here:</p> <pre><code><ivy-module version="2.0"> <info organisation="yourorg" module="moduleB-javadoc" /> <dependencies> <dependency org="yourorg" name="moduleA-javadoc" /> </dependencies> </ivy-module> </code></pre> <blockquote> <p>In my dependent projects I want to have Ivy resolve that dependency and provide it to a javadoc command in ant as arguments for the subtask.</p> </blockquote> <p>Describe javadoc artifact as dependency in dependent project's ivy.xml, then specify in your build.xml that ant javadoc task depends on target that performs and manipulate javadoc jar as you want (for details see ant documentation).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload