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 mislead
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 wrote:
> that used to be true with Maven 2, but is not any more since Maven 3 and
> its
> m-site-
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 repo
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 wrote:
> This has been fixed and should work. But properties might still be the
> better approach..
>
> Paul Benedict wrote o
This has been fixed and should work. But properties might still be the better
approach..
Paul Benedict wrote on 03.10.2014 10:46:
> only affects -- it does not affect :
> https://jira.codehaus.org/browse/MNG-3385
>
> Cheers,
> Paul
>
> On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik
> wro
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://bitb
On Thu, Oct 2, 2014 at 5:02 PM, Paul Benedict wrote:
> I use the maven-javadoc-plugin in both and . I don't
> want to fall back to to share the plugin version. Is there a
> better way than using ?
>
No.
Best,
Laird
--
http://about.me/lairdnelson
just learn something new
Thanks!
On 4 October 2014 00:46, Paul Benedict wrote:
> only affects -- it does not affect
> :
> https://jira.codehaus.org/browse/MNG-3385
>
> Cheers,
> Paul
>
> On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik
> wrote:
>
> > we using for this
> >
> > On 3 October 20
only affects -- it does not affect :
https://jira.codehaus.org/browse/MNG-3385
Cheers,
Paul
On Thu, Oct 2, 2014 at 9:06 PM, Maxim Solodovnik
wrote:
> we using for this
>
> On 3 October 2014 07:24, Kathryn Huxtable
> wrote:
>
> > I’ve always used , but would it work to use
> > ? -K
> >
> > O
we using for this
On 3 October 2014 07:24, Kathryn Huxtable
wrote:
> I’ve always used , but would it work to use
> ? -K
>
> On Oct 2, 2014, at 7:02 PM, Paul Benedict wrote:
>
> > I use the maven-javadoc-plugin in both and . I don't
> > want to fall back to to share the plugin version. Is the
I’ve always used , but would it work to use ? -K
On Oct 2, 2014, at 7:02 PM, Paul Benedict wrote:
> I use the maven-javadoc-plugin in both and . I don't
> want to fall back to to share the plugin version. Is there a
> better way than using ?
>
> Cheers,
> Paul
--
I use the maven-javadoc-plugin in both and . I don't
want to fall back to to share the plugin version. Is there a
better way than using ?
Cheers,
Paul
12 matches
Mail list logo
