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

Bug 221042

Summary:	[xslt][launcher] Need ability to set working directory or output directory
Product:	[WebTools] WTP Source Editing	Reporter:	David Carver <d_a_carver>
Component:	wst.xsl	Assignee:	Doug <doug.satchwell>
Status:	RESOLVED FIXED	QA Contact:	Doug <doug.satchwell>
Severity:	enhancement
Priority:	P2	CC:	doug.satchwell, remy.suen, stuartharper, thatnitind
Version:	unspecified
Target Milestone:	3.1
Hardware:	PC
OS:	All
Whiteboard:
Bug Depends on:	221973
Bug Blocks:

Description David Carver

2008-03-01 16:00:01 EST

0.5M5

When setting up a XSL launch configuration that makes use of Xalan's support for EXSLT functions like exslt:document

http://www.exslt.org/exsl/elements/document/index.html

These will output files to the working directory which could be outside the files system.   This causes items like the Eclipse xsl, to wrongly output the plugin.xml, and toc.xml to the wrong directories instead of the appropriate plugin directory.

Comment 1 Remy Suen

2008-03-01 16:27:27 EST

Did someone just say working directory? Please see bug 214696. :)

Comment 2 David Carver

2008-06-05 21:40:40 EDT

Mass Migration to wtp.inc.xsl

Comment 3 Doug

2008-06-26 11:05:06 EDT

If the working directory were changed, it would cause any relative URI's to includes/imports not to work. It would be better to use a variable for the output documents, which can be set in the run configuration.

Comment 4 David Carver

2008-06-26 11:50:38 EDT

(In reply to comment #3)
> If the working directory were changed, it would cause any relative URI's to
> includes/imports not to work. It would be better to use a variable for the
> output documents, which can be set in the run configuration.
> 

Processors should be basing the includes/imports off the location and path where the XSLT processor is stored, so I don't necessarily think this is going to mess up imports and includes, but we should test this, and have a unit test to verify this situation before just marking it as invalid, so I'm suggesting that we reopen this for further investigation.

Comment 5 Doug

2008-06-26 12:39:48 EDT

Ok - re-opening so we can have some unit tests for this.

Comment 6 David Carver

2008-07-28 20:58:50 EDT

Looks like Remy may have made some progress on this from the base platform.   So once this is handled, we may be able to add this tab and use it in XSL Tools launch configurations.

Comment 7 David Carver

2008-08-31 18:17:26 EDT

This will need to wait until bug 221973 is implemented at the platform.  This will separate out the JDT working directory into a more general working directory that can be used regardless if JDT is available or not.

Comment 8 David Carver

2009-01-12 10:19:52 EST

re-assigning until the dependent patch is implemented.

Comment 9 Doug

2009-02-23 17:37:18 EST

Added the new block to the Output tab

Comment 10 David Carver

2009-02-24 18:25:58 EST

A report in the WTP-Incubator is saying there are some problems with this.

Stuart Harper wrote:
> I just did an update from HEAD and there seems to be a couple of issues in the current revision:
>
> -In xsl.debug.ui the class WorkingDirectoryBlock is missing
> -In xsl.jaxp.launching The file JAXPJavaLaunchConfigurationDelegate calls a method  getWorkingDir() on LaunchHelper which doesn't exist.

Comment 11 David Carver

2009-02-24 23:21:52 EST

Doug it looks like some changes that were done for org.eclipse.wst.xsl.launching were not checked in as I'm able to duplicate the error messages when I check out code from head.

Comment 12 David Carver

2009-02-24 23:22:33 EST

re-assigning to doug so that he can check in the missing code for the xsl.launching plugin.

Comment 13 Doug

2009-02-25 04:18:53 EST

Its checked in now. Not sure how I missed it, but I did.

Comment 14 Doug

2009-02-26 06:28:51 EST

Mark as fixed

Comment 15 David Carver

2009-04-30 14:24:17 EDT

mass update to 3.1 target due to movement from wtp incubator to wtp source editing lost the original milestones.