[jira] Updated: (MRM-767) generated LICENSE and NOTICE files need improvement
[ http://jira.codehaus.org/browse/MRM-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-767: - Priority: Blocker (was: Major) Fix Version/s: 1.1 generated LICENSE and NOTICE files need improvement --- Key: MRM-767 URL: http://jira.codehaus.org/browse/MRM-767 Project: Archiva Issue Type: Bug Components: build Affects Versions: 1.0.1 Reporter: Brett Porter Priority: Blocker Fix For: 1.1 the NOTICE file includes incorrect information under the unknown section, as well as listing many components that are not necessary since they all come from Apache. the LICENSE file currently omits the BSD license from the Java Service Wrapper 3.2.3 -- 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: (MRM-767) generated LICENSE and NOTICE files need improvement
generated LICENSE and NOTICE files need improvement --- Key: MRM-767 URL: http://jira.codehaus.org/browse/MRM-767 Project: Archiva Issue Type: Bug Components: build Affects Versions: 1.0.1 Reporter: Brett Porter Fix For: 1.1 the NOTICE file includes incorrect information under the unknown section, as well as listing many components that are not necessary since they all come from Apache. the LICENSE file currently omits the BSD license from the Java Service Wrapper 3.2.3 -- 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: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129969#action_129969 ] Brett Porter commented on MRM-659: -- if you have the proxied repository in legacy mode, but the managed repository in maven2 mode, then the problem will not occur - is that an option for you? archiva cannot serve ejb artifacts from a maven1 repository --- Key: MRM-659 URL: http://jira.codehaus.org/browse/MRM-659 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0 Reporter: nicolas de loof Assignee: Brett Porter Fix For: 1.0.2 requesting an ejb from a maven1 repository builds the path groupId/jars/artifactId.jar, and not the location where maven1 ejb:deploy places the ejb jars (groupId/ejbs/artifactId.jar). The type folder is created based on the file extension, with some exceptions. It should be created based on the artifact type. -- 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: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129972#action_129972 ] Brett Porter commented on MRM-659: -- you're right, sorry. The managed repository can be set to either, but to pass an ejb request to the legacy remote repository requires the incoming request to be in legacy format. This is because of the erasure of information in the Maven 2 repository format. archiva cannot serve ejb artifacts from a maven1 repository --- Key: MRM-659 URL: http://jira.codehaus.org/browse/MRM-659 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0 Reporter: nicolas de loof Assignee: Brett Porter Fix For: 1.0.2 requesting an ejb from a maven1 repository builds the path groupId/jars/artifactId.jar, and not the location where maven1 ejb:deploy places the ejb jars (groupId/ejbs/artifactId.jar). The type folder is created based on the file extension, with some exceptions. It should be created based on the artifact type. -- 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: (MRM-243) 507 Insufficient Storage when deploying artifact with webdav
[ http://jira.codehaus.org/browse/MRM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129985#action_129985 ] Andrew Heald commented on MRM-243: -- This issue is not fixed in Archiva 1.0.1 and pops up at least once a day on our most complex integration build, though never for out other builds. Client side environment here: Maven 2.0.8 and we're using wagon-webdav 1.0-beta-2. I replaced plexus-urils 1.4 with 1.5.1 in Archiva but that hasn't fixed the problem. Please reopen this issue, or shall I create a clone? 507 Insufficient Storage when deploying artifact with webdav Key: MRM-243 URL: http://jira.codehaus.org/browse/MRM-243 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-alpha-1, 1.0-alpha-2, 1.0-beta-1, 1.0-beta-2 Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK 1.5.0_08, archiva HEAD Reporter: Magne Rasmussen Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 Sometimes when deploying with dav I get a 507 Insufficient Storage error. The artifact (.../group/artifact/version/artifact-version.jar) gets deployed (with checksums). The metadata (.../group/artifact/version/maven-metatdata.xml) gets deployed (with checksums). It seems to happen when maven tries to upload the updated parent metadata (.../group/artifact/maven-metadata.xml). The checksums for this metadata deploys OK. -- 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: (MRM-243) 507 Insufficient Storage when deploying artifact with webdav
[ http://jira.codehaus.org/browse/MRM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130001#action_130001 ] Andrew Heald commented on MRM-243: -- Thanks, Brett. I have 1.0.2 up and running and I'll report back after a few days if the upload errors vanish. 507 Insufficient Storage when deploying artifact with webdav Key: MRM-243 URL: http://jira.codehaus.org/browse/MRM-243 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-alpha-1, 1.0-alpha-2, 1.0-beta-1, 1.0-beta-2 Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK 1.5.0_08, archiva HEAD Reporter: Magne Rasmussen Assignee: Joakim Erdfelt Fix For: 1.0-beta-3 Sometimes when deploying with dav I get a 507 Insufficient Storage error. The artifact (.../group/artifact/version/artifact-version.jar) gets deployed (with checksums). The metadata (.../group/artifact/version/maven-metatdata.xml) gets deployed (with checksums). It seems to happen when maven tries to upload the updated parent metadata (.../group/artifact/maven-metadata.xml). The checksums for this metadata deploys OK. -- 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: (MRM-123) add RSS view to repository manager
[ http://jira.codehaus.org/browse/MRM-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130021#action_130021 ] Maria Odea Ching commented on MRM-123: -- Changes in -r645576: - generate/update rss feeds after repository scan - add rss feed icon in repositories (for new artifacts in repo feed) and in browse artifact (for new versions of artifact feed) add RSS view to repository manager -- Key: MRM-123 URL: http://jira.codehaus.org/browse/MRM-123 Project: Archiva Issue Type: New Feature Components: web application Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.1 possibly needs a new component in JIRA. Items that could have RSS: - a particular search - preset for latest added artifacts - preset for new versions of artifacts - preset for new artifacts from a given sync partner -- 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
