[jira] Updated: (MNG-3866) Plugin definitions from child and parent are not merged when version differs
[
http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3866:
---
Attachment: (was: plugin-model-container.patch)
> Plugin definitions from child and parent are not merged when version differs
>
>
> Key: MNG-3866
> URL: http://jira.codehaus.org/browse/MNG-3866
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
> Attachments: plugin-model-container.patch
>
>
> Parent POM snippet
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
>
>
> PASSED
>
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> Effective child POM:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> i.e. the configuration from the parent POM is completely lost.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3866) Plugin definitions from child and parent are not merged when version differs
[
http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3866:
---
Attachment: plugin-model-container.patch
Proposed patch, using a dedicated PluginModelContainer.
> Plugin definitions from child and parent are not merged when version differs
>
>
> Key: MNG-3866
> URL: http://jira.codehaus.org/browse/MNG-3866
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
> Attachments: plugin-model-container.patch
>
>
> Parent POM snippet
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
>
>
> PASSED
>
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> Effective child POM:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> i.e. the configuration from the parent POM is completely lost.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3866) Plugin definitions from child and parent are not merged when version differs
[
http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3866:
---
Attachment: plugin-model-container.patch
> Plugin definitions from child and parent are not merged when version differs
>
>
> Key: MNG-3866
> URL: http://jira.codehaus.org/browse/MNG-3866
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
> Attachments: plugin-model-container.patch
>
>
> Parent POM snippet
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
>
>
> PASSED
>
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> Effective child POM:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> i.e. the configuration from the parent POM is completely lost.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3871) war-dependency is not resolved from a remote repository
[ http://jira.codehaus.org/browse/MNG-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155849#action_155849 ] Robert Scholte commented on MNG-3871: - For those interested: this issue was first addressed by me to nexus [https://issues.sonatype.org/browse/NEXUS-1182] but it seems it's not nexus who's causing a problem. > war-dependency is not resolved from a remote repository > --- > > Key: MNG-3871 > URL: http://jira.codehaus.org/browse/MNG-3871 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9, 2.1.0-M1 > Environment: linux, windows >Reporter: Robert Scholte > > I've used the overlay-example to include a war-dependecy in a webapp-project. > But this only seems to work if the dependency is available in the local > repository. I use nexus and thought the problem was there, but after > including a filter to log all servletRequests I didn't see any request for > the war-dependency. > I've tried it on several OS and also some differrent maven-version. They all > had the same problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3814) Reactor builds fail due to erroneous cycle in project sorting which does not consider versions
[
http://jira.codehaus.org/browse/MNG-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155844#action_155844
]
Régis Décamps commented on MNG-3814:
The problem occurs with any type of dependency. It can be a plugin dependency
or a dependency.
My project fails because
module-1.1 (uses plugin)-> plugin-1.0 (which depends on)-> module-1.0
> Reactor builds fail due to erroneous cycle in project sorting which does not
> consider versions
> --
>
> Key: MNG-3814
> URL: http://jira.codehaus.org/browse/MNG-3814
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 2.0.9, 2.1.0-M1, 3.0-alpha-1
>Reporter: Benjamin Bentmann
>
> Just to officially track the reason why the parent POM {{maven-plugins}}
> currently excludes the maven-project-info-reports-plugin from the reactor:
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] The projects in the reactor contain a cyclic reference:
> Edge between
> 'Vertex{label='org.apache.maven.plugins:maven-remote-resources-plugin'}'
> and
> 'Vertex{label='org.apache.maven.plugins:maven-project-info-reports-plugin'}'
> introduces to cycle in the graph
> org.apache.maven.plugins:maven-project-info-reports-plugin -->
> org.apache.maven.plugins:maven-remote-resources-plugin -->
> org.apache.maven.plugins:maven-project-info-reports-plugin
> {noformat}
> It appears the {{ProjectSorter}} does not take versions into account, i.e.
> there is no cycle in a multi-module scenario like this:
> {noformat}
> parent:1
> - plugin-a:2.0 which uses plugin-b:1.0
> - plugin-b:2.0 which uses plugin-a:1.0
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3380) MavenMetadataSource retrieves ResolutionGroup without consulting ManagedVersionMap, is problem when relocation
[
http://jira.codehaus.org/browse/MNG-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3380:
---
Description:
Consider the following scenario:
{code:xml}
4.0.0
root-groupId
root-artifactId
1
direct-dependency-groupId
direct-dependency-artifactId
1
transitive-dependency-new-groupId
transitive-dependency-artifactId
2
{code}
{code:xml}
4.0.0
direct-dependency-groupId
direct-dependency-artifactId
1
transitive-dependency-old-groupId
transitive-dependency-artifactId
1
{code}
{code:xml}
4.0.0
transitive-dependency-old-groupId
transitive-dependency-artifactId
1
transitive-dependency-new-groupId
{code}
{code:xml}
4.0.0
transitive-dependency-new-groupId
transitive-dependency-artifactId
1
other-groupId
other-artifactId-a
1
{code}
{code:xml}
4.0.0
transitive-dependency-new-groupId
transitive-dependency-artifactId
2
other-groupId
other-artifactId-a
1
other-groupId
other-artifactId-b
1
{code}
{noformat}
--
actual dependency:tree
root-groupId:root-artifactId:jar:1
\- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile
\-
transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile
(version managed from 1)
\- other-groupId:other-artifactId-a:jar:1:compile
--
expected dependency:tree
root-groupId:root-artifactId:jar:1
\- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile
\-
transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile
(version managed from 1)
\- other-groupId:other-artifactId-a:jar:1:compile
\- other-groupId:other-artifactId-b:jar:1:compile <-- missing from
actual result
--
{noformat}
As you can see from the listing above,
other-groupId:other-artifactId-b:jar:1:compile is missing from the dependency
list.
I have attached the zipped repo which was used when generating the
dependency:tree listings shown above. I also attached a crude temporary patch
which my team is currently using to resolve this issue. After ignoring
whitespace changes, it is about 10 lines different.
Thanks,
Luke
was:
Consider the following scenario:
4.0.0
root-groupId
root-artifactId
1
direct-dependency-groupId
direct-dependency-artifactId
1
transitive-dependency-new-groupId
transitive-dependency-artifactId
2
4.0.0
direct-dependency-groupId
direct-dependency-artifactId
1
transitive-dependency-old-groupId
transitive-dependency-artifactId
1
4.0.0
transitive-dependency-old-groupId
transitive-dependency-artifactId
1
transitive-dependency-new-groupId
4.0.0
transitive-dependency-new-groupId
transitive-dependency-artifactId
1
other-groupId
other-artifactId-a
1
4.0.0
transitive-dependency-new-groupId
transitive-dependency-artifactId
2
other-groupId
other-artifactId-a
1
other-groupId
other-artifactId-b
1
--
actual dependency:tree
root-groupId:root-artifactId:jar:1
\- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile
\-
transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile
(version managed from 1)
\- other-groupId:other-artifactId-a:jar:1:compile
--
expected dependency:tree
root-groupId:root-artifactId:jar:1
\- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile
\-
transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile
(version managed from 1)
\- other-groupId:other-artifactId-a:jar:1:compile
\- other-groupId:other-artifactId-b:jar:1:compile <-- missing from
actual result
--
As you can see from the listing above,
other-groupId:other-artifactId-b:jar:1:compile is missing from the dependency
list.
I have attached the zipped repo which was
[jira] Commented: (MAVENUPLOAD-2286) nez sync rule from sourceforge project
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155811#action_155811 ] Christophe Lallement commented on MAVENUPLOAD-2286: --- maybe there is an error and the hostname to sync is: "org.jvyaml","[EMAIL PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","ouaibsky.free.fr",, > nez sync rule from sourceforge project > -- > > Key: MAVENUPLOAD-2286 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2286 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Christophe Lallement > > "org.jvyaml","[EMAIL > PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","ouaibsky.free.fr",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2287) New opensource library (swing) to sync with central repository: JBusyComponent
New opensource library (swing) to sync with central repository: JBusyComponent -- Key: MAVENUPLOAD-2287 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2287 Project: Maven Upload Requests Issue Type: Wish Reporter: Christophe Lallement "org.divxdede","[EMAIL PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","[EMAIL PROTECTED]",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2286) nez sync rule from sourceforge project
nez sync rule from sourceforge project -- Key: MAVENUPLOAD-2286 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2286 Project: Maven Upload Requests Issue Type: Wish Reporter: Christophe Lallement "org.jvyaml","[EMAIL PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","ouaibsky.free.fr",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3877) Reporting output directory not basedir aligned when queried from MavenProject
Reporting output directory not basedir aligned when queried from MavenProject
-
Key: MNG-3877
URL: http://jira.codehaus.org/browse/MNG-3877
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle, POM
Affects Versions: 2.1.0-M1, 2.0.9, 3.0-alpha-1
Reporter: Benjamin Bentmann
Priority: Minor
Calliing {{MavenProject.getReporting().getOutputDirectory()}} inside a plugin
delivers a relative path in case the corresponding POM element was specified
using a relative path.
This is a very close relative of MNG-3475 (basedir-aligned plugin parameter
expressions) and MNG-3822 (basedir-aligned interpolation) but occurs in a
different context.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
