@the jansi problem: I think Łukasz knows more about this problem
@the ITest problem: This is a maven3 issue. The problem is that we're
internally still use m2 references and this does not work out too well
for this integration test using m3. But AFAIK this is already on the
list for karaf 3.0

Kind regards,
Andreas

On Fri, Mar 4, 2011 at 6:39 AM, David Jencks <[email protected]> wrote:
>
> On Mar 3, 2011, at 9:03 PM, Willem Jiang wrote:
>
>> On 3/4/11 12:35 PM, David Jencks wrote:
>>> I'm having trouble building karaf trunk today.
>>>
>>> 1. I can't find org.fusesource.jansi:jansi:1.5-SNAPSHOT anywhere.  However 
>>> 1.5 looks like it was released last november.  Furthermore Style says it 
>>> wraps Ansi with a fluent api but the Ansi from 1.5 looks already fluent.  
>>> Can't we use the released jansi and use its fluent api?  AFAICT this 
>>> dependency was upgraded yesterday 1.4 to 1.5-SNAPSHOT in rev 1076175 by 
>>> ldywicki at which point the Style class was added.
>>>
>> I just checked this repo[1], the latest release jansi version is 1.2.
>
> Something is messed up: this one contains 1.5 from november:
>   
> http://repo.fusesource.com/nexus/content/repositories/public/org/fusesource/jansi/jansi/1.5/
>
> and it's on central
> http://repo2.maven.org/maven2/org/fusesource/jansi/jansi/1.5/
> again dated in last nov.  What's going on that the source still has version 
> 1.5-SNAPSHOT?
>
>> BTW, I just kicked a new deployment of 
>> org.fusesource.jansi:jansi:1.5-SNAPSHOT, you should find the artifact from 
>> here[2]
>>
>> Now I get the compile error of Style with latest trunk code.
>
> The released code has the same problem, which is why I asked about the fluent 
> api present in the released version.
>
> thanks
> david jencks
>
>>
>>> 2. I'm getting an itest failure from archetypes itests (last project) and 
>>> noticed this...
>>>
>>> [ maven embedder INFO] Archetype repository missing. Using the one from 
>>> [org.apache.karaf.archetypes:archetypes-command:2.1.4] found in catalog 
>>> remote
>>>
>>> is this an external dependency that the archtype be deployed to a catalog?  
>>> Or maybe something new with maven 3???
>>>
>>> thanks
>>> david jencks
>>>
>>>
>>
>> [1]http://repo.fusesource.com/nexus/content/repositories/releases/org/fusesource/jansi/jansi/
>> [2]http://repo.fusesource.com/nexus/content/repositories/snapshots/org/fusesource/jansi/jansi/1.5-SNAPSHOT/
>> --
>> Willem
>> ----------------------------------
>> FuseSource
>> Web: http://www.fusesource.com
>> Blog:    http://willemjiang.blogspot.com (English)
>>         http://jnn.javaeye.com (Chinese)
>> Twitter: willemjiang
>
>

Reply via email to