Well, this is about pulling down source JARs for existing artifacts,
so I'm not sure this applies.  Perhaps later, when I'm generating
artifacts via Ant/Ivy.

On Wed, Jun 4, 2008 at 6:54 AM, Loehr, Ruel <[EMAIL PROTECTED]> wrote:
> I'm not sure of the best practice, but one thing that you can do is create s 
> a conf called "src".
>
>
>    <configurations>
>        <conf name="src" description="artifacts"/>
>    </configurations>
>
> And then publish src artifacts to that configuration
>
>
>    <publications>
>        <artifact name="blogapp" type="zip" conf="src" ext="zip"/>
>    </publications>
>
> You could publish them directly into the same conf, but I don't like to do 
> that as I auto configure my classpath to point to the retrieve location.
>
> Welcome to ivy.   You'll never look to m2 again.
>
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 03, 2008 7:48 PM
> To: Ant Users List
> Subject: Ivy [2.0-beta-2]: Download Source Jars
>
> I'm just getting started with Ivy, but one thing that is very
> important for me is to easily download source JARs where available.
>
> <ivy-module version="2.0">
>    <info organisation="com.nfjs.hls" module="blogapp"/>
>    <configurations>
>        <conf name="runtime" description="Dependencies needed at runtime."/>
>    </configurations>
>    <publications>
>        <artifact name="blogapp" type="war" conf="runtime" ext="war"/>
>    </publications>
>    <dependencies>
>        <dependency org="org.apache.tapestry" name="tapestry-core"
> rev="5.0.11" conf="runtime->default">
>            <exclude module="servlet-api"/>
>        </dependency>
>    </dependencies>
> </ivy-module>
>
>
> <project xmlns:ivy="antlib:org.apache.ivy.ant" name="blogapp">
>
>    <target name="-ivy-setup">
>        <ivy:settings file="ivysettings.xml"/>
>    </target>
>
>    <target name="update-libs" depends="-ivy-setup"
> description="Download external library dependencies">
>        <ivy:retrieve sync="true"
> pattern="${ivy.lib.dir}/[conf]-[type]s/[artifact]-[revision].[ext]"
> type="jar,source"/>
>    </target>
>
>
> </project>
>
> This runs and places my expected dependencies in lib/runtime-jars/ as
> I want them.
>
> However, there is no lib/runtime-sources folder.
>
> I get the same results if I omit the type attribute on <ivy:retrieve/>.
>
> How does Ivy associate an artifact with its source artifact?
>
> The things I'm downloading, tapestry JARs and such, all have source
> JARs (built and deployed via Maven).
>
> Thanks for any pointers,
>
> Howard
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to