[ANN] Release Maven Help Plugin 3.0.0 released

2018-03-17 Thread Michael Osipov 
The Apache Maven team is pleased to announce the release of the Maven 
Help Plugin version 3.0.0.


This module generates browsable HTML pages from Java source code.

https://maven.apache.org/plugins/maven-help-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-help-plugin
  3.0.0



Release Notes - Maven Help Plugin - Version 3.0.0

** Bug
* [MPH-53] - mvn help:describe returns the version that is 
specified in metadata instead of  the one in the parent pom
* [MPH-87] - help:effective-pom/effective-settings uses platform 
encoding and garbles non-ASCII characters, emits invalid XML
* [MPH-97] - [Patch] maven-help-plugin does not build with latest 
version of maven-plugin-testing-harness

* [MPH-99] - Evaluate has no output in quiet mode
* [MPH-105] - Effective pom aggregation is not triggered
* [MPH-107] - Mojos use inconsistent line endings throughout
* [MPH-108] - Patch for MPH-72 not fully applied
* [MPH-110] - Cannot run ITs successfully
* [MPH-111] - IT 'effective-pom_properties' fails if run with 
-Dinvoker.mergeUserSettings

* [MPH-114] - Goal fails with “Unable to get the POM for the artifact”
* [MPH-119] - The "artifact" parameter is not taken into account 
with Maven 3

* [MPH-121] - incorrect text in help:describe for cmd
* [MPH-123] - all-profiles does not show right active status

** Improvement
* [MPH-106] - add gav parameter to calculate effective pom for any 
gav, not only reactor

* [MPH-109] - Use ISO 8601 date format for the remaining goals
* [MPH-116] - Printout the information if a goal is a report goal 
or not

* [MPH-120] - Migrate plugin to Maven 3.0
* [MPH-124] - Show parameter aliases in describe goal

** Task
* [MPH-103] - Remove unused dependency maven-monitor
* [MPH-112] - Upgrade to Commons Lang3
* [MPH-126] - Require Java 7
* [MPH-132] - Drop parameter 'medium'
* [MPH-133] - Drop deprecated alias 'full'
* [MPH-134] - Drop deprecated alias 'mojo'

** Dependency upgrade
* [MPH-102] - Upgrade to maven-plugins parent version 27
* [MPH-104] - Upgrade maven-plugin-testing-harness to 1.3
* [MPH-117] - Upgrade plexus-utils to 3.0.22
* [MPH-118] - Upgrade maven-plugins to version 30
* [MPH-125] - Upgrade parent to 31
* [MPH-127] - Upgrade Maven  Artifact Transfer to 0.9.1
* [MPH-128] - Upgrade Maven Reporting Exec to 1.4
* [MPH-129] - Upgrade Plexus Utils to 3.1.0
* [MPH-130] - Upgrade XStream to 1.4.7
* [MPH-131] - Ugprade Commons Lang to 3.7


Enjoy,

-The Apache Maven team


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to tell maven where to look for extensions (instead of central repository)

2018-03-17 Thread Anders Hammar 
You need to provide more info to understand your questions.
"obviously everything else fails"? why obviously?
"why are plugin repositories being ignored? they shouldn't for plugins and
their deps. If it is it's most likely due to a misconfiguration on your
end, but it could be a bug in maven.

/Anders

On Fri, Mar 16, 2018 at 8:21 AM, Salvatore  wrote:

