Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320897 - Doc cleanup: Java EE Module Dependencies does not show in Helios
Summary: Doc cleanup: Java EE Module Dependencies does not show in Helios
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: Future   Edit
Assignee: Chuck Bridgham CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-26 09:41 EDT by japickard CLA
Modified: 2010-08-24 21:14 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description japickard CLA 2010-07-26 09:41:21 EDT
Build Identifier: 20100617-1415

Created a dynamic web project in Galileo and in project preferences I had Java EE Module Dependencies is a selection.  Open the same project in Helios and the selection is no longer available, which makes it very hard to add new libraries to web project and have them export.

Reproducible: Always

Steps to Reproduce:
1. Open project in Galileo, open project preferences see Java EE Module Dep.
2. Open same project in Helios, and don't see selection in project preferences.
3.
Comment 1 Remy Suen CLA 2010-07-26 10:54:53 EDT
Project preferences? Did you mean project properties?
Comment 2 japickard CLA 2010-07-26 11:51:04 EDT
(In reply to comment #1)
> Project preferences? Did you mean project properties?

yes sorry for cofusion
Comment 3 Prakash Rangaraj CLA 2010-07-29 03:32:39 EDT
I suspect that you don't have WTP installed. Which package of Helios did you download? The Java EE Developers or the Java Developers?
Comment 4 Prakash Rangaraj CLA 2010-07-29 05:41:24 EDT
(In reply to comment #3)
> I suspect that you don't have WTP installed. Which package of Helios did you
> download? The Java EE Developers or the Java Developers?

Either case, its not a platform-ui bug. Moving to WTP
Comment 5 Krzysztof Daniel CLA 2010-07-29 06:12:17 EDT
AFAIK this option has been removed and replaced with 'Deployment Assembly'.
Comment 6 japickard CLA 2010-07-29 07:31:40 EDT
Yes I did get the Java EE edition, because I can created new dynamic web projects, which you can't do with the standard edition.  Further, when I check on install new software all of the Web, XML features are showing installed save the PHP developer kit.

Using 'Deployment Assembly' works, added external jar files and it works as expected.  However, I did spend some time on the Wiki site and it still states the Java EE Module Dependency option is still available, might want to look into updating the documentation.
Comment 7 David Williams CLA 2010-07-31 14:09:21 EDT
Fixing docs would be a good idea! But, where did you see the old documentation? Which wiki? Or, an old tutorial?
Comment 8 japickard CLA 2010-08-02 13:04:42 EDT
Fairly certain it was the Wiki, but I will research out as many links as I can and let you know.  Also pretty sure I tried the in application help as well.  As I said will research out and report back.
Comment 9 Carl Anderson CLA 2010-08-02 17:08:24 EDT
Moving this over to Chuck for initial investigation/wiki clean up.  I saw that bug 277482 mentions that http://wiki.eclipse.org/ClasspathEntriesPublishExportSupport refers to the old Java EE Module Dependencies page.
Comment 10 japickard CLA 2010-08-04 08:31:54 EDT
UI -
Ok from the UI click on the help menu, and then select search.  Type in java ee module dependency, and look at the resulting documentation.  The first document is definitely wrong, just a quick cursory go through I found at least 3 more.

Wiki - 
On the wiki perform a search for java ee module dependency, and there are several wrong documents there as well, at least for setting up a WAR export.
Comment 11 Dean Hiller CLA 2010-08-24 21:14:54 EDT
shucks, I have the same issue....on upgrade everything is broke but using the Deployment Assembly didn't work for me at all :(.  which file should change ...the .settings/*.component file still, right?  I see that file change but don't see my jars...maybe I ahve some kind of user error...would be nice if upgrade from galileo worked!!!