Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342582 - tools always download to the same fixed directories, even if they're not in provisioning->searchPaths
Summary: tools always download to the same fixed directories, even if they're not in p...
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-12 10:46 EDT by Martin Lippert CLA
Modified: 2012-03-07 22:51 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Lippert CLA 2011-04-12 10:46:35 EDT
Since it's a pain to keep on moving/copying the contents of repository/bundles/usr and repository/libraries/usr for each new AP installation, I've changed my platform.config to use a central dir for bundles and libs instead of the local usr ones.
The tools do pick this up when it comes to showing the available bundles and libs. However, when downloading, the bundles and libs are always placed in repository/bundles/usr and repository/libraries/usr: these directories even get created if they don't exist.
Since these directories are no longer part of the locations I've configured in the searchPaths for provisioning, they're not added to the actual provisioning repository for my server. This means the download support in the tools is useless unless I add the usr directories to my searchPaths again, or I have to move the files to my shared directories by hand after downloading.

The actual download locations for bundles and libs should be configurable per server instance, and should be picked from the existing list of directories as defined in the searchPaths (if it exists) or from the implied defaults (of not configured explicitly).

(moved over from: https://issuetracker.springsource.com/browse/STS-339)
Comment 1 Miles Parker CLA 2012-01-16 18:35:47 EST
Question: is this relevant to the current runtime server directory structure and deployment scenarios? I'm not sure if we should be supporting putting bundles somewhere other then where they are intended for the well-defined virgo server. Or perhaps I'm misunderstanding this bug...
Comment 2 Miles Parker CLA 2012-03-07 22:51:21 EST
Comments? Could we mark this one as invalid?