Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323111 - Split outlets for Java and non-Java code
Summary: Split outlets for Java and non-Java code
Status: CLOSED WONTFIX
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 1.0.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-19 05:03 EDT by Karsten Thoms CLA
Modified: 2012-11-14 05:18 EST (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 Karsten Thoms CLA 2010-08-19 05:03:27 EDT 
We want to be able to seperate the Java code and non-Java resources into different source directories. The generator properties srcPath and srcGenPath should be used to configure outlets for Java artifacts, and additionally new properties srcResPath and srcResGenPath should be introduced for non-Java artifacts. Of course the values of the new properties should default to srcPath and srcGenPath.

Our driver in the project is to adjust the Xtext projects to the standard Maven project layout. Manual sources will go to src/main/java and src/main/resources, and generated resources should go to target/generated/java and target/generated/resources. At the moment we are forced to register the source folder also as a resource folder.
Comment 1 Sebastian Zarnekow CLA 2010-08-25 14:21:54 EDT 
Can you solve this one with a workflow component, that moves files according to a name-scheme from main/java to whatever you like?
Comment 2 Sven Efftinge CLA 2012-11-14 05:18:43 EST 
no plans to change that.