You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Maria Odea Ching <oc...@exist.com> on 2007/08/01 13:06:19 UTC
Archiva releases (Take 2)
Hi All,
We (Brett, Joakim and I) have segregated the issues in Jira to prep for
the upcoming 1.0 release (finally! :-) ). Anyway, there'll be two beta
releases first before 1.0.
So..here's the plan (excerpted from Brett):
- finish all issues for 1.0-beta-1
- then move on to 1.0-beta-2 issues for the next release
- do a big bug bash to find the problems in it
- decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be Monday
my time), and this will include the following:
1. Resolved/Closed:
- MRM-290 (Ability to pre-configure the Jetty port in conf/plexus.xml)
- MRM-326 (Adding/Editing repositories doesn't have validation)
- MRM-425 (Search and Browse do not work for snapshots)
- MRM-426 (Search does not work for snapshots because of different
version values in index and database when the snapshot version is unique)
2. In Progress/Open:
- MRM-143 (Improve error reporting on corrupt jars, poms, etc)
- MRM-275 (add "remove old snapshots" Scheduler)
- MRM-294 (Repository purge feature for snapshots)
- MRM-329 (The Reports link gives an HTTP 500)
- MRM-347 (Undefined ${appserver.home} and ${appserver.base})
- MRM-373 (Unable to delete the pre-configured example network proxy)
- MRM-412 (Add support for maven 1 (legacy) request to access a maven2
(default layout) repo )
- MRM-428 (Managed and remote repositories with same name causes problems)
- MRM-429 (Find artifact does not work when the applet is disabled)
- MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
Everyone okay with this? :)
Thanks,
Deng
Re: Tomcat and Windows
Posted by Brett Porter <br...@apache.org>.
Hehe. Clever, but sounds a little voodoo...
Going with 40 sounds like a good idea, but definitely should just be
a warning IMO.
- Brett
On 02/08/2007, at 9:49 PM, Joakim Erdfelt wrote:
> Just a thought.
>
> Would putting in a check on the path depth for a local repository
> when running under windows be useful?
>
> We specify some threshold of character length or sub directory
> count that causes problems, and warn the user to specify something
> simpler.
>
> So if a user decides to use "file://D:/data/archiva/repositories/
> corporate", we error (or warning) out and say "The specified root
> for your local repository is too large for windows to handle, try
> using something smaller and less deep such as file://D:/repos/
> corporate/" ?
>
> Just did a scan of ibiblio's repository to determine the largest
> path there.
> Here what I found ...
>
> 167 - org/codehaus/plexus/security/plexus-security-authorization-
> rbac-store-memory/1.0-alpha-10/plexus-security-authorization-rbac-
> store-memory-1.0-alpha-10-sources.jar.sha1
> 169 - org/codehaus/plexus/security/plexus-security-authentication-
> provider-keystore/1.0-alpha-11/plexus-security-authentication-
> provider-keystore-1.0-alpha-11-sources.jar.sha1
> 178 -
> org/codehaus/plexus/security/plexus-security-authentication-
> provider-user-manager/1.0-alpha-11/plexus-security-authentication-
> provider-user-manager-1.0-alpha-11-sources.jar.sha1
>
> If we take those numbers + 20% (to allow for growth), and subtract
> the windows limit of 255 characters we are left with the magic # of
> max characters for a windows repository root.
>
> (178 + 20%) = 213.6
> 256 - 214 = 42
>
> How about we set a 42 (creepy number) characters as the limit for
> the root of a windows repository?
>
>
Re: Archiva releases (Take 2)
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Just a thought.
Would putting in a check on the path depth for a local repository when
running under windows be useful?
We specify some threshold of character length or sub directory count
that causes problems, and warn the user to specify something simpler.
So if a user decides to use
"file://D:/data/archiva/repositories/corporate", we error (or warning)
out and say "The specified root for your local repository is too large
for windows to handle, try using something smaller and less deep such as
file://D:/repos/corporate/" ?
Just did a scan of ibiblio's repository to determine the largest path there.
Here what I found ...
167 -
org/codehaus/plexus/security/plexus-security-authorization-rbac-store-memory/1.0-alpha-10/plexus-security-authorization-rbac-store-memory-1.0-alpha-10-sources.jar.sha1
169 -
org/codehaus/plexus/security/plexus-security-authentication-provider-keystore/1.0-alpha-11/plexus-security-authentication-provider-keystore-1.0-alpha-11-sources.jar.sha1
178 -
org/codehaus/plexus/security/plexus-security-authentication-provider-user-manager/1.0-alpha-11/plexus-security-authentication-provider-user-manager-1.0-alpha-11-sources.jar.sha1
If we take those numbers + 20% (to allow for growth), and subtract the
windows limit of 255 characters we are left with the magic # of max
characters for a windows repository root.
(178 + 20%) = 213.6
256 - 214 = 42
How about we set a 42 (creepy number) characters as the limit for the
root of a windows repository?
- Joakim
Ludovic Maitre wrote:
> Hi Fabrice, all,
>
> Thanks for your answers; so if you have succeeded deploying Archiva
> (1.0-alpha-2 ?) on Tomcat and accessing the repository perhaps it's
> only a deployment problem on my side, i will look more deeply in my
> config. Also i hope that it was ok to discuss these on the dev list,
> perhaps these are more userland issues/questions.
>
> Good holidays,
>
> Fabrice Bellingard wrote:
>> Since I'm working on Archiva, I've always been testing it on Tomcat
>> 5.5.23and I've never had a single problem (using the tips provided on
>> the Wiki:
>> http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat)
>>
>> I'll look at MRM-323 when I have some time (that is after my coming
>> holidays
>> :-))
>>
>> Fabrice.
>>
>> On 8/2/07, Brett Porter <br...@apache.org> wrote:
>>
>>> I'd be happy to run some tests on Tomcat post beta-1 as well. I've
>>> spent way too much time battling these things in a past life not to
>>> have learned something that might be helpful :)
>>>
>>> Anyone here deploying to something other than Tomcat? We have Jetty5
>>> (via appserver) and 6 (via plugin) covered - I'm interested to know
>>> if these issues are isolated to TC.
>>>
>>> - Brett
>>>
>>> On 02/08/2007, at 10:32 AM, Maria Odea Ching wrote:
>>>
>>>
>>>> Yep, we also expect users to deploy Archiva standalone in
>>>> production. So far, MRM-323 and all the other remaining Tomcat
>>>> issues are scheduled for 1.0.x since most of them needs to be
>>>> investigated further. I've looked at MRM-323 in jira and saw your
>>>> findings for this issue. I'll take a look at it later on and
>>>> "maybe" we could include this in beta-2 :)
>>>>
>>>>
>>>> Thanks,
>>>> Deng
>>>>
>>>>
>>>> Ludovic Maitre wrote:
>>>>
>>>>> Hi Maria, all,
>>>>>
>>>>> Although i'm a new user of Archiva, i would like to know when in
>>>>> the roadmap the team plan to fix issues related to running Archiva
>>>>> inside Tomcat (issues like http://jira.codehaus.org/browse/
>>>>> MRM-323 ) ? Is it something important for the team ? Did you
>>>>> expect users to deploy Archiva standalone in production ?
>>>>> Best regards,
>>>>>
>>>>> Maria Odea Ching wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> We (Brett, Joakim and I) have segregated the issues in Jira to
>>>>>> prep for the upcoming 1.0 release (finally! :-) ). Anyway,
>>>>>> there'll be two beta releases first before 1.0.
>>>>>>
>>>>>> So..here's the plan (excerpted from Brett):
>>>>>> - finish all issues for 1.0-beta-1
>>>>>> - then move on to 1.0-beta-2 issues for the next release
>>>>>> - do a big bug bash to find the problems in it
>>>>>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>>>>>>
>>>>>>
>>>>>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
>>>>>> Monday my time), and this will include the following:
>>>>>> 1. Resolved/Closed:
>>>>>> - MRM-290 (Ability to pre-configure the Jetty port in conf/
>>>>>> plexus.xml)
>>>>>> - MRM-326 (Adding/Editing repositories doesn't have validation)
>>>>>> - MRM-425 (Search and Browse do not work for snapshots)
>>>>>> - MRM-426 (Search does not work for snapshots because of
>>>>>> different version values in index and database when the snapshot
>>>>>> version is unique)
>>>>>>
>>>>>> 2. In Progress/Open:
>>>>>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
>>>>>> - MRM-275 (add "remove old snapshots" Scheduler)
>>>>>> - MRM-294 (Repository purge feature for snapshots)
>>>>>> - MRM-329 (The Reports link gives an HTTP 500)
>>>>>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
>>>>>> - MRM-373 (Unable to delete the pre-configured example network
>>>>>> proxy)
>>>>>> - MRM-412 (Add support for maven 1 (legacy) request to access a
>>>>>> maven2 (default layout) repo )
>>>>>> - MRM-428 (Managed and remote repositories with same name causes
>>>>>> problems)
>>>>>> - MRM-429 (Find artifact does not work when the applet is disabled)
>>>>>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>>>>>>
>>>>>> Everyone okay with this? :)
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Deng
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>>
>
>
--
- Joakim Erdfelt
joakim@erdfelt.com
Open Source Software (OSS) Developer
Re: Archiva releases (Take 2)
Posted by Ludovic Maitre <lu...@free.fr>.
Hi Fabrice, all,
Thanks for your answers; so if you have succeeded deploying Archiva
(1.0-alpha-2 ?) on Tomcat and accessing the repository perhaps it's only
a deployment problem on my side, i will look more deeply in my config.
Also i hope that it was ok to discuss these on the dev list, perhaps
these are more userland issues/questions.
Good holidays,
Fabrice Bellingard wrote:
> Since I'm working on Archiva, I've always been testing it on Tomcat
> 5.5.23and I've never had a single problem (using the tips provided on
> the Wiki:
> http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat)
>
> I'll look at MRM-323 when I have some time (that is after my coming holidays
> :-))
>
> Fabrice.
>
> On 8/2/07, Brett Porter <br...@apache.org> wrote:
>
>> I'd be happy to run some tests on Tomcat post beta-1 as well. I've
>> spent way too much time battling these things in a past life not to
>> have learned something that might be helpful :)
>>
>> Anyone here deploying to something other than Tomcat? We have Jetty5
>> (via appserver) and 6 (via plugin) covered - I'm interested to know
>> if these issues are isolated to TC.
>>
>> - Brett
>>
>> On 02/08/2007, at 10:32 AM, Maria Odea Ching wrote:
>>
>>
>>> Yep, we also expect users to deploy Archiva standalone in
>>> production. So far, MRM-323 and all the other remaining Tomcat
>>> issues are scheduled for 1.0.x since most of them needs to be
>>> investigated further. I've looked at MRM-323 in jira and saw your
>>> findings for this issue. I'll take a look at it later on and
>>> "maybe" we could include this in beta-2 :)
>>>
>>>
>>> Thanks,
>>> Deng
>>>
>>>
>>> Ludovic Maitre wrote:
>>>
>>>> Hi Maria, all,
>>>>
>>>> Although i'm a new user of Archiva, i would like to know when in
>>>> the roadmap the team plan to fix issues related to running Archiva
>>>> inside Tomcat (issues like http://jira.codehaus.org/browse/
>>>> MRM-323 ) ? Is it something important for the team ? Did you
>>>> expect users to deploy Archiva standalone in production ?
>>>> Best regards,
>>>>
>>>> Maria Odea Ching wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> We (Brett, Joakim and I) have segregated the issues in Jira to
>>>>> prep for the upcoming 1.0 release (finally! :-) ). Anyway,
>>>>> there'll be two beta releases first before 1.0.
>>>>>
>>>>> So..here's the plan (excerpted from Brett):
>>>>> - finish all issues for 1.0-beta-1
>>>>> - then move on to 1.0-beta-2 issues for the next release
>>>>> - do a big bug bash to find the problems in it
>>>>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>>>>>
>>>>>
>>>>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
>>>>> Monday my time), and this will include the following:
>>>>> 1. Resolved/Closed:
>>>>> - MRM-290 (Ability to pre-configure the Jetty port in conf/
>>>>> plexus.xml)
>>>>> - MRM-326 (Adding/Editing repositories doesn't have validation)
>>>>> - MRM-425 (Search and Browse do not work for snapshots)
>>>>> - MRM-426 (Search does not work for snapshots because of
>>>>> different version values in index and database when the snapshot
>>>>> version is unique)
>>>>>
>>>>> 2. In Progress/Open:
>>>>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
>>>>> - MRM-275 (add "remove old snapshots" Scheduler)
>>>>> - MRM-294 (Repository purge feature for snapshots)
>>>>> - MRM-329 (The Reports link gives an HTTP 500)
>>>>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
>>>>> - MRM-373 (Unable to delete the pre-configured example network
>>>>> proxy)
>>>>> - MRM-412 (Add support for maven 1 (legacy) request to access a
>>>>> maven2 (default layout) repo )
>>>>> - MRM-428 (Managed and remote repositories with same name causes
>>>>> problems)
>>>>> - MRM-429 (Find artifact does not work when the applet is disabled)
>>>>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>>>>>
>>>>> Everyone okay with this? :)
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Deng
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>
>
--
Cordialement,
Ludo - http://www.ubik-products.com
---
"L'amour pour principe et l'ordre pour base; le progres pour but" (A.Comte)
Re: Archiva releases (Take 2)
Posted by Fabrice Bellingard <be...@gmail.com>.
Since I'm working on Archiva, I've always been testing it on Tomcat
5.5.23and I've never had a single problem (using the tips provided on
the Wiki:
http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat)
I'll look at MRM-323 when I have some time (that is after my coming holidays
:-))
Fabrice.
On 8/2/07, Brett Porter <br...@apache.org> wrote:
>
> I'd be happy to run some tests on Tomcat post beta-1 as well. I've
> spent way too much time battling these things in a past life not to
> have learned something that might be helpful :)
>
> Anyone here deploying to something other than Tomcat? We have Jetty5
> (via appserver) and 6 (via plugin) covered - I'm interested to know
> if these issues are isolated to TC.
>
> - Brett
>
> On 02/08/2007, at 10:32 AM, Maria Odea Ching wrote:
>
> > Yep, we also expect users to deploy Archiva standalone in
> > production. So far, MRM-323 and all the other remaining Tomcat
> > issues are scheduled for 1.0.x since most of them needs to be
> > investigated further. I've looked at MRM-323 in jira and saw your
> > findings for this issue. I'll take a look at it later on and
> > "maybe" we could include this in beta-2 :)
> >
> >
> > Thanks,
> > Deng
> >
> >
> > Ludovic Maitre wrote:
> >> Hi Maria, all,
> >>
> >> Although i'm a new user of Archiva, i would like to know when in
> >> the roadmap the team plan to fix issues related to running Archiva
> >> inside Tomcat (issues like http://jira.codehaus.org/browse/
> >> MRM-323 ) ? Is it something important for the team ? Did you
> >> expect users to deploy Archiva standalone in production ?
> >> Best regards,
> >>
> >> Maria Odea Ching wrote:
> >>> Hi All,
> >>>
> >>> We (Brett, Joakim and I) have segregated the issues in Jira to
> >>> prep for the upcoming 1.0 release (finally! :-) ). Anyway,
> >>> there'll be two beta releases first before 1.0.
> >>>
> >>> So..here's the plan (excerpted from Brett):
> >>> - finish all issues for 1.0-beta-1
> >>> - then move on to 1.0-beta-2 issues for the next release
> >>> - do a big bug bash to find the problems in it
> >>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
> >>>
> >>>
> >>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
> >>> Monday my time), and this will include the following:
> >>> 1. Resolved/Closed:
> >>> - MRM-290 (Ability to pre-configure the Jetty port in conf/
> >>> plexus.xml)
> >>> - MRM-326 (Adding/Editing repositories doesn't have validation)
> >>> - MRM-425 (Search and Browse do not work for snapshots)
> >>> - MRM-426 (Search does not work for snapshots because of
> >>> different version values in index and database when the snapshot
> >>> version is unique)
> >>>
> >>> 2. In Progress/Open:
> >>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
> >>> - MRM-275 (add "remove old snapshots" Scheduler)
> >>> - MRM-294 (Repository purge feature for snapshots)
> >>> - MRM-329 (The Reports link gives an HTTP 500)
> >>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
> >>> - MRM-373 (Unable to delete the pre-configured example network
> >>> proxy)
> >>> - MRM-412 (Add support for maven 1 (legacy) request to access a
> >>> maven2 (default layout) repo )
> >>> - MRM-428 (Managed and remote repositories with same name causes
> >>> problems)
> >>> - MRM-429 (Find artifact does not work when the applet is disabled)
> >>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
> >>>
> >>> Everyone okay with this? :)
> >>>
> >>>
> >>> Thanks,
> >>> Deng
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
>
Re: Archiva releases (Take 2)
Posted by Brett Porter <br...@apache.org>.
I'd be happy to run some tests on Tomcat post beta-1 as well. I've
spent way too much time battling these things in a past life not to
have learned something that might be helpful :)
Anyone here deploying to something other than Tomcat? We have Jetty5
(via appserver) and 6 (via plugin) covered - I'm interested to know
if these issues are isolated to TC.
- Brett
On 02/08/2007, at 10:32 AM, Maria Odea Ching wrote:
> Yep, we also expect users to deploy Archiva standalone in
> production. So far, MRM-323 and all the other remaining Tomcat
> issues are scheduled for 1.0.x since most of them needs to be
> investigated further. I've looked at MRM-323 in jira and saw your
> findings for this issue. I'll take a look at it later on and
> "maybe" we could include this in beta-2 :)
>
>
> Thanks,
> Deng
>
>
> Ludovic Maitre wrote:
>> Hi Maria, all,
>>
>> Although i'm a new user of Archiva, i would like to know when in
>> the roadmap the team plan to fix issues related to running Archiva
>> inside Tomcat (issues like http://jira.codehaus.org/browse/
>> MRM-323 ) ? Is it something important for the team ? Did you
>> expect users to deploy Archiva standalone in production ?
>> Best regards,
>>
>> Maria Odea Ching wrote:
>>> Hi All,
>>>
>>> We (Brett, Joakim and I) have segregated the issues in Jira to
>>> prep for the upcoming 1.0 release (finally! :-) ). Anyway,
>>> there'll be two beta releases first before 1.0.
>>>
>>> So..here's the plan (excerpted from Brett):
>>> - finish all issues for 1.0-beta-1
>>> - then move on to 1.0-beta-2 issues for the next release
>>> - do a big bug bash to find the problems in it
>>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>>>
>>>
>>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
>>> Monday my time), and this will include the following:
>>> 1. Resolved/Closed:
>>> - MRM-290 (Ability to pre-configure the Jetty port in conf/
>>> plexus.xml)
>>> - MRM-326 (Adding/Editing repositories doesn't have validation)
>>> - MRM-425 (Search and Browse do not work for snapshots)
>>> - MRM-426 (Search does not work for snapshots because of
>>> different version values in index and database when the snapshot
>>> version is unique)
>>>
>>> 2. In Progress/Open:
>>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
>>> - MRM-275 (add "remove old snapshots" Scheduler)
>>> - MRM-294 (Repository purge feature for snapshots)
>>> - MRM-329 (The Reports link gives an HTTP 500)
>>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
>>> - MRM-373 (Unable to delete the pre-configured example network
>>> proxy)
>>> - MRM-412 (Add support for maven 1 (legacy) request to access a
>>> maven2 (default layout) repo )
>>> - MRM-428 (Managed and remote repositories with same name causes
>>> problems)
>>> - MRM-429 (Find artifact does not work when the applet is disabled)
>>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>>>
>>> Everyone okay with this? :)
>>>
>>>
>>> Thanks,
>>> Deng
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
Re: Archiva releases (Take 2)
Posted by Maria Odea Ching <oc...@exist.com>.
Yep, we also expect users to deploy Archiva standalone in production. So
far, MRM-323 and all the other remaining Tomcat issues are scheduled for
1.0.x since most of them needs to be investigated further. I've looked
at MRM-323 in jira and saw your findings for this issue. I'll take a
look at it later on and "maybe" we could include this in beta-2 :)
Thanks,
Deng
Ludovic Maitre wrote:
> Hi Maria, all,
>
> Although i'm a new user of Archiva, i would like to know when in the
> roadmap the team plan to fix issues related to running Archiva inside
> Tomcat (issues like http://jira.codehaus.org/browse/MRM-323 ) ? Is it
> something important for the team ? Did you expect users to deploy
> Archiva standalone in production ?
> Best regards,
>
> Maria Odea Ching wrote:
>> Hi All,
>>
>> We (Brett, Joakim and I) have segregated the issues in Jira to prep
>> for the upcoming 1.0 release (finally! :-) ). Anyway, there'll be two
>> beta releases first before 1.0.
>>
>> So..here's the plan (excerpted from Brett):
>> - finish all issues for 1.0-beta-1
>> - then move on to 1.0-beta-2 issues for the next release
>> - do a big bug bash to find the problems in it
>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>>
>>
>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
>> Monday my time), and this will include the following:
>> 1. Resolved/Closed:
>> - MRM-290 (Ability to pre-configure the Jetty port in conf/plexus.xml)
>> - MRM-326 (Adding/Editing repositories doesn't have validation)
>> - MRM-425 (Search and Browse do not work for snapshots)
>> - MRM-426 (Search does not work for snapshots because of different
>> version values in index and database when the snapshot version is
>> unique)
>>
>> 2. In Progress/Open:
>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
>> - MRM-275 (add "remove old snapshots" Scheduler)
>> - MRM-294 (Repository purge feature for snapshots)
>> - MRM-329 (The Reports link gives an HTTP 500)
>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
>> - MRM-373 (Unable to delete the pre-configured example network proxy)
>> - MRM-412 (Add support for maven 1 (legacy) request to access a
>> maven2 (default layout) repo )
>> - MRM-428 (Managed and remote repositories with same name causes
>> problems)
>> - MRM-429 (Find artifact does not work when the applet is disabled)
>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>>
>> Everyone okay with this? :)
>>
>>
>> Thanks,
>> Deng
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Re: Archiva releases (Take 2)
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
For the record.
Archiva runs fine on jetty 5.x and 6.x.
- Joakim
Ludovic Maitre wrote:
> Hi Maria, all,
>
> Although i'm a new user of Archiva, i would like to know when in the
> roadmap the team plan to fix issues related to running Archiva inside
> Tomcat (issues like http://jira.codehaus.org/browse/MRM-323 ) ? Is it
> something important for the team ? Did you expect users to deploy
> Archiva standalone in production ?
> Best regards,
>
> Maria Odea Ching wrote:
>> Hi All,
>>
>> We (Brett, Joakim and I) have segregated the issues in Jira to prep
>> for the upcoming 1.0 release (finally! :-) ). Anyway, there'll be two
>> beta releases first before 1.0.
>>
>> So..here's the plan (excerpted from Brett):
>> - finish all issues for 1.0-beta-1
>> - then move on to 1.0-beta-2 issues for the next release
>> - do a big bug bash to find the problems in it
>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>>
>>
>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
>> Monday my time), and this will include the following:
>> 1. Resolved/Closed:
>> - MRM-290 (Ability to pre-configure the Jetty port in conf/plexus.xml)
>> - MRM-326 (Adding/Editing repositories doesn't have validation)
>> - MRM-425 (Search and Browse do not work for snapshots)
>> - MRM-426 (Search does not work for snapshots because of different
>> version values in index and database when the snapshot version is
>> unique)
>>
>> 2. In Progress/Open:
>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
>> - MRM-275 (add "remove old snapshots" Scheduler)
>> - MRM-294 (Repository purge feature for snapshots)
>> - MRM-329 (The Reports link gives an HTTP 500)
>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
>> - MRM-373 (Unable to delete the pre-configured example network proxy)
>> - MRM-412 (Add support for maven 1 (legacy) request to access a
>> maven2 (default layout) repo )
>> - MRM-428 (Managed and remote repositories with same name causes
>> problems)
>> - MRM-429 (Find artifact does not work when the applet is disabled)
>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>>
>> Everyone okay with this? :)
>>
>>
>> Thanks,
>> Deng
>>
>>
>>
>>
>>
>>
>>
>>
>
>
--
- Joakim Erdfelt
joakim@erdfelt.com
Open Source Software (OSS) Developer
Re: Archiva releases (Take 2)
Posted by Ludovic Maitre <lu...@free.fr>.
Hi Maria, all,
Although i'm a new user of Archiva, i would like to know when in the
roadmap the team plan to fix issues related to running Archiva inside
Tomcat (issues like http://jira.codehaus.org/browse/MRM-323 ) ? Is it
something important for the team ? Did you expect users to deploy
Archiva standalone in production ?
Best regards,
Maria Odea Ching wrote:
> Hi All,
>
> We (Brett, Joakim and I) have segregated the issues in Jira to prep
> for the upcoming 1.0 release (finally! :-) ). Anyway, there'll be two
> beta releases first before 1.0.
>
> So..here's the plan (excerpted from Brett):
> - finish all issues for 1.0-beta-1
> - then move on to 1.0-beta-2 issues for the next release
> - do a big bug bash to find the problems in it
> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>
>
> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
> Monday my time), and this will include the following:
> 1. Resolved/Closed:
> - MRM-290 (Ability to pre-configure the Jetty port in conf/plexus.xml)
> - MRM-326 (Adding/Editing repositories doesn't have validation)
> - MRM-425 (Search and Browse do not work for snapshots)
> - MRM-426 (Search does not work for snapshots because of different
> version values in index and database when the snapshot version is unique)
>
> 2. In Progress/Open:
> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
> - MRM-275 (add "remove old snapshots" Scheduler)
> - MRM-294 (Repository purge feature for snapshots)
> - MRM-329 (The Reports link gives an HTTP 500)
> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
> - MRM-373 (Unable to delete the pre-configured example network proxy)
> - MRM-412 (Add support for maven 1 (legacy) request to access a maven2
> (default layout) repo )
> - MRM-428 (Managed and remote repositories with same name causes
> problems)
> - MRM-429 (Find artifact does not work when the applet is disabled)
> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>
> Everyone okay with this? :)
>
>
> Thanks,
> Deng
>
>
>
>
>
>
>
>
--
Cordialement,
Ludo - http://www.ubik-products.com
---
"L'amour pour principe et l'ordre pour base; le progres pour but" (A.Comte)
Re: Archiva releases (Take 2)
Posted by Maria Odea Ching <oc...@exist.com>.
Ok, thanks Fabrice :)
I'll add that to the list.
-Deng
Fabrice Bellingard wrote:
> I've closed MRM-373 (Unable to delete the pre-configured example network
> proxy), which was no longer valid.
>
> Fabrice.
>
> On 8/1/07, Maria Odea Ching <oc...@exist.com> wrote:
>
>> Hi All,
>>
>> We (Brett, Joakim and I) have segregated the issues in Jira to prep for
>> the upcoming 1.0 release (finally! :-) ). Anyway, there'll be two beta
>> releases first before 1.0.
>>
>> So..here's the plan (excerpted from Brett):
>> - finish all issues for 1.0-beta-1
>> - then move on to 1.0-beta-2 issues for the next release
>> - do a big bug bash to find the problems in it
>> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>>
>>
>> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be Monday
>> my time), and this will include the following:
>> 1. Resolved/Closed:
>> - MRM-290 (Ability to pre-configure the Jetty port in conf/plexus.xml)
>> - MRM-326 (Adding/Editing repositories doesn't have validation)
>> - MRM-425 (Search and Browse do not work for snapshots)
>> - MRM-426 (Search does not work for snapshots because of different
>> version values in index and database when the snapshot version is unique)
>>
>> 2. In Progress/Open:
>> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
>> - MRM-275 (add "remove old snapshots" Scheduler)
>> - MRM-294 (Repository purge feature for snapshots)
>> - MRM-329 (The Reports link gives an HTTP 500)
>> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
>> - MRM-373 (Unable to delete the pre-configured example network proxy)
>> - MRM-412 (Add support for maven 1 (legacy) request to access a maven2
>> (default layout) repo )
>> - MRM-428 (Managed and remote repositories with same name causes problems)
>> - MRM-429 (Find artifact does not work when the applet is disabled)
>> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>>
>> Everyone okay with this? :)
>>
>>
>> Thanks,
>> Deng
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Re: Archiva releases (Take 2)
Posted by Fabrice Bellingard <be...@gmail.com>.
I've closed MRM-373 (Unable to delete the pre-configured example network
proxy), which was no longer valid.
Fabrice.
On 8/1/07, Maria Odea Ching <oc...@exist.com> wrote:
>
> Hi All,
>
> We (Brett, Joakim and I) have segregated the issues in Jira to prep for
> the upcoming 1.0 release (finally! :-) ). Anyway, there'll be two beta
> releases first before 1.0.
>
> So..here's the plan (excerpted from Brett):
> - finish all issues for 1.0-beta-1
> - then move on to 1.0-beta-2 issues for the next release
> - do a big bug bash to find the problems in it
> - decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
>
>
> Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be Monday
> my time), and this will include the following:
> 1. Resolved/Closed:
> - MRM-290 (Ability to pre-configure the Jetty port in conf/plexus.xml)
> - MRM-326 (Adding/Editing repositories doesn't have validation)
> - MRM-425 (Search and Browse do not work for snapshots)
> - MRM-426 (Search does not work for snapshots because of different
> version values in index and database when the snapshot version is unique)
>
> 2. In Progress/Open:
> - MRM-143 (Improve error reporting on corrupt jars, poms, etc)
> - MRM-275 (add "remove old snapshots" Scheduler)
> - MRM-294 (Repository purge feature for snapshots)
> - MRM-329 (The Reports link gives an HTTP 500)
> - MRM-347 (Undefined ${appserver.home} and ${appserver.base})
> - MRM-373 (Unable to delete the pre-configured example network proxy)
> - MRM-412 (Add support for maven 1 (legacy) request to access a maven2
> (default layout) repo )
> - MRM-428 (Managed and remote repositories with same name causes problems)
> - MRM-429 (Find artifact does not work when the applet is disabled)
> - MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
>
> Everyone okay with this? :)
>
>
> Thanks,
> Deng
>
>
>
>
>
>
>