Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 389715 - WAR export from IDE always includes java source - ignoring 'export source files' checkbox
Summary: WAR export from IDE always includes java source - ignoring 'export source fil...
Status: CLOSED DUPLICATE of bug 380581
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.servlet (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: jst.servlet CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2012-09-17 09:04 EDT by Tomasz Barczyk CLA
Modified: 2012-09-24 11:41 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Barczyk CLA 2012-09-17 09:04:37 EDT

    
Comment 1 Dani Megert CLA 2012-09-18 03:59:16 EDT
Please provide more detailed steps.
Which build do you use?
Comment 2 Tomasz Barczyk CLA 2012-09-18 04:34:13 EDT
(In reply to comment #1)
> Please provide more detailed steps.
> Which build do you use?

Hi,

Pasted from 'About Eclipse':
Eclipse Java EE IDE for Web Developers.
Version: Juno Release
Build id: 20120614-1722

Java Web Application (Dynamic Web Module)
Steps:
Right mouse click on project name in Package Explorer
select context menu: Export ...
first form: Web / WAR file, Next >
second form: 'Export source files' checkbox UNCHECKED
The WAR is created but still contains .class and .java files
(the behaviour was correct in Indigo)
Comment 3 Nitin Dahyabhai CLA 2012-09-24 11:12:47 EDT
Can you attach a project where this happens, or at least the project's .project and .classpath files and .settings folder?
Comment 4 Carl Anderson CLA 2012-09-24 11:41:38 EDT
This was found just after we shut down for Eclipse Juno.  There is a public patch available, and it will also be fixed in Juno SR1, which becomes available this Friday.

*** This bug has been marked as a duplicate of bug 380581 ***