[jira] Commented: (MNG-4732) Version string validation
[ http://jira.codehaus.org/browse/MNG-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229081#action_229081 ] Joerg Schaible commented on MNG-4732: - '+' is missing, it's also not allowed Version string validation - Key: MNG-4732 URL: http://jira.codehaus.org/browse/MNG-4732 Project: Maven 2 3 Issue Type: Improvement Components: POM Affects Versions: 3.0-beta-1 Reporter: Paul Gier Assignee: Benjamin Bentmann Priority: Minor Fix For: 3.0-beta-2 If a / character is accidentally put into a version string it can cause some weird results. Maven installs and deploys some nameless (.jar, -sources.jar, etc) files without an error messages. This can be a bit tricky to track down, so it would be better if Maven did some validation on the version string to prevent the '/' character or other invalid characters. -- 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-4732) Version string validation
[ http://jira.codehaus.org/browse/MNG-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229082#action_229082 ] Benjamin Bentmann commented on MNG-4732: Joerg, can you elaborate why/where + is invalid? Version string validation - Key: MNG-4732 URL: http://jira.codehaus.org/browse/MNG-4732 Project: Maven 2 3 Issue Type: Improvement Components: POM Affects Versions: 3.0-beta-1 Reporter: Paul Gier Assignee: Benjamin Bentmann Priority: Minor Fix For: 3.0-beta-2 If a / character is accidentally put into a version string it can cause some weird results. Maven installs and deploys some nameless (.jar, -sources.jar, etc) files without an error messages. This can be a bit tricky to track down, so it would be better if Maven did some validation on the version string to prevent the '/' character or other invalid characters. -- 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] Closed: (MANTTASKS-189) NPE when using scope=system
[
http://jira.codehaus.org/browse/MANTTASKS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MANTTASKS-189.
---
Resolution: Fixed
Fix Version/s: 2.1.1
Assignee: Herve Boutemy
done in [r965211|http://svn.apache.org/viewvc?view=revisionrevision=965211]
thanks for your feedback
NPE when using scope=system
-
Key: MANTTASKS-189
URL: http://jira.codehaus.org/browse/MANTTASKS-189
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: dependencies task
Affects Versions: 2.1.0
Reporter: SebbASF
Assignee: Herve Boutemy
Fix For: 2.1.1
Using scope=system:
{code:xml}artifact:dependencies
dependency groupId=commons-logging artifactId=commons-logging
version=1.1.1 scope=system/
/artifact:dependencies{code}
causes NPE:
{noformat}java.lang.NullPointerException
at java.io.File.init(File.java:222)
at
org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:445)
at
org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTask.java:186)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:721)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
at org.apache.tools.ant.Main.runBuild(Main.java:801)
at org.apache.tools.ant.Main.startAnt(Main.java:218)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
{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] Commented: (MANTTASKS-191) No explanation of how to use multiple Maven repositories to resolve dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229084#action_229084 ] Herve Boutemy commented on MANTTASKS-191: - bq. There does not seem to be any documentation on how to use multiple repositories when resolving dependencies. [reference documentation|http://maven.apache.org/ant-tasks/reference.html#dependencies] tells The task can include the dependency nested type, in addition to the other shared types localRepository, pom and remoteRepository: how can I make it more explicit? bq. As far as I can tell, central is always searched. True with Maven Ant Tasks 2.1.0: previous versions had a bug in parent pom handling which dropped repository definition. But now that it is fixed, central is always searched as it is defined in [super-pom|http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Super_POM]. I'll fix the documentation bq. Even if I name my repository central it will not override the builtin central, but instead append to it. nice catch. Please create another jira issue, since this is a bug No explanation of how to use multiple Maven repositories to resolve dependencies Key: MANTTASKS-191 URL: http://jira.codehaus.org/browse/MANTTASKS-191 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: documentation Affects Versions: 2.1.0 Reporter: SebbASF There does not seem to be any documentation on how to use multiple repositories when resolving dependencies. -- 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] Closed: (MANTTASKS-163) Support for POM dependency classifier.
[ http://jira.codehaus.org/browse/MANTTASKS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-163. --- Resolution: Cannot Reproduce Assignee: Herve Boutemy it has always been supported AFAIK, since this is code directly taken from Maven Core, without any code duplication in Maven Ant Tasks. Support for POM dependency classifier. -- Key: MANTTASKS-163 URL: http://jira.codehaus.org/browse/MANTTASKS-163 Project: Maven 2.x Ant Tasks Issue Type: New Feature Components: dependencies task Affects Versions: 2.0.10 Environment: 64 bit hardware, Fedora 11, Maven 2.2.1, JDK 1.6 Reporter: Jeremy Whiting Assignee: Herve Boutemy Priority: Minor Please can support for the classifier be provided. -- 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] Closed: (MANTTASKS-192) NPE when using remoteRepository with refid which has not been defined
[
http://jira.codehaus.org/browse/MANTTASKS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MANTTASKS-192.
---
Resolution: Fixed
Fix Version/s: 2.1.1
Assignee: Herve Boutemy
done in [r965226|http://svn.apache.org/viewvc?view=revisionrevision=965226]
thanks for your feedback
NPE when using remoteRepository with refid which has not been defined
-
Key: MANTTASKS-192
URL: http://jira.codehaus.org/browse/MANTTASKS-192
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: dependencies task
Affects Versions: 2.1.0
Reporter: SebbASF
Assignee: Herve Boutemy
Fix For: 2.1.1
{code:xml}artifact:dependencies
remoteRepository refid=not-defined/
dependency groupId=commons-logging artifactId=commons-logging
version=1.1.1/
/artifact:dependencies{code}
causes the following NPE:
{noformat}java.lang.NullPointerException
at
org.apache.maven.artifact.ant.RemoteRepository.getUrl(RemoteRepository.java:43)
at
org.apache.maven.artifact.ant.AbstractArtifactWithRepositoryTask.addConfiguredRemoteRepository(AbstractArtifactWithRepositoryTask.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.IntrospectionHelper$AddNestedCreator.istore(IntrospectionHelper.java:1469)
at
org.apache.tools.ant.IntrospectionHelper$AddNestedCreator.store(IntrospectionHelper.java:1463)
at
org.apache.tools.ant.IntrospectionHelper$Creator.store(IntrospectionHelper.java:1370)
at
org.apache.tools.ant.UnknownElement.handleChild(UnknownElement.java:582)
at
org.apache.tools.ant.UnknownElement.handleChildren(UnknownElement.java:349)
at
org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:201)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
at org.apache.tools.ant.Task.perform(Task.java:347)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
at org.apache.tools.ant.Main.runBuild(Main.java:801)
at org.apache.tools.ant.Main.startAnt(Main.java:218)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
{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] Closed: (MNG-4717) Repository Ids containing : will lead to checksum errors on Windows machines
[
http://jira.codehaus.org/browse/MNG-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4717.
--
Resolution: Fixed
Fix Version/s: 3.0-beta-2
Assignee: Benjamin Bentmann
Emitted validation warning for the illegal characters {{\/:|?*}} in
[r965233|http://svn.apache.org/viewvc?view=revisionrevision=965233].
Repository Ids containing : will lead to checksum errors on Windows machines
--
Key: MNG-4717
URL: http://jira.codehaus.org/browse/MNG-4717
Project: Maven 2 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.2.1
Environment: Windows 7
Reporter: Felix Simmendinger
Assignee: Benjamin Bentmann
Fix For: 3.0-beta-2
If a repositorys id element contains a : character, maven tries to create a
{{repository-metadata-repositoryId.xml}} file under certain circumstances
(in our case when version ranges are used). Under windows this is not
possible and will lead to an error looking like this:
{code}
[WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING
[WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING
[WARNING] repository metadata for: 'artifact XX:XX' could not be retrieved
from repository: YY:YY due to an error: Error copying temporary file to the
final destination: Die Syntax für den Dateinamen, Verzeichnisnamen oder die
Datenträgerbezeichnung ist falsch
{code}
The Problem is in
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata#getLocalFilename.
Better Logging, robustness check or documentation of this issue would be
helpfull.
--
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] Closed: (MANTTASKS-182) deploy task tries to upload things it shouldn't.
[ http://jira.codehaus.org/browse/MANTTASKS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-182. --- Resolution: Duplicate seems like a duplicate of MANTTASKS-170 deploy task tries to upload things it shouldn't. Key: MANTTASKS-182 URL: http://jira.codehaus.org/browse/MANTTASKS-182 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: deploy task Affects Versions: 2.1.0 Reporter: Aaron Kaplan When I run the deploy ant task, deploying to a nexus repository via http, the first thing it does is try to upload org/apache/maven/super-pom/2.0/super-pom-2.0.jar . This fails with a 400 error code because the file exists in the repository already. I posted this problem to maven-users but received no replies. http://mail-archives.apache.org/mod_mbox/maven-users/201004.mbox/%3c4bb60bca.5070...@aaronkaplan.info%3e -- 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] Closed: (MANTTASKS-191) No explanation of how to use multiple Maven repositories to resolve dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-191. --- Resolution: Fixed Fix Version/s: 2.1.1 Assignee: Herve Boutemy documentation about central repository fixed in [r965247|http://svn.apache.org/viewvc?view=revisionrevision=965247] for multiple remote repositories usage, it's already written just a few lines before: bq. All of the tasks can optionally take *one or more* remote repositories to download from and upload to, and a local repository to store downloaded and installed archives to. No explanation of how to use multiple Maven repositories to resolve dependencies Key: MANTTASKS-191 URL: http://jira.codehaus.org/browse/MANTTASKS-191 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: documentation Affects Versions: 2.1.0 Reporter: SebbASF Assignee: Herve Boutemy Fix For: 2.1.1 There does not seem to be any documentation on how to use multiple repositories when resolving dependencies. -- 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: (MANTTASKS-191) No explanation of how to use multiple Maven repositories to resolve dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229094#action_229094 ] Knut Forkalsrud commented on MANTTASKS-191: --- I filed MANTTASKS-195 for the override problem. No explanation of how to use multiple Maven repositories to resolve dependencies Key: MANTTASKS-191 URL: http://jira.codehaus.org/browse/MANTTASKS-191 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: documentation Affects Versions: 2.1.0 Reporter: SebbASF Assignee: Herve Boutemy Fix For: 2.1.1 There does not seem to be any documentation on how to use multiple repositories when resolving dependencies. -- 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: (MANTTASKS-195) Cannot override central repository with my own
Cannot override central repository with my own
--
Key: MANTTASKS-195
URL: http://jira.codehaus.org/browse/MANTTASKS-195
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: dependencies task
Affects Versions: 2.1.0
Reporter: Knut Forkalsrud
Even if I name my repository central it will not override the builtin
central, but instead append to it.
Here's my sample ant task (using maven-ant-tasks 2.1.0)
{code:xml}
target name=init
artifact:dependencies pathId=dependency.classpath
filesetId=dependency.fileset
remoteRepository id=central
url=http://mycompany.net/nexus/content/repo/
dependency groupId=foo artifactId=bar version=3.8.2/
/artifact:dependencies
/target
{code}
A few lines of output from ant -v compile:
{noformat}
[artifact:dependencies] Using remote repositories:
* id=central, url=http://mycompany.net/nexus/content/repo, releases=enabled,
snapshots=enabled
* id=central, url=http://repo1.maven.org/maven2, releases=enabled,
snapshots=disabled
org.apache.maven:super-pom:jar:2.0 (selected)
{noformat}
This was also mentioned in MANTTASKS-191, which was primarily about
documentation.
--
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-4734) Maven pom resolving does not respect a 301 permanent redirect
Maven pom resolving does not respect a 301 permanent redirect
-
Key: MNG-4734
URL: http://jira.codehaus.org/browse/MNG-4734
Project: Maven 2 3
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.2.1
Reporter: Graham Leggett
When an attempt is made to depend upon the following dependency:
com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.pom
Instead of downloading the pom, a 301 Moved Permanently is saved in it's place.
This breaks all maven builds on the particular machine:
{code}
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title301 Moved Permanently/title
/headbody
h1Moved Permanently/h1
pThe document has moved a
href=http://download.java.net/maven/1/com.sun.tools.xjc.maven2/poms/maven-jaxb-plugin-1.1.pom;here/a./p
hr
addressApache Server at maven-repository.dev.java.net Port 443/address
/body/html
{code}
This looks like a regression since v2.2.0, as another machine running v2.2.0
downloads the pom for the above artifact correctly.
This is what it looks like when it breaks:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: com.sun.tools.xjc.maven2:maven-jaxb-plugin
POM Location:
/home/chandler/minfrin/.m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.pom
Reason: Not a v4.0.0 POM. for project
com.sun.tools.xjc.maven2:maven-jaxb-plugin at
/home/chandler/minfrin/.m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.pom
--
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] Closed: (MNG-4734) Maven pom resolving does not respect a 301 permanent redirect
[
http://jira.codehaus.org/browse/MNG-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4734.
--
Resolution: Duplicate
Assignee: Benjamin Bentmann
Maven pom resolving does not respect a 301 permanent redirect
-
Key: MNG-4734
URL: http://jira.codehaus.org/browse/MNG-4734
Project: Maven 2 3
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.2.1
Reporter: Graham Leggett
Assignee: Benjamin Bentmann
When an attempt is made to depend upon the following dependency:
com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.pom
Instead of downloading the pom, a 301 Moved Permanently is saved in it's
place. This breaks all maven builds on the particular machine:
{code}
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title301 Moved Permanently/title
/headbody
h1Moved Permanently/h1
pThe document has moved a
href=http://download.java.net/maven/1/com.sun.tools.xjc.maven2/poms/maven-jaxb-plugin-1.1.pom;here/a./p
hr
addressApache Server at maven-repository.dev.java.net Port 443/address
/body/html
{code}
This looks like a regression since v2.2.0, as another machine running v2.2.0
downloads the pom for the above artifact correctly.
This is what it looks like when it breaks:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: com.sun.tools.xjc.maven2:maven-jaxb-plugin
POM Location:
/home/chandler/minfrin/.m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.pom
Reason: Not a v4.0.0 POM. for project
com.sun.tools.xjc.maven2:maven-jaxb-plugin at
/home/chandler/minfrin/.m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.pom
--
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-4428) Permament move (error 301) not handled properly by Maven
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229097#action_229097 ] Graham Leggett commented on MNG-4428: - This is a major regression that completely sinks all maven versions newer than v2.2.0, a patch has been available since March, but the patch has been ignored, this bug is unassigned and is marked as minor. Is this on the radar for anyone to fix, or has it fallen through the cracks? Permament move (error 301) not handled properly by Maven Key: MNG-4428 URL: http://jira.codehaus.org/browse/MNG-4428 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.2.1 Reporter: Grzegorz Slowikowski Priority: Minor Attachments: mng-4428.patch Artifact cannot be downloaded by http-lightweight-wagon used (as default) in all Maven versions except 2.2.0, which uses http-wagon by default. Instead of pom and jar files html files appear in the local repo with content like: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://download.java.net/maven/2/org/codehaus/castor/castor-xml-schema/1.2/castor-xml-schema-1.2.pom;here/a./p hr addressApache Server at maven2-repository.dev.java.net Port 443/address /body/html Only Maven 2.2.0 handles 301 properly. By the way, I haven't expected such Apache configuration (permament move) in central Maven repo. As you can see this is not handled properly by almost all versions of Maven. -- 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] Closed: (SCM-562) Don't overwrite SVN auth cache
[
http://jira.codehaus.org/browse/SCM-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed SCM-562.
Resolution: Fixed
fix [rev 965281|http://svn.apache.org/viewvc?rev=965281view=rev]
Thanks !
Don't overwrite SVN auth cache
--
Key: SCM-562
URL: http://jira.codehaus.org/browse/SCM-562
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-provider-svn
Affects Versions: 1.3
Reporter: Carlos Sanchez
Assignee: Olivier Lamy
Fix For: 1.4
From MRELEASE-497. Patch attached to that issue
{quote}
When release-plugin commit to SVN, it overwrites the auth cache with
username/password defined in the pom.xml.
I want to use a separate username `maven' for maven-related commits, and
personal username `lenik' for personal development commits, when I start to
using maven release plugin, it always overwrite the auth cache with user
`maven' , and I must do a Tortoise/Settings/Saved Data/Clear auth cache
before commit my personal changes.
A recommend solution:
add an option --no-auth-cache to svn commit command line will resolve this
problem. with option --no-auth-cache, the existing auth cache is left
unchanged after commited.
if there is an auth-cache option in pom.xml, say
auth-cachefalse/auth-cache under scm element, it should be false be
default.
{quote}
--
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: (MRELEASE-497) Don't overwrite SVN auth cache
[ http://jira.codehaus.org/browse/MRELEASE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-497: -- Fix Version/s: 2.1 Assignee: Olivier Lamy Don't overwrite SVN auth cache -- Key: MRELEASE-497 URL: http://jira.codehaus.org/browse/MRELEASE-497 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: perform, prepare, scm Environment: Windows XP, JDK 1.7, SVN 1.6.5 Reporter: Lenik Assignee: Olivier Lamy Priority: Critical Fix For: 2.1 Attachments: no-auth-cache.patch When release-plugin commit to SVN, it overwrites the auth cache with username/password defined in the pom.xml. I want to use a separate username `maven' for maven-related commits, and personal username `lenik' for personal development commits, when I start to using maven release plugin, it always overwrite the auth cache with user `maven' , and I must do a Tortoise/Settings/Saved Data/Clear auth cache before commit my personal changes. A recommend solution: add an option --no-auth-cache to svn commit command line will resolve this problem. with option --no-auth-cache, the existing auth cache is left unchanged after commited. if there is an auth-cache option in pom.xml, say auth-cachefalse/auth-cache under scm element, it should be false be default. -- 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] Closed: (MRELEASE-497) Don't overwrite SVN auth cache
[ http://jira.codehaus.org/browse/MRELEASE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-497. - Resolution: Fixed fixed with SCM-562 Don't overwrite SVN auth cache -- Key: MRELEASE-497 URL: http://jira.codehaus.org/browse/MRELEASE-497 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: perform, prepare, scm Environment: Windows XP, JDK 1.7, SVN 1.6.5 Reporter: Lenik Assignee: Olivier Lamy Priority: Critical Fix For: 2.1 Attachments: no-auth-cache.patch When release-plugin commit to SVN, it overwrites the auth cache with username/password defined in the pom.xml. I want to use a separate username `maven' for maven-related commits, and personal username `lenik' for personal development commits, when I start to using maven release plugin, it always overwrite the auth cache with user `maven' , and I must do a Tortoise/Settings/Saved Data/Clear auth cache before commit my personal changes. A recommend solution: add an option --no-auth-cache to svn commit command line will resolve this problem. with option --no-auth-cache, the existing auth cache is left unchanged after commited. if there is an auth-cache option in pom.xml, say auth-cachefalse/auth-cache under scm element, it should be false be default. -- 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: (MANTTASKS-183) Property not evaluated in pom/project/parent/version
[
http://jira.codehaus.org/browse/MANTTASKS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229105#action_229105
]
Marcin Wisnicki commented on MANTTASKS-183:
---
Unfortunately nothing changed (with today trunk).
I have noticed however that it is only writepom/ that even attempts any kind
of interpolation. Referencing existing pom file with pom/ and then doing
install/ results in exact copy of pom being installed (no interpolation).
Strangely, I cannot find anything about interpolation of pom variables in
manttask documentation.
I will try to attach simple test case tomorrow.
Property not evaluated in pom/project/parent/version
Key: MANTTASKS-183
URL: http://jira.codehaus.org/browse/MANTTASKS-183
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: pom task
Affects Versions: 2.1.0
Environment: Ant 1.7.1
Reporter: Marcin Wisnicki
I'm trying to define parent version in pom by property:
{code:xml|title=hamcrest-integration.pom}
project xmlns=http://maven.apache.org/POM/4.0.0;
modelVersion4.0.0/modelVersion
parent
groupIdorg.hamcrest/groupId
artifactIdhamcrest-parent/artifactId
version${hamcrest.version}/version
/parent
groupIdorg.hamcrest/groupId
artifactIdhamcrest-integration/artifactId
version${hamcrest.version}/version
/project
{code}
And using something like following in build.xml:
{code:xml|title=build.xml}
property name=hamcrest.version value=1.2/
artifact:pom id=generator.pom file=poms/hamcrest-generator.pom/
{code}
Unfortunately generated pom (via writepom/install/deploy) has
{{project.version}} resolved, but {{project.parent.version}} remains
unresolved.
--
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
