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 Fri, 02 Oct 2009 12:13:23 GMT

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

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

IBM admits that disabling this feature was a mistake.  They intended to disable the feature
of WTP allowing the mapping of external jars to the JEE module dependencies, and managed to
take out a bit too much.  Here is the response from IBM:

1.  Why does the loose classpath module dependencies preference not persist?

"...the 'Allow loose classpath module dependencies' preference persistence problem is a defect.
I will provide you with the APAR (defect) number once it's available. I will also request
a testfix for you for both RAD v7.5.3 and RAD v7.5.4."

2.  When can we expect to see classpath containers back in the JEE Module Dependencies?

"The feature to map user defined classpath container under Web Libraries (i.e. add the user
defined classpath to Java Build Path, and reference it from J2EE module dependencies >
Web Libraries tab) is disabled when disabling a WTP feature in RAD. A feature request was
created to enable this feature in future RAD v7.5.x release. It is currently targeted for
RAD v7.5.5 which is tentatively scheduled to be released in Dec 2009."

3.  What about the warning message?  Does our use case result in an unsupported application?

"Enabling 'Allow loose classpath module dependencies' option is a supported workaround to
enable the feature to map user defined classpath container under Web Libraries."

I'll post the fix APAR when I get it.  In the meantime, my documentation patch details how
to get around this problem for RAD users.

> 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