Feature Requests item #1179302, was opened at 2005-04-08 17:56
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1179302&group_id=119783

Category: project/ site
Group: 1.0.0-rc1
Status: Open
Priority: 9
Submitted By: Martijn Dashorst (dashorst)
Assigned to: Martijn Dashorst (dashorst)
Summary: Add netbeans configuration docs to site

Initial Comment:
Currently it is very hard for netbeans users to
use/experience wicket. Writing some docs for the
support of netbeans will help them get the best out of
both wicket and netbeans.

>From the mailing list (by Andrew de Torres):

Exploring Wicket has been a fairly painful experience
so far
(just started yesterday).  It looks cool, and I'm
hopeful, so
I'm sticking with it.

I was immediately hit by the "spaces in Windows paths"
problem. 
In my case, I'm using NetBeans (4.0) with its
integrated Tomcat.
 NetBeans by default puts stuff in "c:\documents and
settings\(username)\.netbeans\4.0\...".  The quick
workaround is
to move the whole .netbeans tree out of "documents and
settings"
to a spaceless path.  Then you have to specify
"-userdir XXX" in
your NetBeans config file.

Since Tim Boudreau's blog led me to Wicket in the first
place, I
thought there might be other NetBeans users who might
benefit
from this tip...

-Andy

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1179302&group_id=119783


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to