11:42 a.m.
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>
10:40 p.m.
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
8:07 a.m.
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
12:44 p.m.
+1 to add them, as I believe they make no difference for non-eclipse users
but are handy for those who use it.
On 24 Aug 2012 15:07, "Brett Meyer" <brmeyer(a)redhat.com> wrote:
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
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
5:14 a.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
4503
days inactive
4505
days old
4 comments
4 participants
participants (4)
-
Brett Meyer -
Hardy Ferentschik -
Max Rydahl Andersen -
Sanne Grinovero