Hi Mirko,
>
Both the Maven 3[0] and Maven 2[1] build fail because two of the
components (maven-shared-utils, maven-jar-signer) are currently voted
on, so are not available in Central.
1) I see there is a staging-group at
https://repository.apache.org/content/repositories/maven-staging-group/
Should this group maybe be included in settings or a profile so stuff
in a vote may already be used?
the first is caused by the missing artifact
[0] https://builds.apache.org/job/maven-plugins-ITs-m3.0.4/512/console
cause maven-shared-utils 0.6 is not in Maven Central cause currently the
vote is running ....
which you already mentoined....
During the vote we use separate staging repositories to make it possible
to separately configure your repository manager (within the company or
where ever you are which means creating a separate proxy repository
which points to that staging repository) and use this artifact if you
like it for testing ...without any influence on your internal proxied
central repo etc. (I'm a local nexus on my Mac book to do such testing
which helped very often)...
Afterwards the vote will be done you can remove that special
configuration from your Repo manager and just get the artifact via
Central...or if the vote would have resulted in a fail you can simple
remove that special repo from your repository configuration you will are
fine and have clean state of your repositories.
Furthermore this will make sure having only the new artifacts in this
staging repository and your new plugin/artifact version works correctly
with other artifacts from central and does not use artifacts which might
have not released yet...(from the point of view of maven plugin tester)...
Or in other words i don't like to add a profile etc. to add the
maven-staging-group into the builds nor i would suggest to change the
configuration into this directions...because this would lead into
problem in my opinion...
2) Maven2 is (finally :-)) deprecated, why run a Jenkins build for this :-).
Maven 2 is dead based on the thing that no one will create a new Maven
2.2.X version but we know many people using Maven 2.2.1 out in the wild
so at moment it might be a good idea to have those tests and see if it's
working or not. As a result of such things it might be decided not to
keep Maven 2 compatibility but than this is a conscious decision which
means plugin developer etc. are aware of the result and of course can
document that in the release notes or can make things clear by using a
different version like a major version update ....
But at this point we need to separate runtime from build time...
Kind regards
Karl-Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
