Re: Maven 3.5.0 and the versions plugin

2017-04-13 Thread Karl Heinz Marbaise 

Hi Mark,

for the versions-maven-plugin there is already an issue for that:

https://github.com/mojohaus/versions-maven-plugin/issues/56

Currently I'm working on a large number of the issues in the 
versions-maven-plugin ...


https://github.com/mojohaus/versions-maven-plugin/milestone/2?closed=1


It will take some time...

Kind regards
Karl Heinz Marbaise

On 13/04/17 23:00, Mark Eggers wrote:

Folks,

I'm working on upgrading an environment to maven 3.5.0. With
prerequisites in pom.xml, I get the expected message:

   [WARNING] The project org.mdeggers:CSEquity:war:1.0-SNAPSHOT
   uses prerequisites which is only intended for maven-plugin projects
   but not for non maven-plugin projects. For such purposes you should
   use the maven-enforcer-plugin. See
   https://maven.apache.org/enforcer/enforcer-
   rules/requireMavenVersion.html

I then remove the prerequisites tag and replace it with the
appropriately configured enforcer plugin. The project builds cleanly.

However, one of the things that we do in Jenkins is run a series of mvn
versions:display--updates (plugins, dependencies) and mail the
results to developers.

When I run mvn versions:display-plugin-updates, I get the expected
output as well as the following:

   [WARNING] Project does not define minimum Maven version, default is:
   2.0

   [ERROR] Project does not define required minimum version of Maven.
   [ERROR] Update the pom.xml to contain
   [ERROR] 
   [ERROR]   3.0
   [ERROR] 

Is there a way to resolve this? Should I file an issue with the maven
versions plugin?

. . . just my two cents
/mde/




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

Re: Maven 3.5.0 and the versions plugin

2017-04-13 Thread Manfred Moser 
Yeah. Provided you have tested this with the latest version of the versions 
plugin and it still shows that problem... 

Mark Eggers wrote on 2017-04-13 14:00:

> Folks,
> 
> I'm working on upgrading an environment to maven 3.5.0. With
> prerequisites in pom.xml, I get the expected message:
> 
>   [WARNING] The project org.mdeggers:CSEquity:war:1.0-SNAPSHOT
>   uses prerequisites which is only intended for maven-plugin projects
>   but not for non maven-plugin projects. For such purposes you should
>   use the maven-enforcer-plugin. See
>   https://maven.apache.org/enforcer/enforcer-
>   rules/requireMavenVersion.html
> 
> I then remove the prerequisites tag and replace it with the
> appropriately configured enforcer plugin. The project builds cleanly.
> 
> However, one of the things that we do in Jenkins is run a series of mvn
> versions:display--updates (plugins, dependencies) and mail the
> results to developers.
> 
> When I run mvn versions:display-plugin-updates, I get the expected
> output as well as the following:
> 
>   [WARNING] Project does not define minimum Maven version, default is:
>   2.0
> 
>   [ERROR] Project does not define required minimum version of Maven.
>   [ERROR] Update the pom.xml to contain
>   [ERROR] 
>   [ERROR]   3.0
>   [ERROR] 
> 
> Is there a way to resolve this? Should I file an issue with the maven
> versions plugin?
> 
> . . . just my two cents
> /mde/
> 
> 


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

Maven 3.5.0 and the versions plugin

2017-04-13 Thread Mark Eggers 
Folks,

I'm working on upgrading an environment to maven 3.5.0. With
prerequisites in pom.xml, I get the expected message:

   [WARNING] The project org.mdeggers:CSEquity:war:1.0-SNAPSHOT
   uses prerequisites which is only intended for maven-plugin projects
   but not for non maven-plugin projects. For such purposes you should
   use the maven-enforcer-plugin. See
   https://maven.apache.org/enforcer/enforcer-
   rules/requireMavenVersion.html

I then remove the prerequisites tag and replace it with the
appropriately configured enforcer plugin. The project builds cleanly.

However, one of the things that we do in Jenkins is run a series of mvn
versions:display--updates (plugins, dependencies) and mail the
results to developers.

When I run mvn versions:display-plugin-updates, I get the expected
output as well as the following:

   [WARNING] Project does not define minimum Maven version, default is:
   2.0

   [ERROR] Project does not define required minimum version of Maven.
   [ERROR] Update the pom.xml to contain
   [ERROR] 
   [ERROR]   3.0
   [ERROR] 

Is there a way to resolve this? Should I file an issue with the maven
versions plugin?

. . . just my two cents
/mde/



signature.asc
Description: OpenPGP digital signature

Please officially support RELEASE and LATEST (was: Re: dependency question)

2017-04-13 Thread Curtis Rueden 
Hi Maven developers,

I would like to argue for the inclusion / restoration / continued support
of the RELEASE and LATEST tags.

Reasons:

