You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Steve Swinsburg <s....@lancaster.ac.uk> on 2009/03/12 19:39:22 UTC
building a wicket app with maven 1
Hi all,
I have a need to backport my wicket app that builds perfectly in
Maven2 to Maven1. I think I've adjusted all the pom.xml to project.xml
correctly as all the classes and dependent jars looks like they are
where they need to be, but on startup I get this:
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
Although in my WEB-INF/lib I have (amongst the others) the required
jars:
slf4j-log4j12-1.4.2.jar
log4j-1.2.14.jar
Any idea what's missing? Does anyone else build under Maven1?
thanks,
Steve
Re: building a wicket app with maven 1
Posted by Igor Vaynberg <ig...@gmail.com>.
mvn dependency:tree is your friend
-Igor
On 3/13/09, Stephen Swinsburg <s....@lancaster.ac.uk> wrote:
> Spot on, it's been a while since I've done Maven1 work and this has
> caught me out previously I just didn't think of it this time! I'll
> double check the jars that are in my Maven2 webapp and presume I will
> find that jar missing from the Maven1 build.
>
> Thanks Linda and Adriano!
>
>
> On 13/03/2009, at 8:05 AM, Linda van der Pal wrote:
>
>> Maven2 handles transitive dependencies, meaning that if a project
>> you are dependent on is dependent on other projects, Maven will add
>> them to the classpath. So that's why you didn't have to add that jar
>> manually, Maven did it for you. I don't think Maven1 had this
>> functionality.
>>
>> Linda
>>
>> Stephen Swinsburg wrote:
>>> Thanks Adriano. I don't seem to need that for my Maven2 build
>>> though, is there a reason for that? I'll try that though.
>>>
>>>
>>> cheers,
>>> Steve
>>>
>>>
>>>
>>> On 12/03/2009, at 8:02 PM, Adriano dos Santos Fernandes wrote:
>>>
>>>> Steve Swinsburg escreveu:
>>>>> Hi all,
>>>>>
>>>>> I have a need to backport my wicket app that builds perfectly in
>>>>> Maven2 to Maven1. I think I've adjusted all the pom.xml to
>>>>> project.xml correctly as all the classes and dependent jars looks
>>>>> like they are where they need to be, but on startup I get this:
>>>>>
>>>>> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>>>>
>>>>> Although in my WEB-INF/lib I have (amongst the others) the
>>>>> required jars:
>>>>>
>>>>> slf4j-log4j12-1.4.2.jar
>>>>> log4j-1.2.14.jar
>>>>>
>>>>>
>>>>> Any idea what's missing? Does anyone else build under Maven1?
>>>> You also need slf4j-api-*.jar.
>>>>
>>>>
>>>> Adriano
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>> ------------------------------------------------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com Version: 8.5.278 / Virus Database:
>>> 270.11.10/1996 - Release Date: 03/11/09 20:42:00
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: building a wicket app with maven 1
Posted by Steve Swinsburg <s....@lancaster.ac.uk>.
Yes I do, but the particular framework they are building this app into
requires Maven1 unfortunately. Recent iterations of it are now on M2
its just a legacy version they are running and can't upgrade due to
various factors.
cheers,
Steve
On 13 Mar 2009, at 08:55, Martijn Dashorst wrote:
> You (and presumably your client) do know that maven 1 is a
> technological, and evolutional dead end just like the dodo, right?
>
> Martijn
>
> On Fri, Mar 13, 2009 at 9:35 AM, Stephen Swinsburg
> <s....@lancaster.ac.uk> wrote:
>> Spot on, it's been a while since I've done Maven1 work and this has
>> caught
>> me out previously I just didn't think of it this time! I'll double
>> check the
>> jars that are in my Maven2 webapp and presume I will find that jar
>> missing
>> from the Maven1 build.
>>
>> Thanks Linda and Adriano!
>>
>>
>> On 13/03/2009, at 8:05 AM, Linda van der Pal wrote:
>>
>>> Maven2 handles transitive dependencies, meaning that if a project
>>> you are
>>> dependent on is dependent on other projects, Maven will add them
>>> to the
>>> classpath. So that's why you didn't have to add that jar manually,
>>> Maven did
>>> it for you. I don't think Maven1 had this functionality.
>>>
>>> Linda
>>>
>>> Stephen Swinsburg wrote:
>>>>
>>>> Thanks Adriano. I don't seem to need that for my Maven2 build
>>>> though, is
>>>> there a reason for that? I'll try that though.
>>>>
>>>>
>>>> cheers,
>>>> Steve
>>>>
>>>>
>>>>
>>>> On 12/03/2009, at 8:02 PM, Adriano dos Santos Fernandes wrote:
>>>>
>>>>> Steve Swinsburg escreveu:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I have a need to backport my wicket app that builds perfectly
>>>>>> in Maven2
>>>>>> to Maven1. I think I've adjusted all the pom.xml to project.xml
>>>>>> correctly as
>>>>>> all the classes and dependent jars looks like they are where
>>>>>> they need to
>>>>>> be, but on startup I get this:
>>>>>>
>>>>>> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>>>>>
>>>>>> Although in my WEB-INF/lib I have (amongst the others) the
>>>>>> required
>>>>>> jars:
>>>>>>
>>>>>> slf4j-log4j12-1.4.2.jar
>>>>>> log4j-1.2.14.jar
>>>>>>
>>>>>>
>>>>>> Any idea what's missing? Does anyone else build under Maven1?
>>>>>
>>>>> You also need slf4j-api-*.jar.
>>>>>
>>>>>
>>>>> Adriano
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> No virus found in this incoming message.
>>>> Checked by AVG - www.avg.com Version: 8.5.278 / Virus Database:
>>>> 270.11.10/1996 - Release Date: 03/11/09 20:42:00
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
Re: building a wicket app with maven 1
Posted by Martijn Dashorst <ma...@gmail.com>.
You (and presumably your client) do know that maven 1 is a
technological, and evolutional dead end just like the dodo, right?
Martijn
On Fri, Mar 13, 2009 at 9:35 AM, Stephen Swinsburg
<s....@lancaster.ac.uk> wrote:
> Spot on, it's been a while since I've done Maven1 work and this has caught
> me out previously I just didn't think of it this time! I'll double check the
> jars that are in my Maven2 webapp and presume I will find that jar missing
> from the Maven1 build.
>
> Thanks Linda and Adriano!
>
>
> On 13/03/2009, at 8:05 AM, Linda van der Pal wrote:
>
>> Maven2 handles transitive dependencies, meaning that if a project you are
>> dependent on is dependent on other projects, Maven will add them to the
>> classpath. So that's why you didn't have to add that jar manually, Maven did
>> it for you. I don't think Maven1 had this functionality.
>>
>> Linda
>>
>> Stephen Swinsburg wrote:
>>>
>>> Thanks Adriano. I don't seem to need that for my Maven2 build though, is
>>> there a reason for that? I'll try that though.
>>>
>>>
>>> cheers,
>>> Steve
>>>
>>>
>>>
>>> On 12/03/2009, at 8:02 PM, Adriano dos Santos Fernandes wrote:
>>>
>>>> Steve Swinsburg escreveu:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I have a need to backport my wicket app that builds perfectly in Maven2
>>>>> to Maven1. I think I've adjusted all the pom.xml to project.xml correctly as
>>>>> all the classes and dependent jars looks like they are where they need to
>>>>> be, but on startup I get this:
>>>>>
>>>>> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>>>>
>>>>> Although in my WEB-INF/lib I have (amongst the others) the required
>>>>> jars:
>>>>>
>>>>> slf4j-log4j12-1.4.2.jar
>>>>> log4j-1.2.14.jar
>>>>>
>>>>>
>>>>> Any idea what's missing? Does anyone else build under Maven1?
>>>>
>>>> You also need slf4j-api-*.jar.
>>>>
>>>>
>>>> Adriano
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>> ------------------------------------------------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com Version: 8.5.278 / Virus Database:
>>> 270.11.10/1996 - Release Date: 03/11/09 20:42:00
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: building a wicket app with maven 1
Posted by Stephen Swinsburg <s....@lancaster.ac.uk>.
Spot on, it's been a while since I've done Maven1 work and this has
caught me out previously I just didn't think of it this time! I'll
double check the jars that are in my Maven2 webapp and presume I will
find that jar missing from the Maven1 build.
Thanks Linda and Adriano!
On 13/03/2009, at 8:05 AM, Linda van der Pal wrote:
> Maven2 handles transitive dependencies, meaning that if a project
> you are dependent on is dependent on other projects, Maven will add
> them to the classpath. So that's why you didn't have to add that jar
> manually, Maven did it for you. I don't think Maven1 had this
> functionality.
>
> Linda
>
> Stephen Swinsburg wrote:
>> Thanks Adriano. I don't seem to need that for my Maven2 build
>> though, is there a reason for that? I'll try that though.
>>
>>
>> cheers,
>> Steve
>>
>>
>>
>> On 12/03/2009, at 8:02 PM, Adriano dos Santos Fernandes wrote:
>>
>>> Steve Swinsburg escreveu:
>>>> Hi all,
>>>>
>>>> I have a need to backport my wicket app that builds perfectly in
>>>> Maven2 to Maven1. I think I've adjusted all the pom.xml to
>>>> project.xml correctly as all the classes and dependent jars looks
>>>> like they are where they need to be, but on startup I get this:
>>>>
>>>> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>>>
>>>> Although in my WEB-INF/lib I have (amongst the others) the
>>>> required jars:
>>>>
>>>> slf4j-log4j12-1.4.2.jar
>>>> log4j-1.2.14.jar
>>>>
>>>>
>>>> Any idea what's missing? Does anyone else build under Maven1?
>>> You also need slf4j-api-*.jar.
>>>
>>>
>>> Adriano
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com Version: 8.5.278 / Virus Database:
>> 270.11.10/1996 - Release Date: 03/11/09 20:42:00
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: building a wicket app with maven 1
Posted by Linda van der Pal <lv...@heritageagenturen.nl>.
Maven2 handles transitive dependencies, meaning that if a project you
are dependent on is dependent on other projects, Maven will add them to
the classpath. So that's why you didn't have to add that jar manually,
Maven did it for you. I don't think Maven1 had this functionality.
Linda
Stephen Swinsburg wrote:
> Thanks Adriano. I don't seem to need that for my Maven2 build though,
> is there a reason for that? I'll try that though.
>
>
> cheers,
> Steve
>
>
>
> On 12/03/2009, at 8:02 PM, Adriano dos Santos Fernandes wrote:
>
>> Steve Swinsburg escreveu:
>>> Hi all,
>>>
>>> I have a need to backport my wicket app that builds perfectly in
>>> Maven2 to Maven1. I think I've adjusted all the pom.xml to
>>> project.xml correctly as all the classes and dependent jars looks
>>> like they are where they need to be, but on startup I get this:
>>>
>>> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>>
>>> Although in my WEB-INF/lib I have (amongst the others) the required
>>> jars:
>>>
>>> slf4j-log4j12-1.4.2.jar
>>> log4j-1.2.14.jar
>>>
>>>
>>> Any idea what's missing? Does anyone else build under Maven1?
>> You also need slf4j-api-*.jar.
>>
>>
>> Adriano
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.278 / Virus Database: 270.11.10/1996 - Release Date: 03/11/09 20:42:00
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: building a wicket app with maven 1
Posted by Stephen Swinsburg <s....@lancaster.ac.uk>.
Thanks Adriano. I don't seem to need that for my Maven2 build though,
is there a reason for that? I'll try that though.
cheers,
Steve
On 12/03/2009, at 8:02 PM, Adriano dos Santos Fernandes wrote:
> Steve Swinsburg escreveu:
>> Hi all,
>>
>> I have a need to backport my wicket app that builds perfectly in
>> Maven2 to Maven1. I think I've adjusted all the pom.xml to
>> project.xml correctly as all the classes and dependent jars looks
>> like they are where they need to be, but on startup I get this:
>>
>> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>
>> Although in my WEB-INF/lib I have (amongst the others) the required
>> jars:
>>
>> slf4j-log4j12-1.4.2.jar
>> log4j-1.2.14.jar
>>
>>
>> Any idea what's missing? Does anyone else build under Maven1?
> You also need slf4j-api-*.jar.
>
>
> Adriano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: building a wicket app with maven 1
Posted by Adriano dos Santos Fernandes <ad...@gmail.com>.
Steve Swinsburg escreveu:
> Hi all,
>
> I have a need to backport my wicket app that builds perfectly in
> Maven2 to Maven1. I think I've adjusted all the pom.xml to project.xml
> correctly as all the classes and dependent jars looks like they are
> where they need to be, but on startup I get this:
>
> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>
> Although in my WEB-INF/lib I have (amongst the others) the required jars:
>
> slf4j-log4j12-1.4.2.jar
> log4j-1.2.14.jar
>
>
> Any idea what's missing? Does anyone else build under Maven1?
You also need slf4j-api-*.jar.
Adriano
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: building a wicket app with maven 1
Posted by Stephen Swinsburg <s....@lancaster.ac.uk>.
Ok I'll post when I get back into the office.
I was mainly wondering if anyone knew of some major issue with Maven1
and Wicket/SLF4J - ie the versions in the Maven repositories etc. I
note that the Maven1 repo now uses the Maven2 artifacts.
I guess, in order to rule out Maven, I could just place the right jars
in the right spot manually and see if that works ;)
Steve
On 12/03/2009, at 6:47 PM, Jeremy Thomerson wrote:
> It's very unlikely that someone will be able to help you without
> actually
> seeing the POM / XML file(s). Also, you might try the Maven mailing
> list.
> But at least supply the file - it will surely increase your chances of
> finding assistance here.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Thu, Mar 12, 2009 at 1:39 PM, Steve Swinsburg <
> s.swinsburg@lancaster.ac.uk> wrote:
>
>> Hi all,
>> I have a need to backport my wicket app that builds perfectly in
>> Maven2 to
>> Maven1. I think I've adjusted all the pom.xml to project.xml
>> correctly as
>> all the classes and dependent jars looks like they are where they
>> need to
>> be, but on startup I get this:
>>
>> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>
>> Although in my WEB-INF/lib I have (amongst the others) the required
>> jars:
>>
>> slf4j-log4j12-1.4.2.jar
>> log4j-1.2.14.jar
>>
>>
>> Any idea what's missing? Does anyone else build under Maven1?
>>
>> thanks,
>> Steve
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: building a wicket app with maven 1
Posted by Jeremy Thomerson <je...@wickettraining.com>.
It's very unlikely that someone will be able to help you without actually
seeing the POM / XML file(s). Also, you might try the Maven mailing list.
But at least supply the file - it will surely increase your chances of
finding assistance here.
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, Mar 12, 2009 at 1:39 PM, Steve Swinsburg <
s.swinsburg@lancaster.ac.uk> wrote:
> Hi all,
> I have a need to backport my wicket app that builds perfectly in Maven2 to
> Maven1. I think I've adjusted all the pom.xml to project.xml correctly as
> all the classes and dependent jars looks like they are where they need to
> be, but on startup I get this:
>
> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>
> Although in my WEB-INF/lib I have (amongst the others) the required jars:
>
> slf4j-log4j12-1.4.2.jar
> log4j-1.2.14.jar
>
>
> Any idea what's missing? Does anyone else build under Maven1?
>
> thanks,
> Steve
>
>
>