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?
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/ ?xml version=1.0 encoding=UTF-8? configuration version2/version repositoryScanning fileTypes fileType idartifacts/id patterns pattern**/*.bin/pattern pattern**/*.car/pattern pattern**/*.dtd/pattern pattern**/*.ear/pattern pattern**/*.jar/pattern pattern**/*.mar/pattern pattern**/*.nar/pattern pattern**/*.pom/pattern pattern**/*.rar/pattern pattern**/*.rpm/pattern pattern**/*.sar/pattern pattern**/*.tar.bz2/pattern pattern**/*.tar.gz/pattern pattern**/*.tld/pattern pattern**/*.war/pattern pattern**/*.xml/pattern pattern**/*.zip/pattern /patterns /fileType fileType idauto-remove/id patterns pattern**/*-/pattern pattern**/*.bak/pattern pattern**/*~/pattern /patterns /fileType fileType idignored/id patterns pattern**/*.rb/pattern pattern**/*.sh/pattern pattern**/.DAV/**/pattern pattern**/.htaccess/pattern pattern**/.svn/**/pattern pattern**/KEYS/pattern /patterns /fileType fileType idindexable-content/id patterns pattern**/*.block/pattern pattern**/*.config/pattern pattern**/*.dtd/pattern pattern**/*.pom/pattern pattern**/*.tld/pattern pattern**/*.txt/pattern pattern**/*.TXT/pattern pattern**/*.xml/pattern pattern**/*.xsd/pattern /patterns /fileType /fileTypes knownContentConsumers knownContentConsumercreate-missing-checksums/knownContentConsumer knownContentConsumerindex-content/knownContentConsumer knownContentConsumerrepository-purge/knownContentConsumer knownContentConsumerupdate-db-artifact/knownContentConsumer knownContentConsumervalidate-checksums/knownContentConsumer /knownContentConsumers invalidContentConsumers invalidContentConsumerupdate-db-bad-content/invalidContentConsumer /invalidContentConsumers /repositoryScanning databaseScanning cronExpression0 15 * * * ?/cronExpression unprocessedConsumers unprocessedConsumerindex-archive-toc/unprocessedConsumer unprocessedConsumerindex-artifact/unprocessedConsumer unprocessedConsumerindex-public-methods/unprocessedConsumer unprocessedConsumerupdate-db-bytecode-stats/unprocessedConsumer unprocessedConsumerupdate-db-project/unprocessedConsumer unprocessedConsumervalidate-repository-metadata/unprocessedConsumer /unprocessedConsumers cleanupConsumers cleanupConsumernot-present-remove-db-artifact/cleanupConsumer cleanupConsumernot-present-remove-db-project/cleanupConsumer cleanupConsumernot-present-remove-indexed/cleanupConsumer /cleanupConsumers /databaseScanning managedRepositories managedRepository location/disk1/html/maven2-client/location snapshotstrue/snapshots refreshCronExpression0 0 4 * * ?/refreshCronExpression daysOlder0/daysOlder
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 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?
Brett Porter wrote: If you are able to, please test the following build: http://people.apache.org/~brett/builds/apache-archiva-1.0.2-SNAPSHOT-bin.zip (please note this is not an official release) If there is going to be a 1.0.2, then I beg to reconsider closing http://jira.codehaus.org/browse/MRM-618 as WONTFIX. It is a serious problem for any upgrade. Jochen -- View this message in context: http://www.nabble.com/archiva-1.0.2-eta--tp15643198p16046685.html Sent from the archiva-users mailing list archive at Nabble.com.
Re: archiva-1.0.2 eta?
On 14/03/2008, greyfairer1 [EMAIL PROTECTED] wrote: I just cloned the issue as MRM-738, but it's still reported as duplicate of MRM-674, which it is not IMHO. See comments on MRM-738. This problem occurred at an important client of mine, so I'm not eager to install any snapshot versions there, if I'm not sure the problem is fixed. Ok, I've updated the issue. I think your first issue has already been addressed, but I'll look at the second. - Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
I will send the log output later tonight. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 4:42 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? What is the error you are getting? I tried the one you previously posted to the list and it ran through the unit tests on the branch just fine. - Brett On 14/03/2008, Jason Chaffee [EMAIL PROTECTED] wrote: I am using the SNAPSHOT that Brett provided, and MRM-691 seems to be fixed, but not MRM-632 as I am still seeing that for some artifacts. -Original Message- From: greyfairer1 [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 9:20 AM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? So, apart from the log file issues, are MR-632 and MRM-691 fixed in the 1.02-SNAPSHOT release? Or should I build archiva from trunk to check? Brett Porter wrote: Are these issues new, or were they present before (just wondering if it's a regression because of my changes). Anyway, I can add more tests. How is the performance/stability after a little while now? - Brett On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Looks like I still have some issues. I have attached parts of the log file because the entire file is too large. Let me know if you would like any other information. I am using the same archiva.xml as before. These errors may be due to some non-standard artifacts in our repo, but most of them do seem correct to me. I do know that we have some artifacts that do not have poms though. -- View this message in context: http://www.nabble.com/archiva-1.0.2-eta--tp15643198p16030511.html Sent from the archiva-users mailing list archive at Nabble.com. -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
Thanks Joakim. I already found it changed it locally. I also modified
the logging for the wrapper.conf.
I might suggest changing the default that ships OR at least providing
some good documentation around this issue and how to configure the
logging in both log4j.xml and the wrapper.conf.
-Original Message-
From: Joakim Erdfelt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26, 2008 10:50 PM
To: archiva-users@maven.apache.org
Subject: Re: archiva-1.0.2 eta?
Here's a changed log4j.xml file for you.
It changes from a DailyRollingFileAppender to a RollingFileAppender with
a max of Six 500MB files ever.
It also squelches the output to error / fatal messages only in the main
log.
It leaves the audit log alone.
?xml version=1.0 encoding=UTF-8 ?
!DOCTYPE log4j:configuration SYSTEM log4j.dtd
log4j:configuration xmlns:log4j=http://jakarta.apache.org/log4j/;
appender name=rolling class=org.apache.log4j.RollingFileAppender
param name=file value=${appserver.base}/logs/archiva.log /
param name=append value=true /
param name=maxFileSize value=500MB /
param name=maxBackupIndex value=6 /
layout class=org.apache.log4j.PatternLayout
param name=ConversionPattern value=%-4r [%t] %-5p %c %x -
%m%n/
/layout
/appender
appender name=auditlog
class=org.apache.log4j.DailyRollingFileAppender
param name=file value=${appserver.base}/logs/audit.log /
param name=append value=true /
param name=datePattern value='.'-MM-dd /
layout class=org.apache.log4j.PatternLayout
param name=ConversionPattern value=%d{-MM-dd HH:mm:ss}
%m%n/
/layout
/appender
appender name=console class=org.apache.log4j.ConsoleAppender
param name=Target value=System.out/
layout class=org.apache.log4j.PatternLayout
param name=ConversionPattern value=%d [%t] %-5p %c %x -
%m%n/
/layout
/appender
logger name=org.apache.archiva.AuditLog
level value=info /
appender-ref ref=auditlog /
/logger
root
priority value =error /
appender-ref ref=console /
appender-ref ref=rolling /
/root
/log4j:configuration
Brett Porter wrote:
On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I have not. Is that configured in the plexus.xml?
No, log4j.xml - but it seems like the problem is just too many
exception messages? Is that what is filling the log so fast?
- Brett
Re: archiva-1.0.2 eta?
Are these issues new, or were they present before (just wondering if it's a regression because of my changes). Anyway, I can add more tests. How is the performance/stability after a little while now? - Brett On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Looks like I still have some issues. I have attached parts of the log file because the entire file is too large. Let me know if you would like any other information. I am using the same archiva.xml as before. These errors may be due to some non-standard artifacts in our repo, but most of them do seem correct to me. I do know that we have some artifacts that do not have poms though.
Re: archiva-1.0.2 eta?
I see - have you customised the default logging levels? - Brett On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: I think it has something to do with the log file reaching 2 GB in size. I couldn't even restart it until I remove the log files. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 9:44 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? The snapshot build crashed on my this evening and had to be stopped. When I stopped it, it had a stale pid and said it wasn't running. However, there was some process still running that I had to kill manually. Either way, there is still some type of issue. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 1:58 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are these issues new, or were they present before (just wondering if it's a regression because of my changes). Anyway, I can add more tests. How is the performance/stability after a little while now? - Brett On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Looks like I still have some issues. I have attached parts of the log file because the entire file is too large. Let me know if you would like any other information. I am using the same archiva.xml as before. These errors may be due to some non-standard artifacts in our repo, but most of them do seem correct to me. I do know that we have some artifacts that do not have poms though. -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
I have not. Is that configured in the plexus.xml? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 10:06 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? I see - have you customised the default logging levels? - Brett On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: I think it has something to do with the log file reaching 2 GB in size. I couldn't even restart it until I remove the log files. -Original Message- From: Jason Chaffee [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 9:44 PM To: archiva-users@maven.apache.org Subject: RE: archiva-1.0.2 eta? The snapshot build crashed on my this evening and had to be stopped. When I stopped it, it had a stale pid and said it wasn't running. However, there was some process still running that I had to kill manually. Either way, there is still some type of issue. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 1:58 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are these issues new, or were they present before (just wondering if it's a regression because of my changes). Anyway, I can add more tests. How is the performance/stability after a little while now? - Brett On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Looks like I still have some issues. I have attached parts of the log file because the entire file is too large. Let me know if you would like any other information. I am using the same archiva.xml as before. These errors may be due to some non-standard artifacts in our repo, but most of them do seem correct to me. I do know that we have some artifacts that do not have poms though. -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: archiva-1.0.2 eta?
If you are able to, please test the following build: http://people.apache.org/~brett/builds/apache-archiva-1.0.2-SNAPSHOT-bin.zip (please note this is not an official release) The problems should now be corrected. It would be helpful to check how that runs for a few days so we know whether it is worth putting together as a release including the fixes so far, or if more investigation is needed. Thanks, Brett On 25/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Actually, I misspoke. I checked the logs again today and saw the NPE during the database scanning. I am not sure what is going on because I didn't change any of the database configuration from installed defaults. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 12:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Did you switch to a build of 1.0.2-SNAPSHOT which caused the issue to not become reproducible, or have you stopped observing it in your current installation? Thanks, Brett On 24/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: In particular, I would like the fixes for the following issues: * http://jira.codehaus.org/browse/MRM-674 * http://jira.codehaus.org/browse/MRM-632 * http://jira.codehaus.org/browse/MRM-691 Only the last one still needs to be fixed, if it is still an issue. I am not able to reproduce it anymore. -Original Message- From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are there any specific bugs in the bug tracking system that you feel need attention? Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi Archiva overall open (non-future) bugs - http://urltea.com/2rqj - Joakim Jason Chaffee wrote: Is there an ETA on the 1.0.2 release? I would really like to get a couple of bug fixes. -- Brett Porter Blog: http://blogs.exist.com/bporter/ -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
Will do. I will install it today and test if for a couple of days. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 7:53 AM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? If you are able to, please test the following build: http://people.apache.org/~brett/builds/apache-archiva-1.0.2-SNAPSHOT-bin .zip (please note this is not an official release) The problems should now be corrected. It would be helpful to check how that runs for a few days so we know whether it is worth putting together as a release including the fixes so far, or if more investigation is needed. Thanks, Brett On 25/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Actually, I misspoke. I checked the logs again today and saw the NPE during the database scanning. I am not sure what is going on because I didn't change any of the database configuration from installed defaults. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 12:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Did you switch to a build of 1.0.2-SNAPSHOT which caused the issue to not become reproducible, or have you stopped observing it in your current installation? Thanks, Brett On 24/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: In particular, I would like the fixes for the following issues: * http://jira.codehaus.org/browse/MRM-674 * http://jira.codehaus.org/browse/MRM-632 * http://jira.codehaus.org/browse/MRM-691 Only the last one still needs to be fixed, if it is still an issue. I am not able to reproduce it anymore. -Original Message- From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are there any specific bugs in the bug tracking system that you feel need attention? Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi Archiva overall open (non-future) bugs - http://urltea.com/2rqj - Joakim Jason Chaffee wrote: Is there an ETA on the 1.0.2 release? I would really like to get a couple of bug fixes. -- Brett Porter Blog: http://blogs.exist.com/bporter/ -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: archiva-1.0.2 eta?
Great - thanks for your patience. On 26/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Will do. I will install it today and test if for a couple of days. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 7:53 AM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? If you are able to, please test the following build: http://people.apache.org/~brett/builds/apache-archiva-1.0.2-SNAPSHOT-bin .zip (please note this is not an official release) The problems should now be corrected. It would be helpful to check how that runs for a few days so we know whether it is worth putting together as a release including the fixes so far, or if more investigation is needed. Thanks, Brett On 25/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: Actually, I misspoke. I checked the logs again today and saw the NPE during the database scanning. I am not sure what is going on because I didn't change any of the database configuration from installed defaults. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 12:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Did you switch to a build of 1.0.2-SNAPSHOT which caused the issue to not become reproducible, or have you stopped observing it in your current installation? Thanks, Brett On 24/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: In particular, I would like the fixes for the following issues: * http://jira.codehaus.org/browse/MRM-674 * http://jira.codehaus.org/browse/MRM-632 * http://jira.codehaus.org/browse/MRM-691 Only the last one still needs to be fixed, if it is still an issue. I am not able to reproduce it anymore. -Original Message- From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are there any specific bugs in the bug tracking system that you feel need attention? Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi Archiva overall open (non-future) bugs - http://urltea.com/2rqj - Joakim Jason Chaffee wrote: Is there an ETA on the 1.0.2 release? I would really like to get a couple of bug fixes. -- Brett Porter Blog: http://blogs.exist.com/bporter/ -- Brett Porter Blog: http://blogs.exist.com/bporter/ -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: archiva-1.0.2 eta?
Did you switch to a build of 1.0.2-SNAPSHOT which caused the issue to not become reproducible, or have you stopped observing it in your current installation? Thanks, Brett On 24/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: In particular, I would like the fixes for the following issues: * http://jira.codehaus.org/browse/MRM-674 * http://jira.codehaus.org/browse/MRM-632 * http://jira.codehaus.org/browse/MRM-691 Only the last one still needs to be fixed, if it is still an issue. I am not able to reproduce it anymore. -Original Message- From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are there any specific bugs in the bug tracking system that you feel need attention? Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi Archiva overall open (non-future) bugs - http://urltea.com/2rqj - Joakim Jason Chaffee wrote: Is there an ETA on the 1.0.2 release? I would really like to get a couple of bug fixes. -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
Actually, I misspoke. I checked the logs again today and saw the NPE during the database scanning. I am not sure what is going on because I didn't change any of the database configuration from installed defaults. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 12:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Did you switch to a build of 1.0.2-SNAPSHOT which caused the issue to not become reproducible, or have you stopped observing it in your current installation? Thanks, Brett On 24/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: In particular, I would like the fixes for the following issues: * http://jira.codehaus.org/browse/MRM-674 * http://jira.codehaus.org/browse/MRM-632 * http://jira.codehaus.org/browse/MRM-691 Only the last one still needs to be fixed, if it is still an issue. I am not able to reproduce it anymore. -Original Message- From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are there any specific bugs in the bug tracking system that you feel need attention? Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi Archiva overall open (non-future) bugs - http://urltea.com/2rqj - Joakim Jason Chaffee wrote: Is there an ETA on the 1.0.2 release? I would really like to get a couple of bug fixes. -- Brett Porter Blog: http://blogs.exist.com/bporter/
