Hi Mark,
yes, I meant SCM-698. It's really weird what happened, because I would
expect tests to fail if there's no components.xml. It happened to me only
once, during the most critical moment: release:perform. Just double check
your release, that's all I'm saying.
Robert
Op Tue, 30 Oct 2012 23:50:39 +0100 schreef Mark Hobson
<[email protected]>:
Hi Robert,
Is this in reference to SCM-698 which switched from
plexus-maven-plugin to plexus-component-metadata? The latter plugin
still correctly generates the plexus components.xml files for
maven-scm. Perhaps the maven-invoker problem is specific to plexus
annotations which I don't believe we're using yet.
Thanks,
Mark
On 30 October 2012 22:11, Robert Scholte <[email protected]> wrote:
Mark,
FYI, it seems like there's an issue with the plexus-component-metadata.
My latest release is of the maven-invoker is missing the
plexus/components.xml so I'll have to re-release a new one as soon as I
know
what the issue is.
Running a package twice does generate the file.
I assume it's this project:
https://github.com/sonatype/plexus-containers
but I still haven't found the right sources on my system
Robert
Op Tue, 30 Oct 2012 22:41:21 +0100 schreef Mark Hobson
<[email protected]>:
Sounds reasonable to me, I'll release it as 1.8.1.
Mark
On 27 October 2012 23:28, Chris Graham <[email protected]> wrote:
1.9 or 1.8.1?
It doesn't appear to be a major change.
-Chris
Sent from my iPhone
On 27/10/2012, at 11:31 PM, Mark Hobson <[email protected]> wrote:
On 26 October 2012 21:14, Olivier Lamy <[email protected]> wrote:
2012/10/26 Mark Hobson <[email protected]>:
Any objections before I start a vote?
Nope
Great, I'll get the ball rolling.
Also, what is the convention for running maven-scm ITs? I'm
guessing
it's done manually prior to releasing. Does it require all the SCM
tools to be installed locally or can we just trust CI?
Some are not available for free.
Perso I usually run tck for git,svn and cvs
(-Ptck-git,tck-svn,tck-cvs)
Thanks to care of this release !
Sounds good, no probs!
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
