I created Debian packages for maven 3.2.5..

[Kevin Burton]

Yo dawg.  I heard you like maven. So I used maven to build debian packages
of maven so you can use maven while you build maven. ….

Debian only has an old/stale version of Debian so I created my own packages

https://github.com/spinn3r/apache-maven-deb

You an just run mvn package to build these.

I haven’t tested them extensively but they work fine for me so far.

I didn’t do much with the dependencies but you have to have Java installed.

Feel free to submit a pull request if you would like any changes.

-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile

[ANN] Apache Maven Dependency Plugin Version 2.10 Released

[Karl Heinz Marbaise]

The Apache Maven team is pleased to announce the release of the 
Apache Maven Dependecy Plugin, version 2.10

The dependency plugin provides the capability to manipulate artifacts. It can
copy and/or unpack artifacts from local or remote repositories to a specified
location.

http://maven.apache.org/plugins/maven-dependency-plugin/

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


  org.apache.maven.plugins
  maven-dependency-plugin
  2.10


Release Notes - Maven Dependency Plugin - Version 2.10

Bugs:

 * [MDEP-109] - Dependency plugin loses file permissions when unpacking or 
copying
artifact items
 * [MDEP-242] - Exclude does not work correctly for tar.gz (but is working for 
zip)
 * [MDEP-397] - When using unpack-dependencies with a zip created on unixes, 
contained symlinks aren't correctly unpackaged
 * [MDEP-436] - German umlauts in outputDirectory and destFileName getting 
garbled
 * [MDEP-466] - analyze fails on multimodule project (regression)

Improvements:

 * [MDEP-465] - Update version of plexus-archiver from 2.4.4 to 2.9
 * [MDEP-467] - Update plexus-io from 2.0.9 to 2.2
 * [MDEP-472] - Upgrade to maven-plugins parent version 27

New Feature:

 * [MDEP-476] - add the ability to ignore dependencies in the analyze-* goals


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: Question about Java version range using in Maven Enforcer Plugin

[Sandra Kosmalla]

Hi Curtis,

thanks for your explanation. Your suggestion works.

Regards,

Sandra

Am 27.01.2015 um 15:35 schrieb Curtis Rueden:
> Hi Sandra,
> 
>> I discussed with my team how they interprets the range value
>> [1.6,1.8]. They would interpret this as every Java 8 version is
>> possible. Is this a misinterpretation of us?
> 
> For the most part, "the RequireMavenVersion and RequireJavaVersion rules
> use the standard Maven version range syntax" [1].
> 
> So try writing:
> [1.6, 1.9)
> 
> Where the closing paren means "up to, but not including, 1.9."
> 
> Regards,
> Curtis
> 
> [1] http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html
> 
> On Tue, Jan 27, 2015 at 3:18 PM, Sandra Kosmalla  wrote:
> 
>> Hi,
>>
>> I want to set the RequiredJavaVersion rule in Maven Enforcer Plugin with
>> the requirement that using Java in versions 1.6, 1.7 and 1.8 is possible
>> (independent of update version). So I set the value [1.6,1.8] in the
>> property "version" in the RequiredJavaVersion rule. If I configure Java
>> 8 in my JAVA_HOME, the build failed because of the rule
>> RequiredJavaVersion.
>>
>> The goal enforcer:display-info prints following information
>>
>> [INFO] --- maven-enforcer-plugin:1.3.1:display-info (default-cli) @  ---
>> [INFO] Maven Version: 3.2.5
>> [INFO] JDK Version: 1.8.0_31 normalized as: 1.8.0-31
>> [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version:
>> 3.13.0-37-generic
>>
>> I have to set the range value to [1.6,1.8.0.*] so that the build runs
>> successfully.
>>
>> I discussed with my team how they interprets the range value [1.6,1.8].
>> They would interpret this as every Java 8 version is possible. Is this a
>> misinterpretation of us? What do you say about it?
>>
>> Thanks and best regards,
>>
>> Sandra Kosmalla
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> 

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

Re: Question about Java version range using in Maven Enforcer Plugin

[Curtis Rueden]

Hi Sandra,

> I discussed with my team how they interprets the range value
> [1.6,1.8]. They would interpret this as every Java 8 version is
> possible. Is this a misinterpretation of us?

For the most part, "the RequireMavenVersion and RequireJavaVersion rules
use the standard Maven version range syntax" [1].

So try writing:
[1.6, 1.9)

Where the closing paren means "up to, but not including, 1.9."

Regards,
Curtis

[1] http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html

On Tue, Jan 27, 2015 at 3:18 PM, Sandra Kosmalla  wrote:

> Hi,
>
> I want to set the RequiredJavaVersion rule in Maven Enforcer Plugin with
> the requirement that using Java in versions 1.6, 1.7 and 1.8 is possible
> (independent of update version). So I set the value [1.6,1.8] in the
> property "version" in the RequiredJavaVersion rule. If I configure Java
> 8 in my JAVA_HOME, the build failed because of the rule
> RequiredJavaVersion.
>
> The goal enforcer:display-info prints following information
>
> [INFO] --- maven-enforcer-plugin:1.3.1:display-info (default-cli) @  ---
> [INFO] Maven Version: 3.2.5
> [INFO] JDK Version: 1.8.0_31 normalized as: 1.8.0-31
> [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version:
> 3.13.0-37-generic
>
> I have to set the range value to [1.6,1.8.0.*] so that the build runs
> successfully.
>
> I discussed with my team how they interprets the range value [1.6,1.8].
> They would interpret this as every Java 8 version is possible. Is this a
> misinterpretation of us? What do you say about it?
>
> Thanks and best regards,
>
> Sandra Kosmalla
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Question about Java version range using in Maven Enforcer Plugin

[Sandra Kosmalla]

Hi,

I want to set the RequiredJavaVersion rule in Maven Enforcer Plugin with
the requirement that using Java in versions 1.6, 1.7 and 1.8 is possible
(independent of update version). So I set the value [1.6,1.8] in the
property "version" in the RequiredJavaVersion rule. If I configure Java
8 in my JAVA_HOME, the build failed because of the rule RequiredJavaVersion.

The goal enforcer:display-info prints following information

[INFO] --- maven-enforcer-plugin:1.3.1:display-info (default-cli) @  ---
[INFO] Maven Version: 3.2.5
[INFO] JDK Version: 1.8.0_31 normalized as: 1.8.0-31
[INFO] OS Info: Arch: amd64 Family: unix Name: linux Version:
3.13.0-37-generic

I have to set the range value to [1.6,1.8.0.*] so that the build runs
successfully.

I discussed with my team how they interprets the range value [1.6,1.8].
They would interpret this as every Java 8 version is possible. Is this a
misinterpretation of us? What do you say about it?

Thanks and best regards,

Sandra Kosmalla

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