Re: [hibernate-dev] Eclipse-specific execution filters in POMs
Sorry -- to clarify, this is only for Hibernate 3.3 within EAP 5 (Maven based).
----- Original Message -----
From: "Max Rydahl Andersen" <max.andersen(a)redhat.com>
To: "Brett Meyer" <brmeyer(a)redhat.com>
Cc: hibernate-dev(a)lists.jboss.org
Sent: Thursday, August 23, 2012 11:40:28 PM
Subject: Re: [hibernate-dev] Eclipse-specific execution filters in POMs
hibernate doesn't use maven build anymore, so don't think this applies anymore?
about m2e - upcoming version of m2e will allow storing these things *externally* to the
pom.xml making this problem go away.
/max
On 23 Aug 2012, at 18:42, Brett Meyer <brmeyer(a)redhat.com> 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev