Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 54728

Summary: [build] remove hardcoded path in swtdownload target
Product: [Eclipse Project] Platform Reporter: Jan Schulz <jasc>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: billy.biggs, ericwill, snorthov
Version: 3.0Keywords: triaged
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
patch agains swt.gtk build.xml none

Description Jan Schulz CLA 2004-03-12 18:31:00 EST 
Hello,

I'm currently trying to build debian packages for swt (and afterwards complete 
eclipse) and I would like to use the swtdownlaod target to install the jars into 
the right dir. For that it would be nice, if you could change the copy targets 
to something, which could be set from outside the target and split the arch 
independ part from the arch dependend.

See attched patch for what I mean.
Comment 1 Jan Schulz CLA 2004-03-12 18:33:21 EST 
Created attachment 8549 [details]
patch agains swt.gtk build.xml

The patch does what I want (calling copyToLocation) and results in the same zip
as before, if the swtdownload target is called.
Comment 2 Billy Biggs CLA 2005-05-24 23:26:53 EDT 
Veronika, I think you were recently looking at this stuff.
Comment 3 Grant Gayed CLA 2009-08-27 14:43:29 EDT 
Moving report to triage, see http://www.eclipse.org/swt/triage.php
for swt bug handling process.
Comment 4 Eric Williams CLA 2017-07-28 10:17:09 EDT 
Ping, is this bug still valid?
Comment 5 Eclipse Genie CLA 2020-02-13 08:01:59 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.