Re: [VOTE] Release Archiva 1.0-beta-3

2007-10-21 Thread Fabrice Bellingard
Of course +1!
:-)
Fabrice

On 10/22/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
> Archiva 1.0-beta-3 is now ready for release.
>
> The highlights of this release are:
> - major fixes in path resolution of artifacts (for proxying and consumers)
> - fixes in updating of metadata files
> - fixes in proxy connectors configuration
> - tomcat deployment issues
> - additional fixes in proxying
> - form validations in webapp
>
> The release notes for Archiva 1.0-beta-3 is available here:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660&styleName=Text&projectId=10980&Create=Create
> <
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660&styleName=Text&projectId=10980&Create=Create
> >
>
>
> While the binaries including the sources, checksums and signatures can be
> found in:
>
> http://people.apache.org/builds/maven/archiva/1.0-beta-3/<
> http://people.apache.org/builds/maven/archiva/1.0-beta-2/>
>
> Everyone is encouraged to vote and give their feedback.
>
> [ ]  +1  Release it!
> [ ]   0
> [ ]  -1  Don't release it, because...
>
>
> The vote will be open for 72 hours. So, cast your votes now ;-)
>
>
> Here's my +1
>
>
> Thanks,
> Deng
>


Re: [VOTE] Release Archiva 1.0-beta-3

2007-10-21 Thread Maria Odea Ching
Sorry, this is the correct url for the binaries.. :)

http://people.apache.org/builds/maven/archiva/1.0-beta-3/

-Deng

On 10/22/07, James William Dumay <[EMAIL PROTECTED]> wrote:
>
> Not sure if I can vote or not but heres my +1.
>
> James
>
>
> On Mon, 2007-10-22 at 13:31 +0800, Maria Odea Ching wrote:
> > Hi All,
> >
> > Archiva 1.0-beta-3 is now ready for release.
> >
> > The highlights of this release are:
> > - major fixes in path resolution of artifacts (for proxying and
> consumers)
> > - fixes in updating of metadata files
> > - fixes in proxy connectors configuration
> > - tomcat deployment issues
> > - additional fixes in proxying
> > - form validations in webapp
> >
> > The release notes for Archiva 1.0-beta-3 is available here:
> >
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660&styleName=Text&projectId=10980&Create=Create
> <
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660&styleName=Text&projectId=10980&Create=Create
> >
> >
> >
> > While the binaries including the sources, checksums and signatures can
> be
> > found in:
> >
> > http://people.apache.org/builds/maven/archiva/1.0-beta-3/<
> http://people.apache.org/builds/maven/archiva/1.0-beta-2/>
> >
> > Everyone is encouraged to vote and give their feedback.
> >
> > [ ]  +1  Release it!
> > [ ]   0
> > [ ]  -1  Don't release it, because...
> >
> >
> > The vote will be open for 72 hours. So, cast your votes now ;-)
> >
> >
> > Here's my +1
> >
> >
> > Thanks,
> > Deng
>
>


Re: [VOTE] Release Archiva 1.0-beta-3

2007-10-21 Thread James William Dumay
Not sure if I can vote or not but heres my +1.

James


On Mon, 2007-10-22 at 13:31 +0800, Maria Odea Ching wrote:
> Hi All,
> 
> Archiva 1.0-beta-3 is now ready for release.
> 
> The highlights of this release are:
> - major fixes in path resolution of artifacts (for proxying and consumers)
> - fixes in updating of metadata files
> - fixes in proxy connectors configuration
> - tomcat deployment issues
> - additional fixes in proxying
> - form validations in webapp
> 
> The release notes for Archiva 1.0-beta-3 is available here:
> 
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660&styleName=Text&projectId=10980&Create=Create
> 
> 
> While the binaries including the sources, checksums and signatures can be
> found in:
> 
> http://people.apache.org/builds/maven/archiva/1.0-beta-3/
> 
> Everyone is encouraged to vote and give their feedback.
> 
> [ ]  +1  Release it!
> [ ]   0
> [ ]  -1  Don't release it, because...
> 
> 
> The vote will be open for 72 hours. So, cast your votes now ;-)
> 
> 
> Here's my +1
> 
> 
> Thanks,
> Deng



[VOTE] Release Archiva 1.0-beta-3

2007-10-21 Thread Maria Odea Ching
Hi All,

Archiva 1.0-beta-3 is now ready for release.

The highlights of this release are:
- major fixes in path resolution of artifacts (for proxying and consumers)
- fixes in updating of metadata files
- fixes in proxy connectors configuration
- tomcat deployment issues
- additional fixes in proxying
- form validations in webapp

The release notes for Archiva 1.0-beta-3 is available here:

http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660&styleName=Text&projectId=10980&Create=Create


While the binaries including the sources, checksums and signatures can be
found in:

http://people.apache.org/builds/maven/archiva/1.0-beta-3/

Everyone is encouraged to vote and give their feedback.

[ ]  +1  Release it!
[ ]   0
[ ]  -1  Don't release it, because...


