Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337439 - Would like a command line parameter to override the default target directory for generation.
Summary: Would like a command line parameter to override the default target directory ...
Status: RESOLVED WONTFIX
Alias: None
Product: Tigerstripe
Classification: Technology
Component: Headless (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 336669 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-17 09:07 EST by Steve Jerman CLA
Modified: 2011-07-20 13:34 EDT (History)
1 user (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 Steve Jerman CLA 2011-02-17 09:07:10 EST 
Since the function of the 'PROJECT_IMPORT' has changed in the latest builds from an 'import' to a 'copy', in a lot of situations, the generation will be to a temporary directory in a different place from that used when someone hand generates a project. It would be good if the user could override the 'normal' target location and generate back to the original project. This will make the user experience more consistent and prevent confusion.
Comment 1 Navid Mehregani CLA 2011-02-17 09:42:20 EST 
Just to clarify, what Steve is requesting is a way to specify the generator directory on the command line.  As of now, all the generated artifacts are created inside the model project, but Steve wants the ability to specify any arbitrary location.
Comment 2 Navid Mehregani CLA 2011-02-24 11:51:24 EST 
*** Bug 336669 has been marked as a duplicate of this bug. ***
Comment 3 Navid Mehregani CLA 2011-05-24 09:33:03 EDT 
Is there still a need for this defect after the implementation of a one button solution to generate the artifact jar within the SDK? 
The issue before was that the maven approach would create the artifact jar in a sub directory of the generation folder.  However, with the contribution of the 'create artifact jar' button, the artifact jar is now conveniently created as a top-level file under the generation folder.
Comment 4 Navid Mehregani CLA 2011-07-20 13:34:06 EDT 
Closing enhancement per discussion with Steve.