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
jer...@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),
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 jer...@dijkmeijer.comwrote:
Hi,
I think this is more of a maven question, so its also posted at the maven
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
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
... 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
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
mvn eclipse:eclipse already does that for you (2.7)
Martijn
On Wed, Feb 10, 2010 at 7:20 PM, Igor Vaynberg igor.vaynb...@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
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
martijn.dasho...@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
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!
youre welcome ;)
-igor
On Wed, Feb 10, 2010 at 11:27 AM, Jeremy Thomerson
jer...@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
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 igor.vaynb...@gmail.com wrote:
mvn eclipse:eclipse only work across the modules of the same
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
12 matches
Mail list logo
