hdockter wrote:
>
> What you can do is something like (configure is a rather new
> convenience method in trunk):
>
> dependencies {
> addArtifacts('libs', configure(new DefaultPublishArtifact()) {
> name = 'mytaglib'
> extension = 'tld'
> type = 'tld'})
> }
>
> See http://gradle.org/api/latestlatest/org/gradle/api/
> DependencyManager.html and the methods getAbsoluteArtifactPattern,
> getDefaultArtifactPaterns and getArtifactParentDirs for telling Ivy
> where to look for artifacts.
>
Thanks.
hdockter wrote:
>
>>
>> BTW, how can I specify the configuration, in which the file will be
>> published (e.g. a source configuration for the published source code)?
>
> Could you explain this a little bit more?
>
See the following example of an ivy.xml:
<publications>
<artifact name="mySomething" type="jar" conf="master" />
<artifact name="mySomethingSecurity" type="jar" conf="security" />
<artifact name="mySomethingExtension" type="jar" conf="extension" />
<artifact name="myTags" type="tld" conf="tags" />
</publications>
This way whoever needs my module, can specify which configuration(s) he
needs and will get the appropriate jars (and other files).
--
View this message in context:
http://www.nabble.com/Upload-non-archive-artefacts--tp20455961p20497716.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
