ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Updated: (IVYDE-153) Better support the resolve in workspace feature
Date Tue, 20 Jan 2009 16:30:59 GMT


Nicolas Lalevée updated IVYDE-153:

    Attachment: IVYDE-153-r736034.patch

Here is a patch that use most of the work done by Eugene Goldfarb (IVYDE-43). To avoid changing
user's ivysettings, I made IvyDE use this IvySettings:
    private class WorkspaceIvySettings extends IvySettings {
        public DependencyResolver getResolver(String resolverName) {
            DependencyResolver resolver = super.getResolver(resolverName);
            if (resolver == null) {
                Message.error("unknown resolver " + resolverName);
                return null;
            ChainResolver chain = new ChainResolver();
            chain.setName(javaProject.getElementName() + "-ivyde-workspace-chain-resolver");
            chain.add(new WorkspaceResolver(javaProject, this));
            return chain;

But apprently this is making some of my project failing to resolve existing artifacts. In
the Ivy console I see logged some:
==== sandbox-local: tried

But actually that file does exist... And if I remove the resolve in workspace option in that
project, so IvyDE will use normal IvySettings implementation, IvyDE successfully resolve the
dependencies, even the ojdbc5.
Some strange side effect is happening here...

> Better support the resolve in workspace feature
> -----------------------------------------------
>                 Key: IVYDE-153
>                 URL:
>             Project: IvyDE
>          Issue Type: Improvement
>    Affects Versions: 2.0.0.beta1
>            Reporter: Nicolas Lalevée
>             Fix For:
>         Attachments: IVYDE-153-r736034.patch
> Today the "resolve in workspace" feature is quite a work around: the resolve process
run against the real artifacts in the real repositories, and only after that the resolved
artifacts are maybe replaced by the project.
> Drawbacks:
> * the resolve can fail if the artifact is not build but the project exist
> * we have no control of when a project is included or not
> So what we need here is a specific implementation of Ivy's DependencyResolver managed
by IvyDE.

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

View raw message