[ 
https://issues.apache.org/jira/browse/MASSEMBLY-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729576#comment-16729576
 ] 

Michael Schierl commented on MASSEMBLY-873:
-------------------------------------------

[~eolivelli] can you point me to a Maven repo that contains 3.1.1 (or a 
snapshot that I can test)? It does not seem to be in Maven Central yet.

 
{code:java}
[ERROR] Plugin org.apache.maven.plugins:maven-assembly-plugin:3.1.1 or one of 
its dependencies could not be resolved: Could not find artifact 
org.apache.maven.plugins:maven-assembly-plugin:jar:3.1.1 in central 
(https://repo.maven.apache.org/maven2) -> [Help 1]{code}
 

Then I can test it with the project where the problem originally occurred.

> Maven-Assembly-Plugin freezes when building jar-with-dependencies of project 
> depending on org.bouncycastle:bcprov-jdk15on:1.58
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-873
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-873
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1.0
>         Environment: Maven 3.5.2, Java 8u151 (32-bit) as well as 9.0 
> (64-bit), Windows 10
>            Reporter: Michael Schierl
>            Priority: Major
>         Attachments: pom.xml
>
>
> To reproduce:
> 1. Create a new directory
> 2. Add attached pom.xml (no other sources required to reproduce; in real 
> world you would add some source that uses BouncyCastle lib, too).
> 3. Run {{mvn package}}
> Actual result:
> Maven hangs after 
> {{[INFO] Building jar: 
> C:\Daten\Eigenes\svn\iota\hang\target\bug-1.0-SNAPSHOT-jar-with-dependencies.jar}}
> , consuming one CPU core.
> Expected result:
> Maven builds a package containing no own source and the dependency 
> (bouncycastle)
> Workaround:
> In maven local repository, edit the .jar file of BouncyCastle and remove the 
> `META-INF\BC*` files. Then the package can be built again. So it seems to be 
> caused somehow by verifying signed jar files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to