Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313628 - Ant build from within Eclipse uses the Eclipse home directory instead of project directory as a base
Summary: Ant build from within Eclipse uses the Eclipse home directory instead of proj...
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-19 16:55 EDT by Dean Schulze CLA
Modified: 2010-05-20 17:29 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Schulze CLA 2010-05-19 16:55:22 EDT 
Build Identifier: 20100506-2000

Upgraded from M6 to M7 (different workspace for M6 and M7).  Imported an existing project into M7.  Opened the Ant view in the J2EE perspective.  The Ant build fails when running the <wsimport> task because it looks for a .wsdl file relative to the Eclipse home directory instead of relative to the project directory.

Running Ant from the command line works properly.

I pulled M6 out of the trash and it works properly.  The Ant wsimport task uses the project directory as a base instead of the Eclipse home directory.

I looked at the external tools configuration in both M6 and M7 and they look the same.


Reproducible: Always

Steps to Reproduce:
1.  Install M7
2.  Import an existing project that uses the Ant <wsimport> task.
3.  Do an Ant build from within M7 using the Ant <wsimport> task.
Comment 1 Olivier Thomann CLA 2010-05-19 19:13:59 EDT 
Move to Platform/Ant
Comment 2 Darin Wright CLA 2010-05-20 14:29:51 EDT 
Can you attach a simple example project that demonstrates the problem? A quick look at code changes between M6/M7 shows no changes in working directory handling.
Comment 3 Dean Schulze CLA 2010-05-20 17:29:37 EDT 
I got the same problem after backing out to M6 when it used the same workspace.  Using a new workspace solved this issue with M7 (M6 works with the new workspace too).

Somehow my workspace got changed.