RE: archiva-1.0.2 eta?
I can probably change that to be more specific to only pick up the specific xml files. This might fix my build number issue as well. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:42 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? On 20/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > I just sent my archiva.xml, which should give you a complete picture. Ok, so I will file a new issue, but removing *.xml from your artifacts list temporarily will fix the exception problems you were having with the latest code (since it's picking up metadata files). As for the wrong build numbers, you were probably seeing this: http://jira.codehaus.org/browse/MNG-3441 Cheers, Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: archiva-1.0.2 eta?
On 20/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > I just sent my archiva.xml, which should give you a complete picture. Ok, so I will file a new issue, but removing *.xml from your artifacts list temporarily will fix the exception problems you were having with the latest code (since it's picking up metadata files). As for the wrong build numbers, you were probably seeing this: http://jira.codehaus.org/browse/MNG-3441 Cheers, Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
I just sent my archiva.xml, which should give you a complete picture. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:33 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Thanks. Do you have maven-metadata.xml or *.xml in the "artifacts" list at the top of that page? - Brett On 20/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Currently, I have the following enbled: > > > > * create-missing-checksums > > * index-content > > * repository-purge > > * repository-purge > > * validate-checksums > > > > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 19, 2008 9:24 PM > To: archiva-users@maven.apache.org > > Subject: Re: archiva-1.0.2 eta? > > > > Jason, > > > > I took a look at this - the only way I could reproduce it was by > > adding maven-metadata.xml to the list of artifacts in the "repository > > scanning" tab - can you confirm whether that is the case for you? > > > > Cheers, > > Brett > > > > On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > > > Here is a snippet from the log file: > > > > > > 431177909 [pool-2-thread-1] ERROR > > > > > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default > - > > > Consumer [repository-purge] had an error when processing file > > > > > > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > > > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
Here is my archiva.xml, in case it provides any other info. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:33 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? I was using the metdata-updater at one time, but we started to see stange issues with the buld number being reset when we do a deploy, even though the build number should have been 35, it became 1. I thought this consumer might be the cause. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:29 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? Currently, I have the following enbled: * create-missing-checksums * index-content * repository-purge * repository-purge * validate-checksums -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:24 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Jason, I took a look at this - the only way I could reproduce it was by adding maven-metadata.xml to the list of artifacts in the "repository scanning" tab - can you confirm whether that is the case for you? Cheers, Brett On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Here is a snippet from the log file: > > 431177909 [pool-2-thread-1] ERROR > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - > Consumer [repository-purge] had an error when processing file > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > -- Brett Porter Blog: http://blogs.exist.com/bporter/ 2 artifacts **/*.bin **/*.car **/*.dtd **/*.ear **/*.jar **/*.mar **/*.nar **/*.pom **/*.rar **/*.rpm **/*.sar **/*.tar.bz2 **/*.tar.gz **/*.tld **/*.war **/*.xml **/*.zip auto-remove **/*- **/*.bak **/*~ ignored **/*.rb **/*.sh **/.DAV/** **/.htaccess **/.svn/** **/KEYS indexable-content **/*.block **/*.config **/*.dtd **/*.pom **/*.tld **/*.txt **/*.TXT **/*.xml **/*.xsd create-missing-checksums index-content repository-purge update-db-artifact validate-checksums update-db-bad-content 0 15 * * * ? index-archive-toc index-artifact index-public-methods update-db-bytecode-stats update-db-project validate-repository-metadata not-present-remove-db-artifact not-present-remove-db-project not-present-remove-indexed /disk1/html/maven2-client true 0 0 4 * * ? 0 true tva.client TVA Client Repository /disk1/html/maven2 0 0 3 * * ? 20 tva.release TVA Release Repository /disk1/html/maven2-snapshot true 0 30 * * * ? 10 0 true tva.snapshot TVA Snapshot Repository /proxy/maven2 true 0 10 * * * ? 0 true tva.proxy TVA Proxy Repository http://repo1.maven.org/maven2 central Central Repository http://download.java.net/maven/2/ maven2-repository.dev.java.net Java.net Repository for Maven 2 http://people.apache.org/repo/m2-incubating-repository/ apache.incubating Apache Incubating Repository http://people.apache.org/repo/m2-snapshot-repository/ apache.snapshot Apache Snapshot Repository http://repository.codehaus.org/ codehaus Codehaus Repository http://snapshots.repository.codehaus.org/ codehaus.snapshot Codehaus Snapshot Repository http://java.freehep.org/maven2/ freehep FreeHEP Maven Repository http://download.java.net/maven/1/ maven1-repository.dev.java.net Java.net Maven 1 Repository legacy http://repository.jboss.com/maven2/ jboss JBoss Repository 1 tva.proxy central (direct connection) always never fix no 2 tva.proxy maven1-repository.dev.java.net (direct connection) always fix never no
RE: archiva-1.0.2 eta?
Here is my archiva.xml, in case it provides any other info. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:33 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? I was using the metdata-updater at one time, but we started to see stange issues with the buld number being reset when we do a deploy, even though the build number should have been 35, it became 1. I thought this consumer might be the cause. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:29 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? Currently, I have the following enbled: * create-missing-checksums * index-content * repository-purge * repository-purge * validate-checksums -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:24 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Jason, I took a look at this - the only way I could reproduce it was by adding maven-metadata.xml to the list of artifacts in the "repository scanning" tab - can you confirm whether that is the case for you? Cheers, Brett On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Here is a snippet from the log file: > > 431177909 [pool-2-thread-1] ERROR > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - > Consumer [repository-purge] had an error when processing file > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > -- Brett Porter Blog: http://blogs.exist.com/bporter/ 2 artifacts **/*.bin **/*.car **/*.dtd **/*.ear **/*.jar **/*.mar **/*.nar **/*.pom **/*.rar **/*.rpm **/*.sar **/*.tar.bz2 **/*.tar.gz **/*.tld **/*.war **/*.xml **/*.zip auto-remove **/*- **/*.bak **/*~ ignored **/*.rb **/*.sh **/.DAV/** **/.htaccess **/.svn/** **/KEYS indexable-content **/*.block **/*.config **/*.dtd **/*.pom **/*.tld **/*.txt **/*.TXT **/*.xml **/*.xsd create-missing-checksums index-content repository-purge update-db-artifact validate-checksums update-db-bad-content 0 15 * * * ? index-archive-toc index-artifact index-public-methods update-db-bytecode-stats update-db-project validate-repository-metadata not-present-remove-db-artifact not-present-remove-db-project not-present-remove-indexed /disk1/html/maven2-client true 0 0 4 * * ? 0 true tva.client TVA Client Repository /disk1/html/maven2 0 0 3 * * ? 20 tva.release TVA Release Repository /disk1/html/maven2-snapshot true 0 30 * * * ? 10 0 true tva.snapshot TVA Snapshot Repository /proxy/maven2 true 0 10 * * * ? 0 true tva.proxy TVA Proxy Repository http://repo1.maven.org/maven2 central Central Repository http://download.java.net/maven/2/ maven2-repository.dev.java.net Java.net Repository for Maven 2 http://people.apache.org/repo/m2-incubating-repository/ apache.incubating Apache Incubating Repository http://people.apache.org/repo/m2-snapshot-repository/ apache.snapshot Apache Snapshot Repository http://repository.codehaus.org/ codehaus Codehaus Repository http://snapshots.repository.codehaus.org/ codehaus.snapshot Codehaus Snapshot Repository http://java.freehep.org/maven2/ freehep FreeHEP Maven Repository http://download.java.net/maven/1/ maven1-repository.dev.java.net Java.net Maven 1 Repository legacy http://repository.jboss.com/maven2/ jboss JBoss Repository 1 tva.proxy central (direct connection) always never fix no 2 tva.proxy maven1-repository.dev.java.net (direct connection) always fix never no
Re: archiva-1.0.2 eta?
Thanks. Do you have maven-metadata.xml or *.xml in the "artifacts" list at the top of that page? - Brett On 20/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Currently, I have the following enbled: > > > > * create-missing-checksums > > * index-content > > * repository-purge > > * repository-purge > > * validate-checksums > > > > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 19, 2008 9:24 PM > To: archiva-users@maven.apache.org > > Subject: Re: archiva-1.0.2 eta? > > > > Jason, > > > > I took a look at this - the only way I could reproduce it was by > > adding maven-metadata.xml to the list of artifacts in the "repository > > scanning" tab - can you confirm whether that is the case for you? > > > > Cheers, > > Brett > > > > On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > > > Here is a snippet from the log file: > > > > > > 431177909 [pool-2-thread-1] ERROR > > > > > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default > - > > > Consumer [repository-purge] had an error when processing file > > > > > > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > > > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
I was using the metdata-updater at one time, but we started to see stange issues with the buld number being reset when we do a deploy, even though the build number should have been 35, it became 1. I thought this consumer might be the cause. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:29 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? Currently, I have the following enbled: * create-missing-checksums * index-content * repository-purge * repository-purge * validate-checksums -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:24 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Jason, I took a look at this - the only way I could reproduce it was by adding maven-metadata.xml to the list of artifacts in the "repository scanning" tab - can you confirm whether that is the case for you? Cheers, Brett On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Here is a snippet from the log file: > > 431177909 [pool-2-thread-1] ERROR > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - > Consumer [repository-purge] had an error when processing file > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
Currently, I have the following enbled: * create-missing-checksums * index-content * repository-purge * repository-purge * validate-checksums -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:24 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Jason, I took a look at this - the only way I could reproduce it was by adding maven-metadata.xml to the list of artifacts in the "repository scanning" tab - can you confirm whether that is the case for you? Cheers, Brett On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Here is a snippet from the log file: > > 431177909 [pool-2-thread-1] ERROR > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - > Consumer [repository-purge] had an error when processing file > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: archiva-1.0.2 eta?
Jason, I took a look at this - the only way I could reproduce it was by adding maven-metadata.xml to the list of artifacts in the "repository scanning" tab - can you confirm whether that is the case for you? Cheers, Brett On 14/03/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Here is a snippet from the log file: > > 431177909 [pool-2-thread-1] ERROR > > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - > Consumer [repository-purge] had an error when processing file > > [/proxy/maven2/org/apache/cxf/cxf-rt-bindings-soap/2.0.3-incubator/maven > -metadata.xml]: Invalid path to Artifact: filename format is invalid, > -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: archiva and nexus indexer
> After a quick look with Luke, it appears the format is the same as it > has always been, with a couple of additions that appear to be unused > on the central repository. So the old code from Archiva 0.9 could just > be re-added to serve this. Great news ! Thanks
Re: JDO dialect from Mysql ?
this seems to be the following issue: http://jira.codehaus.org/browse/MRM-680 On 19/03/2008, Lustig, Marc (Allianz Deutschland AG) <[EMAIL PROTECTED]> wrote: > We are using Mysql (4.1, Connector-j 5.1.6) as database for archiva > 1.0.1 running on JBoss on the same linux box. > On startup, Mysql complains about bad syntax: > > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: BLOB/TEXT > column 'IDENTIFIER' used in key specification without a key length > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA > ccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons > tructorAccessorImpl.java:27) > at > java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) > at com.mysql.jdbc.Util.getInstance(Util.java:381) > at > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030) > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) > at > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2536) > at > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:734) > at > org.jboss.resource.adapter.jdbc.WrappedStatement.execute(WrappedStatemen > t.java:84) > at > org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTab > le.java:614) > at > org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(Abstrac > tTable.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(RDB > MSManager.java:3065) > at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(R > DBMSManager.java:3326) > at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2567) > at > org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.j > ava: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:13 > 1) > at > org.codehaus.plexus.redback.rbac.jdo.JdoTool.getPersistenceManager(JdoTo > ol.java:118) > at > org.codehaus.plexus.redback.rbac.jdo.JdoTool.getObjectById(JdoTool.java: > 292) > at > org.codehaus.plexus.redback.rbac.jdo.JdoTool.objectExistsById(JdoTool.ja > va:340) > at > org.codehaus.plexus.redback.rbac.jdo.JdoRbacManager.resourceExists(JdoRb > acManager.java:467) > at > org.codehaus.plexus.redback.rbac.cached.CachedRbacManager.resourceExists > (CachedRbacManager.java:622) > at > org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.pro > cessResources(DefaultRoleModelProcessor.java:77) > at > org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.pro > cess(DefaultRoleModelProcessor.java:63) > at > org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(Defaul > tRoleManager.java:210) > at > org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(Defaul > tRoleManager.java:132) > > > Does this JDO implementation (jpox) need some dialect configured, like > Hibernate? > -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: archiva and nexus indexer
On 19/03/2008, Brett Porter <[EMAIL PROTECTED]> wrote: > Assuming it's a Lucene index, it should be straightforward to create > this format - we actually previously had in place a generator for very > old versions of m2eclipse. I haven't looked at the index myself. After a quick look with Luke, it appears the format is the same as it has always been, with a couple of additions that appear to be unused on the central repository. So the old code from Archiva 0.9 could just be re-added to serve this. Cheers, Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/
JDO dialect from Mysql ?
We are using Mysql (4.1, Connector-j 5.1.6) as database for archiva 1.0.1 running on JBoss on the same linux box. On startup, Mysql complains about bad syntax: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: BLOB/TEXT column 'IDENTIFIER' used in key specification without a key length at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA ccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons tructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.Util.getInstance(Util.java:381) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2536) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465) at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:734) at org.jboss.resource.adapter.jdbc.WrappedStatement.execute(WrappedStatemen t.java:84) at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTab le.java:614) at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(Abstrac tTable.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(RDB MSManager.java:3065) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(R DBMSManager.java:3326) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2567) at org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.j ava: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:13 1) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.getPersistenceManager(JdoTo ol.java:118) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.getObjectById(JdoTool.java: 292) at org.codehaus.plexus.redback.rbac.jdo.JdoTool.objectExistsById(JdoTool.ja va:340) at org.codehaus.plexus.redback.rbac.jdo.JdoRbacManager.resourceExists(JdoRb acManager.java:467) at org.codehaus.plexus.redback.rbac.cached.CachedRbacManager.resourceExists (CachedRbacManager.java:622) at org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.pro cessResources(DefaultRoleModelProcessor.java:77) at org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.pro cess(DefaultRoleModelProcessor.java:63) at org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(Defaul tRoleManager.java:210) at org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(Defaul tRoleManager.java:132) Does this JDO implementation (jpox) need some dialect configured, like Hibernate?
Re: archiva and nexus indexer
On 19/03/2008, Henri Gomez <[EMAIL PROTECTED]> wrote: > > I've asked about the format of the nexus index but haven't received a > > response. Archiva stores in what is likely a similar format, but it is > > not used by m2eclipse. > > > What about adding some nexusindexer task in archiva own tasks ? Assuming it's a Lucene index, it should be straightforward to create this format - we actually previously had in place a generator for very old versions of m2eclipse. I haven't looked at the index myself. Cheers, Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: Archiva with network drives
Here is the Java issue, related to URI.normalize() : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4723726 state " In progress," since jully 2002 ;-) 2008/3/19, nicolas de loof <[EMAIL PROTECTED]>: > > Java has poor support for windows UNC (samba) fiel storage. > > I myself tried to store my managed repository on \\myserver\mybackup but > the WebDav support fails due to call to Java File.normalize() method. This > is a known java limitation (I don't have the java bug Id but it is reported > for long time and never fixed). > > An option (not tested) would be to "mount" the network share as a drive > (as "X:"). I didn't tried this myself as it was simplier for me to configure > my backup ! > > Nico. > > 2008/3/19, PascalTrema <[EMAIL PROTECTED]>: > > > > > > Archiva > > > > Windows XP, Tomcat 6.0 > > > > I have archiva under tomcat, and to secure my data, directories for each > > repository are on networks hard disks . > > That's pretty good > > > > On Windows 2003 server, tomcat 6.0 > > When I do the same operation, I have the following error when I click on > > WebDAV URL > > Etat HTTP 404 - [enterprise-releases] Not Found (Likely Unconfigured). > > > > type Rapport d'état > > > > message [enterprise-releases] Not Found (Likely Unconfigured). > > > > description La ressource demandée ([enterprise-releases] Not Found > > (Likely > > Unconfigured).) n'est pas disponible. > > Apache Tomcat/6.0.14 > > > > is a probleme with 2003 server or > > > > -- > > View this message in context: > > http://www.nabble.com/Archiva-with-network-drives-tp16141644p16141644.html > > Sent from the archiva-users mailing list archive at Nabble.com. > > > > >
Re: archiva and nexus indexer
I've asked about the format of the nexus index but haven't received a response. Archiva stores in what is likely a similar format, but it is not used by m2eclipse. Other integrations such as MevenIDE (Netbeans) and q4e are making pluggable implementations for repository manager indexes so that they can support any implementation. Cheers, Brett On 19/03/2008, Henri Gomez <[EMAIL PROTECTED]> wrote: > Hi to all, > > Did there is a way to use Nexus Indexer > (http://docs.codehaus.org/display/M2ECLIPSE/Nexus+indexer) with > Archiva ? > > I may use the nexusindexer cli from a batch job but the regular > location in under repourl/.index where achiva allreay story its own > informations. > > Regards > -- Brett Porter Blog: http://blogs.exist.com/bporter/
archiva and nexus indexer
Hi to all, Did there is a way to use Nexus Indexer (http://docs.codehaus.org/display/M2ECLIPSE/Nexus+indexer) with Archiva ? I may use the nexusindexer cli from a batch job but the regular location in under repourl/.index where achiva allreay story its own informations. Regards
Archiva with network drives
Archiva Windows XP, Tomcat 6.0 I have archiva under tomcat, and to secure my data, directories for each repository are on networks hard disks . That's pretty good On Windows 2003 server, tomcat 6.0 When I do the same operation, I have the following error when I click on WebDAV URL Etat HTTP 404 - [enterprise-releases] Not Found (Likely Unconfigured). type Rapport d'état message [enterprise-releases] Not Found (Likely Unconfigured). description La ressource demandée ([enterprise-releases] Not Found (Likely Unconfigured).) n'est pas disponible. Apache Tomcat/6.0.14 is a probleme with 2003 server or -- View this message in context: http://www.nabble.com/Archiva-with-network-drives-tp16141644p16141644.html Sent from the archiva-users mailing list archive at Nabble.com.
