[ http://jira.codehaus.org/browse/MRM-4?page=comments#action_40874 ]
Trygve Laugstol commented on MRM-4:
---
John: Is is possible to have a process that scans for changed/new artifacts
only and processes them? Is so, is this process any less disk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it already does so, based on the artifact itself's lastMod time...this
is why the POM check is getting messed up...the artifact has changed, so
repoclean processes it without any regard for what's already there WRT
the POM...
That's what we need to
This doesn't need to be complicated, do timestamp checks, or anything -
it is just when there is no pom at the source, don't create a fake one
at the dest, if it already exists. If there is one at the source, its
fine to do a conversion.
- Brett
John Casey wrote:
it already does so, based
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...which was exactly my point. I'll implement this later today, when I
get the profiles ITs done.
Brett Porter wrote:
This doesn't need to be complicated, do timestamp checks, or anything -
it is just when there is no pom at the source, don't
[ http://jira.codehaus.org/browse/MRM-4?page=comments#action_40823 ]
John Casey commented on MRM-4:
--
shouldn't we opt to publish to the m1 repo and let the converter push it across
instead of putting in this check? We talked about this at one time on
