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

Bug 357595

Summary:	Support deployment of configuration artifacts from tooling
Product:	[RT] Virgo	Reporter:	Alexey Romanov <alexey.v.romanov>
Component:	tooling	Assignee:	Project Inbox <virgo-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse, leo.dos.santos, mlippert
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Alexey Romanov

2011-09-14 03:22:17 EDT

Build Identifier: 

Currently bundle and PAR projects, and plan files, can be deployed from tooling. However, configuration files can't. They have to be copied to /pickup or /repository/usr manually. This also doesn't control of their deployment order from tooling.

Reproducible: Always

Comment 1 Miles Parker

2012-03-07 22:53:16 EST

Alexey, can you give more detail on how the user story would go here?

Comment 2 Alexey Romanov

2012-03-21 09:14:17 EDT

I had simply this in mind:

1. Detect *.properties files in EclipseRT projects as configuration artifacts. 
2. Add them to the "Available" list in the "Add and Remove..." dialog for server, and to plan editor when it's more than just XML editor.
3. List the ones which were added in "Artefact Deployment Order" in server overview.