The vote will be open for 72 hours. So, cast your votes now ;-)


Here's my +1


Thanks,
Deng


Re: svn commit: r586919 - in /maven/archiva/trunk: archiva-base/archiva-consumers/archiva-database-consumers/src/main/java/org/apache/maven/archiva/consumers/database/ archiva-database/src/main/java/o

2007-10-21 Thread Brett Porter


On 22/10/2007, at 10:42 AM, Maria Odea Ching wrote:


Hi Brett,

I thought that if there was a problem cleaning up the repository  
data, the delete of the repo shouldn't proceed.. or should it? :-)


That makes sense - I just wanted to check if there was anything else.

My only concern is the saveConfiguration method returning something  
other than success and the repository will still be configured but  
most of the data deleted. I'm not sure if that's possible, though :)


Anyway, this should be fine for now - if we do push these back from  
the web layer we should ensure we have some more testing around the  
exception cases.


Thanks,
Brett



Thanks,
Deng

Brett Porter wrote:

Hi Deng,

On 22/10/2007, at 3:30 AM, [EMAIL PROTECTED] wrote:


@@ -89,13 +105,12 @@
try
{
Configuration configuration =  
archivaConfiguration.getConfiguration();

+ cleanupRepositoryData( existingRepository );
removeRepository( repoid, configuration );
result = saveConfiguration( configuration );

if ( result.equals( SUCCESS ) )
{
- cleanupRepositoryData( existingRepository );
-


Can you just clarify why this was moved?


Re: svn commit: r586919 - in /maven/archiva/trunk: archiva-base/archiva-consumers/archiva-database-consumers/src/main/java/org/apache/maven/archiva/consumers/database/ archiva-database/src/main/java/o

2007-10-21 Thread Maria Odea Ching

Hi Brett,

I thought that if there was a problem cleaning up the repository data, 
the delete of the repo shouldn't proceed.. or should it? :-)


Thanks,
Deng

Brett Porter wrote:

Hi Deng,

On 22/10/2007, at 3:30 AM, [EMAIL PROTECTED] wrote:


@@ -89,13 +105,12 @@
try
{
Configuration configuration = archivaConfiguration.getConfiguration();
+ cleanupRepositoryData( existingRepository );
removeRepository( repoid, configuration );
result = saveConfiguration( configuration );

if ( result.equals( SUCCESS ) )
{
- cleanupRepositoryData( existingRepository );
-


Can you just clarify why this was moved?

private void cleanupRepositoryData( ManagedRepositoryConfiguration 
cleanupRepository )

- throws RoleManagerException
+ throws RoleManagerException, ArchivaDatabaseException
{
removeRepositoryRoles( cleanupRepository );

// TODO: [MRM-382] Remove index from artifacts of deleted managed 
repositories.


- // TODO: [MRM-265] After removing a managed repository - 
Browse/Search still see it

-
+ // [MRM-265] After removing a managed repository - Browse/Search 
still see it

+ cleanupDatabase( cleanupRepository.getId() );
+ cleanupScanStats( cleanupRepository.getId() );
+
// [MRM-520] Proxy Connectors are not deleted with the deletion of a 
Repository.
List proxyConnectors = 
getProxyConnectors();

for ( ProxyConnectorConfiguration proxyConnector : proxyConnectors )


Just a general note (not specific to this commit) - we need to start 
thinking about the accumulation of logic in the web actions and 
shuffle it over to the business layer.


Thanks!

Cheers,
Brett

--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/





Re: svn commit: r586858 - /maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml

2007-10-21 Thread Brett Porter


On 22/10/2007, at 2:02 AM, Joakim Erdfelt wrote:


Can you wrap this into a profile?


I thought about that, but the idea is to have it by default so that  
if I forget an option I get a sensible default. Otherwise, I  
accidentally hose my actual "production" install on the same machine  
by the appearance of ~/.m2/archiva.xml



Like we do for the mysql / postgres options?
This makes testing large repositories rather difficult, as I have  
to reconfigure every time now.


I use -Dappserver.base=/path/to/other-install, but only when I need  
to test the other data. Do you need to test a large repository every  
time you test the webapp?


It also appears that this is showing up in the standalone plexus  
application, making user level configuration impossible that way too.


I'm not sure what you are referring to here?

I'm happy to roll it back if it's inconveniencing anyone else, I just  
wanted to go for the safer option by default.


Cheers,
Brett

--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/


Re: svn commit: r586919 - in /maven/archiva/trunk: archiva-base/archiva-consumers/archiva-database-consumers/src/main/java/org/apache/maven/archiva/consumers/database/ archiva-database/src/main/java/o

2007-10-21 Thread Brett Porter

Hi Deng,

On 22/10/2007, at 3:30 AM, [EMAIL PROTECTED] wrote:


@@ -89,13 +105,12 @@
 try
 {
 Configuration configuration =  
archivaConfiguration.getConfiguration();

+cleanupRepositoryData( existingRepository );
 removeRepository( repoid, configuration );
 result = saveConfiguration( configuration );

 if ( result.equals( SUCCESS ) )
 {
-cleanupRepositoryData( existingRepository );
-


Can you just clarify why this was moved?

 private void cleanupRepositoryData 
( ManagedRepositoryConfiguration cleanupRepository )

-throws RoleManagerException
+throws RoleManagerException, ArchivaDatabaseException
 {
 removeRepositoryRoles( cleanupRepository );

 // TODO: [MRM-382] Remove index from artifacts of deleted  
managed repositories.


-// TODO: [MRM-265] After removing a managed repository -  
Browse/Search still see it

-
+// [MRM-265] After removing a managed repository - Browse/ 
Search still see it

+cleanupDatabase( cleanupRepository.getId() );
+cleanupScanStats( cleanupRepository.getId() );
+
 // [MRM-520] Proxy Connectors are not deleted with the  
deletion of a Repository.
 List proxyConnectors =  
getProxyConnectors();
 for ( ProxyConnectorConfiguration proxyConnector :  
proxyConnectors )


Just a general note (not specific to this commit) - we need to start  
thinking about the accumulation of logic in the web actions and  
shuffle it over to the business layer.


Thanks!

Cheers,
Brett

--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/


Re: svn commit: r586858 - /maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml

2007-10-21 Thread Joakim Erdfelt

Can you wrap this into a profile?
Like we do for the mysql / postgres options?
This makes testing large repositories rather difficult, as I have to 
reconfigure every time now.
It also appears that this is showing up in the standalone plexus 
application, making user level configuration impossible that way too.


- Joakim

[EMAIL PROTECTED] wrote:

Author: brett
Date: Sat Oct 20 22:20:38 2007
New Revision: 586858

URL: http://svn.apache.org/viewvc?rev=586858&view=rev
Log:
add a configuration file for jetty:run so that it doesn't create 
~/.m2/archiva.xml - make testing isolated

Added:

maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml
   (with props)

Added: 
maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml
URL: 
http://svn.apache.org/viewvc/maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml?rev=586858&view=auto
==
--- 
maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml
 (added)
+++ 
maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml
 Sat Oct 20 22:20:38 2007
@@ -0,0 +1,169 @@
+
+
+  2
+  
+
+  internal
+  Archiva Managed Internal Repository
+  ${appserver.base}/data/repositories/internal
+  default
+  true
+  false
+  true
+  0 0 0 * * ?
+  30
+
+
+  snapshots
+  Archiva Managed Snapshot Repository
+  ${appserver.base}/data/repositories/snapshots
+  default
+  false
+  true
+  true
+  0 0\,30 0 * * ?
+  30
+
+  
+  
+
+  central
+  Central Repository
+  http://repo1.maven.org/maven2
+  default
+
+
+  maven2-repository.dev.java.net
+  Java.net Repository for Maven 2
+  http://download.java.net/maven/2/
+  default
+
+  
+
+  
+
+  internal
+  central
+  
+  
+disabled
+once
+fix
+cached
+  
+  
+**/*
+  
+
+
+  internal
+  maven2-repository.dev.java.net
+  
+  
+disabled
+once
+fix
+cached
+  
+  
+javax/**
+  
+
+  
+
+  
+
+  
+artifacts
+
+  **/*.pom
+  **/*.jar
+  **/*.ear
+  **/*.war
+  **/*.car
+  **/*.sar
+  **/*.mar
+  **/*.rar
+  **/*.dtd
+  **/*.tld
+  **/*.tar.gz
+  **/*.tar.bz2
+  **/*.zip
+
+  
+  
+indexable-content
+
+  **/*.txt
+  **/*.TXT
+  **/*.block
+  **/*.config
+  **/*.pom
+  **/*.xml
+  **/*.xsd
+  **/*.dtd
+  **/*.tld
+
+  
+  
+auto-remove
+
+  **/*.bak
+  **/*~
+  **/*-
+
+  
+  
+ignored
+
+  **/.htaccess
+  **/KEYS
+  **/*.rb
+  **/*.sh
+  **/.svn/**
+  **/.DAV/**
+
+  
+
+
+  update-db-artifact
+  create-missing-checksums
+  
update-db-repository-metadata
+  validate-checksum
+  validate-signature
+  index-content
+  auto-remove
+  auto-rename
+  metadata-updater
+  
+
+
+  update-db-bad-content
+
+  
+
+  
+0 0 0 * * ?
+
+  index-artifact
+  update-db-project
+  validate-repository-metadata
+  index-archive-toc
+  update-db-bytecode-stats
+  index-public-methods
+
+
+  not-present-remove-db-artifact
+  not-present-remove-db-project
+  not-present-remove-indexed
+
+  
+
+  
+
+  true
+  true
+
+  
+
+

Propchange: 
maven/archiva/trunk/archiva-web/archiva-webapp/src/appserver-base/conf/archiva.xml
--
svn:eol-style = native


  



--
- Joakim Erdfelt
 [EMAIL PROTECTED]
 Open Source Software (OSS) Developer