You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Stefan Lindner <li...@visionet.de> on 2009/07/23 12:54:09 UTC
Maven with Eclipse
Hi Tauren,
wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
have commit acces and now I'm starting over with development.
Current steps:
1. Add keypressed detection
2. Separate the Project into small pieces
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Maven with Eclipse
Posted by Tauren Mills <yo...@gmail.com>.
Looks good to me. I'm looking forward to seeing your efforts!
I will hopefully be getting to adding DND to my project soon. Once I
do that, I'm planning to create a new example or update the existing
example to make it more attractive looking.
No offense, but when I first tried out the WicketJQuery example, it
kind of turned me off because it was quite messy and confusing. Once I
played with it some, it all made sense and I realized it would work
well for me. But initial impressions are important.
Tauren
On Thu, Jul 23, 2009 at 10:13 AM, Stefan Lindner<li...@visionet.de> wrote:
> Tauren,
>
> I think tooltips should be separated too. The layout will be
>
> jwicket-parent
> jwicket-core (both jwicket core and ui core)
> jwicket-plugins
> jwicket-ui-dragdrop
> jwicket-ui-resize
> jwicket-tooltip-variantA
> jwicket-tooltip-variantB
> jwicket-tooltip-variantC
> jwicket-examples
>
> Stefan
> -----Ursprüngliche Nachricht-----
> Von: Tauren Mills [mailto:yowzator@gmail.com]
> Gesendet: Donnerstag, 23. Juli 2009 18:30
> An: users@wicket.apache.org
> Betreff: Re: Maven with Eclipse
>
> Stefan,
>
> I'm using m2eclipse. But it can take a little getting used to. I also
> think it causes an occasional eclipse crash. However, I'm still glad
> to have it. Never tried the other one.
>
> Once m2eclipse installed, go to your SVN Repositories perspective,
> browse the wicketstuff-core project. Right click onto jwicket and
> select "Check out as Maven project". This will download all of the
> jwicket projects (jwicket-parent, jwicket, jwicket-examples), give
> each of them an eclipse project with maven support enabled, and
> activate subversion support. Pretty seamless to then start working
> and committing.
>
> I still find that I need to use the "mvn install" command from the
> command line sometimes to get things deployed to my local repo.
>
> How do you want to structure the sub-projects. Perhaps something like this?
>
> jwicket-parent
> jwicket
> jwicket-core
> jwicket-ui-core
> jwicket-plugins
> jwicket-ui-drag
> jwicket-ui-drop
> jwicket-ui-resize
> jwicket-tooltip
> jwicket-examples
>
> Or maybe:
>
> jwicket-parent
> jwicket-core (both jwicket core and ui core)
> jwicket-plugins
> jwicket-ui-dragdrop
> jwicket-ui-resize
> jwicket-tooltip
> jwicket-examples
>
> Should tooltips be separated into different projects too?
>
> I don't think we should go too far overboard on modularization.
>
> Tauren
>
>
> On Thu, Jul 23, 2009 at 3:54 AM, Stefan Lindner<li...@visionet.de> wrote:
>> Hi Tauren,
>>
>> wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
>> have commit acces and now I'm starting over with development.
>> Current steps:
>> 1. Add keypressed detection
>> 2. Separate the Project into small pieces
>>
>> Stefan
>>
>> ---------------------------------------------------------------------
>> 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
AW: Maven with Eclipse
Posted by Stefan Lindner <li...@visionet.de>.
Tauren,
I think tooltips should be separated too. The layout will be
jwicket-parent
jwicket-core (both jwicket core and ui core)
jwicket-plugins
jwicket-ui-dragdrop
jwicket-ui-resize
jwicket-tooltip-variantA
jwicket-tooltip-variantB
jwicket-tooltip-variantC
jwicket-examples
Stefan
-----Ursprüngliche Nachricht-----
Von: Tauren Mills [mailto:yowzator@gmail.com]
Gesendet: Donnerstag, 23. Juli 2009 18:30
An: users@wicket.apache.org
Betreff: Re: Maven with Eclipse
Stefan,
I'm using m2eclipse. But it can take a little getting used to. I also
think it causes an occasional eclipse crash. However, I'm still glad
to have it. Never tried the other one.
Once m2eclipse installed, go to your SVN Repositories perspective,
browse the wicketstuff-core project. Right click onto jwicket and
select "Check out as Maven project". This will download all of the
jwicket projects (jwicket-parent, jwicket, jwicket-examples), give
each of them an eclipse project with maven support enabled, and
activate subversion support. Pretty seamless to then start working
and committing.
I still find that I need to use the "mvn install" command from the
command line sometimes to get things deployed to my local repo.
How do you want to structure the sub-projects. Perhaps something like this?
jwicket-parent
jwicket
jwicket-core
jwicket-ui-core
jwicket-plugins
jwicket-ui-drag
jwicket-ui-drop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Or maybe:
jwicket-parent
jwicket-core (both jwicket core and ui core)
jwicket-plugins
jwicket-ui-dragdrop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Should tooltips be separated into different projects too?
I don't think we should go too far overboard on modularization.
Tauren
On Thu, Jul 23, 2009 at 3:54 AM, Stefan Lindner<li...@visionet.de> wrote:
> Hi Tauren,
>
> wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
> have commit acces and now I'm starting over with development.
> Current steps:
> 1. Add keypressed detection
> 2. Separate the Project into small pieces
>
> Stefan
>
> ---------------------------------------------------------------------
> 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: Maven with Eclipse
Posted by Tauren Mills <yo...@gmail.com>.
Stefan,
I'm using m2eclipse. But it can take a little getting used to. I also
think it causes an occasional eclipse crash. However, I'm still glad
to have it. Never tried the other one.
Once m2eclipse installed, go to your SVN Repositories perspective,
browse the wicketstuff-core project. Right click onto jwicket and
select "Check out as Maven project". This will download all of the
jwicket projects (jwicket-parent, jwicket, jwicket-examples), give
each of them an eclipse project with maven support enabled, and
activate subversion support. Pretty seamless to then start working
and committing.
I still find that I need to use the "mvn install" command from the
command line sometimes to get things deployed to my local repo.
How do you want to structure the sub-projects. Perhaps something like this?
jwicket-parent
jwicket
jwicket-core
jwicket-ui-core
jwicket-plugins
jwicket-ui-drag
jwicket-ui-drop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Or maybe:
jwicket-parent
jwicket-core (both jwicket core and ui core)
jwicket-plugins
jwicket-ui-dragdrop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Should tooltips be separated into different projects too?
I don't think we should go too far overboard on modularization.
Tauren
On Thu, Jul 23, 2009 at 3:54 AM, Stefan Lindner<li...@visionet.de> wrote:
> Hi Tauren,
>
> wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
> have commit acces and now I'm starting over with development.
> Current steps:
> 1. Add keypressed detection
> 2. Separate the Project into small pieces
>
> Stefan
>
> ---------------------------------------------------------------------
> 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