Release Archiva 1.2.2

[Deng Ching-2]

Hi All,

I'm planning to cut a release of Archiva at the end of the week. So far,
there are 24 issues scheduled for 1.2.2 that have already been resolved:

* [MRM-1168] - A locked user gets HTTP ERROR 500 page when logging in
Artifact Repository page
* [MRM-1196] - checksums are not updated when artifact is re-uploaded
* [MRM-1214] - Web Application Deployment, Troubleshooting
* [MRM-1217] - upgrade standalone bundle to Jetty 6.1.19
* [MRM-1216] - Logging conflict on startup in Jetty bundle
* [MRM-1218] - upgrade to JSP 2.1
* [MRM-1219] - Missing appenders in log4j configuration
* [MRM-1220] - disable Struts devMode
* [MRM-1171] - Archiva 1.2 - Internet Explorer - Search - Anvanced Search -
Advanced Search Fields - Add Search Field (green +)
* [MRM-1212] - create-missing-checksums and metadata-updater sometimes
causes deployments to fail for large projects when enabled
* [MRM-1197] - Random 400 Error when uploading maven-metadata.xml to Archiva
1.2/1.2.1
* [MRM-1202] - 404 error when changing password
* [MRM-1163] - Add some decent logs in webdav for debugging purposes
* [MRM-1141] - archiva-cli no longer works
* [MRM-1194] - Archiva doesn't cope with versions in a pom.xml that are
properties
* [MRM-1232] - Unable to get artifacts from repositories which requires
Repository Manager role using repository group
* [MRM-1234] - Typo in Appearance Page
* [MRM-1204] -
org.apache.maven.archiva.repository.project.ProjectModelMerge.merge throws
NPE
* [MRM-1085] - CLONE -Failing to startup due to invalid bean definition
* [MRM-1198] - field length for ARCHIVA_SCM.URL is too short
* [MRM-1207] - Make wrapper.log roll each day so it won't get too large
* [MRM-1191] - Add Archiva log files in documentation
* [MRM-1002] - Website navigation links don't work as expected
* [MRM-1182] - Clarify 'delete released snapshots' functionality


While 19 issues are still open:

