Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-21 Thread jeffrey ai
You will have to regenerate your eclipse settings each time that you change your pom (adding/removing a dependency for example). After that you can ** import ** your project in eclipse and you'll use the standard build of eclipse (Ctrl + B) to build your application. I think you just need to

[M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
Hi, I'm new to M2 and I use Eclipse 3.2 WTP, Maven 2.0.7 and the latest maven plugin for eclipse. I use the server integration in Eclipse to test my webapp and I set the dependency in my pom.xml. For example, I develop a Tapestry webapp so I added the tapestry-core-5.0.6 dependency in the pom.xml

RE: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Beelen, M. - SPLXL
, November 20, 2007 9:49 AM To: users@maven.apache.org Subject: [M2]Eclipse WTP, dependency, deployement, libraries Hi, I'm new to M2 and I use Eclipse 3.2 WTP, Maven 2.0.7 and the latest maven plugin for eclipse. I use the server integration in Eclipse to test my webapp and I set the dependency in my

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
PROTECTED] Sent: Tuesday, November 20, 2007 9:49 AM To: users@maven.apache.org Subject: [M2]Eclipse WTP, dependency, deployement, libraries Hi, I'm new to M2 and I use Eclipse 3.2 WTP, Maven 2.0.7 and the latest maven plugin for eclipse. I use the server integration in Eclipse to test my webapp

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Arnaud HERITIER
Did you activate the WTP support in the eclipse plugin for maven 2 ? mvn eclipse:eclipse -Dwtpversion=1.5 It's working fine generally TEll us if you have any problem, we'll try to solve them Arnaud On Nov 20, 2007 9:49 AM, Michael Bernagou [EMAIL PROTECTED] wrote: Hi, I'm new to M2 and

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Arnaud HERITIER
ok, sorry, I didn't see that you were new to M2. You have actually several choices to work with maven 2 and eclipse. The first one is to use a plugin in eclipse to launch maven 2 to build your application. There are 2 plugins actually for eclipse : - http://code.google.com/p/q4e/ which we hope

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Arnaud HERITIER
You have to launch it in your project directory. Arnaud On Nov 20, 2007 3:01 PM, Michael Bernagou [EMAIL PROTECTED] wrote: So I did it : R:\java\tools\maven-2.0.7\binmvn eclipse:eclipse -Dwtpversion=1.5 - Declipse.workspace=R:\Michael\PersonalWS [INFO] Scanning for projects... [INFO]

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
So I did it : R:\java\tools\maven-2.0.7\binmvn eclipse:eclipse -Dwtpversion=1.5 - Declipse.workspace=R:\Michael\PersonalWS [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'eclipse'. [INFO]

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
Hum, I don't know how to do that. Ok I can create a bat file to launch the command but is it to do only once? 2007/11/20, Arnaud HERITIER [EMAIL PROTECTED]: Did you activate the WTP support in the eclipse plugin for maven 2 ? mvn eclipse:eclipse -Dwtpversion=1.5 It's working fine

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
Ok I did what you explain and something happended :D It replace all my source by ... nothing and create a target/classes folder in the root project. It deleted all the lib I had in WEB-INF/lib and put only the 4 I had defined for test purpose in my pom.xml using the scope system and added them as

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Arnaud HERITIER
On Nov 20, 2007 3:19 PM, Michael Bernagou [EMAIL PROTECTED] wrote: Ok I did what you explain and something happended :D It replace all my source by ... nothing and create a target/classes folder in the root project. It deleted all the lib I had in WEB-INF/lib and put only the 4 I had defined

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
Be careful, conventions in maven are to have only one src folder by langage (src/main/java) and one artifact (a jar, a war, ..) per project. But Axis2 convention is to have web services implementation outside to be deployed in WEB-INF/services instead of WEB-INF/classes as the other... When

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
I'm completely lost. I think I'm going to restart step by step. First a Maven2 Webapp using WTP and Tapestry... and then I'll study the Axis2 plugins to integrate in my project. But, just to understand a little bit more. What you propose to me is to put my webservice sources outside the main

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Arnaud HERITIER
On Nov 20, 2007 4:54 PM, Michael Bernagou [EMAIL PROTECTED] wrote: I'm completely lost. I think I'm going to restart step by step. First a Maven2 Webapp using WTP and Tapestry... and then I'll study the Axis2 plugins to integrate in my project. You can find free books to help you on

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Michael Bernagou
Thanks a lot... I'm going to try and let you know. 2007/11/20, Arnaud HERITIER [EMAIL PROTECTED]: On Nov 20, 2007 3:52 PM, Michael Bernagou [EMAIL PROTECTED] wrote: Be careful, conventions in maven are to have only one src folder by langage (src/main/java) and one artifact (a jar, a

Re: [M2]Eclipse WTP, dependency, deployement, libraries

2007-11-20 Thread Arnaud HERITIER
On Nov 20, 2007 3:52 PM, Michael Bernagou [EMAIL PROTECTED] wrote: Be careful, conventions in maven are to have only one src folder by langage (src/main/java) and one artifact (a jar, a war, ..) per project. But Axis2 convention is to have web services implementation outside to be