The gitexe has already the full maven-sm-test TCK suite implemented. So all the
things like a prepackaged git repo for the TCK is already there.
LieGrue,
strub
--- Brian Fox schrieb am Sa, 25.4.2009:
> Von: Brian Fox
> Betreff: Re: Using GIT as the canonical repository for Maven 3.x
> An: "
If you like me to help then simply ping me, I'd be honoured to help.
I didn't dive into the testing structure in place there, but if it
doesn't exist already, some external ITs would be awesome. Something we
could run against the multiple implementations to guarantee compatibility.
---
> Mark, it looks like the git provider is
> already setup to
> easily integrate an alternate implementation
Yes, when I wrote the maven-scm-providers-git I basically copied over the svn
provider, exactly because it had the structure to support multiple
implementations (thats btw the reason why
I'm talking with the jgit guys to see about adapting the git archive
functionality to implement an effective export that we can use from the
release plugin. Mark, it looks like the git provider is already setup to
easily integrate an alternate implementation so I think this won't be
hard once t
will that not remove the release.properties file too?
2009/4/25 Antony Stubbs
>
> not true!
>
> git reset --hard
> git clean -f
> git checkout tag
>
> will ensure an exact match with the tag/branch.
>
>
> struberg wrote:
> >
> >
> >> Do we really need to do a clean checkout from the tag?
> >
> >
Hi Antony!
I thought about this too, but imho you also have to provide the -x option to
git clean to make sure that there is no temporary product left. But this will
also clean your .project, *.iml etc, which is not a good deal usually :)
So you can either clean _all_ files or you also have al
