JDK1.4 dependencies

[Stephan Michels <st...@apache.org>]

Hi,

I have the following problem, I got a strange exception with
Cocoon, which use the Event package as you know.

java.lang.AbstractMethodError:
org/apache/excalibur/event/impl/AbstractQueue.enqueue
  at
org.apache.excalibur.event.command.AbstractThreadManager$PipelineRunner.run(AbstractThreadManager.java:310)
  at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727)
  at java.lang.Thread.run(Thread.java:484)

This exception only occurs with Blackdown's JDK 1.3 under
Linux/PPC, and I think the BSD platform got the same problem.
In most cases compiling the package solved the problem(WTF?! anyway).

So I tried compile the current Avalon snapshot, and noticed
you changed to maven(first time I tried).

But the build process aborted cause of dependencies to
JDK14 classes. But in my case I don't have 1.4 by the hand
for PPC.

[...]

avalon:compile-api:

avalon:compile-impl:
    [javac] Compiling 27 source files to
/usr/local/stephan/avalon/framework/target/impl
/usr/local/stephan/avalon/framework/src/impl/org/apache/avalon/framework/logger/Jdk14Logger.java:57:
cannot resolve symbol
symbol  : class Level
location: package logging
import java.util.logging.Level;
                         ^
/usr/local/stephan/avalon/framework/src/impl/org/apache/avalon/framework/logger/Jdk14Logger.java:87:
cannot resolve symbol
symbol  : class Logger
location: package logging
    private final java.util.logging.Logger m_logger;

[...]

So, my question is this intentional, or a unresolved behaviour?

Thank you for your attention, Stephan Michels.

_______________________________________________________________________
         Stephan Michels               EMail: stephan@apache.org
         ICQ: 115535699                Tel: +49-030-314-21583
----+----|----+----|----+----|----+----|----+----|----+----|----+----|-|


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

Re: JDK1.4 dependencies

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

Leo Simons wrote:

> Stephan Michels wrote:
>
>> So, my question is this intentional, or a unresolved behaviour?
>
>
> the latter. The problem is how to do clean conditional filtering of 
> classes based on available stuff in maven. Sure its possible. A todo. 
> Help welcome ;) 


IMVHO, start by breaking the project api and impl into
seperate projects. I've been running into lots of problems
with the quasi src seperation because I can apply maven
goals to specific artificats.  I'm also locked into a lot
of "special" scripts that really belong in a seperate
plugin. 

Cheers, Steve.

>
>
> cheers,
>
> - Leo
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>

-- 

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

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

Re: JDK1.4 dependencies

[Leo Simons <le...@apache.org>]

Stephan Michels wrote:
> So, my question is this intentional, or a unresolved behaviour?

the latter. The problem is how to do clean conditional filtering of 
classes based on available stuff in maven. Sure its possible. A todo. 
Help welcome ;)

cheers,

- Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org