Re: mvn eclipse:plugin and project inheritance
yes, that is the way it is currently set up On 5/17/06, Taavi Sildeberg <[EMAIL PROTECTED]> wrote: Hello David, Do you have inside a module A and s module B parent defined? Something like this: your parent groupid your parent artifact id your parent version Taavi Davis Ford wrote: > Hi, I have a parent pom.xml project in C:\someplace\pom.xml that has > > moduleA > moduleB > > Then I have > > C:\someplace\moduleA\pom.xml > C:\someplace\moduleB\pom.xml > > If I execute: > > C:\someplace\>mvn clean > C:\someplace\>mvn compile > C:\someplace\>mvn test > > That works great for moduleA, moduleB > > If I execute: > > C:\someplace\moduleA\mvn eclipse:eclipse > C:\someplace\moduleB\mvn eclipse:eclipse > > That works great to create eclipse projects for moduleA, moduleB > > If I execute: > > C:\someplace\mvn eclipse:eclipse > > This causes a problem. If I refresh moduleA, moduleB projects in > eclipse after doing so, they complain about not finding the other > subprojects. > > What is the best-practice here? Is there a workaround for this? > > Thanks in advance, > Davis > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Zeno Consulting, Inc. (248) 894-4922 (p) (206) 202-4077 (f) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn eclipse:plugin and project inheritance
Hello David, Do you have inside a module A and s module B parent defined? Something like this: your parent groupid your parent artifact id your parent version Taavi Davis Ford wrote: Hi, I have a parent pom.xml project in C:\someplace\pom.xml that has moduleA moduleB Then I have C:\someplace\moduleA\pom.xml C:\someplace\moduleB\pom.xml If I execute: C:\someplace\>mvn clean C:\someplace\>mvn compile C:\someplace\>mvn test That works great for moduleA, moduleB If I execute: C:\someplace\moduleA\mvn eclipse:eclipse C:\someplace\moduleB\mvn eclipse:eclipse That works great to create eclipse projects for moduleA, moduleB If I execute: C:\someplace\mvn eclipse:eclipse This causes a problem. If I refresh moduleA, moduleB projects in eclipse after doing so, they complain about not finding the other subprojects. What is the best-practice here? Is there a workaround for this? Thanks in advance, Davis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn eclipse:plugin and project inheritance
Hi, I have a parent pom.xml project in C:\someplace\pom.xml that has moduleA moduleB Then I have C:\someplace\moduleA\pom.xml C:\someplace\moduleB\pom.xml If I execute: C:\someplace\>mvn clean C:\someplace\>mvn compile C:\someplace\>mvn test That works great for moduleA, moduleB If I execute: C:\someplace\moduleA\mvn eclipse:eclipse C:\someplace\moduleB\mvn eclipse:eclipse That works great to create eclipse projects for moduleA, moduleB If I execute: C:\someplace\mvn eclipse:eclipse This causes a problem. If I refresh moduleA, moduleB projects in eclipse after doing so, they complain about not finding the other subprojects. What is the best-practice here? Is there a workaround for this? Thanks in advance, Davis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
