[jira] Updated: (MRM-130) improve search results page
[ http://jira.codehaus.org/browse/MRM-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-130: - Fix Version/s: (was: 1.1) 1.x improve search results page --- Key: MRM-130 URL: http://jira.codehaus.org/browse/MRM-130 Project: Archiva Issue Type: Improvement Components: web application Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.x Original Estimate: 3 hours Time Spent: 1 hour Remaining Estimate: 2 hours currently, the search results are very plain. We should: - provide more information about the artifact - provide more information about the relevance of the result - provide information about how the search hit occurred (what field) - paginate the results -- 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-135) integrate repository sync and conversion in the main application
[ http://jira.codehaus.org/browse/MRM-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-135: - Fix Version/s: (was: Future) 1.1 integrate repository sync and conversion in the main application Key: MRM-135 URL: http://jira.codehaus.org/browse/MRM-135 Project: Archiva Issue Type: New Feature Components: partner sync, repository converter, scheduling Reporter: Brett Porter 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-84) Basic statistics
[ http://jira.codehaus.org/browse/MRM-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-84: Fix Version/s: (was: 1.x) 1.1 Basic statistics Key: MRM-84 URL: http://jira.codehaus.org/browse/MRM-84 Project: Archiva Issue Type: Task Components: reporting Affects Versions: 1.0 Reporter: John Tolentino Fix For: 1.1 Original Estimate: 16 hours Remaining Estimate: 16 hours -- 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
]
Brett Porter updated MRM-629:
-
Fix Version/s: (was: 1.x)
1.1
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.1
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-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 ] Brett Porter updated MRM-604: - Fix Version/s: (was: 1.x) 1.1 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.1 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-684) Clients timeout due to Archiva blocking when downloading large files
[ http://jira.codehaus.org/browse/MRM-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-684: - Affects Version/s: (was: 1.1) Fix Version/s: 1.1 Clients timeout due to Archiva blocking when downloading large files Key: MRM-684 URL: http://jira.codehaus.org/browse/MRM-684 Project: Archiva Issue Type: Bug Components: WebDAV interface Affects Versions: 1.0, 1.0.1 Reporter: James William Dumay Assignee: James William Dumay Fix For: 1.1 Attachments: wagon-streaming.patch Clients connecting to Archiva may time out when Archiva is proxying large files from an up stream remote repository. Internally, Archiva uses Wagon and Plexus webdav which can only reference resources as JAVA File objects. Thus, Archiva must wait until Wagon has finished downloading from the remote repository before it can return the valid File object to the Plexus Webdav Servlet. -- 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-695) Database seems to be getting initialized twice -- the second time causing the Repositories page to take a long time to load on initial access
[ http://jira.codehaus.org/browse/MRM-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-695: - Fix Version/s: 1.1 Database seems to be getting initialized twice -- the second time causing the Repositories page to take a long time to load on initial access - Key: MRM-695 URL: http://jira.codehaus.org/browse/MRM-695 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0, 1.0.1 Reporter: Maria Odea Ching Fix For: 1.1 Attachments: archiva-database-initialization.logs The database seems to be initialized twice. The first one during startup and the second one when you initially access the Repositories page causing this page to take a long time to load . Please see attached logs. -- 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-652) Invalid html links in webdav directory browsing
[
http://jira.codehaus.org/browse/MRM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-652:
-
Fix Version/s: (was: 1.0.2)
1.0.x
Invalid html links in webdav directory browsing
-
Key: MRM-652
URL: http://jira.codehaus.org/browse/MRM-652
Project: Archiva
Issue Type: Bug
Components: WebDAV interface
Affects Versions: 1.0
Reporter: Xavier Hanin
Fix For: 1.0.x
The html page served by archiva in the webdav repository browsing contains
badly formed a href links. Here is an example of what I get at
http://localhost:8080/archiva/repository/internal/ant/ant/:
{code}
html
head
titleCollection: /ant/ant//title
/head
body
h2Collection: /ant/ant//h2
ul
lia href=../ant//a ismall(Parent)/small/i/li
/ul
ul
lia href=./1.6.2/1.6.2//li
lia href=./1.6.5/1.6.5//li
lia href=./1.6/1.6//li
/ul
/body
/html
{code}
As you can see the a elements referencing the available versions are not
closed.
--
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 ] Brett Porter updated MRM-656: - Fix Version/s: (was: 1.0.2) 1.0.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.0.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-592) For upgrade, assume that existing users have been verified (pre-beta-4)
[ http://jira.codehaus.org/browse/MRM-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-592: - Fix Version/s: (was: 1.1) 1.x For upgrade, assume that existing users have been verified (pre-beta-4) --- Key: MRM-592 URL: http://jira.codehaus.org/browse/MRM-592 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-4 Reporter: James William Dumay Fix For: 1.x Hey guys, Upgraded my Archiva instances to beta-4 from a beta-3 SNAPSHOT and noticed that none of the user accounts could be accessed because they had not been verified with the user via email. Can we assume when archiva is upgraded that all existing users have been verified in this case? -- 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-402) javadoc jar is listed as just jar in the download box
[ http://jira.codehaus.org/browse/MRM-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-402: - Fix Version/s: (was: 1.0.2) 1.0.x javadoc jar is listed as just jar in the download box - Key: MRM-402 URL: http://jira.codehaus.org/browse/MRM-402 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-alpha-1 Reporter: Brett Porter Priority: Minor Fix For: 1.0.x Attachments: archiva-bad-downloads-box.jpg go to an artifact that has an attached javadoc jar - you will notice that it is described as Jar, not Javadoc -- 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-391) Browse repository should display a suitable message when empty
[ http://jira.codehaus.org/browse/MRM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-391: - Fix Version/s: (was: 1.0.2) 1.0.x Browse repository should display a suitable message when empty -- Key: MRM-391 URL: http://jira.codehaus.org/browse/MRM-391 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Brett Porter Priority: Minor Fix For: 1.0.x When the configured repositories are empty, the browse page simply lists nothing. A suitable message indicating that no repositories are configured, or are not indexed, or whatever is necessary should be displayed instead. -- 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-639) 1.0 in the breadcrumbs is incorrectly linked to /docs/1.0/docs/1.0 in the docs subsite
[ http://jira.codehaus.org/browse/MRM-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-639: - Fix Version/s: (was: 1.0.2) 1.0.x 1.0 in the breadcrumbs is incorrectly linked to /docs/1.0/docs/1.0 in the docs subsite Key: MRM-639 URL: http://jira.codehaus.org/browse/MRM-639 Project: Archiva Issue Type: Bug Components: documentation Affects Versions: 1.0 Reporter: Brett Porter Fix For: 1.0.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-448) validation for reports form
[ http://jira.codehaus.org/browse/MRM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-448: - Fix Version/s: (was: 1.0.2) 1.0.x 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.x 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-367) [Admin / Repositories] the consumers need to identify and highlight Permanent / Mandatory consumers better.
[ http://jira.codehaus.org/browse/MRM-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-367: - Fix Version/s: (was: 1.0.2) 1.0.x [Admin / Repositories] the consumers need to identify and highlight Permanent / Mandatory consumers better. --- Key: MRM-367 URL: http://jira.codehaus.org/browse/MRM-367 Project: Archiva Issue Type: Bug Components: design Affects Versions: 1.0-alpha-1 Reporter: Joakim Erdfelt Fix For: 1.0.x Some consumers are flagged (on the compile time side) as permanent (aka mandatory) and cannot be disabled. The UI screens need to show this concept to the users. -- 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
