You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Johan Compagner <jc...@gmail.com> on 2007/03/08 23:49:39 UTC
mvn eclipse:eclipse
This is a bit horrible,
If i do that then on some projects who needs java5 it uses java4, so thats
the first thing i need to change.
But the worse part is that i then also have to go over every project and
delete the wicket.jar (and the wicket-extentions.jar when used)
and assign the project :(
Can this really not be changed, because this is horrible.
johan
Re: mvn eclipse:eclipse
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Al Maw:
> Johan Compagner wrote:
>
> >that does something more. Please make a doc in every wicket
> >project pointing this build process out!
>
> :-)
>
> If we move to my proposed direcotry structure we don't need this
> any more.
>
> Time to start a vote, methinks. :-)
Before voting please explain what you intend to do.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: mvn eclipse:eclipse
Posted by Al Maw <wi...@almaw.com>.
Johan Compagner wrote:
> that does something more.
>
> Please make a doc in every wicket project pointing this build process out!
:-)
If we move to my proposed direcotry structure we don't need this any more.
Time to start a vote, methinks. :-)
Al
Re: mvn eclipse:eclipse
Posted by Johan Compagner <jc...@gmail.com>.
that does something more.
Please make a doc in every wicket project pointing this build process out!
johan
On 3/9/07, Jean-Baptiste Quenot <jb...@apache.org> wrote:
>
> * Johan Compagner:
> > I am not completely stupid :)
> >
> > if i do this:
> >
> > C:\workspace\wicket-parent>mvn eclipse:eclipse
>
> You're missing -Pjdk1.4 or -Pjdk1.5
> --
> Jean-Baptiste Quenot
> aka John Banana Qwerty
> http://caraldi.com/jbq/
>
Re: mvn eclipse:eclipse
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Johan Compagner:
> I am not completely stupid :)
>
> if i do this:
>
> C:\workspace\wicket-parent>mvn eclipse:eclipse
You're missing -Pjdk1.4 or -Pjdk1.5
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: mvn eclipse:eclipse
Posted by Johan Compagner <jc...@gmail.com>.
I am not completely stupid :)
if i do this:
C:\workspace\wicket-parent>mvn eclipse:eclipse
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building Wicket Parent
[INFO] task-segment: [eclipse:eclipse]
[INFO]
-------------------------------------------------------------------------
---
[INFO] Preparing eclipse:eclipse
[INFO] Setting property: classpath.resource.loader.class => '
org.codehaus.plexus
.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [eclipse:eclipse]
[INFO] Not running eclipse plugin goal for pom project
<<<<<<<<<<<<<<<<<<<<<<<<<<??
[INFO]
-------------------------------------------------------------------------
---
[INFO] BUILD SUCCESSFUL
[INFO]
-------------------------------------------------------------------------
---
[INFO] Total time: 1 second
[INFO] Finished at: Fri Mar 09 14:32:14 CET 2007
[INFO] Final Memory: 6M/11M
[INFO]
-------------------------------------------------------------------------
---
And nothing is changed in the wicket folders.
But again, how does it know that, how did you check it out?
Where is wicket, wicket-extentions, examples and where is wicket-parent?
and if i do then mvn eclispe:eclipse in wicket and the extentions i get in
the .classpath:
<classpathentry kind="var"
path="M2_REPO/org/apache/wicket/wicket/1.3-incubati
ng-SNAPSHOT/wicket-1.3-incubating-SNAPSHOT.jar"
sourcepath="M2_REPO/org/apache/w
icket/wicket/1.3-incubating-SNAPSHOT/wicket-
1.3-incubating-SNAPSHOT-sources.jar"
johan
On 3/9/07, Jean-Baptiste Quenot <jb...@apache.org> wrote:
>
> * Johan Compagner:
>
> > if i do mvn eclipse:eclipse in my wicket parent project (folder)
> > then nothing is happening to the other projects i have.
>
> Did you refresh your workspace after running mvn eclipse:eclipse?
> --
> Jean-Baptiste Quenot
> aka John Banana Qwerty
> http://caraldi.com/jbq/
>
Re: mvn eclipse:eclipse
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Johan Compagner:
> if i do mvn eclipse:eclipse in my wicket parent project (folder)
> then nothing is happening to the other projects i have.
Did you refresh your workspace after running mvn eclipse:eclipse?
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: mvn eclipse:eclipse
Posted by Johan Compagner <jc...@gmail.com>.
if i do mvn eclipse:eclipse in my wicket parent project (folder)
then nothing is happening to the other projects i have.
On 3/9/07, Jean-Baptiste Quenot <jb...@apache.org> wrote:
>
> * Johan Compagner:
>
> > But the worse part is that i then also have to go over every
> > project and delete the wicket.jar (and the wicket-extentions.jar
> > when used) and assign the project :(
>
> No, you don't have to if you run maven from wicket-parent.
> --
> Jean-Baptiste Quenot
> aka John Banana Qwerty
> http://caraldi.com/jbq/
>
Re: mvn eclipse:eclipse
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Johan Compagner:
> But the worse part is that i then also have to go over every
> project and delete the wicket.jar (and the wicket-extentions.jar
> when used) and assign the project :(
No, you don't have to if you run maven from wicket-parent.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: mvn eclipse:eclipse
Posted by Alastair Maw <me...@almaw.com>.
Johan Compagner wrote:
> This is a bit horrible,
> If i do that then on some projects who needs java5 it uses java4, so thats
> the first thing i need to change.
It should properly pick up to use 1.4 JDK to compile against, at least,
but not for the JRE lib to link against. I might see what is required to
sort this out and cook up an Eclipse plug-in that runs eclipse:eclipse
and then tweaks it to use a 1.4 JDK if available as the JRE container to
link against.
> But the worse part is that i then also have to go over every project and
> delete the wicket.jar (and the wicket-extentions.jar when used)
> and assign the project :(
You shouldn't have to do that unless you're running mvn eclipse:eclipse
on each project individually.
You should be able to mvn eclipse:eclipse on the top-level and have it
pull in the project deps properly. I'm off to test this, but it was
working fine the other day.
Al