[jira] Closed: (MRM-742) Add date column in the
[ http://jira.codehaus.org/browse/MRM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Baptiste MATHUS closed MRM-742. --- Resolution: Duplicate Add date column in the -- Key: MRM-742 URL: http://jira.codehaus.org/browse/MRM-742 Project: Archiva Issue Type: Improvement Components: repository interface Affects Versions: 1.0 Reporter: Baptiste MATHUS When manually browsing the repositories, a date column should be added. I guess this should be a good idea to get closer to the interface provided by http://repo1.maven.org/maven2/ for example. At the moment, there's only a list of the available artifacts. Thanks a lot. -- 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] 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_127895 ] Wendy Smoak commented on MRM-677: - The issue summary says Redback 1.0, but the fix was to upgrade to 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-680) User database cannot be used with MySQL 4.1
[ http://jira.codehaus.org/browse/MRM-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-680: Summary: User database cannot be used with MySQL 4.1 (was: User database cannot be used with MySQL) Editing the summary to say MySQL 4.1, as we're successfully using it with MySQL 5.0. User database cannot be used with MySQL 4.1 --- Key: MRM-680 URL: http://jira.codehaus.org/browse/MRM-680 Project: Archiva Issue Type: Bug Components: Users/Security Affects Versions: 1.0.1 Environment: SunOS 5.8, JDK 1.5.0_06, MySQL 4.1.21 Reporter: Dennis Kieselhorst Fix For: 1.0.x Changed database configuration in plexus.xml to MySQL. It works for the resource jdbc/archiva but not for the jdbc/users resource: 11587 [WrapperSimpleAppMain] ERROR JPOX.RDBMS - Error thrown executing CREATE TABLE `SECURITY_OPERATIONS` ( `NAME` VARCHAR(256) BINARY NOT NULL, `DESCRIPTION` VARCHAR(256) BINARY NULL, `PERMANENT` BIT NOT NULL, `RESOURCE_REQUIRED` BIT NOT NULL, PRIMARY KEY (`NAME`) ) TYPE=INNODB : BLOB/TEXT column 'NAME' used in key specification without a key length com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: BLOB/TEXT column 'NAME' used in key specification without a key length at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1027) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:957) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3376) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3308) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1837) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1961) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2537) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2466) at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:735) at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:261) at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:614) at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:570) at org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:297) at org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:341) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(RDBMSManager.java:3065) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3326) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2567) at org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2419) at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:824) at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:838) at org.jpox.store.StoreManager.getDatastoreClass(StoreManager.java:1218) at org.jpox.store.rdbms.RDBMSManager.getExtent(RDBMSManager.java:1357) at org.jpox.AbstractPersistenceManager.getExtent(AbstractPersistenceManager.java:2328) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.getAllObjects(JdoTool.java:205) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.getAllObjects(JdoTool.java:188) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.triggerInit(JdoTool.java:131) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.getPersistenceManager(JdoTool.java:118) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.getObjectById(JdoTool.java:292) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.objectExistsById(JdoTool.java:340) at org.codehaus.plexus.redback.rbac.jdo.JdoRbacManager.resourceExists(JdoRbacManager.java:467) at org.codehaus.plexus.redback.rbac.cached.CachedRbacManager.resourceExists(CachedRbacManager.java:622) at org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.processResources(DefaultRoleModelProcessor.java:77) at org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.process(DefaultRoleModelProcessor.java:63) at org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(DefaultRoleManager.java:210) at org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(DefaultRoleManager.java:132) at org.codehaus.plexus.redback.role.DefaultRoleManager.initialize(DefaultRoleManager.java:457) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:128) at
[jira] Closed: (MRM-701) Buggy documentation on separating the base from the installation
[ http://jira.codehaus.org/browse/MRM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-701. Assignee: Brett Porter Resolution: Fixed applied, thanks. I left out step 4 since that will be fixed by MRM-618 Buggy documentation on separating the base from the installation -- Key: MRM-701 URL: http://jira.codehaus.org/browse/MRM-701 Project: Archiva Issue Type: Bug Components: documentation Affects Versions: 1.0.1 Reporter: Martin Höller Assignee: Brett Porter Priority: Minor Fix For: 1.0.2 The documentation on http://maven.apache.org/archiva/docs/1.0.1/adminguide/standalone.html says in Separating the base from the installation 2. Move the conf and data directories from the Archiva installation to the new location. But there is no data directory in a fresh installation. -- 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-746) unable to include *.xml in artifacts list as it picks up maven-metadata.xml
unable to include *.xml in artifacts list as it picks up maven-metadata.xml --- Key: MRM-746 URL: http://jira.codehaus.org/browse/MRM-746 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0.1 Reporter: Brett Porter Fix For: 1.0.2 metadata should be explicitly removed from the artifact consumers list -- 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-746) unable to include *.xml in artifacts list as it picks up maven-metadata.xml
[ http://jira.codehaus.org/browse/MRM-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127957 ] Wendy Smoak commented on MRM-746: - Try to exclude things like maven-metadata-central.xml that really shouldn't be in a remote repo, but sometimes are. unable to include *.xml in artifacts list as it picks up maven-metadata.xml --- Key: MRM-746 URL: http://jira.codehaus.org/browse/MRM-746 Project: Archiva Issue Type: Bug Components: repository scanning Affects Versions: 1.0.1 Reporter: Brett Porter Fix For: 1.0.2 metadata should be explicitly removed from the artifact consumers list -- 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 in Geronimo
[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-727: - Summary: Archiva does not download plugin artifacts in Geronimo (was: Archiva does not download plugin artifacts) Archiva does not download plugin artifacts in Geronimo -- 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.x 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-627) Archiva doesn't download SNAPSHOTs for proxied repositories.
[ http://jira.codehaus.org/browse/MRM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127958 ] Brett Porter commented on MRM-627: -- this would likely be a problem only with non-unique versioned snapshots. Will test. Archiva doesn't download SNAPSHOTs for proxied repositories. Key: MRM-627 URL: http://jira.codehaus.org/browse/MRM-627 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0 Environment: Linux, JDK 1.5, Reporter: gumnaam Fix For: 1.0.2 I have setup Archiva Managed Internal Repository as my whole and sole mirror in my settings.xml. The settings.xml does not contain any other repository information, just the mirror entry . The Archiva Manged Internal Repository is set to proxy 4/5 external repositories, One of which contains certain SNAPSHOTs that I have as dependencies. The proxy connector for this repository has snapshot policy set to always, I also tried daily, hourly. But the SNAPSHOT is never downloaded any my build fails. The log file shows no special activity. Also I am including the link to the thread on user-list http://www.nabble.com/Proxying-SNAPSHOT-repositories-td14336170.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-627) Archiva doesn't download SNAPSHOTs for proxied repositories.
[ http://jira.codehaus.org/browse/MRM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reassigned MRM-627: Assignee: Brett Porter Archiva doesn't download SNAPSHOTs for proxied repositories. Key: MRM-627 URL: http://jira.codehaus.org/browse/MRM-627 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0 Environment: Linux, JDK 1.5, Reporter: gumnaam Assignee: Brett Porter Fix For: 1.0.2 I have setup Archiva Managed Internal Repository as my whole and sole mirror in my settings.xml. The settings.xml does not contain any other repository information, just the mirror entry . The Archiva Manged Internal Repository is set to proxy 4/5 external repositories, One of which contains certain SNAPSHOTs that I have as dependencies. The proxy connector for this repository has snapshot policy set to always, I also tried daily, hourly. But the SNAPSHOT is never downloaded any my build fails. The log file shows no special activity. Also I am including the link to the thread on user-list http://www.nabble.com/Proxying-SNAPSHOT-repositories-td14336170.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
