[jira] [Commented] (MASSEMBLY-875) Maven 3.x is about 10x slower than 2.6
[
https://issues.apache.org/jira/browse/MASSEMBLY-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348102#comment-16348102
]
Hervé Boutemy commented on MASSEMBLY-875:
-
please share a test project and the result of execution of
maven-buildtime-profiler to give us more precise and reproducible case and more
precise facts
with the textual description, we see the general idea but nothing to really dig
into: help us so we can help you
> Maven 3.x is about 10x slower than 2.6
> --
>
> Key: MASSEMBLY-875
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-875
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Stu
>Priority: Minor
>
> In all our java projects, we have a fairly basic assembly configuration,
> something like this:
> {code:java}
>
> maven-assembly-plugin
> 2.6
>
>
>
> org.x.x.x
>
>
>
> jar-with-dependencies
>
>
>
>
> make-assembly
> package
>
> single
>
>
>
> {code}
> They all take about 10x longer with any 3.x.x version of the maven assembly
> plugin than the 2.6 version.
> This has been noticed by others:
> [https://stackoverflow.com/questions/9009232/what-sort-of-configuration-issues-or-problems-might-make-maven-assembly-plugin-g/24519615#24519615]
> But not reported as a bug that I could find.
> Although I could only justify "Minor" for the priority, this is really is a
> blocker for us moving to 3.x.x
> The upgrade is just not worth taking your build from < 10 sec to > 50 sec.
> (For this particular build, it went from about ~ 7 sec to ~ 57 sec.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPOM-182) remove Google+ button
[ https://issues.apache.org/jira/browse/MPOM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-182: --- Description: and Facebook Like that was tested in MPOM-181 see discussion on dev@maven https://lists.apache.org/thread.html/3dfc1bd7ec798ca5d6b3ebde9d1efa96fa416320e43fb7d839e7dd49@%3Cdev.maven.apache.org%3E > remove Google+ button > - > > Key: MPOM-182 > URL: https://issues.apache.org/jira/browse/MPOM-182 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > > and Facebook Like that was tested in MPOM-181 > see discussion on dev@maven > https://lists.apache.org/thread.html/3dfc1bd7ec798ca5d6b3ebde9d1efa96fa416320e43fb7d839e7dd49@%3Cdev.maven.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-182) remove Google+ button
[ https://issues.apache.org/jira/browse/MPOM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-182. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-parent.git=commit=0791ace4d4fa33733b0be652f9ce21fb110ed7e0 > remove Google+ button > - > > Key: MPOM-182 > URL: https://issues.apache.org/jira/browse/MPOM-182 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPOM-181) add Facebook Like button to skin
[ https://issues.apache.org/jira/browse/MPOM-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347809#comment-16347809 ] Hudson commented on MPOM-181: - Build succeeded in Jenkins: Maven TLP » maven-parent » master #59 See https://builds.apache.org/job/maven-box/job/maven-parent/job/master/59/ > add Facebook Like button to skin > > > Key: MPOM-181 > URL: https://issues.apache.org/jira/browse/MPOM-181 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > > http://developers.facebook.com/docs/reference/plugins/like/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-176) Upgrade extra-enforcer-rules to 1.0-beta-7
[ https://issues.apache.org/jira/browse/MPOM-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-176. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-parent.git=commit=a01ffbd9994104d007710f320e9e57863b8e2f6f > Upgrade extra-enforcer-rules to 1.0-beta-7 > -- > > Key: MPOM-176 > URL: https://issues.apache.org/jira/browse/MPOM-176 > Project: Maven POMs > Issue Type: Dependency upgrade >Affects Versions: MAVEN-31 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-179) update sonar url to https://builds.apache.org/analysis/
[ https://issues.apache.org/jira/browse/MPOM-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-179. -- Resolution: Fixed Assignee: Hervé Boutemy https://gitbox.apache.org/repos/asf?p=maven-parent.git=commit=259d51cc09feea4e6eae130e7741621939d858d1 > update sonar url to https://builds.apache.org/analysis/ > --- > > Key: MPOM-179 > URL: https://issues.apache.org/jira/browse/MPOM-179 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > > current value: [https://analysis.apache.org/] > has changed to [https://builds.apache.org/analysis/]: see > [https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MASSEMBLY-875) Maven 3.x is about 10x slower than 2.6
[
https://issues.apache.org/jira/browse/MASSEMBLY-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347731#comment-16347731
]
Stu edited comment on MASSEMBLY-875 at 1/31/18 10:56 PM:
-
[~khmarbaise] - all your questions were already directly answered in the
description.
The only thing that is not directly listed as answer is the memory settings -
but from my maven pom, you can infer that they are the default settings ;)
was (Author: stuatasf):
[~khmarbaise] - all your questions were already directly answered in the
description.
> Maven 3.x is about 10x slower than 2.6
> --
>
> Key: MASSEMBLY-875
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-875
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Stu
>Priority: Minor
>
> In all our java projects, we have a fairly basic assembly configuration,
> something like this:
> {code:java}
>
> maven-assembly-plugin
> 2.6
>
>
>
> org.x.x.x
>
>
>
> jar-with-dependencies
>
>
>
>
> make-assembly
> package
>
> single
>
>
>
> {code}
> They all take about 10x longer with any 3.x.x version of the maven assembly
> plugin than the 2.6 version.
> This has been noticed by others:
> [https://stackoverflow.com/questions/9009232/what-sort-of-configuration-issues-or-problems-might-make-maven-assembly-plugin-g/24519615#24519615]
> But not reported as a bug that I could find.
> Although I could only justify "Minor" for the priority, this is really is a
> blocker for us moving to 3.x.x
> The upgrade is just not worth taking your build from < 10 sec to > 50 sec.
> (For this particular build, it went from about ~ 7 sec to ~ 57 sec.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MASSEMBLY-875) Maven 3.x is about 10x slower than 2.6
[
https://issues.apache.org/jira/browse/MASSEMBLY-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347731#comment-16347731
]
Stu commented on MASSEMBLY-875:
---
[~khmarbaise] - all your questions were already directly answered in the
description.
> Maven 3.x is about 10x slower than 2.6
> --
>
> Key: MASSEMBLY-875
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-875
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Stu
>Priority: Minor
>
> In all our java projects, we have a fairly basic assembly configuration,
> something like this:
> {code:java}
>
> maven-assembly-plugin
> 2.6
>
>
>
> org.x.x.x
>
>
>
> jar-with-dependencies
>
>
>
>
> make-assembly
> package
>
> single
>
>
>
> {code}
> They all take about 10x longer with any 3.x.x version of the maven assembly
> plugin than the 2.6 version.
> This has been noticed by others:
> [https://stackoverflow.com/questions/9009232/what-sort-of-configuration-issues-or-problems-might-make-maven-assembly-plugin-g/24519615#24519615]
> But not reported as a bug that I could find.
> Although I could only justify "Minor" for the priority, this is really is a
> blocker for us moving to 3.x.x
> The upgrade is just not worth taking your build from < 10 sec to > 50 sec.
> (For this particular build, it went from about ~ 7 sec to ~ 57 sec.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPOM-181) add Facebook Like button to skin
[ https://issues.apache.org/jira/browse/MPOM-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-181. -- Resolution: Won't Fix > add Facebook Like button to skin > > > Key: MPOM-181 > URL: https://issues.apache.org/jira/browse/MPOM-181 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > > http://developers.facebook.com/docs/reference/plugins/like/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPOM-182) remove Google+ button
Hervé Boutemy created MPOM-182: -- Summary: remove Google+ button Key: MPOM-182 URL: https://issues.apache.org/jira/browse/MPOM-182 Project: Maven POMs Issue Type: Task Components: maven Affects Versions: MAVEN-30 Reporter: Hervé Boutemy Assignee: Hervé Boutemy Fix For: MAVEN-31 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-180) add Twitter Follow ASFMavenProject
[ https://issues.apache.org/jira/browse/MPOM-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-180. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-parent.git=commit=9580200c77a88e6ad3ec460d6378e4767999baf9 > add Twitter Follow ASFMavenProject > -- > > Key: MPOM-180 > URL: https://issues.apache.org/jira/browse/MPOM-180 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > > https://twitter.com/ASFMavenProject -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-679) Make all classes package private in internal package
[
https://issues.apache.org/jira/browse/MSHARED-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347622#comment-16347622
]
Hudson commented on MSHARED-679:
Build failed in Jenkins: Maven TLP » maven-artifact-transfer »
MSHARED-679-package-private #3
See
https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-679-package-private/3/
> Make all classes package private in internal package
>
>
> Key: MSHARED-679
> URL: https://issues.apache.org/jira/browse/MSHARED-679
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Make all classes in package {{*.internal}} package only visible and not
> public.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347621#comment-16347621
]
Hudson commented on MSHARED-656:
Build failed in Jenkins: Maven TLP » maven-artifact-transfer »
MSHARED-679-package-private #3
See
https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-679-package-private/3/
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MRELEASE-996) Staging a release cleans up
[
https://issues.apache.org/jira/browse/MRELEASE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347540#comment-16347540
]
Robert Scholte commented on MRELEASE-996:
-
Can you add a link to the location of the quote?
> Staging a release cleans up
> ---
>
> Key: MRELEASE-996
> URL: https://issues.apache.org/jira/browse/MRELEASE-996
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: stage
>Affects Versions: 2.5.3
>Reporter: Ben Maes
>Priority: Major
>
> The wiki's documentation says the following about staging a release:
> {quote}
> After the release is complete, the release.properties and other release files
> will NOT be removed, so that you can still execute a release:rollback if some
> error has been detected and a new candidate must be created after some fixes.
> You just need to use a distinct tag in SCM, or rename the one that has been
> created if the SCM provider supports renaming tags.
> {quote}
> However everytime I use mvn release:stage the last thing showing up on my
> commandline is
> {quote}
> [INFO] Uploaded:
> http://devserver:8081/nexus/content/repositories/release_candidates/be/pensionarchitects/aatest/1.3.8/aatest-1.3.8-javadoc.jar
> (66 KB at 420.2 KB/sec)
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 7.225 s
> [INFO] [INFO] Finished at: 2018-01-31T14:15:21+01:00
> [INFO] [INFO] Final Memory: 25M/310M
> [INFO] [INFO]
>
> [INFO] Cleaning up after release...
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 11.333 s
> [INFO] Finished at: 2018-01-31T14:15:21+01:00
> [INFO] Final Memory: 17M/310M
> [INFO]
>
> {quote}
> Thx
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-4463) Dependency management import should support version ranges.
[
https://issues.apache.org/jira/browse/MNG-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347255#comment-16347255
]
Robert Thornton edited comment on MNG-4463 at 1/31/18 5:43 PM:
---
Does this fix also allow expressions in the version? For example:
{code:xml}
group
artifact
${artifact.version}
pom
import
{code}
was (Author: rptmaestro):
Does this fix also allow expressions in the version? For example:
groupartifact${artifact.version}pomimport
> Dependency management import should support version ranges.
> ---
>
> Key: MNG-4463
> URL: https://issues.apache.org/jira/browse/MNG-4463
> Project: Maven
> Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: Maven 2.2.1
>Reporter: Rob ten Hove
>Priority: Major
> Fix For: 3.5.x-candidate
>
>
> Version ranges cannot be used for artifacts with {{import}} scope. If a
> version range is used for such an artifact, Maven cannot find it. Looking at
> the console output shows that it takes the version range as the version,
> without resolving it:
> {noformat}Downloading:
> http://some-repo/group/artifact/[1.0.0,2.0.0)/artifact-[1.0.0,2.0.0).pom{noformat}
> This is the POM snippet:
> {code:xml}
>
>
>
> group
> artifact
> [1.0.0,2.0.0)
>
> pom
> import
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-4463) Dependency management import should support version ranges.
[
https://issues.apache.org/jira/browse/MNG-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347255#comment-16347255
]
Robert Thornton commented on MNG-4463:
--
Does this fix also allow expressions in the version? For example:
groupartifact${artifact.version}pomimport
> Dependency management import should support version ranges.
> ---
>
> Key: MNG-4463
> URL: https://issues.apache.org/jira/browse/MNG-4463
> Project: Maven
> Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: Maven 2.2.1
>Reporter: Rob ten Hove
>Priority: Major
> Fix For: 3.5.x-candidate
>
>
> Version ranges cannot be used for artifacts with {{import}} scope. If a
> version range is used for such an artifact, Maven cannot find it. Looking at
> the console output shows that it takes the version range as the version,
> without resolving it:
> {noformat}Downloading:
> http://some-repo/group/artifact/[1.0.0,2.0.0)/artifact-[1.0.0,2.0.0).pom{noformat}
> This is the POM snippet:
> {code:xml}
>
>
>
> group
> artifact
> [1.0.0,2.0.0)
>
> pom
> import
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MDEPLOY-229) Error injecting: org.apache.maven.artifact.deployer.DefaultArtifactDeployer in Maven 3.3.9
Jakub Bochenski created MDEPLOY-229:
---
Summary: Error injecting:
org.apache.maven.artifact.deployer.DefaultArtifactDeployer in Maven 3.3.9
Key: MDEPLOY-229
URL: https://issues.apache.org/jira/browse/MDEPLOY-229
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.2
Environment: Maven 3.3.9
Reporter: Jakub Bochenski
The stacktrace is huge but I think the gist is:
{code:java}
java.lang.IllegalArgumentException: Can not set
org.eclipse.aether.spi.log.Logger field
org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger to
org.eclipse.aether.internal.impl.slf4j.Slf4jLoggerFactory{code}
Tried the same with Maven 3.5.0 and it works fine.
Full stack trace:
https://gist.github.com/jakub-bochenski/08b7e9dce1823ef55c2335eb7e79fb14
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MRELEASE-996) Staging a release cleans up
Ben Maes created MRELEASE-996:
-
Summary: Staging a release cleans up
Key: MRELEASE-996
URL: https://issues.apache.org/jira/browse/MRELEASE-996
Project: Maven Release Plugin
Issue Type: Bug
Components: stage
Affects Versions: 2.5.3
Reporter: Ben Maes
The wiki's documentation says the following about staging a release:
{quote}
After the release is complete, the release.properties and other release files
will NOT be removed, so that you can still execute a release:rollback if some
error has been detected and a new candidate must be created after some fixes.
You just need to use a distinct tag in SCM, or rename the one that has been
created if the SCM provider supports renaming tags.
{quote}
However everytime I use mvn release:stage the last thing showing up on my
commandline is
{quote}
[INFO] Uploaded:
http://devserver:8081/nexus/content/repositories/release_candidates/be/pensionarchitects/aatest/1.3.8/aatest-1.3.8-javadoc.jar
(66 KB at 420.2 KB/sec)
[INFO] [INFO]
[INFO] [INFO] BUILD SUCCESS
[INFO] [INFO]
[INFO] [INFO] Total time: 7.225 s
[INFO] [INFO] Finished at: 2018-01-31T14:15:21+01:00
[INFO] [INFO] Final Memory: 25M/310M
[INFO] [INFO]
[INFO] Cleaning up after release...
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 11.333 s
[INFO] Finished at: 2018-01-31T14:15:21+01:00
[INFO] Final Memory: 17M/310M
[INFO]
{quote}
Thx
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARCHETYPE-539) Maven archetype:generate hangs on retrieval of archetype-catalog.xml even on offline mode
Franz Allan Valencia See created ARCHETYPE-539:
--
Summary: Maven archetype:generate hangs on retrieval of
archetype-catalog.xml even on offline mode
Key: ARCHETYPE-539
URL: https://issues.apache.org/jira/browse/ARCHETYPE-539
Project: Maven Archetype
Issue Type: Bug
Components: Generator
Affects Versions: 3.0.1
Environment: macOS High Sierra v10.13.1
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T15:58:13+08:00)
Maven home: /opt/maven/active
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.1", arch: "x86_64", family: "mac"
Reporter: Franz Allan Valencia See
Attachments: build.log
*Steps to reproduce*
1.a Have slow connection
1.b.Alternatively, simulate slow connection with
[crapify|https://www.npmjs.com/package/crapify]
1.b.1. Install crapify - {{npm install crapify -g}}
1.b.2. Run crapify - {{crapify --port=5000 --speed=1 start}}
1.b.3. Configure {{~/.m2/settings.xml}} to use crapify
{code:xml}
...
crapify-proxy
true
http
localhost
5000
...
{code}
2. Execute
{code:bash}
$ mvn archetype:generate -DgroupId=com.example -DartifactId=example
-Dversion=1.0-SNAPSHOT -o
{code}
*Expected Behaviour:*
The list of available archetypes would be shown to the user.
_Note: I believe in older versions, only the basic archetypes are shown like
quickstart_
*Actual Behaviour:*
Maven command hangs in this last last line:
{code:bash}
[DEBUG] Searching for remote catalog:
https://repo.maven.apache.org/maven2/archetype-catalog.xml
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
