[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 (IndexArchiv

[jira] Created: (MRM-730) Index/Search by class, method or package name

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 Reporte

[jira] Commented: (MRM-728) After successful admin login archiva reacts as if user is guest

[ http://jira.codehaus.org/browse/MRM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126265 ] Arun Nachimuthu commented on MRM-728: - I am facing exactly the same issue. Archiva 1.0.1 on Tomcat 6.x RedHat Linux. Onc

[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

[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.

[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_126215 ] Christian Domsch commented on MRM-727: -- As far as I found out, part of the problem seems to be a classloading issue with g

[jira] Updated: (MRM-724) Unable to restart Archiva after restarting Tomcat : "SQL Exception: Failed to start database"

[ http://jira.codehaus.org/browse/MRM-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-724: - Fix Version/s: 1.0.x > Unable to restart Archiva after restarting Tomcat : "SQL Exception: Failed to > start data

[jira] Updated: (MRM-729) [MySQL] Specified key was too long; max key length is 765 bytes - in redback

[ http://jira.codehaus.org/browse/MRM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-729: - Fix Version/s: 1.0.x > [MySQL] Specified key was too long; max key length is 765 bytes - in redback >

[jira] Updated: (MRM-725) /archiva/browse URL does not work on WebSphere

[ http://jira.codehaus.org/browse/MRM-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-725: - Fix Version/s: 1.0.x > /archiva/browse URL does not work on WebSphere > --

[jira] Updated: (MRM-726) snapshot artifacts in maven1 repo with legacy timestamps not being cleaned

[ http://jira.codehaus.org/browse/MRM-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-726: - Fix Version/s: 1.0.x > snapshot artifacts in maven1 repo with legacy timestamps not being cleaned > --

[jira] Updated: (MRM-728) After successful admin login archiva reacts as if user is guest

[ http://jira.codehaus.org/browse/MRM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-728: - Fix Version/s: 1.0.x > After successful admin login archiva reacts as if user is guest > -

[jira] Commented: (MRM-728) After successful admin login archiva reacts as if user is guest

[ http://jira.codehaus.org/browse/MRM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126172 ] Brett Porter commented on MRM-728: -- There are two things to investigate: - was there anything in the logs or anything additiona

[jira] Commented: (MRM-729) CLONE -[MySQL] Specified key was too long; max key length is 765 bytes

[ http://jira.codehaus.org/browse/MRM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126148 ] Arnaud Heritier commented on MRM-729: - The problem seems to be in rednack and no more in archiva itself. Fixing the applica

[jira] Updated: (MRM-729) [MySQL] Specified key was too long; max key length is 765 bytes - in redback

[ http://jira.codehaus.org/browse/MRM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MRM-729: Summary: [MySQL] Specified key was too long; max key length is 765 bytes - in redback (was: CLONE -[MySQL]

[jira] Updated: (MRM-729) CLONE -[MySQL] Specified key was too long; max key length is 765 bytes

[ http://jira.codehaus.org/browse/MRM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MRM-729: Attachment: wrapper.txt Wrapper logs > CLONE -[MySQL] Specified key was too long; max key length is 765 byt

[jira] Updated: (MRM-729) CLONE -[MySQL] Specified key was too long; max key length is 765 bytes

[ http://jira.codehaus.org/browse/MRM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MRM-729: Assignee: (was: Joakim Erdfelt) Reporter: Arnaud Heritier (was: Joakim Erdfelt)

[jira] Created: (MRM-729) CLONE -[MySQL] Specified key was too long; max key length is 765 bytes

CLONE -[MySQL] Specified key was too long; max key length is 765 bytes -- Key: MRM-729 URL: http://jira.codehaus.org/browse/MRM-729 Project: Archiva Issue Type: Bug

[jira] Updated: (MRM-657) 'ORA-00910: specified length too long for its datatype' Error when clicking on searched artifact.

[ http://jira.codehaus.org/browse/MRM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gunther Van den Bosch updated MRM-657: -- Attachment: package-oracle.orm > 'ORA-00910: specified length too long for its datatype' Error w

[jira] Commented: (MRM-657) 'ORA-00910: specified length too long for its datatype' Error when clicking on searched artifact.

[ http://jira.codehaus.org/browse/MRM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126122 ] Gunther Van den Bosch commented on MRM-657: --- This could be solved by adapting the JDO mapping for Oracle. Oracle suppo

[jira] Created: (MRM-728) After successful admin login archiva reacts as if user is guest

After successful admin login archiva reacts as if user is guest --- Key: MRM-728 URL: http://jira.codehaus.org/browse/MRM-728 Project: Archiva Issue Type: Bug Affects Versions:

[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.xm

[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 >