librelist archives

« back to archive

Jar naming

Jar naming

From:
Dave Sann
Date:
2013-03-08 @ 09:25
in a project:  group/name

The artefact name does not need to be unique.

jars are named : name-suffix.jar

I think that it would be perhaps better to have jars by default named as:

group-name-suffix.jar

This means that you can uniquely tell what a jar is by its name.
There is also no possibility of conflict. (with lein2 not using lib/
anymore this is not really an issue but I still prefer unique naming)


This would be a minor change to the jar task.


Currently, I name my projects group/group-name to do this. But it is a but
annoying to write [x/x-name "..."].

yes? no?

Dave

Re: [leiningen] Jar naming

From:
Laurent Petit
Date:
2013-03-08 @ 10:09
I agree with you. And the maven community also does this wrong thing
of not adding the group-name, and instead repeating the group name in
the artifact id.

I would appreciate what you're suggesting.

For instance, org.clojure/tools.nrepl  would then produce
org.clojure-tools.nrepl or org.clojure.tools.nrepl jars instead of the
opaque tools.nrepl jar ...

2013/3/8 Dave Sann <davesann.s@gmail.com>:
> in a project:  group/name
>
> The artefact name does not need to be unique.
>
> jars are named : name-suffix.jar
>
> I think that it would be perhaps better to have jars by default named as:
>
> group-name-suffix.jar
>
> This means that you can uniquely tell what a jar is by its name.
> There is also no possibility of conflict. (with lein2 not using lib/ anymore
> this is not really an issue but I still prefer unique naming)
>
>
> This would be a minor change to the jar task.
>
>
> Currently, I name my projects group/group-name to do this. But it is a but
> annoying to write [x/x-name "..."].
>
> yes? no?
>
> Dave
>
>
>

Re: [leiningen] Jar naming

From:
Dave Sann
Date:
2013-03-16 @ 23:42
Raised as an issue here



On 8 March 2013 21:09, Laurent PETIT <laurent.petit@gmail.com> wrote:

> I agree with you. And the maven community also does this wrong thing
> of not adding the group-name, and instead repeating the group name in
> the artifact id.
>
> I would appreciate what you're suggesting.
>
> For instance, org.clojure/tools.nrepl  would then produce
> org.clojure-tools.nrepl or org.clojure.tools.nrepl jars instead of the
> opaque tools.nrepl jar ...
>
> 2013/3/8 Dave Sann <davesann.s@gmail.com>:
> > in a project:  group/name
> >
> > The artefact name does not need to be unique.
> >
> > jars are named : name-suffix.jar
> >
> > I think that it would be perhaps better to have jars by default named as:
> >
> > group-name-suffix.jar
> >
> > This means that you can uniquely tell what a jar is by its name.
> > There is also no possibility of conflict. (with lein2 not using lib/
> anymore
> > this is not really an issue but I still prefer unique naming)
> >
> >
> > This would be a minor change to the jar task.
> >
> >
> > Currently, I name my projects group/group-name to do this. But it is a
> but
> > annoying to write [x/x-name "..."].
> >
> > yes? no?
> >
> > Dave
> >
> >
> >
>

Re: [leiningen] Jar naming

From:
Dave Sann
Date:
2013-03-16 @ 23:42
raised as an issue here

https://github.com/technomancy/leiningen/issues/1070

Dave


On 8 March 2013 21:09, Laurent PETIT <laurent.petit@gmail.com> wrote:

> I agree with you. And the maven community also does this wrong thing
> of not adding the group-name, and instead repeating the group name in
> the artifact id.
>
> I would appreciate what you're suggesting.
>
> For instance, org.clojure/tools.nrepl  would then produce
> org.clojure-tools.nrepl or org.clojure.tools.nrepl jars instead of the
> opaque tools.nrepl jar ...
>
> 2013/3/8 Dave Sann <davesann.s@gmail.com>:
> > in a project:  group/name
> >
> > The artefact name does not need to be unique.
> >
> > jars are named : name-suffix.jar
> >
> > I think that it would be perhaps better to have jars by default named as:
> >
> > group-name-suffix.jar
> >
> > This means that you can uniquely tell what a jar is by its name.
> > There is also no possibility of conflict. (with lein2 not using lib/
> anymore
> > this is not really an issue but I still prefer unique naming)
> >
> >
> > This would be a minor change to the jar task.
> >
> >
> > Currently, I name my projects group/group-name to do this. But it is a
> but
> > annoying to write [x/x-name "..."].
> >
> > yes? no?
> >
> > Dave
> >
> >
> >
>