Don't want to repeat plugin version for both build and reporting

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Don't want to repeat plugin version for both build and reporting

Paul Benedict
I use the maven-javadoc-plugin in both <build> and <reporting>. I don't
want to fall back to <properties> to share the plugin version. Is there a
better way than using <properties>?

Cheers,
Paul
Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Kathryn Huxtable
I’ve always used <properties>, but would it work to use <buildDependencies>? -K

On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]> wrote:

> I use the maven-javadoc-plugin in both <build> and <reporting>. I don't
> want to fall back to <properties> to share the plugin version. Is there a
> better way than using <properties>?
>
> Cheers,
> Paul


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Maxim Solodovnik
we using <pluginManagement> for this

On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]>
wrote:

> I’ve always used <properties>, but would it work to use
> <buildDependencies>? -K
>
> On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]> wrote:
>
> > I use the maven-javadoc-plugin in both <build> and <reporting>. I don't
> > want to fall back to <properties> to share the plugin version. Is there a
> > better way than using <properties>?
> >
> > Cheers,
> > Paul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Paul Benedict
<pluginManagement> only affects <plugins> -- it does not affect <reporting>:
https://jira.codehaus.org/browse/MNG-3385

Cheers,
Paul

On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[hidden email]>
wrote:

> we using <pluginManagement> for this
>
> On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]>
> wrote:
>
> > I’ve always used <properties>, but would it work to use
> > <buildDependencies>? -K
> >
> > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]> wrote:
> >
> > > I use the maven-javadoc-plugin in both <build> and <reporting>. I don't
> > > want to fall back to <properties> to share the plugin version. Is
> there a
> > > better way than using <properties>?
> > >
> > > Cheers,
> > > Paul
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> WBR
> Maxim aka solomax
>
Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Maxim Solodovnik
just learn something new
Thanks!

On 4 October 2014 00:46, Paul Benedict <[hidden email]> wrote:

> <pluginManagement> only affects <plugins> -- it does not affect
> <reporting>:
> https://jira.codehaus.org/browse/MNG-3385
>
> Cheers,
> Paul
>
> On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[hidden email]>
> wrote:
>
> > we using <pluginManagement> for this
> >
> > On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]>
> > wrote:
> >
> > > I’ve always used <properties>, but would it work to use
> > > <buildDependencies>? -K
> > >
> > > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]>
> wrote:
> > >
> > > > I use the maven-javadoc-plugin in both <build> and <reporting>. I
> don't
> > > > want to fall back to <properties> to share the plugin version. Is
> > there a
> > > > better way than using <properties>?
> > > >
> > > > Cheers,
> > > > Paul
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>



--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

ljnelson
In reply to this post by Paul Benedict
On Thu, Oct 2, 2014 at 5:02 PM, Paul Benedict <[hidden email]> wrote:

> I use the maven-javadoc-plugin in both <build> and <reporting>. I don't
> want to fall back to <properties> to share the plugin version. Is there a
> better way than using <properties>?
>

No.

Best,
Laird

--
http://about.me/lairdnelson
Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Mirko Friedenhagen-2
Using properties for plugin versions has the additional benefit, that
versions-maven-plugin is able to update plugins as well via
versions:update-properties.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Oct 3, 2014 at 8:01 PM, Laird Nelson <[hidden email]> wrote:

> On Thu, Oct 2, 2014 at 5:02 PM, Paul Benedict <[hidden email]> wrote:
>
>> I use the maven-javadoc-plugin in both <build> and <reporting>. I don't
>> want to fall back to <properties> to share the plugin version. Is there a
>> better way than using <properties>?
>>
>
> No.
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Manfred Moser
In reply to this post by Paul Benedict
This has been fixed and should work. But properties might still be the better approach..

Paul Benedict wrote on 03.10.2014 10:46:

> <pluginManagement> only affects <plugins> -- it does not affect <reporting>:
> https://jira.codehaus.org/browse/MNG-3385
>
> Cheers,
> Paul
>
> On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[hidden email]>
> wrote:
>
>> we using <pluginManagement> for this
>>
>> On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]>
>> wrote:
>>
>> > I’ve always used <properties>, but would it work to use
>> > <buildDependencies>? -K
>> >
>> > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]> wrote:
>> >
>> > > I use the maven-javadoc-plugin in both <build> and <reporting>. I don't
>> > > want to fall back to <properties> to share the plugin version. Is
>> there a
>> > > better way than using <properties>?
>> > >
>> > > Cheers,
>> > > Paul
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>> >
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Dan Tran
I am not able to find any indication of this fix in release notes under 3.x

But I do recall Hervé did some work on it

-D

On Fri, Oct 3, 2014 at 12:01 PM, Manfred Moser <[hidden email]> wrote:

> This has been fixed and should work. But properties might still be the
> better approach..
>
> Paul Benedict wrote on 03.10.2014 10:46:
>
> > <pluginManagement> only affects <plugins> -- it does not affect
> <reporting>:
> > https://jira.codehaus.org/browse/MNG-3385
> >
> > Cheers,
> > Paul
> >
> > On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[hidden email]>
> > wrote:
> >
> >> we using <pluginManagement> for this
> >>
> >> On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]>
> >> wrote:
> >>
> >> > I’ve always used <properties>, but would it work to use
> >> > <buildDependencies>? -K
> >> >
> >> > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]>
> wrote:
> >> >
> >> > > I use the maven-javadoc-plugin in both <build> and <reporting>. I
> don't
> >> > > want to fall back to <properties> to share the plugin version. Is
> >> there a
> >> > > better way than using <properties>?
> >> > >
> >> > > Cheers,
> >> > > Paul
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [hidden email]
> >> > For additional commands, e-mail: [hidden email]
> >> >
> >> >
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Hervé BOUTEMY
In reply to this post by Paul Benedict
that used to be true with Maven 2, but is not any more since Maven 3 and its
m-site-p 3.0 version

