[jira] Created: (MECLIPSE-704) Request to merge when 'filtering' is not identical

[Paul Mackinlay (JIRA)]

Request to merge when 'filtering' is not identical
--

 Key: MECLIPSE-704
 URL: https://jira.codehaus.org/browse/MECLIPSE-704
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Bug
Affects Versions: 2.8, 2.7
Reporter: Paul Mackinlay
 Attachments: parent_pom.txt

mvn eclipse:eclipse fails with a "Request to merge when 'filtering' is not 
identical" message. There is a discussion about this on the internet and the 
accepted workaround is to user eclipse plugin 2.6 (see 
http://forums.atlassian.com/thread.jspa?threadID=34952)

In my case it is happening with non standard maven directory structure. The 
parent pom has the config in the attached parent_pom.txt file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (SCM-615) RemoveMojo to allow removing resources from version control

[Paul Mackinlay (JIRA)]

RemoveMojo to allow removing resources from version control
---

 Key: SCM-615
 URL: http://jira.codehaus.org/browse/SCM-615
 Project: Maven SCM
  Issue Type: Improvement
  Components: maven-plugin
Affects Versions: 1.5
Reporter: Paul Mackinlay
 Attachments: remove_mojo_patch.txt

A patch file is included.

Running the junit test shows that although the remove command fails, it is not 
propagated to the mojo class.

It is suggested that PerforceRemoveCommand.executeRemoveCommand() is changed to 
rethrow CommandLineException as a ScmException.

-- 
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: (MDEP-272) purge-local-repository does nothing if certain dependencies are included

[Paul Mackinlay (JIRA)]

[ 
http://jira.codehaus.org/browse/MDEP-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256172#action_256172
 ] 

Paul Mackinlay commented on MDEP-272:
-

This does not look like it is specific to jasperreports.jar, I have other 
dependencies and am experiencing the same issue.

> purge-local-repository does nothing if certain dependencies are included
> 
>
> Key: MDEP-272
> URL: http://jira.codehaus.org/browse/MDEP-272
> Project: Maven 2.x Dependency Plugin
>  Issue Type: Bug
>  Components: purge-local-repository
>Affects Versions: 2.0
>Reporter: Michele Lorenzini
>Assignee: Brian Fox
> Attachments: pom.xml
>
>
> I've noticed that the {{purge-local-repository}} goal does nothing if certain 
> dependencies are present in the dependency tree of the project.
> After some attempts I've found some of the dependencies that can show problem.
> See attached {{pom.xml}}: if I run {{mvn validate}} as is, maven purges the 
> local repository and the log4j jar is downloaded from the remote repository.
> Removing the comment around the jasperreports dependency and re-running {{mvn 
> validate}} gives the following result:
> {code}
> [INFO] [dependency:purge-local-repository {execution: default}]
> [INFO] Nothing to do for project: test-issue:test-issue:pom:1.0.0.0-SNAPSHOT
> {code}
> So it seems that something goes wrong while resolving the dependencies for 
> the project if the jasperreports jar is included, resulting in the 
> {{purge-local-repository}} to skip the clean of the local repository.
> I dont know if this happens only with jasperreports dependency or if it is 
> something more general.

-- 
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