You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Simon Nash <na...@apache.org> on 2008/11/28 23:02:15 UTC
Tuscany runtime always creates "target" subdirectory
While running a test that launches the Tuscany runtime standalone
from a command line, I noticed that Tuscany always creates an empty
"target" subdirectory under the current directory. It isn't very
friendly to modify the user's environment in this way, and in some
cases (running from a read-only location) this would cause Tuscany
to fail.
On investigation I found that this is caused by the lines
repository = new ContributionRepositoryImpl("target", inputFactory, monitor);
in ReallySmallRuntimeBuilder and
FileHelper.forceMkdir(rootFile);
in ContributionRepositoryImpl.
What is the purpose of this empty subdirectory? Does it need to be
placed under the current directory? I noticed that there is code in
ContributionServiceImpl to default the location of this subdirectory to
<user.home>/.tuscany/domains/local/
which seems like a friendlier location for a directory owned by the
Tuscany runtime, but this default location is being overridden by the
hard-wired "target" subdirectory passed in by ReallySmallRuntimeBuilder.
Is it possible to defer the creation of this subdirectory to when it's
really needed, rather than creating it all the time even when it's left
empty? Alternatively, can this subdirectory be created under <user.home>
so that it doesn't intrude so much on the user's runtime environment?
(Or perhaps both of the above.)
Simon
Re: Tuscany runtime always creates "target" subdirectory
Posted by ant elder <an...@gmail.com>.
I think its already been removed in trunk now that thats been replaced with
the equinox branch code.
...ant
On Sat, Nov 29, 2008 at 3:57 AM, Luciano Resende <lu...@gmail.com>wrote:
> Hey Simon
>
> This is obsolete code and can be definitely removed. I have looked
> in removing the ContributionRepository completely, but maybe the
> approach I took was not so good and was causing too much side effects.
> If you want, I can take a look at this after Wednesday.
>
> Here is another thread on the same subject [1]
> [1] http://markmail.org/message/mwebwj3wvkiwhzjn
>
> On Fri, Nov 28, 2008 at 2:02 PM, Simon Nash <na...@apache.org> wrote:
> > While running a test that launches the Tuscany runtime standalone
> > from a command line, I noticed that Tuscany always creates an empty
> > "target" subdirectory under the current directory. It isn't very
> > friendly to modify the user's environment in this way, and in some
> > cases (running from a read-only location) this would cause Tuscany
> > to fail.
> >
> > On investigation I found that this is caused by the lines
> > repository = new ContributionRepositoryImpl("target", inputFactory,
> > monitor);
> > in ReallySmallRuntimeBuilder and
> > FileHelper.forceMkdir(rootFile);
> > in ContributionRepositoryImpl.
> >
> > What is the purpose of this empty subdirectory? Does it need to be
> > placed under the current directory? I noticed that there is code in
> > ContributionServiceImpl to default the location of this subdirectory to
> > <user.home>/.tuscany/domains/local/
> > which seems like a friendlier location for a directory owned by the
> > Tuscany runtime, but this default location is being overridden by the
> > hard-wired "target" subdirectory passed in by ReallySmallRuntimeBuilder.
> >
> > Is it possible to defer the creation of this subdirectory to when it's
> > really needed, rather than creating it all the time even when it's left
> > empty? Alternatively, can this subdirectory be created under <user.home>
> > so that it doesn't intrude so much on the user's runtime environment?
> > (Or perhaps both of the above.)
> >
> > Simon
> >
> >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
Re: Tuscany runtime always creates "target" subdirectory
Posted by Luciano Resende <lu...@gmail.com>.
Hey Simon
This is obsolete code and can be definitely removed. I have looked
in removing the ContributionRepository completely, but maybe the
approach I took was not so good and was causing too much side effects.
If you want, I can take a look at this after Wednesday.
Here is another thread on the same subject [1]
[1] http://markmail.org/message/mwebwj3wvkiwhzjn
On Fri, Nov 28, 2008 at 2:02 PM, Simon Nash <na...@apache.org> wrote:
> While running a test that launches the Tuscany runtime standalone
> from a command line, I noticed that Tuscany always creates an empty
> "target" subdirectory under the current directory. It isn't very
> friendly to modify the user's environment in this way, and in some
> cases (running from a read-only location) this would cause Tuscany
> to fail.
>
> On investigation I found that this is caused by the lines
> repository = new ContributionRepositoryImpl("target", inputFactory,
> monitor);
> in ReallySmallRuntimeBuilder and
> FileHelper.forceMkdir(rootFile);
> in ContributionRepositoryImpl.
>
> What is the purpose of this empty subdirectory? Does it need to be
> placed under the current directory? I noticed that there is code in
> ContributionServiceImpl to default the location of this subdirectory to
> <user.home>/.tuscany/domains/local/
> which seems like a friendlier location for a directory owned by the
> Tuscany runtime, but this default location is being overridden by the
> hard-wired "target" subdirectory passed in by ReallySmallRuntimeBuilder.
>
> Is it possible to defer the creation of this subdirectory to when it's
> really needed, rather than creating it all the time even when it's left
> empty? Alternatively, can this subdirectory be created under <user.home>
> so that it doesn't intrude so much on the user's runtime environment?
> (Or perhaps both of the above.)
>
> Simon
>
>
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/