How maven assembly plugin auto-resolves classpath conflicts (example case)

[Michał Siatkowski]

Hello.

I have found this to be an issue while migrating a project from Maven to
SBT.
SBT is only here for reference since it reports what I think should be
reported.

To describe the problem I have created an example project with dependencies
that I found to behave differently, depending on the build tool.
https://github.com/atais/mvn-sbt-assembly

The only dependencies are (sbt style)

"com.netflix.astyanax" % "astyanax-cassandra" % "3.9.0",
"org.apache.cassandra" % "cassandra-all" % "3.4",

and what I do not understand is, why mvn package creates the fat jar
successfully, while sbt assembly gives conflicts:

[error] 39 errors were encountered during merge
[error] java.lang.RuntimeException: deduplicate: different file contents
found in the following:
[error]
/home/siatkowskim/.ivy2/cache/org.slf4j/jcl-over-slf4j/jars/jcl-over-slf4j-1.7.7.jar:org/apache/commons/logging/
[error]
/home/siatkowskim/.ivy2/cache/commons-logging/commons-logging/jars/commons-logging-1.1.1.jar:org/apache/commons/logging/
...
[error]
/home/siatkowskim/.ivy2/cache/com.github.stephenc.high-scale-lib/high-scale-lib/jars/high-scale-lib-1.1.2.jar:org/cliffc/high_scale_lib/
[error]
/home/siatkowskim/.ivy2/cache/com.boundary/high-scale-lib/jars/high-scale-lib-1.0.6.jar:org/cliffc/high_scale_lib/
...

How come Maven knows which class to take?
How can it be sure, that it is the correct choice?

There is a question on SO, if you would like to earn some points:
https://stackoverflow.com/questions/50249818/why-maven-assembly-works-when-sbt-assembly-find-conflicts

I have been directed here, from
https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-887

Atlas-create-jira-plugin (Build failed)

[Denisa Claudia]

Hello,

I am trying to create a jira plugin, but the build is failing. I think I
need to add some proxy configuration in settings.xml. In my company, we
have a automatic proxy configuration script and there is no proxy host/ip
configuration. In these case how do I setup the proxy configuration in
settings.xml?


Have a splendid day! :)

Denisa

Re: maven-license plugin's license-list

[jieryn]

The plugin ships with a bunch of licenses it can use to control the
license information in your source files. You can always add more
licenses (two files) and have the plugin keep your license up to date
with the ones you specify.

On Tue, May 22, 2018 at 1:00 PM, Désilets, Alain
 wrote:
> Thx Thomas. Good thing I checked!
>
> Alain
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-license plugin's license-list

[Désilets , Alain]

Thx Thomas. Good thing I checked!

Alain
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-license plugin's license-list

[Thomas Broyer]

No, AFAICT, it's the list of all licences known to the plugin, irrespective
of "applicability" and/or your dependencies.

On Tue, May 22, 2018 at 5:20 PM Désilets, Alain <
alain.desil...@nrc-cnrc.gc.ca> wrote:

> This may sound a bit nit-picky, but I need to be 100% about this...
>
>
> I am using the maven-license plugin to figure out under which Open Source
> license (if any) under which I have to license my code.
>
>
> I am running the 'license-list' goal, and it produces a report that looks
> like this:
>
>
> =
>
> [INFO] Available licenses :
>
>
>  * agpl_v3 : GNU Affero General Public License (AGPL) version 3.0
>
>  * apache_v2   : Apache License version 2.0
>
>  * bsd_2   : BSD 2-Clause License
>
>  * bsd_3   : BSD 3-Clause License
>
>  * cddl_v1 : COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
> Version 1.0
>
> etc..
>
> =
>
>
> I am ASSUMING that this is a list of all the alternative licenses that I
> could use to distribute my code under. In other words, this is the
> INTERSECTION (as opposed to the UNION) of the licenses that are compatible
> with each of the individual third party modules, correct? Can someone
> please confirm?
>
>
> Thanks again for bearing with me. The word "available licenses" is just a
> bit too ambiguous for my taste and I couldn't find anywhere a more precise
> explanation of what is meant by that.
>
>
>
>

maven-license plugin's license-list

[Désilets , Alain]

This may sound a bit nit-picky, but I need to be 100% about this...


I am using the maven-license plugin to figure out under which Open Source 
license (if any) under which I have to license my code.


I am running the 'license-list' goal, and it produces a report that looks like 
this:


=

[INFO] Available licenses :


 * agpl_v3 : GNU Affero General Public License (AGPL) version 3.0

 * apache_v2   : Apache License version 2.0

 * bsd_2   : BSD 2-Clause License

 * bsd_3   : BSD 3-Clause License

 * cddl_v1 : COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0

etc..

=


I am ASSUMING that this is a list of all the alternative licenses that I could 
use to distribute my code under. In other words, this is the INTERSECTION (as 
opposed to the UNION) of the licenses that are compatible with each of the 
individual third party modules, correct? Can someone please confirm?


Thanks again for bearing with me. The word "available licenses" is just a bit 
too ambiguous for my taste and I couldn't find anywhere a more precise 
explanation of what is meant by that.