Rusty Wright wrote at Mittwoch, 1. Juli 2009 00:15:
This may be a dumb or inappropriate question, but why does Tomcat need
commons logging? Why can't it just use java util logging?
Who did mention Tomcat in this thread? And no, recent versions of Tomcat use
their own logging framework JULI
Lucas Bergman wrote at Dienstag, 30. Juni 2009 21:49:
Dennis Lundberg wrote:
Lucas Bergman wrote:
Running this test with Maven 2.1.0 fails:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
[ ... ]
The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
Lucas Bergman wrote:
Dennis Lundberg wrote:
That is your problem. What this does is mess the dependency-tree. It
removes commons-logging from the dependency tree because that
version 99.0-... is larger than the latest current release of
commons-logging. The 99.0-... version should *never
I forgot to mention that my tests were conducted using Maven 2.0.9. I will redo
the tests with Maven 2.2.0.
Ceki Gulcu wrote:
Lucas Bergman wrote:
Dennis Lundberg wrote:
That is your problem. What this does is mess the dependency-tree. It
removes commons-logging from the dependency
Using Maven 2.2.0, the behavior remains the same as with Maven
2.0.9. Moreover, if you remove the dependency on
net.sf.ehcache:ehcache:1.6.0 from the pom file for htmlunitbug, then
the test passes (with the original pom files for hibernate-ehcache
hibernate-parent referencing commons-logging
2009/7/1 Ceki Gulcu c...@qos.ch:
Using Maven 2.2.0, the behavior remains the same as with Maven
2.0.9. Moreover, if you remove the dependency on
net.sf.ehcache:ehcache:1.6.0 from the pom file for htmlunitbug, then
the test passes (with the original pom files for hibernate-ehcache
Lucas Bergman wrote:
I ran into a strange dependency resolution problem at work, which a
colleague and I whittled down to a fairly simple test case. Consider
the following POM:
project xmlns=http://maven.apache.org/POM/4.0.0;
Lucas Bergman wrote at Montag, 29. Juni 2009 18:11:
Jörg Schaible wrote:
Lucas Bergman wrote:
Jörg Schaible wrote:
Lucas Bergman wrote:
Running this test with Maven 2.1.0 fails:
java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
[ ... ]
Jörg Schaible wrote:
You've been right, I should have read your question closer. See Dennis'
answer. Actually there was an attempt to release an official empty
commons-logging at Apache recently and it was tunred down exactly because
we could foresee this problem you're facing now :-/
Note
Hi Ceki,
Ceki Gulcu wrote at Dienstag, 30. Juni 2009 16:45:
Jörg Schaible wrote:
You've been right, I should have read your question closer. See Dennis'
answer. Actually there was an attempt to release an official empty
commons-logging at Apache recently and it was tunred down exactly
Dennis Lundberg wrote:
Lucas Bergman wrote:
Running this test with Maven 2.1.0 fails:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
[ ... ]
The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
(compile-scope) dependency, so this seems wrong.
This may be a dumb or inappropriate question, but why does Tomcat need commons
logging? Why can't it just use java util logging?
Jörg Schaible wrote:
Hi Ceki,
Ceki Gulcu wrote at Dienstag, 30. Juni 2009 16:45:
Jörg Schaible wrote:
You've been right, I should have read your question
Jörg Schaible wrote:
Lucas Bergman wrote:
Running this test with Maven 2.1.0 fails:
java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
[ ... ]
The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
(compile-scope) dependency, so this seems wrong.
Lucas Bergman wrote at Montag, 29. Juni 2009 15:25:
Jörg Schaible wrote:
Lucas Bergman wrote:
Running this test with Maven 2.1.0 fails:
java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
[ ... ]
The POM for htmlunit 2.5 declares commons-logging 1.1.1
Jörg Schaible wrote:
Lucas Bergman wrote:
Jörg Schaible wrote:
Lucas Bergman wrote:
Running this test with Maven 2.1.0 fails:
java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
[ ... ]
The POM for htmlunit 2.5 declares commons-logging
I ran into a strange dependency resolution problem at work, which a
colleague and I whittled down to a fairly simple test case. Consider
the following POM:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Lucas Bergman wrote:
I ran into a strange dependency resolution problem at work, which a
colleague and I whittled down to a fairly simple test case. Consider
the following POM:
project xmlns=http://maven.apache.org/POM/4.0.0;
I'm trying to eliminate commons-logging from being transitively passed
on to projects that depend on my library and my library uses spring.
Spring uses commons-logging but doesn't mark it as optional or
scope:provided, however when I try to exclude commons logging from a
spring dependency, I no
On 4/25/07, Trevor Torrez [EMAIL PROTECTED] wrote:
I'm trying to eliminate commons-logging from being transitively passed
on to projects that depend on my library and my library uses spring.
Spring uses commons-logging but doesn't mark it as optional or
scope:provided, however when I try to
The problem arises when blah is used as a dependency in a downstream
project that is not using commons logging at all (ie, slf4j); since
that project will not have commons logging as a dependency it gets
resolved and included in the project from the transitive dependency on
spring-dao. Since it
Thanks for this example. It's exactly what I hoped to find on Jetty website.
But I first tried to run the tests with Eclipse, and the process hangs
indefinitly on server.getThreadPool().join();
I tried to remove this line, and tests are now running fine under eclipse.
But with Maven, I
If it works under eclipse, it should work under Maven. It sounds
like maybe you didn't do a clean rebuild under Maven and the
join() is still in there.
FYI, please find attached a sample test case that works just
find under Maven.
cheers
Jan
Julien Henry wrote:
Sorry if I wasn't clear, but
Hi Jan,
Here is currently how it works. I have many JUnit tests. These tests are
grouped in a test suite called AllTests.java this way :
public class AllTests extends TestSuite {
public static Test suite() {
TestSuite suite = new TestSuite();
Julien,
You're not starting jetty6 correctly in the JettySetup setup() method.
You need to do:
Server server = new Server();
XmlConfiguration xmlConfiguration = new XmlConfiguration(jettyConfig);
xmlConfiguration.configure(server);
server.start();
server.getThreadPool().join();
Instead of
Julien,
Embedding Jetty6 is pretty simple. The jetty.xml config file is written
in a straightforward mapping from the java API to xml syntax. There is the
beginnings of a guide to embedding jetty also on the wiki at:
http://docs.codehaus.org/display/JETTY/Embedding+Jetty
Jetty is often used in
Hi,
I'm using Jetty to test my project. I have this in my pom (I use JSP) :
dependency
groupIdjetty/groupId
artifactIdorg.mortbay.jetty/artifactId
version5.1.10/version
scopetest/scope
/dependency
dependency
groupIdjetty/groupId
Hi Julien.
Jetty 5.x is built by ant, but the artifacts are made available on
ibiblio. The jetty5.x series, whilst the current stable series is
about to be superceded by the 6.x series.
Jetty 6.x is built by maven2 and has full poms with dependencies
listed which maven2 will transitively
Sounds like an error in the pom.
File a MEV bug with the proper jetty5 pom.xml file attached and
someone will update the pom on ibiblio.
Wayne
On 4/20/06, Jan Bartel [EMAIL PROTECTED] wrote:
Hi Julien.
Jetty 5.x is built by ant, but the artifacts are made available on
ibiblio. The jetty5.x
28 matches
Mail list logo
