thanks a lot for replaying your answer are really helpful. I am going to replay you below.
2011/4/20 Barrie Treloar <[email protected]> > On Wed, Apr 20, 2011 at 10:24 PM, Fernando Wermus > <[email protected]> wrote: > [del] > > I am trying to run mvn eclipse:eclipse in parent pom.xml without any > > success. > > I am not sure if pom.xml for constructing developer environment run mvn > > eclipse:eclipse in pom.xml parent or in itself. I am almost sure that is > > doing it in parent pom.xml without any success. > [del] > > What you have described so far appears reasonable. > > Can you please run > mvn eclipse:eclipse -Pdeveloper > and paste the error output. > I change that for <execution> <id>genero-proyectos2</id> <phase>verify</phase> <configuration> <executable>mvn</executable> <workingDirectory>${src.modulos}</workingDirectory> <arguments> <argument>-Pdesarrollo</argument> <argument>eclipse:eclipse</argument> </arguments> </configuration> <goals> <goal>exec</goal> </goals> </execution> > > I'd recommend against putting the eclipse configuration inside a profile. > What I do instead is to put this inside > build > pluginManagement > So that people can run > mvn eclipse:eclipse > without having to remember to turn on a profile > Rememeber, the eclipse plugin does not participate in the standard > lifecycle. > What we are doing with maven in development profile is: 1. checkout trunk 2. compile 3. mvn eclipse:eclipse 4. copy weblogic to a folder As you can see, we consider that maven should resolve all the problem about having a development environment. This includes some operations that are not part of standard lifecycle. Are we taking a correct path? if not, this instructions are a part needed for developers when they construct their environment. How do you recommend is it the best way to achieve this goal? > If this is for internal development inside your company, then I > recommend putting this stuff into your corporate parent pom. > That way any maven projects get this configuration - not just your project > > Personally I dont use these options below > <workspace>...</workspace> > > > <workspaceCodeStylesURL>file:///${user.home}/WorkingDirectory/${odea.cvs.branch}/env/config/IDEs/eclipse/formatting-rules.xml</workspaceCodeStylesURL> > > By doing this you've made some assumptions that may not be valid: > * that the workspace is always one directory above where you checked > out the code. > * that the code style file is in a fixed location on disk. > > Since the code style file doesn't change that regularly we do all that > manually, by downloading it and installing it via Window > > Preferences. > > If you do want to automate it then check out > > http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html > If you bundle corporate stuff into its own project, then you can use > copy-resources to put them into your target/ directory and then > reference them that way. It may be better to place them into a > different directory than target/ so they dont get deleted when you run > clean. But at least these are now project local references instead of > fixed references. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
