Community
Participate
Working Groups
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)
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...
Comments? Could we mark this one as invalid?