* [MRM-782] - archiva attempts to get remote version metadata for snapshots,
even if policy disables it
* [MRM-993] - Metadata update should honor proxy connector blacklisting
* [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
Project
* [MRM-1097] - Error 500 "too many open files"
* [MRM-1103] - One of our two archiva servers does appear to close file
descriptors.
* [MRM-1146] - [Virtual repo browse] An artifact is immediately proxied from
the remote repo (assuming a proxy connector is configured for the first
repo) if the artifact doesn't exist in the first repo but exists in the
second repo in the group
* [MRM-1149] - White/Blacklist pattern matching doesn't work for
Maven-1-repos
* [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
* [MRM-1153] - bad component definitions in dependencies can trigger
failures instead of warnings
* [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
* [MRM-1158] - Maven 1.x deployment fails
* [MRM-1180] - use of Lucene 2.4 creates incompatible Nexus indexes for
consumers with older versions of Lucene
* [MRM-1205] - Should only create tmp directory for managed repository if
the repository has remote repositories
* [MRM-1206] - HTTP ERROR: 500 when adding/deleting artifact, adding
repository/legacy support/network proxies with null values
* [MRM-1175] - archiva-consumer-plugin-archetype: generates code that does
not compile
* [MRM-1235] - Upgrade task for altering the database schema for the changes
in the length of URL fields
* [MRM-1089] - LDAP Support and Documentation
* [MRM-1080] - Update SearchServiceImplTest so that it uses the new search
API
* [MRM-1123] - ensure all nexus indexer dependencies are in central or built
in to JAR appropriately


I'm planning to push some of the remaining issues to the next release. I've
identified a few which can be included in the 1.2.2 release:

* [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
* [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
* [MRM-1205] - Should only create tmp directory for managed repository if
the repository has remote repositories
* [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
Project

Any thoughts or comments on this?


Thanks,
Deng

[Julien HENRY]

Hi Deng,

Is it possible to fix REDBACK-233 and include it in Archiva? The fix is trivial and will allow my english users to work with Archiva.
The issue is when Archiva is deployed on a French JVM, it is not possible to switch to English language.

Thanks

Julien




________________________________
De : Deng Ching <oching@...>
À : dev@...
Envoyé le : Mardi, 18 Août 2009, 5h08mn 57s
Objet : Release Archiva 1.2.2

Hi All,

I'm planning to cut a release of Archiva at the end of the week. So far,
there are 24 issues scheduled for 1.2.2 that have already been resolved:

* [MRM-1168] - A locked user gets HTTP ERROR 500 page when logging in
Artifact Repository page
* [MRM-1196] - checksums are not updated when artifact is re-uploaded
* [MRM-1214] - Web Application Deployment, Troubleshooting
* [MRM-1217] - upgrade standalone bundle to Jetty 6.1.19
* [MRM-1216] - Logging conflict on startup in Jetty bundle
* [MRM-1218] - upgrade to JSP 2.1
* [MRM-1219] - Missing appenders in log4j configuration
* [MRM-1220] - disable Struts devMode
* [MRM-1171] - Archiva 1.2 - Internet Explorer - Search - Anvanced Search -
Advanced Search Fields - Add Search Field (green +)
* [MRM-1212] - create-missing-checksums and metadata-updater sometimes
causes deployments to fail for large projects when enabled
* [MRM-1197] - Random 400 Error when uploading maven-metadata.xml to Archiva
1.2/1.2.1
* [MRM-1202] - 404 error when changing password
* [MRM-1163] - Add some decent logs in webdav for debugging purposes
* [MRM-1141] - archiva-cli no longer works
* [MRM-1194] - Archiva doesn't cope with versions in a pom.xml that are
properties
* [MRM-1232] - Unable to get artifacts from repositories which requires
Repository Manager role using repository group
* [MRM-1234] - Typo in Appearance Page
* [MRM-1204] -
org.apache.maven.archiva.repository.project.ProjectModelMerge.merge throws
NPE
* [MRM-1085] - CLONE -Failing to startup due to invalid bean definition
* [MRM-1198] - field length for ARCHIVA_SCM.URL is too short
* [MRM-1207] - Make wrapper.log roll each day so it won't get too large
* [MRM-1191] - Add Archiva log files in documentation
* [MRM-1002] - Website navigation links don't work as expected
* [MRM-1182] - Clarify 'delete released snapshots' functionality


While 19 issues are still open:

* [MRM-782] - archiva attempts to get remote version metadata for snapshots,
even if policy disables it
* [MRM-993] - Metadata update should honor proxy connector blacklisting
* [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
Project
* [MRM-1097] - Error 500 "too many open files"
* [MRM-1103] - One of our two archiva servers does appear to close file
descriptors.
* [MRM-1146] - [Virtual repo browse] An artifact is immediately proxied from
the remote repo (assuming a proxy connector is configured for the first
repo) if the artifact doesn't exist in the first repo but exists in the
second repo in the group
* [MRM-1149] - White/Blacklist pattern matching doesn't work for
Maven-1-repos
* [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
* [MRM-1153] - bad component definitions in dependencies can trigger
failures instead of warnings
* [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
* [MRM-1158] - Maven 1.x deployment fails
* [MRM-1180] - use of Lucene 2.4 creates incompatible Nexus indexes for
consumers with older versions of Lucene
* [MRM-1205] - Should only create tmp directory for managed repository if
the repository has remote repositories
* [MRM-1206] - HTTP ERROR: 500 when adding/deleting artifact, adding
repository/legacy support/network proxies with null values
* [MRM-1175] - archiva-consumer-plugin-archetype: generates code that does
not compile
* [MRM-1235] - Upgrade task for altering the database schema for the changes
in the length of URL fields
* [MRM-1089] - LDAP Support and Documentation
* [MRM-1080] - Update SearchServiceImplTest so that it uses the new search
API
* [MRM-1123] - ensure all nexus indexer dependencies are in central or built
in to JAR appropriately


I'm planning to push some of the remaining issues to the next release. I've
identified a few which can be included in the 1.2.2 release:

* [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
* [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
* [MRM-1205] - Should only create tmp directory for managed repository if
the repository has remote repositories
* [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
Project

Any thoughts or comments on this?


Thanks,
Deng

[Deng Ching-2]

Hi Julien,

I guess we can include it. From the comments and links in REDBACK-233, I
take it the fix doesn't require any changes in the code?

Thanks,
Deng

On Tue, Aug 18, 2009 at 4:03 PM, Julien HENRY <henryju@...> wrote:

> Hi Deng,
>
> Is it possible to fix REDBACK-233 and include it in Archiva? The fix is
> trivial and will allow my english users to work with Archiva.
> The issue is when Archiva is deployed on a French JVM, it is not possible
> to switch to English language.
>
> Thanks
>
> Julien
>
>
>
>
> ________________________________
> De : Deng Ching <oching@...>
> À : dev@...
> Envoyé le : Mardi, 18 Août 2009, 5h08mn 57s
> Objet : Release Archiva 1.2.2
>
> Hi All,
>
> I'm planning to cut a release of Archiva at the end of the week. So far,
> there are 24 issues scheduled for 1.2.2 that have already been resolved:
>
> * [MRM-1168] - A locked user gets HTTP ERROR 500 page when logging in
> Artifact Repository page
> * [MRM-1196] - checksums are not updated when artifact is re-uploaded
> * [MRM-1214] - Web Application Deployment, Troubleshooting
> * [MRM-1217] - upgrade standalone bundle to Jetty 6.1.19
> * [MRM-1216] - Logging conflict on startup in Jetty bundle
> * [MRM-1218] - upgrade to JSP 2.1
> * [MRM-1219] - Missing appenders in log4j configuration
> * [MRM-1220] - disable Struts devMode
> * [MRM-1171] - Archiva 1.2 - Internet Explorer - Search - Anvanced Search -
> Advanced Search Fields - Add Search Field (green +)
> * [MRM-1212] - create-missing-checksums and metadata-updater sometimes
> causes deployments to fail for large projects when enabled
> * [MRM-1197] - Random 400 Error when uploading maven-metadata.xml to
> Archiva
> 1.2/1.2.1
> * [MRM-1202] - 404 error when changing password
> * [MRM-1163] - Add some decent logs in webdav for debugging purposes
> * [MRM-1141] - archiva-cli no longer works
> * [MRM-1194] - Archiva doesn't cope with versions in a pom.xml that are
> properties
> * [MRM-1232] - Unable to get artifacts from repositories which requires
> Repository Manager role using repository group
> * [MRM-1234] - Typo in Appearance Page
> * [MRM-1204] -
> org.apache.maven.archiva.repository.project.ProjectModelMerge.merge throws
> NPE
> * [MRM-1085] - CLONE -Failing to startup due to invalid bean definition
> * [MRM-1198] - field length for ARCHIVA_SCM.URL is too short
> * [MRM-1207] - Make wrapper.log roll each day so it won't get too large
> * [MRM-1191] - Add Archiva log files in documentation
> * [MRM-1002] - Website navigation links don't work as expected
> * [MRM-1182] - Clarify 'delete released snapshots' functionality
>
>
> While 19 issues are still open:
>
> * [MRM-782] - archiva attempts to get remote version metadata for
> snapshots,
> even if policy disables it
> * [MRM-993] - Metadata update should honor proxy connector blacklisting
> * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
> Project
> * [MRM-1097] - Error 500 "too many open files"
> * [MRM-1103] - One of our two archiva servers does appear to close file
> descriptors.
> * [MRM-1146] - [Virtual repo browse] An artifact is immediately proxied
> from
> the remote repo (assuming a proxy connector is configured for the first
> repo) if the artifact doesn't exist in the first repo but exists in the
> second repo in the group
> * [MRM-1149] - White/Blacklist pattern matching doesn't work for
> Maven-1-repos
> * [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
> * [MRM-1153] - bad component definitions in dependencies can trigger
> failures instead of warnings
> * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
> * [MRM-1158] - Maven 1.x deployment fails
> * [MRM-1180] - use of Lucene 2.4 creates incompatible Nexus indexes for
> consumers with older versions of Lucene
> * [MRM-1205] - Should only create tmp directory for managed repository if
> the repository has remote repositories
> * [MRM-1206] - HTTP ERROR: 500 when adding/deleting artifact, adding
> repository/legacy support/network proxies with null values
> * [MRM-1175] - archiva-consumer-plugin-archetype: generates code that does
> not compile
> * [MRM-1235] - Upgrade task for altering the database schema for the
> changes
> in the length of URL fields
> * [MRM-1089] - LDAP Support and Documentation
> * [MRM-1080] - Update SearchServiceImplTest so that it uses the new search
> API
> * [MRM-1123] - ensure all nexus indexer dependencies are in central or
> built
> in to JAR appropriately
>
>
> I'm planning to push some of the remaining issues to the next release. I've
> identified a few which can be included in the 1.2.2 release:
>
> * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
> * [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
> * [MRM-1205] - Should only create tmp directory for managed repository if
> the repository has remote repositories
> * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
> Project
>
> Any thoughts or comments on this?
>
>
> Thanks,
> Deng
>
>
>
>
>

[Julien HENRY]

You're right, no code change is needed: only add an empty property file to serve as a placeholder for the default locale.

Thanks

Julien




________________________________
De : Deng Ching <oching@...>
À : dev@...
Envoyé le : Mardi, 18 Août 2009, 10h29mn 37s
Objet : Re: Re : Release Archiva 1.2.2

Hi Julien,

I guess we can include it. From the comments and links in REDBACK-233, I
take it the fix doesn't require any changes in the code?

Thanks,
Deng

On Tue, Aug 18, 2009 at 4:03 PM, Julien HENRY <henryju@...> wrote:

> Hi Deng,
>
> Is it possible to fix REDBACK-233 and include it in Archiva? The fix is
> trivial and will allow my english users to work with Archiva.
> The issue is when Archiva is deployed on a French JVM, it is not possible
> to switch to English language.
>
> Thanks
>
> Julien
>
>
>
>
> ________________________________
> De : Deng Ching <oching@...>
> À : dev@...
> Envoyé le : Mardi, 18 Août 2009, 5h08mn 57s
> Objet : Release Archiva 1.2.2
>
> Hi All,
>
> I'm planning to cut a release of Archiva at the end of the week. So far,
> there are 24 issues scheduled for 1.2.2 that have already been resolved:
>
> * [MRM-1168] - A locked user gets HTTP ERROR 500 page when logging in
> Artifact Repository page
> * [MRM-1196] - checksums are not updated when artifact is re-uploaded
> * [MRM-1214] - Web Application Deployment, Troubleshooting
> * [MRM-1217] - upgrade standalone bundle to Jetty 6.1.19
> * [MRM-1216] - Logging conflict on startup in Jetty bundle
> * [MRM-1218] - upgrade to JSP 2.1
> * [MRM-1219] - Missing appenders in log4j configuration
> * [MRM-1220] - disable Struts devMode
> * [MRM-1171] - Archiva 1.2 - Internet Explorer - Search - Anvanced Search -
> Advanced Search Fields - Add Search Field (green +)
> * [MRM-1212] - create-missing-checksums and metadata-updater sometimes
> causes deployments to fail for large projects when enabled
> * [MRM-1197] - Random 400 Error when uploading maven-metadata.xml to
> Archiva
> 1.2/1.2.1
> * [MRM-1202] - 404 error when changing password
> * [MRM-1163] - Add some decent logs in webdav for debugging purposes
> * [MRM-1141] - archiva-cli no longer works
> * [MRM-1194] - Archiva doesn't cope with versions in a pom.xml that are
> properties
> * [MRM-1232] - Unable to get artifacts from repositories which requires
> Repository Manager role using repository group
> * [MRM-1234] - Typo in Appearance Page
> * [MRM-1204] -
> org.apache.maven.archiva.repository.project.ProjectModelMerge.merge throws
> NPE
> * [MRM-1085] - CLONE -Failing to startup due to invalid bean definition
> * [MRM-1198] - field length for ARCHIVA_SCM.URL is too short
> * [MRM-1207] - Make wrapper.log roll each day so it won't get too large
> * [MRM-1191] - Add Archiva log files in documentation
> * [MRM-1002] - Website navigation links don't work as expected
> * [MRM-1182] - Clarify 'delete released snapshots' functionality
>
>
> While 19 issues are still open:
>
> * [MRM-782] - archiva attempts to get remote version metadata for
> snapshots,
> even if policy disables it
> * [MRM-993] - Metadata update should honor proxy connector blacklisting
> * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
> Project
> * [MRM-1097] - Error 500 "too many open files"
> * [MRM-1103] - One of our two archiva servers does appear to close file
> descriptors.
> * [MRM-1146] - [Virtual repo browse] An artifact is immediately proxied
> from
> the remote repo (assuming a proxy connector is configured for the first
> repo) if the artifact doesn't exist in the first repo but exists in the
> second repo in the group
> * [MRM-1149] - White/Blacklist pattern matching doesn't work for
> Maven-1-repos
> * [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
> * [MRM-1153] - bad component definitions in dependencies can trigger
> failures instead of warnings
> * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
> * [MRM-1158] - Maven 1.x deployment fails
> * [MRM-1180] - use of Lucene 2.4 creates incompatible Nexus indexes for
> consumers with older versions of Lucene
> * [MRM-1205] - Should only create tmp directory for managed repository if
> the repository has remote repositories
> * [MRM-1206] - HTTP ERROR: 500 when adding/deleting artifact, adding
> repository/legacy support/network proxies with null values
> * [MRM-1175] - archiva-consumer-plugin-archetype: generates code that does
> not compile
> * [MRM-1235] - Upgrade task for altering the database schema for the
> changes
> in the length of URL fields
> * [MRM-1089] - LDAP Support and Documentation
> * [MRM-1080] - Update SearchServiceImplTest so that it uses the new search
> API
> * [MRM-1123] - ensure all nexus indexer dependencies are in central or
> built
> in to JAR appropriately
>
>
> I'm planning to push some of the remaining issues to the next release. I've
> identified a few which can be included in the 1.2.2 release:
>
> * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
> * [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
> * [MRM-1205] - Should only create tmp directory for managed repository if
> the repository has remote repositories
> * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
> Project
>
> Any thoughts or comments on this?
>
>
> Thanks,
> Deng
>
>
>
>
>

[Deng Ching-2]

Ok, thanks Julien! I'll get the fix in Redback and Archiva.

Thanks,
Deng

On Tue, Aug 18, 2009 at 4:52 PM, Julien HENRY <henryju@...> wrote:

> You're right, no code change is needed: only add an empty property file to
> serve as a placeholder for the default locale.
>
> Thanks
>
> Julien
>
>
>
>
> ________________________________
> De : Deng Ching <oching@...>
> À : dev@...
> Envoyé le : Mardi, 18 Août 2009, 10h29mn 37s
> Objet : Re: Re : Release Archiva 1.2.2
>
> Hi Julien,
>
> I guess we can include it. From the comments and links in REDBACK-233, I
> take it the fix doesn't require any changes in the code?
>
> Thanks,
> Deng
>
> On Tue, Aug 18, 2009 at 4:03 PM, Julien HENRY <henryju@...> wrote:
>
> > Hi Deng,
> >
> > Is it possible to fix REDBACK-233 and include it in Archiva? The fix is
> > trivial and will allow my english users to work with Archiva.
> > The issue is when Archiva is deployed on a French JVM, it is not possible
> > to switch to English language.
> >
> > Thanks
> >
> > Julien
> >
> >
> >
> >
> > ________________________________
> > De : Deng Ching <oching@...>
> > À : dev@...
> > Envoyé le : Mardi, 18 Août 2009, 5h08mn 57s
> > Objet : Release Archiva 1.2.2
> >
> > Hi All,
> >
> > I'm planning to cut a release of Archiva at the end of the week. So far,
> > there are 24 issues scheduled for 1.2.2 that have already been resolved:
> >
> > * [MRM-1168] - A locked user gets HTTP ERROR 500 page when logging in
> > Artifact Repository page
> > * [MRM-1196] - checksums are not updated when artifact is re-uploaded
> > * [MRM-1214] - Web Application Deployment, Troubleshooting
> > * [MRM-1217] - upgrade standalone bundle to Jetty 6.1.19
> > * [MRM-1216] - Logging conflict on startup in Jetty bundle
> > * [MRM-1218] - upgrade to JSP 2.1
> > * [MRM-1219] - Missing appenders in log4j configuration
> > * [MRM-1220] - disable Struts devMode
> > * [MRM-1171] - Archiva 1.2 - Internet Explorer - Search - Anvanced Search
> -
> > Advanced Search Fields - Add Search Field (green +)
> > * [MRM-1212] - create-missing-checksums and metadata-updater sometimes
> > causes deployments to fail for large projects when enabled
> > * [MRM-1197] - Random 400 Error when uploading maven-metadata.xml to
> > Archiva
> > 1.2/1.2.1
> > * [MRM-1202] - 404 error when changing password
> > * [MRM-1163] - Add some decent logs in webdav for debugging purposes
> > * [MRM-1141] - archiva-cli no longer works
> > * [MRM-1194] - Archiva doesn't cope with versions in a pom.xml that are
> > properties
> > * [MRM-1232] - Unable to get artifacts from repositories which requires
> > Repository Manager role using repository group
> > * [MRM-1234] - Typo in Appearance Page
> > * [MRM-1204] -
> > org.apache.maven.archiva.repository.project.ProjectModelMerge.merge
> throws
> > NPE
> > * [MRM-1085] - CLONE -Failing to startup due to invalid bean definition
> > * [MRM-1198] - field length for ARCHIVA_SCM.URL is too short
> > * [MRM-1207] - Make wrapper.log roll each day so it won't get too large
> > * [MRM-1191] - Add Archiva log files in documentation
> > * [MRM-1002] - Website navigation links don't work as expected
> > * [MRM-1182] - Clarify 'delete released snapshots' functionality
> >
> >
> > While 19 issues are still open:
> >
> > * [MRM-782] - archiva attempts to get remote version metadata for
> > snapshots,
> > even if policy disables it
> > * [MRM-993] - Metadata update should honor proxy connector blacklisting
> > * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
> > Project
> > * [MRM-1097] - Error 500 "too many open files"
> > * [MRM-1103] - One of our two archiva servers does appear to close file
> > descriptors.
> > * [MRM-1146] - [Virtual repo browse] An artifact is immediately proxied
> > from
> > the remote repo (assuming a proxy connector is configured for the first
> > repo) if the artifact doesn't exist in the first repo but exists in the
> > second repo in the group
> > * [MRM-1149] - White/Blacklist pattern matching doesn't work for
> > Maven-1-repos
> > * [MRM-1151] - Error when processing file
> nexus-maven-repository-index.zip
> > * [MRM-1153] - bad component definitions in dependencies can trigger
> > failures instead of warnings
> > * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
> > * [MRM-1158] - Maven 1.x deployment fails
> > * [MRM-1180] - use of Lucene 2.4 creates incompatible Nexus indexes for
> > consumers with older versions of Lucene
> > * [MRM-1205] - Should only create tmp directory for managed repository if
> > the repository has remote repositories
> > * [MRM-1206] - HTTP ERROR: 500 when adding/deleting artifact, adding
> > repository/legacy support/network proxies with null values
> > * [MRM-1175] - archiva-consumer-plugin-archetype: generates code that
> does
> > not compile
> > * [MRM-1235] - Upgrade task for altering the database schema for the
> > changes
> > in the length of URL fields
> > * [MRM-1089] - LDAP Support and Documentation
> > * [MRM-1080] - Update SearchServiceImplTest so that it uses the new
> search
> > API
> > * [MRM-1123] - ensure all nexus indexer dependencies are in central or
> > built
> > in to JAR appropriately
> >
> >
> > I'm planning to push some of the remaining issues to the next release.
> I've
> > identified a few which can be included in the 1.2.2 release:
> >
> > * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
> > * [MRM-1151] - Error when processing file
> nexus-maven-repository-index.zip
> > * [MRM-1205] - Should only create tmp directory for managed repository if
> > the repository has remote repositories
> > * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
> > Project
> >
> > Any thoughts or comments on this?
> >
> >
> > Thanks,
> > Deng
> >
> >
> >
> >
> >
>
>
>
>
>

[Jevica Arianne Zurbano]

Hi,

For this issue, I have created http://jira.codehaus.org/browse/MRM-1236.

And, I will be committing the fix shortly.


Deng Ching wrote:

> Ok, thanks Julien! I'll get the fix in Redback and Archiva.
>
> Thanks,
> Deng
>
> On Tue, Aug 18, 2009 at 4:52 PM, Julien HENRY <henryju@...> wrote:
>
>  
>> You're right, no code change is needed: only add an empty property file to
>> serve as a placeholder for the default locale.
>>
>> Thanks
>>
>> Julien
>>
>>
>>
>>
>> ________________________________
>> De : Deng Ching <oching@...>
>> À : dev@...
>> Envoyé le : Mardi, 18 Août 2009, 10h29mn 37s
>> Objet : Re: Re : Release Archiva 1.2.2
>>
>> Hi Julien,
>>
>> I guess we can include it. From the comments and links in REDBACK-233, I
>> take it the fix doesn't require any changes in the code?
>>
>> Thanks,
>> Deng
>>
>> On Tue, Aug 18, 2009 at 4:03 PM, Julien HENRY <henryju@...> wrote:
>>
>>    
>>> Hi Deng,
>>>
>>> Is it possible to fix REDBACK-233 and include it in Archiva? The fix is
>>> trivial and will allow my english users to work with Archiva.
>>> The issue is when Archiva is deployed on a French JVM, it is not possible
>>> to switch to English language.
>>>
>>> Thanks
>>>
>>> Julien
>>>
>>>
>>>      

--

Thanks,

Jev

[brettporter]

On 17/08/2009, at 11:08 PM, Deng Ching wrote:

> Hi All,
>
> I'm planning to cut a release of Archiva at the end of the week. So  
> far,

+1, important to get some of these out there even if there is more to do


> I'm planning to push some of the remaining issues to the next  
> release. I've

You'll push these to a 1.2.3?

> identified a few which can be included in the 1.2.2 release:
>
> * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
> * [MRM-1151] - Error when processing file nexus-maven-repository-
> index.zip
> * [MRM-1205] - Should only create tmp directory for managed  
> repository if
> the repository has remote repositories
> * [MRM-1066] - Shutdown of Tomcat causes Exception when running  
> Archiva
> Project
>

note that MRM-1180 is probably required / helpful to fix MRM-1155.

Cheers,
Brett

[Deng Ching-2]

On Wed, Aug 19, 2009 at 10:47 PM, Brett Porter <brett@...> wrote:

> On 17/08/2009, at 11:08 PM, Deng Ching wrote:
>
>  Hi All,
>>
>> I'm planning to cut a release of Archiva at the end of the week. So far,
>>
>
> +1, important to get some of these out there even if there is more to do
>
>
>  I'm planning to push some of the remaining issues to the next release.
>> I've
>>
>
> You'll push these to a 1.2.3?
>

Done :)

>
>
>
>  identified a few which can be included in the 1.2.2 release:
>>
>> * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
>> * [MRM-1151] - Error when processing file nexus-maven-repository-index.zip
>> * [MRM-1205] - Should only create tmp directory for managed repository if
>> the repository has remote repositories
>> * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
>> Project
>>
>>
> note that MRM-1180 is probably required / helpful to fix MRM-1155.

I think we've already fixed MRM-1155. The index was just not optimized
before being packaged :)


Thanks,
Deng

[Deng Ching-2]

Hi All,

I wasn't able to release 1.2.2 over the weekend because minotaur is down
where people.apache is. Is there somewhere else we could stage the release?

Thanks,
Deng

On Thu, Aug 20, 2009 at 7:16 PM, Deng Ching <oching@...> wrote:

> On Wed, Aug 19, 2009 at 10:47 PM, Brett Porter <brett@...> wrote:
>
>> On 17/08/2009, at 11:08 PM, Deng Ching wrote:
>>
>>  Hi All,
>>>
>>> I'm planning to cut a release of Archiva at the end of the week. So far,
>>>
>>
>> +1, important to get some of these out there even if there is more to do
>>
>>
>>  I'm planning to push some of the remaining issues to the next release.
>>> I've
>>>
>>
>> You'll push these to a 1.2.3?
>>
>
> Done :)
>
>
>>
>>
>>
>>  identified a few which can be included in the 1.2.2 release:
>>>
>>> * [MRM-1155] - m2eclipse - getting index from archiva 1.2 failed
>>> * [MRM-1151] - Error when processing file
>>> nexus-maven-repository-index.zip
>>> * [MRM-1205] - Should only create tmp directory for managed repository if
>>> the repository has remote repositories
>>> * [MRM-1066] - Shutdown of Tomcat causes Exception when running Archiva
>>> Project
>>>
>>>
>> note that MRM-1180 is probably required / helpful to fix MRM-1155.
>
>
> I think we've already fixed MRM-1155. The index was just not optimized
> before being packaged :)
>
>
> Thanks,
> Deng
>

[brettporter]

On 23/08/2009, at 10:21 PM, Deng Ching wrote:

> Hi All,
>
> I wasn't able to release 1.2.2 over the weekend because minotaur is  
> down
> where people.apache is. Is there somewhere else we could stage the  
> release?

I just suggested it in dev@continuum too - how about to Archiva on  
vmbuild?

Dogfood and all that :)

Perhaps that would inspire us to get staging built in...

Do you have admin on it already? I'd suggest for now we just create a  
single staging repository and we'll promote it manually after the vote.

- Brett

[Deng Ching-2]

On Mon, Aug 24, 2009 at 10:29 AM, Brett Porter <brett@...> wrote:

> On 23/08/2009, at 10:21 PM, Deng Ching wrote:
>
>  Hi All,
>>
>> I wasn't able to release 1.2.2 over the weekend because minotaur is down
>> where people.apache is. Is there somewhere else we could stage the
>> release?
>>
>
> I just suggested it in dev@continuum too - how about to Archiva on
> vmbuild?
>
> Dogfood and all that :)
>

> Perhaps that would inspire us to get staging built in...


+1


>
>
> Do you have admin on it already? I'd suggest for now we just create a
> single staging repository and we'll promote it manually after the vote.


I don't think so :) I just registered for an account today

Thanks,
Deng

[Deng Ching-2]

Unfortunately, my account got locked in Archiva vmbuild and I can't deploy
:( Anybody around who has an admin role who can unlock my account?

-Deng

On Mon, Aug 24, 2009 at 10:35 AM, Deng Ching <oching@...> wrote:

>
>
> On Mon, Aug 24, 2009 at 10:29 AM, Brett Porter <brett@...> wrote:
>
>> On 23/08/2009, at 10:21 PM, Deng Ching wrote:
>>
>>  Hi All,
>>>
>>> I wasn't able to release 1.2.2 over the weekend because minotaur is down
>>> where people.apache is. Is there somewhere else we could stage the
>>> release?
>>>
>>
>> I just suggested it in dev@continuum too - how about to Archiva on
>> vmbuild?
>>
>> Dogfood and all that :)
>>
>
>> Perhaps that would inspire us to get staging built in...
>
>
> +1
>
>
>>
>>
>> Do you have admin on it already? I'd suggest for now we just create a
>> single staging repository and we'll promote it manually after the vote.
>
>
> I don't think so :) I just registered for an account today
>
> Thanks,
> Deng
>
>

[brettporter]

Done. Make sure you have your password right before deploying :)

On 24/08/2009, at 3:15 AM, Deng Ching wrote:

> Unfortunately, my account got locked in Archiva vmbuild and I can't  
> deploy
> :( Anybody around who has an admin role who can unlock my account?
>
> -Deng
>
> On Mon, Aug 24, 2009 at 10:35 AM, Deng Ching <oching@...>  
> wrote:
>
>>
>>
>> On Mon, Aug 24, 2009 at 10:29 AM, Brett Porter <brett@...>  
>> wrote:
>>
>>> On 23/08/2009, at 10:21 PM, Deng Ching wrote:
>>>
>>> Hi All,
>>>>
>>>> I wasn't able to release 1.2.2 over the weekend because minotaur  
>>>> is down
>>>> where people.apache is. Is there somewhere else we could stage the
>>>> release?
>>>>
>>>
>>> I just suggested it in dev@continuum too - how about to Archiva on
>>> vmbuild?
>>>
>>> Dogfood and all that :)
>>>
>>
>>> Perhaps that would inspire us to get staging built in...
>>
>>
>> +1
>>
>>
>>>
>>>
>>> Do you have admin on it already? I'd suggest for now we just  
>>> create a
>>> single staging repository and we'll promote it manually after the  
>>> vote.
>>
>>
>> I don't think so :) I just registered for an account today
>>
>> Thanks,
>> Deng
>>
>>

[Deng Ching-2]

Yeah, I learned my lesson now hehe. Thanks Brett!

-Deng

On Mon, Aug 24, 2009 at 8:52 PM, Brett Porter <brett@...> wrote:

> Done. Make sure you have your password right before deploying :)
>
>
> On 24/08/2009, at 3:15 AM, Deng Ching wrote:
>
>  Unfortunately, my account got locked in Archiva vmbuild and I can't deploy
>> :( Anybody around who has an admin role who can unlock my account?
>>
>> -Deng
>>
>> On Mon, Aug 24, 2009 at 10:35 AM, Deng Ching <oching@...> wrote:
>>
>>
>>>
>>> On Mon, Aug 24, 2009 at 10:29 AM, Brett Porter <brett@...> wrote:
>>>
>>>  On 23/08/2009, at 10:21 PM, Deng Ching wrote:
>>>>
>>>> Hi All,
>>>>
>>>>>
>>>>> I wasn't able to release 1.2.2 over the weekend because minotaur is
>>>>> down
>>>>> where people.apache is. Is there somewhere else we could stage the
>>>>> release?
>>>>>
>>>>>
>>>> I just suggested it in dev@continuum too - how about to Archiva on
>>>> vmbuild?
>>>>
>>>> Dogfood and all that :)
>>>>
>>>>
>>>  Perhaps that would inspire us to get staging built in...
>>>>
>>>
>>>
>>> +1
>>>
>>>
>>>
>>>>
>>>> Do you have admin on it already? I'd suggest for now we just create a
>>>> single staging repository and we'll promote it manually after the vote.
>>>>
>>>
>>>
>>> I don't think so :) I just registered for an account today
>>>
>>> Thanks,
>>> Deng
>>>
>>>
>>>
>