The Maven team is pleased to announce the release of the Apache Maven
Reporting Executor, version 1.4
Classes to manage report plugin executions with Maven 3.
https://maven.apache.org/shared/maven-reporting-exec/
You should specify the version in your project's dependency configuration:
Hi,
The vote has passed with the following result:
+1 : Robert Scholte, Arnaud Héritier, Hervé Boutemy
PMC quorum: reached
I will promote the artifacts to the central repo.
Regards,
Hervé
Le vendredi 13 octobre 2017, 02:09:58 CEST Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 3 issues:
>
I think this would modify the overall Maven behaviour and you would therefore
have to implement this as an extension rather than as a plugin. Fyi. we have
such an extension that modifies usage of the local repository already within
Takari.
Use it as inspiration..
>
> This should be possible by providing WorkspaceReader implementation -
> @Component( role = WorkspaceReader.class, hint = "ide" )
>
> Note that Maven tries resolution from workspace *before* repositories -
> workspace reader has priority lower than reactor, but higher than remote
> repos known
On 10/16/2017 06:42 AM, Christoph Laeubrich wrote:
> Hi,
>
> thanks for your reply. I'd like to make artifacts avaiable to maven
> via that are located in a repository with a format that
> maven does not understand.
> Even though if I would have the group+artifactid+version I can locate
> that
