[
http://jira.codehaus.org/browse/MDEP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252477#action_252477
]
Phillip Hellewell commented on MDEP-225:
----------------------------------------
This bug is so annoying, and the fix is so incredibly simple and totally makes
sense. How can it not be applied yet? Hasn't Ruediger Dreier done enough?
Are you just waiting for integration tests or what, because I can help do that
if you will help me understand how.
I can reproduce this bug easily in both Windows and Linux. Just follow these
steps and you'll see.
1. Set up two projects: B depends on A and uses unpack-dependencies.
2. Install a snapshot of project A.
3. Run mvn process-sources in project B. It will unpack A and create a new
marker.
4. Install a snapshot of project A (same version).
5. Run mvn process-sources in project B. It will unpack the new A, but the
marker timestamp is not updated!
6. Repeat step 5 forever; it will always unpack A and never update the marker
timestamp!
I find myself touching the marker file manually every time after an unpack.
That is a royal pain.
So tell me again why you can't apply a 4-line patch that totally makes sense?
When createNewFile fails (because it already exists), the timestamp doesn't get
updated, so simply update it.
(Granted, the marker timestamps ought to be set to the timestamp of the
artifact that got unpacked, not the current time, but that is a different
bug/feature).
> Dependency plugin seems to unpack archive even, if it is already unpacked
> -------------------------------------------------------------------------
>
> Key: MDEP-225
> URL: http://jira.codehaus.org/browse/MDEP-225
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.1
> Reporter: Jason Chaffee
> Assignee: Brian Fox
> Attachments: MDEP-225.patch, MDEP-225.patch
>
>
> The plugin used to be smart about not unpacking archives if it found the
> archive was already unpacked (maybe I was doing something different than..not
> sure). However, now it unpacks the archive every time, no matter what I try
> to keep it from doing it, including using overwriteIfNewer.
> I would like to be able to run the build once to extract the archive, then
> not have it extracted again, unless I clean the target directory because the
> archive takes several minutes to unpack.
> Here are the steps.
> 1) configure unpack in pom
> 2) run mvn clean install --> expect unpacking
> 3) run mvn install --> do not expect unpacking as it is still unpaced from
> step (2)
--
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
