You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Paul Spencer <pa...@apache.org> on 2007/04/11 23:18:25 UTC
FYI: How to clean the maven repository when testing release candidates
Since it appears their will be a 2nd release canidate for Tomahawk 1.1.5, I thought
the following command to cleanup the local maven repository might be useful.
mvn dependency:purge-local-repository -Dverbose=true -DreResolve=false -DresolutionFuzziness=version
Notes:
reResolve=false - Do not download the artifact in this maven session after deleting it.
resolutionFuzziness=version - Delete all files associated with the artifact's version.
Paul Spencer
PS: Thanks to Manfred for his work on the 1.1.5 release!
Re: FYI: How to clean the maven repository when testing release candidates
Posted by Martin Marinschek <ma...@gmail.com>.
Have you read Manfred's release diary? It seems he had problems with
an unresolved artifact yesterday night...
regards,
Martin
On 4/11/07, Wendy Smoak <ws...@gmail.com> wrote:
> On 4/11/07, Paul Spencer <pa...@apache.org> wrote:
> > Since it appears their will be a 2nd release canidate for Tomahawk 1.1.5, I thought
> > the following command to cleanup the local maven repository might be useful.
> >
> > mvn dependency:purge-local-repository -Dverbose=true -DreResolve=false -DresolutionFuzziness=version
> >
> > Notes:
> > reResolve=false - Do not download the artifact in this maven session after deleting it.
> > resolutionFuzziness=version - Delete all files associated with the artifact's version.
>
> There's another issue... the staging repo seems to have more than one
> thing in it:
>
> http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/
>
> The intent is to stage releases separately so it's easy to move them
> over to the rsynced repo after the vote. Not a huge deal in this case
> since it's everything under the 'tomahawk' directory.
>
> With the current configuration, the procedure should be to move the
> directory after deploying the staged release.
>
> Another option is to change <distributionManagement><repository> to
> include ${version}, so it will land in the right place by default.
> (My preference, Antonio over at Tiles thought it up, but I haven't
> gotten around to changing it here yet.)
>
> --
> Wendy
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: FYI: How to clean the maven repository when testing release candidates
Posted by Wendy Smoak <ws...@gmail.com>.
On 4/11/07, Paul Spencer <pa...@apache.org> wrote:
> Since it appears their will be a 2nd release canidate for Tomahawk 1.1.5, I thought
> the following command to cleanup the local maven repository might be useful.
>
> mvn dependency:purge-local-repository -Dverbose=true -DreResolve=false -DresolutionFuzziness=version
>
> Notes:
> reResolve=false - Do not download the artifact in this maven session after deleting it.
> resolutionFuzziness=version - Delete all files associated with the artifact's version.
There's another issue... the staging repo seems to have more than one
thing in it:
http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/
The intent is to stage releases separately so it's easy to move them
over to the rsynced repo after the vote. Not a huge deal in this case
since it's everything under the 'tomahawk' directory.
With the current configuration, the procedure should be to move the
directory after deploying the staged release.
Another option is to change <distributionManagement><repository> to
include ${version}, so it will land in the right place by default.
(My preference, Antonio over at Tiles thought it up, but I haven't
gotten around to changing it here yet.)
--
Wendy