Hi Brett,
I updated my workspace today and tried to build Archiva, and I get an error
during JPOX enhancement, in the archiva-model module
(UnsupportedClassVersionError, see at the end of the mail for the log). If I
use the last revision of the Archiva's root POM (that is, with compiler set
to 1.
Fabrice,
Excellent news! :-)
Check out jira.
We recently moved a large chunk of issues out of 1.0-alpha-2 to the
nebulous 1.0.x fix version.
The remaining list in 1.0-alpha-2 I consider to be important enough to
address for 1.0-alpha-2, even if that means, a message on the jira that
says "ye
I don't agree to postpone m1 support for 1.0.X. It's one of the feature
which create the difference with others proxy repo tools... It's the feature
which help to install archiva in corporate contexts...
Arnaud
On 20/06/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
Fabrice,
Excellent news! :-
m1 is just postponed to a release after 1.0-alpha-2, and before 1.0-final
It's not out, it's not forgotten. :-)
The "1.0.x" fix version is just a holding area for 1.0 related jiras.
Things that are post-1.0 are in the "Future" fix version right now.
When I get back from my various trips these
ok, fine !
thanks a lot !!
Arnaud
On 20/06/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
m1 is just postponed to a release after 1.0-alpha-2, and before 1.0-final
It's not out, it's not forgotten. :-)
The "1.0.x" fix version is just a holding area for 1.0 related jiras.
Things that are post-
On 6/19/07, Fabrice Bellingard <[EMAIL PROTECTED]> wrote:
which proxy related bugs do you think of? I've tested Archiva proxying for
some days, and it works pretty good for me. I mean, if we'd have to release
alpha-2, I wouldn't say no. :-)
That's good to know. I see 14 closed issues in alpha
No problems here, or on the solaris zone. You ran with clean as well?
I'd suggest upgrading your JDK if it really is _01 - that's pretty
old :)
- Brett
On 20/06/2007, at 8:42 PM, Fabrice Bellingard wrote:
Hi Brett,
I updated my workspace today and tried to build Archiva, and I get
an er
The only one I'd change is the maximum. I don't really understand the
usefulness of that and it's hit me a couple of times.
- Brett
On 18/06/2007, at 8:12 PM, Joakim Erdfelt wrote:
There has been some controversy on the closing of MRM-229 and MRM-225,
I feel that they should remain closed.
On 6/20/07, Brett Porter <[EMAIL PROTECTED]> wrote:
The only one I'd change is the maximum. I don't really understand the
usefulness of that and it's hit me a couple of times.
Same here. Jesse already said he'd change it in Redback, so Archiva
will pick up the change at some point.
--
Wendy