Re: Updated documentation for Central Repository

On 3/25/2014 4:42 PM, Manfred Moser wrote: Hello everyone! We have updated the documentation for publishing artifacts to the Central Repository via the free Sonatype Open Source Repository Hosting (OSSRH) and added more documents about status, getting help and more and put it all together on

Re: Forcing Integration Tests Before a Release

Ahhh, actually adding "-P run-it" to the preparationGoals parameter does exactly what I want, and I can dispense with all the other complexities. I did not realize I could add other arguments to the preparationGoals parameter. Sometimes getting what you want from Maven is not obvious, until y

Re: Forcing Integration Tests Before a Release

On 26 March 2014 07:34, Eric Kolotyluk wrote: > I have tried to get this working, but it does not seem to work. When I do > > mvn release:prepare > > I get > > [INFO] Executing: cmd.exe /X /C "D:\bin\Apache\apache-maven-3.1.1\bin\mvn > -s C:\Users\Eric\AppData\Local\Temp\release-settings26521

Updated documentation for Central Repository

Hello everyone! We have updated the documentation for publishing artifacts to the Central Repository via the free Sonatype Open Source Repository Hosting (OSSRH) and added more documents about status, getting help and more and put it all together on a brand new website. Please look at the anno

Re: Forcing Integration Tests Before a Release

Eric, I do only use release:prepare, see https://github.com/1and1/foss-parent/blob/master/release line 47ff. Regards Mirko -- Sent from my mobile On Mar 25, 2014 10:05 PM, "Eric Kolotyluk" wrote: > I have tried to get this working, but it does not seem to work. When I do > > mvn release:prep

Re: Forcing Integration Tests Before a Release

Eric, you might modify the preparationGoals parameter to include -DperformRelease=true. Regards Mirko -- Sent from my mobile On Mar 25, 2014 10:05 PM, "Eric Kolotyluk" wrote: > I have tried to get this working, but it does not seem to work. When I do > > mvn release:prepare > > I get > > [

Re: Forcing Integration Tests Before a Release

performRelease is only set during release:perform :-) Regards Mirko -- Sent from my mobile On Mar 25, 2014 10:05 PM, "Eric Kolotyluk" wrote: > I have tried to get this working, but it does not seem to work. When I do > > mvn release:prepare > > I get > > [INFO] Executing: cmd.exe /X /C "D:\

Re: Incremental build API

Should work for any kind of plugins. We have integrated this into 20 or so mojos thus far ranging from source generation, resource processing, resource generation, compilation and class file processing. It's intended to be general purpose but we're looking for feedback to help flesh out the APIs

Re: Incremental build API

On Mar 25, 2014, at 2:36 PM, Mauri, Richard wrote: > Thanks, I’ll take a look > One of these days I was going to attempt a port of an incremental build > system we developed to Maven. > Some concepts include a post compile artifact byte code analyzer and > comparator that classifies the nature

Re: Incremental build API

Looking interesting - will definitely take a look at this for my various language plugins ( coffee script, clojure, frege ). On 26 Mar 2014, at 6:44, Jason van Zyl wrote: A note to those interested that the use of the API in Maven requires 3.2.1+.

Re: Incremental build API

Thanks, I’ll take a look One of these days I was going to attempt a port of an incremental build system we developed to Maven. Some concepts include a post compile artifact byte code analyzer and comparator that classifies the nature of change to help optimize away (in some cases) the dependent

Re: Forcing Integration Tests Before a Release

I have tried to get this working, but it does not seem to work. When I do mvn release:prepare I get [INFO] Executing: cmd.exe /X /C "D:\bin\Apache\apache-maven-3.1.1\bin\mvn -s C:\Users\Eric\AppData\Local\Temp\release-settings2652114304406041143.xml clean verify site --no-plugin-updates

Incremental build API

Hi, For those who are interested in incremental builds we, at Takari, have released a general purpose incremental build API with an initial focus on Maven. We've created a short, high-level description of the framework[1] and we've opened up our Git repository with the code[2]. We also have a s

[ANN] Animal Sniffer version 1.11 Released

Hi, The Mojo team is pleased to announce the release of Animal Sniffer version 1.11. This release permits the use of custom annotations in lieu of @IgnoreJRERequirement Animal Sniffer provides tools to assist verifying that classes compiled with a newer JDK/API are compatible with an older JDK/A

Re: [ANN] Apache Maven Shared Jarsigner 1.3.2 Released

No, the specified groupId is correct. There is a plugin as well but this announcement is for the shared component, not the plugin. /Anders On Tue, Mar 25, 2014 at 8:25 AM, Christian Schlichtherle < christ...@schlichtherle.de> wrote: > Hi all, > > I believe the groupId should be org.apache.maven

Re: properties that are not being resolved

The File vs String types note is the relevant part IIRC... It's not just file vs string though On Tuesday, 25 March 2014, Henrik Østerlund Gram wrote: > Thanks for the link. It was quite informative, but I'm again a little > confused because it is stated in your explanation, > the sections wil

Re: [ANN] Apache Maven Shared Jarsigner 1.3.2 Released

Hi all, I believe the groupId should be org.apache.maven.plugins, not org.apache.maven.shared. Regards, Christian Schlichtherle Am 24.03.2014 um 08:45 schrieb Tony Chemit : > The Maven team is pleased to announce the release of the Apache Maven > Jarsigner, > version 1.3.2 > > This compone