[
http://jira.codehaus.org/browse/MECLIPSE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87211
]
Rob Baily commented on MECLIPSE-78:
-----------------------------------
Martin, your setup looks correct to me and it looks like the same thing we have
done. Do the child POMs reference back to the parent? They do for us and that
is how the configuration is passed down. I think otherwise you would need to
put the configuration in each.
I'm still not really clear on your point in #2. Your second configuration
appears to be like what you have. I presume that this is better since now you
don't have to specify all of those things. If your problem is that with the
first configuration that it appears twice then that seems likely as I hadn't
considered what happens if the config exists manually. What I'm not sure about
is whether this is consistent with other items or not. Meaning for other
configurations do they only should up once if entered manually and the
m2eclipse flag is set.
I believe that what you have patched is the only thing I have done. No waste
of my time. :) If it is working for you at some level then hopefully you can
keep going like that until they decide to push this into the project at some
point.
> create eclipse projects which are m2eclipse ready
> -------------------------------------------------
>
> Key: MECLIPSE-78
> URL: http://jira.codehaus.org/browse/MECLIPSE-78
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Environment: Fedora Core 3, Sun JDK 1.5.0.06, Eclipse 3.1.1, Maven
> 2.0.2
> Reporter: Joshua Nichols
> Attachments: m2eclipse-add-repo-tag-2.3.patch,
> m2eclipse-add-repo.patch, m2eclipse.patch, m2eclipse.patch, m2eclipse.patch,
> m2eclipse.patch, MECLIPSE-78-tag-2.3-rev2.patch, MECLIPSE-78-tag-2.3.patch,
> MECLIPSE-78.patch
>
>
> WIth the recent development of the m2eclipse plugin, I believe it is useful
> to create eclipse projects via mvn eclipse:eclipse that use m2eclipse from
> the start. One of the advantages of using m2eclipse is that you don't have to
> rerun eclipse:eclipse when you update any dependencies.
> A few things are necessary to accomplish this, in terms of changes to
> .classpath and .project.
> .project needs a new nature and builder added. For the builder:
> <buildCommand>
> <name>org.maven.ide.eclipse.maven2Builder</name>
> <arguments/>
> </buildCommand>
> For the nature:
> <nature>org.maven.ide.eclipse.maven2Nature</nature>
> In the .classpath, we need to add:
> <classpathentry kind="con"
> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
> In .classpath, you also don't want entries <classpathentry kind="var"
> path="M2_REPO/blah/blah/x.y.z/blah-x.y.z.jar"/>, because they would conflict
> with m2eclipse setting up the classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