1) There are many valid use cases for them. For example, my script jrun [1]
uses RELEASE right now to make it easier to launch a Maven GAV. Launching
e.g. the Jython REPL is as easy as "jrun org.python:jython-standalone" from
the CLI. But this relies on RELEASE working. I know that Maven is
traditionally viewed as primarily a build-time tool, but it is also
extremely useful for synthesizing runtime environments, and IMHO
underutilized in this regard.

2) For LATEST, you can achieve basically the same behavior using a version
range like [0,). There is no other way (that I know of) to achieve what the
RELEASE tag does.

3) The argument that they harm reproducibility is totally valid. But so do
SNAPSHOTs, and so do version ranges. And those have not been deprecated. So
why are RELEASE and LATEST eschewed so heavily?

Orthogonally: I think it would be awesome to warn about irreproducible
builds, be they from SNAPSHOTs, version ranges, or these special keywords.
People need to know when their builds are vulnerable. But there should
probably also be a property to disable this warning, for the cases when the
developer intentionally wants/needs to use them, and knows what they are
doing. If the issue is just that no ones has time to work on e.g. MNG-6206,
I could try to make some time for it—I feel strongly enough about this
issue.

Thanks for any insight, workarounds, counterarguments, agreement.
(Especially if you agree: please speak up, so the core Maven devs know I'm
not just an outlier here!)

Regards,
Curtis

[1] https://github.com/ctrueden/jrun

--
Curtis Rueden
LOCI software architect - https://loci.wisc.edu/software
ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden


On Tue, Apr 11, 2017 at 4:56 PM, Karl Heinz Marbaise 
wrote:

> Hi,
>
>
> On 11/04/17 23:38, Stephen Connolly wrote:
>
>> On Tue 11 Apr 2017 at 20:55, Curtis Rueden  wrote:
>>
>> Hi Stephen,
>>>
>>> There is a special version keyword LATEST which means the very newest
> version, snapshot or otherwise. And RELEASE means the newest release
> (non-SNAPSHOT) version.
>

 Support for those were dropped in Maven 3

>>>
>>> By "support" do you mean "social support" as opposed to technical
>>> functionality?
>>>
>>
>>
>> They were supposed to be removed.
>>
>> If they are working now, that's a bug
>>
>
> Unfortunately they are working ;-(..
>
> https://issues.apache.org/jira/browse/MNG-6206
>
>
> Kind regards
> Karl Heinz Marbaise
>
>
>>
>>
>>> Because they are still present in the codebase, and they still work
>>> technically:
>>>https://github.com/apache/maven/blob/master/maven-
>>> resolver-provider/src/main/java/org/apache/maven/repository/internal/
>>> DefaultVersionResolver.java#L188-L197
>>>
>>> Regards,
>>> Curtis
>>>
>>> --
>>> Curtis Rueden
>>> LOCI software architect - https://loci.wisc.edu/software
>>> ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden
>>>
>>>
>>> On Tue, Apr 11, 2017 at 2:44 PM, Stephen Connolly <
>>> stephen.alan.conno...@gmail.com> wrote:
>>>
>>> On Tue 11 Apr 2017 at 16:02, Curtis Rueden  wrote:

 Hi Hector,
>
> This is fine as long as the dependency is always set to
>>
> x.y.z-Snapshot
>>>
 and the dependency is always overwritten this way.  What if the
>> producer produces x.y.z.1-Snapshot, x.y.z.2-Snapshot,
>>
> x.y.z.3-Snapshot
>>>
 and I want the dependent build to always get the latest in this case,
>> x.y.z.3-Snapshot ?
>>
>
> There is a special version keyword LATEST which means the very newest
> version, snapshot or otherwise. And RELEASE means the newest release
> (non-SNAPSHOT) version.
>


 Support for those were dropped in Maven 3

 *and* anyway they were only for *plugin* versions because the plugin
 version does not support ranges.

 For dependency versions, define a range


>
> Similar to version ranges, Maven will have to ask the remote repository
> about the latest known version in these cases, and will then use that.
>
> I want to emphasize, as others have mentioned, that using any of these
> strategies will result in _irreproducible builds_. That is, your code
>
 might

> build today, and then the same code will fail to build in the future,
> because the versions will resolve differently. The only way (I know of)
>
 to

> achieve reproducible builds is to use fixed release versions, always.
>
> Regards,
> Curtis
>
> --
> Curtis Rueden
> LOCI software architect - https://loci.wisc.edu/software
> ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden
>
>
> On Tue, Apr 11, 2017 at 9:57 AM, Magnanao, Hector <
>

Maven PDF Plugin footer

2017-04-13 Thread Alex O'Ree 
Is there a way to remove or change the footer printed on all pages
except for the title page?

It looks like the default is

(c) ${year} {$organization} -  All rights reserved

This appears to open be used for the fo implementation. It's not
present on the IText output, but I don't personally care for the
formatting it uses.

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