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 i
On 4/27/07, nicolas de loof <[EMAIL PROTECTED]> 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 goo
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
nicolas de loof a écrit :
2007/4/27, Emmanuel Venisse <[EMAIL PROTECTED]>:
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.
2007/4/27, Emmanuel Venisse <[EMAIL PROTECTED]>:
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 behin
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 ol
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 rele
+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 <[EMAIL PROTECTED]>:
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.
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 <[EMAIL PROTECTED]> wrote:
I vote A. We switch the branch and the trunk.
I'll apply Nicolas' patches on this branch and w
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 <[
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.dat
I'll apply them on the trunk or in a branch
I'm testing it (http://forge.octo.com/archiva/) and hope to commit this WE.
Arnaud
On 27/04/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Arnaud, I saw on the branch merge vote that you mentioned applying
some patches to trunk. Please do, if you have t
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 sta
13 matches
Mail list logo
