You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Lynch (JIRA)" <ji...@codehaus.org> on 2009/12/08 21:01:55 UTC
[jira] Created: (MECLIPSE-626) Upgrade Maven dependencies from
2.0.8 to at least 2.0.9 to match minimum version required to build
Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build
--------------------------------------------------------------------------------------------------
Key: MECLIPSE-626
URL: http://jira.codehaus.org/browse/MECLIPSE-626
Project: Maven 2.x Eclipse Plugin
Issue Type: Task
Affects Versions: 2.8
Reporter: Peter Lynch
The pom.xml for this project uses the maven enforcer plugin to require it be built with version 2.0.9 or greater of maven due to requirements of the integration tests.
All the maven dependencies for this project require maven 2.0.8 however.
Things 'work' more or less however consider the following issue.
You want to run integration tests on this plugin and attach a debugger. So when you execute maven, you are forced to use Maven 2.0.9. However the debugger ( example one include with Netbeans or Eclipse) by default will load sources from 2.0.8. This makes stepping through code accurately - impossible - unless you manually run the inegration test and set sources by hand, by passing IDE. As noted in the pom, 2.0.9 is required for some integration tests.
Unless there is some major concern not evident the plugin dependencies marked 2.0.8 should be updated to depend on Maven 2.0.9 or match whatever the minimum required Maven version used to actually build the project.
--
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
[jira] Updated: (MECLIPSE-626) Upgrade Maven dependencies from
2.0.8 to at least 2.0.9 to match minimum version required to build
Posted by "Peter Lynch (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Lynch updated MECLIPSE-626:
---------------------------------
Attachment: MECLIPSE-626.patch
Patch to pom.xml enforcing minimum Maven version of 2.0.9 for dependencies and running the build in all lifecycles.
> Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build
> --------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-626
> URL: http://jira.codehaus.org/browse/MECLIPSE-626
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Task
> Affects Versions: 2.8
> Reporter: Peter Lynch
> Attachments: MECLIPSE-626.patch
>
>
> The pom.xml for this project uses the maven enforcer plugin to require it be built with version 2.0.9 or greater of maven due to requirements of the integration tests.
> All the maven dependencies for this project require maven 2.0.8 however.
> Things 'work' more or less however consider the following issue.
> You want to run integration tests on this plugin and attach a debugger. So when you execute maven, you are forced to use Maven 2.0.9. However the debugger ( example one include with Netbeans or Eclipse) by default will load sources from 2.0.8. This makes stepping through code accurately - impossible - unless you manually run the inegration test and set sources by hand, by passing IDE. As noted in the pom, 2.0.9 is required for some integration tests.
> Unless there is some major concern not evident the plugin dependencies marked 2.0.8 should be updated to depend on Maven 2.0.9 or match whatever the minimum required Maven version used to actually build the project.
--
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
[jira] Issue Comment Edited: (MECLIPSE-626) Upgrade Maven
dependencies from 2.0.8 to at least 2.0.9 to match minimum version required
to build
Posted by "Peter Lynch (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202018#action_202018 ]
Peter Lynch edited comment on MECLIPSE-626 at 12/9/09 10:08 PM:
----------------------------------------------------------------
Summary of the problems, the maven prerequisites are set as follows
{code:xml}
<prerequisites>
<maven>2.0.1</maven>
</prerequisites>
{code}
The dependencies are 2.0.8
{code:xml}
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-project</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-plugin-api</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-model</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-artifact-manager</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-artifact</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-core</artifactId>
<version>2.0.8</version>
</dependency>
{code}
And the enforcer plugin ( not in the run-its profile ) is configured as
{code:xml}
<plugin>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>require-maven-2.0.9</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireMavenVersion>
<!-- The tests check file encoding and class path ordering which depends on fixes in latest Maven -->
<version>[2.0.9,)</version>
</requireMavenVersion>
</rules>
</configuration>
</execution>
</executions>
</plugin>
{code}
was (Author: plynch):
Summary of the problems, the maven prerequisites are set as follows
{code:xml}
<prerequisites>
<maven>2.0.1</maven>
</prerequisites>
{code}
The dependecies are 2.0.8
{code:xml}
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-project</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-plugin-api</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-model</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-artifact-manager</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-artifact</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-core</artifactId>
<version>2.0.8</version>
</dependency>
{code}
And the enforcer plugin ( not in the run-its profile ) is configured as
{code:xml}
<plugin>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>require-maven-2.0.9</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireMavenVersion>
<!-- The tests check file encoding and class path ordering which depends on fixes in latest Maven -->
<version>[2.0.9,)</version>
</requireMavenVersion>
</rules>
</configuration>
</execution>
</executions>
</plugin>
{code}
> Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build
> --------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-626
> URL: http://jira.codehaus.org/browse/MECLIPSE-626
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Task
> Affects Versions: 2.8
> Reporter: Peter Lynch
>
> The pom.xml for this project uses the maven enforcer plugin to require it be built with version 2.0.9 or greater of maven due to requirements of the integration tests.
> All the maven dependencies for this project require maven 2.0.8 however.
> Things 'work' more or less however consider the following issue.
> You want to run integration tests on this plugin and attach a debugger. So when you execute maven, you are forced to use Maven 2.0.9. However the debugger ( example one include with Netbeans or Eclipse) by default will load sources from 2.0.8. This makes stepping through code accurately - impossible - unless you manually run the inegration test and set sources by hand, by passing IDE. As noted in the pom, 2.0.9 is required for some integration tests.
> Unless there is some major concern not evident the plugin dependencies marked 2.0.8 should be updated to depend on Maven 2.0.9 or match whatever the minimum required Maven version used to actually build the project.
--
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
[jira] Commented: (MECLIPSE-626) Upgrade Maven dependencies from
2.0.8 to at least 2.0.9 to match minimum version required to build
Posted by "Peter Lynch (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202018#action_202018 ]
Peter Lynch commented on MECLIPSE-626:
--------------------------------------
Summary of the problems, the maven prerequisites are set as follows
{code:xml}
<prerequisites>
<maven>2.0.1</maven>
</prerequisites>
{code}
The dependecies are 2.0.8
{code:xml}
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-project</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-plugin-api</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-model</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-artifact-manager</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-artifact</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-core</artifactId>
<version>2.0.8</version>
</dependency>
{code}
And the enforcer plugin ( not in the run-its profile ) is configured as
{code:xml}
<plugin>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>require-maven-2.0.9</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireMavenVersion>
<!-- The tests check file encoding and class path ordering which depends on fixes in latest Maven -->
<version>[2.0.9,)</version>
</requireMavenVersion>
</rules>
</configuration>
</execution>
</executions>
</plugin>
{code}
> Upgrade Maven dependencies from 2.0.8 to at least 2.0.9 to match minimum version required to build
> --------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-626
> URL: http://jira.codehaus.org/browse/MECLIPSE-626
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Task
> Affects Versions: 2.8
> Reporter: Peter Lynch
>
> The pom.xml for this project uses the maven enforcer plugin to require it be built with version 2.0.9 or greater of maven due to requirements of the integration tests.
> All the maven dependencies for this project require maven 2.0.8 however.
> Things 'work' more or less however consider the following issue.
> You want to run integration tests on this plugin and attach a debugger. So when you execute maven, you are forced to use Maven 2.0.9. However the debugger ( example one include with Netbeans or Eclipse) by default will load sources from 2.0.8. This makes stepping through code accurately - impossible - unless you manually run the inegration test and set sources by hand, by passing IDE. As noted in the pom, 2.0.9 is required for some integration tests.
> Unless there is some major concern not evident the plugin dependencies marked 2.0.8 should be updated to depend on Maven 2.0.9 or match whatever the minimum required Maven version used to actually build the project.
--
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