ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Schneider (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVYDE-202) Another method for adding IvyDE classpath container to the WTP dynamic module tree.
Date Tue, 20 Oct 2009 12:03:59 GMT

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

Jon Schneider commented on IVYDE-202:
-------------------------------------

The PMR is 00686,370,000.  Feature request RATLC01407291 was created to have the feature added
to future RAD v7.5.x release.  I have attached the fix in the meantime.  The fix for RAD 7.5.3
helps the property to persist.  The fix for RAD 7.5.4 eliminates the need to have to check
this property.

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


Mime
View raw message