You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Frank Silbermann <fr...@fedex.com> on 2008/05/01 22:51:56 UTC
Difficulty getting QuickStart
I wrote in earlier about a problem I had in less-old releases of Wicket
1.2. Since no more work is being done on that version, I thought I'd
try the sample on Wicket 1.2. I figured the easiest approach was to
download the Wicket 1.3 QuickStart application. That requires Maven,
which I've never before used. I downloaded and installed Maven (I
assume correctly) and then followed the instructions to get the
QuckStart application, but the Maven command failed with the following
output. Can anyone tell me what I did wrong? (I apologize if this is
really a Maven question, but obtaining QuickStart is my only reason for
messing with Maven.)
C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
-DarchetypeArtifactId=wicket-archetype-quickstart
-DarchetypeVersion=1.3.3 -DgroupId=com.mycompany -DartifactId=myproject
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] org.apache.maven.plugins: checking for updates from central
[WARNING] repository metadata for: 'org.apache.maven.plugins' could not
be retrieved from repository: central due to an error: Error
transferring file
[INFO] Repository 'central' will be blacklisted
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does
not exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 21 seconds
[INFO] Finished at: Thu May 01 15:42:12 CDT 2008
[INFO] Final Memory: 1M/2M
[INFO]
------------------------------------------------------------------------
/Frank
Re: Difficulty getting QuickStart
Posted by James Carman <ja...@carmanconsulting.com>.
Maven comes with an Eclipse "plugin" that allows you to generate
eclipse project files based on the pom.xml file of your project. In
the eclipse project files, they refer to an M2_REPO (the Maven2
Repository) directory as a classpath variable. You have to make sure
your Eclipse instance is configured with that variable.
On Wed, May 7, 2008 at 4:01 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Warren provided a link
> (http://herebebeasties.com/2007-10-07/wicket-quickstart/) to a very
> helpful site that demonstrates:
>
> 1. Using Maven2 to download the Wicket Quickstart project,
> 2. Downloading the Eclipse plug-in for Maven2,
> 3. Configuring Eclipse to find Maven2, and
> 4. Running the Quickstart application in Eclipse.
>
> I'm a bit confused as to the relationship between these three. The
> Maven2 documentation says that this plug-in allows maven to be run from
> within Eclipse, rather than using the command-line. But in the demo it
> seems to be doing more than that. In the demo, Eclipse complains about
> unknown dependencies in the Quickstart project until a a configuration
> variable in Eclipse is set to a Maven2 directory; then Eclipse finds the
> Quickstart's dependencies. What exactly is the relationship between
> Maven2 and Eclipse when using this plug-in? Does it tell Eclipse to
> forgo its normal project description format and instead rely on Maven2
> to describe the project and replace Eclipse' native build commands?
>
> When the demonstrator downloads the Eclipse plug-in for Maven2 (or is it
> rather a Maven2 plug-in for Eclipse?), Maven downloads a bunch of stuff
> including a Wicket jar. That surprised me. Why would it assume that a
> user of Maven2 with Eclipse would need Wicket? Is Maven2 actually smart
> enough to look in the Quickstart project to see what Eclipse needs to
> run it? What if I had installed Maven2 and the Eclipse plug-in _before_
> downloading the Quickstart project to begin developing in Wicket?
>
> Please for give my naivite, but Eclipse, Maven2 and the Wicket
> Quickstart project are all new to me, and I'm getting as to what exactly
> is the flow of information between these components as we set up the
> environment.
>
> /Frank
>
>
>
> -----Original Message-----
> From: Warren [mailto:warren@clarksnutrition.com]
> Sent: Thursday, May 01, 2008 3:58 PM
> To: users@wicket.apache.org
>
>
> Subject: RE: Difficulty getting QuickStart
>
> I was having some problems until I went to this site:
>
> http://herebebeasties.com/2007-10-07/wicket-quickstart/
>
> There is a screencast there that will show you everything. It was real
> helpful.
>
> > -----Original Message-----
> > From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
> > Sent: Thursday, May 01, 2008 1:52 PM
> > To: users@wicket.apache.org
> > Subject: Difficulty getting QuickStart
> >
> >
> > I wrote in earlier about a problem I had in less-old releases of
> > Wicket 1.2. Since no more work is being done on that version, I
> > thought I'd try the sample on Wicket 1.2. I figured the easiest
> > approach was to download the Wicket 1.3 QuickStart application. That
> > requires Maven, which I've never before used. I downloaded and
> > installed Maven (I assume correctly) and then followed the
> > instructions to get the QuckStart application, but the Maven command
> > failed with the following output. Can anyone tell me what I did
> > wrong? (I apologize if this is really a Maven question, but obtaining
> > QuickStart is my only reason for messing with Maven.)
> >
> > C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> > -DarchetypeArtifactId=wicket-archetype-quickstart
> > -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany
> > -DartifactId=myproject [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'archetype'.
> > [INFO] org.apache.maven.plugins: checking for updates from central
> > [WARNING] repository metadata for: 'org.apache.maven.plugins' could
> > not be retrieved from repository: central due to an error: Error
> > transferring file [INFO] Repository 'central' will be blacklisted
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [ERROR] BUILD ERROR
> > [INFO]
> > ----------------------------------------------------------------------
> > -- [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin'
> > does not exist or no valid version could be found [INFO]
> > ----------------------------------------------------------------------
> > -- [INFO] For more information, run Maven with the -e switch [INFO]
> > ----------------------------------------------------------------------
> > --
> > [INFO] Total time: 21 seconds
> > [INFO] Finished at: Thu May 01 15:42:12 CDT 2008 [INFO] Final Memory:
> > 1M/2M [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> >
> >
> > /Frank
> >
> >
>
>
> ---------------------------------------------------------------------
> 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: Difficulty getting QuickStart
Posted by Jeremy Thomerson <je...@thomersonfamily.com>.
If you're just getting started with Maven / Wicket QuickStart, etc, I'd
suggest the following...
Go to this page and follow the instructions on it:
http://wicket.apache.org/quickstart.html
Basically, after you have Maven properly installed, you go to the page
above, and generate the Maven command to create your project folder, like:
mvn archetype:create -DarchetypeGroupId=org.apache.wicket
-DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=1.3.3
-DgroupId=com.mycompany -DartifactId=myproject
After you've run that, you will have a folder that has your complete setup
for a Wicket application.
Then, go into Eclipse, create a new java project from existing source, and
point it to the folder you just created.
Then, you can use these commands to get you along:
This one will setup your classpath in Eclipse and attach the source for
everything that it can find source for:
mvn eclipse:eclipse -DdownloadSource=true
Create your WAR:
mvn clean package
Run your test cases:
mvn test
Create the WAR and put it into your local (or a distributed - with some
configuration) repository:
mvn install
To run your application, I find the easiest way is after importing the
project into Eclipse, and running mvn eclipse:eclipse, just run the
Start.java as a java application from within Eclipse. This will allow you
to run in debug, attach to the debugger, etc....
Hope this helps,
Jeremy Thomerson
http://www.wickettraining.com
On Wed, May 7, 2008 at 3:01 PM, Frank Silbermann <fr...@fedex.com>
wrote:
> Warren provided a link
> (http://herebebeasties.com/2007-10-07/wicket-quickstart/) to a very
> helpful site that demonstrates:
>
> 1. Using Maven2 to download the Wicket Quickstart project,
> 2. Downloading the Eclipse plug-in for Maven2,
> 3. Configuring Eclipse to find Maven2, and
> 4. Running the Quickstart application in Eclipse.
>
> I'm a bit confused as to the relationship between these three. The
> Maven2 documentation says that this plug-in allows maven to be run from
> within Eclipse, rather than using the command-line. But in the demo it
> seems to be doing more than that. In the demo, Eclipse complains about
> unknown dependencies in the Quickstart project until a a configuration
> variable in Eclipse is set to a Maven2 directory; then Eclipse finds the
> Quickstart's dependencies. What exactly is the relationship between
> Maven2 and Eclipse when using this plug-in? Does it tell Eclipse to
> forgo its normal project description format and instead rely on Maven2
> to describe the project and replace Eclipse' native build commands?
>
> When the demonstrator downloads the Eclipse plug-in for Maven2 (or is it
> rather a Maven2 plug-in for Eclipse?), Maven downloads a bunch of stuff
> including a Wicket jar. That surprised me. Why would it assume that a
> user of Maven2 with Eclipse would need Wicket? Is Maven2 actually smart
> enough to look in the Quickstart project to see what Eclipse needs to
> run it? What if I had installed Maven2 and the Eclipse plug-in _before_
> downloading the Quickstart project to begin developing in Wicket?
>
> Please for give my naivite, but Eclipse, Maven2 and the Wicket
> Quickstart project are all new to me, and I'm getting as to what exactly
> is the flow of information between these components as we set up the
> environment.
>
> /Frank
>
>
> -----Original Message-----
> From: Warren [mailto:warren@clarksnutrition.com]
> Sent: Thursday, May 01, 2008 3:58 PM
> To: users@wicket.apache.org
> Subject: RE: Difficulty getting QuickStart
>
> I was having some problems until I went to this site:
>
> http://herebebeasties.com/2007-10-07/wicket-quickstart/
>
> There is a screencast there that will show you everything. It was real
> helpful.
>
> > -----Original Message-----
> > From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
> > Sent: Thursday, May 01, 2008 1:52 PM
> > To: users@wicket.apache.org
> > Subject: Difficulty getting QuickStart
> >
> >
> > I wrote in earlier about a problem I had in less-old releases of
> > Wicket 1.2. Since no more work is being done on that version, I
> > thought I'd try the sample on Wicket 1.2. I figured the easiest
> > approach was to download the Wicket 1.3 QuickStart application. That
> > requires Maven, which I've never before used. I downloaded and
> > installed Maven (I assume correctly) and then followed the
> > instructions to get the QuckStart application, but the Maven command
> > failed with the following output. Can anyone tell me what I did
> > wrong? (I apologize if this is really a Maven question, but obtaining
> > QuickStart is my only reason for messing with Maven.)
> >
> > C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> > -DarchetypeArtifactId=wicket-archetype-quickstart
> > -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany
> > -DartifactId=myproject [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'archetype'.
> > [INFO] org.apache.maven.plugins: checking for updates from central
> > [WARNING] repository metadata for: 'org.apache.maven.plugins' could
> > not be retrieved from repository: central due to an error: Error
> > transferring file [INFO] Repository 'central' will be blacklisted
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [ERROR] BUILD ERROR
> > [INFO]
> > ----------------------------------------------------------------------
> > -- [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin'
> > does not exist or no valid version could be found [INFO]
> > ----------------------------------------------------------------------
> > -- [INFO] For more information, run Maven with the -e switch [INFO]
> > ----------------------------------------------------------------------
> > --
> > [INFO] Total time: 21 seconds
> > [INFO] Finished at: Thu May 01 15:42:12 CDT 2008 [INFO] Final Memory:
> > 1M/2M [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> >
> >
> > /Frank
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
RE: Difficulty getting QuickStart
Posted by Frank Silbermann <fr...@fedex.com>.
Warren provided a link
(http://herebebeasties.com/2007-10-07/wicket-quickstart/) to a very
helpful site that demonstrates:
1. Using Maven2 to download the Wicket Quickstart project,
2. Downloading the Eclipse plug-in for Maven2,
3. Configuring Eclipse to find Maven2, and
4. Running the Quickstart application in Eclipse.
I'm a bit confused as to the relationship between these three. The
Maven2 documentation says that this plug-in allows maven to be run from
within Eclipse, rather than using the command-line. But in the demo it
seems to be doing more than that. In the demo, Eclipse complains about
unknown dependencies in the Quickstart project until a a configuration
variable in Eclipse is set to a Maven2 directory; then Eclipse finds the
Quickstart's dependencies. What exactly is the relationship between
Maven2 and Eclipse when using this plug-in? Does it tell Eclipse to
forgo its normal project description format and instead rely on Maven2
to describe the project and replace Eclipse' native build commands?
When the demonstrator downloads the Eclipse plug-in for Maven2 (or is it
rather a Maven2 plug-in for Eclipse?), Maven downloads a bunch of stuff
including a Wicket jar. That surprised me. Why would it assume that a
user of Maven2 with Eclipse would need Wicket? Is Maven2 actually smart
enough to look in the Quickstart project to see what Eclipse needs to
run it? What if I had installed Maven2 and the Eclipse plug-in _before_
downloading the Quickstart project to begin developing in Wicket?
Please for give my naivite, but Eclipse, Maven2 and the Wicket
Quickstart project are all new to me, and I'm getting as to what exactly
is the flow of information between these components as we set up the
environment.
/Frank
-----Original Message-----
From: Warren [mailto:warren@clarksnutrition.com]
Sent: Thursday, May 01, 2008 3:58 PM
To: users@wicket.apache.org
Subject: RE: Difficulty getting QuickStart
I was having some problems until I went to this site:
http://herebebeasties.com/2007-10-07/wicket-quickstart/
There is a screencast there that will show you everything. It was real
helpful.
> -----Original Message-----
> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
> Sent: Thursday, May 01, 2008 1:52 PM
> To: users@wicket.apache.org
> Subject: Difficulty getting QuickStart
>
>
> I wrote in earlier about a problem I had in less-old releases of
> Wicket 1.2. Since no more work is being done on that version, I
> thought I'd try the sample on Wicket 1.2. I figured the easiest
> approach was to download the Wicket 1.3 QuickStart application. That
> requires Maven, which I've never before used. I downloaded and
> installed Maven (I assume correctly) and then followed the
> instructions to get the QuckStart application, but the Maven command
> failed with the following output. Can anyone tell me what I did
> wrong? (I apologize if this is really a Maven question, but obtaining
> QuickStart is my only reason for messing with Maven.)
>
> C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> -DarchetypeArtifactId=wicket-archetype-quickstart
> -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany
> -DartifactId=myproject [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO] org.apache.maven.plugins: checking for updates from central
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could
> not be retrieved from repository: central due to an error: Error
> transferring file [INFO] Repository 'central' will be blacklisted
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> -- [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin'
> does not exist or no valid version could be found [INFO]
> ----------------------------------------------------------------------
> -- [INFO] For more information, run Maven with the -e switch [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 21 seconds
> [INFO] Finished at: Thu May 01 15:42:12 CDT 2008 [INFO] Final Memory:
> 1M/2M [INFO]
> ----------------------------------------------------------------------
> --
>
>
>
> /Frank
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Difficulty getting QuickStart
Posted by Gwyn Evans <gw...@gmail.com>.
Yes, Frank was meaning anything that limits you from directly
accessing 'external' resouces, rather than anyhting stopping incoming
traffic!
/Gwyn
On Fri, May 2, 2008 at 2:09 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Of course I am. Who isn't, these days? /Frank
>
>
> -----Original Message-----
> From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
> On Behalf Of James Carman
> Sent: Thursday, May 01, 2008 4:16 PM
> To: users@wicket.apache.org
>
>
> Subject: Re: Difficulty getting QuickStart
>
> Are you behind a firewall of some sort? Or, perhaps an HTTP proxy
> server?
>
> On Thu, May 1, 2008 at 4:51 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
> > I wrote in earlier about a problem I had in less-old releases of
> > Wicket 1.2. Since no more work is being done on that version, I
> > thought I'd try the sample on Wicket 1.2. I figured the easiest
> > approach was to download the Wicket 1.3 QuickStart application. That
>
> > requires Maven, which I've never before used. I downloaded and
> > installed Maven (I assume correctly) and then followed the
> > instructions to get the QuckStart application, but the Maven command
> > failed with the following output. Can anyone tell me what I did
> > wrong? (I apologize if this is really a Maven question, but
> > obtaining QuickStart is my only reason for messing with Maven.)
> >
> > C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> > -DarchetypeArtifactId=wicket-archetype-quickstart
> > -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany
> > -DartifactId=myproject [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'archetype'.
> > [INFO] org.apache.maven.plugins: checking for updates from central
> > [WARNING] repository metadata for: 'org.apache.maven.plugins' could
> > not be retrieved from repository: central due to an error: Error
> > transferring file [INFO] Repository 'central' will be blacklisted
> > [INFO]
> >
> > ----------------------------------------------------------------------
> > --
> > [ERROR] BUILD ERROR
> > [INFO]
> >
> > ----------------------------------------------------------------------
> > -- [INFO] The plugin
> > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or
> > no valid version could be found [INFO]
> >
> > ----------------------------------------------------------------------
> > -- [INFO] For more information, run Maven with the -e switch [INFO]
> >
> > ----------------------------------------------------------------------
> > --
> > [INFO] Total time: 21 seconds
> > [INFO] Finished at: Thu May 01 15:42:12 CDT 2008 [INFO] Final
> > Memory: 1M/2M [INFO]
> >
> > ----------------------------------------------------------------------
> > --
> >
> >
> >
> > /Frank
> >
> >
>
> ---------------------------------------------------------------------
> 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: Pros and cons of WicketBench
Posted by Igor Vaynberg <ig...@gmail.com>.
the problem is i dont know eclipse internals that well. i think if
johan, or anyone else was interested in spending time on it all he
would have to do to check this out is to create a new eclipse plugin
from the tabbed editor plugin wizard and then try to embed the java
editor as one of the panes.
-igor
On Sat, May 3, 2008 at 3:38 AM, Gerolf Seitz <ge...@gmail.com> wrote:
> On Fri, May 2, 2008 at 10:05 PM, Igor Vaynberg <ig...@gmail.com>
> wrote:
>
>
> > however, it does have its problems. eclipse' java editor is not built
> > with embedding in mind, so once you start using (2) you will miss out
> > on such useful things as "mark occurences", double clicking the left
> > border to set a breakpoint ( right clicking still works ), ctrl
> > clicking into a class wont always work, etc.
> >
> > i think the idea is awesome, too bad eclipse makes it so hard to implement
> > :(
> >
>
> do you know (or can you estimate) what needs to be done to make
> the java editor more flexible regarding these issues?
>
> since we have a spy in the eclipse camp (*cough* johan *cough*),
> it's maybe worth a try.
>
> Gerolf
>
> P.S.: yes, i know johan isn't part of the JDT team ;)
>
>
>
>
> > -igor
> >
> >
> > On Fri, May 2, 2008 at 12:15 PM, Frank Silbermann
> > <fr...@fedex.com> wrote:
> > >
> > > When I was developing in Wicket 1.2 I used Jbuilder 2006; it was what
> > > the employer provided. Other developers, however, use Eclipse for
> > their
> > > (non-Wicket) projects, and Jbuilder 2007/8 are Eclipse-based, so I
> > > figured might might as well start my Wicket 1.3 experiments using
> > > Eclipse.
> > >
> > > What are the pros and (if any) cons of using the Wicket Bench plug-in?
> > > Is it worth setting up if all I'm really going to be doing is (perhaps)
> > > to upgrade a Wicket 1.2 application to Wicket 1.3?
> > >
> > > ---------------------------------------------------------------------
> > > 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: Pros and cons of WicketBench
Posted by Gerolf Seitz <ge...@gmail.com>.
On Fri, May 2, 2008 at 10:05 PM, Igor Vaynberg <ig...@gmail.com>
wrote:
> however, it does have its problems. eclipse' java editor is not built
> with embedding in mind, so once you start using (2) you will miss out
> on such useful things as "mark occurences", double clicking the left
> border to set a breakpoint ( right clicking still works ), ctrl
> clicking into a class wont always work, etc.
>
> i think the idea is awesome, too bad eclipse makes it so hard to implement
> :(
>
do you know (or can you estimate) what needs to be done to make
the java editor more flexible regarding these issues?
since we have a spy in the eclipse camp (*cough* johan *cough*),
it's maybe worth a try.
Gerolf
P.S.: yes, i know johan isn't part of the JDT team ;)
> -igor
>
>
> On Fri, May 2, 2008 at 12:15 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
> >
> > When I was developing in Wicket 1.2 I used Jbuilder 2006; it was what
> > the employer provided. Other developers, however, use Eclipse for
> their
> > (non-Wicket) projects, and Jbuilder 2007/8 are Eclipse-based, so I
> > figured might might as well start my Wicket 1.3 experiments using
> > Eclipse.
> >
> > What are the pros and (if any) cons of using the Wicket Bench plug-in?
> > Is it worth setting up if all I'm really going to be doing is (perhaps)
> > to upgrade a Wicket 1.2 application to Wicket 1.3?
> >
> > ---------------------------------------------------------------------
> > 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: Pros and cons of WicketBench
Posted by Igor Vaynberg <ig...@gmail.com>.
for me there are two cool aspects to wicket-bench:
1) refactor support - if you rename a class that extends Component it
will find any matching .html and .properties file and rename those
also
2) editor - wicketbench replaces java editor with a tabbed editor that
lets you quickly switch between java/html/properties files when you
open a class that extends Component. very handy.
however, it does have its problems. eclipse' java editor is not built
with embedding in mind, so once you start using (2) you will miss out
on such useful things as "mark occurences", double clicking the left
border to set a breakpoint ( right clicking still works ), ctrl
clicking into a class wont always work, etc.
i think the idea is awesome, too bad eclipse makes it so hard to implement :(
-igor
On Fri, May 2, 2008 at 12:15 PM, Frank Silbermann
<fr...@fedex.com> wrote:
>
> When I was developing in Wicket 1.2 I used Jbuilder 2006; it was what
> the employer provided. Other developers, however, use Eclipse for their
> (non-Wicket) projects, and Jbuilder 2007/8 are Eclipse-based, so I
> figured might might as well start my Wicket 1.3 experiments using
> Eclipse.
>
> What are the pros and (if any) cons of using the Wicket Bench plug-in?
> Is it worth setting up if all I'm really going to be doing is (perhaps)
> to upgrade a Wicket 1.2 application to Wicket 1.3?
>
> ---------------------------------------------------------------------
> 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
Pros and cons of WicketBench
Posted by Frank Silbermann <fr...@fedex.com>.
When I was developing in Wicket 1.2 I used Jbuilder 2006; it was what
the employer provided. Other developers, however, use Eclipse for their
(non-Wicket) projects, and Jbuilder 2007/8 are Eclipse-based, so I
figured might might as well start my Wicket 1.3 experiments using
Eclipse.
What are the pros and (if any) cons of using the Wicket Bench plug-in?
Is it worth setting up if all I'm really going to be doing is (perhaps)
to upgrade a Wicket 1.2 application to Wicket 1.3?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Difficulty getting QuickStart
Posted by James Carman <ja...@carmanconsulting.com>.
Maven requires some setup to get through your proxy server. Look for
your MAVEN_HOME/conf/settings.xml file. There's an example of how to
set up a proxy server. That should fix it, I would think. The
central repository is working for me. :) Good luck!
On Fri, May 2, 2008 at 9:09 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> Of course I am. Who isn't, these days? /Frank
>
>
> -----Original Message-----
> From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
> On Behalf Of James Carman
> Sent: Thursday, May 01, 2008 4:16 PM
> To: users@wicket.apache.org
>
>
> Subject: Re: Difficulty getting QuickStart
>
> Are you behind a firewall of some sort? Or, perhaps an HTTP proxy
> server?
>
> On Thu, May 1, 2008 at 4:51 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
> > I wrote in earlier about a problem I had in less-old releases of
> > Wicket 1.2. Since no more work is being done on that version, I
> > thought I'd try the sample on Wicket 1.2. I figured the easiest
> > approach was to download the Wicket 1.3 QuickStart application. That
>
> > requires Maven, which I've never before used. I downloaded and
> > installed Maven (I assume correctly) and then followed the
> > instructions to get the QuckStart application, but the Maven command
> > failed with the following output. Can anyone tell me what I did
> > wrong? (I apologize if this is really a Maven question, but
> > obtaining QuickStart is my only reason for messing with Maven.)
> >
> > C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> > -DarchetypeArtifactId=wicket-archetype-quickstart
> > -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany
> > -DartifactId=myproject [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'archetype'.
> > [INFO] org.apache.maven.plugins: checking for updates from central
> > [WARNING] repository metadata for: 'org.apache.maven.plugins' could
> > not be retrieved from repository: central due to an error: Error
> > transferring file [INFO] Repository 'central' will be blacklisted
> > [INFO]
> >
> > ----------------------------------------------------------------------
> > --
> > [ERROR] BUILD ERROR
> > [INFO]
> >
> > ----------------------------------------------------------------------
> > -- [INFO] The plugin
> > 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or
> > no valid version could be found [INFO]
> >
> > ----------------------------------------------------------------------
> > -- [INFO] For more information, run Maven with the -e switch [INFO]
> >
> > ----------------------------------------------------------------------
> > --
> > [INFO] Total time: 21 seconds
> > [INFO] Finished at: Thu May 01 15:42:12 CDT 2008 [INFO] Final
> > Memory: 1M/2M [INFO]
> >
> > ----------------------------------------------------------------------
> > --
> >
> >
> >
> > /Frank
> >
> >
>
>
>
> ---------------------------------------------------------------------
> 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: Difficulty getting QuickStart
Posted by Frank Silbermann <fr...@fedex.com>.
Of course I am. Who isn't, these days? /Frank
-----Original Message-----
From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
On Behalf Of James Carman
Sent: Thursday, May 01, 2008 4:16 PM
To: users@wicket.apache.org
Subject: Re: Difficulty getting QuickStart
Are you behind a firewall of some sort? Or, perhaps an HTTP proxy
server?
On Thu, May 1, 2008 at 4:51 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> I wrote in earlier about a problem I had in less-old releases of
> Wicket 1.2. Since no more work is being done on that version, I
> thought I'd try the sample on Wicket 1.2. I figured the easiest
> approach was to download the Wicket 1.3 QuickStart application. That
> requires Maven, which I've never before used. I downloaded and
> installed Maven (I assume correctly) and then followed the
> instructions to get the QuckStart application, but the Maven command
> failed with the following output. Can anyone tell me what I did
> wrong? (I apologize if this is really a Maven question, but
> obtaining QuickStart is my only reason for messing with Maven.)
>
> C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> -DarchetypeArtifactId=wicket-archetype-quickstart
> -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany
> -DartifactId=myproject [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO] org.apache.maven.plugins: checking for updates from central
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could
> not be retrieved from repository: central due to an error: Error
> transferring file [INFO] Repository 'central' will be blacklisted
> [INFO]
>
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
>
> ----------------------------------------------------------------------
> -- [INFO] The plugin
> 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or
> no valid version could be found [INFO]
>
> ----------------------------------------------------------------------
> -- [INFO] For more information, run Maven with the -e switch [INFO]
>
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 21 seconds
> [INFO] Finished at: Thu May 01 15:42:12 CDT 2008 [INFO] Final
> Memory: 1M/2M [INFO]
>
> ----------------------------------------------------------------------
> --
>
>
>
> /Frank
>
>
---------------------------------------------------------------------
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: Difficulty getting QuickStart
Posted by James Carman <ja...@carmanconsulting.com>.
Are you behind a firewall of some sort? Or, perhaps an HTTP proxy server?
On Thu, May 1, 2008 at 4:51 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> I wrote in earlier about a problem I had in less-old releases of Wicket
> 1.2. Since no more work is being done on that version, I thought I'd
> try the sample on Wicket 1.2. I figured the easiest approach was to
> download the Wicket 1.3 QuickStart application. That requires Maven,
> which I've never before used. I downloaded and installed Maven (I
> assume correctly) and then followed the instructions to get the
> QuckStart application, but the Maven command failed with the following
> output. Can anyone tell me what I did wrong? (I apologize if this is
> really a Maven question, but obtaining QuickStart is my only reason for
> messing with Maven.)
>
> C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> -DarchetypeArtifactId=wicket-archetype-quickstart
> -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany -DartifactId=myproject
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO] org.apache.maven.plugins: checking for updates from central
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not
> be retrieved from repository: central due to an error: Error
> transferring file
> [INFO] Repository 'central' will be blacklisted
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does
> not exist or no valid version could be found
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 21 seconds
> [INFO] Finished at: Thu May 01 15:42:12 CDT 2008
> [INFO] Final Memory: 1M/2M
> [INFO]
> ------------------------------------------------------------------------
>
>
>
> /Frank
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Difficulty getting QuickStart
Posted by Warren <wa...@clarksnutrition.com>.
I was having some problems until I went to this site:
http://herebebeasties.com/2007-10-07/wicket-quickstart/
There is a screencast there that will show you everything. It was real
helpful.
> -----Original Message-----
> From: Frank Silbermann [mailto:frank.silbermann@fedex.com]
> Sent: Thursday, May 01, 2008 1:52 PM
> To: users@wicket.apache.org
> Subject: Difficulty getting QuickStart
>
>
> I wrote in earlier about a problem I had in less-old releases of Wicket
> 1.2. Since no more work is being done on that version, I thought I'd
> try the sample on Wicket 1.2. I figured the easiest approach was to
> download the Wicket 1.3 QuickStart application. That requires Maven,
> which I've never before used. I downloaded and installed Maven (I
> assume correctly) and then followed the instructions to get the
> QuckStart application, but the Maven command failed with the following
> output. Can anyone tell me what I did wrong? (I apologize if this is
> really a Maven question, but obtaining QuickStart is my only reason for
> messing with Maven.)
>
> C:\>mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> -DarchetypeArtifactId=wicket-archetype-quickstart
> -DarchetypeVersion=1.3.3 -DgroupId=com.mycompany -DartifactId=myproject
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO] org.apache.maven.plugins: checking for updates from central
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not
> be retrieved from repository: central due to an error: Error
> transferring file
> [INFO] Repository 'central' will be blacklisted
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does
> not exist or no valid version could be found
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 21 seconds
> [INFO] Finished at: Thu May 01 15:42:12 CDT 2008
> [INFO] Final Memory: 1M/2M
> [INFO]
> ------------------------------------------------------------------------
>
>
>
> /Frank
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org