[jira] Commented: (MECLIPSE-597) Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management)
[
https://jira.codehaus.org/browse/MECLIPSE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274588#comment-274588
]
Robrecht Anrijs commented on MECLIPSE-597:
--
The environment is indeed irrelevant. The provided patch works when installing
on version 2.8 of the plugin.
Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a
different version from that in dependency management)
---
Key: MECLIPSE-597
URL: https://jira.codehaus.org/browse/MECLIPSE-597
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path
(.classpath)
Affects Versions: 2.7
Environment: Nexus 1.3.6, Eclipse 3.4, Windows XP
Reporter: Michal Galet
Priority: Critical
Attachments: maven-eclipse-plugin-2.7.patch
When generating eclipse project with mvn eclipse:eclipse
-Declipse.workspace=d:/eclipse-ws the SNAPSHOT dependencies are not resolved
from workspace correctly. See console output below. This is probably caused
by the way how Nexus handles the SNAPSHOTs. The artifact is resolved by
ArtifactResolver and the version is changed from 1.1.0-SNAPSHOT to
1.1.0-20090819.145009-4.
The comparison should be performed against {{artifact.getBaseVersion()}}
instead of {{artifact.getVersion()}}. A simple fix is attached as a patch.
Console output:
[INFO] Artifact com.test:sample:jar:4.0.0.B02-SNAPSHOT already available a
s a workspace project, but with different version. Expected:
4.0.0.B02-20090819.145009-4, found
: 4.0.0.B02-SNAPSHOT
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5142) allow static URLSs which don't change in derived submodules
[
https://jira.codehaus.org/browse/MNG-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274621#comment-274621
]
Robert Scholte commented on MNG-5142:
-
The {{absolute=true}} assumes there are only two options: {{absolute}} and
{{not absolute}}, which could be {{relative}}. There might be more complex
transitions possible, like relative to the parents parent, although this will
be a rare case.
Binding it to two states could bring us into trouble in the future.
I'd suggest to use an attribute like {{transition}} or {{location}} with at
least support for {{relative}} and {{absolute}}.
allow static URLSs which don't change in derived submodules
---
Key: MNG-5142
URL: https://jira.codehaus.org/browse/MNG-5142
Project: Maven 2 3
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.2.1, 3.0.3
Reporter: Mark Struberg
In sub-modules, URLs in the MavenModel will automatically get expanded by
adding the artifactId of the very sub-module.
This is fine for e.g. a SVN scm URL but breaks other SCMs like git or hg.
Proposal:
We should introduce a 'static:' prefix for URLs which must not get
automatically expanded in submodules.
An example:
scm
developerConnectionstatic:scm:git:https://myserver.com/gitrepo/...
The 'static:' info will get removed while parsing the pom.
Compat notes:
I've tried that such scm URLs with mvn-3.0.3 and mvn-2.2.1 in
scmconnection, developerConnection, url,
distributionManagementsiteurl
and got no error building my project. Of course, if you use the 'static:'
prefix then you cannot release or do other site and scm tasks with an old
maven version anymore. But that part is considered to be broken anyway at the
moment ;)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-693) Some generated xml files are missing their xml-header
Some generated xml files are missing their xml-header
-
Key: MECLIPSE-693
URL: https://jira.codehaus.org/browse/MECLIPSE-693
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : .project, Core : Dependencies resolution and build
path (.classpath), WTP support
Reporter: Robert Scholte
Priority: Minor
Eclipse xml files should all start with
{code:xml}
?xml version=1.0 encoding=UTF-8?
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-693) Some generated xml files are missing their xml-header
[
https://jira.codehaus.org/browse/MECLIPSE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MECLIPSE-693.
---
Resolution: Fixed
Fix Version/s: 2.9
Assignee: Robert Scholte
Fixed in [rev. 1152335|http://svn.apache.org/viewvc?rev=1152335view=rev]
Some generated xml files are missing their xml-header
-
Key: MECLIPSE-693
URL: https://jira.codehaus.org/browse/MECLIPSE-693
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : .project, Core : Dependencies resolution and
build path (.classpath), WTP support
Reporter: Robert Scholte
Assignee: Robert Scholte
Priority: Minor
Fix For: 2.9
Eclipse xml files should all start with
{code:xml}
?xml version=1.0 encoding=UTF-8?
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-597) Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management)
[
https://jira.codehaus.org/browse/MECLIPSE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MECLIPSE-597.
---
Resolution: Fixed
Fix Version/s: 2.9
Assignee: Robert Scholte
Fixed in [rev. 1152339|http://svn.apache.org/viewvc?rev=1152339view=rev]
Thanks!
Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a
different version from that in dependency management)
---
Key: MECLIPSE-597
URL: https://jira.codehaus.org/browse/MECLIPSE-597
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path
(.classpath)
Affects Versions: 2.7
Environment: Nexus 1.3.6, Eclipse 3.4, Windows XP
Reporter: Michal Galet
Assignee: Robert Scholte
Priority: Critical
Fix For: 2.9
Attachments: maven-eclipse-plugin-2.7.patch
When generating eclipse project with mvn eclipse:eclipse
-Declipse.workspace=d:/eclipse-ws the SNAPSHOT dependencies are not resolved
from workspace correctly. See console output below. This is probably caused
by the way how Nexus handles the SNAPSHOTs. The artifact is resolved by
ArtifactResolver and the version is changed from 1.1.0-SNAPSHOT to
1.1.0-20090819.145009-4.
The comparison should be performed against {{artifact.getBaseVersion()}}
instead of {{artifact.getVersion()}}. A simple fix is attached as a patch.
Console output:
[INFO] Artifact com.test:sample:jar:4.0.0.B02-SNAPSHOT already available a
s a workspace project, but with different version. Expected:
4.0.0.B02-20090819.145009-4, found
: 4.0.0.B02-SNAPSHOT
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-466) application.xml generated incorrectly for 3rd party ejb modules
[ https://jira.codehaus.org/browse/MECLIPSE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MECLIPSE-466. --- Resolution: Duplicate Fix Version/s: (was: 2.9) application.xml generated incorrectly for 3rd party ejb modules --- Key: MECLIPSE-466 URL: https://jira.codehaus.org/browse/MECLIPSE-466 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: WTP support Affects Versions: 2.5.1 Reporter: Siarhei Dudzin Attachments: test-project.tar.gz As you may know by default the project version is not added to the project name. In case I have 3rd party ejb modules from a maven repository (jboss seam for example) the version number for those modules is removed from the generated application.xml as well which breaks the WTP deployment: the server can't find the 3rd party ejb jar because it expects the jar also be without the version number. Looks like during generation of application.xml there is no distinction made between dependencies from projects and libraries. I included a test case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-601) Period added to URL prevents proper cloning with Mercurial
Period added to URL prevents proper cloning with Mercurial -- Key: MSITE-601 URL: https://jira.codehaus.org/browse/MSITE-601 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:deploy Affects Versions: 3.0-beta-3 Environment: Javac 7 on Fedora Linux 15, Mercurial 1.9 Reporter: Leon Blakey Priority: Critical I deploy my Maven site over Mercurial on Google Code. I use this configuration distributionManagement !--Site deploy repository-- site idMYPROJECT.googlecode.com/id urlscm:hg:https://code.google.com/p/MYPROJECT.site//url /site /distributionManagement And a standard server in settings.xml servers server idMYPROJECT.googlecode.com/id usernameUSERNAME/username passwordPASSWORD/password /server /servers However when running site:deploy it decides that it should add a dot to the URL, meaning it tries to execute this command EXECUTING: /bin/sh -c cd /tmp hg clone -r tip https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//. /tmp/wagon-scm1348091978.checkout Which on Google and other repositories gives a 404 since the file . (look at the end of the URL) doesn't exist. Why is that period there? Is it coming from Maven Site or the Mercurial plugin (I'm assuming here)? Can it get removed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-627) Parsing URL for clone does not match what is passed in with -DconnectionUrl
Parsing URL for clone does not match what is passed in with -DconnectionUrl --- Key: SCM-627 URL: https://jira.codehaus.org/browse/SCM-627 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.5 Environment: centos5.4 Reporter: Hubert Mercurial server's hostname name is hg. URL to get to clone a repository is: http://hg/hg/maven The SCM plugin seems to treat this URL funny, such that it clones the wrong URL. Original == Turns into http://hg/hg/maven == http://hg//maven Don't even need a valid Mercurial server to reproduce. $ mvn scm:checkout -DconnectionUrl=scm:hg:http://hg/hg/maven [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building myplugin Maven Plugin 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-scm-plugin:1.5:checkout (default-cli) @ myplugin --- [INFO] Removing /sandbox/target/checkout [INFO] Removing /sandbox/target/checkout [INFO] EXECUTING: /bin/sh -c cd /sandbox/target hg clone -r tip http://hg//maven /sandbox/target/checkout [ERROR] EXECUTION FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-627) Parsing URL for clone does not match what is passed in with -DconnectionUrl
[ https://jira.codehaus.org/browse/SCM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hubert updated SCM-627: --- Attachment: SCM-627.patch Patch to fix the issue. It is diffed from tag: maven-scm-1.5 Parsing URL for clone does not match what is passed in with -DconnectionUrl --- Key: SCM-627 URL: https://jira.codehaus.org/browse/SCM-627 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.5 Environment: centos5.4 Reporter: Hubert Attachments: SCM-627.patch Mercurial server's hostname name is hg. URL to get to clone a repository is: http://hg/hg/maven The SCM plugin seems to treat this URL funny, such that it clones the wrong URL. Original == Turns into http://hg/hg/maven == http://hg//maven Don't even need a valid Mercurial server to reproduce. $ mvn scm:checkout -DconnectionUrl=scm:hg:http://hg/hg/maven [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building myplugin Maven Plugin 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-scm-plugin:1.5:checkout (default-cli) @ myplugin --- [INFO] Removing /sandbox/target/checkout [INFO] Removing /sandbox/target/checkout [INFO] EXECUTING: /bin/sh -c cd /sandbox/target hg clone -r tip http://hg//maven /sandbox/target/checkout [ERROR] EXECUTION FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-627) Parsing URL for clone does not match what is passed in with -DconnectionUrl
[ https://jira.codehaus.org/browse/SCM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hubert closed SCM-627. -- Resolution: Duplicate Duplicate of SCM-628, and SCM-628 has the patch attached. Parsing URL for clone does not match what is passed in with -DconnectionUrl --- Key: SCM-627 URL: https://jira.codehaus.org/browse/SCM-627 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.5 Environment: centos5.4 Reporter: Hubert Attachments: SCM-627.patch Mercurial server's hostname name is hg. URL to get to clone a repository is: http://hg/hg/maven The SCM plugin seems to treat this URL funny, such that it clones the wrong URL. Original == Turns into http://hg/hg/maven == http://hg//maven Don't even need a valid Mercurial server to reproduce. $ mvn scm:checkout -DconnectionUrl=scm:hg:http://hg/hg/maven [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building myplugin Maven Plugin 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-scm-plugin:1.5:checkout (default-cli) @ myplugin --- [INFO] Removing /sandbox/target/checkout [INFO] Removing /sandbox/target/checkout [INFO] EXECUTING: /bin/sh -c cd /sandbox/target hg clone -r tip http://hg//maven /sandbox/target/checkout [ERROR] EXECUTION FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-628) scm:checkout parsing URL for clone does not match what is passed in with -DconnectionUrl
scm:checkout parsing URL for clone does not match what is passed in with -DconnectionUrl Key: SCM-628 URL: https://jira.codehaus.org/browse/SCM-628 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-mercurial (hg) Affects Versions: 1.5 Environment: centos5.4 Reporter: Hubert Attachments: SCM-627.patch Mercurial server's hostname name is hg. URL to get to clone a repository is: http://hg/hg/maven The SCM plugin seems to treat this URL funny, such that it clones the wrong URL. Original == Turns into http://hg/hg/maven == http://hg//maven Don't even need a valid Mercurial server to reproduce. $ mvn scm:checkout -DconnectionUrl=scm:hg:http://hg/hg/maven [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building myplugin Maven Plugin 1.0.0-SNAPSHOT [INFO] [INFO] [INFO] maven-scm-plugin:1.5:checkout (default-cli) @ myplugin [INFO] Removing /sandbox/target/checkout [INFO] Removing /sandbox/target/checkout [INFO] EXECUTING: /bin/sh -c cd /sandbox/target hg clone -r tip http://hg//maven /sandbox/target/checkout [ERROR] EXECUTION FAILED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-601) Period added to URL prevents proper cloning with Mercurial
[ https://jira.codehaus.org/browse/MSITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274654#comment-274654 ] Lukas Theussl commented on MSITE-601: - Can you try maven-site-plugin-3.0-SNAPSHOT? Period added to URL prevents proper cloning with Mercurial -- Key: MSITE-601 URL: https://jira.codehaus.org/browse/MSITE-601 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:deploy Affects Versions: 3.0-beta-3 Environment: Javac 7 on Fedora Linux 15, Mercurial 1.9 Reporter: Leon Blakey Priority: Critical I deploy my Maven site over Mercurial on Google Code. I use this configuration distributionManagement !--Site deploy repository-- site idMYPROJECT.googlecode.com/id urlscm:hg:https://code.google.com/p/MYPROJECT.site//url /site /distributionManagement And a standard server in settings.xml servers server idMYPROJECT.googlecode.com/id usernameUSERNAME/username passwordPASSWORD/password /server /servers However when running site:deploy it decides that it should add a dot to the URL, meaning it tries to execute this command EXECUTING: /bin/sh -c cd /tmp hg clone -r tip https://USERNAME:passw...@code.google.com/p/MYPROJECT.site//. /tmp/wagon-scm1348091978.checkout Which on Google and other repositories gives a 404 since the file . (look at the end of the URL) doesn't exist. Why is that period there? Is it coming from Maven Site or the Mercurial plugin (I'm assuming here)? Can it get removed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
