Its always helpful to be over-specific in emails. I'm having to make assumptions about your environment that are likely incorrect and so the advice is not as good as it could be.
In your original email you say "it doesn't create any." referring to eclipse project files (like .project, .classpath, etc) In Roland's reply he asks whether it creates the files. In your reply you say the files are not created. Do you mean .project, .classpath, etc are not created at all? Remember that mvn eclipse:eclipse just automates what you can do manually. Have you been able to manually import the projects into eclipse and setup their classpaths? In the fourth email, you reply with a bit more detail. You say that you have a separate pom.xml for constructing the developers environment. Roland's reply "I presume that the POM you are using is *not* the one you call 'parent' in your structure" As he rightly points out if it is not parent, then mvn eclipse:eclipse will be working with the wrong information. If you have moved the common configuration into a profile in the parent pom.xml then you may be ok. Are the projects (A, B, C) modules of parent? If they are not modules then mvn doesn't know about them, so neither will eclipse:eclipse. However thinking about this, I don't think maven dynamically load the pom.xml files, it think it reads them all at startup. So its possible that you can't do a checkout, which creates the modules, and then invoke eclipse:eclipse in a single invocation of mvn. You need to be aware of a bug (I dont have the jira for it) where multiple executions at the same phase do not have a defined ordering. Thus, when you have everything in you profile as phase=verify, you need to carefully watch the output to see that the execution.id printed out when maven is run is the order that you expect things to be in. It is very possible that your problem is that eclipse:eclipse is being run prior to checking anything out. The only way to fix this is to use different phases. I do wonder why you are trying to automate a task that is done infrequently. Once you have manually checked out the project you never need to do this again (you only do syncs). Reasons for checking out another instance of the project may include preparing for a release, or branch, or perhaps your workflow requires bugs to be worked on in separate workspaces. Once checked out you manually run eclipse:eclipse. Reasons for re-running eclipse:eclipse are because dependencies have changed (either the project has been released, something you depend upon has bug fixes and you want a different version, or new dependencies have been added). I think you would be better off including the step by step instructions in a readme.txt file, your wiki, or a batch file. Trying to do this in Maven doesn't feel like the right thing to do. Maven manages your build lifecycle and checkout and eclipse:eclipse are not part of that build lifecycle, they are steps prior to that. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
