Recursive dependencies

[Jeff Turner <je...@socialchange.net.au>]

FYI,

Just recently, it seems some code in Excalibur's scratchpad has gained a
dependency on Command. Unfortunately, Command has a dep on scratchpad,
so the whole thing is unbuildable.

Commenting out the scratchpad <javac> fixes the problem for now.


--Jeff

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

Re: Recursive dependencies

[Jeff Turner <je...@socialchange.net.au>]

On Wed, Apr 03, 2002 at 07:42:06AM +0100, Paul Hammant wrote:
> Jeff,
> 
> >Just recently, it seems some code in Excalibur's scratchpad has gained a
> >dependency on Command. Unfortunately, Command has a dep on scratchpad,
> >so the whole thing is unbuildable.
> >
> >Commenting out the scratchpad <javac> fixes the problem for now.
> >
> Interesting.  
> 
> In theory we could allow recursive dependancies if we had interface/impl 
> separation to the extent where all interfaces were built before impls.
> My assumption is that AImpl requires BInterface and Bimpl requires 
> AInterface.

That makes sense.. compile the interfaces first and everyone's happy.
Doesn't look too applicable to Excalibur through :/ Our situation is
this (-> means "depends on"):

scratchpad mpool -> command
scratchpad system -> command
scratchpad thread  -> core, framework, lang
command -> thread
scratchpad lang -> (nothing)


So one possibility would be to break the 'thread' package off into a
separately compiled component. I'll try that unless anyone has
objections or better suggestion..

--Jeff
 
> Thoughts?
> 
> Regards,
> 
> - Paul

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

RE: Recursive dependencies

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

The correct dependencies for Command are:

collections
event
thread

> -----Original Message-----
> From: Paul Hammant [mailto:Paul_Hammant@yahoo.com] 
> Sent: Wednesday, April 03, 2002 1:42 AM
> To: Avalon Developers List
> Subject: Re: Recursive dependencies
> 
> 
> Jeff,
> 
> >Just recently, it seems some code in Excalibur's scratchpad 
> has gained 
> >a dependency on Command. Unfortunately, Command has a dep on 
> >scratchpad, so the whole thing is unbuildable.
> >
> >Commenting out the scratchpad <javac> fixes the problem for now.
> >
> Interesting.  
> 
> In theory we could allow recursive dependancies if we had 
> interface/impl 
> separation to the extent where all interfaces were built 
> before impls. My assumption is that AImpl requires BInterface 
> and Bimpl requires 
> AInterface.
> 
> We could split the compiles into two stages :
> 
>   <!-- interface compile -->
>        <javac srcdir="${java.dir}"
>            destdir="${build.classes}"
>            debug="${build.debug}"
>            optimize="${build.optimize}"
>            deprecation="${build.deprecation}">
>         <classpath refid="project.class.path" />
>         <exclude name="org/apache/excalibur/aaa/impl/**" />
>       </javac>
> 
>   <!-- impl compile -->
>        <javac srcdir="${java.dir}"
>            destdir="${build.classes}"
>            debug="${build.debug}"
>            optimize="${build.optimize}"
>            deprecation="${build.deprecation}">
>         <classpath refid="project.class.path" />
>         <exclude name="org/apache/excalibur/aaa/*" />
>       </javac>
> 
> Thoughts?
> 
> Regards,
> 
> - Paul
> 
> 
> --
> 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>

Re: Recursive dependencies

[Paul Hammant <Pa...@yahoo.com>]

Jeff,

>Just recently, it seems some code in Excalibur's scratchpad has gained a
>dependency on Command. Unfortunately, Command has a dep on scratchpad,
>so the whole thing is unbuildable.
>
>Commenting out the scratchpad <javac> fixes the problem for now.
>
Interesting.  

In theory we could allow recursive dependancies if we had interface/impl 
separation to the extent where all interfaces were built before impls.
My assumption is that AImpl requires BInterface and Bimpl requires 
AInterface.

We could split the compiles into two stages :

  <!-- interface compile -->
       <javac srcdir="${java.dir}"
           destdir="${build.classes}"
           debug="${build.debug}"
           optimize="${build.optimize}"
           deprecation="${build.deprecation}">
        <classpath refid="project.class.path" />
        <exclude name="org/apache/excalibur/aaa/impl/**" />
      </javac>

  <!-- impl compile -->
       <javac srcdir="${java.dir}"
           destdir="${build.classes}"
           debug="${build.debug}"
           optimize="${build.optimize}"
           deprecation="${build.deprecation}">
        <classpath refid="project.class.path" />
        <exclude name="org/apache/excalibur/aaa/*" />
      </javac>

Thoughts?

Regards,

- Paul


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