Bug 116643 - [jar exporter] Allowing to use VARIABLEs in jar export path
Summary: [jar exporter] Allowing to use VARIABLEs in jar export path
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-16 07:00 EST by Hasan Ceylan CLA
Modified: 2007-06-14 10:43 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 Hasan Ceylan CLA 2005-11-16 07:00:49 EST 
I have a project that I maintain in both linux and windows. Therefore I switch
between OSs very frequently. 

I use jar export to export the binaries. with CVS it is pain to change the
export path all the time. 

I would be great to have eclipse variables or environment variables support in
the export path. Therefore it is not a change each time I commit the project to
the CVS server.

Hasan Ceylan
Comment 1 Jerome Lanneluc CLA 2005-11-16 07:04:03 EST 
Moving to JDT UI
Comment 2 Martin Aeschlimann CLA 2005-11-16 19:06:55 EST 
Where exactly would you like to specify a variable. Is it in the .jardesc file?
Comment 3 Hasan Ceylan CLA 2005-11-17 06:13:57 EST 
Yes...

"Select export destination" section "JAR File"..
Comment 4 Per Lauge Holst CLA 2006-08-23 05:27:44 EDT 
Just to put in my 2 cents and a twist on this:

I think it'd be nice if the JAR filename could be substituted by some of the standard template variables such as ${date}, ${time}, and ${user} - possibly also having an automatically incrementing version number. 

I know this is a weird form of version/deployment control.

Of course, adding variables poses the problem when someone actually wants a $ in their filename, or on Windows if a user is named "con" etc. and that's the full name of the file.