[jira] [Closed] (MSHARED-833) make pom.properties entries order reproducible
[ https://issues.apache.org/jira/browse/MSHARED-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MSHARED-833. - Fix Version/s: maven-archiver-3.4.1 Resolution: Fixed done in https://gitbox.apache.org/repos/asf?p=maven-archiver.git;a=commit;h=763a940540eefad74f9ba73cb5eed288dc4e639d > make pom.properties entries order reproducible > -- > > Key: MSHARED-833 > URL: https://issues.apache.org/jira/browse/MSHARED-833 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-3.4.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: maven-archiver-3.4.1 > > > necessary for Reproducible Builds, as discussed in MSHARED-800 and seen > during tests: even on one platform, JDK 9 and more do not get the same order > as JDK 8 and less -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (MSHARED-833) make pom.properties entries order reproducible
[ https://issues.apache.org/jira/browse/MSHARED-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919248#comment-16919248 ] Hudson commented on MSHARED-833: Build succeeded in Jenkins: Maven TLP » maven-archiver » master #12 See https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/12/ > make pom.properties entries order reproducible > -- > > Key: MSHARED-833 > URL: https://issues.apache.org/jira/browse/MSHARED-833 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-3.4.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > > necessary for Reproducible Builds, as discussed in MSHARED-800 and seen > during tests: even on one platform, JDK 9 and more do not get the same order > as JDK 8 and less -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (MSHARED-833) make pom.properties entries order reproducible
Hervé Boutemy created MSHARED-833: - Summary: make pom.properties entries order reproducible Key: MSHARED-833 URL: https://issues.apache.org/jira/browse/MSHARED-833 Project: Maven Shared Components Issue Type: Improvement Components: maven-archiver Affects Versions: maven-archiver-3.4.0 Reporter: Hervé Boutemy Assignee: Hervé Boutemy necessary for Reproducible Builds, as discussed in MSHARED-800 and seen during tests: even on one platform, JDK 9 and more do not get the same order as JDK 8 and less -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [maven-archetypes] johnlinp opened a new pull request #4: Remove trailing spaces in generated App.java and AppTest.java
johnlinp opened a new pull request #4: Remove trailing spaces in generated App.java and AppTest.java URL: https://github.com/apache/maven-archetypes/pull/4 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MSITE-849) Unable to inject MavenProject when using `mvn site:run`
[
https://issues.apache.org/jira/browse/MSITE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918920#comment-16918920
]
Abel Salgado Romero commented on MSITE-849:
---
Adding {{SessionScoped}} causes the following error and component not even
starts.
{code:java}
com.google.inject.ProvisionException: Unable to provision, see the following
errors:
1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot
access Key[type=org.asciidoctor.maven.site.AsciidoctorDoxiaParser,
annotation=[none]] outside of a scoping block
at org.asciidoctor.maven.site.AsciidoctorDoxiaParser.class(Unknown Source)
while locating org.asciidoctor.maven.site.AsciidoctorDoxiaParser
at ClassRealm[plugin>org.apache.maven.plugins:maven-site-plugin:3.8.2,
parent: sun.misc.Launcher$AppClassLoader@18b4aac2] (via modules:
org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule)
while locating org.apache.maven.doxia.parser.Parser annotated with
@com.google.inject.name.Named(value=asciidoc)
{code}
And injecting {{MavenSession}} has the same effect as the {{MavenProject}}.
Checking the whole stacktrace I realize that during {{site:run}}, the Doxia
component runs inside a web context. And the call stack is completely different
from the one when building with {{site:site}} (see attachment below), there's
no Mojo involved. That makes me think that no Maven context is created and that
the error does in fact make a lot of sense. I can see how the web context is
created...
{code:java}
Caused by: com.google.inject.OutOfScopeException: Cannot access
Key[type=org.apache.maven.project.MavenProject, annotation=[none]] outside of a
scoping block
at org.apache.maven.execution.scope.internal.MojoExecutionScope$2.get
(MojoExecutionScope.java:122)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get
(InternalFactoryToProviderAdapter.java:39)
at com.google.inject.internal.InjectorImpl$1.get (InjectorImpl.java:1050)
at org.asciidoctor.maven.site.AsciidoctorDoxiaParser.parse
(AsciidoctorDoxiaParser.java:81)
at org.apache.maven.doxia.DefaultDoxia.parse (DefaultDoxia.java:65)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument
(DefaultSiteRenderer.java:436)
at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument
(DoxiaDocumentRenderer.java:52)
at org.apache.maven.plugins.site.run.DoxiaFilter.doFilter
(DoxiaFilter.java:144)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter
(ServletHandler.java:1652)
at org.eclipse.jetty.servlet.ServletHandler.doHandle
(ServletHandler.java:585)
at org.eclipse.jetty.server.handler.ScopedHandler.handle
(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle
(SecurityHandler.java:577)
at org.eclipse.jetty.server.session.SessionHandler.doHandle
(SessionHandler.java:223)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle
(ContextHandler.java:1127)
at org.eclipse.jetty.servlet.ServletHandler.doScope
(ServletHandler.java:515)
at org.eclipse.jetty.server.session.SessionHandler.doScope
(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope
(ContextHandler.java:1061)
at org.eclipse.jetty.server.handler.ScopedHandler.handle
(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle
(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle (Server.java:499)
at org.eclipse.jetty.server.HttpChannel.handle (HttpChannel.java:311)
at org.eclipse.jetty.server.HttpConnection.onFillable
(HttpConnection.java:258)
at org.eclipse.jetty.io.AbstractConnection$2.run
(AbstractConnection.java:544)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob
(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run
(QueuedThreadPool.java:555)
at java.lang.Thread.run (Thread.java:748)
{code}
!site_site.png!
> Unable to inject MavenProject when using `mvn site:run`
> ---
>
> Key: MSITE-849
> URL: https://issues.apache.org/jira/browse/MSITE-849
> Project: Maven Site Plugin
> Issue Type: New Feature
>Affects Versions: 3.7.1, 3.8.2
>Reporter: Abel Salgado Romero
>Assignee: Michael Osipov
>Priority: Major
> Attachments: site_site.png
>
>
> In https://github.com/asciidoctor/asciidoctor-maven-plugin we inject a
> MavenProject to obtain addition configurations from the pom.xml
> (https://github.com/asciidoctor/asciidoctor-maven-plugin/blob/a4d86a949643ab68c124fd4c1b9b936412637d93/src/main/java/org/asciidoctor/maven/site/AsciidoctorDoxiaParser.java#L54).
> This works fine with {{site:site}}, but when using {{site:run}} and accessing
> one of the
[jira] [Updated] (MSITE-849) Unable to inject MavenProject when using `mvn site:run`
[
https://issues.apache.org/jira/browse/MSITE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abel Salgado Romero updated MSITE-849:
--
Attachment: site_site.png
> Unable to inject MavenProject when using `mvn site:run`
> ---
>
> Key: MSITE-849
> URL: https://issues.apache.org/jira/browse/MSITE-849
> Project: Maven Site Plugin
> Issue Type: New Feature
>Affects Versions: 3.7.1, 3.8.2
>Reporter: Abel Salgado Romero
>Assignee: Michael Osipov
>Priority: Major
> Attachments: site_site.png
>
>
> In https://github.com/asciidoctor/asciidoctor-maven-plugin we inject a
> MavenProject to obtain addition configurations from the pom.xml
> (https://github.com/asciidoctor/asciidoctor-maven-plugin/blob/a4d86a949643ab68c124fd4c1b9b936412637d93/src/main/java/org/asciidoctor/maven/site/AsciidoctorDoxiaParser.java#L54).
> This works fine with {{site:site}}, but when using {{site:run}} and accessing
> one of the Asciidoc generated pages we get the error below.
> I saw that:
> * The error occurs when trying to retrieve the instance of the MavenProject.
> * Behavior is the same if I directly inject the MavenProject instead of using
> a provider. That is, {{site:site}} works, {{site:run}} fails because it
> cannot find the instance.
> {code:java}
> HTTP ERROR 500
> Problem accessing /hello.html. Reason:
> Server Error
> Caused by:
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> 1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot
> access Key[type=org.apache.maven.project.MavenProject, annotation=[none]]
> outside of a scoping block
> at
> org.apache.maven.execution.scope.internal.MojoExecutionScopeModule.configure(MojoExecutionScopeModule.java:55)
> (via modules: org.eclipse.sisu.wire.WireModule ->
> org.apache.maven.execution.scope.internal.MojoExecutionScopeModule)
> while locating org.apache.maven.project.MavenProject
> 1 error
> at
> com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:226)
> at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1053)
> at
> org.asciidoctor.maven.site.AsciidoctorDoxiaParser.parse(AsciidoctorDoxiaParser.java:78)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> {code}
> * How to reproduce:
> # clone https://github.com/asciidoctor/asciidoctor-maven-examples
> # cd asciidoc-maven-site-example
> # mvn site:run
> # Access {{http://localhost:8080/hello.html}}
> * Env:
> {code}
> $ mvn -v
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> Maven home: /home//.sdkman/candidates/maven/current
> Java version: 1.8.0_222, vendor: AdoptOpenJDK, runtime:
> /home/-/.sdkman/candidates/java/8.0.222.hs-adpt/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.1.21-1-manjaro", arch: "amd64", family: "unix
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MSITE-849) Unable to inject MavenProject when using `mvn site:run`
[
https://issues.apache.org/jira/browse/MSITE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918908#comment-16918908
]
Robert Scholte commented on MSITE-849:
--
I don't know if and where a MavenProject could be injected, but I do know it
should work for MavenSession. It requires the
{{@org.apache.maven.SessionScoped}} annotation on your class. See also
https://maven.apache.org/examples/maven-3-lifecycle-extensions.html
> Unable to inject MavenProject when using `mvn site:run`
> ---
>
> Key: MSITE-849
> URL: https://issues.apache.org/jira/browse/MSITE-849
> Project: Maven Site Plugin
> Issue Type: New Feature
>Affects Versions: 3.7.1, 3.8.2
>Reporter: Abel Salgado Romero
>Assignee: Michael Osipov
>Priority: Major
>
> In https://github.com/asciidoctor/asciidoctor-maven-plugin we inject a
> MavenProject to obtain addition configurations from the pom.xml
> (https://github.com/asciidoctor/asciidoctor-maven-plugin/blob/a4d86a949643ab68c124fd4c1b9b936412637d93/src/main/java/org/asciidoctor/maven/site/AsciidoctorDoxiaParser.java#L54).
> This works fine with {{site:site}}, but when using {{site:run}} and accessing
> one of the Asciidoc generated pages we get the error below.
> I saw that:
> * The error occurs when trying to retrieve the instance of the MavenProject.
> * Behavior is the same if I directly inject the MavenProject instead of using
> a provider. That is, {{site:site}} works, {{site:run}} fails because it
> cannot find the instance.
> {code:java}
> HTTP ERROR 500
> Problem accessing /hello.html. Reason:
> Server Error
> Caused by:
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> 1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot
> access Key[type=org.apache.maven.project.MavenProject, annotation=[none]]
> outside of a scoping block
> at
> org.apache.maven.execution.scope.internal.MojoExecutionScopeModule.configure(MojoExecutionScopeModule.java:55)
> (via modules: org.eclipse.sisu.wire.WireModule ->
> org.apache.maven.execution.scope.internal.MojoExecutionScopeModule)
> while locating org.apache.maven.project.MavenProject
> 1 error
> at
> com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:226)
> at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1053)
> at
> org.asciidoctor.maven.site.AsciidoctorDoxiaParser.parse(AsciidoctorDoxiaParser.java:78)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> {code}
> * How to reproduce:
> # clone https://github.com/asciidoctor/asciidoctor-maven-examples
> # cd asciidoc-maven-site-example
> # mvn site:run
> # Access {{http://localhost:8080/hello.html}}
> * Env:
> {code}
> $ mvn -v
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> Maven home: /home//.sdkman/candidates/maven/current
> Java version: 1.8.0_222, vendor: AdoptOpenJDK, runtime:
> /home/-/.sdkman/candidates/java/8.0.222.hs-adpt/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.1.21-1-manjaro", arch: "amd64", family: "unix
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MNG-6750) Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.6:exploded (pre-exploded-war) openjdk1.8u222
[ https://issues.apache.org/jira/browse/MNG-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918893#comment-16918893 ] Michael Osipov commented on MNG-6750: - Try 3.6.2 first. > Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.6:exploded > (pre-exploded-war) openjdk1.8u222 > --- > > Key: MNG-6750 > URL: https://issues.apache.org/jira/browse/MNG-6750 > Project: Maven > Issue Type: Bug > Environment: NAME="Ubuntu" > VERSION="18.04.3 LTS (Bionic Beaver)" > ID=ubuntu > ID_LIKE=debian > PRETTY_NAME="Ubuntu 18.04.3 LTS" > VERSION_ID="18.04" > # arch > x86_64 > # java -version > openjdk version "1.8.0_222" > OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10) > OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) > # mvn --version > Apache Maven 3.6.0 > Maven home: /usr/share/maven > Java version: 1.8.0_222, vendor: Private Build, runtime: > /usr/lib/jvm/java-8-openjdk-amd64/jre > Default locale: en_US, platform encoding: ANSI_X3.4-1968 > OS name: "linux", version: "4.4.0-154-generic", arch: "amd64", family: "unix" >Reporter: Vibhuti Sawant >Priority: Blocker > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-war-plugin:2.6:exploded (pre-exploded-war) on > project alfresco-platform: Execution pre-exploded-war of goal > org.apache.maven.plugins:maven-war-plugin:2.6:exploded failed: Cannot > construct org.apache.maven.plugin.war.util.WebappStructure as it does not > have a no-args constructor : Cannot construct > org.apache.maven.plugin.war.util.WebappStructure as it does not have a > no-args constructor > [ERROR] Debugging information > [ERROR] message : Cannot construct > org.apache.maven.plugin.war.util.WebappStructure as it does not have a > no-args constructor > [ERROR] cause-exception : > com.thoughtworks.xstream.converters.reflection.ObjectAccessException > [ERROR] cause-message : Cannot construct > org.apache.maven.plugin.war.util.WebappStructure as it does not have a > no-args constructor > [ERROR] class : org.apache.maven.plugin.war.util.WebappStructure > [ERROR] required-type : org.apache.maven.plugin.war.util.WebappStructure > [ERROR] converter-type : > com.thoughtworks.xstream.converters.reflection.ReflectionConverter > [ERROR] path : /webapp-structure > [ERROR] version : null > [ERROR] --- > [ERROR] -> [Help 1] > > please guide in understanding what could be the issue. As the same command > had worked fine with previous openjdk versions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (MSITE-849) Unable to inject MavenProject when using `mvn site:run`
[
https://issues.apache.org/jira/browse/MSITE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918891#comment-16918891
]
Michael Osipov commented on MSITE-849:
--
Not for now, maybe [~rfscholte] has a good clue.
> Unable to inject MavenProject when using `mvn site:run`
> ---
>
> Key: MSITE-849
> URL: https://issues.apache.org/jira/browse/MSITE-849
> Project: Maven Site Plugin
> Issue Type: New Feature
>Affects Versions: 3.7.1, 3.8.2
>Reporter: Abel Salgado Romero
>Assignee: Michael Osipov
>Priority: Major
>
> In https://github.com/asciidoctor/asciidoctor-maven-plugin we inject a
> MavenProject to obtain addition configurations from the pom.xml
> (https://github.com/asciidoctor/asciidoctor-maven-plugin/blob/a4d86a949643ab68c124fd4c1b9b936412637d93/src/main/java/org/asciidoctor/maven/site/AsciidoctorDoxiaParser.java#L54).
> This works fine with {{site:site}}, but when using {{site:run}} and accessing
> one of the Asciidoc generated pages we get the error below.
> I saw that:
> * The error occurs when trying to retrieve the instance of the MavenProject.
> * Behavior is the same if I directly inject the MavenProject instead of using
> a provider. That is, {{site:site}} works, {{site:run}} fails because it
> cannot find the instance.
> {code:java}
> HTTP ERROR 500
> Problem accessing /hello.html. Reason:
> Server Error
> Caused by:
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> 1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot
> access Key[type=org.apache.maven.project.MavenProject, annotation=[none]]
> outside of a scoping block
> at
> org.apache.maven.execution.scope.internal.MojoExecutionScopeModule.configure(MojoExecutionScopeModule.java:55)
> (via modules: org.eclipse.sisu.wire.WireModule ->
> org.apache.maven.execution.scope.internal.MojoExecutionScopeModule)
> while locating org.apache.maven.project.MavenProject
> 1 error
> at
> com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:226)
> at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1053)
> at
> org.asciidoctor.maven.site.AsciidoctorDoxiaParser.parse(AsciidoctorDoxiaParser.java:78)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> {code}
> * How to reproduce:
> # clone https://github.com/asciidoctor/asciidoctor-maven-examples
> # cd asciidoc-maven-site-example
> # mvn site:run
> # Access {{http://localhost:8080/hello.html}}
> * Env:
> {code}
> $ mvn -v
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T21:00:29+02:00)
> Maven home: /home//.sdkman/candidates/maven/current
> Java version: 1.8.0_222, vendor: AdoptOpenJDK, runtime:
> /home/-/.sdkman/candidates/java/8.0.222.hs-adpt/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.1.21-1-manjaro", arch: "amd64", family: "unix
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MNG-6656) Introduce base for build/consumer pom
[ https://issues.apache.org/jira/browse/MNG-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918820#comment-16918820 ] Hudson commented on MNG-6656: - Build unstable in Jenkins: Maven TLP » maven » MNG-6656 #11 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6656/11/ > Introduce base for build/consumer pom > - > > Key: MNG-6656 > URL: https://issues.apache.org/jira/browse/MNG-6656 > Project: Maven > Issue Type: New Feature > Components: POM >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 3.7.0-candidate > > > The pom.xml as we know it has reached it limits, but it is quite hard to do > improvements as long as the local pom (as part of the sources) is exactly the > same as the file being published. > For the Maven eco system it is important that the published file will still > be a model 4.0.0 to ensure other projects can still depend on these artifacts. > This will be a first step to separate the poms and to make it possible to > work on model 5.0.0. > During install/deploy the pom.xml will be adjusted. At first this means > removing the modules and adjusting the relativePath elements. > This is done for the following reasons: > - these elements refer to relative paths on a local system. Once published > these elements don't have any value anymore. > - It will give us experience with manipuating files during install/deploy. > - We can see IDEs and CI servers can handle this and how we can move forward. > This feature will at first be disabled by default and can be activated with > the System property maven.experimental.buildconsumer=true -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [maven-indexer] slachiewicz commented on issue #39: Add getName() to Record.EntryKey
slachiewicz commented on issue #39: Add getName() to Record.EntryKey URL: https://github.com/apache/maven-indexer/pull/39#issuecomment-526280116 Yes, please This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-indexer] sixcorners commented on issue #39: Add getName() to Record.EntryKey
sixcorners commented on issue #39: Add getName() to Record.EntryKey URL: https://github.com/apache/maven-indexer/pull/39#issuecomment-526266758 Should I close this? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MNG-6752) submodule with $revision version can't be referenced by a normal version number
Martin K created MNG-6752:
-
Summary: submodule with $revision version can't be referenced by a
normal version number
Key: MNG-6752
URL: https://issues.apache.org/jira/browse/MNG-6752
Project: Maven
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.6.1
Reporter: Martin K
In the following example, pp/pom.xml can't reference its parent with a specific
version number ("1-SNAPSHOT") - Unless
pp1:pp-pom:pom:1-SNAPSHOT is already present in a maven repository, the build
will fail.
Maven reads the parent poms and caches them, before resolving $revision.
Therefore it just caches the artifact version "${revsion}" and fails to load
the local parent pom, if the parent reference does not also use the version
"${revision}"
Precondition: Non of these artificats is already present in a local or remote
maven repository.
File pom.xml:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
pp
y-pom
yy
pom
1-SNAPSHOT
pp1
pp
1-SNAPSHOT
{code}
File ./pp/pom.xml:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
pp
pp-pom
PP
pom
${revision}
pp1
pp-pom
1-SNAPSHOT
../pp1/pom.xml
1-SNAPSHOT
{code}
File ./pp1/pom.xml:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
pp1
pp-pom
PP
pom
${revision}
1-SNAPSHOT
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (MNG-6751) Warning on empty version of reporting plugins
Radek Antoniuk created MNG-6751:
---
Summary: Warning on empty version of reporting plugins
Key: MNG-6751
URL: https://issues.apache.org/jira/browse/MNG-6751
Project: Maven
Issue Type: Task
Components: Documentation: General
Affects Versions: 3.6.1
Reporter: Radek Antoniuk
Per [https://maven.apache.org/plugins/maven-site-plugin/maven-3.html]
_When used with Maven 3, a report plugin version can be empty (like build
plugins)__._
but I'm still getting a warning on _mvn site_
{noformat}
[WARNING] Report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin has an empty version.
[WARNING] Report plugin org.owasp:dependency-check-maven has an empty version.
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (MNG-6750) Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.6:exploded (pre-exploded-war) openjdk1.8u222
Vibhuti Sawant created MNG-6750: --- Summary: Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.6:exploded (pre-exploded-war) openjdk1.8u222 Key: MNG-6750 URL: https://issues.apache.org/jira/browse/MNG-6750 Project: Maven Issue Type: Bug Environment: NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.3 LTS" VERSION_ID="18.04" # arch x86_64 # java -version openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) # mvn --version Apache Maven 3.6.0 Maven home: /usr/share/maven Java version: 1.8.0_222, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "4.4.0-154-generic", arch: "amd64", family: "unix" Reporter: Vibhuti Sawant [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.6:exploded (pre-exploded-war) on project alfresco-platform: Execution pre-exploded-war of goal org.apache.maven.plugins:maven-war-plugin:2.6:exploded failed: Cannot construct org.apache.maven.plugin.war.util.WebappStructure as it does not have a no-args constructor : Cannot construct org.apache.maven.plugin.war.util.WebappStructure as it does not have a no-args constructor [ERROR] Debugging information [ERROR] message : Cannot construct org.apache.maven.plugin.war.util.WebappStructure as it does not have a no-args constructor [ERROR] cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException [ERROR] cause-message : Cannot construct org.apache.maven.plugin.war.util.WebappStructure as it does not have a no-args constructor [ERROR] class : org.apache.maven.plugin.war.util.WebappStructure [ERROR] required-type : org.apache.maven.plugin.war.util.WebappStructure [ERROR] converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter [ERROR] path : /webapp-structure [ERROR] version : null [ERROR] --- [ERROR] -> [Help 1] please guide in understanding what could be the issue. As the same command had worked fine with previous openjdk versions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (MSHARED-832) Cannot invoke maven from path with parentheses on Windows
Anton Krylov created MSHARED-832:
Summary: Cannot invoke maven from path with parentheses on Windows
Key: MSHARED-832
URL: https://issues.apache.org/jira/browse/MSHARED-832
Project: Maven Shared Components
Issue Type: Bug
Components: maven-invoker
Affects Versions: maven-invoker-2.2
Environment: Windows 10
Reporter: Anton Krylov
When {{M2_HOME}} is set to a path with parentheses (in this case
{{C:\work\lol(1)\maven)}}, the following command is generated on windows:
{noformat}
cmd.exe /X /C "C:\work\lol(1)\maven\bin\mvn.cmd -B -e -V compile"
{noformat}
This command fails, saying that C:\work\lol is not a known command
When a space is added to the path, the path gets escaped, and the command runs
successfully.
It looks like more characters need to be escaped on some platforms
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
