Hi, we have the same plugin configuration in the Hibernate Search pom. Mainly because Sanne is an Eclipse user. Personally I never liked it and I think IDE settings have no place in a pom. I never understood why m2e decided for this approach. Glad to hear that this seems to go away and I will be happy top remove this again from the pom. Also as Max pointed out, for the current master branch of Hibernate ORM it is not an issue, because we are using gradle there.
Bottom line, -1 for IDE specific settings in the pom. --Hardy On 23 Jan 2012, at 6:42 PM, Brett Meyer wrote: > I know a lot of you don't use Eclipse, but... > > Its Maven plugin (M2E) does not have connectors for several of Hibernate > 3.3's lifecycle mappings. The only way to get the IDE to ignore them is to > add the following (as an example). What are your opinions of having > IDE-specific areas, like this, in the parent POM? > > > > <!--This plugin's configuration is used to store Eclipse m2e settings only. > It has no influence on the Maven build itself.--> > <plugin> > <groupId>org.eclipse.m2e</groupId> > <artifactId>lifecycle-mapping</artifactId> > <version>1.0.0</version> > <configuration> > <lifecycleMappingMetadata> > <pluginExecutions> > <pluginExecution> > <pluginExecutionFilter> > <groupId> > > org.jboss.maven.plugins > </groupId> > <artifactId> > > maven-injection-plugin > </artifactId> > <versionRange> > [1.0.2,) > </versionRange> > <goals> > > <goal>bytecode</goal> > </goals> > </pluginExecutionFilter> > <action> > > <ignore></ignore> > </action> > </pluginExecution> > </pluginExecutions> > </lifecycleMappingMetadata> > </configuration> > </plugin> > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
