[ http://jira.codehaus.org/browse/MDEPLOY-19?page=comments#action_59380 ] 

Jerome Lacoste commented on MDEPLOY-19:
---------------------------------------

To Brett: "I've had problems with your method of patches before Jerome - can 
you use "svn diff" instead of taking copies of the files and using diff? We 
need to know what the source revision was."

The reason I don't use svn diff directly is I often have several patches 
waiting on the same project. For example I submitted that one in a serie of 3 
patches. I cannot then use svn diff to create my patch. I would have to create 
each patch independently of the other and 1- it is often not possible, 2- that 
means I would have to update my patch when a precedent one is checked in. So 
svn diff is not an option in some cases given the way I work (in batch).

So I use 'quilt' to handle the patches. It is supposed to work. I've used it 
successfully on all the other projects I am working on. But I sometimes make a 
mistake, and that render the patch not usable. I will improve my discipline and 
make sure that I better test apply my patch stack before submission. Maybe 
should I only submit them as a group (that's what is done in other projects)?

Sorry if that caused you some issues but I think that this is still the correct 
way to go for me.

> Ability to deploy-file as classifier
> ------------------------------------
>
>          Key: MDEPLOY-19
>          URL: http://jira.codehaus.org/browse/MDEPLOY-19
>      Project: Maven 2.x Deploy Plugin
>         Type: New Feature

>     Versions: 2.1
>  Environment: xp
>     Reporter: Dan Tran
>     Assignee: Allan Ramirez
>  Attachments: MDEPLOY19.diff
>
>   Time Spent: 2 hours
>    Remaining: 0 minutes
>
> deploy-file currently does not support this option

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to