fortress -> assembly dep?

[Jeff Turner <je...@apache.org>]

Hi,

Just playing with Leif's nifty build.xml, which fails when it runs fortress's 'big-jar' target:
"jakarta-avalon-excalibur/assembly/dist not found."

How come Fortress tries to build Merlin in it's dependencies?

    <target name="dependencies" description="Check dependencies" unless="skip.dependencies">
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkCommon"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkFramework"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkLogkit"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkAltrmi"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkCollections"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkInstrument"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkInstrumentManager"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkSourceResolve"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkEvent"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkThreadcontext"/>
        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkLogger"/>
        <ant antfile="../assembly/build.xml" target="dist" inheritAll="false"/>

When the depchecker is turned off, as it is in build.xml, the 'dependencies'
target isn't run, which is why assembly/dist isn't present.


--Jeff

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: fortress -> assembly dep?

[Stephen McConnell <mc...@apache.org>]

Let me know if there is anything I need to do.  Berin added some 
additional jars to the Merlin lib a little earlier and I updated the 
build.xml and manifest to take these into account a few hours later - 
which may or may not have anything to do with the problem ;-)

Steve.


Jeff Turner wrote:

>Hi,
>
>Just playing with Leif's nifty build.xml, which fails when it runs fortress's 'big-jar' target:
>"jakarta-avalon-excalibur/assembly/dist not found."
>
>How come Fortress tries to build Merlin in it's dependencies?
>
>    <target name="dependencies" description="Check dependencies" unless="skip.dependencies">
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkCommon"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkFramework"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkLogkit"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkAltrmi"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkCollections"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkInstrument"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkInstrumentManager"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkSourceResolve"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkEvent"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkThreadcontext"/>
>        <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkLogger"/>
>        <ant antfile="../assembly/build.xml" target="dist" inheritAll="false"/>
>
>When the depchecker is turned off, as it is in build.xml, the 'dependencies'
>target isn't run, which is why assembly/dist isn't present.
>
>
>--Jeff
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>  
>

-- 

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: fortress -> assembly dep?

[Stephen McConnell <mc...@apache.org>]

Berin Loritsch wrote:

>>From: Jeff Turner [mailto:jefft@apache.org] 
>>
>>Hi,
>>
>>Just playing with Leif's nifty build.xml, which fails when it 
>>runs fortress's 'big-jar' target: 
>>"jakarta-avalon-excalibur/assembly/dist not found."
>>
>>How come Fortress tries to build Merlin in it's dependencies?
>>    
>>
>
>
>I was preparing for a Fortress/Merlin merger--building a version
>of the Container that is compatible with Merlin.
>

This is cool!

Out of the box we will have one hell of a solution ...

  (a) Fortress container in Merlin Kernel or container in
      a Merlin Container
        - hosting ECM style components
          (Cocoon comes in from the cold)
        - ECM bridge between dynamic lookup and structured meta based
          component models
        - instrumentation
  (b) Merlin containers
        - hosting structured service
        - cornerstone components
        - Phoenix blocks
        - dynamically loaded components
        - nested Merlin kernels (i.e. nested container hierarchies)
        - and Fortress

It's almost incestuous!

Cheers, Steve.

-- 

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: fortress -> assembly dep?

[Berin Loritsch <bl...@apache.org>]

> From: Jeff Turner [mailto:jefft@apache.org] 
> 
> Hi,
> 
> Just playing with Leif's nifty build.xml, which fails when it 
> runs fortress's 'big-jar' target: 
> "jakarta-avalon-excalibur/assembly/dist not found."
> 
> How come Fortress tries to build Merlin in it's dependencies?


I was preparing for a Fortress/Merlin merger--building a version
of the Container that is compatible with Merlin.

> 
>     <target name="dependencies" description="Check 
> dependencies" unless="skip.dependencies">
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkCommon"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkFramework"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkLogkit"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkAltrmi"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkCollections"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkInstrument"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkInstrumentManager"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkSourceResolve"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkEvent"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkThreadcontext"/>
>         <ant antfile="${depchecker.prefix}/depchecker.xml" 
> target="checkLogger"/>
>         <ant antfile="../assembly/build.xml" target="dist" 
> inheritAll="false"/>
> 
> When the depchecker is turned off, as it is in build.xml, the 
> 'dependencies' target isn't run, which is why assembly/dist 
> isn't present.
> 
> 
> --Jeff
> 
> --
> To unsubscribe, e-mail:   
> <mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <ma...@jakarta.apache.org>
> 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>