Maybe we could do both..We don't want to cram everything in 1.1 :) Also, a
large portion of the issues in the 1.1 bucket are bug fixes. We could
probably move some of them to 1.0.2 or 1.0.x, wdyt?
Thanks also for updating the roadmap and jira Brett!
-Deng
On Feb 15, 2008 3:45 PM, Brett Porter <[
Aha, here it is: MRM-675
On Feb 18, 2008 9:14 AM, Napoleon Esmundo C. Ramirez <
[EMAIL PROTECTED]> wrote:
> I remember experiencing this as well, when I tried to build archiva with
> jasper reports in it--though I really couldn't rule out that archiva doesn't
> proxy version ranges.
>
>
> On Feb
I remember experiencing this as well, when I tried to build archiva with
jasper reports in it--though I really couldn't rule out that archiva doesn't
proxy version ranges.
On Feb 18, 2008 3:14 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Pretty sure that's the same bug you reported before (metad
Pretty sure that's the same bug you reported before (metadata problems
with versions). I also think I've seen this one explicitly called out
in JIRA.
- Brett
On 18/02/2008, at 6:11 AM, Wendy Smoak wrote:
Yet another unsubstantiated rumor. :) I'm using Archiva as a proxy
for central, and g
Yet another unsubstantiated rumor. :) I'm using Archiva as a proxy
for central, and getting this in the Struts 2 build:
$mvn install -Pall
...
Couldn't find a version in [1.6] to match range [1.7,)
commons-digester:commons-digester:jar:null
If I go straight to central, no problem.
--
Wendy
