ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <>
Subject [jira] Commented: (IVYDE-51) IvyDE doesn't set the ${basedir} property
Date Sun, 21 Sep 2008 21:53:44 GMT


Maarten Coene commented on IVYDE-51:

On a previous job, I had a configuration where it was possible for modules to have a "lib"
directory where they could add some kind of private libraries into.
Setting up a filesystemresolver in ant was pretty easy, the artifact pattern started with
However, with IvyDE this wasn't possible if there was more than 1 project in the workspace
with this setup, but I think IvyDE should support this in some way or the other...

If I understand correctly, with IVYDE-52 fixed, could I use "${user.dir}/lib" as artifact
pattern? If so, we can close this issue...

> IvyDE doesn't set the ${basedir} property
> -----------------------------------------
>                 Key: IVYDE-51
>                 URL:
>             Project: IvyDE
>          Issue Type: Improvement
>          Components: classpath container
>    Affects Versions: 2.0.0.alpha1
>            Reporter: Maarten Coene
> IvyDE doesn't specify the ${basedir} property when resolving the dependencies.
> This means that it's not possible to resolve jar files in a [project]/lib directory.
> For instance, the following resolver doesn't work:
> {code}
> <filesystem name="local-repository">
>       <artifact pattern="${ivy.project.dir}/lib/[artifact](-[revision]).[ext]" />
> </filesystem>
> {code}
> Maarten

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message