[jira] [Commented] (MWRAPPER-9) Ability to automatically download JRE
[ https://issues.apache.org/jira/browse/MWRAPPER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223271#comment-17223271 ] Manfred Moser commented on MWRAPPER-9: -- I think thats beyond the scope of the wrapper. there are other tools that can do that. If anything we should make sure that the wrapper fails gracefully with a good error message if not Java is found. From what I recall thats already the case but it might be worth testing again. > Ability to automatically download JRE > - > > Key: MWRAPPER-9 > URL: https://issues.apache.org/jira/browse/MWRAPPER-9 > Project: Maven Wrapper > Issue Type: Bug >Reporter: Yannick Menager >Priority: Normal > > It would be helpful if the wrapper had the ability to download a JRE like > adoptjdk for example > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6971) Upload a Artifact
[ https://issues.apache.org/jira/browse/MNG-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166503#comment-17166503 ] Manfred Moser commented on MNG-6971: Also mvnrepsitory is NOT an official part of Maven Central. Here is the official search [https://search.maven.org/] and the docs [https://central.sonatype.org/] .. specifically you have to be part of the vertica team to be legally allowed to upload a veritca jar.. > Upload a Artifact > - > > Key: MNG-6971 > URL: https://issues.apache.org/jira/browse/MNG-6971 > Project: Maven > Issue Type: Task > Components: Artifacts and Repositories >Reporter: hemanth >Priority: Major > Labels: Artifact, upload > Attachments: vertica-jdbc-10.0.0-0.jar > > > Upload the latest artifact to the the below repo: > "[https://mvnrepository.com/artifact/com.vertica/vertica-jdbc]"; > > The latest artifact for vertica driver can be downloaded from the below link. > [https://www.vertica.com/client_drivers/10.0.x/10.0.0-0/vertica-jdbc-10.0.0-0.jar > > |https://www.vertica.com/client_drivers/10.0.x/10.0.0-0/vertica-jdbc-10.0.0-0.jar%3c/url]I > have also attached the jar in the attachments. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6765) [Regression] tycho pom-less builds fails with 3.6.2
[
https://issues.apache.org/jira/browse/MNG-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954223#comment-16954223
]
Manfred Moser commented on MNG-6765:
I would rather not have to update polyglot to work with 3.6.2 and break
compatibility with 3.6.1 and below but if we have to I am prepared to do
that. Most polyglot users are using the latest version of Maven so it being
busted with 3.6.2 is a problem for jruby community and others. cc [~headius]
> [Regression] tycho pom-less builds fails with 3.6.2
> ---
>
> Key: MNG-6765
> URL: https://issues.apache.org/jira/browse/MNG-6765
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.2
>Reporter: Jonathan Chen
>Priority: Critical
>
> Projects using tycho pom-less builds fail with maven-3.6.2.
> One such example would be using maven-3.6.2 to build Eclipse-4.13, which
> fails pretty early in the build with:
> {noformat}
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation10/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.cdcfoundation11/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.feature/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se12/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se13/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se14/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.j2se15/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase16/.polyglot.build.properties:
> input contained no data @
> [FATAL] Non-readable POM
> /home/jonc/work/ports/freebsd-eclipse/eclipse.platform.releng.aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/.polyglot.build.properties:
> input contained no data @
> ...
> {noformat}
> These errors do not arise with maven-3.6.0 or maven-3.6.1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNG-6788) [Regression] Conversion to guice appears to break polyglot maven
[ https://issues.apache.org/jira/browse/MNG-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser updated MNG-6788: --- Summary: [Regression] Conversion to guice appears to break polyglot maven (was: Conversion to guice appears to break polyglot maven) > [Regression] Conversion to guice appears to break polyglot maven > > > Key: MNG-6788 > URL: https://issues.apache.org/jira/browse/MNG-6788 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.2 >Reporter: Charles Oliver Nutter >Priority: Major > > Very recently, polyglot maven builds have started failing as detailed here: > [https://github.com/takari/polyglot-maven/issues/200] > This failure is new in 3.6.2 and at least one commenter believes it was > caused by the move to guice here: > [https://github.com/apache/maven/commit/353d3eaa8f2be47878f584a7da398572b41d90af] > This has now completely broken the build for many projects that depend on > polyglot-maven. Nothing changed in polyglot to cause this; simply updating to > Maven 3.6.2 will break the build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6685) Convert Maven Model Builder to JSR 330
[
https://issues.apache.org/jira/browse/MNG-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954198#comment-16954198
]
Manfred Moser commented on MNG-6685:
This also breaks polyglot-maven - see
https://issues.apache.org/jira/browse/MNG-6788
> Convert Maven Model Builder to JSR 330
> --
>
> Key: MNG-6685
> URL: https://issues.apache.org/jira/browse/MNG-6685
> Project: Maven
> Issue Type: Sub-task
>Affects Versions: 3.6.1
>Reporter: Joseph Walton
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.6.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Convert all Plexus {{@Component}} classes in {{maven-model-builder}} to JSR
> 330 annotations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6399) Lift JDK minimum to JDK 8
[ https://issues.apache.org/jira/browse/MNG-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518716#comment-16518716 ] Manfred Moser commented on MNG-6399: I dont think we would get much benefit from adopting the module system and it would be a HUGE effort. I am fine with having a policy that is clear and I think we need to ensure it works on LTS versions. I also think it should work on non-LTS version though. E.g. 9 and 10. Adopting the module system looks more like busy work to me to be honest with little prospect for benefits making it worth the effort. > Lift JDK minimum to JDK 8 > - > > Key: MNG-6399 > URL: https://issues.apache.org/jira/browse/MNG-6399 > Project: Maven > Issue Type: Task >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.6.x-candidate > > > I would like to lift the minimum of Maven Core to JDK 8 (I think it's time).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MNG-6399) Lift JDK minimum to JDK 8
[ https://issues.apache.org/jira/browse/MNG-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518716#comment-16518716 ] Manfred Moser edited comment on MNG-6399 at 6/20/18 11:30 PM: -- I dont think we would get much benefit from adopting the module system and it would be a HUGE effort. I am fine with having a policy that is clear and I think we need to ensure it works on LTS versions. I also think it should work on non-LTS version though. E.g. 9 and 10 (which it does) Adopting the module system looks more like busy work to me to be honest with little prospect for benefits making it worth the effort. was (Author: simpligility): I dont think we would get much benefit from adopting the module system and it would be a HUGE effort. I am fine with having a policy that is clear and I think we need to ensure it works on LTS versions. I also think it should work on non-LTS version though. E.g. 9 and 10. Adopting the module system looks more like busy work to me to be honest with little prospect for benefits making it worth the effort. > Lift JDK minimum to JDK 8 > - > > Key: MNG-6399 > URL: https://issues.apache.org/jira/browse/MNG-6399 > Project: Maven > Issue Type: Task >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.6.x-candidate > > > I would like to lift the minimum of Maven Core to JDK 8 (I think it's time).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRESOURCES-240) Add some binnary types to nonFilteredFileExtension by default
[ https://issues.apache.org/jira/browse/MRESOURCES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279103#comment-16279103 ] Manfred Moser commented on MRESOURCES-240: -- I think this should NOT be implemented. Users can set that themselves as needed already and whatever defaults we come up with might be wrong for some users and incomplete for others. This does not really solve a problem but instead creates more complexity. > Add some binnary types to nonFilteredFileExtension by default > --- > > Key: MRESOURCES-240 > URL: https://issues.apache.org/jira/browse/MRESOURCES-240 > Project: Maven Resources Plugin > Issue Type: Improvement > Components: filtering >Reporter: Flávio Casas de Arcega >Priority: Minor > Labels: easyfix, patch > > Hi! > I had problems with filtering binnary resources, fonts and icons from my > application where corrupted during the build process. > To solve, I added this configuration to the maven-resources-plugin: > > > > maven-resources-plugin > > > > svg > > woff > > woff2 > > ttf > > eot > > otf > > > > > > And I was wondering if this binnary types coudn't be excluded from filters by > default. > I think It would be possible, changing the > org.apache.maven.shared.maven-filtering plugin by applying this patch to the > org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering class: > 79a80,85 > > this.defaultNonFilteredFileExtensions.add( "svg" ); > > this.defaultNonFilteredFileExtensions.add( "woff" ); > > this.defaultNonFilteredFileExtensions.add( "woff2" ); > > this.defaultNonFilteredFileExtensions.add( "ttf" ); > > this.defaultNonFilteredFileExtensions.add( "eot" ); > > this.defaultNonFilteredFileExtensions.add( "otf" ); > Only a suggestion, thanks 4 all... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MNGSITE-193) Questionable tip for using multiple repositories
[
https://issues.apache.org/jira/browse/MNGSITE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Moser reassigned MNGSITE-193:
-
Assignee: (was: Manfred Moser)
> Questionable tip for using multiple repositories
>
>
> Key: MNGSITE-193
> URL: https://issues.apache.org/jira/browse/MNGSITE-193
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Robert Wruck
>Priority: Minor
>
> In the Guide to using Multiple Repositories
> (http://maven.apache.org/guides/mini/guide-multiple-repositories.html) it is
> stated that
> {quote}
> The repositories element is inherited so you would usually specify the
> repositories to use for a group of projects by defining a repositories
> element at the top of your inheritance chain.
> {quote}
> It is quite obvious that this won't work since the parent POM for a project
> would need to be fetched from a repository whose location is specified in the
> parent POM which needs to be fetched from a repository whose location is
> specified in the parent POM ... etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MRESOLVER-29. -- Resolution: Fixed > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-37) Release ant-tasks
[ https://issues.apache.org/jira/browse/MRESOLVER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275344#comment-16275344 ] Manfred Moser commented on MRESOLVER-37: Source is now in the new repo https://github.com/apache/maven-resolver-ant-tasks and a release can be started from my perspective. > Release ant-tasks > - > > Key: MRESOLVER-37 > URL: https://issues.apache.org/jira/browse/MRESOLVER-37 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser > > We need to release version 1.1.0 of the ant-tasks. They are not released or > at least can not be found in Central. > http://repo1.maven.org/maven2/org/apache/maven/resolver/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275342#comment-16275342 ] Manfred Moser commented on MRESOLVER-29: CI setup now exists. I deleted the ant-tasks branch in the original repo. The new repo is ready to be used for a release for which I created https://issues.apache.org/jira/browse/MRESOLVER-37 > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MRESOLVER-37) Release ant-tasks
[ https://issues.apache.org/jira/browse/MRESOLVER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser updated MRESOLVER-37: --- Description: We need to release version 1.1.0 of the ant-tasks. They are not released or at least can not be found in Central. http://repo1.maven.org/maven2/org/apache/maven/resolver/ was:We need to release version 1.1.0 of the ant-tasks. They are not released or at least can not be found in Central. > Release ant-tasks > - > > Key: MRESOLVER-37 > URL: https://issues.apache.org/jira/browse/MRESOLVER-37 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser > > We need to release version 1.1.0 of the ant-tasks. They are not released or > at least can not be found in Central. > http://repo1.maven.org/maven2/org/apache/maven/resolver/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MRESOLVER-37) Release ant-tasks
Manfred Moser created MRESOLVER-37: -- Summary: Release ant-tasks Key: MRESOLVER-37 URL: https://issues.apache.org/jira/browse/MRESOLVER-37 Project: Maven Resolver Issue Type: Task Components: ant tasks Reporter: Manfred Moser We need to release version 1.1.0 of the ant-tasks. They are not released or at least can not be found in Central. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266195#comment-16266195 ] Manfred Moser commented on MRESOLVER-29: We decided to move the ant tasks to new top level repo. This is now done and available at https://github.com/apache/maven-resolver-ant-tasks and gitbox. For this issue I think the only thing missing are probably changes for CI setup (not sure who can do that) and deleting the branch in the old repo. At this stage the build works and looking at Central I think there is no 1.1.0 release of the ant tasks (or any for that matter). http://repo1.maven.org/maven2/org/apache/maven/resolver/ I think we should cut that release (and do that as a separate issue) > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MRESOLVER-28. -- Resolution: Fixed demos branches deleted now as well > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265878#comment-16265878 ] Manfred Moser commented on MRESOLVER-28: So should we delete the demos branch and close the issue? > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263788#comment-16263788 ] Manfred Moser commented on MRESOLVER-29: The related move of the demos is completed. > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263787#comment-16263787 ] Manfred Moser commented on MRESOLVER-29: We had a longer discussion about this on the dev mailing list and it turns out that there is a ciruclar dependency between maven-resolver, maven (maven-resolver-provider to be precise) and maven-resolver-ant-task. Breaking this up is too much work for now. As a result we came to the conclusion to either leave the ant tasks in the branch for now or give it a separate top level repository. I will see what it takes to get it its own repo. > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263782#comment-16263782 ] Manfred Moser edited comment on MRESOLVER-28 at 11/23/17 4:11 AM: -- I also cleaned up all remaining branches, Last task is to delete the now defunct demos branch. Should I do that now? Or do we do that after the next release? How do we avoid forgetting? All temporary branches are already cleaned up. was (Author: simpligility): I also cleaned up all remaining branches, Last task is to delete the now defunct demos branch. Should I do that now? Or do we do that after the next release? How do we avoid forgetting? > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263782#comment-16263782 ] Manfred Moser commented on MRESOLVER-28: I also cleaned up all remaining branches, Last task is to delete the now defunct demos branch. Should I do that now? Or do we do that after the next release? How do we avoid forgetting? > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263781#comment-16263781 ] Manfred Moser commented on MRESOLVER-28: Commits https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d and earlier > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263779#comment-16263779 ] Manfred Moser edited comment on MRESOLVER-28 at 11/23/17 4:06 AM: -- This is now all done and pushed to master including complete history and adaptations on pom files to use reactor resolver version and so on. See more in commit history. was (Author: simpligility): THis is now all done and pushed to master including complete history and adaptations on pom files to use reactor resolver version and so on. See more in commit history. > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263779#comment-16263779 ] Manfred Moser commented on MRESOLVER-28: THis is now all done and pushed to master including complete history and adaptations on pom files to use reactor resolver version and so on. See more in commit history. > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253841#comment-16253841 ] Manfred Moser edited comment on MRESOLVER-29 at 11/15/17 5:48 PM: -- The ant tasks are published (installed and deployed) as normal so there is no issue. The second issue indicated seems more a code and dependency problem than a reason to keep it in a separate branch. Looking at the pom the shade plugin is used to create an uber jar and there is all sorts of funky relocation and stuff happening. I have a feeling we should merge this all into one branch and then work on cleaning this uber jar up more. mavenVersion is already set at 3.5.0 and we should therefore be able to get rid of a lot of this magic since all the relocation work is no longer needed with 3.5.2 and in the ant runtime context it can all be just consistently with newer versions instead of trying be compatible with old maven versions and dealing with the funky moves of resolver to sonatype, to eclipse and back to apache. I think if the ant tasks are not releasable at any time the resolver should not be released either and having them all in one multi module project expresses that idea better. The main reason I did the change is so that it is easier to see the code all in one place and work with it as well as cleaner for the user and to maintain as an overall project. Wdyt? Also if there are specific changes for the ant task I can do to fix the dependency version issues I can attack them after the merge and prior to the next release. was (Author: simpligility): The ant tasks are published (installed and deployed) as normal so there is no issue. The second issue indicated seems more a code and dependency problem than a reason to keep it in a separate branch. Looking at the pom the shade plugin is used to create an uber jar and there is all sorts of funky relocation and stuff happening. I have a feeling we should merge this all into one branch and then work on cleaning this uber jar up more. mavenVersion is already set at 3.5.0 and we should therefore be able to get rid of a lot of this magic since all the relocation work is no longer needed with 3.5.2 and in the ant runtime context it can all be just consistently with newer versions instead of trying be compatible with old maven versions. I think if the ant tasks are not releasable at any time the resolver should not be released either and having them all in one multi module project expresses that idea better. The main reason I did the change is so that it is easier to see the code all in one place and work with it as well as cleaner for the user and to maintain as an overall project. Wdyt? Also if there are specific changes for the ant task I can do to fix the dependency version issues I can attack them after the merge and prior to the next release. > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253841#comment-16253841 ] Manfred Moser edited comment on MRESOLVER-29 at 11/15/17 5:47 PM: -- The ant tasks are published (installed and deployed) as normal so there is no issue. The second issue indicated seems more a code and dependency problem than a reason to keep it in a separate branch. Looking at the pom the shade plugin is used to create an uber jar and there is all sorts of funky relocation and stuff happening. I have a feeling we should merge this all into one branch and then work on cleaning this uber jar up more. mavenVersion is already set at 3.5.0 and we should therefore be able to get rid of a lot of this magic since all the relocation work is no longer needed with 3.5.2 and in the ant runtime context it can all be just consistently with newer versions instead of trying be compatible with old maven versions. I think if the ant tasks are not releasable at any time the resolver should not be released either and having them all in one multi module project expresses that idea better. The main reason I did the change is so that it is easier to see the code all in one place and work with it as well as cleaner for the user and to maintain as an overall project. Wdyt? Also if there are specific changes for the ant task I can do to fix the dependency version issues I can attack them after the merge and prior to the next release. was (Author: simpligility): The ant tasks are published (installed and deployed) as normal so there is no issue. The second issue indicated more a code and dependency problem than a reason to keep it in a separate branch. Looking at the pom the shade plugin is used to create an uber jar and there is all sorts of funky relocation and stuff happening. I have a feeling we should merge this all into one branch and then work on cleaning this uber jar up more. mavenVersion is already set at 3.5.0 and we should therefore be able to get rid of a lot of this magic since all the relocation work is no longer needed with 3.5.2 and in the ant runtime context it can all be just consistently with newer versions instead of trying be compatible with old maven versions. I think if the ant tasks are not releasable at any time the resolver should not be released either and having them all in one multi module project expresses that idea better. The main reason I did the change is so that it is easier to see the code all in one place and work with it as well as cleaner for the user and to maintain as an overall project. Wdyt? Also if there are specific changes for the ant task I can do to fix the dependency version issues I can attack them after the merge and prior to the next release. > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253841#comment-16253841 ] Manfred Moser commented on MRESOLVER-29: The ant tasks are published (installed and deployed) as normal so there is no issue. The second issue indicated more a code and dependency problem than a reason to keep it in a separate branch. Looking at the pom the shade plugin is used to create an uber jar and there is all sorts of funky relocation and stuff happening. I have a feeling we should merge this all into one branch and then work on cleaning this uber jar up more. mavenVersion is already set at 3.5.0 and we should therefore be able to get rid of a lot of this magic since all the relocation work is no longer needed with 3.5.2 and in the ant runtime context it can all be just consistently with newer versions instead of trying be compatible with old maven versions. I think if the ant tasks are not releasable at any time the resolver should not be released either and having them all in one multi module project expresses that idea better. The main reason I did the change is so that it is easier to see the code all in one place and work with it as well as cleaner for the user and to maintain as an overall project. Wdyt? Also if there are specific changes for the ant task I can do to fix the dependency version issues I can attack them after the merge and prior to the next release. > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253785#comment-16253785 ] Manfred Moser commented on MRESOLVER-28: Demos are not deployed as the plugin is skipped. This is the same as it is in the current branch. > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245242#comment-16245242 ] Manfred Moser commented on MRESOLVER-28: Turns out the rat failures are due .checkstyle files that are created somehow. Once I delete them all is good.. > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245224#comment-16245224 ] Manfred Moser edited comment on MRESOLVER-28 at 11/9/17 5:33 AM: - Further cleanup done. CI build passes. Local site build also worked. https://builds.apache.org/job/maven-resolver-jenkinsfile/job/master-all/ One issue is that for local build I have to skip rat plugin but that seems to be the case for master for me as well. What do we need to do as a next step in terms of review? I will ask on the maven dev list but essentially my steps would include - doc updates in readme files and site sources where necessary - other changes required I cant think of atm - merge master-all into master - delete now redundant branchs ant-tasks, ant-tasks-folder, demos, demos-folder, master-all - do a release including binaries deploy and site publish was (Author: simpligility): Further cleanup done. CI build passes. Local site build also worked. https://builds.apache.org/job/maven-resolver-jenkinsfile/job/master-all/ What do we need to do as a next step in terms of review? I will ask on the maven dev list but essentially my steps would include - doc updates in readme files and site sources where necessary - other changes required I cant think of atm - merge master-all into master - delete now redundant branchs ant-tasks, ant-tasks-folder, demos, demos-folder, master-all - do a release including binaries deploy and site publish > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245224#comment-16245224 ] Manfred Moser commented on MRESOLVER-28: Further cleanup done. CI build passes. Local site build also worked. https://builds.apache.org/job/maven-resolver-jenkinsfile/job/master-all/ What do we need to do as a next step in terms of review? I will ask on the maven dev list but essentially my steps would include - doc updates in readme files and site sources where necessary - other changes required I cant think of atm - merge master-all into master - delete now redundant branchs ant-tasks, ant-tasks-folder, demos, demos-folder, master-all - do a release including binaries deploy and site publish > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245219#comment-16245219 ] Manfred Moser commented on MRESOLVER-29: More comments in linked issue > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245174#comment-16245174 ] Manfred Moser commented on MRESOLVER-28: The linked issue and its work is covered in this issue. > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245173#comment-16245173 ] Manfred Moser commented on MRESOLVER-28: Thin integration with simple module addition is done and build works. Pushed into master-all branch. WIll improve versioning and so on next. > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245170#comment-16245170 ] Manfred Moser commented on MRESOLVER-29: Moved into subfolder and pushed into new branch ant-tasks-folder > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245171#comment-16245171 ] Manfred Moser commented on MRESOLVER-28: Moved into new folder and pushed in new branch demos-folder > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MRESOLVER-28: -- Assignee: Manfred Moser > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser >Assignee: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MRESOLVER-29) Move ant tasks into master as new modules
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MRESOLVER-29: -- Assignee: Manfred Moser > Move ant tasks into master as new modules > - > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MRESOLVER-29) Move ant tasks into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser updated MRESOLVER-29: --- Summary: Move ant tasks into master as new module (was: Move ant tasks into master as new modules) > Move ant tasks into master as new module > > > Key: MRESOLVER-29 > URL: https://issues.apache.org/jira/browse/MRESOLVER-29 > Project: Maven Resolver > Issue Type: Task > Components: ant tasks >Reporter: Manfred Moser >Assignee: Manfred Moser > > The ant tasks of Maven Resolver are currently in a separate branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MRESOLVER-28) Move demos into master as new module
[ https://issues.apache.org/jira/browse/MRESOLVER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser updated MRESOLVER-28: --- Component/s: demo > Move demos into master as new module > > > Key: MRESOLVER-28 > URL: https://issues.apache.org/jira/browse/MRESOLVER-28 > Project: Maven Resolver > Issue Type: Task > Components: demo >Reporter: Manfred Moser > > The demos of Maven Resolver are currently in a separate demos branch. This > makes it hard to keep version consistent and is also harder to understand and > locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MRESOLVER-29) Move ant tasks into master as new modules
Manfred Moser created MRESOLVER-29: -- Summary: Move ant tasks into master as new modules Key: MRESOLVER-29 URL: https://issues.apache.org/jira/browse/MRESOLVER-29 Project: Maven Resolver Issue Type: Task Components: ant tasks Reporter: Manfred Moser The ant tasks of Maven Resolver are currently in a separate branch. This makes it hard to keep version consistent and is also harder to understand and locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MRESOLVER-28) Move demos into master as new module
Manfred Moser created MRESOLVER-28: -- Summary: Move demos into master as new module Key: MRESOLVER-28 URL: https://issues.apache.org/jira/browse/MRESOLVER-28 Project: Maven Resolver Issue Type: Task Reporter: Manfred Moser The demos of Maven Resolver are currently in a separate demos branch. This makes it hard to keep version consistent and is also harder to understand and locate for users in apache git and on github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6254) Clarificatin on sorting in Repository Metadata
[ https://issues.apache.org/jira/browse/MNG-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082666#comment-16082666 ] Manfred Moser commented on MNG-6254: I do not think it is realistic to reprocess all existing metadata files based on some new desired "correct" behavior. Instead I propose to document how it actually works > Clarificatin on sorting in Repository Metadata > - > > Key: MNG-6254 > URL: https://issues.apache.org/jira/browse/MNG-6254 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.5.0 >Reporter: Markus Karg > > The document > http://maven.apache.org/ref/3.3.9/maven-repository-metadata/repository-metadata.html > explains that does contain a _List_, hence is _sorted_. > When pulling _real _metadata from Maven Central, e. g. > http://repo.maven.apache.org/maven2/javax/ws/rs/jsr311-api/maven-metadata.xml, > it is apparent that the content of is _not_ sorted (in this > example, 1.1-ea is listed _after_ 1.1, which is a violation of the sorting, > because -ea must be listed _before_ 1.1). So effectively Maven Central > devliers _unsorted_ versions. > Also, the effectively listed XSD > http://maven.apache.org/xsd/metadata-1.1.0.xsd is nonexistent, so cannot be > looked but whether Maven Central is wrong, or whether actually the > specification should say it must be Set instead of List. > To sum up, there should be a clarification whether must be sorted > according to the Maven Version Numbering Schema, whether it must be Set vs > List, and whether the missing XSD should be uploaded. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6254) Clarificatin on sorting in Repository Metadata
[ https://issues.apache.org/jira/browse/MNG-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081735#comment-16081735 ] Manfred Moser commented on MNG-6254: Afaik it is sorted by time of deployment... each deployment (independent of version) appends as new entry. So its sorted .. just not the way you might want it. > Clarificatin on sorting in Repository Metadata > - > > Key: MNG-6254 > URL: https://issues.apache.org/jira/browse/MNG-6254 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.5.0 >Reporter: Markus Karg > > The document > http://maven.apache.org/ref/3.3.9/maven-repository-metadata/repository-metadata.html > explains that does contain a _List_, hence is _sorted_. > When pulling _real _metadata from Maven Central, e. g. > http://repo.maven.apache.org/maven2/javax/ws/rs/jsr311-api/maven-metadata.xml, > it is apparent that the content of is _not_ sorted (in this > example, 1.1-ea is listed _after_ 1.1, which is a violation of the sorting, > because -ea must be listed _before_ 1.1). So effectively Maven Central > devliers _unsorted_ versions. > Also, the effectively listed XSD > http://maven.apache.org/xsd/metadata-1.1.0.xsd is nonexistent, so cannot be > looked but whether Maven Central is wrong, or whether actually the > specification should say it must be Set instead of List. > To sum up, there should be a clarification whether must be sorted > according to the Maven Version Numbering Schema, whether it must be Set vs > List, and whether the missing XSD should be uploaded. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.
[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985467#comment-15985467 ] Manfred Moser commented on MNG-6112: I agree that this seems like a bad idea. If anything I would go with always .. provided its performance overhead is not too bad. I would leave as is for now though. > Central repository in the 4.0.0 super POM should declare update policy > 'never'. > --- > > Key: MNG-6112 > URL: https://issues.apache.org/jira/browse/MNG-6112 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0-beta-1 >Reporter: Christian Schulte > Fix For: 3.5.1-candidate > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNGSITE-289) Broken Link in Documentation
[ https://issues.apache.org/jira/browse/MNGSITE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342542#comment-15342542 ] Manfred Moser commented on MNGSITE-289: --- Correct link is http://books.sonatype.com/mvnex-book/reference/multimodule.html in case [~khmarbaise] beats me to it ;-) > Broken Link in Documentation > > > Key: MNGSITE-289 > URL: https://issues.apache.org/jira/browse/MNGSITE-289 > Project: Maven Project Web Site > Issue Type: Bug > Environment: > https://maven.apache.org/guides/mini/guide-multiple-modules.html >Reporter: Francesco La Torre >Assignee: Manfred Moser >Priority: Minor > > https://maven.apache.org/guides/mini/guide-multiple-modules.html > The provided link to "Chapter 8. A Multi-module Project (Maven by Example)" > which goes to > "http://www.sonatype.com/books/mvnex-book/reference/multimodule.html"; is > broken. > On the sonatype site i see only a 404 message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-289) Broken Link in Documentation
[ https://issues.apache.org/jira/browse/MNGSITE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342003#comment-15342003 ] Manfred Moser commented on MNGSITE-289: --- I will fix that later this week. > Broken Link in Documentation > > > Key: MNGSITE-289 > URL: https://issues.apache.org/jira/browse/MNGSITE-289 > Project: Maven Project Web Site > Issue Type: Bug > Environment: > https://maven.apache.org/guides/mini/guide-multiple-modules.html >Reporter: Francesco La Torre >Assignee: Manfred Moser >Priority: Minor > > https://maven.apache.org/guides/mini/guide-multiple-modules.html > The provided link to "Chapter 8. A Multi-module Project (Maven by Example)" > which goes to > "http://www.sonatype.com/books/mvnex-book/reference/multimodule.html"; is > broken. > On the sonatype site i see only a 404 message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MNGSITE-289) Broken Link in Documentation
[ https://issues.apache.org/jira/browse/MNGSITE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MNGSITE-289: - Assignee: Manfred Moser > Broken Link in Documentation > > > Key: MNGSITE-289 > URL: https://issues.apache.org/jira/browse/MNGSITE-289 > Project: Maven Project Web Site > Issue Type: Bug > Environment: > https://maven.apache.org/guides/mini/guide-multiple-modules.html >Reporter: Francesco La Torre >Assignee: Manfred Moser >Priority: Minor > > https://maven.apache.org/guides/mini/guide-multiple-modules.html > The provided link to "Chapter 8. A Multi-module Project (Maven by Example)" > which goes to > "http://www.sonatype.com/books/mvnex-book/reference/multimodule.html"; is > broken. > On the sonatype site i see only a 404 message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-118) Enforce strong GPG signatures by default
[
https://issues.apache.org/jira/browse/MPOM-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289481#comment-15289481
]
Manfred Moser commented on MPOM-118:
I agree with this proposal.
> Enforce strong GPG signatures by default
>
>
> Key: MPOM-118
> URL: https://issues.apache.org/jira/browse/MPOM-118
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-17
>Reporter: Christopher Tubbs
>
> maven-gpg-plugin configuration could be improved a bit so that ASF releases
> are not weakened by a user's weak personal configuration.
> I suggest adding something like the following to maven-gpg-plugin's
> configuration in the pluginManagement section:
> {code:xml}
>
> --digest-algo=SHA512
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6006) Import Aether to Maven codebase
[ https://issues.apache.org/jira/browse/MNG-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254935#comment-15254935 ] Manfred Moser commented on MNG-6006: This should somehow continue to provide the Aether Ant Tasks as they are very useful tool for migration from Ant to Maven (and that still happens a LOT). > Import Aether to Maven codebase > --- > > Key: MNG-6006 > URL: https://issues.apache.org/jira/browse/MNG-6006 > Project: Maven > Issue Type: Task >Reporter: Hervé Boutemy > > After [Aether termination at > Eclipse|https://projects.eclipse.org/projects/technology.aether/reviews/termination-review], > import Aether codebase to Maven codebase -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-167) Maven Getting Started Guide should clarify SNAPSHOT qualifier of 'version' element precedes release
[ https://issues.apache.org/jira/browse/MNGSITE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095642#comment-15095642 ] Manfred Moser commented on MNGSITE-167: --- Patch reviewed and committed. http://svn.apache.org/viewvc?rev=1724356&view=rev > Maven Getting Started Guide should clarify SNAPSHOT qualifier of 'version' > element precedes release > --- > > Key: MNGSITE-167 > URL: https://issues.apache.org/jira/browse/MNGSITE-167 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Dan Rollo >Assignee: Manfred Moser > Attachments: MNGSITE_167_add_missing_description_of_SNAPSHOT.patch > > > In the "Maven Getting Started Guide" > http://maven.apache.org/guides/getting-started/index.html > (linked to as: "Getting Started Tutorial" from: > http://maven.apache.org/users/index.html, > which is linked to as: "Use Maven" from: http://maven.apache.org/ > ) > under the link: "How do I make my first Maven project?", the description > bullet for the "version" pom element mentions SNAPSHOT as follows: > version This element indicates the version of the artifact generated by the > project. Maven goes a long way to help you with version management and you > will often see the SNAPSHOT designator in a version, which indicates that a > project is in a state of development. We will discuss the use of snapshots > and how they work further on in this guide. > Though a later description is promised, the concept that a SNAPSHOT version > "preceeds" the non-SNAPSHOT (aka "release") version is never mentioned in > this document. > I have had to describe this fact to a number of people as well, so I think > this 'version' element doc should be changed to mention a SNAPSHOT precedes a > release (or some new section added elsewhere in this doc to clarify this > point). > Here are some of the other responses from the user list that might help to > come up with a clear doco snippet: > 1. > A SNAPSHOT is the development version before producing the release. > A SNAPSHOT is older than its release > 1.0.0-SNAPSHOT -> 1.0.0-> 1.0.1-SNAPSHOT -> 1.0.1 -> .. > 2. > 1.0.0 is newer than 1.0.0-SNAPSHOT > 3. > x.x.x-SNAPSHOT is the precursor to x.x.x The SNAPSHOT value is used to allow > the version to refer to the 'latest' code along a branch and provides no > guarantee that the code is stable or unchanging. The release process changes > x.x.x-SNAPSHOT to x.x.x, freezes the code to provide a guarantee that the > version is unchanging. The release process should also move the version to > x.x.x+1-SNAPSHOT. > > It follows that any released code cannot be dependent on SNAPSHOT code > Below is a thread snippet from maven users mailing list: > Subject: > Re: 1.0.0-SNAPSHOT considered older than 1.0.0? > From: > > Date: > 12/20/2012 10:09 AM > To: > "Maven Users List" > On Thu, 20 Dec 2012 15:08:26 +0100 > Arnaud Héritier wrote: > > I don't have the time to check the doc but if it's not in, this is a big > > error (don't hesitate to open an issue) > > A SNAPSHOT is the development version before producing the release. > > A SNAPSHOT is older than its release > > 1.0.0-SNAPSHOT -> 1.0.0-> 1.0.1-SNAPSHOT -> 1.0.1 -> .. > Thanks to all that replied. > The missing documentation I was referring to was: > > http://maven.apache.org/guides/getting-started/index.html#How_do_I_make_my_first_Maven_project > Note: > "We will discuss the use of snapshots and how they work further on in > this guide" > The word "snapshots" doesn't appear again on the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNGSITE-167) Maven Getting Started Guide should clarify SNAPSHOT qualifier of 'version' element precedes release
[ https://issues.apache.org/jira/browse/MNGSITE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNGSITE-167. - Resolution: Fixed > Maven Getting Started Guide should clarify SNAPSHOT qualifier of 'version' > element precedes release > --- > > Key: MNGSITE-167 > URL: https://issues.apache.org/jira/browse/MNGSITE-167 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Dan Rollo >Assignee: Manfred Moser > Attachments: MNGSITE_167_add_missing_description_of_SNAPSHOT.patch > > > In the "Maven Getting Started Guide" > http://maven.apache.org/guides/getting-started/index.html > (linked to as: "Getting Started Tutorial" from: > http://maven.apache.org/users/index.html, > which is linked to as: "Use Maven" from: http://maven.apache.org/ > ) > under the link: "How do I make my first Maven project?", the description > bullet for the "version" pom element mentions SNAPSHOT as follows: > version This element indicates the version of the artifact generated by the > project. Maven goes a long way to help you with version management and you > will often see the SNAPSHOT designator in a version, which indicates that a > project is in a state of development. We will discuss the use of snapshots > and how they work further on in this guide. > Though a later description is promised, the concept that a SNAPSHOT version > "preceeds" the non-SNAPSHOT (aka "release") version is never mentioned in > this document. > I have had to describe this fact to a number of people as well, so I think > this 'version' element doc should be changed to mention a SNAPSHOT precedes a > release (or some new section added elsewhere in this doc to clarify this > point). > Here are some of the other responses from the user list that might help to > come up with a clear doco snippet: > 1. > A SNAPSHOT is the development version before producing the release. > A SNAPSHOT is older than its release > 1.0.0-SNAPSHOT -> 1.0.0-> 1.0.1-SNAPSHOT -> 1.0.1 -> .. > 2. > 1.0.0 is newer than 1.0.0-SNAPSHOT > 3. > x.x.x-SNAPSHOT is the precursor to x.x.x The SNAPSHOT value is used to allow > the version to refer to the 'latest' code along a branch and provides no > guarantee that the code is stable or unchanging. The release process changes > x.x.x-SNAPSHOT to x.x.x, freezes the code to provide a guarantee that the > version is unchanging. The release process should also move the version to > x.x.x+1-SNAPSHOT. > > It follows that any released code cannot be dependent on SNAPSHOT code > Below is a thread snippet from maven users mailing list: > Subject: > Re: 1.0.0-SNAPSHOT considered older than 1.0.0? > From: > > Date: > 12/20/2012 10:09 AM > To: > "Maven Users List" > On Thu, 20 Dec 2012 15:08:26 +0100 > Arnaud Héritier wrote: > > I don't have the time to check the doc but if it's not in, this is a big > > error (don't hesitate to open an issue) > > A SNAPSHOT is the development version before producing the release. > > A SNAPSHOT is older than its release > > 1.0.0-SNAPSHOT -> 1.0.0-> 1.0.1-SNAPSHOT -> 1.0.1 -> .. > Thanks to all that replied. > The missing documentation I was referring to was: > > http://maven.apache.org/guides/getting-started/index.html#How_do_I_make_my_first_Maven_project > Note: > "We will discuss the use of snapshots and how they work further on in > this guide" > The word "snapshots" doesn't appear again on the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MNGSITE-167) Maven Getting Started Guide should clarify SNAPSHOT qualifier of 'version' element precedes release
[ https://issues.apache.org/jira/browse/MNGSITE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reopened MNGSITE-167: --- Assignee: Manfred Moser > Maven Getting Started Guide should clarify SNAPSHOT qualifier of 'version' > element precedes release > --- > > Key: MNGSITE-167 > URL: https://issues.apache.org/jira/browse/MNGSITE-167 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Dan Rollo >Assignee: Manfred Moser > Attachments: MNGSITE_167_add_missing_description_of_SNAPSHOT.patch > > > In the "Maven Getting Started Guide" > http://maven.apache.org/guides/getting-started/index.html > (linked to as: "Getting Started Tutorial" from: > http://maven.apache.org/users/index.html, > which is linked to as: "Use Maven" from: http://maven.apache.org/ > ) > under the link: "How do I make my first Maven project?", the description > bullet for the "version" pom element mentions SNAPSHOT as follows: > version This element indicates the version of the artifact generated by the > project. Maven goes a long way to help you with version management and you > will often see the SNAPSHOT designator in a version, which indicates that a > project is in a state of development. We will discuss the use of snapshots > and how they work further on in this guide. > Though a later description is promised, the concept that a SNAPSHOT version > "preceeds" the non-SNAPSHOT (aka "release") version is never mentioned in > this document. > I have had to describe this fact to a number of people as well, so I think > this 'version' element doc should be changed to mention a SNAPSHOT precedes a > release (or some new section added elsewhere in this doc to clarify this > point). > Here are some of the other responses from the user list that might help to > come up with a clear doco snippet: > 1. > A SNAPSHOT is the development version before producing the release. > A SNAPSHOT is older than its release > 1.0.0-SNAPSHOT -> 1.0.0-> 1.0.1-SNAPSHOT -> 1.0.1 -> .. > 2. > 1.0.0 is newer than 1.0.0-SNAPSHOT > 3. > x.x.x-SNAPSHOT is the precursor to x.x.x The SNAPSHOT value is used to allow > the version to refer to the 'latest' code along a branch and provides no > guarantee that the code is stable or unchanging. The release process changes > x.x.x-SNAPSHOT to x.x.x, freezes the code to provide a guarantee that the > version is unchanging. The release process should also move the version to > x.x.x+1-SNAPSHOT. > > It follows that any released code cannot be dependent on SNAPSHOT code > Below is a thread snippet from maven users mailing list: > Subject: > Re: 1.0.0-SNAPSHOT considered older than 1.0.0? > From: > > Date: > 12/20/2012 10:09 AM > To: > "Maven Users List" > On Thu, 20 Dec 2012 15:08:26 +0100 > Arnaud Héritier wrote: > > I don't have the time to check the doc but if it's not in, this is a big > > error (don't hesitate to open an issue) > > A SNAPSHOT is the development version before producing the release. > > A SNAPSHOT is older than its release > > 1.0.0-SNAPSHOT -> 1.0.0-> 1.0.1-SNAPSHOT -> 1.0.1 -> .. > Thanks to all that replied. > The missing documentation I was referring to was: > > http://maven.apache.org/guides/getting-started/index.html#How_do_I_make_my_first_Maven_project > Note: > "We will discuss the use of snapshots and how they work further on in > this guide" > The word "snapshots" doesn't appear again on the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work
[ https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047092#comment-15047092 ] Manfred Moser commented on SUREFIRE-1191: - Nice work. Works as expected now ;-) > Run Single Test with Package Name Doesn't work > -- > > Key: SUREFIRE-1191 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1191 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.19 >Reporter: Gunnar Schmidt >Assignee: Tibor Digana > Fix For: 2.19.1 > > > Running the following command works: > mvn test -Dtest=MyTestCaseTest#myTest > This doesn't work (package name included): > mvn test -Dtest=my.package.name.MyTestCaseTest#myTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5944) No implementation for org.eclipse.aether.connector.wagon.WagonConfigurator was bound
[ https://issues.apache.org/jira/browse/MNG-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045778#comment-15045778 ] Manfred Moser commented on MNG-5944: And yes... the groupId of the plugin changed with the release of 4.0.0. It is however the same plugin managed by the same people/team. > No implementation for org.eclipse.aether.connector.wagon.WagonConfigurator > was bound > > > Key: MNG-5944 > URL: https://issues.apache.org/jira/browse/MNG-5944 > Project: Maven > Issue Type: Bug >Affects Versions: 3.3.9 > Environment: Windows 8.1/Java 1.8 JDK & 1.7 JDK/Eclipse Mars 4.5.1 >Reporter: battleblaze101 > > *Step 1* > git clone git://github.com/ecsec/open-ecard.git > *Step2* > cd open-ecard > *Step 3* > git submodule update --init > *Step 4* > mvn clean install > And - crash: > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; > 2015-11-10T17:41:47+01:00) > Maven home: F:\Programs\apache-maven-3.3.9\bin\.. > Java version: 1.8.0_51, vendor: Oracle Corporation > Java home: C:\Program Files (x86)\Java\jdk1.8.0_51\jre > Default locale: en_GB, platform encoding: Cp1252 > OS name: "windows 8.1", version: "6.3", arch: "x86", family: "dos" > [DEBUG] Created new class realm maven.api > [DEBUG] Importing foreign packages into class realm maven.api > [DEBUG] Imported: javax.enterprise.inject.* < plexus.core > [DEBUG] Imported: javax.enterprise.util.* < plexus.core > [DEBUG] Imported: javax.inject.* < plexus.core > [DEBUG] Imported: org.apache.maven.* < plexus.core > [DEBUG] Imported: org.apache.maven.artifact < plexus.core > [DEBUG] Imported: org.apache.maven.classrealm < plexus.core > [DEBUG] Imported: org.apache.maven.cli < plexus.core > [DEBUG] Imported: org.apache.maven.configuration < plexus.core > [DEBUG] Imported: org.apache.maven.exception < plexus.core > [DEBUG] Imported: org.apache.maven.execution < plexus.core > [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core > [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core > [DEBUG] Imported: org.apache.maven.model < plexus.core > [DEBUG] Imported: org.apache.maven.monitor < plexus.core > [DEBUG] Imported: org.apache.maven.plugin < plexus.core > [DEBUG] Imported: org.apache.maven.profiles < plexus.core > [DEBUG] Imported: org.apache.maven.project < plexus.core > [DEBUG] Imported: org.apache.maven.reporting < plexus.core > [DEBUG] Imported: org.apache.maven.repository < plexus.core > [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core > [DEBUG] Imported: org.apache.maven.settings < plexus.core > [DEBUG] Imported: org.apache.maven.toolchain < plexus.core > [DEBUG] Imported: org.apache.maven.usability < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core > [DEBUG] Imported: org.codehaus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.* < plexus.core > [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.component < plexus.core > [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core > [DEBUG] Imported: org.codehaus.plexus.container < plexus.core > [DEBUG] Imported: org.codehaus.plexus.context < plexus.core > [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core > [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core > [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < > plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException > < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < > plexus.core > [DEBUG] Imported: org.eclipse.aether.* < plexus.core > [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core > [DEBUG] Imported: org.eclipse.aether.collection < plexus.core > [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core > [DEBUG] Imported: org.eclipse.aether.graph < plexus.core > [DEBUG] Imported: org.eclipse.aether.impl < plexus.core > [DEBUG] Imported: org.eclipse.aether.installation < plexus.core > [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core > [DEBUG
[jira] [Closed] (MNG-5944) No implementation for org.eclipse.aether.connector.wagon.WagonConfigurator was bound
[ https://issues.apache.org/jira/browse/MNG-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNG-5944. -- Resolution: Invalid Invalid for Maven itself.. > No implementation for org.eclipse.aether.connector.wagon.WagonConfigurator > was bound > > > Key: MNG-5944 > URL: https://issues.apache.org/jira/browse/MNG-5944 > Project: Maven > Issue Type: Bug >Affects Versions: 3.3.9 > Environment: Windows 8.1/Java 1.8 JDK & 1.7 JDK/Eclipse Mars 4.5.1 >Reporter: battleblaze101 > > *Step 1* > git clone git://github.com/ecsec/open-ecard.git > *Step2* > cd open-ecard > *Step 3* > git submodule update --init > *Step 4* > mvn clean install > And - crash: > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; > 2015-11-10T17:41:47+01:00) > Maven home: F:\Programs\apache-maven-3.3.9\bin\.. > Java version: 1.8.0_51, vendor: Oracle Corporation > Java home: C:\Program Files (x86)\Java\jdk1.8.0_51\jre > Default locale: en_GB, platform encoding: Cp1252 > OS name: "windows 8.1", version: "6.3", arch: "x86", family: "dos" > [DEBUG] Created new class realm maven.api > [DEBUG] Importing foreign packages into class realm maven.api > [DEBUG] Imported: javax.enterprise.inject.* < plexus.core > [DEBUG] Imported: javax.enterprise.util.* < plexus.core > [DEBUG] Imported: javax.inject.* < plexus.core > [DEBUG] Imported: org.apache.maven.* < plexus.core > [DEBUG] Imported: org.apache.maven.artifact < plexus.core > [DEBUG] Imported: org.apache.maven.classrealm < plexus.core > [DEBUG] Imported: org.apache.maven.cli < plexus.core > [DEBUG] Imported: org.apache.maven.configuration < plexus.core > [DEBUG] Imported: org.apache.maven.exception < plexus.core > [DEBUG] Imported: org.apache.maven.execution < plexus.core > [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core > [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core > [DEBUG] Imported: org.apache.maven.model < plexus.core > [DEBUG] Imported: org.apache.maven.monitor < plexus.core > [DEBUG] Imported: org.apache.maven.plugin < plexus.core > [DEBUG] Imported: org.apache.maven.profiles < plexus.core > [DEBUG] Imported: org.apache.maven.project < plexus.core > [DEBUG] Imported: org.apache.maven.reporting < plexus.core > [DEBUG] Imported: org.apache.maven.repository < plexus.core > [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core > [DEBUG] Imported: org.apache.maven.settings < plexus.core > [DEBUG] Imported: org.apache.maven.toolchain < plexus.core > [DEBUG] Imported: org.apache.maven.usability < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core > [DEBUG] Imported: org.codehaus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.* < plexus.core > [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.component < plexus.core > [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core > [DEBUG] Imported: org.codehaus.plexus.container < plexus.core > [DEBUG] Imported: org.codehaus.plexus.context < plexus.core > [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core > [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core > [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < > plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException > < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < > plexus.core > [DEBUG] Imported: org.eclipse.aether.* < plexus.core > [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core > [DEBUG] Imported: org.eclipse.aether.collection < plexus.core > [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core > [DEBUG] Imported: org.eclipse.aether.graph < plexus.core > [DEBUG] Imported: org.eclipse.aether.impl < plexus.core > [DEBUG] Imported: org.eclipse.aether.installation < plexus.core > [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core > [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core > [DEBUG] Imported: org.eclipse.aether.repository < plexus.core > [DEBUG] Imported:
[jira] [Commented] (MNG-5944) No implementation for org.eclipse.aether.connector.wagon.WagonConfigurator was bound
[ https://issues.apache.org/jira/browse/MNG-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045769#comment-15045769 ] Manfred Moser commented on MNG-5944: This is a VERY old version of the Android Maven Plugin. You should NOT be using it anymore. Please update to a new version and if you still find issues file it with the plugin project. More information at http://simpligility.github.io/android-maven-plugin/report-issue.html > No implementation for org.eclipse.aether.connector.wagon.WagonConfigurator > was bound > > > Key: MNG-5944 > URL: https://issues.apache.org/jira/browse/MNG-5944 > Project: Maven > Issue Type: Bug >Affects Versions: 3.3.9 > Environment: Windows 8.1/Java 1.8 JDK & 1.7 JDK/Eclipse Mars 4.5.1 >Reporter: battleblaze101 > > *Step 1* > git clone git://github.com/ecsec/open-ecard.git > *Step2* > cd open-ecard > *Step 3* > git submodule update --init > *Step 4* > mvn clean install > And - crash: > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; > 2015-11-10T17:41:47+01:00) > Maven home: F:\Programs\apache-maven-3.3.9\bin\.. > Java version: 1.8.0_51, vendor: Oracle Corporation > Java home: C:\Program Files (x86)\Java\jdk1.8.0_51\jre > Default locale: en_GB, platform encoding: Cp1252 > OS name: "windows 8.1", version: "6.3", arch: "x86", family: "dos" > [DEBUG] Created new class realm maven.api > [DEBUG] Importing foreign packages into class realm maven.api > [DEBUG] Imported: javax.enterprise.inject.* < plexus.core > [DEBUG] Imported: javax.enterprise.util.* < plexus.core > [DEBUG] Imported: javax.inject.* < plexus.core > [DEBUG] Imported: org.apache.maven.* < plexus.core > [DEBUG] Imported: org.apache.maven.artifact < plexus.core > [DEBUG] Imported: org.apache.maven.classrealm < plexus.core > [DEBUG] Imported: org.apache.maven.cli < plexus.core > [DEBUG] Imported: org.apache.maven.configuration < plexus.core > [DEBUG] Imported: org.apache.maven.exception < plexus.core > [DEBUG] Imported: org.apache.maven.execution < plexus.core > [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core > [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core > [DEBUG] Imported: org.apache.maven.model < plexus.core > [DEBUG] Imported: org.apache.maven.monitor < plexus.core > [DEBUG] Imported: org.apache.maven.plugin < plexus.core > [DEBUG] Imported: org.apache.maven.profiles < plexus.core > [DEBUG] Imported: org.apache.maven.project < plexus.core > [DEBUG] Imported: org.apache.maven.reporting < plexus.core > [DEBUG] Imported: org.apache.maven.repository < plexus.core > [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core > [DEBUG] Imported: org.apache.maven.settings < plexus.core > [DEBUG] Imported: org.apache.maven.toolchain < plexus.core > [DEBUG] Imported: org.apache.maven.usability < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core > [DEBUG] Imported: org.codehaus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.* < plexus.core > [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.component < plexus.core > [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core > [DEBUG] Imported: org.codehaus.plexus.container < plexus.core > [DEBUG] Imported: org.codehaus.plexus.context < plexus.core > [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core > [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core > [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < > plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException > < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < > plexus.core > [DEBUG] Imported: org.eclipse.aether.* < plexus.core > [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core > [DEBUG] Imported: org.eclipse.aether.collection < plexus.core > [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core > [DEBUG] Imported: org.eclipse.aether.graph < plexus.core > [DEBUG] Imported: org.eclipse.aether.impl < plexus.core >
[jira] [Commented] (ARCHETYPE-493) Incorrect site documentation
[ https://issues.apache.org/jira/browse/ARCHETYPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030273#comment-15030273 ] Manfred Moser commented on ARCHETYPE-493: - [~crowne] you are looking at the archive in these links. We are not updating old archive content. Instead please check the actual documentation for the maven archetype plugin at http://maven.apache.org/archetype/maven-archetype-plugin/ and report any issues you find in a new issue. From all I can see this current documentation is correct. > Incorrect site documentation > > > Key: ARCHETYPE-493 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-493 > Project: Maven Archetype > Issue Type: Improvement > Components: Documentation >Reporter: Neil Crow > > The example given on the page below does not work > https://maven.apache.org/plugins-archives/maven-archetype-plugin-1.0-alpha-7/examples/simple.html > I found the correct syntax at: > http://stackoverflow.com/questions/9181683/maven-3-failed-to-execute-goal-org-apache-maven-pluginsmaven-archetype-plugin > Also I noticed that the version displayed on the breadcrumb bar is "Last > Published: 08 Feb 2008 | Version: 1.0-alpha-7" which is quite old and way > behind the latest release 2.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ARCHETYPE-493) Incorrect site documentation
[ https://issues.apache.org/jira/browse/ARCHETYPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed ARCHETYPE-493. --- Resolution: Invalid > Incorrect site documentation > > > Key: ARCHETYPE-493 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-493 > Project: Maven Archetype > Issue Type: Improvement > Components: Documentation >Reporter: Neil Crow > > The example given on the page below does not work > https://maven.apache.org/plugins-archives/maven-archetype-plugin-1.0-alpha-7/examples/simple.html > I found the correct syntax at: > http://stackoverflow.com/questions/9181683/maven-3-failed-to-execute-goal-org-apache-maven-pluginsmaven-archetype-plugin > Also I noticed that the version displayed on the breadcrumb bar is "Last > Published: 08 Feb 2008 | Version: 1.0-alpha-7" which is quite old and way > behind the latest release 2.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-929) 2.5.3 release is broken in maven-central
[ https://issues.apache.org/jira/browse/MRELEASE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002693#comment-15002693 ] Manfred Moser commented on MRELEASE-929: This must be a connection issue on your side. The pom files and all other files are there. > 2.5.3 release is broken in maven-central > > > Key: MRELEASE-929 > URL: https://issues.apache.org/jira/browse/MRELEASE-929 > Project: Maven Release Plugin > Issue Type: Bug >Affects Versions: 2.5.3 >Reporter: Osvaldo Pinali Doederlein > > I now get this trying to build a pom that depends on 2.5.3: > [WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 > is missing, no dependency information available > Checking the repo, > https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/ > It's missing some of the sign files, e.g. .asc.md5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRELEASE-929) 2.5.3 release is broken in maven-central
[ https://issues.apache.org/jira/browse/MRELEASE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MRELEASE-929. -- Resolution: Not A Problem > 2.5.3 release is broken in maven-central > > > Key: MRELEASE-929 > URL: https://issues.apache.org/jira/browse/MRELEASE-929 > Project: Maven Release Plugin > Issue Type: Bug >Affects Versions: 2.5.3 >Reporter: Osvaldo Pinali Doederlein > > I now get this trying to build a pom that depends on 2.5.3: > [WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 > is missing, no dependency information available > Checking the repo, > https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/ > It's missing some of the sign files, e.g. .asc.md5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work
[ https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981728#comment-14981728 ] Manfred Moser commented on SUREFIRE-1191: - Thanks for clarifying this. I did not realize the scope of this change was that big due to the involved libraries. Maybe we should change this issue to "wish" then and work on it later. > Run Single Test with Package Name Doesn't work > -- > > Key: SUREFIRE-1191 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1191 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.19 >Reporter: Gunnar Schmidt > > Running the following command works: > mvn test -Dtest=MyTestCaseTest#myTest > This doesn't work (package name included): > mvn test -Dtest=my.package.name.MyTestCaseTest#myTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work
[ https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981294#comment-14981294 ] Manfred Moser commented on SUREFIRE-1191: - >From a users perspective it completely makes sense to use the fully qualified >name of the class including the package with the dot notation. I have not >looked at the code of surefire but on the surface this should not be too hard >to implement. Would be it be worth adding this as a new feature? > Run Single Test with Package Name Doesn't work > -- > > Key: SUREFIRE-1191 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1191 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.19 >Reporter: Gunnar Schmidt > > Running the following command works: > mvn test -Dtest=MyTestCaseTest#myTest > This doesn't work (package name included): > mvn test -Dtest=my.package.name.MyTestCaseTest#myTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MDEPLOY-197) deploy:deploy-file in some cases upload a file twice
[ https://issues.apache.org/jira/browse/MDEPLOY-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635517#comment-14635517 ] Manfred Moser commented on MDEPLOY-197: --- Omar, Your issue is different and it should not reopen this issue. For your use case the only solutions I am aware of are - upload the javadoc and source jars with the REST API of Nexus rather than via Maven or - manually copy the files into the repository in the filesystem on the server or - deleting the existing artifact and uploading all at once properly > deploy:deploy-file in some cases upload a file twice > > > Key: MDEPLOY-197 > URL: https://issues.apache.org/jira/browse/MDEPLOY-197 > Project: Maven Deploy Plugin > Issue Type: Bug > Components: deploy:deploy-file >Affects Versions: 2.8.2 >Reporter: Jeffrey Dang >Assignee: Robert Scholte >Priority: Trivial > Labels: easyfix > Attachments: added_file_check.patch > > Original Estimate: 5m > Remaining Estimate: 5m > > In org/apache/maven/plugin/deploy/DeployFileMojo.java, > When executing, deploy will be called on the file specified by deploy-file > goal. > Afterward, deploy will be called on project.getAttachedArtifacts(). > The specified deploy file can be included in the attached artifacts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-251) Update link to SortPom reference
[ https://issues.apache.org/jira/browse/MNGSITE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634226#comment-14634226 ] Manfred Moser commented on MNGSITE-251: --- This should probably link to the tidy maven plugin http://www.mojohaus.org/tidy-maven-plugin/pom-mojo.html > Update link to SortPom reference > > > Key: MNGSITE-251 > URL: https://issues.apache.org/jira/browse/MNGSITE-251 > Project: Maven Project Web Site > Issue Type: Documentation >Reporter: Björn Ekryd >Priority: Minor > Labels: documentation, easyfix > > On the page https://maven.apache.org/developers/conventions/code.html, you > have a link to the SortPom plugin. > Since Google Code is shutting down, the plugin has moved location to GitHub. > Please change the plugin link reference to https://github.com/Ekryd/sortpom -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1170) skiptTests=true is used by maven-surefire-plugin as well as of maven-failsafe-plugin
[
https://issues.apache.org/jira/browse/SUREFIRE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632608#comment-14632608
]
Manfred Moser commented on SUREFIRE-1170:
-
Same applies for maven.skip.tests=true .. both are also honoured as a broad
setting by the android-maven-plugin fyi
> skiptTests=true is used by maven-surefire-plugin as well as of
> maven-failsafe-plugin
>
>
> Key: SUREFIRE-1170
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1170
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.18.1
>Reporter: Karl Heinz Marbaise
>
> By using the properties {{skipTests=true}} will skip the tests for
> maven-surefire-plugin as well as for maven-failsafe-plugin.
> So currently it's not simple to make a separation of skipping either unit
> tests (maven-surefire-plugin) or integration tests (maven-failsafe-plugin).
> maven-failsafe-plugin has a property {{skipITs=true}} which will skip the
> integration tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5854) Maven Installation instructions not working on Mac
[ https://issues.apache.org/jira/browse/MNG-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617149#comment-14617149 ] Manfred Moser commented on MNG-5854: Also please show us how you are adding the bin folder of the maven install to the $PATH > Maven Installation instructions not working on Mac > -- > > Key: MNG-5854 > URL: https://issues.apache.org/jira/browse/MNG-5854 > Project: Maven > Issue Type: Documentation > Components: Documentation: General >Affects Versions: 3.3.3 > Environment: OS X Yosemite (10.10.4) >Reporter: Nathan Christie >Assignee: Manfred Moser >Priority: Blocker > Labels: documentation, easyfix, maven > > The Installation instructions for Apache > (https://maven.apache.org/install.html) do not work when attempting to > install on my Mac. After following the installation instructions, the > following error is observed when attempting to run a: > mvn -v > Error: Could not find or load main class > org.codehaus.plexus.classworlds.launcher.Launcher > However, when I did an: > export $M2_HOME=/opt/apache-maven-3.3.3 > It worked fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5854) Maven Installation instructions not working on Mac
[ https://issues.apache.org/jira/browse/MNG-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617147#comment-14617147 ] Manfred Moser commented on MNG-5854: We no longer suggest to use th M2_HOME environment variable and it works fine on my machine. Could you run echo $PATH and which mvn and comment the out here? > Maven Installation instructions not working on Mac > -- > > Key: MNG-5854 > URL: https://issues.apache.org/jira/browse/MNG-5854 > Project: Maven > Issue Type: Documentation > Components: Documentation: General >Affects Versions: 3.3.3 > Environment: OS X Yosemite (10.10.4) >Reporter: Nathan Christie >Priority: Blocker > Labels: documentation, easyfix, maven > > The Installation instructions for Apache > (https://maven.apache.org/install.html) do not work when attempting to > install on my Mac. After following the installation instructions, the > following error is observed when attempting to run a: > mvn -v > Error: Could not find or load main class > org.codehaus.plexus.classworlds.launcher.Launcher > However, when I did an: > export $M2_HOME=/opt/apache-maven-3.3.3 > It worked fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MNG-5854) Maven Installation instructions not working on Mac
[ https://issues.apache.org/jira/browse/MNG-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MNG-5854: -- Assignee: Manfred Moser > Maven Installation instructions not working on Mac > -- > > Key: MNG-5854 > URL: https://issues.apache.org/jira/browse/MNG-5854 > Project: Maven > Issue Type: Documentation > Components: Documentation: General >Affects Versions: 3.3.3 > Environment: OS X Yosemite (10.10.4) >Reporter: Nathan Christie >Assignee: Manfred Moser >Priority: Blocker > Labels: documentation, easyfix, maven > > The Installation instructions for Apache > (https://maven.apache.org/install.html) do not work when attempting to > install on my Mac. After following the installation instructions, the > following error is observed when attempting to run a: > mvn -v > Error: Could not find or load main class > org.codehaus.plexus.classworlds.launcher.Launcher > However, when I did an: > export $M2_HOME=/opt/apache-maven-3.3.3 > It worked fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-246) Documentation of mavenrc_pre / .mavenrc
[ https://issues.apache.org/jira/browse/MNGSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615151#comment-14615151 ] Manfred Moser commented on MNGSITE-246: --- This should be added with a little info to the new configure page and then with more details on a separate page linked off it imho. http://maven.apache.org/configure.html > Documentation of mavenrc_pre / .mavenrc > --- > > Key: MNGSITE-246 > URL: https://issues.apache.org/jira/browse/MNGSITE-246 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > > The usage and the intention of mavenrc_pre and .maverc should be documented > somehow. cause at the moment it does not exist any documenation about this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5851) environment variable to configure settings.xml location
[ https://issues.apache.org/jira/browse/MNG-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613490#comment-14613490 ] Manfred Moser commented on MNG-5851: Check out this for more info http://blog.soebes.de/blog/2015/03/17/apache-maven-3-dot-3-1-features/ > environment variable to configure settings.xml location > --- > > Key: MNG-5851 > URL: https://issues.apache.org/jira/browse/MNG-5851 > Project: Maven > Issue Type: New Feature >Reporter: Caleb Cushing > > Wercker which is a continuous integration/deployment saas, and has a platform > built on docker. > what I'd like to be able to do is specify M2_SETTINGS="./settings.xml" so > that I could put my settings into my repo without extending the official > docker image. This way I could configure Wercker to be able to do releases to > a nexus server. Inside the settings.xml I could define other variables like > server/username/password so that wercker could fill them in at runtime. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5851) environment variable to configure settings.xml location
[ https://issues.apache.org/jira/browse/MNG-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613480#comment-14613480 ] Manfred Moser commented on MNG-5851: Correct. I am not sure if a patch to support M2_SETTINGS would be approved. We just recently removed the need for M2_HOME .. Anyway.. you might have better luck with something that allows settings in the projet specific .mvn folder or so. Not sure to be honest. > environment variable to configure settings.xml location > --- > > Key: MNG-5851 > URL: https://issues.apache.org/jira/browse/MNG-5851 > Project: Maven > Issue Type: New Feature >Reporter: Caleb Cushing > > Wercker which is a continuous integration/deployment saas, and has a platform > built on docker. > what I'd like to be able to do is specify M2_SETTINGS="./settings.xml" so > that I could put my settings into my repo without extending the official > docker image. This way I could configure Wercker to be able to do releases to > a nexus server. Inside the settings.xml I could define other variables like > server/username/password so that wercker could fill them in at runtime. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5851) environment variable to configure settings.xml location
[ https://issues.apache.org/jira/browse/MNG-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613439#comment-14613439 ] Manfred Moser commented on MNG-5851: You could just add the -s or -gs command line switches on your mvn invocations. As such there is no need to another environment variable. > environment variable to configure settings.xml location > --- > > Key: MNG-5851 > URL: https://issues.apache.org/jira/browse/MNG-5851 > Project: Maven > Issue Type: New Feature >Reporter: Caleb Cushing > > Wercker which is a continuous integration/deployment saas, and has a platform > built on docker. > what I'd like to be able to do is specify M2_SETTINGS="./settings.xml" so > that I could put my settings into my repo without extending the official > docker image. This way I could configure Wercker to be able to do releases to > a nexus server. Inside the settings.xml I could define other variables like > server/username/password so that wercker could fill them in at runtime. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-248) Remove old IDE related content
[ https://issues.apache.org/jira/browse/MNGSITE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613414#comment-14613414 ] Manfred Moser commented on MNGSITE-248: --- http://svn.apache.org/viewvc?view=revision&revision=1689065 > Remove old IDE related content > -- > > Key: MNGSITE-248 > URL: https://issues.apache.org/jira/browse/MNGSITE-248 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Manfred Moser >Assignee: Manfred Moser > > The documentation for using an IDE with Maven should be maintained by the IDE > docs. All we got on the site is old and out of date. Its gotta go! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNGSITE-248) Remove old IDE related content
[ https://issues.apache.org/jira/browse/MNGSITE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNGSITE-248. - Resolution: Fixed > Remove old IDE related content > -- > > Key: MNGSITE-248 > URL: https://issues.apache.org/jira/browse/MNGSITE-248 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Manfred Moser >Assignee: Manfred Moser > > The documentation for using an IDE with Maven should be maintained by the IDE > docs. All we got on the site is old and out of date. Its gotta go! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNGSITE-248) Remove old IDE related content
[ https://issues.apache.org/jira/browse/MNGSITE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser updated MNGSITE-248: -- Description: The documentation for using an IDE with Maven should be maintained by the IDE docs. All we got on the site is old and out of date. Its gotta go! > Remove old IDE related content > -- > > Key: MNGSITE-248 > URL: https://issues.apache.org/jira/browse/MNGSITE-248 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Manfred Moser >Assignee: Manfred Moser > > The documentation for using an IDE with Maven should be maintained by the IDE > docs. All we got on the site is old and out of date. Its gotta go! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNGSITE-248) Remove old IDE related content
Manfred Moser created MNGSITE-248: - Summary: Remove old IDE related content Key: MNGSITE-248 URL: https://issues.apache.org/jira/browse/MNGSITE-248 Project: Maven Project Web Site Issue Type: Task Reporter: Manfred Moser -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MNGSITE-248) Remove old IDE related content
[ https://issues.apache.org/jira/browse/MNGSITE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MNGSITE-248: - Assignee: Manfred Moser > Remove old IDE related content > -- > > Key: MNGSITE-248 > URL: https://issues.apache.org/jira/browse/MNGSITE-248 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Manfred Moser >Assignee: Manfred Moser > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNGSITE-247) Broken link in Guides index
[ https://issues.apache.org/jira/browse/MNGSITE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNGSITE-247. - Resolution: Fixed > Broken link in Guides index > --- > > Key: MNGSITE-247 > URL: https://issues.apache.org/jira/browse/MNGSITE-247 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Aidan Pitt-Brooke >Assignee: Manfred Moser >Priority: Minor > Labels: broken, broken-link, links > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > The Maven website's [categorized documentation > index|http://maven.apache.org/guides/index.html] has a link with the text > "Webapps" under the "Guides" heading, which points to > http://maven.apache.org/guides/mini/guide-webapp.html. The linked page > doesn't exist. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-247) Broken link in Guides index
[ https://issues.apache.org/jira/browse/MNGSITE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613404#comment-14613404 ] Manfred Moser commented on MNGSITE-247: --- http://svn.apache.org/viewvc?view=revision&revision=1689057 > Broken link in Guides index > --- > > Key: MNGSITE-247 > URL: https://issues.apache.org/jira/browse/MNGSITE-247 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Aidan Pitt-Brooke >Assignee: Manfred Moser >Priority: Minor > Labels: broken, broken-link, links > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > The Maven website's [categorized documentation > index|http://maven.apache.org/guides/index.html] has a link with the text > "Webapps" under the "Guides" heading, which points to > http://maven.apache.org/guides/mini/guide-webapp.html. The linked page > doesn't exist. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MNGSITE-247) Broken link in Guides index
[ https://issues.apache.org/jira/browse/MNGSITE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MNGSITE-247: - Assignee: Manfred Moser > Broken link in Guides index > --- > > Key: MNGSITE-247 > URL: https://issues.apache.org/jira/browse/MNGSITE-247 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Aidan Pitt-Brooke >Assignee: Manfred Moser >Priority: Minor > Labels: broken, broken-link, links > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > The Maven website's [categorized documentation > index|http://maven.apache.org/guides/index.html] has a link with the text > "Webapps" under the "Guides" heading, which points to > http://maven.apache.org/guides/mini/guide-webapp.html. The linked page > doesn't exist. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNGSITE-239) Download page does not cite Java requirement for 3.3.x versions
[ https://issues.apache.org/jira/browse/MNGSITE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNGSITE-239. - Resolution: Fixed > Download page does not cite Java requirement for 3.3.x versions > --- > > Key: MNGSITE-239 > URL: https://issues.apache.org/jira/browse/MNGSITE-239 > Project: Maven Project Web Site > Issue Type: Bug > Environment: https://maven.apache.org/download.cgi >Reporter: Sebb >Assignee: Manfred Moser > > The download page does not mention the Java version requirement for running > version 3.3.x in the heading; the information is buried way down the page. > It would be helpful if the minimum Java requirement was documented for each > release stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-239) Download page does not cite Java requirement for 3.3.x versions
[ https://issues.apache.org/jira/browse/MNGSITE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613394#comment-14613394 ] Manfred Moser commented on MNGSITE-239: --- http://svn.apache.org/viewvc?view=revision&revision=1689055 > Download page does not cite Java requirement for 3.3.x versions > --- > > Key: MNGSITE-239 > URL: https://issues.apache.org/jira/browse/MNGSITE-239 > Project: Maven Project Web Site > Issue Type: Bug > Environment: https://maven.apache.org/download.cgi >Reporter: Sebb >Assignee: Manfred Moser > > The download page does not mention the Java version requirement for running > version 3.3.x in the heading; the information is buried way down the page. > It would be helpful if the minimum Java requirement was documented for each > release stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNGSITE-245) Improved download and install experience
[ https://issues.apache.org/jira/browse/MNGSITE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNGSITE-245. - Resolution: Fixed http://svn.apache.org/viewvc?view=revision&revision=1689055 > Improved download and install experience > > > Key: MNGSITE-245 > URL: https://issues.apache.org/jira/browse/MNGSITE-245 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Manfred Moser >Assignee: Manfred Moser > > I propose to do the following changes: > - Simplify the 'Get Maven' submenu to just have Download, Install and Run > - Remove older versions than latest release from Download page > - Clearly add requirements to top of page > - Create separate install page > - Create new run page (with stuff from old wiki and other resources) > The aim is to make the initial download and get started experience better and > remove confusing choices about Maven versions to use and so on. > We effectively only push fixes into latest release and such this is the only > one that should be available for download easily. The rest can be retrieved > from the archive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNGSITE-150) Installation guide creates unnecessary M2 variable
[ https://issues.apache.org/jira/browse/MNGSITE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNGSITE-150. - Resolution: Fixed > Installation guide creates unnecessary M2 variable > -- > > Key: MNGSITE-150 > URL: https://issues.apache.org/jira/browse/MNGSITE-150 > Project: Maven Project Web Site > Issue Type: Bug > Environment: http://maven.apache.org/download.html#Installation >Reporter: Sebb >Assignee: Manfred Moser >Priority: Minor > > The installation guide says one needs to create an "M2" environment variable. > However, M2 only appears to be used for updating the PATH; it does not appear > to be used by the Maven scripts. > If it's not necessary - only a convenience - then this should be stated, and > / or the instructions reworded to avoid using it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-150) Installation guide creates unnecessary M2 variable
[ https://issues.apache.org/jira/browse/MNGSITE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613391#comment-14613391 ] Manfred Moser commented on MNGSITE-150: --- http://svn.apache.org/viewvc?view=revision&revision=1689055 > Installation guide creates unnecessary M2 variable > -- > > Key: MNGSITE-150 > URL: https://issues.apache.org/jira/browse/MNGSITE-150 > Project: Maven Project Web Site > Issue Type: Bug > Environment: http://maven.apache.org/download.html#Installation >Reporter: Sebb >Assignee: Manfred Moser >Priority: Minor > > The installation guide says one needs to create an "M2" environment variable. > However, M2 only appears to be used for updating the PATH; it does not appear > to be used by the Maven scripts. > If it's not necessary - only a convenience - then this should be stated, and > / or the instructions reworded to avoid using it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-300) Upgrade to Checkstyle 6.8.x+
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612232#comment-14612232 ] Manfred Moser commented on MCHECKSTYLE-300: --- Generally there is no schedule. You would simply ask for a new release on the dev or user mailing list with a justification and hopefully a committer can get to it soon thereafter. > Upgrade to Checkstyle 6.8.x+ > > > Key: MCHECKSTYLE-300 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-300 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Reporter: Juan Martín Sotuyo Dodero > > We should upgrade to the latest and greatest checkstyle version. Notice since > 6.8 there was a big breaking change: > Rename CheckStyleTask to CheckstyleAntTask, Rename and move > checkstyletask.properties. Author: Michal Kordas > [#1108|https://github.com/checkstyle/checkstyle/issues/1108] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-300) Upgrade to Checkstyle 6.8.x+
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612198#comment-14612198 ] Manfred Moser commented on MCHECKSTYLE-300: --- You could supply patches to speed up the process... > Upgrade to Checkstyle 6.8.x+ > > > Key: MCHECKSTYLE-300 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-300 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Reporter: Juan Martín Sotuyo Dodero > > We should upgrade to the latest and greatest checkstyle version. Notice since > 6.8 there was a big breaking change: > Rename CheckStyleTask to CheckstyleAntTask, Rename and move > checkstyletask.properties. Author: Michal Kordas > [#1108|https://github.com/checkstyle/checkstyle/issues/1108] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MCOMPILER-246) Incorrect example in documentation
[
https://issues.apache.org/jira/browse/MCOMPILER-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Moser closed MCOMPILER-246.
---
Resolution: Fixed
> Incorrect example in documentation
> --
>
> Key: MCOMPILER-246
> URL: https://issues.apache.org/jira/browse/MCOMPILER-246
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Reporter: Mikhail Mazurskiy
>Assignee: Manfred Moser
>Priority: Minor
>
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
> Compiler args should be inside {{}} block.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MCOMPILER-246) Incorrect example in documentation
[
https://issues.apache.org/jira/browse/MCOMPILER-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610767#comment-14610767
]
Manfred Moser commented on MCOMPILER-246:
-
Fixed with http://svn.apache.org/viewvc?view=revision&revision=1688699
Will go live on site with next release.
> Incorrect example in documentation
> --
>
> Key: MCOMPILER-246
> URL: https://issues.apache.org/jira/browse/MCOMPILER-246
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Reporter: Mikhail Mazurskiy
>Assignee: Manfred Moser
>Priority: Minor
>
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
> Compiler args should be inside {{}} block.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MCOMPILER-246) Incorrect example in documentation
[
https://issues.apache.org/jira/browse/MCOMPILER-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Moser reassigned MCOMPILER-246:
---
Assignee: Manfred Moser
> Incorrect example in documentation
> --
>
> Key: MCOMPILER-246
> URL: https://issues.apache.org/jira/browse/MCOMPILER-246
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Reporter: Mikhail Mazurskiy
>Assignee: Manfred Moser
>Priority: Minor
>
> https://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
> Compiler args should be inside {{}} block.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MNGSITE-150) Installation guide creates unnecessary M2 variable
[ https://issues.apache.org/jira/browse/MNGSITE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MNGSITE-150: - Assignee: Manfred Moser > Installation guide creates unnecessary M2 variable > -- > > Key: MNGSITE-150 > URL: https://issues.apache.org/jira/browse/MNGSITE-150 > Project: Maven Project Web Site > Issue Type: Bug > Environment: http://maven.apache.org/download.html#Installation >Reporter: Sebb >Assignee: Manfred Moser >Priority: Minor > > The installation guide says one needs to create an "M2" environment variable. > However, M2 only appears to be used for updating the PATH; it does not appear > to be used by the Maven scripts. > If it's not necessary - only a convenience - then this should be stated, and > / or the instructions reworded to avoid using it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNGSITE-150) Installation guide creates unnecessary M2 variable
[ https://issues.apache.org/jira/browse/MNGSITE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603755#comment-14603755 ] Manfred Moser commented on MNGSITE-150: --- Will fix this as part of the clean up process for the installation process. > Installation guide creates unnecessary M2 variable > -- > > Key: MNGSITE-150 > URL: https://issues.apache.org/jira/browse/MNGSITE-150 > Project: Maven Project Web Site > Issue Type: Bug > Environment: http://maven.apache.org/download.html#Installation >Reporter: Sebb >Assignee: Manfred Moser >Priority: Minor > > The installation guide says one needs to create an "M2" environment variable. > However, M2 only appears to be used for updating the PATH; it does not appear > to be used by the Maven scripts. > If it's not necessary - only a convenience - then this should be stated, and > / or the instructions reworded to avoid using it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNGSITE-193) Questionable tip for using multiple repositories
[
https://issues.apache.org/jira/browse/MNGSITE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603738#comment-14603738
]
Manfred Moser edited comment on MNGSITE-193 at 6/26/15 11:02 PM:
-
I will update this to create a best practice doc about repo manager usage and
avoid repositories in the pom and even too many of them in settings to avoid
performance and management issue.s
was (Author: simpligility):
I will update this to create a best practice doc about repo manager usage and
avoid repositories in settings.
> Questionable tip for using multiple repositories
>
>
> Key: MNGSITE-193
> URL: https://issues.apache.org/jira/browse/MNGSITE-193
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Robert Wruck
>Assignee: Manfred Moser
>Priority: Minor
>
> In the Guide to using Multiple Repositories
> (http://maven.apache.org/guides/mini/guide-multiple-repositories.html) it is
> stated that
> {quote}
> The repositories element is inherited so you would usually specify the
> repositories to use for a group of projects by defining a repositories
> element at the top of your inheritance chain.
> {quote}
> It is quite obvious that this won't work since the parent POM for a project
> would need to be fetched from a repository whose location is specified in the
> parent POM which needs to be fetched from a repository whose location is
> specified in the parent POM ... etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNGSITE-193) Questionable tip for using multiple repositories
[
https://issues.apache.org/jira/browse/MNGSITE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603738#comment-14603738
]
Manfred Moser edited comment on MNGSITE-193 at 6/26/15 11:02 PM:
-
I will update this to create a best practice doc about repo manager usage and
avoid repositories in the pom and even too many of them in settings to avoid
performance and management issues.
was (Author: simpligility):
I will update this to create a best practice doc about repo manager usage and
avoid repositories in the pom and even too many of them in settings to avoid
performance and management issue.s
> Questionable tip for using multiple repositories
>
>
> Key: MNGSITE-193
> URL: https://issues.apache.org/jira/browse/MNGSITE-193
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Robert Wruck
>Assignee: Manfred Moser
>Priority: Minor
>
> In the Guide to using Multiple Repositories
> (http://maven.apache.org/guides/mini/guide-multiple-repositories.html) it is
> stated that
> {quote}
> The repositories element is inherited so you would usually specify the
> repositories to use for a group of projects by defining a repositories
> element at the top of your inheritance chain.
> {quote}
> It is quite obvious that this won't work since the parent POM for a project
> would need to be fetched from a repository whose location is specified in the
> parent POM which needs to be fetched from a repository whose location is
> specified in the parent POM ... etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNGSITE-193) Questionable tip for using multiple repositories
[
https://issues.apache.org/jira/browse/MNGSITE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603738#comment-14603738
]
Manfred Moser commented on MNGSITE-193:
---
I will update this to create a best practice doc about repo manager usage and
avoid repositories in settings.
> Questionable tip for using multiple repositories
>
>
> Key: MNGSITE-193
> URL: https://issues.apache.org/jira/browse/MNGSITE-193
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Robert Wruck
>Assignee: Manfred Moser
>Priority: Minor
>
> In the Guide to using Multiple Repositories
> (http://maven.apache.org/guides/mini/guide-multiple-repositories.html) it is
> stated that
> {quote}
> The repositories element is inherited so you would usually specify the
> repositories to use for a group of projects by defining a repositories
> element at the top of your inheritance chain.
> {quote}
> It is quite obvious that this won't work since the parent POM for a project
> would need to be fetched from a repository whose location is specified in the
> parent POM which needs to be fetched from a repository whose location is
> specified in the parent POM ... etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MNGSITE-193) Questionable tip for using multiple repositories
[
https://issues.apache.org/jira/browse/MNGSITE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Moser reassigned MNGSITE-193:
-
Assignee: Manfred Moser
> Questionable tip for using multiple repositories
>
>
> Key: MNGSITE-193
> URL: https://issues.apache.org/jira/browse/MNGSITE-193
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Robert Wruck
>Assignee: Manfred Moser
>Priority: Minor
>
> In the Guide to using Multiple Repositories
> (http://maven.apache.org/guides/mini/guide-multiple-repositories.html) it is
> stated that
> {quote}
> The repositories element is inherited so you would usually specify the
> repositories to use for a group of projects by defining a repositories
> element at the top of your inheritance chain.
> {quote}
> It is quite obvious that this won't work since the parent POM for a project
> would need to be fetched from a repository whose location is specified in the
> parent POM which needs to be fetched from a repository whose location is
> specified in the parent POM ... etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MNGSITE-245) Improved download and install experience
Manfred Moser created MNGSITE-245: - Summary: Improved download and install experience Key: MNGSITE-245 URL: https://issues.apache.org/jira/browse/MNGSITE-245 Project: Maven Project Web Site Issue Type: Improvement Reporter: Manfred Moser Assignee: Manfred Moser I propose to do the following changes: - Simplify the 'Get Maven' submenu to just have Download, Install and Run - Remove older versions than latest release from Download page - Clearly add requirements to top of page - Create separate install page - Create new run page (with stuff from old wiki and other resources) The aim is to make the initial download and get started experience better and remove confusing choices about Maven versions to use and so on. We effectively only push fixes into latest release and such this is the only one that should be available for download easily. The rest can be retrieved from the archive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNGSITE-206) Could not resolve target platform specification artifact
[ https://issues.apache.org/jira/browse/MNGSITE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser closed MNGSITE-206. - Resolution: Invalid Not related to the Maven site itself. > Could not resolve target platform specification artifact > > > Key: MNGSITE-206 > URL: https://issues.apache.org/jira/browse/MNGSITE-206 > Project: Maven Project Web Site > Issue Type: Bug > Environment: Linux x86 >Reporter: Himanshu Mishra > Attachments: debug.log > > > Actually i am trying to build org.eclipse.cdt.dsf and also set the target > platform as mentioned in the documentation but it is still giving Internal > Exception. The debug.log is attched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MNGSITE-239) Download page does not cite Java requirement for 3.3.x versions
[ https://issues.apache.org/jira/browse/MNGSITE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser reassigned MNGSITE-239: - Assignee: Manfred Moser > Download page does not cite Java requirement for 3.3.x versions > --- > > Key: MNGSITE-239 > URL: https://issues.apache.org/jira/browse/MNGSITE-239 > Project: Maven Project Web Site > Issue Type: Bug > Environment: https://maven.apache.org/download.cgi >Reporter: Sebb >Assignee: Manfred Moser > > The download page does not mention the Java version requirement for running > version 3.3.x in the heading; the information is buried way down the page. > It would be helpful if the minimum Java requirement was documented for each > release stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
