Allow configuration of directory as alternative to USERHOME [message #1730771] |
Thu, 28 April 2016 11:47 |
|
In many company networks the userhome is pointing to a roamed directory which has only a limited size. Oomph is currently storing the p2 bundlepool there. Therefore the directory is growing to large and causes synchronization problems.
Would it be possible to make the this location configurable?
Currently implementation is hardcode inside AgentManagerImpl?
public AgentManagerImpl()
{
this(new File(PropertiesUtil.USER_HOME));
}
What do you think about a something like an additional SystemProperty inside org.eclipse.oomph.internal.setup.SetupProperties named which is only used when given or is defaulting otherwise to userhome value.
What do you think?
Would you accept a contribution?
|
|
|
|
Re: Allow configuration of directory as alternative to USERHOME [message #1730801 is a reply to message #1730785] |
Thu, 28 April 2016 14:45 |
|
Hi Ed,
that is exactly my point. I do not want to change the userhome cause it is used for other eclipse user stores, like secure_storage and so on.
My question/requirement is to configure the defaultAgentLocation?
As far as I know this is currently not possible?
What do you think about making it configurable?
I'm trying to provide a default oomph with custom batch file for launching and configuring oomph for the "enterprise" setup.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02188 seconds