You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Joakim Erdfelt <jo...@erdfelt.com> on 2007/04/26 02:15:31 UTC
[VOTE] Merge Archiva Database Branch to Trunk
Lots of work has been done in the archiva database branch in the past 2
months.
It has come time to start the merge back into trunk and get the help of
others to finish off the work.
I wanted to point people to the branch and let them take a look around,
and then vote.
As I see it we have 3 options.
option A [ ] Make the branch the new trunk.
option B [ ] Merge the branch into the existing trunk.
option C [ ] -1 Do not merge the branch into trunk.
I'll wait the usual 72 hours and tabulate the scores.
Scores will be tabulated around 1:00am Sunday UTC.
I favor option A personally, but I don't know what that will mean to
those people that have trunk currently checked out.
The Branch:
https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
The Good:
1) Completed Integration of JPOX Database into system.
2) Completely overhauled the repository scanning for performance,
availability, resilience, and capabilities.
3) Completely overhauled the reporting system for growth and use of the
database.
The Bad:
1) Admin screens have not yet been converted to the new configuration.
(that's a priority for me ATM)
2) Automatic Artifact relocation on proxied requests has not been
implemented.
3) Untested.
I'm eager to get the other devs involved ASAP.
While the vote is going on, I'll be alternating between Redback
development and Archiva Admin Screen work.
- Joakim Erdfelt
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Arnaud,
I would encourage you to not waste your time on that fix/patch (let me
attempt to explain why ...)
MRM-211 and MRM-212 have been corrected in the branch.
The entire policy handling mechanism has been overhauled in there.
In the branch, policies are defined in a property section in the
configuration.
<repository>
<policies>
<snapshots>disabled</snapshots>
<releases>disabled</releases>
<cache-failures>cache</cache-failures>
<checksum>fail</checksum>
</policies>
</repository>
The list of policies can grow this way.
Each policy is either a PreDownload or a PostDownload policy.
(determined by the policy impl).
Example, Checksum policy is a PostDownload policy with setting
possibilities of (ignored, fail, or fix).
The extension <-> type mappings have been overhauled in the branch too.
There is now a LegacyExtensionMapper and DefaultExtensionMapper objects
to handle that.
The branch also has a proper BidirectionalLayout mecahnism (unlike the 1
way version in maven components).
- Joakim
Arnaud HERITIER wrote:
> I'm testing Nicola's patch on the trunk and I wanted to apply them before
> the end of the week.
> I'm not sure that it's a good solution if you merge the branch.
> Did you have a look if there was a lot of changes in the trunk since you
> created the branch ?
>
> Arnaud
>
> On 26/04/07, Maria Odea Ching <oc...@exist.com> wrote:
>>
>> +1 option B [ ] Merge the branch into the existing trunk.
>>
>> Btw, great work on the branch!
>> Count me in for the other issues :)
>>
>> Thanks,
>> Deng
>>
>> Joakim Erdfelt wrote:
>> > Lots of work has been done in the archiva database branch in the past
>> > 2 months.
>> >
>> > It has come time to start the merge back into trunk and get the help
>> > of others to finish off the work.
>> >
>> > I wanted to point people to the branch and let them take a look
>> > around, and then vote.
>> >
>> > As I see it we have 3 options.
>> >
>> > option A [ ] Make the branch the new trunk.
>> > option B [ ] Merge the branch into the existing trunk.
>> > option C [ ] -1 Do not merge the branch into trunk.
>> >
>> > I'll wait the usual 72 hours and tabulate the scores.
>> > Scores will be tabulated around 1:00am Sunday UTC.
>> >
>> > I favor option A personally, but I don't know what that will mean to
>> > those people that have trunk currently checked out.
>> >
>> > The Branch:
>> >
>> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>>
>> >
>> >
>> > The Good:
>> > 1) Completed Integration of JPOX Database into system.
>> > 2) Completely overhauled the repository scanning for performance,
>> > availability, resilience, and capabilities.
>> > 3) Completely overhauled the reporting system for growth and use of
>> > the database.
>> >
>> > The Bad:
>> > 1) Admin screens have not yet been converted to the new configuration.
>> > (that's a priority for me ATM)
>> > 2) Automatic Artifact relocation on proxied requests has not been
>> > implemented.
>> > 3) Untested.
>> >
>> > I'm eager to get the other devs involved ASAP.
>> >
>> > While the vote is going on, I'll be alternating between Redback
>> > development and Archiva Admin Screen work.
>> >
>> > - Joakim Erdfelt
>> >
>> > !DSPAM:602,462fef3782972047432395!
>> >
>>
>>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Arnaud HERITIER <ah...@gmail.com>.
I'm testing Nicola's patch on the trunk and I wanted to apply them before
the end of the week.
I'm not sure that it's a good solution if you merge the branch.
Did you have a look if there was a lot of changes in the trunk since you
created the branch ?
Arnaud
On 26/04/07, Maria Odea Ching <oc...@exist.com> wrote:
>
> +1 option B [ ] Merge the branch into the existing trunk.
>
> Btw, great work on the branch!
> Count me in for the other issues :)
>
> Thanks,
> Deng
>
> Joakim Erdfelt wrote:
> > Lots of work has been done in the archiva database branch in the past
> > 2 months.
> >
> > It has come time to start the merge back into trunk and get the help
> > of others to finish off the work.
> >
> > I wanted to point people to the branch and let them take a look
> > around, and then vote.
> >
> > As I see it we have 3 options.
> >
> > option A [ ] Make the branch the new trunk.
> > option B [ ] Merge the branch into the existing trunk.
> > option C [ ] -1 Do not merge the branch into trunk.
> >
> > I'll wait the usual 72 hours and tabulate the scores.
> > Scores will be tabulated around 1:00am Sunday UTC.
> >
> > I favor option A personally, but I don't know what that will mean to
> > those people that have trunk currently checked out.
> >
> > The Branch:
> >
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
> >
> >
> > The Good:
> > 1) Completed Integration of JPOX Database into system.
> > 2) Completely overhauled the repository scanning for performance,
> > availability, resilience, and capabilities.
> > 3) Completely overhauled the reporting system for growth and use of
> > the database.
> >
> > The Bad:
> > 1) Admin screens have not yet been converted to the new configuration.
> > (that's a priority for me ATM)
> > 2) Automatic Artifact relocation on proxied requests has not been
> > implemented.
> > 3) Untested.
> >
> > I'm eager to get the other devs involved ASAP.
> >
> > While the vote is going on, I'll be alternating between Redback
> > development and Archiva Admin Screen work.
> >
> > - Joakim Erdfelt
> >
> > !DSPAM:602,462fef3782972047432395!
> >
>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Maria Odea Ching <oc...@exist.com>.
+1 option B [ ] Merge the branch into the existing trunk.
Btw, great work on the branch!
Count me in for the other issues :)
Thanks,
Deng
Joakim Erdfelt wrote:
> Lots of work has been done in the archiva database branch in the past
> 2 months.
>
> It has come time to start the merge back into trunk and get the help
> of others to finish off the work.
>
> I wanted to point people to the branch and let them take a look
> around, and then vote.
>
> As I see it we have 3 options.
>
> option A [ ] Make the branch the new trunk.
> option B [ ] Merge the branch into the existing trunk.
> option C [ ] -1 Do not merge the branch into trunk.
>
> I'll wait the usual 72 hours and tabulate the scores.
> Scores will be tabulated around 1:00am Sunday UTC.
>
> I favor option A personally, but I don't know what that will mean to
> those people that have trunk currently checked out.
>
> The Branch:
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>
>
> The Good:
> 1) Completed Integration of JPOX Database into system.
> 2) Completely overhauled the repository scanning for performance,
> availability, resilience, and capabilities.
> 3) Completely overhauled the reporting system for growth and use of
> the database.
>
> The Bad:
> 1) Admin screens have not yet been converted to the new configuration.
> (that's a priority for me ATM)
> 2) Automatic Artifact relocation on proxied requests has not been
> implemented.
> 3) Untested.
>
> I'm eager to get the other devs involved ASAP.
>
> While the vote is going on, I'll be alternating between Redback
> development and Archiva Admin Screen work.
>
> - Joakim Erdfelt
>
> !DSPAM:602,462fef3782972047432395!
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Wendy Smoak <ws...@gmail.com>.
On 4/26/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> Also, even if we go with option B (which seems to be leading the vote
> counts so far) the commit messages will not be lost, the svn log should
> still contain that information (if I'm not mistaken).
When I look at 'svn log' for a random part of the nmaven trunk (which
Shane has been branching and merging back) I only see:
wsmoak@apollo /cygdrive/c/svn/nmaven/components
$ svn log
------------------------------------------------------------------------
r521824 | sisbell | 2007-03-23 10:37:38 -0700 (Fri, 23 Mar 2007) | 1 line
Merge of SI_RUBY branch.
------------------------------------------------------------------------
r520983 | sisbell | 2007-03-21 12:50:36 -0700 (Wed, 21 Mar 2007) | 1 line
Merge of SI_IDE branch to the trunk.
------------------------------------------------------------------------
I'd have to go over to the branch to look at the individual commits
that explain what was changed and why. I'd prefer to have as much of
that history as possible available on the Archiva trunk.
--
Wendy
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Carlos doesn't need to worry, as the maven-meeper (or is it
archiva-meeper?) tree has remained untouched in the branch.
His changes there will remain current, in either approach.
Also, even if we go with option B (which seems to be leading the vote
counts so far) the commit messages will not be lost, the svn log should
still contain that information (if I'm not mistaken).
- Joakim
Wendy Smoak wrote:
> On 4/25/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
>
>> As I see it we have 3 options.
>>
>> option A [ ] Make the branch the new trunk.
>> option B [ ] Merge the branch into the existing trunk.
>> option C [ ] -1 Do not merge the branch into trunk.
>
> I haven't looked at the code, but based on the volume of commits and
> the summaries you've sent of far-reaching changes, I wonder if merging
> will even work. Also, I'd like to preserve the commit messages rather
> than have the svn log for trunk just say "merged rX:rY to trunk".
>
> So I'd go for A, move trunk over to a 0.9 branch, then move your
> branch onto trunk.
>
> We would probably need to bring back the module that Carlos uses to
> sync things to central. Are any of the other changes on trunk even
> relevant to the refactored branch?
>
> Arnaud, if you're willing to do the work, I'm still interested in an
> 0.9-alpha-2 build from what is now the trunk.
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Wendy Smoak <ws...@gmail.com>.
On 4/25/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> As I see it we have 3 options.
>
> option A [ ] Make the branch the new trunk.
> option B [ ] Merge the branch into the existing trunk.
> option C [ ] -1 Do not merge the branch into trunk.
I haven't looked at the code, but based on the volume of commits and
the summaries you've sent of far-reaching changes, I wonder if merging
will even work. Also, I'd like to preserve the commit messages rather
than have the svn log for trunk just say "merged rX:rY to trunk".
So I'd go for A, move trunk over to a 0.9 branch, then move your
branch onto trunk.
We would probably need to bring back the module that Carlos uses to
sync things to central. Are any of the other changes on trunk even
relevant to the refactored branch?
Arnaud, if you're willing to do the work, I'm still interested in an
0.9-alpha-2 build from what is now the trunk.
--
Wendy
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by nicolas de loof <ni...@gmail.com>.
+1 option B [ ] Merge the branch into the existing trunk.
Nico.
2007/4/26, Joakim Erdfelt <jo...@erdfelt.com>:
>
> Lots of work has been done in the archiva database branch in the past 2
> months.
>
> It has come time to start the merge back into trunk and get the help of
> others to finish off the work.
>
> I wanted to point people to the branch and let them take a look around,
> and then vote.
>
> As I see it we have 3 options.
>
> option A [ ] Make the branch the new trunk.
> option B [ ] Merge the branch into the existing trunk.
> option C [ ] -1 Do not merge the branch into trunk.
>
> I'll wait the usual 72 hours and tabulate the scores.
> Scores will be tabulated around 1:00am Sunday UTC.
>
> I favor option A personally, but I don't know what that will mean to
> those people that have trunk currently checked out.
>
> The Branch:
>
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>
> The Good:
> 1) Completed Integration of JPOX Database into system.
> 2) Completely overhauled the repository scanning for performance,
> availability, resilience, and capabilities.
> 3) Completely overhauled the reporting system for growth and use of the
> database.
>
> The Bad:
> 1) Admin screens have not yet been converted to the new configuration.
> (that's a priority for me ATM)
> 2) Automatic Artifact relocation on proxied requests has not been
> implemented.
> 3) Untested.
>
> I'm eager to get the other devs involved ASAP.
>
> While the vote is going on, I'll be alternating between Redback
> development and Archiva Admin Screen work.
>
> - Joakim Erdfelt
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Arnaud HERITIER <ah...@gmail.com>.
I'll try your branch in parallel of the trunk patched but I fear to find
somebugs and to use the trunk for some weeks.
I'll give you my feedback soon.
Arnaud
On 26/04/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
>
> Please try again.
>
> All of the unit tests now work on windows.
>
> - Joakim
>
> Emmanuel Venisse wrote:
> > Option C: Tests don't work on windows so I can't test it.
> >
> > When they'll be fixed, I'll be for Option B.
> >
> > Emmanuel
> >
> > Joakim Erdfelt a écrit :
> >> Lots of work has been done in the archiva database branch in the past
> >> 2 months.
> >>
> >> It has come time to start the merge back into trunk and get the help
> >> of others to finish off the work.
> >>
> >> I wanted to point people to the branch and let them take a look
> >> around, and then vote.
> >>
> >> As I see it we have 3 options.
> >>
> >> option A [ ] Make the branch the new trunk.
> >> option B [ ] Merge the branch into the existing trunk.
> >> option C [ ] -1 Do not merge the branch into trunk.
> >>
> >> I'll wait the usual 72 hours and tabulate the scores.
> >> Scores will be tabulated around 1:00am Sunday UTC.
> >>
> >> I favor option A personally, but I don't know what that will mean to
> >> those people that have trunk currently checked out.
> >>
> >> The Branch:
> >>
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
> >>
> >>
> >> The Good:
> >> 1) Completed Integration of JPOX Database into system.
> >> 2) Completely overhauled the repository scanning for performance,
> >> availability, resilience, and capabilities.
> >> 3) Completely overhauled the reporting system for growth and use of
> >> the database.
> >>
> >> The Bad:
> >> 1) Admin screens have not yet been converted to the new
> >> configuration. (that's a priority for me ATM)
> >> 2) Automatic Artifact relocation on proxied requests has not been
> >> implemented.
> >> 3) Untested.
> >>
> >> I'm eager to get the other devs involved ASAP.
> >>
> >> While the vote is going on, I'll be alternating between Redback
> >> development and Archiva Admin Screen work.
> >>
> >> - Joakim Erdfelt
> >>
> >>
> >>
> >
>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Brett Porter <br...@apache.org>.
Please do A, but only after reviewing the changes on trunk since you
branched and applying anything that still makes sense (or adapting
it). We don't want to lose anything (and there have been relevant
changes - even last time I checked)
You're going to have trouble tabulating these 'votes', but that's ok.
It looks enough like consensus.
- Brett
On 30/04/2007, at 1:33 AM, Jesse McConnell wrote:
> +1 for option A, to move the branch to the trunk, I have worked on the
> code on the branch a bit and I find it very sanely organized and very
> extensible in parts dealing with repository scanning and whatnot. I
> think within a few days of usage we'll be able to iron out the
> majority of webapp oddities and there is a drive here to get some
> alpha releases going of both continuum and archiva so I think there is
> some momentum here...
>
> nice job with it joakim
>
> jesse
>
> On 4/27/07, nicolas de loof <ni...@gmail.com> wrote:
>> >
>> >
>> > An 0.9 release is not intended to attract users, it's intended
>> to deal
>> > with the fact that it already *has* users, and should have been
>> > officially released a long time ago.
>> >
>> > I'm not planning to make a big deal of it, a quiet mention on
>> the user
>> > list and a link at the bottom of the download page is plenty.
>> > Personally, I have this code in production and would like to see
>> this
>> > line of development nicely wrapped up rather than just abandoned.
>>
>>
>>
>> I also use this codebase for my corporate job and will contribute to
>> maintain supported features in future releases. I just don't
>> understand why
>> a "0.9" release would change about the trunk code to be maintained
>> or not.
>> Do you just mean that having a (pre)release would make the supported
>> features included in the roadmap ? We still have to re-code them
>> in the
>> branch-code.
>>
>>
>> --
>> > Wendy
>> >
>>
>
>
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Jesse McConnell <jm...@apache.org>.
+1 for option A, to move the branch to the trunk, I have worked on the
code on the branch a bit and I find it very sanely organized and very
extensible in parts dealing with repository scanning and whatnot. I
think within a few days of usage we'll be able to iron out the
majority of webapp oddities and there is a drive here to get some
alpha releases going of both continuum and archiva so I think there is
some momentum here...
nice job with it joakim
jesse
On 4/27/07, nicolas de loof <ni...@gmail.com> wrote:
> >
> >
> > An 0.9 release is not intended to attract users, it's intended to deal
> > with the fact that it already *has* users, and should have been
> > officially released a long time ago.
> >
> > I'm not planning to make a big deal of it, a quiet mention on the user
> > list and a link at the bottom of the download page is plenty.
> > Personally, I have this code in production and would like to see this
> > line of development nicely wrapped up rather than just abandoned.
>
>
>
> I also use this codebase for my corporate job and will contribute to
> maintain supported features in future releases. I just don't understand why
> a "0.9" release would change about the trunk code to be maintained or not.
> Do you just mean that having a (pre)release would make the supported
> features included in the roadmap ? We still have to re-code them in the
> branch-code.
>
>
> --
> > Wendy
> >
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by nicolas de loof <ni...@gmail.com>.
>
>
> An 0.9 release is not intended to attract users, it's intended to deal
> with the fact that it already *has* users, and should have been
> officially released a long time ago.
>
> I'm not planning to make a big deal of it, a quiet mention on the user
> list and a link at the bottom of the download page is plenty.
> Personally, I have this code in production and would like to see this
> line of development nicely wrapped up rather than just abandoned.
I also use this codebase for my corporate job and will contribute to
maintain supported features in future releases. I just don't understand why
a "0.9" release would change about the trunk code to be maintained or not.
Do you just mean that having a (pre)release would make the supported
features included in the roadmap ? We still have to re-code them in the
branch-code.
--
> Wendy
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Wendy Smoak <ws...@gmail.com>.
On 4/27/07, nicolas de loof <ni...@gmail.com> wrote:
> According to this I would vote for option A (move branch to trunk).
>
> Hard refactoring has been made on branch, and trunk is now only a demo of
> what archiva may look like some day. Releasing archiva 0.9 from trunk, even
> in alpha, is not a good idea IMHO as this will not reflect the real
> development status. Maybe I missundertand "alpha" keyword.
An 0.9 release is not intended to attract users, it's intended to deal
with the fact that it already *has* users, and should have been
officially released a long time ago.
I'm not planning to make a big deal of it, a quiet mention on the user
list and a link at the bottom of the download page is plenty.
Personally, I have this code in production and would like to see this
line of development nicely wrapped up rather than just abandoned.
--
Wendy
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by nicolas de loof <ni...@gmail.com>.
According to this I would vote for option A (move branch to trunk).
Hard refactoring has been made on branch, and trunk is now only a demo of
what archiva may look like some day. Releasing archiva 0.9 from trunk, even
in alpha, is not a good idea IMHO as this will not reflect the real
development status. Maybe I missundertand "alpha" keyword.
I also would like a archiva release to come out. Having a working app from
the branch with limited features would be better IMHO than publishing some
"alpha" with features that have been dropped from the codebase.
Nico
2007/4/27, Emmanuel Venisse <em...@venisse.net>:
>
>
>
> nicolas de loof a écrit :
> > 2007/4/27, Emmanuel Venisse <em...@venisse.net>:
> >>
> >>
> >>
> >> nicolas de loof a écrit :
> >> > I just checked out the branch and ran mvn install. I got all test
> >> failures
> >> > for Archiva Database (on windows 2000)
> >>
> >> Can you send the test outputs? All build fine on linux and Win XP.
> >
> >
> >
> > [solved]
> > as I'm running behind archiva configured <mirrorOf>*, and current
> archiva
> > trunk doesn't update snapshots, my snapshots dependencies were not up to
> > date.
> >
> > I now can build the branch and deploy it as expected on tomcat with a
> newly
> > created db.
> >
> >
> > I just can't access admin space so cannot do any test to check for
> > supported
> > features...
> >
> > settings
> > ->
> >
> > java.lang.NullPointerException:
> >
> org.apache.maven.archiva.web.action.admin.RepositoriesAction.setServletRequest
> (RepositoriesAction.java:109)
> >
> >
> > managed or proxied repositories
> > ->
> >
> > There is no Action mapped for namespace /admin and action name
> > managedRepositories.
> >
> >
> >
> > Did I miss something ?
> > Is this expected to work ?
> >
>
> managedRepositories and proxiedRepositories actions don't exist now and
> are replaced by repositories action like the settings link.
> I have the same NPE but I think joakim doesn't have finished this part as
> he worked on it yesterday.
>
> I get an other NPE on
> org.apache.maven.archiva.scheduled.RepositoryTaskJob.execute(
> RepositoryTaskJob.java:59)
>
> Emmanuel
>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
nicolas de loof a écrit :
> 2007/4/27, Emmanuel Venisse <em...@venisse.net>:
>>
>>
>>
>> nicolas de loof a écrit :
>> > I just checked out the branch and ran mvn install. I got all test
>> failures
>> > for Archiva Database (on windows 2000)
>>
>> Can you send the test outputs? All build fine on linux and Win XP.
>
>
>
> [solved]
> as I'm running behind archiva configured <mirrorOf>*, and current archiva
> trunk doesn't update snapshots, my snapshots dependencies were not up to
> date.
>
> I now can build the branch and deploy it as expected on tomcat with a newly
> created db.
>
>
> I just can't access admin space so cannot do any test to check for
> supported
> features...
>
> settings
> ->
>
> java.lang.NullPointerException:
> org.apache.maven.archiva.web.action.admin.RepositoriesAction.setServletRequest(RepositoriesAction.java:109)
>
>
> managed or proxied repositories
> ->
>
> There is no Action mapped for namespace /admin and action name
> managedRepositories.
>
>
>
> Did I miss something ?
> Is this expected to work ?
>
managedRepositories and proxiedRepositories actions don't exist now and are replaced by repositories action like the settings link.
I have the same NPE but I think joakim doesn't have finished this part as he worked on it yesterday.
I get an other NPE on org.apache.maven.archiva.scheduled.RepositoryTaskJob.execute(RepositoryTaskJob.java:59)
Emmanuel
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by nicolas de loof <ni...@gmail.com>.
2007/4/27, Emmanuel Venisse <em...@venisse.net>:
>
>
>
> nicolas de loof a écrit :
> > I just checked out the branch and ran mvn install. I got all test
> failures
> > for Archiva Database (on windows 2000)
>
> Can you send the test outputs? All build fine on linux and Win XP.
[solved]
as I'm running behind archiva configured <mirrorOf>*, and current archiva
trunk doesn't update snapshots, my snapshots dependencies were not up to
date.
I now can build the branch and deploy it as expected on tomcat with a newly
created db.
I just can't access admin space so cannot do any test to check for supported
features...
settings
->
java.lang.NullPointerException:
org.apache.maven.archiva.web.action.admin.RepositoriesAction.setServletRequest(RepositoriesAction.java:109)
managed or proxied repositories
->
There is no Action mapped for namespace /admin and action name
managedRepositories.
Did I miss something ?
Is this expected to work ?
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
nicolas de loof a écrit :
> I just checked out the branch and ran mvn install. I got all test failures
> for Archiva Database (on windows 2000)
Can you send the test outputs? All build fine on linux and Win XP.
>
> I then built with "-Dmaven.test.skip=true" and deployed on my local tomcat
> (with old database deleted)
>
> Got some funy ascii-art in logs, but some errors
I like the alpaca :)
>
> "org.apache.maven.archiva.database.ArchivaDatabaseException: Error in JDO
> during
> get of Database object id [internal] of type
> org.apache.maven.archiva.model.Arch
> ivaRepositoryModel using no fetch-group"
>
> .. and accessing localhost:8080/archiva :
>
> Caught Exception while registering Interceptor class
> pssEnvironmentCheckInterceptor - [unknown location]
> org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:152)
>
> ...
What is the revision you use? This morning I updated few dependencies then started Archiva without pb. Only few NPE in the scheduler and repositories screens that didn't work.
Emmanuel
>
>
> Maybe the database refactoring is required, but IMHO the current
> branch isn't ready for becoming the trunk ...
>
>
>
>
>
>
> 2007/4/27, Emmanuel Venisse <em...@venisse.net>:
>>
>> It's ok now, thanks.
>>
>> The branch seems to be good and well organized.
>> Even if I found some NPE when I used the webapp, I'm +1 to use it as
>> trunk.
>>
>> I don't think you'll can do option B easily, so I vote to option A. You
>> can move the actual trunk to branches/archiva-0.9.x until the new
>> trunk is
>> stable.
>>
>> Emmanuel
>>
>> Joakim Erdfelt a écrit :
>> > Please try again.
>> >
>> > All of the unit tests now work on windows.
>> >
>> > - Joakim
>> >
>> > Emmanuel Venisse wrote:
>> >> Option C: Tests don't work on windows so I can't test it.
>> >>
>> >> When they'll be fixed, I'll be for Option B.
>> >>
>> >> Emmanuel
>> >>
>> >> Joakim Erdfelt a écrit :
>> >>> Lots of work has been done in the archiva database branch in the past
>> >>> 2 months.
>> >>>
>> >>> It has come time to start the merge back into trunk and get the help
>> >>> of others to finish off the work.
>> >>>
>> >>> I wanted to point people to the branch and let them take a look
>> >>> around, and then vote.
>> >>>
>> >>> As I see it we have 3 options.
>> >>>
>> >>> option A [ ] Make the branch the new trunk.
>> >>> option B [ ] Merge the branch into the existing trunk.
>> >>> option C [ ] -1 Do not merge the branch into trunk.
>> >>>
>> >>> I'll wait the usual 72 hours and tabulate the scores.
>> >>> Scores will be tabulated around 1:00am Sunday UTC.
>> >>>
>> >>> I favor option A personally, but I don't know what that will mean to
>> >>> those people that have trunk currently checked out.
>> >>>
>> >>> The Branch:
>> >>>
>> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>>
>> >>>
>> >>>
>> >>> The Good:
>> >>> 1) Completed Integration of JPOX Database into system.
>> >>> 2) Completely overhauled the repository scanning for performance,
>> >>> availability, resilience, and capabilities.
>> >>> 3) Completely overhauled the reporting system for growth and use of
>> >>> the database.
>> >>>
>> >>> The Bad:
>> >>> 1) Admin screens have not yet been converted to the new
>> >>> configuration. (that's a priority for me ATM)
>> >>> 2) Automatic Artifact relocation on proxied requests has not been
>> >>> implemented.
>> >>> 3) Untested.
>> >>>
>> >>> I'm eager to get the other devs involved ASAP.
>> >>>
>> >>> While the vote is going on, I'll be alternating between Redback
>> >>> development and Archiva Admin Screen work.
>> >>>
>> >>> - Joakim Erdfelt
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> >
>> >
>>
>>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
the release plugin support to create releases from a branch.
In the next nights (more probably next days ;) ), I'll modify the release plugin to create branches from a trunk or a tag and update all version in the new branch. (MRELEASE-226)
Emmanuel
Arnaud HERITIER a écrit :
> but ....
> the release plugin doesn't support to create releases from a branch :-(
> Emmanuel, what are you doing for the next nights ?? ;-)
>
> Arnaud
>
> On 27/04/07, Arnaud HERITIER <ah...@gmail.com> wrote:
>>
>> I vote A. We switch the branch and the trunk.
>> I'll apply Nicolas' patches on this branch and we'll release a new
>> version.
>> What it is important is to document it on the web site to inform our
>> users
>> that the trunk isn't stable and that we released some alpha.
>>
>> Arnaud
>>
>> On 27/04/07, nicolas de loof <ni...@gmail.com> wrote:
>> >
>> > I just checked out the branch and ran mvn install. I got all test
>> > failures
>> > for Archiva Database (on windows 2000)
>> >
>> > I then built with "-Dmaven.test.skip=true" and deployed on my local
>> > tomcat
>> > (with old database deleted)
>> >
>> > Got some funy ascii-art in logs, but some errors
>> >
>> > "org.apache.maven.archiva.database.ArchivaDatabaseException: Error in
>> > JDO
>> > during
>> > get of Database object id [internal] of type
>> > org.apache.maven.archiva.model.Arch
>> > ivaRepositoryModel using no fetch-group"
>> >
>> > .. and accessing localhost:8080/archiva :
>> >
>> > Caught Exception while registering Interceptor class
>> > pssEnvironmentCheckInterceptor - [unknown location]
>> >
>> org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(
>> > PlexusObjectFactory.java:152)
>> > ...
>> >
>> >
>> > Maybe the database refactoring is required, but IMHO the current
>> > branch isn't ready for becoming the trunk ...
>> >
>> >
>> >
>> >
>> >
>> >
>> > 2007/4/27, Emmanuel Venisse <em...@venisse.net>:
>> > >
>> > > It's ok now, thanks.
>> > >
>> > > The branch seems to be good and well organized.
>> > > Even if I found some NPE when I used the webapp, I'm +1 to use it as
>> > > trunk.
>> > >
>> > > I don't think you'll can do option B easily, so I vote to option A.
>> > You
>> > > can move the actual trunk to branches/archiva- 0.9.x until the new
>> > trunk is
>> > > stable.
>> > >
>> > > Emmanuel
>> > >
>> > > Joakim Erdfelt a écrit :
>> > > > Please try again.
>> > > >
>> > > > All of the unit tests now work on windows.
>> > > >
>> > > > - Joakim
>> > > >
>> > > > Emmanuel Venisse wrote:
>> > > >> Option C: Tests don't work on windows so I can't test it.
>> > > >>
>> > > >> When they'll be fixed, I'll be for Option B.
>> > > >>
>> > > >> Emmanuel
>> > > >>
>> > > >> Joakim Erdfelt a écrit :
>> > > >>> Lots of work has been done in the archiva database branch in the
>> > past
>> > > >>> 2 months.
>> > > >>>
>> > > >>> It has come time to start the merge back into trunk and get the
>> > help
>> > > >>> of others to finish off the work.
>> > > >>>
>> > > >>> I wanted to point people to the branch and let them take a look
>> > > >>> around, and then vote.
>> > > >>>
>> > > >>> As I see it we have 3 options.
>> > > >>>
>> > > >>> option A [ ] Make the branch the new trunk.
>> > > >>> option B [ ] Merge the branch into the existing trunk.
>> > > >>> option C [ ] -1 Do not merge the branch into trunk.
>> > > >>>
>> > > >>> I'll wait the usual 72 hours and tabulate the scores.
>> > > >>> Scores will be tabulated around 1:00am Sunday UTC.
>> > > >>>
>> > > >>> I favor option A personally, but I don't know what that will mean
>> > to
>> > > >>> those people that have trunk currently checked out.
>> > > >>>
>> > > >>> The Branch:
>> > > >>>
>> > >
>> >
>> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>>
>> > > >>>
>> > > >>>
>> > > >>> The Good:
>> > > >>> 1) Completed Integration of JPOX Database into system.
>> > > >>> 2) Completely overhauled the repository scanning for performance,
>> > > >>> availability, resilience, and capabilities.
>> > > >>> 3) Completely overhauled the reporting system for growth and use
>> > of
>> > > >>> the database.
>> > > >>>
>> > > >>> The Bad:
>> > > >>> 1) Admin screens have not yet been converted to the new
>> > > >>> configuration. (that's a priority for me ATM)
>> > > >>> 2) Automatic Artifact relocation on proxied requests has not been
>> > > >>> implemented.
>> > > >>> 3) Untested.
>> > > >>>
>> > > >>> I'm eager to get the other devs involved ASAP.
>> > > >>>
>> > > >>> While the vote is going on, I'll be alternating between Redback
>> > > >>> development and Archiva Admin Screen work.
>> > > >>>
>> > > >>> - Joakim Erdfelt
>> > > >>>
>> > > >>>
>> > > >>>
>> > > >>
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>>
>>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Arnaud HERITIER <ah...@gmail.com>.
but ....
the release plugin doesn't support to create releases from a branch :-(
Emmanuel, what are you doing for the next nights ?? ;-)
Arnaud
On 27/04/07, Arnaud HERITIER <ah...@gmail.com> wrote:
>
> I vote A. We switch the branch and the trunk.
> I'll apply Nicolas' patches on this branch and we'll release a new
> version.
> What it is important is to document it on the web site to inform our users
> that the trunk isn't stable and that we released some alpha.
>
> Arnaud
>
> On 27/04/07, nicolas de loof <ni...@gmail.com> wrote:
> >
> > I just checked out the branch and ran mvn install. I got all test
> > failures
> > for Archiva Database (on windows 2000)
> >
> > I then built with "-Dmaven.test.skip=true" and deployed on my local
> > tomcat
> > (with old database deleted)
> >
> > Got some funy ascii-art in logs, but some errors
> >
> > "org.apache.maven.archiva.database.ArchivaDatabaseException: Error in
> > JDO
> > during
> > get of Database object id [internal] of type
> > org.apache.maven.archiva.model.Arch
> > ivaRepositoryModel using no fetch-group"
> >
> > .. and accessing localhost:8080/archiva :
> >
> > Caught Exception while registering Interceptor class
> > pssEnvironmentCheckInterceptor - [unknown location]
> > org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(
> > PlexusObjectFactory.java:152)
> > ...
> >
> >
> > Maybe the database refactoring is required, but IMHO the current
> > branch isn't ready for becoming the trunk ...
> >
> >
> >
> >
> >
> >
> > 2007/4/27, Emmanuel Venisse <em...@venisse.net>:
> > >
> > > It's ok now, thanks.
> > >
> > > The branch seems to be good and well organized.
> > > Even if I found some NPE when I used the webapp, I'm +1 to use it as
> > > trunk.
> > >
> > > I don't think you'll can do option B easily, so I vote to option A.
> > You
> > > can move the actual trunk to branches/archiva- 0.9.x until the new
> > trunk is
> > > stable.
> > >
> > > Emmanuel
> > >
> > > Joakim Erdfelt a écrit :
> > > > Please try again.
> > > >
> > > > All of the unit tests now work on windows.
> > > >
> > > > - Joakim
> > > >
> > > > Emmanuel Venisse wrote:
> > > >> Option C: Tests don't work on windows so I can't test it.
> > > >>
> > > >> When they'll be fixed, I'll be for Option B.
> > > >>
> > > >> Emmanuel
> > > >>
> > > >> Joakim Erdfelt a écrit :
> > > >>> Lots of work has been done in the archiva database branch in the
> > past
> > > >>> 2 months.
> > > >>>
> > > >>> It has come time to start the merge back into trunk and get the
> > help
> > > >>> of others to finish off the work.
> > > >>>
> > > >>> I wanted to point people to the branch and let them take a look
> > > >>> around, and then vote.
> > > >>>
> > > >>> As I see it we have 3 options.
> > > >>>
> > > >>> option A [ ] Make the branch the new trunk.
> > > >>> option B [ ] Merge the branch into the existing trunk.
> > > >>> option C [ ] -1 Do not merge the branch into trunk.
> > > >>>
> > > >>> I'll wait the usual 72 hours and tabulate the scores.
> > > >>> Scores will be tabulated around 1:00am Sunday UTC.
> > > >>>
> > > >>> I favor option A personally, but I don't know what that will mean
> > to
> > > >>> those people that have trunk currently checked out.
> > > >>>
> > > >>> The Branch:
> > > >>>
> > >
> > https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
> > > >>>
> > > >>>
> > > >>> The Good:
> > > >>> 1) Completed Integration of JPOX Database into system.
> > > >>> 2) Completely overhauled the repository scanning for performance,
> > > >>> availability, resilience, and capabilities.
> > > >>> 3) Completely overhauled the reporting system for growth and use
> > of
> > > >>> the database.
> > > >>>
> > > >>> The Bad:
> > > >>> 1) Admin screens have not yet been converted to the new
> > > >>> configuration. (that's a priority for me ATM)
> > > >>> 2) Automatic Artifact relocation on proxied requests has not been
> > > >>> implemented.
> > > >>> 3) Untested.
> > > >>>
> > > >>> I'm eager to get the other devs involved ASAP.
> > > >>>
> > > >>> While the vote is going on, I'll be alternating between Redback
> > > >>> development and Archiva Admin Screen work.
> > > >>>
> > > >>> - Joakim Erdfelt
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by nicolas de loof <ni...@gmail.com>.
+1
current trunk will then be released as a "proof-of-concept" or demo, as the
code base and configuration changes for 1.0.
2007/4/27, Arnaud HERITIER <ah...@gmail.com>:
>
> I vote A. We switch the branch and the trunk.
> I'll apply Nicolas' patches on this branch and we'll release a new
> version.
> What it is important is to document it on the web site to inform our users
> that the trunk isn't stable and that we released some alpha.
>
> Arnaud
>
> On 27/04/07, nicolas de loof <ni...@gmail.com> wrote:
> >
> > I just checked out the branch and ran mvn install. I got all test
> failures
> > for Archiva Database (on windows 2000)
> >
> > I then built with "-Dmaven.test.skip=true" and deployed on my local
> tomcat
> > (with old database deleted)
> >
> > Got some funy ascii-art in logs, but some errors
> >
> > "org.apache.maven.archiva.database.ArchivaDatabaseException: Error in
> JDO
> > during
> > get of Database object id [internal] of type
> > org.apache.maven.archiva.model.Arch
> > ivaRepositoryModel using no fetch-group"
> >
> > .. and accessing localhost:8080/archiva :
> >
> > Caught Exception while registering Interceptor class
> > pssEnvironmentCheckInterceptor - [unknown location]
> > org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(
> > PlexusObjectFactory.java:152)
> > ...
> >
> >
> > Maybe the database refactoring is required, but IMHO the current
> > branch isn't ready for becoming the trunk ...
> >
> >
> >
> >
> >
> >
> > 2007/4/27, Emmanuel Venisse <em...@venisse.net>:
> > >
> > > It's ok now, thanks.
> > >
> > > The branch seems to be good and well organized.
> > > Even if I found some NPE when I used the webapp, I'm +1 to use it as
> > > trunk.
> > >
> > > I don't think you'll can do option B easily, so I vote to option A.
> You
> > > can move the actual trunk to branches/archiva-0.9.x until the new
> trunk
> > is
> > > stable.
> > >
> > > Emmanuel
> > >
> > > Joakim Erdfelt a écrit :
> > > > Please try again.
> > > >
> > > > All of the unit tests now work on windows.
> > > >
> > > > - Joakim
> > > >
> > > > Emmanuel Venisse wrote:
> > > >> Option C: Tests don't work on windows so I can't test it.
> > > >>
> > > >> When they'll be fixed, I'll be for Option B.
> > > >>
> > > >> Emmanuel
> > > >>
> > > >> Joakim Erdfelt a écrit :
> > > >>> Lots of work has been done in the archiva database branch in the
> > past
> > > >>> 2 months.
> > > >>>
> > > >>> It has come time to start the merge back into trunk and get the
> help
> > > >>> of others to finish off the work.
> > > >>>
> > > >>> I wanted to point people to the branch and let them take a look
> > > >>> around, and then vote.
> > > >>>
> > > >>> As I see it we have 3 options.
> > > >>>
> > > >>> option A [ ] Make the branch the new trunk.
> > > >>> option B [ ] Merge the branch into the existing trunk.
> > > >>> option C [ ] -1 Do not merge the branch into trunk.
> > > >>>
> > > >>> I'll wait the usual 72 hours and tabulate the scores.
> > > >>> Scores will be tabulated around 1:00am Sunday UTC.
> > > >>>
> > > >>> I favor option A personally, but I don't know what that will mean
> to
> > > >>> those people that have trunk currently checked out.
> > > >>>
> > > >>> The Branch:
> > > >>>
> > >
> >
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
> > > >>>
> > > >>>
> > > >>> The Good:
> > > >>> 1) Completed Integration of JPOX Database into system.
> > > >>> 2) Completely overhauled the repository scanning for performance,
> > > >>> availability, resilience, and capabilities.
> > > >>> 3) Completely overhauled the reporting system for growth and use
> of
> > > >>> the database.
> > > >>>
> > > >>> The Bad:
> > > >>> 1) Admin screens have not yet been converted to the new
> > > >>> configuration. (that's a priority for me ATM)
> > > >>> 2) Automatic Artifact relocation on proxied requests has not been
> > > >>> implemented.
> > > >>> 3) Untested.
> > > >>>
> > > >>> I'm eager to get the other devs involved ASAP.
> > > >>>
> > > >>> While the vote is going on, I'll be alternating between Redback
> > > >>> development and Archiva Admin Screen work.
> > > >>>
> > > >>> - Joakim Erdfelt
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Arnaud HERITIER <ah...@gmail.com>.
I vote A. We switch the branch and the trunk.
I'll apply Nicolas' patches on this branch and we'll release a new version.
What it is important is to document it on the web site to inform our users
that the trunk isn't stable and that we released some alpha.
Arnaud
On 27/04/07, nicolas de loof <ni...@gmail.com> wrote:
>
> I just checked out the branch and ran mvn install. I got all test failures
> for Archiva Database (on windows 2000)
>
> I then built with "-Dmaven.test.skip=true" and deployed on my local tomcat
> (with old database deleted)
>
> Got some funy ascii-art in logs, but some errors
>
> "org.apache.maven.archiva.database.ArchivaDatabaseException: Error in JDO
> during
> get of Database object id [internal] of type
> org.apache.maven.archiva.model.Arch
> ivaRepositoryModel using no fetch-group"
>
> .. and accessing localhost:8080/archiva :
>
> Caught Exception while registering Interceptor class
> pssEnvironmentCheckInterceptor - [unknown location]
> org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(
> PlexusObjectFactory.java:152)
> ...
>
>
> Maybe the database refactoring is required, but IMHO the current
> branch isn't ready for becoming the trunk ...
>
>
>
>
>
>
> 2007/4/27, Emmanuel Venisse <em...@venisse.net>:
> >
> > It's ok now, thanks.
> >
> > The branch seems to be good and well organized.
> > Even if I found some NPE when I used the webapp, I'm +1 to use it as
> > trunk.
> >
> > I don't think you'll can do option B easily, so I vote to option A. You
> > can move the actual trunk to branches/archiva-0.9.x until the new trunk
> is
> > stable.
> >
> > Emmanuel
> >
> > Joakim Erdfelt a écrit :
> > > Please try again.
> > >
> > > All of the unit tests now work on windows.
> > >
> > > - Joakim
> > >
> > > Emmanuel Venisse wrote:
> > >> Option C: Tests don't work on windows so I can't test it.
> > >>
> > >> When they'll be fixed, I'll be for Option B.
> > >>
> > >> Emmanuel
> > >>
> > >> Joakim Erdfelt a écrit :
> > >>> Lots of work has been done in the archiva database branch in the
> past
> > >>> 2 months.
> > >>>
> > >>> It has come time to start the merge back into trunk and get the help
> > >>> of others to finish off the work.
> > >>>
> > >>> I wanted to point people to the branch and let them take a look
> > >>> around, and then vote.
> > >>>
> > >>> As I see it we have 3 options.
> > >>>
> > >>> option A [ ] Make the branch the new trunk.
> > >>> option B [ ] Merge the branch into the existing trunk.
> > >>> option C [ ] -1 Do not merge the branch into trunk.
> > >>>
> > >>> I'll wait the usual 72 hours and tabulate the scores.
> > >>> Scores will be tabulated around 1:00am Sunday UTC.
> > >>>
> > >>> I favor option A personally, but I don't know what that will mean to
> > >>> those people that have trunk currently checked out.
> > >>>
> > >>> The Branch:
> > >>>
> >
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
> > >>>
> > >>>
> > >>> The Good:
> > >>> 1) Completed Integration of JPOX Database into system.
> > >>> 2) Completely overhauled the repository scanning for performance,
> > >>> availability, resilience, and capabilities.
> > >>> 3) Completely overhauled the reporting system for growth and use of
> > >>> the database.
> > >>>
> > >>> The Bad:
> > >>> 1) Admin screens have not yet been converted to the new
> > >>> configuration. (that's a priority for me ATM)
> > >>> 2) Automatic Artifact relocation on proxied requests has not been
> > >>> implemented.
> > >>> 3) Untested.
> > >>>
> > >>> I'm eager to get the other devs involved ASAP.
> > >>>
> > >>> While the vote is going on, I'll be alternating between Redback
> > >>> development and Archiva Admin Screen work.
> > >>>
> > >>> - Joakim Erdfelt
> > >>>
> > >>>
> > >>>
> > >>
> > >
> > >
> > >
> > >
> >
> >
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by nicolas de loof <ni...@gmail.com>.
I just checked out the branch and ran mvn install. I got all test failures
for Archiva Database (on windows 2000)
I then built with "-Dmaven.test.skip=true" and deployed on my local tomcat
(with old database deleted)
Got some funy ascii-art in logs, but some errors
"org.apache.maven.archiva.database.ArchivaDatabaseException: Error in JDO
during
get of Database object id [internal] of type
org.apache.maven.archiva.model.Arch
ivaRepositoryModel using no fetch-group"
.. and accessing localhost:8080/archiva :
Caught Exception while registering Interceptor class
pssEnvironmentCheckInterceptor - [unknown location]
org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:152)
...
Maybe the database refactoring is required, but IMHO the current
branch isn't ready for becoming the trunk ...
2007/4/27, Emmanuel Venisse <em...@venisse.net>:
>
> It's ok now, thanks.
>
> The branch seems to be good and well organized.
> Even if I found some NPE when I used the webapp, I'm +1 to use it as
> trunk.
>
> I don't think you'll can do option B easily, so I vote to option A. You
> can move the actual trunk to branches/archiva-0.9.x until the new trunk is
> stable.
>
> Emmanuel
>
> Joakim Erdfelt a écrit :
> > Please try again.
> >
> > All of the unit tests now work on windows.
> >
> > - Joakim
> >
> > Emmanuel Venisse wrote:
> >> Option C: Tests don't work on windows so I can't test it.
> >>
> >> When they'll be fixed, I'll be for Option B.
> >>
> >> Emmanuel
> >>
> >> Joakim Erdfelt a écrit :
> >>> Lots of work has been done in the archiva database branch in the past
> >>> 2 months.
> >>>
> >>> It has come time to start the merge back into trunk and get the help
> >>> of others to finish off the work.
> >>>
> >>> I wanted to point people to the branch and let them take a look
> >>> around, and then vote.
> >>>
> >>> As I see it we have 3 options.
> >>>
> >>> option A [ ] Make the branch the new trunk.
> >>> option B [ ] Merge the branch into the existing trunk.
> >>> option C [ ] -1 Do not merge the branch into trunk.
> >>>
> >>> I'll wait the usual 72 hours and tabulate the scores.
> >>> Scores will be tabulated around 1:00am Sunday UTC.
> >>>
> >>> I favor option A personally, but I don't know what that will mean to
> >>> those people that have trunk currently checked out.
> >>>
> >>> The Branch:
> >>>
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
> >>>
> >>>
> >>> The Good:
> >>> 1) Completed Integration of JPOX Database into system.
> >>> 2) Completely overhauled the repository scanning for performance,
> >>> availability, resilience, and capabilities.
> >>> 3) Completely overhauled the reporting system for growth and use of
> >>> the database.
> >>>
> >>> The Bad:
> >>> 1) Admin screens have not yet been converted to the new
> >>> configuration. (that's a priority for me ATM)
> >>> 2) Automatic Artifact relocation on proxied requests has not been
> >>> implemented.
> >>> 3) Untested.
> >>>
> >>> I'm eager to get the other devs involved ASAP.
> >>>
> >>> While the vote is going on, I'll be alternating between Redback
> >>> development and Archiva Admin Screen work.
> >>>
> >>> - Joakim Erdfelt
> >>>
> >>>
> >>>
> >>
> >
> >
> >
> >
>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
It's ok now, thanks.
The branch seems to be good and well organized.
Even if I found some NPE when I used the webapp, I'm +1 to use it as trunk.
I don't think you'll can do option B easily, so I vote to option A. You can move the actual trunk to branches/archiva-0.9.x until the new trunk is stable.
Emmanuel
Joakim Erdfelt a écrit :
> Please try again.
>
> All of the unit tests now work on windows.
>
> - Joakim
>
> Emmanuel Venisse wrote:
>> Option C: Tests don't work on windows so I can't test it.
>>
>> When they'll be fixed, I'll be for Option B.
>>
>> Emmanuel
>>
>> Joakim Erdfelt a écrit :
>>> Lots of work has been done in the archiva database branch in the past
>>> 2 months.
>>>
>>> It has come time to start the merge back into trunk and get the help
>>> of others to finish off the work.
>>>
>>> I wanted to point people to the branch and let them take a look
>>> around, and then vote.
>>>
>>> As I see it we have 3 options.
>>>
>>> option A [ ] Make the branch the new trunk.
>>> option B [ ] Merge the branch into the existing trunk.
>>> option C [ ] -1 Do not merge the branch into trunk.
>>>
>>> I'll wait the usual 72 hours and tabulate the scores.
>>> Scores will be tabulated around 1:00am Sunday UTC.
>>>
>>> I favor option A personally, but I don't know what that will mean to
>>> those people that have trunk currently checked out.
>>>
>>> The Branch:
>>> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>>>
>>>
>>> The Good:
>>> 1) Completed Integration of JPOX Database into system.
>>> 2) Completely overhauled the repository scanning for performance,
>>> availability, resilience, and capabilities.
>>> 3) Completely overhauled the reporting system for growth and use of
>>> the database.
>>>
>>> The Bad:
>>> 1) Admin screens have not yet been converted to the new
>>> configuration. (that's a priority for me ATM)
>>> 2) Automatic Artifact relocation on proxied requests has not been
>>> implemented.
>>> 3) Untested.
>>>
>>> I'm eager to get the other devs involved ASAP.
>>>
>>> While the vote is going on, I'll be alternating between Redback
>>> development and Archiva Admin Screen work.
>>>
>>> - Joakim Erdfelt
>>>
>>>
>>>
>>
>
>
>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Please try again.
All of the unit tests now work on windows.
- Joakim
Emmanuel Venisse wrote:
> Option C: Tests don't work on windows so I can't test it.
>
> When they'll be fixed, I'll be for Option B.
>
> Emmanuel
>
> Joakim Erdfelt a écrit :
>> Lots of work has been done in the archiva database branch in the past
>> 2 months.
>>
>> It has come time to start the merge back into trunk and get the help
>> of others to finish off the work.
>>
>> I wanted to point people to the branch and let them take a look
>> around, and then vote.
>>
>> As I see it we have 3 options.
>>
>> option A [ ] Make the branch the new trunk.
>> option B [ ] Merge the branch into the existing trunk.
>> option C [ ] -1 Do not merge the branch into trunk.
>>
>> I'll wait the usual 72 hours and tabulate the scores.
>> Scores will be tabulated around 1:00am Sunday UTC.
>>
>> I favor option A personally, but I don't know what that will mean to
>> those people that have trunk currently checked out.
>>
>> The Branch:
>> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>>
>>
>> The Good:
>> 1) Completed Integration of JPOX Database into system.
>> 2) Completely overhauled the repository scanning for performance,
>> availability, resilience, and capabilities.
>> 3) Completely overhauled the reporting system for growth and use of
>> the database.
>>
>> The Bad:
>> 1) Admin screens have not yet been converted to the new
>> configuration. (that's a priority for me ATM)
>> 2) Automatic Artifact relocation on proxied requests has not been
>> implemented.
>> 3) Untested.
>>
>> I'm eager to get the other devs involved ASAP.
>>
>> While the vote is going on, I'll be alternating between Redback
>> development and Archiva Admin Screen work.
>>
>> - Joakim Erdfelt
>>
>>
>>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
Option C: Tests don't work on windows so I can't test it.
When they'll be fixed, I'll be for Option B.
Emmanuel
Joakim Erdfelt a écrit :
> Lots of work has been done in the archiva database branch in the past 2
> months.
>
> It has come time to start the merge back into trunk and get the help of
> others to finish off the work.
>
> I wanted to point people to the branch and let them take a look around,
> and then vote.
>
> As I see it we have 3 options.
>
> option A [ ] Make the branch the new trunk.
> option B [ ] Merge the branch into the existing trunk.
> option C [ ] -1 Do not merge the branch into trunk.
>
> I'll wait the usual 72 hours and tabulate the scores.
> Scores will be tabulated around 1:00am Sunday UTC.
>
> I favor option A personally, but I don't know what that will mean to
> those people that have trunk currently checked out.
>
> The Branch:
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>
>
> The Good:
> 1) Completed Integration of JPOX Database into system.
> 2) Completely overhauled the repository scanning for performance,
> availability, resilience, and capabilities.
> 3) Completely overhauled the reporting system for growth and use of the
> database.
>
> The Bad:
> 1) Admin screens have not yet been converted to the new configuration.
> (that's a priority for me ATM)
> 2) Automatic Artifact relocation on proxied requests has not been
> implemented.
> 3) Untested.
>
> I'm eager to get the other devs involved ASAP.
>
> While the vote is going on, I'll be alternating between Redback
> development and Archiva Admin Screen work.
>
> - Joakim Erdfelt
>
>
>
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Trygve Laugstøl <tr...@apache.org>.
Joakim Erdfelt wrote:
> Trygve Laugstøl wrote:
>> Joakim Erdfelt wrote:
>>> Lots of work has been done in the archiva database branch in the past
>>> 2 months.
>>>
>>> It has come time to start the merge back into trunk and get the help
>>> of others to finish off the work.
>>>
>>> I wanted to point people to the branch and let them take a look
>>> around, and then vote.
>>>
>>> As I see it we have 3 options.
>>>
>>> option A [ ] Make the branch the new trunk.
>>> option B [ ] Merge the branch into the existing trunk.
>>> option C [ ] -1 Do not merge the branch into trunk.
>>>
>>> I'll wait the usual 72 hours and tabulate the scores.
>>> Scores will be tabulated around 1:00am Sunday UTC.
>>
>> I vote for the one that will get an alpha out as soon as possible.
>>
>> Archiva is really missing out on a lot of good customers and thus
>> developers. I am afraid that unless an alpha is kicked out ASAP the
>> development will loose it focus and that it will develop more advanced
>> and/or unnecessary features that needed.
> My timeline is this ...
>
> 1) Get branch merged back into trunk.
As I'm not following Archiva from the code point I find it a bit hard to
vote for A or B. I'd suggest the ones working on trunk specify how
big/isolated their changes are and use that as a basis for a decision.
I'm not sure if a vote is the best tool to sette branch->trunk or
trunk->branch.
> 2) Allow 1 to 2 weeks to stabilize core functionality.
I'd recommend the following approach:
1) Write down all the use cases that you want alpha 1 to implement. Note
that stuff like security is not something that should be the focus of an
alpha 1. I wouldn't mind skipping it for 1.0. I for one don't use any
security for anything but uploading, which I could life without if it
would save me all that httpd configuration that I have all over the place.
2) Write integration tests that do mostly happy day testing of the use
cases. Only fix the functionality that is *broken*, not missing. This
was a very useful tool when developing Continuum, and I'm pretty sure it
will be a very good fit for Archiva aswell. Writing the tests in python
was easy and made it easy to call external programs.
3) Release, rinse and repeat.
> 3) Release 1.0-alpha-1
> 4) Integrate redback.
> 5) Work through jira's.
> 6) Release 1.0-alpha-2 (time since 1.0-alpha-1, about 2 weeks)
> 7) Work through feature set for 1.0 in
> http://docs.codehaus.org/display/MAVENUSER/Archiva+Roadmap
I just did a quick read of the roadmap and have some comments:
Drop everything related to reporting and automatic processing. The
logging stuff is something I would strongly consider moving to 1.1, but
might be very useful in some cases so a simple CSV-like file will cover
the most basic needs until an 1.1 release.
> 8) Tackle jira's
> 9) Iterate thru feature set and jiras until we decide it's time for 1.0
> (final).
I would not use the bugs in JIRA to create your roadmap. Alphas are here
to demonstrate features more that stability. Stability and robustness
come with the betas. Features come with 1.1+ releases.
This baby are way overdue and still adding features just feels wrong.
There is nothing wrong in releasing an 1.1 a month after the initial
release and just show signs of an active community.
--
Trygve
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Trygve Laugstøl wrote:
> Joakim Erdfelt wrote:
>> Lots of work has been done in the archiva database branch in the past
>> 2 months.
>>
>> It has come time to start the merge back into trunk and get the help
>> of others to finish off the work.
>>
>> I wanted to point people to the branch and let them take a look
>> around, and then vote.
>>
>> As I see it we have 3 options.
>>
>> option A [ ] Make the branch the new trunk.
>> option B [ ] Merge the branch into the existing trunk.
>> option C [ ] -1 Do not merge the branch into trunk.
>>
>> I'll wait the usual 72 hours and tabulate the scores.
>> Scores will be tabulated around 1:00am Sunday UTC.
>
> I vote for the one that will get an alpha out as soon as possible.
>
> Archiva is really missing out on a lot of good customers and thus
> developers. I am afraid that unless an alpha is kicked out ASAP the
> development will loose it focus and that it will develop more advanced
> and/or unnecessary features that needed.
My timeline is this ...
1) Get branch merged back into trunk.
2) Allow 1 to 2 weeks to stabilize core functionality.
3) Release 1.0-alpha-1
4) Integrate redback.
5) Work through jira's.
6) Release 1.0-alpha-2 (time since 1.0-alpha-1, about 2 weeks)
7) Work through feature set for 1.0 in
http://docs.codehaus.org/display/MAVENUSER/Archiva+Roadmap
8) Tackle jira's
9) Iterate thru feature set and jiras until we decide it's time for 1.0
(final).
- Joakim
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Trygve Laugstøl <tr...@apache.org>.
Joakim Erdfelt wrote:
> Lots of work has been done in the archiva database branch in the past 2
> months.
>
> It has come time to start the merge back into trunk and get the help of
> others to finish off the work.
>
> I wanted to point people to the branch and let them take a look around,
> and then vote.
>
> As I see it we have 3 options.
>
> option A [ ] Make the branch the new trunk.
> option B [ ] Merge the branch into the existing trunk.
> option C [ ] -1 Do not merge the branch into trunk.
>
> I'll wait the usual 72 hours and tabulate the scores.
> Scores will be tabulated around 1:00am Sunday UTC.
I vote for the one that will get an alpha out as soon as possible.
Archiva is really missing out on a lot of good customers and thus
developers. I am afraid that unless an alpha is kicked out ASAP the
development will loose it focus and that it will develop more advanced
and/or unnecessary features that needed.
--
Trygve
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
Joakim Erdfelt a écrit :
> Emmanuel Venisse wrote:
>>
>>
>> Joakim Erdfelt a écrit :
>>> Ok.
>>>
>>> Here's the vote breakdown.
>>>
>>> option A - Make the branch the new trunk.
>>> * Emmanuel Venisse
>>> * Arnaud Heriter
>>> * Nicolas De Loof
>>> * Jesse McConnell
>>> * Brett Porter
>>> * Wendy Smoak
>>>
>>> option B - Merge the branch into the existing trunk.
>>> * Maria Odea Ching
>>>
>>> option C - Do not merge the branch into trunk.
>>> * (n/a)
>>>
>>> Looks like option A wins!
>>>
>>> The current plan
>>>
>>> 1) Identify the changes since the branch has been made.
>>> Branch was created on March 15, 2007 - on revision 518676
>>> 2) Merge in changes made on trunk since branch into the branch.
>>> 3) Rename the current trunk as branch-0.9
>>
>> Maybe it would be better to use this process:
>> 3) copy trunk as branch-0.9
>> 3.1) Remove trunk
>>
>> I think that with this process a 'svn up' will work fine instead of to
>> do a clean checkout.
> I was just going to use ...
>
> $ svn mv \
> https://svn.apache.org/repos/asf/maven/archiva/trunk \
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-0.9
>
> and then ...
>
> $ svn mv \
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
> \
> https://svn.apache.org/repos/asf/maven/archiva/trunk
>
> After all the docs for "svn mv" state ...
>
> move (mv, rename, ren): Move and/or rename something in working copy or
> repository.
> usage: move SRC DST
>
> Note: *this subcommand is equivalent to a 'copy' and 'delete'.*
> Note: the --revision option has no use and is deprecated.
>
> SRC and DST can both be working copy (WC) paths or URLs:
> WC -> WC: move and schedule for addition (with history)
> URL -> URL: complete server-side rename.
>
> See any problem with this approach?
It should be ok and should update correctly working copies.
Emmanuel
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Emmanuel Venisse wrote:
>
>
> Joakim Erdfelt a écrit :
>> Ok.
>>
>> Here's the vote breakdown.
>>
>> option A - Make the branch the new trunk.
>> * Emmanuel Venisse
>> * Arnaud Heriter
>> * Nicolas De Loof
>> * Jesse McConnell
>> * Brett Porter
>> * Wendy Smoak
>>
>> option B - Merge the branch into the existing trunk.
>> * Maria Odea Ching
>>
>> option C - Do not merge the branch into trunk.
>> * (n/a)
>>
>> Looks like option A wins!
>>
>> The current plan
>>
>> 1) Identify the changes since the branch has been made.
>> Branch was created on March 15, 2007 - on revision 518676
>> 2) Merge in changes made on trunk since branch into the branch.
>> 3) Rename the current trunk as branch-0.9
>
> Maybe it would be better to use this process:
> 3) copy trunk as branch-0.9
> 3.1) Remove trunk
>
> I think that with this process a 'svn up' will work fine instead of to
> do a clean checkout.
I was just going to use ...
$ svn mv \
https://svn.apache.org/repos/asf/maven/archiva/trunk \
https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-0.9
and then ...
$ svn mv \
https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
\
https://svn.apache.org/repos/asf/maven/archiva/trunk
After all the docs for "svn mv" state ...
move (mv, rename, ren): Move and/or rename something in working copy or
repository.
usage: move SRC DST
Note: *this subcommand is equivalent to a 'copy' and 'delete'.*
Note: the --revision option has no use and is deprecated.
SRC and DST can both be working copy (WC) paths or URLs:
WC -> WC: move and schedule for addition (with history)
URL -> URL: complete server-side rename.
See any problem with this approach?
- Joakim Erdfelt
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Emmanuel Venisse <em...@venisse.net>.
Joakim Erdfelt a écrit :
> Ok.
>
> Here's the vote breakdown.
>
> option A - Make the branch the new trunk.
> * Emmanuel Venisse
> * Arnaud Heriter
> * Nicolas De Loof
> * Jesse McConnell
> * Brett Porter
> * Wendy Smoak
>
> option B - Merge the branch into the existing trunk.
> * Maria Odea Ching
>
> option C - Do not merge the branch into trunk.
> * (n/a)
>
> Looks like option A wins!
>
> The current plan
>
> 1) Identify the changes since the branch has been made.
> Branch was created on March 15, 2007 - on revision 518676
> 2) Merge in changes made on trunk since branch into the branch.
> 3) Rename the current trunk as branch-0.9
Maybe it would be better to use this process:
3) copy trunk as branch-0.9
3.1) Remove trunk
I think that with this process a 'svn up' will work fine instead of to do a clean checkout.
> 4) Rename the archiva-jpox-database branch as the new trunk.
> 5) Set the versions in the trunk to 1.0-alpha-1-SNAPSHOT
> 6) Announce completion of merge to archiva-dev
> 7) Continue working on admin screens.
> 8) Once admin screens are stable, get the ball rolling on a 1.0-alpha-1
> release.
>
> - Joakim Erdfelt
>
> Joakim Erdfelt wrote:
>> Lots of work has been done in the archiva database branch in the past
>> 2 months.
>>
>> It has come time to start the merge back into trunk and get the help
>> of others to finish off the work.
>>
>> I wanted to point people to the branch and let them take a look
>> around, and then vote.
>>
>> As I see it we have 3 options.
>>
>> option A [ ] Make the branch the new trunk.
>> option B [ ] Merge the branch into the existing trunk.
>> option C [ ] -1 Do not merge the branch into trunk.
>>
>> I'll wait the usual 72 hours and tabulate the scores.
>> Scores will be tabulated around 1:00am Sunday UTC.
>>
>> I favor option A personally, but I don't know what that will mean to
>> those people that have trunk currently checked out.
>>
>> The Branch:
>> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>>
>>
>> The Good:
>> 1) Completed Integration of JPOX Database into system.
>> 2) Completely overhauled the repository scanning for performance,
>> availability, resilience, and capabilities.
>> 3) Completely overhauled the reporting system for growth and use of
>> the database.
>>
>> The Bad:
>> 1) Admin screens have not yet been converted to the new configuration.
>> (that's a priority for me ATM)
>> 2) Automatic Artifact relocation on proxied requests has not been
>> implemented.
>> 3) Untested.
>>
>> I'm eager to get the other devs involved ASAP.
>>
>> While the vote is going on, I'll be alternating between Redback
>> development and Archiva Admin Screen work.
>>
>> - Joakim Erdfelt
>>
>
>
>
>
Re: Complete: trunk version upgraded to 1.0-alpha-1-SNAPSHOT
Posted by nicolas de loof <ni...@gmail.com>.
Thanks for the work done on the branch.
Nico.
2007/5/1, Joakim Erdfelt <jo...@erdfelt.com>:
>
> The merge is complete.
> Trunk is now on version 1.0-alpha-1-SNAPSHOT using the former database
> branch.
>
> Old trunk is now located in
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-0.9
>
> - Joakim
>
> Joakim Erdfelt wrote:
> > Steps 1-4 are now complete.
> > Working on Step 5 (make version in trunk 1.0-alpha-1-SNAPSHOT) now ...
> >
> > - Joakim
> >
> > Joakim Erdfelt wrote:
> >> Ok.
> >>
> >> Here's the vote breakdown.
> >>
> >> option A - Make the branch the new trunk.
> >> * Emmanuel Venisse
> >> * Arnaud Heriter
> >> * Nicolas De Loof
> >> * Jesse McConnell
> >> * Brett Porter
> >> * Wendy Smoak
> >>
> >> option B - Merge the branch into the existing trunk.
> >> * Maria Odea Ching
> >>
> >> option C - Do not merge the branch into trunk.
> >> * (n/a)
> >>
> >> Looks like option A wins!
> >>
> >> The current plan
> >>
> >> 1) Identify the changes since the branch has been made.
> >> Branch was created on March 15, 2007 - on revision 518676
> >> 2) Merge in changes made on trunk since branch into the branch.
> >> 3) Rename the current trunk as branch-0.9
> >> 4) Rename the archiva-jpox-database branch as the new trunk.
> >> 5) Set the versions in the trunk to 1.0-alpha-1-SNAPSHOT
> >> 6) Announce completion of merge to archiva-dev
> >> 7) Continue working on admin screens.
> >> 8) Once admin screens are stable, get the ball rolling on a
> >> 1.0-alpha-1 release.
> >>
> >> - Joakim Erdfelt
> >
>
>
Re: Complete: trunk version upgraded to 1.0-alpha-1-SNAPSHOT
Posted by Emmanuel Venisse <em...@venisse.net>.
Thanks Joakim :)
Emmanuel
Joakim Erdfelt a écrit :
> The merge is complete.
> Trunk is now on version 1.0-alpha-1-SNAPSHOT using the former database
> branch.
>
> Old trunk is now located in
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-0.9
>
> - Joakim
>
> Joakim Erdfelt wrote:
>> Steps 1-4 are now complete.
>> Working on Step 5 (make version in trunk 1.0-alpha-1-SNAPSHOT) now ...
>>
>> - Joakim
>>
>> Joakim Erdfelt wrote:
>>> Ok.
>>>
>>> Here's the vote breakdown.
>>>
>>> option A - Make the branch the new trunk.
>>> * Emmanuel Venisse
>>> * Arnaud Heriter
>>> * Nicolas De Loof
>>> * Jesse McConnell
>>> * Brett Porter
>>> * Wendy Smoak
>>>
>>> option B - Merge the branch into the existing trunk.
>>> * Maria Odea Ching
>>>
>>> option C - Do not merge the branch into trunk.
>>> * (n/a)
>>>
>>> Looks like option A wins!
>>>
>>> The current plan
>>>
>>> 1) Identify the changes since the branch has been made.
>>> Branch was created on March 15, 2007 - on revision 518676
>>> 2) Merge in changes made on trunk since branch into the branch.
>>> 3) Rename the current trunk as branch-0.9
>>> 4) Rename the archiva-jpox-database branch as the new trunk.
>>> 5) Set the versions in the trunk to 1.0-alpha-1-SNAPSHOT
>>> 6) Announce completion of merge to archiva-dev
>>> 7) Continue working on admin screens.
>>> 8) Once admin screens are stable, get the ball rolling on a
>>> 1.0-alpha-1 release.
>>>
>>> - Joakim Erdfelt
>>
>
>
>
>
Re: Complete: trunk version upgraded to 1.0-alpha-1-SNAPSHOT
Posted by Jesse McConnell <je...@gmail.com>.
\o/ nice job :)
On 5/1/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> The merge is complete.
> Trunk is now on version 1.0-alpha-1-SNAPSHOT using the former database
> branch.
>
> Old trunk is now located in
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-0.9
>
> - Joakim
>
> Joakim Erdfelt wrote:
> > Steps 1-4 are now complete.
> > Working on Step 5 (make version in trunk 1.0-alpha-1-SNAPSHOT) now ...
> >
> > - Joakim
> >
> > Joakim Erdfelt wrote:
> >> Ok.
> >>
> >> Here's the vote breakdown.
> >>
> >> option A - Make the branch the new trunk.
> >> * Emmanuel Venisse
> >> * Arnaud Heriter
> >> * Nicolas De Loof
> >> * Jesse McConnell
> >> * Brett Porter
> >> * Wendy Smoak
> >>
> >> option B - Merge the branch into the existing trunk.
> >> * Maria Odea Ching
> >>
> >> option C - Do not merge the branch into trunk.
> >> * (n/a)
> >>
> >> Looks like option A wins!
> >>
> >> The current plan
> >>
> >> 1) Identify the changes since the branch has been made.
> >> Branch was created on March 15, 2007 - on revision 518676
> >> 2) Merge in changes made on trunk since branch into the branch.
> >> 3) Rename the current trunk as branch-0.9
> >> 4) Rename the archiva-jpox-database branch as the new trunk.
> >> 5) Set the versions in the trunk to 1.0-alpha-1-SNAPSHOT
> >> 6) Announce completion of merge to archiva-dev
> >> 7) Continue working on admin screens.
> >> 8) Once admin screens are stable, get the ball rolling on a
> >> 1.0-alpha-1 release.
> >>
> >> - Joakim Erdfelt
> >
>
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
Complete: trunk version upgraded to 1.0-alpha-1-SNAPSHOT
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
The merge is complete.
Trunk is now on version 1.0-alpha-1-SNAPSHOT using the former database
branch.
Old trunk is now located in
https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-0.9
- Joakim
Joakim Erdfelt wrote:
> Steps 1-4 are now complete.
> Working on Step 5 (make version in trunk 1.0-alpha-1-SNAPSHOT) now ...
>
> - Joakim
>
> Joakim Erdfelt wrote:
>> Ok.
>>
>> Here's the vote breakdown.
>>
>> option A - Make the branch the new trunk.
>> * Emmanuel Venisse
>> * Arnaud Heriter
>> * Nicolas De Loof
>> * Jesse McConnell
>> * Brett Porter
>> * Wendy Smoak
>>
>> option B - Merge the branch into the existing trunk.
>> * Maria Odea Ching
>>
>> option C - Do not merge the branch into trunk.
>> * (n/a)
>>
>> Looks like option A wins!
>>
>> The current plan
>>
>> 1) Identify the changes since the branch has been made.
>> Branch was created on March 15, 2007 - on revision 518676
>> 2) Merge in changes made on trunk since branch into the branch.
>> 3) Rename the current trunk as branch-0.9
>> 4) Rename the archiva-jpox-database branch as the new trunk.
>> 5) Set the versions in the trunk to 1.0-alpha-1-SNAPSHOT
>> 6) Announce completion of merge to archiva-dev
>> 7) Continue working on admin screens.
>> 8) Once admin screens are stable, get the ball rolling on a
>> 1.0-alpha-1 release.
>>
>> - Joakim Erdfelt
>
Complete: update db-branch / trunk->branch-0.9 / db-branch->trunk
swap
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Steps 1-4 are now complete.
Working on Step 5 (make version in trunk 1.0-alpha-1-SNAPSHOT) now ...
- Joakim
Joakim Erdfelt wrote:
> Ok.
>
> Here's the vote breakdown.
>
> option A - Make the branch the new trunk.
> * Emmanuel Venisse
> * Arnaud Heriter
> * Nicolas De Loof
> * Jesse McConnell
> * Brett Porter
> * Wendy Smoak
>
> option B - Merge the branch into the existing trunk.
> * Maria Odea Ching
>
> option C - Do not merge the branch into trunk.
> * (n/a)
>
> Looks like option A wins!
>
> The current plan
>
> 1) Identify the changes since the branch has been made.
> Branch was created on March 15, 2007 - on revision 518676
> 2) Merge in changes made on trunk since branch into the branch.
> 3) Rename the current trunk as branch-0.9
> 4) Rename the archiva-jpox-database branch as the new trunk.
> 5) Set the versions in the trunk to 1.0-alpha-1-SNAPSHOT
> 6) Announce completion of merge to archiva-dev
> 7) Continue working on admin screens.
> 8) Once admin screens are stable, get the ball rolling on a
> 1.0-alpha-1 release.
>
> - Joakim Erdfelt
Re: [VOTE] Merge Archiva Database Branch to Trunk
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Ok.
Here's the vote breakdown.
option A - Make the branch the new trunk.
* Emmanuel Venisse
* Arnaud Heriter
* Nicolas De Loof
* Jesse McConnell
* Brett Porter
* Wendy Smoak
option B - Merge the branch into the existing trunk.
* Maria Odea Ching
option C - Do not merge the branch into trunk.
* (n/a)
Looks like option A wins!
The current plan
1) Identify the changes since the branch has been made.
Branch was created on March 15, 2007 - on revision 518676
2) Merge in changes made on trunk since branch into the branch.
3) Rename the current trunk as branch-0.9
4) Rename the archiva-jpox-database branch as the new trunk.
5) Set the versions in the trunk to 1.0-alpha-1-SNAPSHOT
6) Announce completion of merge to archiva-dev
7) Continue working on admin screens.
8) Once admin screens are stable, get the ball rolling on a 1.0-alpha-1
release.
- Joakim Erdfelt
Joakim Erdfelt wrote:
> Lots of work has been done in the archiva database branch in the past
> 2 months.
>
> It has come time to start the merge back into trunk and get the help
> of others to finish off the work.
>
> I wanted to point people to the branch and let them take a look
> around, and then vote.
>
> As I see it we have 3 options.
>
> option A [ ] Make the branch the new trunk.
> option B [ ] Merge the branch into the existing trunk.
> option C [ ] -1 Do not merge the branch into trunk.
>
> I'll wait the usual 72 hours and tabulate the scores.
> Scores will be tabulated around 1:00am Sunday UTC.
>
> I favor option A personally, but I don't know what that will mean to
> those people that have trunk currently checked out.
>
> The Branch:
> https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-jpox-database-refactor
>
>
> The Good:
> 1) Completed Integration of JPOX Database into system.
> 2) Completely overhauled the repository scanning for performance,
> availability, resilience, and capabilities.
> 3) Completely overhauled the reporting system for growth and use of
> the database.
>
> The Bad:
> 1) Admin screens have not yet been converted to the new configuration.
> (that's a priority for me ATM)
> 2) Automatic Artifact relocation on proxied requests has not been
> implemented.
> 3) Untested.
>
> I'm eager to get the other devs involved ASAP.
>
> While the vote is going on, I'll be alternating between Redback
> development and Archiva Admin Screen work.
>
> - Joakim Erdfelt
>