Cornerstone doesn't build

[Greg Steuck <gr...@nest.cx>]

Hello,

Could someone confirm this error from a freshly updated Cornerstone:
    [javac] src/java/org/apache/avalon/cornerstone/blocks/threads/DefaultThreadManager.java:74: cannot resolve symbol
    [javac] symbol  : constructor DefaultThreadPool (java.lang.String,int,int,org.apache.excalibur.threadcontext.ThreadContext)
    [javac] location: class org.apache.avalon.excalibur.thread.impl.DefaultThreadPool
    [javac]                 new DefaultThreadPool( name, minThreads, maxThreads, threadContext );
    [javac]                 ^

I'd say it complains rightly, for there is no
constructor(String,int,int,ThreadContext) among the jars in lib/. The
closest I found is:

$ javap -extdirs lib org/apache/avalon/excalibur/thread/impl/DefaultThreadPool
    public org/apache/avalon/excalibur/thread/impl/DefaultThreadPool(java.lang.String,int,org.apache.excalibur.threadcontext.ThreadContext) throws java.lang.Exception;

Time to update the lib/?

Thanks
Greg

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

Re: Cornerstone doesn't build

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

Greg Steuck wrote:

>Hello,
>
>Could someone confirm this error from a freshly updated Cornerstone:
>    [javac] src/java/org/apache/avalon/cornerstone/blocks/threads/DefaultThreadManager.java:74: cannot resolve symbol
>    [javac] symbol  : constructor DefaultThreadPool (java.lang.String,int,int,org.apache.excalibur.threadcontext.ThreadContext)
>    [javac] location: class org.apache.avalon.excalibur.thread.impl.DefaultThreadPool
>    [javac]                 new DefaultThreadPool( name, minThreads, maxThreads, threadContext );
>    [javac]                 ^
>
>I'd say it complains rightly, for there is no
>constructor(String,int,int,ThreadContext) among the jars in lib/. The
>closest I found is:
>
>$ javap -extdirs lib org/apache/avalon/excalibur/thread/impl/DefaultThreadPool
>    public org/apache/avalon/excalibur/thread/impl/DefaultThreadPool(java.lang.String,int,org.apache.excalibur.threadcontext.ThreadContext) throws java.lang.Exception;
>
>Time to update the lib/?
>

Yes and no.

The current build process bundles all of the corenerstone content into a 
single jar file - different components, different status, depedencies, 
maturity, etc.  I've been seperating some of these out into independent 
packages.  For example, you can build the threads comoponent by running:

   ant -buildfile threads.xml

This will generate a jar file cornerstone-threads-1.0.jar based on the 
current Excalibur thread package. However - this is problamatic because 
it ties the cornerstone package to the last build in Excalibur as 
distinct from the released or candidate releases.  The solution used in 
Cornerstone has been to add release libraries into the Cornerstone/lib 
directory - however that is also problamatic because these jars tend to 
get updated when you need to solve problems (e.g. like the recent pool 
max bug fix). The solution to this is to get a good  release management 
environment into Avalon.  Towards that end I'm currenty playing with Maven.

So that answer is - Yes, update the jar is the fix. No, its not the 
solution.

Cheers, Steve.

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net




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