Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <1603295252.1256040479459.JavaMail.jira@brutus>
Date: Tue, 20 Oct 2009 12:07:59 +0000 (UTC)
From: "Jon Schneider (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Resolved: (IVYDE-202) Another method for adding IvyDE
 classpath container to the WTP dynamic module tree.
In-Reply-To: <720081792.1253125557678.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/IVYDE-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Schneider resolved IVYDE-202.
---------------------------------

       Resolution: Won't Fix
    Fix Version/s: 2.1.0

> Another method for adding IvyDE classpath container to the WTP dynamic module tree.
> -----------------------------------------------------------------------------------
>
>                 Key: IVYDE-202
>                 URL: https://issues.apache.org/jira/browse/IVYDE-202
>             Project: IvyDE
>          Issue Type: Improvement
>         Environment: IBM RAD 7.5.3, Websphere 6.1.0.25
>            Reporter: Jon Schneider
>             Fix For: 2.1.0
>
>         Attachments: ClasspathTestFixesFor75x.zip, ivyde-202.patch, rad_jee_page.jpg
>
>
> Recently, my colleagues at work upgraded from RAD 7.5.2 to RAD 7.5.3.  Before the upgrade, IvyDE classpath containers showed up in the Web Libraries tab of the JEE Module Dependencies preference page.  After the upgrade, the classpath container is conspicuously missing.  Manually affecting the .classpath to add the container attribute does not help to deploy the contents of the container.
> After some exhaustive debugging with WTP 3.0.4 and WTP 3.0.5, I concluded that the issue had to be somehow RAD specific.  IBM's response was:
> "This rings a bell. The ability to map "User Libraries" under Web libraries was a piece of functionality that was removed between RAD 7.5.2 and 7.5.3.
> I did some digging and it seems the reason this was removed has something to do with reliability issues...
> Apparently the old behaviour can be had by enabling the preference "Allow loose classpath module dependencies" [in a RAD specific workspace preference page] although there is a scary warning accompanying it."

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