[jira] [Commented] (MNG-5771) improved user-configurable core extensions mechanism
[
https://issues.apache.org/jira/browse/MNG-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643440#comment-14643440
]
Igor Fedorenko commented on MNG-5771:
-
@Yuri I meant d...@maven.apache.org maven development list, not m2e dev list.
sorry for the confusion.
> improved user-configurable core extensions mechanism
>
>
> Key: MNG-5771
> URL: https://issues.apache.org/jira/browse/MNG-5771
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading
>Reporter: Igor Fedorenko
>Assignee: igorfie
> Fix For: 3.3.1
>
>
> As of version 3.2.5 maven provides two mechanisms to contribute additional
> components to maven core runtime. It is possible to add component jars to
> {{$M2_HOME/lib/ext directory}}. It is also possible to specify component jars
> using {{-Dmaven.ext.class.path}} command line parameter. Neither of the
> mechanisms is user friendly. In both cases, the user is expected to manually
> locate and download all required jar file. In both cases, this has to be done
> on all systems where the extensions are needed. In both cases, all extra jars
> are loaded into single classloader so all extensions must agree of the same
> set of dependencies.
> This jira is to track changes needed to make it possible to configure core
> extensions in terms of groupId/artifactId/version and share set of required
> extensions across multiple systems.
> More specifically,
> * introduce new {{$\{maven.projectBasedir\}/.mvn/extensions.xml}} descriptor
> to specify list of extensions. Initially, the descriptor will only allow
> specification of extension groupId/artifactId/version, but can be extended to
> support dependency includes/excludes mechanism and configuration parameters
> later
> {code:xml}
>
>
>
> ...
> ...
> ...
>
> ...
> ...
>
> {code}
> * change maven to read and load core extensions in separate class realms as
> part of plexus container setup.
> * provide mechanism for extensions to declare exported artifacts and packages
> using {{META-INF/maven/extension.xml}} descriptor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MCOMPILER-247) "Pass Compiler Arguments" Documentation is inaccurate
Ben Romberg created MCOMPILER-247:
-
Summary: "Pass Compiler Arguments" Documentation is inaccurate
Key: MCOMPILER-247
URL: https://issues.apache.org/jira/browse/MCOMPILER-247
Project: Maven Compiler Plugin
Issue Type: Bug
Reporter: Ben Romberg
Priority: Minor
The documentation on
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
shows how to pass additional compiler arguments:
{code}
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.3
-verbose
-Xlint:all,-options,-path
[...]
[...]
{code}
It doesn't work, as the {compilerArgs} block needs to be inside the
configuration block. Also, the indentation is off by a few spaces. This is how
it actually works:
{code}
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.3
-verbose
-Xlint:all,-options,-path
[...]
[...]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MCOMPILER-247) "Pass Compiler Arguments" Documentation is inaccurate
[
https://issues.apache.org/jira/browse/MCOMPILER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Romberg updated MCOMPILER-247:
--
Description:
The documentation on
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
shows how to pass additional compiler arguments:
{code}
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.3
-verbose
-Xlint:all,-options,-path
[...]
[...]
{code}
It doesn't work, as the {{compilerArgs}} block needs to be inside the
configuration block. Also, the indentation is off by a few spaces. This is how
it actually works:
{code}
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.3
-verbose
-Xlint:all,-options,-path
[...]
[...]
{code}
was:
The documentation on
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
shows how to pass additional compiler arguments:
{code}
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.3
-verbose
-Xlint:all,-options,-path
[...]
[...]
{code}
It doesn't work, as the {compilerArgs} block needs to be inside the
configuration block. Also, the indentation is off by a few spaces. This is how
it actually works:
{code}
[...]
[...]
org.apache.maven.plugins
maven-compiler-plugin
3.3
-verbose
-Xlint:all,-options,-path
[...]
[...]
{code}
> "Pass Compiler Arguments" Documentation is inaccurate
> -
>
> Key: MCOMPILER-247
> URL: https://issues.apache.org/jira/browse/MCOMPILER-247
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Reporter: Ben Romberg
>Priority: Minor
>
> The documentation on
> http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
> shows how to pass additional compiler arguments:
> {code}
>
> [...]
>
> [...]
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.3
>
> -verbose
> -Xlint:all,-options,-path
>
>
>
> [...]
>
> [...]
>
> {code}
> It doesn't work, as the {{compilerArgs}} block needs to be inside the
> configuration block. Also, the indentation is off by a few spaces. This is
> how it actually works:
> {code}
>
> [...]
>
> [...]
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.3
>
>
> -verbose
> -Xlint:all,-options,-path
>
>
>
>
> [...]
>
> [...]
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5771) improved user-configurable core extensions mechanism
[
https://issues.apache.org/jira/browse/MNG-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643251#comment-14643251
]
Yuri commented on MNG-5771:
---
{quote}
I don't think settings.xml in project basedir is a good idea. User settings are
meant to provide environment specific configuration, like user credentials,
which cannot be shared across different build system.
{quote}
I agree 100%.
{quote}
Using ~/.m2/settings.xml to configure extensions is not a good idea because it
will break earlier versions of maven. I don't have strong opinion about
~/.m2/extension.xml (or something like that). It is probably okay to for
environment specific extensions, like your custom repository extension,
assuming I understood your usercase correctly. I have no immediate plans to
implement this myself, however.
{quote}
I didn't realize it would break earlier versions of maven. In any case,
something like *~/.m2/extension.xml* would work just the same.
Just to be a bit more specific, we are using Spring's S3 Wagon and it provides
us a scalable and fault tolerant storage for our artifacts without the need for
something like Artifactory or Nexus. We used to set this S3 wagon extension in
a parent POM that was released independently, but then we got into a chicken
and egg problem, specially when we have new hires or when bootstrapping a new
laptop or when recreating *~/.m2/repo*: how to download the parent POM when it
is the one that would tell maven how.
So we moved the urls to settings.xml as properties in an
active-by-default profile and we started distributing a custom Maven
distribution with the S3 wagon jars embedded in the *lib/ext* folder. It works
but it is a bit of a pain specially when there are new versions etc. If we were
able to provide every developer a *~/.m2/settings.xml* and a
*~/.m2/extension.xml* then both the S3 urls and the S3 wagon that can
read/write these urls, then we would be done with it.
> improved user-configurable core extensions mechanism
>
>
> Key: MNG-5771
> URL: https://issues.apache.org/jira/browse/MNG-5771
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading
>Reporter: Igor Fedorenko
>Assignee: igorfie
> Fix For: 3.3.1
>
>
> As of version 3.2.5 maven provides two mechanisms to contribute additional
> components to maven core runtime. It is possible to add component jars to
> {{$M2_HOME/lib/ext directory}}. It is also possible to specify component jars
> using {{-Dmaven.ext.class.path}} command line parameter. Neither of the
> mechanisms is user friendly. In both cases, the user is expected to manually
> locate and download all required jar file. In both cases, this has to be done
> on all systems where the extensions are needed. In both cases, all extra jars
> are loaded into single classloader so all extensions must agree of the same
> set of dependencies.
> This jira is to track changes needed to make it possible to configure core
> extensions in terms of groupId/artifactId/version and share set of required
> extensions across multiple systems.
> More specifically,
> * introduce new {{$\{maven.projectBasedir\}/.mvn/extensions.xml}} descriptor
> to specify list of extensions. Initially, the descriptor will only allow
> specification of extension groupId/artifactId/version, but can be extended to
> support dependency includes/excludes mechanism and configuration parameters
> later
> {code:xml}
>
>
>
> ...
> ...
> ...
>
> ...
> ...
>
> {code}
> * change maven to read and load core extensions in separate class realms as
> part of plexus container setup.
> * provide mechanism for extensions to declare exported artifacts and packages
> using {{META-INF/maven/extension.xml}} descriptor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSHADE-200) Property in parent.artifactId isn't interpolated
Chiwan Park created MSHADE-200:
--
Summary: Property in parent.artifactId isn't interpolated
Key: MSHADE-200
URL: https://issues.apache.org/jira/browse/MSHADE-200
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 2.4.1
Reporter: Chiwan Park
I'm using property in project artifact id to support multiple scala version
like following:
{code}
org.apache.flink
flink-parent${scala.suffix}
0.10-SNAPSHOT
{code}
So child pom have to direct parent with property.
{code}
org.apache.flink
flink-parent${scala.suffix}
0.10-SNAPSHOT
..
flink-scala${scala.suffix}
flink-scala
{code}
In dependency reduced pom, I expected that property in parent artifactId is
interpolated. But I found that there is untouched property expression.
{code}
flink-parent${scala.suffix}
org.apache.flink
0.10-SNAPSHOT
../../pom.xml
4.0.0
flink-scala_2.11
flink-scala
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MASSEMBLY-782) DependencySets fails to bring a transitive dependency declared in another circular dependency
[
https://issues.apache.org/jira/browse/MASSEMBLY-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent TOURREAU updated MASSEMBLY-782:
---
Description:
See as attachment the pom.xml and assembly.xml
I have declared a dependency to Apache FOP:
{code}
org.apache.xmlgraphics
fop
0.95
{code}
A dependency:tree give us:
{code}
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ my-app ---
[INFO] com.mycompany:my-app:pom:0.0.1-SNAPSHOT
[INFO] \- org.apache.xmlgraphics:fop:jar:0.95:compile
[INFO]+- org.apache.xmlgraphics:xmlgraphics-commons:jar:1.3.1:compile
[INFO]+- org.apache.xmlgraphics:batik-svg-dom:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-anim:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-css:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-dom:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-parser:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-util:jar:1.7:compile
[INFO]| +- xml-apis:xml-apis:jar:1.3.04:compile
[INFO]| \- xml-apis:xml-apis-ext:jar:1.3.04:compile
[INFO]+- org.apache.xmlgraphics:batik-bridge:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-script:jar:1.7:compile
[INFO]| | \- org.apache.xmlgraphics:batik-js:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-xml:jar:1.7:compile
[INFO]| \- xalan:xalan:jar:2.6.0:compile
[INFO]+- org.apache.xmlgraphics:batik-awt-util:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-gvt:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-transcoder:jar:1.7:compile
[INFO]| \- org.apache.xmlgraphics:batik-svggen:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-extension:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-ext:jar:1.7:compile
[INFO]+- commons-logging:commons-logging:jar:1.0.4:compile
[INFO]+- commons-io:commons-io:jar:1.3.1:compile
[INFO]\- org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
{code}
In the assembly.xml i only declare this clause:
{code}
{code}
In the zip the library batik-js-1.7.jar is missing.
According to me the root cause is on batik-script and batik-script pom.xml
dependencies declaration.
batik-bridge pom.xml:
{code}
...
org.apache.xmlgraphics
batik-script
1.7
...
{code}
batik-script pom.xml:
{code}
...
org.apache.xmlgraphics
batik-bridge
1.7
...
org.apache.xmlgraphics
batik-js
1.7
...
{code}
batik-script references batik-bridge which references batik-script.
DependencySet is unable to resolve and retrieve batik-js dependency.
was:
See as attachment the pom.xml and assembly.xml
I have declared a dependency to Apache FOP:
{code}
org.apache.xmlgraphics
fop
0.95
{code}
A dependency:tree give us:
{code}
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ my-app ---
[INFO] com.mycompany:my-app:pom:0.0.1-SNAPSHOT
[INFO] \- org.apache.xmlgraphics:fop:jar:0.95:compile
[INFO]+- org.apache.xmlgraphics:xmlgraphics-commons:jar:1.3.1:compile
[INFO]+- org.apache.xmlgraphics:batik-svg-dom:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-anim:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-css:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-dom:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-parser:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-util:jar:1.7:compile
[INFO]| +- xml-apis:xml-apis:jar:1.3.04:compile
[INFO]| \- xml-apis:xml-apis-ext:jar:1.3.04:compile
[INFO]+- org.apache.xmlgraphics:batik-bridge:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-script:jar:1.7:compile
[INFO]| | \- org.apache.xmlgraphics:batik-js:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-xml:jar:1.7:compile
[INFO]| \- xalan:xalan:jar:2.6.0:compile
[INFO]+- org.apache.xmlgraphics:batik-awt-util:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-gvt:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-transcoder:jar:1.7:compile
[INFO]| \- org.apache.xmlgraphics:batik-svggen:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-extension:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-ext:jar:1.7:compile
[INFO]+- commons-logging:commons-logging:jar:1.0.4:compile
[INFO]+- commons-io:commons-io:jar:1.3.1:compile
[INFO]\- org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
{code}
In the assembly.xml i only declare this clause:
{code}
{code}
In the zip the library batik-js-1.7.jar is missing.
According to me the root cause is on batik-script
[jira] [Updated] (MASSEMBLY-782) DependencySets fails to bring a transitive dependency declared in another circular dependency
[
https://issues.apache.org/jira/browse/MASSEMBLY-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent TOURREAU updated MASSEMBLY-782:
---
Attachment: pom.xml
assembly.xml
> DependencySets fails to bring a transitive dependency declared in another
> circular dependency
> -
>
> Key: MASSEMBLY-782
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-782
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: dependencySet
>Affects Versions: 2.1, 2.2, 2.3, 2.4, 2.4.1, 2.5.1, 2.5.2, 2.5.3, 2.5.4,
> 2.5.5
> Environment: Maven 3.2.5
>Reporter: Laurent TOURREAU
>Priority: Critical
> Attachments: assembly.xml, pom.xml
>
>
> See as attachment the pom.xml and assembly.xml
> I have declared a dependency to Apache FOP:
> {code}
>
>
> org.apache.xmlgraphics
> fop
> 0.95
>
>
> {code}
> A dependency:tree give us:
> {code}
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ my-app ---
> [INFO] com.mycompany:my-app:pom:0.0.1-SNAPSHOT
> [INFO] \- org.apache.xmlgraphics:fop:jar:0.95:compile
> [INFO]+- org.apache.xmlgraphics:xmlgraphics-commons:jar:1.3.1:compile
> [INFO]+- org.apache.xmlgraphics:batik-svg-dom:jar:1.7:compile
> [INFO]| +- org.apache.xmlgraphics:batik-anim:jar:1.7:compile
> [INFO]| +- org.apache.xmlgraphics:batik-css:jar:1.7:compile
> [INFO]| +- org.apache.xmlgraphics:batik-dom:jar:1.7:compile
> [INFO]| +- org.apache.xmlgraphics:batik-parser:jar:1.7:compile
> [INFO]| +- org.apache.xmlgraphics:batik-util:jar:1.7:compile
> [INFO]| +- xml-apis:xml-apis:jar:1.3.04:compile
> [INFO]| \- xml-apis:xml-apis-ext:jar:1.3.04:compile
> [INFO]+- org.apache.xmlgraphics:batik-bridge:jar:1.7:compile
> [INFO]| +- org.apache.xmlgraphics:batik-script:jar:1.7:compile
> [INFO]| | \- org.apache.xmlgraphics:batik-js:jar:1.7:compile
> [INFO]| +- org.apache.xmlgraphics:batik-xml:jar:1.7:compile
> [INFO]| \- xalan:xalan:jar:2.6.0:compile
> [INFO]+- org.apache.xmlgraphics:batik-awt-util:jar:1.7:compile
> [INFO]+- org.apache.xmlgraphics:batik-gvt:jar:1.7:compile
> [INFO]+- org.apache.xmlgraphics:batik-transcoder:jar:1.7:compile
> [INFO]| \- org.apache.xmlgraphics:batik-svggen:jar:1.7:compile
> [INFO]+- org.apache.xmlgraphics:batik-extension:jar:1.7:compile
> [INFO]+- org.apache.xmlgraphics:batik-ext:jar:1.7:compile
> [INFO]+- commons-logging:commons-logging:jar:1.0.4:compile
> [INFO]+- commons-io:commons-io:jar:1.3.1:compile
> [INFO]\-
> org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
> {code}
> In the assembly.xml i only declare this clause:
> {code}
>
>
>
>
> {code}
> In the zip the library batik-js-1.7.jar is missing.
> According to me the root cause is on batik-script and batik-script pom.xml
> dependencies declaration.
> batik-bridge pom.xml:
> {code}
> ...
>
> org.apache.xmlgraphics
> batik-script
> 1.7
>
> ...
> {code}
> batik-script pom.xml:
> {code}
> ...
>
> org.apache.xmlgraphics
> batik-bridge
> 1.7
>
> ...
>
> org.apache.xmlgraphics
> batik-js
> 1.7
>
> ...
> {code}
> batik-script references batik-bridge which references batik-script.
> DependencySet is unable to resole and retrieve batik-js dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MASSEMBLY-782) DependencySets fails to bring a transitive dependency declared in another circular dependency
Laurent TOURREAU created MASSEMBLY-782:
--
Summary: DependencySets fails to bring a transitive dependency
declared in another circular dependency
Key: MASSEMBLY-782
URL: https://issues.apache.org/jira/browse/MASSEMBLY-782
Project: Maven Assembly Plugin
Issue Type: Bug
Components: dependencySet
Affects Versions: 2.5.5, 2.5.4, 2.5.3, 2.5.2, 2.5.1, 2.4.1, 2.4, 2.3, 2.2,
2.1
Environment: Maven 3.2.5
Reporter: Laurent TOURREAU
Priority: Critical
See as attachment the pom.xml and assembly.xml
I have declared a dependency to Apache FOP:
{code}
org.apache.xmlgraphics
fop
0.95
{code}
A dependency:tree give us:
{code}
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ my-app ---
[INFO] com.mycompany:my-app:pom:0.0.1-SNAPSHOT
[INFO] \- org.apache.xmlgraphics:fop:jar:0.95:compile
[INFO]+- org.apache.xmlgraphics:xmlgraphics-commons:jar:1.3.1:compile
[INFO]+- org.apache.xmlgraphics:batik-svg-dom:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-anim:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-css:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-dom:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-parser:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-util:jar:1.7:compile
[INFO]| +- xml-apis:xml-apis:jar:1.3.04:compile
[INFO]| \- xml-apis:xml-apis-ext:jar:1.3.04:compile
[INFO]+- org.apache.xmlgraphics:batik-bridge:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-script:jar:1.7:compile
[INFO]| | \- org.apache.xmlgraphics:batik-js:jar:1.7:compile
[INFO]| +- org.apache.xmlgraphics:batik-xml:jar:1.7:compile
[INFO]| \- xalan:xalan:jar:2.6.0:compile
[INFO]+- org.apache.xmlgraphics:batik-awt-util:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-gvt:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-transcoder:jar:1.7:compile
[INFO]| \- org.apache.xmlgraphics:batik-svggen:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-extension:jar:1.7:compile
[INFO]+- org.apache.xmlgraphics:batik-ext:jar:1.7:compile
[INFO]+- commons-logging:commons-logging:jar:1.0.4:compile
[INFO]+- commons-io:commons-io:jar:1.3.1:compile
[INFO]\- org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
{code}
In the assembly.xml i only declare this clause:
{code}
{code}
In the zip the library batik-js-1.7.jar is missing.
According to me the root cause is on batik-script and batik-script pom.xml
dependencies declaration.
batik-bridge pom.xml:
{code}
...
org.apache.xmlgraphics
batik-script
1.7
...
{code}
batik-script pom.xml:
{code}
...
org.apache.xmlgraphics
batik-bridge
1.7
...
org.apache.xmlgraphics
batik-js
1.7
...
{code}
batik-script references batik-bridge which references batik-script.
DependencySet is unable to resole and retrieve batik-js dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD
[
https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642721#comment-14642721
]
Arthur Bauer edited comment on MNG-5821 at 7/27/15 1:42 PM:
There are 3 maven projects in the attached zip file:
- bundle
- child
- parent
Just try to build the bundle. It will fail with a message like this:
{code}
[ERROR] Non-resolvable parent POM: Failure to find
test:parent:pom:1.0-SNAPSHOT in http://mvn.intra/artifactory/libs-snapshot was
cached in the local repository, resolution will not be reattempted until the
update interval of snapshots has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 5, column 11 -> [Help 2]
{code}
But if you build the parent project first (mvn install) and then build the
bundle project it will succeed.
was (Author: arci):
There are 3 maven projects in the attached zip file:
- bundle
- child
- parent
Just try to build the bundle. It will fail a message like this:
{code}
[ERROR] Non-resolvable parent POM: Failure to find
test:parent:pom:1.0-SNAPSHOT in http://mvn.intra/artifactory/libs-snapshot was
cached in the local repository, resolution will not be reattempted until the
update interval of snapshots has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 5, column 11 -> [Help 2]
{code}
But if you build the parent project first (mvn install) and then build the
bundle project it will succeed.
> Documentation of the element parent.relativePath wrong in XSD
> -
>
> Key: MNG-5821
> URL: https://issues.apache.org/jira/browse/MNG-5821
> Project: Maven
> Issue Type: Documentation
>Reporter: Arthur Bauer
> Fix For: waiting-for-feedback
>
> Attachments: test.zip
>
>
> The documentation of the element parent.relativePath in the XSD file seems to
> be wrong or outdated. It says:
> "Maven looks for the parent pom first in the reactor of currently building
> projects, then in this location on the filesystem, then the local repository,
> and lastly in the remote repo."
> (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd)
> But the actual documentation of maven says
> "Maven looks for the parent POM first in this location on the filesystem,
> then the local repository, and lastly in the remote repo."
> (Source:
> http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29)
> I have tested it on my local and I have seen the behavior as described in the
> second source, i.e. maven does not look for the parent pom in the reactor of
> currently building projects first.
> So this is pretty misleading. It is even more misleading for us, as we are
> reading the documentation directly from eclipse, which loads it from the XSD
> file.
> Could you please correct the XSD documentation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD
[
https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642721#comment-14642721
]
Arthur Bauer edited comment on MNG-5821 at 7/27/15 1:41 PM:
There are 3 maven projects in the attached zip file:
- bundle
- child
- parent
Just try to build the bundle. It will fail a message like this:
{code}
[ERROR] Non-resolvable parent POM: Failure to find
test:parent:pom:1.0-SNAPSHOT in http://mvn.intra/artifactory/libs-snapshot was
cached in the local repository, resolution will not be reattempted until the
update interval of snapshots has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 5, column 11 -> [Help 2]
{code}
But if you build the parent project first (mvn install) and then build the
bundle project it will succeed.
was (Author: arci):
There are 3 maven projects in the attached zip file:
- bundle
- child
- parent
Just try to build the bundle. It will fail a message like this:
[ERROR] Non-resolvable parent POM: Failure to find
test:parent:pom:1.0-SNAPSHOT in http://mvn.intra/artifactory/libs-snapshot was
cached in the local repository, resolution will not be reattempted until the
update interval of snapshots has elapsed or updates are forced and
'parent.relativePath' points at wrong local POM @ line 5, column 11 -> [Help 2]
But if you build the parent project first (mvn install) and then build the
bundle project it will succeed.
> Documentation of the element parent.relativePath wrong in XSD
> -
>
> Key: MNG-5821
> URL: https://issues.apache.org/jira/browse/MNG-5821
> Project: Maven
> Issue Type: Documentation
>Reporter: Arthur Bauer
> Fix For: waiting-for-feedback
>
> Attachments: test.zip
>
>
> The documentation of the element parent.relativePath in the XSD file seems to
> be wrong or outdated. It says:
> "Maven looks for the parent pom first in the reactor of currently building
> projects, then in this location on the filesystem, then the local repository,
> and lastly in the remote repo."
> (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd)
> But the actual documentation of maven says
> "Maven looks for the parent POM first in this location on the filesystem,
> then the local repository, and lastly in the remote repo."
> (Source:
> http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29)
> I have tested it on my local and I have seen the behavior as described in the
> second source, i.e. maven does not look for the parent pom in the reactor of
> currently building projects first.
> So this is pretty misleading. It is even more misleading for us, as we are
> reading the documentation directly from eclipse, which loads it from the XSD
> file.
> Could you please correct the XSD documentation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD
[ https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642721#comment-14642721 ] Arthur Bauer commented on MNG-5821: --- There are 3 maven projects in the attached zip file: - bundle - child - parent Just try to build the bundle. It will fail a message like this: [ERROR] Non-resolvable parent POM: Failure to find test:parent:pom:1.0-SNAPSHOT in http://mvn.intra/artifactory/libs-snapshot was cached in the local repository, resolution will not be reattempted until the update interval of snapshots has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 5, column 11 -> [Help 2] But if you build the parent project first (mvn install) and then build the bundle project it will succeed. > Documentation of the element parent.relativePath wrong in XSD > - > > Key: MNG-5821 > URL: https://issues.apache.org/jira/browse/MNG-5821 > Project: Maven > Issue Type: Documentation >Reporter: Arthur Bauer > Fix For: waiting-for-feedback > > Attachments: test.zip > > > The documentation of the element parent.relativePath in the XSD file seems to > be wrong or outdated. It says: > "Maven looks for the parent pom first in the reactor of currently building > projects, then in this location on the filesystem, then the local repository, > and lastly in the remote repo." > (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd) > But the actual documentation of maven says > "Maven looks for the parent POM first in this location on the filesystem, > then the local repository, and lastly in the remote repo." > (Source: > http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29) > I have tested it on my local and I have seen the behavior as described in the > second source, i.e. maven does not look for the parent pom in the reactor of > currently building projects first. > So this is pretty misleading. It is even more misleading for us, as we are > reading the documentation directly from eclipse, which loads it from the XSD > file. > Could you please correct the XSD documentation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD
[ https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Bauer updated MNG-5821: -- Attachment: test.zip > Documentation of the element parent.relativePath wrong in XSD > - > > Key: MNG-5821 > URL: https://issues.apache.org/jira/browse/MNG-5821 > Project: Maven > Issue Type: Documentation >Reporter: Arthur Bauer > Fix For: waiting-for-feedback > > Attachments: test.zip > > > The documentation of the element parent.relativePath in the XSD file seems to > be wrong or outdated. It says: > "Maven looks for the parent pom first in the reactor of currently building > projects, then in this location on the filesystem, then the local repository, > and lastly in the remote repo." > (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd) > But the actual documentation of maven says > "Maven looks for the parent POM first in this location on the filesystem, > then the local repository, and lastly in the remote repo." > (Source: > http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29) > I have tested it on my local and I have seen the behavior as described in the > second source, i.e. maven does not look for the parent pom in the reactor of > currently building projects first. > So this is pretty misleading. It is even more misleading for us, as we are > reading the documentation directly from eclipse, which loads it from the XSD > file. > Could you please correct the XSD documentation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD
[ https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642715#comment-14642715 ] Arthur Bauer commented on MNG-5821: --- I have tested it with Maven 3.0.3 and 3.2.5 with the same behavior. > Documentation of the element parent.relativePath wrong in XSD > - > > Key: MNG-5821 > URL: https://issues.apache.org/jira/browse/MNG-5821 > Project: Maven > Issue Type: Documentation >Reporter: Arthur Bauer > Fix For: waiting-for-feedback > > > The documentation of the element parent.relativePath in the XSD file seems to > be wrong or outdated. It says: > "Maven looks for the parent pom first in the reactor of currently building > projects, then in this location on the filesystem, then the local repository, > and lastly in the remote repo." > (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd) > But the actual documentation of maven says > "Maven looks for the parent POM first in this location on the filesystem, > then the local repository, and lastly in the remote repo." > (Source: > http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29) > I have tested it on my local and I have seen the behavior as described in the > second source, i.e. maven does not look for the parent pom in the reactor of > currently building projects first. > So this is pretty misleading. It is even more misleading for us, as we are > reading the documentation directly from eclipse, which loads it from the XSD > file. > Could you please correct the XSD documentation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-5821) Documentation of the element parent.relativePath wrong in XSD
[ https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Bauer updated MNG-5821: -- Description: The documentation of the element parent.relativePath in the XSD file seems to be wrong or outdated. It says: "Maven looks for the parent pom first in the reactor of currently building projects, then in this location on the filesystem, then the local repository, and lastly in the remote repo." (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd) But the actual documentation of maven says "Maven looks for the parent POM first in this location on the filesystem, then the local repository, and lastly in the remote repo." (Source: http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29) I have tested it on my local and I have seen the behavior as described in the second source, i.e. maven does not look for the parent pom in the reactor of currently building projects first. So this is pretty misleading. It is even more misleading for us, as we are reading the documentation directly from eclipse, which loads it from the XSD file. Could you please correct the XSD documentation? was: The documentation of the element parent.relativePath in the XSD file seems to be wrong or outdated. It says: "Maven looks for the parent pom first in the reactor of currently building projects, then in this location on the filesystem, then the local repository, and lastly in the remote repo." (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd) But the actual documentation of maven says "Maven looks for the parent POM first in this location on the filesystem, then the local repository, and lastly in the remote repo." (Source: http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29) I have tested it on my local and I have seen the behavior as described in the second source, i.e. maven does not look for the parent pom in the reactor of currently building projects first. So this is pretty misleading. It is even more true for us, as we are reading the documentation directly from eclipse, which loads it from the XSD file. Could you please correct the XSD documentation? > Documentation of the element parent.relativePath wrong in XSD > - > > Key: MNG-5821 > URL: https://issues.apache.org/jira/browse/MNG-5821 > Project: Maven > Issue Type: Documentation >Reporter: Arthur Bauer > Fix For: waiting-for-feedback > > > The documentation of the element parent.relativePath in the XSD file seems to > be wrong or outdated. It says: > "Maven looks for the parent pom first in the reactor of currently building > projects, then in this location on the filesystem, then the local repository, > and lastly in the remote repo." > (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd) > But the actual documentation of maven says > "Maven looks for the parent POM first in this location on the filesystem, > then the local repository, and lastly in the remote repo." > (Source: > http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29) > I have tested it on my local and I have seen the behavior as described in the > second source, i.e. maven does not look for the parent pom in the reactor of > currently building projects first. > So this is pretty misleading. It is even more misleading for us, as we are > reading the documentation directly from eclipse, which loads it from the XSD > file. > Could you please correct the XSD documentation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNGSITE-252) Broken link on web-site
Felix Lefort created MNGSITE-252: Summary: Broken link on web-site Key: MNGSITE-252 URL: https://issues.apache.org/jira/browse/MNGSITE-252 Project: Maven Project Web Site Issue Type: Access Reporter: Felix Lefort Priority: Minor Hello, there's a broken link on: http://maven.apache.org/guides/introduction/introduction-to-archetypes.html The one to 'Maven Archetypes page' leads to a 'page not found' error. Regards, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