Notice that Maven 3.0.x issues a misleading warning about missing version in
reporting section: see MNG-5477

with m-site-p 3.4, even configuration content from pluginManagement is injected
to reporting: see MSITE-516/MSHARED-338 and little note in
http://maven.apache.org/shared/maven-reporting-exec/

Regards,

Hervé

Le vendredi 3 octobre 2014 12:46:21 Paul Benedict a écrit :

> <pluginManagement> only affects <plugins> -- it does not affect <reporting>:
> https://jira.codehaus.org/browse/MNG-3385
>
> Cheers,
> Paul
>
> On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[hidden email]>
>
> wrote:
> > we using <pluginManagement> for this
> >
> > On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]>
> >
> > wrote:
> > > I’ve always used <properties>, but would it work to use
> > > <buildDependencies>? -K
> > >
> > > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]> wrote:
> > > > I use the maven-javadoc-plugin in both <build> and <reporting>. I
> > > > don't
> > > > want to fall back to <properties> to share the plugin version. Is
> >
> > there a
> >
> > > > better way than using <properties>?
> > > >
> > > > Cheers,
> > > > Paul
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> >
> > --
> > WBR
> > Maxim aka solomax


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Paul Benedict
So, shouldn't the misleading warning be fixed? Sounds like something for
3.2.4 -- unless the warning is issued in the site plugin itself.


Cheers,
Paul

On Sat, Oct 4, 2014 at 2:15 AM, Hervé BOUTEMY <[hidden email]> wrote:

> that used to be true with Maven 2, but is not any more since Maven 3 and
> its
> m-site-p 3.0 version
>
> Notice that Maven 3.0.x issues a misleading warning about missing version
> in
> reporting section: see MNG-5477
>
> with m-site-p 3.4, even configuration content from pluginManagement is
> injected
> to reporting: see MSITE-516/MSHARED-338 and little note in
> http://maven.apache.org/shared/maven-reporting-exec/
>
> Regards,
>
> Hervé
>
> Le vendredi 3 octobre 2014 12:46:21 Paul Benedict a écrit :
> > <pluginManagement> only affects <plugins> -- it does not affect
> <reporting>:
> > https://jira.codehaus.org/browse/MNG-3385
> >
> > Cheers,
> > Paul
> >
> > On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[hidden email]>
> >
> > wrote:
> > > we using <pluginManagement> for this
> > >
> > > On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]
> >
> > >
> > > wrote:
> > > > I’ve always used <properties>, but would it work to use
> > > > <buildDependencies>? -K
> > > >
> > > > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]>
> wrote:
> > > > > I use the maven-javadoc-plugin in both <build> and <reporting>. I
> > > > > don't
> > > > > want to fall back to <properties> to share the plugin version. Is
> > >
> > > there a
> > >
> > > > > better way than using <properties>?
> > > > >
> > > > > Cheers,
> > > > > Paul
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Don't want to repeat plugin version for both build and reporting

Hervé BOUTEMY
AFAIK, it was fixed in Maven 3.1.0-alpha-1
I just tested and couldn't get any warning with Maven 3.2.3, where I get it
with Maven 3.0.5

what warning are you seeing?
can you share a test project?

Regards,

Hervé

Le lundi 6 octobre 2014 09:16:31 Paul Benedict a écrit :

> So, shouldn't the misleading warning be fixed? Sounds like something for
> 3.2.4 -- unless the warning is issued in the site plugin itself.
>
>
> Cheers,
> Paul
>
> On Sat, Oct 4, 2014 at 2:15 AM, Hervé BOUTEMY <[hidden email]> wrote:
> > that used to be true with Maven 2, but is not any more since Maven 3 and
> > its
> > m-site-p 3.0 version
> >
> > Notice that Maven 3.0.x issues a misleading warning about missing version
> > in
> > reporting section: see MNG-5477
> >
> > with m-site-p 3.4, even configuration content from pluginManagement is
> > injected
> > to reporting: see MSITE-516/MSHARED-338 and little note in
> > http://maven.apache.org/shared/maven-reporting-exec/
> >
> > Regards,
> >
> > Hervé
> >
> > Le vendredi 3 octobre 2014 12:46:21 Paul Benedict a écrit :
> > > <pluginManagement> only affects <plugins> -- it does not affect
> >
> > <reporting>:
> > > https://jira.codehaus.org/browse/MNG-3385
> > >
> > > Cheers,
> > > Paul
> > >
> > > On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik <[hidden email]>
> > >
> > > wrote:
> > > > we using <pluginManagement> for this
> > > >
> > > > On 3 October 2014 07:24, Kathryn Huxtable <[hidden email]
> > > >
> > > > wrote:
> > > > > I’ve always used <properties>, but would it work to use
> > > > > <buildDependencies>? -K
> > > > >
> > > > > On Oct 2, 2014, at 7:02 PM, Paul Benedict <[hidden email]>
> >
> > wrote:
> > > > > > I use the maven-javadoc-plugin in both <build> and <reporting>. I
> > > > > > don't
> > > > > > want to fall back to <properties> to share the plugin version. Is
> > > >
> > > > there a
> > > >
> > > > > > better way than using <properties>?
> > > > > >
> > > > > > Cheers,
> > > > > > Paul
> > > > >
> > > > > --------------------------------------------------------------------
> > > > > -
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]