[jira] Commented: (MRM-773) Improve RSS feed generation
[ http://jira.codehaus.org/browse/MRM-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131213#action_131213 ] Maria Odea Ching commented on MRM-773: -- Security: - if a user who is subscribed to a feed has been stripped of the necessary permissions or has been deleted, the user should no longer be able to receive updates from the feed Improve RSS feed generation --- Key: MRM-773 URL: http://jira.codehaus.org/browse/MRM-773 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 - add check to control file size of generated RSS feeds - make sure that the when the client requests the RSS, it gets the right headers to not try and update it if it hasn't changed for performance - get the urls of the feeds from the rss feed request More info in: http://www.nabble.com/Re%3A-svn-commit%3A-r645833---in--archiva-trunk%3A-archiva-jetty-src-main-conf-jetty.xml-archiva-modules-archiva-web-archiva-rss-src-main-java-org-apache-archiva-rss-processor-NewArtifactsRssFeedProcessor.java-td16562163.html -- 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-773) Improve RSS feed generation
[ http://jira.codehaus.org/browse/MRM-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130833#action_130833 ] Maria Odea Ching commented on MRM-773: -- Also, clicking the rss feed icon in the repositories page results to a 404 error if the rss feed file does not exist yet. Improve RSS feed generation --- Key: MRM-773 URL: http://jira.codehaus.org/browse/MRM-773 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 - add check to control file size of generated RSS feeds - make sure that the when the client requests the RSS, it gets the right headers to not try and update it if it hasn't changed for performance - get the urls of the feeds from the rss feed request More info in: http://www.nabble.com/Re%3A-svn-commit%3A-r645833---in--archiva-trunk%3A-archiva-jetty-src-main-conf-jetty.xml-archiva-modules-archiva-web-archiva-rss-src-main-java-org-apache-archiva-rss-processor-NewArtifactsRssFeedProcessor.java-td16562163.html -- 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: (MRM-677) Upgrade archiva to the latest redback (1.0.1)
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-677: - Summary: Upgrade archiva to the latest redback (1.0.1) (was: Upgrade archiva to the latest redback (1.1)) Upgrade archiva to the latest redback (1.0.1) - Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 -- 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: (MRM-777) assignments.jsp: missing tr/tr group under Resource Roles:
[
http://jira.codehaus.org/browse/MRM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-777:
-
Fix Version/s: 1.1
assignments.jsp: missing tr/tr group under Resource Roles:
--
Key: MRM-777
URL: http://jira.codehaus.org/browse/MRM-777
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.1
Reporter: Carlos Costa e Silva
Priority: Minor
Fix For: 1.1
/archiva-webapp/src/main/webapp/WEB-INF/jsp/redback/admin/assignments.jsp
missing tr/tr group under Resource Roles:
h5Resource Roles:/h5
...
c:forEach var=row items=${table}
-- tr
c:forEach var=column items=${row}
...
/c:forEach
-- /tr
/c:forEach
--
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: (MRM-711) Security using ldap throws NullPointerException
[ http://jira.codehaus.org/browse/MRM-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-711. Resolution: Fixed Fixed in redback 1.0.1. I already upgraded archiva's redback to this version (-r647651). Security using ldap throws NullPointerException --- Key: MRM-711 URL: http://jira.codehaus.org/browse/MRM-711 Project: Archiva Issue Type: Bug Components: Users/Security Affects Versions: 1.0.1 Environment: Ubuntu Linux, Open-ldap Reporter: Lucas Vilela de Souza Gonçalves Assignee: Maria Odea Ching Priority: Critical Fix For: 1.1 I configured ~/.m2/security.properties with ldap information. In DefaultArchivaConfiguration the Registry load all informations of security.properties. When i was loggin throws this Exception: java.lang.NullPointerException org.codehaus.plexus.redback.common.ldap.connection.LdapConnection.init(LdapConnection.java:58) org.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory.getConnection(ConfigurableLdapConnectionFactory.java:123) org.codehaus.plexus.redback.authentication.ldap.LdapBindAuthenticator.authenticate(LdapBindAuthenticator.java:92) I got redback source code, and i see that any information of ldap was there in LdapConnection! -- 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: (MRM-775) Support generation of pom for legacy artifacts in web upload form
[ http://jira.codehaus.org/browse/MRM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-775: - Fix Version/s: 1.x Support generation of pom for legacy artifacts in web upload form - Key: MRM-775 URL: http://jira.codehaus.org/browse/MRM-775 Project: Archiva Issue Type: New Feature Components: web application Affects Versions: 1.1 Reporter: Maria Odea Ching Fix For: 1.x -- 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: (MRM-774) Support inclusion of pom file when deploying an artifact via the web upload form
[ http://jira.codehaus.org/browse/MRM-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-774: - Fix Version/s: 1.x Support inclusion of pom file when deploying an artifact via the web upload form Key: MRM-774 URL: http://jira.codehaus.org/browse/MRM-774 Project: Archiva Issue Type: New Feature Components: web application Affects Versions: 1.1 Reporter: Maria Odea Ching Fix For: 1.x Currently the web upload form only supports pom generation when uploading M2 artifacts. -- 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
[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=129960#action_129960 ] Maria Odea Ching commented on MRM-123: -- Additional commit in -r645347: - generate feeds for new artifacts in the repository and new versions of artifacts - created tests 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
[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=129501#action_129501 ] Maria Odea Ching commented on MRM-123: -- Initial commit in -r643826. 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
[jira] Updated: (MRM-622) database not being updated with project model information
[ http://jira.codehaus.org/browse/MRM-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-622: - Fix Version/s: (was: 1.1) 1.0.2 database not being updated with project model information - Key: MRM-622 URL: http://jira.codehaus.org/browse/MRM-622 Project: Archiva Issue Type: Bug Affects Versions: 1.0 Environment: OS: Windows XP Software: Java 5 Update 12 and Maven 2.0.4 Reporter: Dário Oliveros Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: archiva-database-consumers.patch, archiva-database.patch, archiva-scheduled.patch I noticed Archiva database was not being updated with project model information in the following scenario: 1) Project B (1.0-SNAPSHOT) depends on Project A (1.0) 2) Project B is deployed to Archiva repository 3) Project B changes Project A dependency version from 1.0 to 1.1-SNAPSHOT 4) Project B is deployed to Archiva repository again. 5) The user executes 'Scan Repository Now' and 'Update Database Now' using Archiva. At this point, if you browse project B, you'll notice it still keeps the reference to the former version of Project A, 1.0, and not 1.1-SNAPSHOT. However, if you download the POM file, you will see it has the lastet dependency version as expected. NOTE: In project B POM file the snapshotRepository is configured with uniqueVersion equals to false. -- 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: (MRM-688) Replace plexus-runtime with standalone jetty bundle
[ http://jira.codehaus.org/browse/MRM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-688: - Assignee: Brett Porter (was: Maria Odea Ching) Replace plexus-runtime with standalone jetty bundle --- Key: MRM-688 URL: http://jira.codehaus.org/browse/MRM-688 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Brett Porter Fix For: 1.1 http://www.nabble.com/Re%3A-Archiva-1.1-Roadmap-p15331690.html -- 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-754) Update the screenshots in the docs
Update the screenshots in the docs -- Key: MRM-754 URL: http://jira.codehaus.org/browse/MRM-754 Project: Archiva Issue Type: Task Components: documentation Reporter: Maria Odea Ching Priority: Minor Fix For: 1.1 Update the following to reflect the changes in the UI (new sections like Legacy Support and Upload Artifact): - Feature Tour - Reports - Search - Identifying An Artifact -- 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-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127984 ] Maria Odea Ching commented on MRM-677: -- I'll update the issue summary as the released redback 1.0 is not usable when I upgraded Archiva to it. The errors I posted above are what I encountered in redback 1.0. The fixes for it are already in place in the deployed redback 1.1-SNAPSHOT. Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 -- 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: (MRM-677) Upgrade archiva to the latest redback (1.1)
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-677: - Summary: Upgrade archiva to the latest redback (1.1) (was: Upgrade archiva to redback 1.0) Upgrade archiva to the latest redback (1.1) --- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 -- 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: (MRM-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-677. Resolution: Fixed Fixed in archiva-trunk -r638845. Changes made: - upgraded redback to 1.1-SNAPSHOT - updated the archiva redback models to the new redback model Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 -- 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] Assigned: (MRM-711) Security using ldap throws NullPointerException
[ http://jira.codehaus.org/browse/MRM-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching reassigned MRM-711: Assignee: Maria Odea Ching Security using ldap throws NullPointerException --- Key: MRM-711 URL: http://jira.codehaus.org/browse/MRM-711 Project: Archiva Issue Type: Bug Components: Users/Security Affects Versions: 1.0.1 Environment: Ubuntu Linux, Open-ldap Reporter: Lucas Vilela de Souza Gonçalves Assignee: Maria Odea Ching Priority: Critical Fix For: 1.1 I configured ~/.m2/security.properties with ldap information. In DefaultArchivaConfiguration the Registry load all informations of security.properties. When i was loggin throws this Exception: java.lang.NullPointerException org.codehaus.plexus.redback.common.ldap.connection.LdapConnection.init(LdapConnection.java:58) org.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory.getConnection(ConfigurableLdapConnectionFactory.java:123) org.codehaus.plexus.redback.authentication.ldap.LdapBindAuthenticator.authenticate(LdapBindAuthenticator.java:92) I got redback source code, and i see that any information of ldap was there in LdapConnection! -- 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] Assigned: (MRM-591) Reports should show from which repository the defective artifact was found.
[ http://jira.codehaus.org/browse/MRM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching reassigned MRM-591: Assignee: Maria Odea Ching Reports should show from which repository the defective artifact was found. --- Key: MRM-591 URL: http://jira.codehaus.org/browse/MRM-591 Project: Archiva Issue Type: Improvement Components: reporting Affects Versions: 1.0-beta-4 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 In the report showing the defective/problematic artifacts from All Repositories, it would be nice to see from which repository each defective artifact was found. The artifacts could be grouped by repository. -- 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: (MRM-608) Unable to find project model for [...] if the initial import of the POM failed
[ http://jira.codehaus.org/browse/MRM-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-608. Resolution: Fixed Fixed in -r637023. -set whenProcessed to null of every artifact discovered (ArtufactUpdateDatabaseConsumer) Unable to find project model for [...] if the initial import of the POM failed --- Key: MRM-608 URL: http://jira.codehaus.org/browse/MRM-608 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0 Environment: Windows32 Reporter: Arne Degenring Assignee: Maria Odea Ching Priority: Critical Fix For: 1.1 Attachments: archiva.log, data.zip It seems that Archiva is not properly updating the database if the initial import of the POM failed due to a parse error, even after the original problem has been corrected, the repository has been rescanned, and the database updated again. Steps to reproduce: 1. Start with a fresh Archiva 1.0 installation 2. Drop a group containing an artifact with a broken POM (illegal XML) to Archiva's internal repo directory 3. Run Scan Repository Now and Update Database Now. The log shows a ProjectModelException because the broken POM could not be parsed. 4. Fix the broken POM. Run Scan Repository Now and Update Database Now again. 5. Use the Browse page to browse to the artifact - you get the error message: Unable to find project model for [junit:junit:3.7]. I've attached the zipped contents of the data directory after performing the steps above, and the log file. Notice that there might be general repository scanning problem in 1.0 that could be related, see http://www.nabble.com/Repository-scanning-problem-in-1.0--tf4897121.html -- 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-216) Upload (deploy) artifacts to a repository - via a web form (not using wagon)
[ http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127064 ] Maria Odea Ching commented on MRM-216: -- The following has already been finished in -r636284 and -r636703: - 'Upload Artifact' already in navigation menu - dropdown box for the repository ids - check for write permissions before allowing deployment in repo - allow user to specify whether to generate a pom for the artifact - update metadata file Upload (deploy) artifacts to a repository - via a web form (not using wagon) Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink Assignee: John Tolentino Fix For: 1.1 Attachments: MRM-216-20070818-1935.patch The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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: (MRM-216) Upload (deploy) artifacts to a repository - via a web form (not using wagon)
[ http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127064 ] oching edited comment on MRM-216 at 3/13/08 8:24 PM: --- The following has already been finished in -r636284 and -r636703: - 'Upload Artifact' already in navigation menu - dropdown box for the repository ids - check for write permissions before allowing deployment in repo - allow user to specify whether to generate a pom for the artifact (for Maven 2 artifacts) - update metadata file was (Author: oching): The following has already been finished in -r636284 and -r636703: - 'Upload Artifact' already in navigation menu - dropdown box for the repository ids - check for write permissions before allowing deployment in repo - allow user to specify whether to generate a pom for the artifact - update metadata file Upload (deploy) artifacts to a repository - via a web form (not using wagon) Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink Assignee: John Tolentino Fix For: 1.1 Attachments: MRM-216-20070818-1935.patch The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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-216) Upload (deploy) artifacts to a repository - via a web form (not using wagon)
[ http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127168 ] Maria Odea Ching commented on MRM-216: -- Additional fix: - Added form validation and other validations in action class (-r636953) Upload (deploy) artifacts to a repository - via a web form (not using wagon) Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink Assignee: John Tolentino Fix For: 1.1 Attachments: MRM-216-20070818-1935.patch The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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-216) Upload (deploy) artifacts to a repository - via a web form (not using wagon)
[ http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127170 ] Maria Odea Ching commented on MRM-216: -- Additional fix: - generate or update checksums of metadata file (-r636957) Upload (deploy) artifacts to a repository - via a web form (not using wagon) Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink Assignee: John Tolentino Fix For: 1.1 Attachments: MRM-216-20070818-1935.patch The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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-216) Upload (deploy) artifacts to a repository - via a web form (not using wagon)
[ http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127171 ] Maria Odea Ching commented on MRM-216: -- Added instructions on how to deploy an artifact via the web UI form in archiva-docs (-r636970) Upload (deploy) artifacts to a repository - via a web form (not using wagon) Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink Assignee: John Tolentino Fix For: 1.1 Attachments: MRM-216-20070818-1935.patch The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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: (MRM-216) Upload (deploy) artifacts to a repository - via a web form (not using wagon)
[ http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-216. Resolution: Fixed Upload (deploy) artifacts to a repository - via a web form (not using wagon) Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink Assignee: Maria Odea Ching Fix For: 1.1 Attachments: MRM-216-20070818-1935.patch The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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] Assigned: (MRM-608) Unable to find project model for [...] if the initial import of the POM failed
[ http://jira.codehaus.org/browse/MRM-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching reassigned MRM-608: Assignee: Maria Odea Ching Unable to find project model for [...] if the initial import of the POM failed --- Key: MRM-608 URL: http://jira.codehaus.org/browse/MRM-608 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0 Environment: Windows32 Reporter: Arne Degenring Assignee: Maria Odea Ching Priority: Critical Fix For: 1.1 Attachments: archiva.log, data.zip It seems that Archiva is not properly updating the database if the initial import of the POM failed due to a parse error, even after the original problem has been corrected, the repository has been rescanned, and the database updated again. Steps to reproduce: 1. Start with a fresh Archiva 1.0 installation 2. Drop a group containing an artifact with a broken POM (illegal XML) to Archiva's internal repo directory 3. Run Scan Repository Now and Update Database Now. The log shows a ProjectModelException because the broken POM could not be parsed. 4. Fix the broken POM. Run Scan Repository Now and Update Database Now again. 5. Use the Browse page to browse to the artifact - you get the error message: Unable to find project model for [junit:junit:3.7]. I've attached the zipped contents of the data directory after performing the steps above, and the log file. Notice that there might be general repository scanning problem in 1.0 that could be related, see http://www.nabble.com/Repository-scanning-problem-in-1.0--tf4897121.html -- 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-711) Security using ldap throws NullPointerException
[ http://jira.codehaus.org/browse/MRM-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126789 ] Maria Odea Ching commented on MRM-711: -- This is already fixed in redback-trunk. We're migrating archiva 1.0.2 to the latest redback, so this would be fixed by then. I'll move this issue to 1.0.2.. Security using ldap throws NullPointerException --- Key: MRM-711 URL: http://jira.codehaus.org/browse/MRM-711 Project: Archiva Issue Type: Bug Components: Users/Security Affects Versions: 1.0.1 Environment: Ubuntu Linux, Open-ldap Reporter: Lucas Vilela de Souza Gonçalves Priority: Critical I configured ~/.m2/security.properties with ldap information. In DefaultArchivaConfiguration the Registry load all informations of security.properties. When i was loggin throws this Exception: java.lang.NullPointerException org.codehaus.plexus.redback.common.ldap.connection.LdapConnection.init(LdapConnection.java:58) org.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory.getConnection(ConfigurableLdapConnectionFactory.java:123) org.codehaus.plexus.redback.authentication.ldap.LdapBindAuthenticator.authenticate(LdapBindAuthenticator.java:92) I got redback source code, and i see that any information of ldap was there in LdapConnection! -- 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: (MRM-711) Security using ldap throws NullPointerException
[ http://jira.codehaus.org/browse/MRM-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-711: - Fix Version/s: 1.0.2 Security using ldap throws NullPointerException --- Key: MRM-711 URL: http://jira.codehaus.org/browse/MRM-711 Project: Archiva Issue Type: Bug Components: Users/Security Affects Versions: 1.0.1 Environment: Ubuntu Linux, Open-ldap Reporter: Lucas Vilela de Souza Gonçalves Priority: Critical Fix For: 1.0.2 I configured ~/.m2/security.properties with ldap information. In DefaultArchivaConfiguration the Registry load all informations of security.properties. When i was loggin throws this Exception: java.lang.NullPointerException org.codehaus.plexus.redback.common.ldap.connection.LdapConnection.init(LdapConnection.java:58) org.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory.getConnection(ConfigurableLdapConnectionFactory.java:123) org.codehaus.plexus.redback.authentication.ldap.LdapBindAuthenticator.authenticate(LdapBindAuthenticator.java:92) I got redback source code, and i see that any information of ldap was there in LdapConnection! -- 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-216) Upload (deploy) artifacts to a repository - via a web form (not using wagon)
[ http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126798 ] Maria Odea Ching commented on MRM-216: -- Applied the patch in archiva-trunk -r635836. I commented out some parts in the UploadAction class which need to be modified due to the changes in the Archiva components used. I made an initial list of what I think still needs to be done and can be improved: - modify the commented parts to adapt to the changes in the components (like the repository layout) - add 'Upload/Deploy Artifact' in the navigation menu - form validation - maybe we could have a drop-down box for the repository ids - include this feature in the documentation Upload (deploy) artifacts to a repository - via a web form (not using wagon) Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink Assignee: John Tolentino Fix For: 1.1 Attachments: MRM-216-20070818-1935.patch The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126680 ] Maria Odea Ching commented on MRM-727: -- I also found this in the geronimo logs.. 14:32:33,558 ERROR [[RepositoryServlet]] Servlet.service() for servlet RepositoryServlet threw exception org.dom4j.InvalidXPathException: Invalid XPath expression: '//metadata/groupId'. Caused by: org/dom4j/Element at org.dom4j.xpath.DefaultXPath.parse(DefaultXPath.java:362) at org.dom4j.xpath.DefaultXPath.init(DefaultXPath.java:59) at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230) at org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207) at org.apache.maven.archiva.xml.XMLReader.createXPath(XMLReader.java:175) at org.apache.maven.archiva.xml.XMLReader.getElementText(XMLReader.java:258) at org.apache.maven.archiva.repository.metadata.RepositoryMetadataReader.read(RepositoryMetadataReader.java:56) at org.apache.maven.archiva.repository.metadata.MetadataTools.readProxyMetadata(MetadataTools.java:360) at org.apache.maven.archiva.repository.metadata.MetadataTools.updateMetadata(MetadataTools.java:435) at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:367) at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchMetadataFromProxies(ProxiedDavServer.java:405) at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:343) at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:189) at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) at org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:353) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Is this the one you've mentioned above Christian? Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea
[jira] Commented: (MRM-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126687 ] Maria Odea Ching commented on MRM-727: -- Could you try it Christian and see if it works for you? Thanks.. Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml When i have an initially blank local maven repo and for example start maven with mvn clean, no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404. When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though. From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a normal artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct file. -- 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-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126673 ] Maria Odea Ching commented on MRM-727: -- Hi James, I was able to reproduce the plugin download problem in Geronimo. The metadata xml files are all incorrect for the plugins. I've attached the logs and the metadata files. Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: MRM727.diff, settings-wrong.xml When i have an initially blank local maven repo and for example start maven with mvn clean, no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404. When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though. From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a normal artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct file. -- 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: (MRM-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-727: - Attachment: MRM-727-build-stack-trace.txt Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: MRM-727-build-stack-trace.txt, MRM727.diff, settings-wrong.xml When i have an initially blank local maven repo and for example start maven with mvn clean, no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404. When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though. From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a normal artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct file. -- 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-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126674 ] Maria Odea Ching commented on MRM-727: -- Christian, I think the dom4j problem is a different one. I got those errors from the geronimo logs as well (see below), but not from proxying but during the repo scanning.. ... 11:00:07,819 ERROR [DatabaseUnprocessedArtifactConsumer:update-db-project] Unable to process model /home/deng/TestFiles/internal/org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.pom due to : org.dom4j.InvalidXPathException : Invalid XPath expression: '//project'. Caused by: org/dom4j/Element org.dom4j.InvalidXPathException: Invalid XPath expression: '//project'. Caused by: org/dom4j/Element at org.dom4j.xpath.DefaultXPath.parse(DefaultXPath.java:362) at org.dom4j.xpath.DefaultXPath.init(DefaultXPath.java:59) at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230) at org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207) at org.apache.maven.archiva.xml.XMLReader.createXPath(XMLReader.java:175) at org.apache.maven.archiva.xml.XMLReader.getElement(XMLReader.java:152) at org.apache.maven.archiva.repository.project.readers.ProjectModel400Reader.read(ProjectModel400Reader.java:80) at org.apache.maven.archiva.consumers.database.ProjectModelToDatabaseConsumer.processArchivaArtifact(ProjectModelToDatabaseConsumer.java:151) at org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:52) at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateUnprocessed(JdoDatabaseUpdater.java:152) at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllUnprocessed(JdoDatabaseUpdater.java:86) at org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:68) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) ... Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml When i have an initially blank local maven repo and for example start maven with mvn clean, no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404. When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though. From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a normal artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct file. -- 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] Work started: (MRM-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-727 started by Maria Odea Ching. Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: MRM727.diff, settings-wrong.xml When i have an initially blank local maven repo and for example start maven with mvn clean, no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404. When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though. From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a normal artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct file. -- 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-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126106 ] Maria Odea Ching commented on MRM-727: -- I tried to replicate this in the standalone archiva using the attached settings.xml, and I couldn't replicate the issue. This is my environment: - maven 2.0.7/maven-2.0.8 - ubuntu 7.04 - jdk 1.5.0_11 I will try deploying Archiva to Geronimo.. Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: MRM727.diff, settings-wrong.xml When i have an initially blank local maven repo and for example start maven with mvn clean, no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404. When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though. From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a normal artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct file. -- 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] Work stopped: (MRM-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-677 stopped by Maria Odea Ching. Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.0.2 -- 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-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126234 ] Maria Odea Ching commented on MRM-677: -- Current status of this issue: waiting for the deployed redback-1.1-SNAPSHOT which contains the fixes to be synched to the codehaus snapshots repo Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.0.2 -- 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-730) Index/Search by class, method or package name
[ http://jira.codehaus.org/browse/MRM-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126269 ] Maria Odea Ching commented on MRM-730: -- There are already stub consumers for this in archiva-lucene-consumers (IndexArchiveTableOfContentsConsumer and IndexJavaPublicMethodsConsumer). Only the implementation code is needed. Index/Search by class, method or package name - Key: MRM-730 URL: http://jira.codehaus.org/browse/MRM-730 Project: Archiva Issue Type: New Feature Components: indexing Reporter: Maria Odea Ching -- 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-688) Replace plexus-runtime with standalone jetty bundle
[ http://jira.codehaus.org/browse/MRM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126013 ] Maria Odea Ching commented on MRM-688: -- Okay, I'll just adjust the documentation for now. I'll add the archiva-jetty module to the build as well so people can also try it out and test it. Thanks! Replace plexus-runtime with standalone jetty bundle --- Key: MRM-688 URL: http://jira.codehaus.org/browse/MRM-688 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 http://www.nabble.com/Re%3A-Archiva-1.1-Roadmap-p15331690.html -- 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] Work stopped: (MRM-688) Replace plexus-runtime with standalone jetty bundle
[ http://jira.codehaus.org/browse/MRM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-688 stopped by Maria Odea Ching. Replace plexus-runtime with standalone jetty bundle --- Key: MRM-688 URL: http://jira.codehaus.org/browse/MRM-688 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 http://www.nabble.com/Re%3A-Archiva-1.1-Roadmap-p15331690.html -- 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] Assigned: (MRM-727) Archiva does not download plugin artifacts
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching reassigned MRM-727: Assignee: Maria Odea Ching Archiva does not download plugin artifacts -- Key: MRM-727 URL: http://jira.codehaus.org/browse/MRM-727 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client Reporter: Christian Domsch Assignee: Maria Odea Ching Fix For: 1.0.2 Attachments: settings-wrong.xml When i have an initially blank local maven repo and for example start maven with mvn clean, no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404. When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though. From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a normal artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct file. -- 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] Work started: (MRM-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-677 started by Maria Odea Ching. Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.0.2 -- 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-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126014 ] Maria Odea Ching commented on MRM-677: -- After upgrading Archiva to redback-1.0, i'm getting the following error during startup: jvm 1| INFO: ** FATAL ERROR STARTING UP PLEXUS-WEBWORK INTEGRATION ** jvm 1| Looks like the Plexus listener was not configured for your web app! jvm 1| You need to add the following to web.xml: jvm 1| jvm 1| listener jvm 1| listener-classorg.codehaus.plexus.xwork.PlexusLifecycleListener/listener-class jvm 1| /listener jvm 1| Mar 4, 2008 6:54:47 PM org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Plexus container already in context. jvm 1| 2008-03-04 18:54:49,149 [WrapperSimpleAppMain] WARN net.sf.ehcache.config.ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/home/deng/Projects/archiva-1.0.x-022508/archiva-web/archiva-standalone/archiva-plexus-runtime/target/apache-archiva-1.0.2-SNAPSHOT/apps/archiva/webapp/WEB-INF/lib/ehcache-1.3.0.jar!/ehcache-failsafe.xml jvm 1| [ERROR] Error while deploying appserver archiva-plexus-application-1.0.2-SNAPSHOT.jar. jvm 1| org.codehaus.plexus.appserver.ApplicationServerException: Error in the app server lifecycle post-app-container-init-service-call phase. jvm 1| at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeployer.deployJar(DefaultApplicationDeployer.java:119) jvm 1| at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeployer.deploy(DefaultApplicationDeployer.java:88) jvm 1| at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase$1.onJarDiscovered(ApplicationDeploymentPhase.java:44) jvm 1| at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scanDirectory(DefaultSupervisor.java:100) jvm 1| at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scan(DefaultSupervisor.java:73) jvm 1| at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase.execute(ApplicationDeploymentPhase.java:58) jvm 1| at org.codehaus.plexus.appserver.DefaultApplicationServer.start(DefaultApplicationServer.java:218) jvm 1| at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java:33) jvm 1| at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:128) jvm 1| at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:142) jvm 1| at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:132) jvm 1| at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:90) jvm 1| at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:147) jvm 1| at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:69) jvm 1| at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:297) jvm 1| at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291) jvm 1| at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicationHost.java:155) jvm 1| at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicationHost.java:85) jvm 1| at org.codehaus.plexus.appserver.PlexusApplicationHost.main(PlexusApplicationHost.java:289) jvm 1| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) jvm 1| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) jvm 1| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) jvm 1| at java.lang.reflect.Method.invoke(Method.java:585) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) jvm 1| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) jvm 1| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) jvm 1| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) jvm 1| at java.lang.reflect.Method.invoke(Method.java:585) jvm 1| at
[jira] Commented: (MRM-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126074 ] Maria Odea Ching commented on MRM-677: -- After applying REDBACK-129 to redback 1.0, i now got this error during startup: jvm 1| INFO: ** FATAL ERROR STARTING UP PLEXUS-WEBWORK INTEGRATION ** jvm 1| Looks like the Plexus listener was not configured for your web app! jvm 1| You need to add the following to web.xml: jvm 1| jvm 1| listener jvm 1| listener-classorg.codehaus.plexus.xwork.PlexusLifecycleListener/listener-class jvm 1| /listener jvm 1| Mar 5, 2008 10:14:56 AM org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Plexus container already in context. jvm 1| 2008-03-05 10:14:58,200 [WrapperSimpleAppMain] WARN net.sf.ehcache.config.ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/home/deng/Projects/archiva-1.0.x-022508/archiva-web/archiva-standalone/archiva-plexus-runtime/target/apache-archiva-1.0.2-SNAPSHOT/apps/archiva/webapp/WEB-INF/lib/ehcache-1.3.0.jar!/ehcache-failsafe.xml jvm 1| Mar 5, 2008 10:14:58 AM org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Initializing org.codehaus.plexus.webdav.simple.SimpleDavServerComponent jvm 1| Mar 5, 2008 10:14:58 AM org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Initializing org.codehaus.plexus.webdav.simple.SimpleDavServerComponent jvm 1| [ERROR] Error while deploying appserver archiva-plexus-application-1.0.2-SNAPSHOT.jar. jvm 1| org.codehaus.plexus.appserver.ApplicationServerException: Error in the app server lifecycle post-app-container-init-service-call phase. jvm 1| at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeployer.deployJar(DefaultApplicationDeployer.java:119) jvm 1| at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeployer.deploy(DefaultApplicationDeployer.java:88) jvm 1| at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase$1.onJarDiscovered(ApplicationDeploymentPhase.java:44) jvm 1| at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scanDirectory(DefaultSupervisor.java:100) jvm 1| at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scan(DefaultSupervisor.java:73) jvm 1| at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase.execute(ApplicationDeploymentPhase.java:58) jvm 1| at org.codehaus.plexus.appserver.DefaultApplicationServer.start(DefaultApplicationServer.java:218) jvm 1| at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java:33) jvm 1| at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:128) jvm 1| at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:142) jvm 1| at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:132) jvm 1| at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:90) jvm 1| at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:147) jvm 1| at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:69) jvm 1| at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:297) jvm 1| at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291) jvm 1| at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicationHost.java:155) jvm 1| at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicationHost.java:85) jvm 1| at org.codehaus.plexus.appserver.PlexusApplicationHost.main(PlexusApplicationHost.java:289) jvm 1| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) jvm 1| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) jvm 1| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) jvm 1| at java.lang.reflect.Method.invoke(Method.java:585) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) jvm 1| at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) jvm 1| at
[jira] Commented: (MRM-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126076 ] Maria Odea Ching commented on MRM-677: -- After applying REDBACK-129 and REDBACK-125 in redback 1.0, Archiva was able to startup successfully. I'll test redback 1.0 with Continuum as well to verify it's behaviour. Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.0.2 -- 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-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126093 ] Maria Odea Ching commented on MRM-677: -- We might need to wait for the next Redback release for the fixes :-) Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.0.2 -- 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-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126091 ] Maria Odea Ching commented on MRM-677: -- These problems also persist in Continuum, though it occurs not during startup but when you try to access the webapp after it was started. Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.0.2 -- 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-688) Replace plexus-runtime with standalone jetty bundle
[ http://jira.codehaus.org/browse/MRM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125999 ] Maria Odea Ching commented on MRM-688: -- Changes made in -r633367: -added config for mail session and archiva users db in jetty.xml -unpack webapp during packaging so that it would be run during startup Replace plexus-runtime with standalone jetty bundle --- Key: MRM-688 URL: http://jira.codehaus.org/browse/MRM-688 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 http://www.nabble.com/Re%3A-Archiva-1.1-Roadmap-p15331690.html -- 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-688) Replace plexus-runtime with standalone jetty bundle
[ http://jira.codehaus.org/browse/MRM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125559 ] Maria Odea Ching commented on MRM-688: -- Added archiva-jetty-archetype-module in archiva-trunk -r632245. This is not yet included in the build for now, as the generated wrapper files are corrupted (see MOJO-1060) Replace plexus-runtime with standalone jetty bundle --- Key: MRM-688 URL: http://jira.codehaus.org/browse/MRM-688 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Assignee: Maria Odea Ching Fix For: 1.1 http://www.nabble.com/Re%3A-Archiva-1.1-Roadmap-p15331690.html -- 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: (MRM-698) Add a 'Known Issues' section in the release notes documentation
[ http://jira.codehaus.org/browse/MRM-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-698: - Fix Version/s: 1.0.2 Add a 'Known Issues' section in the release notes documentation --- Key: MRM-698 URL: http://jira.codehaus.org/browse/MRM-698 Project: Archiva Issue Type: Task Components: documentation Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Fix For: 1.0.2 -- 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: (MRM-692) Repository problem is kept in database even though its related artifact has been already removed
[ http://jira.codehaus.org/browse/MRM-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-692: - Fix Version/s: 1.1 Repository problem is kept in database even though its related artifact has been already removed Key: MRM-692 URL: http://jira.codehaus.org/browse/MRM-692 Project: Archiva Issue Type: Bug Components: reporting Affects Versions: 1.0 Environment: Linux Fedora Core 5 / Windows XP Java 5 Update 12 Reporter: Dário Oliveros Assignee: Maria Odea Ching Fix For: 1.1 Attachments: archiva-mrm-692-over-mrm-622.patch, archiva-mrm-692.patch I've noticed the _Show Report_ functionality always displays repository problems of artifacts that have been already removed. In my opinion, it should not since its associated artifact does not exist anymore. No repository problem is ever purged causing the report to get bigger and bigger. -- 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-699) NPE in IndexArtifactConsumer during db scan
[ http://jira.codehaus.org/browse/MRM-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124029 ] Maria Odea Ching commented on MRM-699: -- I verified this on trunk but the NPE in IndexArtifactConsumer no longer exist.. instead an NPE shows up when there is a change in the repository and you execute db scan. But when you re-excute the db scan again, the NPE is gone and the db update task finishes successfully. Below is the stack trace: jvm 1| 2008-02-17 17:50:58,511 [SocketListener0-0] INFO com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request to update the database has been queued. jvm 1| 2008-02-17 17:50:58,514 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Executing task from queue with job name: database-job:user-requested jvm 1| 2008-02-17 17:50:58,514 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating unprocessed artifacts jvm 1| 2008-02-17 17:50:58,519 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating processed artifacts jvm 1| 2008-02-17 17:50:58,930 [Thread-5] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:database-update - Error executing task jvm 1| edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.NullPointerException jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127) jvm 1| Caused by: java.lang.NullPointerException jvm 1| at org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:56) jvm 1| at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) jvm 1| at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateProcessed(JdoDatabaseUpdater.java:170) jvm 1| at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllProcessed(JdoDatabaseUpdater.java:111) jvm 1| at org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:78) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) jvm 1| at java.lang.Thread.run(Thread.java:595) jvm 1| 2008-02-17 17:51:08,204 [SocketListener0-0] INFO com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request to update the database has been queued. jvm 1| 2008-02-17 17:51:08,206 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Executing task from queue with job name: database-job:user-requested jvm 1| 2008-02-17 17:51:08,206 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating unprocessed artifacts jvm 1| 2008-02-17 17:51:08,210 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating processed artifacts jvm 1| 2008-02-17 17:51:08,825 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Finished database task in 619ms. NPE in IndexArtifactConsumer during db scan --- Key: MRM-699 URL: http://jira.codehaus.org/browse/MRM-699 Project: Archiva Issue Type: Bug Affects Versions: 1.0.1 Reporter: Maria Odea Ching jvm 1| 2008-02-17 18:45:25,215 [SocketListener0-1] INFO com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request to update the database has been queued. jvm 1| 2008-02-17 18:45:25,216 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Executing task from queue with job name: database-job:user-requested jvm 1|
[jira] Issue Comment Edited: (MRM-699) NPE during db scan
[ http://jira.codehaus.org/browse/MRM-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124029 ] oching edited comment on MRM-699 at 2/17/08 4:52 AM: --- I verified this on trunk but the NPE in IndexArtifactConsumer** no longer exist.. instead an NPE shows up when there is a change in the repository and you execute db scan. But when you re-excute the db scan again, the NPE is gone and the db update task finishes successfully. Below is the stack trace: jvm 1| 2008-02-17 17:50:58,511 [SocketListener0-0] INFO com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request to update the database has been queued. jvm 1| 2008-02-17 17:50:58,514 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Executing task from queue with job name: database-job:user-requested jvm 1| 2008-02-17 17:50:58,514 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating unprocessed artifacts jvm 1| 2008-02-17 17:50:58,519 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating processed artifacts jvm 1| 2008-02-17 17:50:58,930 [Thread-5] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:database-update - Error executing task jvm 1| edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.NullPointerException jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127) jvm 1| Caused by: java.lang.NullPointerException jvm 1| at org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:56) jvm 1| at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) jvm 1| at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateProcessed(JdoDatabaseUpdater.java:170) jvm 1| at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllProcessed(JdoDatabaseUpdater.java:111) jvm 1| at org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:78) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) jvm 1| at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) jvm 1| at java.lang.Thread.run(Thread.java:595) jvm 1| 2008-02-17 17:51:08,204 [SocketListener0-0] INFO com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request to update the database has been queued. jvm 1| 2008-02-17 17:51:08,206 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Executing task from queue with job name: database-job:user-requested jvm 1| 2008-02-17 17:51:08,206 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating unprocessed artifacts jvm 1| 2008-02-17 17:51:08,210 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Task: Updating processed artifacts jvm 1| 2008-02-17 17:51:08,825 [pool-1-thread-1] INFO org.codehaus.plexus.taskqueue.execution.TaskExecutor:database-update - Finished database task in 619ms. **Please note that in the stack trace posted in the issue description, the NPE occurs in IndexArtifactConsumer was (Author: oching): I verified this on trunk but the NPE in IndexArtifactConsumer no longer exist.. instead an NPE shows up when there is a change in the repository and you execute db scan. But when you re-excute the db scan again, the NPE is gone and the db update task finishes successfully. Below is the stack trace: jvm 1| 2008-02-17 17:50:58,511 [SocketListener0-0] INFO com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request to update the database has been queued. jvm 1| 2008-02-17 17:50:58,514
[jira] Updated: (MRM-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-677: - Fix Version/s: (was: 1.1) 1.0.2 Upgrade archiva to redback 1.0 -- Key: MRM-677 URL: http://jira.codehaus.org/browse/MRM-677 Project: Archiva Issue Type: Task Components: build Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Fix For: 1.0.2 -- 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: (MRM-632) Repository Purge Consumer throws Invalid Path to Artifact
[
http://jira.codehaus.org/browse/MRM-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-632:
-
Fix Version/s: (was: 1.1)
1.0.2
Repository Purge Consumer throws Invalid Path to Artifact
-
Key: MRM-632
URL: http://jira.codehaus.org/browse/MRM-632
Project: Archiva
Issue Type: Bug
Components: repository scanning
Affects Versions: 1.0
Environment: Tomcat 6.0.14
Windows Server 2003
Reporter: Luke Amdor
Fix For: 1.0.2
I have the repository purge consumer enabled and configured as {{Repository
Purge By Days Older Than}} to 0 and {{Repository Purge By Retention Count}}
set to 3.
This is with a clean database.
I have more than 3 versions of org.irene:irene:2.0-SNAPSHOT already uploaded
into the repository.
When the repository is scanned:
{noformat}
290870 [pool-2-thread-1] ERROR
org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
Consumer [repository-purge] had an error when processing file
[D:\archiva-web\data\repositories\snapshots\org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar]:
Invalid path to Artifact: filename format is invalid,expected timestamp
format in filename.
org.apache.maven.archiva.consumers.ConsumerException: Invalid path to
Artifact: filename format is invalid,expected timestamp format in filename.
at
org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeConsumer.processFile(RepositoryPurgeConsumer.java:189)
at
org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:57)
at
org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117)
at
org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
at
org.apache.maven.archiva.repository.scanner.RepositoryScannerInstance.directoryWalkStep(RepositoryScannerInstance.java:138)
at
org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:173)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:391)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
at
org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
at
org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:344)
at
org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:120)
at
org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:64)
at
org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:106)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
at java.lang.Thread.run(Thread.java:595)
Caused by:
org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeException:
Invalid path to Artifact: filename format is invalid,expected timestamp
format in filename.
at
org.apache.maven.archiva.consumers.core.repository.RetentionCountRepositoryPurge.process(RetentionCountRepositoryPurge.java:102)
at
org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeConsumer.processFile(RepositoryPurgeConsumer.java:185)
... 20 more
290885 [pool-2-thread-1] ERROR
org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
Consumer [metadata-updater] had an error when processing file
[D:\archiva-web\data\repositories\snapshots\org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar]:
Unable to convert to artifact reference:
org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar
org.apache.maven.archiva.consumers.ConsumerException: Unable to convert to
artifact reference:
org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar
at
org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer.processFile(MetadataUpdaterConsumer.java:167)
[jira] Updated: (MRM-448) validation for reports form
[ http://jira.codehaus.org/browse/MRM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-448: - Fix Version/s: (was: 1.1) 1.0.2 validation for reports form --- Key: MRM-448 URL: http://jira.codehaus.org/browse/MRM-448 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-1 Reporter: Brett Porter Fix For: 1.0.2 validation is missing - see MRM-329 -- 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: (MRM-660) unable to uncheck releases included on a managed repository when editing the repository
[ http://jira.codehaus.org/browse/MRM-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-660: - Fix Version/s: 1.0.2 unable to uncheck releases included on a managed repository when editing the repository - Key: MRM-660 URL: http://jira.codehaus.org/browse/MRM-660 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0 Reporter: Brett Porter Fix For: 1.0.2 -- 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: (MRM-674) LayoutException when downloading SNAPSHOT test-sources
[
http://jira.codehaus.org/browse/MRM-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-674:
-
Fix Version/s: 1.0.2
LayoutException when downloading SNAPSHOT test-sources
--
Key: MRM-674
URL: http://jira.codehaus.org/browse/MRM-674
Project: Archiva
Issue Type: Bug
Components: WebDAV interface
Affects Versions: 1.0
Environment: Windows XP, Java 1.5
Reporter: Dan Fabulich
Priority: Critical
Fix For: 1.0.2
Attachments: my-app.zip
If you deploy a SNAPSHOT to Archiva that deploys test sources, and then try
to download the test sources, the download will fail with an error.
To reproduce: Using the attached project, deploy to Archiva, then go to
http://localhost:8080/archiva/repository/snapshots/com/mycompany/app/my-app/1.0-SNAPSHOT/
and try to download the test-sources.jar. (An example settings.xml file is
also provided in the archive; change its password and then do mvn deploy -s
settings.xml.)
You'll get a 404 error, with this exception:
{noformat}
org.apache.maven.archiva.repository.layout.LayoutException: Invalid path to
Artifact: filename format is invalid,expected timestamp format in filename.
at
org.apache.maven.archiva.repository.content.DefaultPathParser.toArtifactReference(DefaultPathParser.java:134)
at
org.apache.maven.archiva.repository.content.RepositoryRequest.toArtifactReference(RepositoryRequest.java:121)
at
org.apache.maven.archiva.repository.content.RepositoryRequest.toNativePath(RepositoryRequest.java:271)
at
org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:193)
at
org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119)
at
org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
at
com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at
com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
{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: (MRM-654) Archetype for generation of Consumer plugins
[ http://jira.codehaus.org/browse/MRM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-654: - Fix Version/s: 1.1 Archetype for generation of Consumer plugins Key: MRM-654 URL: http://jira.codehaus.org/browse/MRM-654 Project: Archiva Issue Type: Improvement Components: repository scanning Affects Versions: 1.1 Reporter: Stephen Gargan Priority: Trivial Fix For: 1.1 Attachments: archiva-consumer-plugin-archetype.patch I've created an archetype for use in creating artifact-consumer-plugin projects. It currently builds and runs against the head version of archiva. - Apply the attached patch in the archiva sandbox dir. - Build and install it - invoke with the following command line mvn archetype:create \ -DarchetypeGroupId=org.apache.maven.archiva\ -DarchetypeArtifactId=archiva-consumer-plugin-archetype \ -DarchetypeVersion=1.1-SNAPSHOT \ -DgroupId=org.example \ -DartifactId=simple-consumer-plugin This will create a project 'simple-consumer-plugin' rgds, ste -- 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: (MRM-656) Admin guide for installing WAR needs updating
[ http://jira.codehaus.org/browse/MRM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-656: - Fix Version/s: 1.x Admin guide for installing WAR needs updating - Key: MRM-656 URL: http://jira.codehaus.org/browse/MRM-656 Project: Archiva Issue Type: Improvement Components: reporting Affects Versions: 1.0 Environment: N/a Reporter: Koryn Grant Fix For: 1.x Original Estimate: 10 minutes Remaining Estimate: 10 minutes The web page at http://maven.apache.org/archiva/docs/1.0/adminguide/webapp.html; needs updating: * The name of the archiva WAR file in the archiva.xml sample should be apache-archiva-1.0.war. * For the note about Tomcat versions: Tomcat 5.5.25 works as expected, provided mail.jar and activation.jar are added to the common/lib directory. * For the note about Derby: Derby 10.3.2.1 seems to work fine. -- 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: (MRM-604) Company POM - Allow a different version than 1 to be entered.
[ http://jira.codehaus.org/browse/MRM-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-604: - Fix Version/s: 1.x Company POM - Allow a different version than 1 to be entered. - Key: MRM-604 URL: http://jira.codehaus.org/browse/MRM-604 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0-alpha-2 Environment: All. Reporter: Parag Mehta Priority: Minor Fix For: 1.x Company POM always takes version 1, a different version cannot be used/entered via GUI. Allow version to be specified along with existing group and artifact ids. Thanks. -- 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: (MRM-650) Deleted metadata files still appear in search results
[ http://jira.codehaus.org/browse/MRM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-650: - Fix Version/s: 1.x Deleted metadata files still appear in search results - Key: MRM-650 URL: http://jira.codehaus.org/browse/MRM-650 Project: Archiva Issue Type: Bug Components: indexing Affects Versions: 1.0 Reporter: Wendy Smoak Priority: Minor Fix For: 1.x When an entire directory tree of artifacts is removed from the repository filesystem, the metadata files still show up in search results. To reproduce, delete any group from the repository, then click both 'Scan Repository Now' and 'Update Database Now'. Search for the artifact again, and note that the metadata files still appear in the results. For example, after deleting /path/to/repository/releases/commons-lang and scanning/updating, this is in the search results for commons-lang: http://example.com/archiva/repository/releases/commons-lang/commons-lang/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] Updated: (MRM-625) LDAP authentication leaks connections
[ http://jira.codehaus.org/browse/MRM-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-625: - Fix Version/s: 1.x LDAP authentication leaks connections - Key: MRM-625 URL: http://jira.codehaus.org/browse/MRM-625 Project: Archiva Issue Type: Bug Components: Users/Security Affects Versions: 1.0-beta-4 Environment: Archiva 1.0-beta-4, OpenLdap Reporter: Emilio Jose Mena Cebrian Priority: Minor Fix For: 1.x I've configured redback to authenticate from a LDAP with cached used manager and I've detected it's leaking connections. Connections from web interface seem to be returned to LdapContext pool , but connection from repository servlet are leaked. The LdapCtx Configuration is : component roleorg.codehaus.plexus.redback.common.ldap.connection.LdapConnectionFactory/role role-hintconfigurable/role-hint implementationorg.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory/implementation description/description configuration hostnamelocalhost/hostname port389/port baseDn/baseDn contextFactorycom.sun.jndi.ldap.LdapCtxFactory/contextFactory password***/password bindDn/bindDn extraProperties property namecom.sun.jndi.ldap.connect.pool/name valuetrue/value /property property namecom.sun.jndi.ldap.connect.pool.maxsize/name value20/value /property property namecom.sun.jndi.ldap.connect.pool.prefsize/name value10/value /property property namecom.sun.jndi.ldap.connect.pool.timeout/name value3/value /property /extraProperties /configuration /component NOTE: sensible configuration tags are correctly configured, but i'm erased them (marked with *) -- 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: (MRM-629) NullPointer when setting corporate POM on a fresh archvia install
[
http://jira.codehaus.org/browse/MRM-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-629:
-
Fix Version/s: 1.x
NullPointer when setting corporate POM on a fresh archvia install
-
Key: MRM-629
URL: http://jira.codehaus.org/browse/MRM-629
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.0
Environment: archiva deployed as a war on tomcat 5.5
Reporter: nicolas de loof
Priority: Minor
Fix For: 1.x
Tryning to set a corporate POM fails with a NullPointerException
The maven-shared-application configuration expect a configuration to exist as
either org.apache.maven.shared.app.user or org.apache.maven.shared.app.base.
The first one is declared in archvia application.xml as
config-forceCreate=true, so it SHOULD have been created, but is absent
from my ${user.home}/.m2
This may be a plexus-registry-provider bug, or a commons-configuration bug.
--
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: (MRM-640) breadcrumbs need to incude current doc so you can navigate back to home page
[ http://jira.codehaus.org/browse/MRM-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-640: - Fix Version/s: 1.x breadcrumbs need to incude current doc so you can navigate back to home page Key: MRM-640 URL: http://jira.codehaus.org/browse/MRM-640 Project: Archiva Issue Type: Bug Reporter: Brett Porter Fix For: 1.x the 1.0 should go back to /archiva/docs/1.0, and the Archiva should go back to /archiva - and be available any time you are not on that index page. Including the page title as a non clickable breadcrumb is an option, or always making the last breadcrumb clickable if it is a different page to that linked. -- 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: (MRM-630) http 502 proxy error with browse button after 2 days running
[ http://jira.codehaus.org/browse/MRM-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-630. Resolution: Fixed http 502 proxy error with browse button after 2 days running Key: MRM-630 URL: http://jira.codehaus.org/browse/MRM-630 Project: Archiva Issue Type: Bug Components: browser Affects Versions: 1.0 Reporter: Julien CARSIQUE Fix For: 1.0.1 Attachments: logs.tar.gz I have to restart archiva every one or two days; if not, archiva becomes unstable : * main page and admin section are accessible and work fine, * archiva/browse/ function is dead, giving in navigator : Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request /GET /archiva/browse http://archiva.nuxeo.org/archiva/browse/. Reason: *Error reading from remote server* Restarting archiva immediately solves the problem. I didn't find relevant logs, I guess -- 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-633) Logging is too verbose
[ http://jira.codehaus.org/browse/MRM-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119419 ] Maria Odea Ching commented on MRM-633: -- -r610730 - committed the specified changes above except i no longer removed this line logger.debug( Sending to consumer: + consumer.getId() ); from ConsumerProcessFileClosure because the default logging level for the repo scanner was set to INFO anyway. The problem with the duplicated logs in archiva.log and wrapper.log still needs to be done. Logging is too verbose -- Key: MRM-633 URL: http://jira.codehaus.org/browse/MRM-633 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0 Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0.1 the default Archiva logging generates about 160Mb of logs a day on my reasonably inactive, not large local instance. This is primarily due to scanning. In addition, the logs are duplicated in the archiva.log and wrapper.log file. -- 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-633) Logging is too verbose
[ http://jira.codehaus.org/browse/MRM-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119120 ] Maria Odea Ching commented on MRM-633: -- I've identified a couple of logging points which probably needs to be changed: - revert the default log level for the repo scanner from debug to info. this could easily be switched to debug for debugging purposes, anyway. - remove this line logger.debug( Sending to consumer: + consumer.getId() ); from ConsumerProcessFileClosure since the consumer problem is logged when an error is encountered during processing. Logging is too verbose -- Key: MRM-633 URL: http://jira.codehaus.org/browse/MRM-633 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0 Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0.1 the default Archiva logging generates about 160Mb of logs a day on my reasonably inactive, not large local instance. This is primarily due to scanning. In addition, the logs are duplicated in the archiva.log and wrapper.log file. -- 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] Assigned: (MRM-628) In the audit.log file the userid for each action is guest, even though the deploy was performed by admin
[ http://jira.codehaus.org/browse/MRM-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching reassigned MRM-628: Assignee: Maria Odea Ching In the audit.log file the userid for each action is guest, even though the deploy was performed by admin Key: MRM-628 URL: http://jira.codehaus.org/browse/MRM-628 Project: Archiva Issue Type: Bug Affects Versions: 1.0 Environment: Windows XP Archiva 1.0 Reporter: Lisa Malgeri Assignee: Maria Odea Ching my settings.xml file has admin as the account in the server section for the repositories -- 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: (MRM-615) When scanning, Archiva doesn't resolve properties/variables of POMs in managed repositories
[
http://jira.codehaus.org/browse/MRM-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-615:
-
Fix Version/s: 1.1
When scanning, Archiva doesn't resolve properties/variables of POMs in
managed repositories
---
Key: MRM-615
URL: http://jira.codehaus.org/browse/MRM-615
Project: Archiva
Issue Type: Bug
Components: repository scanning
Affects Versions: 1.0
Reporter: Fabrice BELLINGARD
Priority: Critical
Fix For: 1.1
If you have a JAR with a POM that contains variables (like pom.version) or
properties, Archiva doesn't resolve them when scanning and analysing the
repository. Some of the multiple consequences are that the Dependencies tab
can list dependencies without real versions, and that the Dependency Tree
tabs can break with an exception Unable to generate graph for [XXX] : Unable
to create ArchivaArtifact with empty version.
A consequence of this bug can be seen by following these steps:
* install Archiva
* ask for the following artifact:
http://localhost:8080/archiva/repository/internal/org/apache/maven/archiva/archiva-model/1.0/archiva-model-1.0.jar
* then go to the page:
http://localhost:8080/archiva/browse/org.apache.maven.archiva/archiva-model/1.0/
** on the Dependencies tab: there's no version for the dependencies (which
is linked to the fact that the versions are defined in the parent POM, but if
${pom.version} would have been specified, we would have had
${pom.version}...}
** on the Dependency Tree, we get the Unable to generate graph for [XXX] :
Unable to create ArchivaArtifact with empty version exception
This bug breaks other functionalities like the Used by tab.
--
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: (MRM-634) moving proxy connectors up and down doesn't necessarily work
[ http://jira.codehaus.org/browse/MRM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-634: - Fix Version/s: 1.x moving proxy connectors up and down doesn't necessarily work - Key: MRM-634 URL: http://jira.codehaus.org/browse/MRM-634 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0 Reporter: Brett Porter Priority: Minor Fix For: 1.x I moved one at the bottom up, and it jumped to second position. Additionally, the up button should be disabled on the first one (and down on the last) -- 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: (MRM-649) Improve the Administration - Proxy Connectors view
[ http://jira.codehaus.org/browse/MRM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-649: - Fix Version/s: 1.x Improve the Administration - Proxy Connectors view Key: MRM-649 URL: http://jira.codehaus.org/browse/MRM-649 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0 Reporter: Trygve Laugstol Fix For: 1.x When clicking the expand button I would assume it to read collapse after I press it. Also, when pressing it it take around 5 seconds for it to actually collapse. Browser: opera 9.25 on os x. -- 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: (MRM-621) Use UTF-8 for better i18n support for page dispaly
[ http://jira.codehaus.org/browse/MRM-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-621: - Fix Version/s: 1.x Use UTF-8 for better i18n support for page dispaly -- Key: MRM-621 URL: http://jira.codehaus.org/browse/MRM-621 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0 Reporter: Ryan X.Wong Fix For: 1.x Current the web page use iso-8859-1 It result in some Chinese Characters display as ? Please help to deal with it. -- 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
