[ 
https://issues.apache.org/jira/browse/IVYDE-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761597#action_12761597
 ] 

Ivica Loncar commented on IVYDE-202:
------------------------------------


There is a workaround that will allow RSA to load preferences:

 - export RSA preferences ( File -> Export: General -> Preferences)
 - open exported .epf file and replace
/instance/org.eclipse.jst.j2ee/org.eclipse.jst.j2ee.preferences.allowClasspathDep=false
with 
/instance/org.eclipse.jst.j2ee/org.eclipse.jst.j2ee.preferences.allowClasspathDep=true



> 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
>         Attachments: 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.

Reply via email to