> That is a bigger change than I expected...
> I've configured a * pointing to my repo to test it
> out, and now the extension is being downloaded, but obviously everything
> else fails. I cannot modify nexus configuration myself, so it seems I will
> have to download the jar manually for now :(
>
> Can I ask why is this needed? Why are plugin repositories being ignored? Is
> it bad to have multiple repositories configured or is this a bug?
>
> Thank you Karl.
> Regards,
> Salva
>
> 2018-03-15 20:35 GMT+01:00 Karl Heinz Marbaise :
>
> > Hi,
> >
> > On 15/03/18 20:12, Salvatore wrote:
> >
> >> Hello,
> >> I have tried with maven 3.3.9 and 3.5.0. I will try with 3.5.3 tomorrow
> >> too.
> >> The repos are configured via settings.xml. I have them both as
> >>  and as . If the docs are right, the
> plugin
> >> repositories should be the important ones for extensions but all I see
> when
> >> I run any goal on that project, with debug enabled, is:
> >>
> >> [WARNING] Failed to read extensions descriptor
> >> /home/my-user/git/my-project/.mvn/extensions.xml: Plugin
> >> com.our-company:kompile-maven-extension:1.0 or one of its dependencies
> >> could not be resolved: Could not find artifact
> >> com.our-company:kompile-maven-extension:jar:1.0 in central (
> >> https://repo.maven.apache.org/maven2)
> >>
> >> There is no line showing that maven tried to download the extension from
> >> any other repo. Thats the only one that is checking out apparently.
> That's
> >> why I thought that maybe extensions are not ready to be downloaded from
> >> custom repos yet...
> >>
> >> I have posted this question in StackOverflow too:
> >> https://stackoverflow.com/questions/49284462/failed-to-read-
> >> extensions-descriptor-could-not-find-artifact-in-central
> >>
> >> Maybe our Sonatype is outdated and we have to updated it to support
> >> extensions? I have to admit I don't know what version are we using, but
> I
> >> can check that out if it makes sense.
> >>
> >
> > It looks like you have configured many repositories in your settings.xml
> > instead of having a single group[1] and the configuration put to the
> > repository manager like Nexus...
> >
> > Furthermore have you checked that the extension you are trying to get is
> > really under the given coordinates and the same version available ?
> >
> >
> > Kind regards
> > Karl Heinz Marbaise
> > [1]: https://books.sonatype.com/nexus-book/2.8/reference/maven-
> > sect-single-group.html
> >
> >
> >> Thank you Karl, I appreciate your help.
> >>
> >> 2018-03-15 19:54 GMT+01:00 Karl Heinz Marbaise  >> >:
> >>
> >> Hi,
> >>
> >> On 15/03/18 11:51, Salvatore wrote:
> >>
> >> Hello, first time here. I have a quick question:
> >> Is it possible to use a maven extension that is not in maven
> >> central
> >> without downloading the jar manually? nor doing a mvn install
> >> locally?
> >>
> >> Cause I have been trying to find out why is my extension not
> being
> >> downloaded by maven from my own repository, but maybe the
> >> problem is that
> >> this is not possible!
> >>
> >> And that's pretty much it. If it is indeed possible then I will
> >> have to ask
> >> a new question, cause maven doesn't seem to care about my repos
> >> at all haha.
> >>
> >>
> >> First question related to that. Which Maven version do you use?
> >> How have you configured your own repositories? Via settings.xml or
> >> via repository manager ?
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >>
> >>
>

Question about using a custom StackTraceWriter with the maven-surefire-plugin

2018-03-17 Thread Zoltan Farkas 
Is it possible to register a custom writer with the maven-surefire-plugin?

let me know.

thank you.

—Z
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to tell maven where to look for extensions (instead of central repository)

2018-03-17 Thread Salvatore 
That is a bigger change than I expected...
I've configured a * pointing to my repo to test it
out, and now the extension is being downloaded, but obviously everything
else fails. I cannot modify nexus configuration myself, so it seems I will
have to download the jar manually for now :(

Can I ask why is this needed? Why are plugin repositories being ignored? Is
it bad to have multiple repositories configured or is this a bug?

Thank you Karl.
Regards,
Salva

2018-03-15 20:35 GMT+01:00 Karl Heinz Marbaise :

> Hi,
>
> On 15/03/18 20:12, Salvatore wrote:
>
>> Hello,
>> I have tried with maven 3.3.9 and 3.5.0. I will try with 3.5.3 tomorrow
>> too.
>> The repos are configured via settings.xml. I have them both as
>>  and as . If the docs are right, the plugin
>> repositories should be the important ones for extensions but all I see when
>> I run any goal on that project, with debug enabled, is:
>>
>> [WARNING] Failed to read extensions descriptor
>> /home/my-user/git/my-project/.mvn/extensions.xml: Plugin
>> com.our-company:kompile-maven-extension:1.0 or one of its dependencies
>> could not be resolved: Could not find artifact
>> com.our-company:kompile-maven-extension:jar:1.0 in central (
>> https://repo.maven.apache.org/maven2)
>>
>> There is no line showing that maven tried to download the extension from
>> any other repo. Thats the only one that is checking out apparently. That's
>> why I thought that maybe extensions are not ready to be downloaded from
>> custom repos yet...
>>
>> I have posted this question in StackOverflow too:
>> https://stackoverflow.com/questions/49284462/failed-to-read-
>> extensions-descriptor-could-not-find-artifact-in-central
>>
>> Maybe our Sonatype is outdated and we have to updated it to support
>> extensions? I have to admit I don't know what version are we using, but I
>> can check that out if it makes sense.
>>
>
> It looks like you have configured many repositories in your settings.xml
> instead of having a single group[1] and the configuration put to the
> repository manager like Nexus...
>
> Furthermore have you checked that the extension you are trying to get is
> really under the given coordinates and the same version available ?
>
>
> Kind regards
> Karl Heinz Marbaise
> [1]: https://books.sonatype.com/nexus-book/2.8/reference/maven-
> sect-single-group.html
>
>
>> Thank you Karl, I appreciate your help.
>>
>> 2018-03-15 19:54 GMT+01:00 Karl Heinz Marbaise > >:
>>
>> Hi,
>>
>> On 15/03/18 11:51, Salvatore wrote:
>>
>> Hello, first time here. I have a quick question:
>> Is it possible to use a maven extension that is not in maven
>> central
>> without downloading the jar manually? nor doing a mvn install
>> locally?
>>
>> Cause I have been trying to find out why is my extension not being
>> downloaded by maven from my own repository, but maybe the
>> problem is that
>> this is not possible!
>>
>> And that's pretty much it. If it is indeed possible then I will
>> have to ask
>> a new question, cause maven doesn't seem to care about my repos
>> at all haha.
>>
>>
>> First question related to that. Which Maven version do you use?
>> How have you configured your own repositories? Via settings.xml or
>> via repository manager ?
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>>
>>