which "plugins" dir

Hello

In 2.7.x, the default value for "-Xpluginsdir" was "${scala.home}/misc/scala-devel/plugins".

By mistake, this is different in the 2.8. trunk. Here the default value is
"${scala.home}/misc:${scala.home}/scala-devel:${scala.home}/plugins".

This is why the continuations plugin is loaded when being placed in
the top-level "plugins" folder.


My question: do we want a top-level "plugins" folder as default or do we want
to keep the old "misc/scala-devel/plugins"? The continuations.jar will be
placed in there.

I'll do the according changes in source / build scripts.


Thanks for a prompt answer.
Lukas

On Sun, Apr 11, 2010 at 05:44:07PM +0200, Lukas Rytz wrote:
> My question: do we want a top-level "plugins" folder as default or do
> we want to keep the old "misc/scala-devel/plugins"? The
> continuations.jar will be placed in there.

I vote that misc/scala-devel/plugins is a needlessly tortuous path given
the relatively small number of entities in the distribution.

The development of compiler plugins is not something that is particularly
commonplace, and the location is transparent to final users in the end
anyway. Therefore the actual location matters is unlikely to matter much
in the end.

That said, I'd keep the old location: I don't see a special reason for an
entire top-level directory.
(Actually, I'd personally put them in lib/plugins).

Toni

On Sun, April 11, 2010 5:44 pm, Lukas Rytz wrote:
> Hello
>
> In 2.7.x, the default value for "-Xpluginsdir" was
> "${scala.home}/misc/scala-devel/plugins".
>
> By mistake, this is different in the 2.8. trunk. Here the default value is
> "${scala.home}/misc:${scala.home}/scala-devel:${scala.home}/plugins".
>
> This is why the continuations plugin is loaded when being placed in
> the top-level "plugins" folder.
>
>
> My question: do we want a top-level "plugins" folder as default or do we
> want
> to keep the old "misc/scala-devel/plugins"? The continuations.jar will be
> placed in there.
>
> I'll do the according changes in source / build scripts.
>
>
> Thanks for a prompt answer.
> Lukas
>

On Sun, Apr 11, 2010 at 06:07:12PM +0200, Antonio Cunei wrote:
> (Actually, I'd personally put them in lib/plugins).

I second that location if an all new one is on the table.

On Sun, Apr 11, 2010 at 06:07:12PM +0200, Antonio Cunei wrote:
> (Actually, I'd personally put them in lib/plugins).

I second that location if an all new one is on the table.

--
Paul Phillips      | All men are frauds.  The only difference between
Caged Spirit       | them is that some admit it.  I myself deny it.
Empiricist         |     -- H. L. Mencken
slap pi uphill!    |----------* http://www.improving.org/paulp/ *----------

The development of compiler plugins is not something that is particularly
commonplace, and the location is transparent to final users in the end
anyway. Therefore the actual location matters is unlikely to matter much
in the end.

That said, I'd keep the old location: I don't see a special reason for an
entire top-level directory.
(Actually, I'd personally put them in lib/plugins).

Toni

On Sun, April 11, 2010 5:44 pm, Lukas Rytz wrote:
> Hello
>
> In 2.7.x, the default value for "-Xpluginsdir" was
> "${scala.home}/misc/scala-devel/plugins".
>
> By mistake, this is different in the 2.8. trunk. Here the default value is
> "${scala.home}/misc:${scala.home}/scala-devel:${scala.home}/plugins".
>
> This is why the continuations plugin is loaded when being placed in
> the top-level "plugins" folder.
>
>
> My question: do we want a top-level "plugins" folder as default or do we
> want
> to keep the old "misc/scala-devel/plugins"? The continuations.jar will be
> placed in there.
>
> I'll do the according changes in source / build scripts.
>
>
> Thanks for a prompt answer.
> Lukas
>

On Sun, Apr 11, 2010 at 18:07, Antonio Cunei < (antonio [dot] cunei [at] epfl [dot] ch> wrote:

The development of compiler plugins is not something that is particularly
commonplace, and the location is transparent to final users in the end
anyway. Therefore the actual location matters is unlikely to matter much
in the end.

That said, I'd keep the old location: I don't see a special reason for an
entire top-level directory.
(Actually, I'd personally put them in lib/plugins).

yeah why not. who decides?

paul: by default, every .jar in "lib" is in the scalabootclasspath, but not
any .jars in subfolders, right? plugins don't need to be in the classpath.

lukas

 

Toni

On Sun, April 11, 2010 5:44 pm, Lukas Rytz wrote:
> Hello
>
> In 2.7.x, the default value for "-Xpluginsdir" was
> "${scala.home}/misc/scala-devel/plugins".
>
> By mistake, this is different in the 2.8. trunk. Here the default value is
> "${scala.home}/misc:${scala.home}/scala-devel:${scala.home}/plugins".
>
> This is why the continuations plugin is loaded when being placed in
> the top-level "plugins" folder.
>
>
> My question: do we want a top-level "plugins" folder as default or do we
> want
> to keep the old "misc/scala-devel/plugins"? The continuations.jar will be
> placed in there.
>
> I'll do the according changes in source / build scripts.
>
>
> Thanks for a prompt answer.
> Lukas
>

On Sun, Apr 11, 2010 at 07:07:41PM +0200, Lukas Rytz wrote:
> paul: by default, every .jar in "lib" is in the scalabootclasspath,
> but not any .jars in subfolders, right? plugins don't need to be in
> the classpath.

Right, everything in lib/* gets on the classpath extdir style, which
means jars in subdirectories would not (but top level directories in lib
should if they were there and had exploded jar structure.) There's a not
entirely clear relationship between the "boot classpath" and the
"extdir" contribution, but except when you need pathological control
over the classpath it doesn't matter since they're all going to turn up
and they'll all be ahead of yours.

On Sun, Apr 11, 2010 at 07:07:41PM +0200, Lukas Rytz wrote:
> paul: by default, every .jar in "lib" is in the scalabootclasspath,
> but not any .jars in subfolders, right? plugins don't need to be in
> the classpath.

Right, everything in lib/* gets on the classpath extdir style, which
means jars in subdirectories would not (but top level directories in lib
should if they were there and had exploded jar structure.) There's a not
entirely clear relationship between the "boot classpath" and the
"extdir" contribution, but except when you need pathological control
over the classpath it doesn't matter since they're all going to turn up
and they'll all be ahead of yours.

--
Paul Phillips      | The important thing here is that the music is not in
Moral Alien        | the piano.  And knowledge and edification is not in the
Empiricist         | computer.  The computer is simply an instrument whose
pp: i haul pills   | music is ideas.  -- Alan Kay

ok, let's keep the old location then. we've had enough surprises with classpaths.

On Sun, Apr 11, 2010 at 20:09, Paul Phillips <paulp@improving.org> wrote:

On Sun, Apr 11, 2010 at 07:07:41PM +0200, Lukas Rytz wrote:
> paul: by default, every .jar in "lib" is in the scalabootclasspath,
> but not any .jars in subfolders, right? plugins don't need to be in
> the classpath.

Right, everything in lib/* gets on the classpath extdir style, which
means jars in subdirectories would not (but top level directories in lib
should if they were there and had exploded jar structure.) There's a not
entirely clear relationship between the "boot classpath" and the
"extdir" contribution, but except when you need pathological control
over the classpath it doesn't matter since they're all going to turn up
and they'll all be ahead of yours.

--
Paul Phillips      | The important thing here is that the music is not in
Moral Alien        | the piano.  And knowledge and edification is not in the
Empiricist         | computer.  The computer is simply an instrument whose
pp: i haul pills   | music is ideas.  -- Alan Kay