Miks, I am not sure if this would be possible. For instance, in your eclipse project you have a "flat" list of dependent libraries whereas in maven most of the dependencies are resolved for you.
E.g. if you put a dependency on hibernate in your pom maven figures out which dependencies hibernate has, in eclipse you have to to this all by yourself. In our team the pom is leading. Every time something .classpath or ,project related changes in the pom we run eclipse:eclipse and are up to date on the eclipse side. rgds, Kees > > It doesn't. It generates Eclipse project out of Maven's project. What I > need is as minumum vice versa -- I do have projects in Eclipse and I > need to have pom.xml generated and kept up to date, as developers > continue development in Eclipse. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
