You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Jeroen Dijkmeijer <je...@dijkmeijer.com> on 2010/02/10 17:05:12 UTC
adding the wicket project for debugging etc
Hi,
I think this is more of a maven question, so its also posted at the
maven user list.
I'm trying to understand wicket a bit more, and I would like it to
add it as source tree to my project, but for for some reason I cant
make it happen.
I have myproject-web, myproject-domain and myproject-parent. The
latter specifying the former 2 as modules. I'm running myproject-web
in tomcat which is configured in eclipse wtp. Myproject-web holds a
reference to wicket as a dependency and I can see the myproject-domain
project.
Now I would like to add wicket with the proper release tag as a source
tree to the project, so I can set debug breakpoints, add log stmts,
take short cuts, break code fix it. All to get a better understanding
what's happening under the hood. Wicket in itself has many subprojects
which i don't need all in the source tree (but I guess it would not be
a disaster if they were).
So I checked out the wicket source from svn to some directory (The
wicket project has a parent pom in the root, and all the other
projects are its siblings) Imported that directory into eclipse, and
added the sub-project wicket as a module to myproject-parent, but that
does not work for me. Also eclipse does not recognize the added wicket
source tree, when opening the declaration it goes straight to the
Wicket-Object.class and shows the attached source code instead of the
code from the newly added source tree. I tried a few other things but
that didnot show the source at best (often I could not even get tomcat
start up)
I'm pretty sure its al very simple but somehow i cant get it to work.
regards,
Jeroen.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: adding the wicket project for debugging etc
Posted by Martijn Dashorst <ma...@gmail.com>.
You have to have added the projects to your workspace before you can
make it work.
Martijn
On Wed, Feb 10, 2010 at 9:07 PM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> Didn't work for me - I had a workspace that had a secular project in it,
> Wicket 1.4.x and Brix trunk (1.0.1-snapshot), and it didn't auto-discover
> anything outside of each individual project.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Wed, Feb 10, 2010 at 2:01 PM, Martijn Dashorst <
> martijn.dashorst@gmail.com> wrote:
>
>> Nope. If it finds the source for a dependency in your workspace then
>> the project is added instead. It even discovers wrong versions and
>> logs them :)
>>
>> Martijn
>>
>> On Wed, Feb 10, 2010 at 8:13 PM, Igor Vaynberg <ig...@gmail.com>
>> wrote:
>> > mvn eclipse:eclipse only work across the modules of the same project,
>> > but not across projects
>> >
>> > -igor
>> >
>> > On Wed, Feb 10, 2010 at 11:10 AM, Martijn Dashorst
>> > <ma...@gmail.com> wrote:
>> >> mvn eclipse:eclipse already does that for you (2.7)
>> >>
>> >> Martijn
>> >>
>> >> On Wed, Feb 10, 2010 at 7:20 PM, Igor Vaynberg <ig...@gmail.com>
>> wrote:
>> >>> you can check out wicket from svn, mvn eclipse:eclipse and import the
>> >>> projects into your workspace. then use something like
>> >>> mvnlink.googlecode.com to make your projects use the imported wicket
>> >>> projects as dependencies instead of jars.
>> >>>
>> >>> -igor
>> >>>
>> >>> On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
>> >>> <je...@dijkmeijer.com> wrote:
>> >>>> Yeah seen it done it been there.
>> >>>> But that doesn't give me the wicket source, which I can debug, or
>> modify.
>> >>>>
>> >>>> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>> >>>>
>> >>>>> Do you know [1]? It is very easy to develop using that approach.
>> >>>>>
>> >>>>> Regards,
>> >>>>>
>> >>>>> Ernesto
>> >>>>>
>> >>>>> [1]-http://wicket.apache.org/quickstart.html
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>> >>>>> <je...@dijkmeijer.com>wrote:
>> >>>>>
>> >>>>>> Hi,
>> >>>>>>
>> >>>>>> I think this is more of a maven question, so its also posted at the
>> maven
>> >>>>>> user list.
>> >>>>>> I'm trying to understand wicket a bit more, and I would like it to
>> add it
>> >>>>>> as source tree to my project, but for for some reason I cant make it
>> >>>>>> happen.
>> >>>>>> I have myproject-web, myproject-domain and myproject-parent. The
>> latter
>> >>>>>> specifying the former 2 as modules. I'm running myproject-web in
>> tomcat
>> >>>>>> which is configured in eclipse wtp. Myproject-web holds a reference
>> to
>> >>>>>> wicket as a dependency and I can see the myproject-domain project.
>> >>>>>> Now I would like to add wicket with the proper release tag as a
>> source
>> >>>>>> tree
>> >>>>>> to the project, so I can set debug breakpoints, add log stmts, take
>> short
>> >>>>>> cuts, break code fix it. All to get a better understanding what's
>> >>>>>> happening
>> >>>>>> under the hood. Wicket in itself has many subprojects which i don't
>> need
>> >>>>>> all
>> >>>>>> in the source tree (but I guess it would not be a disaster if they
>> were).
>> >>>>>> So I checked out the wicket source from svn to some directory (The
>> wicket
>> >>>>>> project has a parent pom in the root, and all the other projects
>> are its
>> >>>>>> siblings) Imported that directory into eclipse, and added the
>> sub-project
>> >>>>>> wicket as a module to myproject-parent, but that does not work for
>> me.
>> >>>>>> Also
>> >>>>>> eclipse does not recognize the added wicket source tree, when
>> opening the
>> >>>>>> declaration it goes straight to the Wicket-Object.class and shows
>> the
>> >>>>>> attached source code instead of the code from the newly added source
>> >>>>>> tree. I
>> >>>>>> tried a few other things but that didnot show the source at best
>> (often I
>> >>>>>> could not even get tomcat start up)
>> >>>>>> I'm pretty sure its al very simple but somehow i cant get it to
>> work.
>> >>>>>>
>> >>>>>> regards,
>> >>>>>> Jeroen.
>> >>>>>>
>> >>>>>>
>> ---------------------------------------------------------------------
>> >>>>>> 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
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> >> Apache Wicket 1.4 increases type safety for web applications
>> >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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.4 increases type safety for web applications
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>>
>> ---------------------------------------------------------------------
>> 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.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: adding the wicket project for debugging etc
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Didn't work for me - I had a workspace that had a secular project in it,
Wicket 1.4.x and Brix trunk (1.0.1-snapshot), and it didn't auto-discover
anything outside of each individual project.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Feb 10, 2010 at 2:01 PM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:
> Nope. If it finds the source for a dependency in your workspace then
> the project is added instead. It even discovers wrong versions and
> logs them :)
>
> Martijn
>
> On Wed, Feb 10, 2010 at 8:13 PM, Igor Vaynberg <ig...@gmail.com>
> wrote:
> > mvn eclipse:eclipse only work across the modules of the same project,
> > but not across projects
> >
> > -igor
> >
> > On Wed, Feb 10, 2010 at 11:10 AM, Martijn Dashorst
> > <ma...@gmail.com> wrote:
> >> mvn eclipse:eclipse already does that for you (2.7)
> >>
> >> Martijn
> >>
> >> On Wed, Feb 10, 2010 at 7:20 PM, Igor Vaynberg <ig...@gmail.com>
> wrote:
> >>> you can check out wicket from svn, mvn eclipse:eclipse and import the
> >>> projects into your workspace. then use something like
> >>> mvnlink.googlecode.com to make your projects use the imported wicket
> >>> projects as dependencies instead of jars.
> >>>
> >>> -igor
> >>>
> >>> On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
> >>> <je...@dijkmeijer.com> wrote:
> >>>> Yeah seen it done it been there.
> >>>> But that doesn't give me the wicket source, which I can debug, or
> modify.
> >>>>
> >>>> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
> >>>>
> >>>>> Do you know [1]? It is very easy to develop using that approach.
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Ernesto
> >>>>>
> >>>>> [1]-http://wicket.apache.org/quickstart.html
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
> >>>>> <je...@dijkmeijer.com>wrote:
> >>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> I think this is more of a maven question, so its also posted at the
> maven
> >>>>>> user list.
> >>>>>> I'm trying to understand wicket a bit more, and I would like it to
> add it
> >>>>>> as source tree to my project, but for for some reason I cant make it
> >>>>>> happen.
> >>>>>> I have myproject-web, myproject-domain and myproject-parent. The
> latter
> >>>>>> specifying the former 2 as modules. I'm running myproject-web in
> tomcat
> >>>>>> which is configured in eclipse wtp. Myproject-web holds a reference
> to
> >>>>>> wicket as a dependency and I can see the myproject-domain project.
> >>>>>> Now I would like to add wicket with the proper release tag as a
> source
> >>>>>> tree
> >>>>>> to the project, so I can set debug breakpoints, add log stmts, take
> short
> >>>>>> cuts, break code fix it. All to get a better understanding what's
> >>>>>> happening
> >>>>>> under the hood. Wicket in itself has many subprojects which i don't
> need
> >>>>>> all
> >>>>>> in the source tree (but I guess it would not be a disaster if they
> were).
> >>>>>> So I checked out the wicket source from svn to some directory (The
> wicket
> >>>>>> project has a parent pom in the root, and all the other projects
> are its
> >>>>>> siblings) Imported that directory into eclipse, and added the
> sub-project
> >>>>>> wicket as a module to myproject-parent, but that does not work for
> me.
> >>>>>> Also
> >>>>>> eclipse does not recognize the added wicket source tree, when
> opening the
> >>>>>> declaration it goes straight to the Wicket-Object.class and shows
> the
> >>>>>> attached source code instead of the code from the newly added source
> >>>>>> tree. I
> >>>>>> tried a few other things but that didnot show the source at best
> (often I
> >>>>>> could not even get tomcat start up)
> >>>>>> I'm pretty sure its al very simple but somehow i cant get it to
> work.
> >>>>>>
> >>>>>> regards,
> >>>>>> Jeroen.
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> 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
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Become a Wicket expert, learn from the best: http://wicketinaction.com
> >> Apache Wicket 1.4 increases type safety for web applications
> >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
> >>
> >> ---------------------------------------------------------------------
> >> 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.4 increases type safety for web applications
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: adding the wicket project for debugging etc
Posted by Martijn Dashorst <ma...@gmail.com>.
Nope. If it finds the source for a dependency in your workspace then
the project is added instead. It even discovers wrong versions and
logs them :)
Martijn
On Wed, Feb 10, 2010 at 8:13 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> mvn eclipse:eclipse only work across the modules of the same project,
> but not across projects
>
> -igor
>
> On Wed, Feb 10, 2010 at 11:10 AM, Martijn Dashorst
> <ma...@gmail.com> wrote:
>> mvn eclipse:eclipse already does that for you (2.7)
>>
>> Martijn
>>
>> On Wed, Feb 10, 2010 at 7:20 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>>> you can check out wicket from svn, mvn eclipse:eclipse and import the
>>> projects into your workspace. then use something like
>>> mvnlink.googlecode.com to make your projects use the imported wicket
>>> projects as dependencies instead of jars.
>>>
>>> -igor
>>>
>>> On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
>>> <je...@dijkmeijer.com> wrote:
>>>> Yeah seen it done it been there.
>>>> But that doesn't give me the wicket source, which I can debug, or modify.
>>>>
>>>> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>>>>
>>>>> Do you know [1]? It is very easy to develop using that approach.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Ernesto
>>>>>
>>>>> [1]-http://wicket.apache.org/quickstart.html
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>>>>> <je...@dijkmeijer.com>wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I think this is more of a maven question, so its also posted at the maven
>>>>>> user list.
>>>>>> I'm trying to understand wicket a bit more, and I would like it to add it
>>>>>> as source tree to my project, but for for some reason I cant make it
>>>>>> happen.
>>>>>> I have myproject-web, myproject-domain and myproject-parent. The latter
>>>>>> specifying the former 2 as modules. I'm running myproject-web in tomcat
>>>>>> which is configured in eclipse wtp. Myproject-web holds a reference to
>>>>>> wicket as a dependency and I can see the myproject-domain project.
>>>>>> Now I would like to add wicket with the proper release tag as a source
>>>>>> tree
>>>>>> to the project, so I can set debug breakpoints, add log stmts, take short
>>>>>> cuts, break code fix it. All to get a better understanding what's
>>>>>> happening
>>>>>> under the hood. Wicket in itself has many subprojects which i don't need
>>>>>> all
>>>>>> in the source tree (but I guess it would not be a disaster if they were).
>>>>>> So I checked out the wicket source from svn to some directory (The wicket
>>>>>> project has a parent pom in the root, and all the other projects are its
>>>>>> siblings) Imported that directory into eclipse, and added the sub-project
>>>>>> wicket as a module to myproject-parent, but that does not work for me.
>>>>>> Also
>>>>>> eclipse does not recognize the added wicket source tree, when opening the
>>>>>> declaration it goes straight to the Wicket-Object.class and shows the
>>>>>> attached source code instead of the code from the newly added source
>>>>>> tree. I
>>>>>> tried a few other things but that didnot show the source at best (often I
>>>>>> could not even get tomcat start up)
>>>>>> I'm pretty sure its al very simple but somehow i cant get it to work.
>>>>>>
>>>>>> regards,
>>>>>> Jeroen.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.4 increases type safety for web applications
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>>
>> ---------------------------------------------------------------------
>> 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.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: adding the wicket project for debugging etc
Posted by Igor Vaynberg <ig...@gmail.com>.
mvn eclipse:eclipse only work across the modules of the same project,
but not across projects
-igor
On Wed, Feb 10, 2010 at 11:10 AM, Martijn Dashorst
<ma...@gmail.com> wrote:
> mvn eclipse:eclipse already does that for you (2.7)
>
> Martijn
>
> On Wed, Feb 10, 2010 at 7:20 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>> you can check out wicket from svn, mvn eclipse:eclipse and import the
>> projects into your workspace. then use something like
>> mvnlink.googlecode.com to make your projects use the imported wicket
>> projects as dependencies instead of jars.
>>
>> -igor
>>
>> On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
>> <je...@dijkmeijer.com> wrote:
>>> Yeah seen it done it been there.
>>> But that doesn't give me the wicket source, which I can debug, or modify.
>>>
>>> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>>>
>>>> Do you know [1]? It is very easy to develop using that approach.
>>>>
>>>> Regards,
>>>>
>>>> Ernesto
>>>>
>>>> [1]-http://wicket.apache.org/quickstart.html
>>>>
>>>>
>>>>
>>>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>>>> <je...@dijkmeijer.com>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I think this is more of a maven question, so its also posted at the maven
>>>>> user list.
>>>>> I'm trying to understand wicket a bit more, and I would like it to add it
>>>>> as source tree to my project, but for for some reason I cant make it
>>>>> happen.
>>>>> I have myproject-web, myproject-domain and myproject-parent. The latter
>>>>> specifying the former 2 as modules. I'm running myproject-web in tomcat
>>>>> which is configured in eclipse wtp. Myproject-web holds a reference to
>>>>> wicket as a dependency and I can see the myproject-domain project.
>>>>> Now I would like to add wicket with the proper release tag as a source
>>>>> tree
>>>>> to the project, so I can set debug breakpoints, add log stmts, take short
>>>>> cuts, break code fix it. All to get a better understanding what's
>>>>> happening
>>>>> under the hood. Wicket in itself has many subprojects which i don't need
>>>>> all
>>>>> in the source tree (but I guess it would not be a disaster if they were).
>>>>> So I checked out the wicket source from svn to some directory (The wicket
>>>>> project has a parent pom in the root, and all the other projects are its
>>>>> siblings) Imported that directory into eclipse, and added the sub-project
>>>>> wicket as a module to myproject-parent, but that does not work for me.
>>>>> Also
>>>>> eclipse does not recognize the added wicket source tree, when opening the
>>>>> declaration it goes straight to the Wicket-Object.class and shows the
>>>>> attached source code instead of the code from the newly added source
>>>>> tree. I
>>>>> tried a few other things but that didnot show the source at best (often I
>>>>> could not even get tomcat start up)
>>>>> I'm pretty sure its al very simple but somehow i cant get it to work.
>>>>>
>>>>> regards,
>>>>> Jeroen.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.4 increases type safety for web applications
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>
> ---------------------------------------------------------------------
> 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: adding the wicket project for debugging etc
Posted by Martijn Dashorst <ma...@gmail.com>.
mvn eclipse:eclipse already does that for you (2.7)
Martijn
On Wed, Feb 10, 2010 at 7:20 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> you can check out wicket from svn, mvn eclipse:eclipse and import the
> projects into your workspace. then use something like
> mvnlink.googlecode.com to make your projects use the imported wicket
> projects as dependencies instead of jars.
>
> -igor
>
> On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
> <je...@dijkmeijer.com> wrote:
>> Yeah seen it done it been there.
>> But that doesn't give me the wicket source, which I can debug, or modify.
>>
>> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>>
>>> Do you know [1]? It is very easy to develop using that approach.
>>>
>>> Regards,
>>>
>>> Ernesto
>>>
>>> [1]-http://wicket.apache.org/quickstart.html
>>>
>>>
>>>
>>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>>> <je...@dijkmeijer.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> I think this is more of a maven question, so its also posted at the maven
>>>> user list.
>>>> I'm trying to understand wicket a bit more, and I would like it to add it
>>>> as source tree to my project, but for for some reason I cant make it
>>>> happen.
>>>> I have myproject-web, myproject-domain and myproject-parent. The latter
>>>> specifying the former 2 as modules. I'm running myproject-web in tomcat
>>>> which is configured in eclipse wtp. Myproject-web holds a reference to
>>>> wicket as a dependency and I can see the myproject-domain project.
>>>> Now I would like to add wicket with the proper release tag as a source
>>>> tree
>>>> to the project, so I can set debug breakpoints, add log stmts, take short
>>>> cuts, break code fix it. All to get a better understanding what's
>>>> happening
>>>> under the hood. Wicket in itself has many subprojects which i don't need
>>>> all
>>>> in the source tree (but I guess it would not be a disaster if they were).
>>>> So I checked out the wicket source from svn to some directory (The wicket
>>>> project has a parent pom in the root, and all the other projects are its
>>>> siblings) Imported that directory into eclipse, and added the sub-project
>>>> wicket as a module to myproject-parent, but that does not work for me.
>>>> Also
>>>> eclipse does not recognize the added wicket source tree, when opening the
>>>> declaration it goes straight to the Wicket-Object.class and shows the
>>>> attached source code instead of the code from the newly added source
>>>> tree. I
>>>> tried a few other things but that didnot show the source at best (often I
>>>> could not even get tomcat start up)
>>>> I'm pretty sure its al very simple but somehow i cant get it to work.
>>>>
>>>> regards,
>>>> Jeroen.
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: adding the wicket project for debugging etc
Posted by Igor Vaynberg <ig...@gmail.com>.
youre welcome ;)
-igor
On Wed, Feb 10, 2010 at 11:27 AM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> Igor - how many cool OS projects are you allowed to crank out? I wish I
> knew about this one a couple weeks ago when I was trying to setup a dev
> environment for a secular project + brix + wicket and link them all together
> in Eclipse so that a change in any of them appeared in the others.
>
> Cool!
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
> On Wed, Feb 10, 2010 at 12:20 PM, Igor Vaynberg <ig...@gmail.com>wrote:
>
>> you can check out wicket from svn, mvn eclipse:eclipse and import the
>> projects into your workspace. then use something like
>> mvnlink.googlecode.com to make your projects use the imported wicket
>> projects as dependencies instead of jars.
>>
>> -igor
>>
>> On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
>> <je...@dijkmeijer.com> wrote:
>> > Yeah seen it done it been there.
>> > But that doesn't give me the wicket source, which I can debug, or modify.
>> >
>> > On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>> >
>> >> Do you know [1]? It is very easy to develop using that approach.
>> >>
>> >> Regards,
>> >>
>> >> Ernesto
>> >>
>> >> [1]-http://wicket.apache.org/quickstart.html
>> >>
>> >>
>> >>
>> >> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>> >> <je...@dijkmeijer.com>wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I think this is more of a maven question, so its also posted at the
>> maven
>> >>> user list.
>> >>> I'm trying to understand wicket a bit more, and I would like it to add
>> it
>> >>> as source tree to my project, but for for some reason I cant make it
>> >>> happen.
>> >>> I have myproject-web, myproject-domain and myproject-parent. The latter
>> >>> specifying the former 2 as modules. I'm running myproject-web in tomcat
>> >>> which is configured in eclipse wtp. Myproject-web holds a reference to
>> >>> wicket as a dependency and I can see the myproject-domain project.
>> >>> Now I would like to add wicket with the proper release tag as a source
>> >>> tree
>> >>> to the project, so I can set debug breakpoints, add log stmts, take
>> short
>> >>> cuts, break code fix it. All to get a better understanding what's
>> >>> happening
>> >>> under the hood. Wicket in itself has many subprojects which i don't
>> need
>> >>> all
>> >>> in the source tree (but I guess it would not be a disaster if they
>> were).
>> >>> So I checked out the wicket source from svn to some directory (The
>> wicket
>> >>> project has a parent pom in the root, and all the other projects are
>> its
>> >>> siblings) Imported that directory into eclipse, and added the
>> sub-project
>> >>> wicket as a module to myproject-parent, but that does not work for me.
>> >>> Also
>> >>> eclipse does not recognize the added wicket source tree, when opening
>> the
>> >>> declaration it goes straight to the Wicket-Object.class and shows the
>> >>> attached source code instead of the code from the newly added source
>> >>> tree. I
>> >>> tried a few other things but that didnot show the source at best (often
>> I
>> >>> could not even get tomcat start up)
>> >>> I'm pretty sure its al very simple but somehow i cant get it to work.
>> >>>
>> >>> regards,
>> >>> Jeroen.
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> 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
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: adding the wicket project for debugging etc
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Igor - how many cool OS projects are you allowed to crank out? I wish I
knew about this one a couple weeks ago when I was trying to setup a dev
environment for a secular project + brix + wicket and link them all together
in Eclipse so that a change in any of them appeared in the others.
Cool!
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Feb 10, 2010 at 12:20 PM, Igor Vaynberg <ig...@gmail.com>wrote:
> you can check out wicket from svn, mvn eclipse:eclipse and import the
> projects into your workspace. then use something like
> mvnlink.googlecode.com to make your projects use the imported wicket
> projects as dependencies instead of jars.
>
> -igor
>
> On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
> <je...@dijkmeijer.com> wrote:
> > Yeah seen it done it been there.
> > But that doesn't give me the wicket source, which I can debug, or modify.
> >
> > On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
> >
> >> Do you know [1]? It is very easy to develop using that approach.
> >>
> >> Regards,
> >>
> >> Ernesto
> >>
> >> [1]-http://wicket.apache.org/quickstart.html
> >>
> >>
> >>
> >> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
> >> <je...@dijkmeijer.com>wrote:
> >>
> >>> Hi,
> >>>
> >>> I think this is more of a maven question, so its also posted at the
> maven
> >>> user list.
> >>> I'm trying to understand wicket a bit more, and I would like it to add
> it
> >>> as source tree to my project, but for for some reason I cant make it
> >>> happen.
> >>> I have myproject-web, myproject-domain and myproject-parent. The latter
> >>> specifying the former 2 as modules. I'm running myproject-web in tomcat
> >>> which is configured in eclipse wtp. Myproject-web holds a reference to
> >>> wicket as a dependency and I can see the myproject-domain project.
> >>> Now I would like to add wicket with the proper release tag as a source
> >>> tree
> >>> to the project, so I can set debug breakpoints, add log stmts, take
> short
> >>> cuts, break code fix it. All to get a better understanding what's
> >>> happening
> >>> under the hood. Wicket in itself has many subprojects which i don't
> need
> >>> all
> >>> in the source tree (but I guess it would not be a disaster if they
> were).
> >>> So I checked out the wicket source from svn to some directory (The
> wicket
> >>> project has a parent pom in the root, and all the other projects are
> its
> >>> siblings) Imported that directory into eclipse, and added the
> sub-project
> >>> wicket as a module to myproject-parent, but that does not work for me.
> >>> Also
> >>> eclipse does not recognize the added wicket source tree, when opening
> the
> >>> declaration it goes straight to the Wicket-Object.class and shows the
> >>> attached source code instead of the code from the newly added source
> >>> tree. I
> >>> tried a few other things but that didnot show the source at best (often
> I
> >>> could not even get tomcat start up)
> >>> I'm pretty sure its al very simple but somehow i cant get it to work.
> >>>
> >>> regards,
> >>> Jeroen.
> >>>
> >>> ---------------------------------------------------------------------
> >>> 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: adding the wicket project for debugging etc
Posted by Igor Vaynberg <ig...@gmail.com>.
you can check out wicket from svn, mvn eclipse:eclipse and import the
projects into your workspace. then use something like
mvnlink.googlecode.com to make your projects use the imported wicket
projects as dependencies instead of jars.
-igor
On Wed, Feb 10, 2010 at 9:44 AM, Jeroen Dijkmeijer
<je...@dijkmeijer.com> wrote:
> Yeah seen it done it been there.
> But that doesn't give me the wicket source, which I can debug, or modify.
>
> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>
>> Do you know [1]? It is very easy to develop using that approach.
>>
>> Regards,
>>
>> Ernesto
>>
>> [1]-http://wicket.apache.org/quickstart.html
>>
>>
>>
>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>> <je...@dijkmeijer.com>wrote:
>>
>>> Hi,
>>>
>>> I think this is more of a maven question, so its also posted at the maven
>>> user list.
>>> I'm trying to understand wicket a bit more, and I would like it to add it
>>> as source tree to my project, but for for some reason I cant make it
>>> happen.
>>> I have myproject-web, myproject-domain and myproject-parent. The latter
>>> specifying the former 2 as modules. I'm running myproject-web in tomcat
>>> which is configured in eclipse wtp. Myproject-web holds a reference to
>>> wicket as a dependency and I can see the myproject-domain project.
>>> Now I would like to add wicket with the proper release tag as a source
>>> tree
>>> to the project, so I can set debug breakpoints, add log stmts, take short
>>> cuts, break code fix it. All to get a better understanding what's
>>> happening
>>> under the hood. Wicket in itself has many subprojects which i don't need
>>> all
>>> in the source tree (but I guess it would not be a disaster if they were).
>>> So I checked out the wicket source from svn to some directory (The wicket
>>> project has a parent pom in the root, and all the other projects are its
>>> siblings) Imported that directory into eclipse, and added the sub-project
>>> wicket as a module to myproject-parent, but that does not work for me.
>>> Also
>>> eclipse does not recognize the added wicket source tree, when opening the
>>> declaration it goes straight to the Wicket-Object.class and shows the
>>> attached source code instead of the code from the newly added source
>>> tree. I
>>> tried a few other things but that didnot show the source at best (often I
>>> could not even get tomcat start up)
>>> I'm pretty sure its al very simple but somehow i cant get it to work.
>>>
>>> regards,
>>> Jeroen.
>>>
>>> ---------------------------------------------------------------------
>>> 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: adding the wicket project for debugging etc
Posted by Cemal Bayramoglu <jW...@cabouge.com>.
... or checkout from SVN [1] if you want to modify Wicket sources
beyond what the debugger allows.
Regards - Cemal
jWeekend
OO & Java Technologies, Wicket
Consulting, Development, Training
http://jWeekend.com
[1] http://wicket.apache.org/building-from-svn.html
On 10 February 2010 17:53, Cemal Bayramoglu <jW...@cabouge.com> wrote:
> Jeroen ,
>
> mvn eclipse:eclipse -DdownloadSources=true
>
> See http://wicket.apache.org/quickstart.html for full instructions.
>
>
> Regards - Cemal
> jWeekend
> OO & Java Technologies, Wicket
> Consulting, Development, Training
> http://jWeekend.com
>
>
>
>
> On 10 February 2010 17:44, Jeroen Dijkmeijer <je...@dijkmeijer.com> wrote:
>> Yeah seen it done it been there.
>> But that doesn't give me the wicket source, which I can debug, or modify.
>>
>> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>>
>>> Do you know [1]? It is very easy to develop using that approach.
>>>
>>> Regards,
>>>
>>> Ernesto
>>>
>>> [1]-http://wicket.apache.org/quickstart.html
>>>
>>>
>>>
>>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>>> <je...@dijkmeijer.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> I think this is more of a maven question, so its also posted at the maven
>>>> user list.
>>>> I'm trying to understand wicket a bit more, and I would like it to add it
>>>> as source tree to my project, but for for some reason I cant make it
>>>> happen.
>>>> I have myproject-web, myproject-domain and myproject-parent. The latter
>>>> specifying the former 2 as modules. I'm running myproject-web in tomcat
>>>> which is configured in eclipse wtp. Myproject-web holds a reference to
>>>> wicket as a dependency and I can see the myproject-domain project.
>>>> Now I would like to add wicket with the proper release tag as a source
>>>> tree
>>>> to the project, so I can set debug breakpoints, add log stmts, take short
>>>> cuts, break code fix it. All to get a better understanding what's
>>>> happening
>>>> under the hood. Wicket in itself has many subprojects which i don't need
>>>> all
>>>> in the source tree (but I guess it would not be a disaster if they were).
>>>> So I checked out the wicket source from svn to some directory (The wicket
>>>> project has a parent pom in the root, and all the other projects are its
>>>> siblings) Imported that directory into eclipse, and added the sub-project
>>>> wicket as a module to myproject-parent, but that does not work for me.
>>>> Also
>>>> eclipse does not recognize the added wicket source tree, when opening the
>>>> declaration it goes straight to the Wicket-Object.class and shows the
>>>> attached source code instead of the code from the newly added source
>>>> tree. I
>>>> tried a few other things but that didnot show the source at best (often I
>>>> could not even get tomcat start up)
>>>> I'm pretty sure its al very simple but somehow i cant get it to work.
>>>>
>>>> regards,
>>>> Jeroen.
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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: adding the wicket project for debugging etc
Posted by Cemal Bayramoglu <jW...@cabouge.com>.
Jeroen ,
mvn eclipse:eclipse -DdownloadSources=true
See http://wicket.apache.org/quickstart.html for full instructions.
Regards - Cemal
jWeekend
OO & Java Technologies, Wicket
Consulting, Development, Training
http://jWeekend.com
On 10 February 2010 17:44, Jeroen Dijkmeijer <je...@dijkmeijer.com> wrote:
> Yeah seen it done it been there.
> But that doesn't give me the wicket source, which I can debug, or modify.
>
> On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
>
>> Do you know [1]? It is very easy to develop using that approach.
>>
>> Regards,
>>
>> Ernesto
>>
>> [1]-http://wicket.apache.org/quickstart.html
>>
>>
>>
>> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer
>> <je...@dijkmeijer.com>wrote:
>>
>>> Hi,
>>>
>>> I think this is more of a maven question, so its also posted at the maven
>>> user list.
>>> I'm trying to understand wicket a bit more, and I would like it to add it
>>> as source tree to my project, but for for some reason I cant make it
>>> happen.
>>> I have myproject-web, myproject-domain and myproject-parent. The latter
>>> specifying the former 2 as modules. I'm running myproject-web in tomcat
>>> which is configured in eclipse wtp. Myproject-web holds a reference to
>>> wicket as a dependency and I can see the myproject-domain project.
>>> Now I would like to add wicket with the proper release tag as a source
>>> tree
>>> to the project, so I can set debug breakpoints, add log stmts, take short
>>> cuts, break code fix it. All to get a better understanding what's
>>> happening
>>> under the hood. Wicket in itself has many subprojects which i don't need
>>> all
>>> in the source tree (but I guess it would not be a disaster if they were).
>>> So I checked out the wicket source from svn to some directory (The wicket
>>> project has a parent pom in the root, and all the other projects are its
>>> siblings) Imported that directory into eclipse, and added the sub-project
>>> wicket as a module to myproject-parent, but that does not work for me.
>>> Also
>>> eclipse does not recognize the added wicket source tree, when opening the
>>> declaration it goes straight to the Wicket-Object.class and shows the
>>> attached source code instead of the code from the newly added source
>>> tree. I
>>> tried a few other things but that didnot show the source at best (often I
>>> could not even get tomcat start up)
>>> I'm pretty sure its al very simple but somehow i cant get it to work.
>>>
>>> regards,
>>> Jeroen.
>>>
>>> ---------------------------------------------------------------------
>>> 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: adding the wicket project for debugging etc
Posted by Jeroen Dijkmeijer <je...@dijkmeijer.com>.
Yeah seen it done it been there.
But that doesn't give me the wicket source, which I can debug, or
modify.
On Feb 10, 2010, at 5:13 PM, Ernesto Reinaldo Barreiro wrote:
> Do you know [1]? It is very easy to develop using that approach.
>
> Regards,
>
> Ernesto
>
> [1]-http://wicket.apache.org/quickstart.html
>
>
>
> On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer <jeroen@dijkmeijer.com
> >wrote:
>
>> Hi,
>>
>> I think this is more of a maven question, so its also posted at the
>> maven
>> user list.
>> I'm trying to understand wicket a bit more, and I would like it to
>> add it
>> as source tree to my project, but for for some reason I cant make
>> it happen.
>> I have myproject-web, myproject-domain and myproject-parent. The
>> latter
>> specifying the former 2 as modules. I'm running myproject-web in
>> tomcat
>> which is configured in eclipse wtp. Myproject-web holds a reference
>> to
>> wicket as a dependency and I can see the myproject-domain project.
>> Now I would like to add wicket with the proper release tag as a
>> source tree
>> to the project, so I can set debug breakpoints, add log stmts, take
>> short
>> cuts, break code fix it. All to get a better understanding what's
>> happening
>> under the hood. Wicket in itself has many subprojects which i don't
>> need all
>> in the source tree (but I guess it would not be a disaster if they
>> were).
>> So I checked out the wicket source from svn to some directory (The
>> wicket
>> project has a parent pom in the root, and all the other projects
>> are its
>> siblings) Imported that directory into eclipse, and added the sub-
>> project
>> wicket as a module to myproject-parent, but that does not work for
>> me. Also
>> eclipse does not recognize the added wicket source tree, when
>> opening the
>> declaration it goes straight to the Wicket-Object.class and shows the
>> attached source code instead of the code from the newly added
>> source tree. I
>> tried a few other things but that didnot show the source at best
>> (often I
>> could not even get tomcat start up)
>> I'm pretty sure its al very simple but somehow i cant get it to work.
>>
>> regards,
>> Jeroen.
>>
>> ---------------------------------------------------------------------
>> 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: adding the wicket project for debugging etc
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Do you know [1]? It is very easy to develop using that approach.
Regards,
Ernesto
[1]-http://wicket.apache.org/quickstart.html
On Wed, Feb 10, 2010 at 5:05 PM, Jeroen Dijkmeijer <je...@dijkmeijer.com>wrote:
> Hi,
>
> I think this is more of a maven question, so its also posted at the maven
> user list.
> I'm trying to understand wicket a bit more, and I would like it to add it
> as source tree to my project, but for for some reason I cant make it happen.
> I have myproject-web, myproject-domain and myproject-parent. The latter
> specifying the former 2 as modules. I'm running myproject-web in tomcat
> which is configured in eclipse wtp. Myproject-web holds a reference to
> wicket as a dependency and I can see the myproject-domain project.
> Now I would like to add wicket with the proper release tag as a source tree
> to the project, so I can set debug breakpoints, add log stmts, take short
> cuts, break code fix it. All to get a better understanding what's happening
> under the hood. Wicket in itself has many subprojects which i don't need all
> in the source tree (but I guess it would not be a disaster if they were).
> So I checked out the wicket source from svn to some directory (The wicket
> project has a parent pom in the root, and all the other projects are its
> siblings) Imported that directory into eclipse, and added the sub-project
> wicket as a module to myproject-parent, but that does not work for me. Also
> eclipse does not recognize the added wicket source tree, when opening the
> declaration it goes straight to the Wicket-Object.class and shows the
> attached source code instead of the code from the newly added source tree. I
> tried a few other things but that didnot show the source at best (often I
> could not even get tomcat start up)
> I'm pretty sure its al very simple but somehow i cant get it to work.
>
> regards,
> Jeroen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>