[jira] Commented: (MNG-4301) Invalid checksums on deploy when using webdav without extension
[ http://jira.codehaus.org/browse/MNG-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=215125#action_215125 ] Stephen Pack commented on MNG-4301: --- @gesha: replace the /all in deckrider's snippet with /put. This workaround works for me using Maven 2.2.1 (note that if you deploy a snapshot that already exists -- or anyone on your team doesn't implement the workaround as well -- you may get the error, since the artifact being replaced has the issue). Invalid checksums on deploy when using webdav without extension --- Key: MNG-4301 URL: http://jira.codehaus.org/browse/MNG-4301 Project: Maven 2 3 Issue Type: Bug Components: Deployment Affects Versions: 2.2.1 Environment: n/a Reporter: Kevin Shekleton Priority: Blocker With maven 2.2.1, our deployments via webdav are producing invalid checksums, similar to the issue reported in MNG-4235. From maven 2.0.8 and previous, the following build extension was required to deploy via webdav: extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions Starting with maven 2.0.9 (see MNG-3418), webdav was included by default and the aforementioned build extension must be removed from the project. If it was included in the project the deployment would fail as Maven would report multiple versions of wagon-webdav present. With maven 2.2.0, our deployment suffered from invalid checksums reported in MNG-4235. With maven 2.2.1, we still see the invalid checksums on deployment as reported in MNG-4235. However, I've found that if you add the above build extension into the project, we don't experience this issue (of generating invalid checksums). Is this workaround an intentional change brought about by the fix of MNG-4235? -- 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-4301) Invalid checksums on deploy when using webdav without extension
[ http://jira.codehaus.org/browse/MNG-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=195024#action_195024 ] Stephen Pack commented on MNG-4301: --- I believe the previous comment is the workaround for maven 2.2.0; for maven 2.2.1, you need to add wagonProviderhttpclient/wagonProvider in the configuration. Without that addition, I got the exception Cannot find setter nor field in org.apache.maven.wagon.providers.http.LightweightHttpWagon for 'httpConfiguration' Invalid checksums on deploy when using webdav without extension --- Key: MNG-4301 URL: http://jira.codehaus.org/browse/MNG-4301 Project: Maven 2 Issue Type: Bug Components: Deployment Affects Versions: 2.2.1 Environment: n/a Reporter: Kevin Shekleton Priority: Blocker With maven 2.2.1, our deployments via webdav are producing invalid checksums, similar to the issue reported in MNG-4235. From maven 2.0.8 and previous, the following build extension was required to deploy via webdav: extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions Starting with maven 2.0.9 (see MNG-3418), webdav was included by default and the aforementioned build extension must be removed from the project. If it was included in the project the deployment would fail as Maven would report multiple versions of wagon-webdav present. With maven 2.2.0, our deployment suffered from invalid checksums reported in MNG-4235. With maven 2.2.1, we still see the invalid checksums on deployment as reported in MNG-4235. However, I've found that if you add the above build extension into the project, we don't experience this issue (of generating invalid checksums). Is this workaround an intentional change brought about by the fix of MNG-4235? -- 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-4294) File ownership on tarball is set
File ownership on tarball is set Key: MNG-4294 URL: http://jira.codehaus.org/browse/MNG-4294 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.2.1 Reporter: Stephen Pack Priority: Minor File ownership was set on the 2.2.1 tarball. When untarring as root with default flags, this results in file ownership assigned unexpectedly. Tarballs for other versions have ownership of 0:0. [r...@ipvmds01 share]# tar -tvf apache-maven-2.2.1-bin.tar.gz -rw-r--r-- jdcasey/jdcasey 37854 2009-07-21 17:14:15 apache-maven-2.2.1/boot/classworlds-1.1.jar -rw-r--r-- 501/501 12933 2009-08-06 14:11:25 apache-maven-2.2.1/LICENSE.txt -rw-r--r-- 501/501 923 2009-08-06 14:11:25 apache-maven-2.2.1/NOTICE.txt -rw-r--r-- 501/501 2532 2009-08-06 14:11:25 apache-maven-2.2.1/README.txt -rw-r--r-- jdcasey/jdcasey 158 2009-08-06 14:18:08 apache-maven-2.2.1/bin/m2.conf -rw-r--r-- jdcasey/jdcasey 5915 2009-08-06 14:18:08 apache-maven-2.2.1/bin/mvn.bat -rw-r--r-- jdcasey/jdcasey 6100 2009-08-06 14:18:08 apache-maven-2.2.1/bin/mvnDebug.bat -rwxr-xr-x jdcasey/jdcasey 4562 2009-08-06 14:18:08 apache-maven-2.2.1/bin/mvn -rwxr-xr-x jdcasey/jdcasey 4743 2009-08-06 14:18:08 apache-maven-2.2.1/bin/mvnDebug drwxrwxrwx 501/501 0 2009-08-06 14:11:25 apache-maven-2.2.1/conf/ -rwxrwxrwx 501/501 10205 2009-08-06 14:11:25 apache-maven-2.2.1/conf/settings.xml -rwxrwxrwx 501/501 3151139 2009-08-06 14:18:06 apache-maven-2.2.1/lib/maven-2.2.1-uber.jar [r...@ipvmds01 share]# tar -tvf apache-maven-2.1.0-bin.tar.gz drwxr-xr-x 0/0 0 2009-03-18 14:04:52 apache-maven-2.1.0/conf/ -rw-r--r-- 0/0 37854 2009-03-18 11:01:38 apache-maven-2.1.0/boot/classworlds-1.1.jar -rw-r--r-- 0/0 11358 2009-03-18 14:04:52 apache-maven-2.1.0/LICENSE.txt -rw-r--r-- 0/0 609 2009-03-18 14:04:52 apache-maven-2.1.0/NOTICE.txt -rw-r--r-- 0/02532 2009-03-18 14:04:52 apache-maven-2.1.0/README.txt -rw-r--r-- 0/0 145 2009-03-18 14:11:57 apache-maven-2.1.0/bin/m2.conf -rw-r--r-- 0/05915 2009-03-18 14:11:57 apache-maven-2.1.0/bin/mvn.bat -rw-r--r-- 0/06100 2009-03-18 14:11:57 apache-maven-2.1.0/bin/mvnDebug.bat -rwxr-xr-x 0/04562 2009-03-18 14:11:57 apache-maven-2.1.0/bin/mvn -rwxr-xr-x 0/04743 2009-03-18 14:11:57 apache-maven-2.1.0/bin/mvnDebug -rw-r--r-- 0/0 10224 2009-03-18 14:04:52 apache-maven-2.1.0/conf/settings.xml -rw-r--r-- 0/0 3230334 2009-03-18 14:11:56 apache-maven-2.1.0/lib/maven-2.1.0-uber.jar [r...@ipvmds01 share]# tar -tvf apache-maven-2.0.10-bin.tar.gz drwxr-xr-x 0/0 0 2009-02-09 20:52:16 apache-maven-2.0.10/conf/ -rw-r--r-- 0/0 11560 2009-02-09 20:52:16 apache-maven-2.0.10/LICENSE.txt -rw-r--r-- 0/0 620 2009-02-09 20:52:16 apache-maven-2.0.10/NOTICE.txt -rw-r--r-- 0/02610 2009-02-09 20:52:16 apache-maven-2.0.10/README.txt -rw-r--r-- 0/01124 2009-02-09 20:52:16 apache-maven-2.0.10/bin/m2.bat -rw-r--r-- 0/0 145 2009-02-09 20:52:16 apache-maven-2.0.10/bin/m2.conf -rw-r--r-- 0/05899 2009-02-09 20:52:16 apache-maven-2.0.10/bin/mvn.bat -rw-r--r-- 0/06082 2009-02-09 20:52:16 apache-maven-2.0.10/bin/mvnDebug.bat -rwxr-xr-x 0/01092 2009-02-09 20:52:16 apache-maven-2.0.10/bin/m2 -rwxr-xr-x 0/04562 2009-02-09 20:52:16 apache-maven-2.0.10/bin/mvn -rwxr-xr-x 0/04735 2009-02-09 20:52:16 apache-maven-2.0.10/bin/mvnDebug -rw-r--r-- 0/09948 2009-02-09 20:52:16 apache-maven-2.0.10/conf/settings.xml -rw-r--r-- 0/0 2300936 2009-02-09 20:57:51 apache-maven-2.0.10/lib/maven-2.0.10-uber.jar -rw-r--r-- 0/0 37854 2009-02-09 20:19:22 apache-maven-2.0.10/boot/classworlds-1.1.jar -- 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-2873) Unable to find transitive dependencies when they have been relocated.
[ http://jira.codehaus.org/browse/MNG-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=146303#action_146303 ] Stephen Pack commented on MNG-2873: --- Thanks Luke! I verified with my initial, more complex use case that RC11 solves this issue. Unable to find transitive dependencies when they have been relocated. - Key: MNG-2873 URL: http://jira.codehaus.org/browse/MNG-2873 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5 Reporter: Micah Whitacre Fix For: 2.0.11 Attachments: MNG2873.ZIP I have two projects A and B. Project A is dependent on B. Project B has compile time on project C which is deployed to a repository, repository1. The newest version, 2.0, of project C has since been relocated from oldGroupId to newGroupId. The relocation POMs are working correctly and Project B is able to be built successfully. Project A is not dependent on anything from repository1 it does not list that repository in its own repositories/ section. When building project A, it tries to resolve the dependencies of B which includes C. However I am currently getting errors when it tries to resolve the C. Below is an example of this error occurring. As you can see the list of remote repositories does not display repository1 as one of the repositories that was checked despite the fact that Project B listed it in its POM. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [1,) oldGroupId:projectC:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2), repo2 (http://repo.some-repo.com/repo) If I change project B to not use a range but to instead depend on a non-relocated version of project C everything works fine and I do not get this issue at all. The other and more correct solution to this issue is to update project B to use the new groupIds however it forces me to release project B immediately since all older released versions of B are broken by using the old groupIds an this issue. -- 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] Issue Comment Edited: (MNG-2873) Unable to find transitive dependencies when they have been relocated.
[ http://jira.codehaus.org/browse/MNG-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=146230#action_146230 ] stephenjpack edited comment on MNG-2873 at 8/28/08 9:12 AM: These projects demonstrate the issue. I'm using maven 2.0.9. It contains 3 projects -- zebra, monkey, and giraffe -- and uses 2 repositories -- zoo and wild. *Deploy zebra (to zoo) *Move zebra to a new groupId within zoo deploy relocation POM *Delete zebra from local repo *Deploy monkey (to wild) *Verify giraffe, which depends on monkey -- zebra isn't resolved. The problem appears to be the relocation POM for zebra in zoo isn't even being read. [DEBUG] animals:giraffe:jar:1.0 (selected for null) [DEBUG] animals:monkey:jar:1.0:compile (selected for compile) [DEBUG] animals:zebra:jar:1.0:compile (selected for compile) [DEBUG] Trying repository wild-repo Downloading: file://c:/test/repo2/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository wild-repo (file://c:/test/repo2) [DEBUG] Trying repository zoo-repo Downloading: file://c:/test/repo/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository zoo-repo (file://c:/test/repo) [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository central (http://repo1.maven.org/maven2) [DEBUG] Unable to download the artifact from any repository was (Author: stephenjpack): These projects demonstrate the issue. I'm using maven 2.0.9. It contains 3 projects -- zebra, monkey, and giraffe -- and uses 2 repositories -- zoo and wild. *Deploy zebra (to zoo) *Move zebra to a new groupId within zoo deploy relocation POM *Delete zebra from local repo *Deploy monkey (to wild) *Verify giraffe, which depends on monkey -- zebra isn't resolved, as only the wild repo is queried (see debug output below). The problem appears to be the relocation POM for zebra in zoo isn't even being read. [DEBUG] animals:giraffe:jar:1.0 (selected for null) [DEBUG] animals:monkey:jar:1.0:compile (selected for compile) [DEBUG] animals:zebra:jar:1.0:compile (selected for compile) [DEBUG] Trying repository wild-repo Downloading: file://c:/test/repo2/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository wild-repo (file://c:/test/repo2) [DEBUG] Trying repository zoo-repo Downloading: file://c:/test/repo/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository zoo-repo (file://c:/test/repo) [DEBUG] Trying repository central Downloading: http://repo.cerner.corp/nexus/content/repositories/central/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository central (http://repo1.maven.org/maven2) [DEBUG] Unable to download the artifact from any repository Unable to find transitive dependencies when they have been relocated. - Key: MNG-2873 URL: http://jira.codehaus.org/browse/MNG-2873 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5 Reporter: Micah Whitacre Fix For: 2.0.11 Attachments: MNG2873.ZIP I have two projects A and B. Project A is dependent on B. Project B has compile time on project C which is deployed to a repository, repository1. The newest version, 2.0, of project C has since been relocated from oldGroupId to newGroupId. The relocation POMs are working correctly and Project B is able to be built successfully. Project A is not dependent on anything from repository1 it does not list that repository in its own repositories/ section. When building project A, it tries to resolve the dependencies of B which includes C. However I am currently getting errors when it tries to resolve the C. Below is an example of this error occurring. As you can see the list of remote repositories does not display repository1 as one of the repositories that was checked despite the fact that Project B listed it in its POM. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [1,) oldGroupId:projectC:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2), repo2 (http://repo.some-repo.com/repo) If I change project B to not use a range but to instead depend on a non-relocated version of project C everything works fine and
[jira] Updated: (MNG-2873) Unable to find transitive dependencies when they have been relocated.
[ http://jira.codehaus.org/browse/MNG-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Pack updated MNG-2873: -- Attachment: MNG2873.ZIP These projects demonstrate the issue. I'm using maven 2.0.9. It contains 3 projects -- zebra, monkey, and giraffe -- and uses 2 repositories -- zoo and wild. *Deploy zebra (to zoo) *Move zebra to a new groupId within zoo deploy relocation POM *Delete zebra from local repo *Deploy monkey (to wild) *Verify giraffe, which depends on monkey -- zebra isn't resolved, as only the wild repo is queried (see output below) Missing: -- 1) animals:zebra:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=animals -DartifactId=zebra -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=animals -DartifactId=zebra -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) animals:giraffe:jar:1.0 2) animals:monkey:jar:1.0 3) animals:zebra:jar:1.0 -- 1 required artifact is missing. for artifact: animals:giraffe:jar:1.0 from the specified remote repositories: wild-repo (file://c:/test/repo2), central (http://repo1.maven.org/maven2) Unable to find transitive dependencies when they have been relocated. - Key: MNG-2873 URL: http://jira.codehaus.org/browse/MNG-2873 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5 Reporter: Micah Whitacre Fix For: 2.0.11 Attachments: MNG2873.ZIP I have two projects A and B. Project A is dependent on B. Project B has compile time on project C which is deployed to a repository, repository1. The newest version, 2.0, of project C has since been relocated from oldGroupId to newGroupId. The relocation POMs are working correctly and Project B is able to be built successfully. Project A is not dependent on anything from repository1 it does not list that repository in its own repositories/ section. When building project A, it tries to resolve the dependencies of B which includes C. However I am currently getting errors when it tries to resolve the C. Below is an example of this error occurring. As you can see the list of remote repositories does not display repository1 as one of the repositories that was checked despite the fact that Project B listed it in its POM. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [1,) oldGroupId:projectC:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2), repo2 (http://repo.some-repo.com/repo) If I change project B to not use a range but to instead depend on a non-relocated version of project C everything works fine and I do not get this issue at all. The other and more correct solution to this issue is to update project B to use the new groupIds however it forces me to release project B immediately since all older released versions of B are broken by using the old groupIds an this issue. -- 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] Issue Comment Edited: (MNG-2873) Unable to find transitive dependencies when they have been relocated.
[ http://jira.codehaus.org/browse/MNG-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=146230#action_146230 ] stephenjpack edited comment on MNG-2873 at 8/27/08 5:38 PM: These projects demonstrate the issue. I'm using maven 2.0.9. It contains 3 projects -- zebra, monkey, and giraffe -- and uses 2 repositories -- zoo and wild. *Deploy zebra (to zoo) *Move zebra to a new groupId within zoo deploy relocation POM *Delete zebra from local repo *Deploy monkey (to wild) *Verify giraffe, which depends on monkey -- zebra isn't resolved, as only the wild repo is queried (see debug output below). The problem appears to be the relocation POM for zebra in zoo isn't even being read. [DEBUG] animals:giraffe:jar:1.0 (selected for null) [DEBUG] animals:monkey:jar:1.0:compile (selected for compile) [DEBUG] animals:zebra:jar:1.0:compile (selected for compile) [DEBUG] Trying repository wild-repo Downloading: file://c:/test/repo2/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository wild-repo (file://c:/test/repo2) [DEBUG] Trying repository zoo-repo Downloading: file://c:/test/repo/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository zoo-repo (file://c:/test/repo) [DEBUG] Trying repository central Downloading: http://repo.cerner.corp/nexus/content/repositories/central/animals/zebra/1.0/zebra-1.0.jar [DEBUG] Unable to get resource 'animals:zebra:jar:1.0' from repository central (http://repo1.maven.org/maven2) [DEBUG] Unable to download the artifact from any repository was (Author: stephenjpack): These projects demonstrate the issue. I'm using maven 2.0.9. It contains 3 projects -- zebra, monkey, and giraffe -- and uses 2 repositories -- zoo and wild. *Deploy zebra (to zoo) *Move zebra to a new groupId within zoo deploy relocation POM *Delete zebra from local repo *Deploy monkey (to wild) *Verify giraffe, which depends on monkey -- zebra isn't resolved, as only the wild repo is queried (see output below) Missing: -- 1) animals:zebra:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=animals -DartifactId=zebra -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=animals -DartifactId=zebra -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) animals:giraffe:jar:1.0 2) animals:monkey:jar:1.0 3) animals:zebra:jar:1.0 -- 1 required artifact is missing. for artifact: animals:giraffe:jar:1.0 from the specified remote repositories: wild-repo (file://c:/test/repo2), central (http://repo1.maven.org/maven2) Unable to find transitive dependencies when they have been relocated. - Key: MNG-2873 URL: http://jira.codehaus.org/browse/MNG-2873 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5 Reporter: Micah Whitacre Fix For: 2.0.11 Attachments: MNG2873.ZIP I have two projects A and B. Project A is dependent on B. Project B has compile time on project C which is deployed to a repository, repository1. The newest version, 2.0, of project C has since been relocated from oldGroupId to newGroupId. The relocation POMs are working correctly and Project B is able to be built successfully. Project A is not dependent on anything from repository1 it does not list that repository in its own repositories/ section. When building project A, it tries to resolve the dependencies of B which includes C. However I am currently getting errors when it tries to resolve the C. Below is an example of this error occurring. As you can see the list of remote repositories does not display repository1 as one of the repositories that was checked despite the fact that Project B listed it in its POM. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [1,) oldGroupId:projectC:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2), repo2 (http://repo.some-repo.com/repo) If I change project B to not use a range but to instead depend on a non-relocated version of project C everything works fine and I do not get this issue at all. The other and more correct solution to
[jira] Created: (MEV-532) JUnit maven-metadata.xml doesn't include 4.3 and 4.3.1 versions
JUnit maven-metadata.xml doesn't include 4.3 and 4.3.1 versions --- Key: MEV-532 URL: http://jira.codehaus.org/browse/MEV-532 Project: Maven Evangelism Issue Type: Task Reporter: Stephen Pack Assignee: Carlos Sanchez The maven-metadata.xml at [1] doesn't include the 3.8.2 version that's out there. Can this please be updated? Thanks. [1] http://www.ibiblio.org/maven2/junit/junit/maven-metadata.xml -- 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: (MEV-532) JUnit maven-metadata.xml doesn't include 4.3 and 4.3.1 versions
[ http://jira.codehaus.org/browse/MEV-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Pack closed MEV-532. Resolution: Duplicate accidental clone JUnit maven-metadata.xml doesn't include 4.3 and 4.3.1 versions --- Key: MEV-532 URL: http://jira.codehaus.org/browse/MEV-532 Project: Maven Evangelism Issue Type: Task Reporter: Stephen Pack Assignee: Carlos Sanchez The maven-metadata.xml at [1] doesn't include the 3.8.2 version that's out there. Can this please be updated? Thanks. [1] http://www.ibiblio.org/maven2/junit/junit/maven-metadata.xml -- 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: (MEV-533) JUnit maven-metadata.xml doesn't include 4.3 versions
JUnit maven-metadata.xml doesn't include 4.3 versions - Key: MEV-533 URL: http://jira.codehaus.org/browse/MEV-533 Project: Maven Evangelism Issue Type: Bug Components: Invalid Metadata Reporter: Stephen Pack The maven-metadata.xml [1] doesn't include the 4.3 and 4.3.1 versions that are out there. Can this please be updated? Thanks. [1] http://repo1.maven.org/maven2/junit/junit/maven-metadata.xml -- 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
