[GitHub] maven-integration-testing pull request #18: [MNG-5958] restore binary compat...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/maven-integration-testing/pull/18


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Mojo testing with JUnit 4?

[Robert Scholte]

Hi,

see  
http://maven.apache.org/plugin-testing/maven-plugin-testing-harness/getting-started/index.html

and look for MojoRule

Robert

On Fri, 27 Jan 2017 21:36:13 +0100, Russell Gold   
wrote:


Are there versions of the base test cases (AbstractMojoTestCase,  
PlexusTestCase) that are usable with JUnit 4? If not, has anyone  
published a pattern for testing mojos with JUnit 4?

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


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

Mojo testing with JUnit 4?

[Russell Gold]

Are there versions of the base test cases (AbstractMojoTestCase, 
PlexusTestCase) that are usable with JUnit 4? If not, has anyone published a 
pattern for testing mojos with JUnit 4?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Always get the false value when calling org.apache.maven.shared.invoker.InvovationRequest.isUpdateSnapshots()

[Alix Lourme]

Hi Samuel,

If your substantive question is: "*How to catch the usage of
--update-snapshots on the Maven command line ?*", I'm not sure
*DefaultInvocationRequest
*is a way (used for maven-invoker call).

I had to do it in the past, and I have not found convenience solution like
some others parameters (ex: *offline* option, retrieved from settings).

A workaround could be (not work on all JRE):

String arguments =
> ManagementFactory.getRuntimeMXBean().getSystemProperties().get(
> "sun.java.command");

boolean isUpdateSnaphots = arguments.contains("-U") || arguments.contains(
> "--update-snapshots");

LOG.debug("isUpdateSnapshots: {}", isUpdateSnaphots);


But perhaps that Maven core team could give a more sustainable solution ...

Best regards

2017-01-24 11:33 GMT+01:00 Samuel Gaspari :

> Hello,
> Using the org.apache.maven.shared.invoker.InvovationRequest leads to get
> always the false value, even if the "-U" or "--update-snapshots" option is
> set.
>
> InvocationRequest request = new DefaultInvocationRequest();
> updateSnapshots = request.isUpdateSnapshots();
>
> Posts @
> http://maven.40175.n5.nabble.com/Plugin-Development-
> Injection-of-component-td5747607.html
> don't explain exactly if it is possible to get the value of an option, it
> seems to be used to set the value of an option.
>
> Thanks a lot for your help.
>
> Regards.
>
> Samuel Gaspari
>



-- 
Alix Lourme

Re: Requesting a single Monorepo enhancement for Maven

[Paul Hammant]

Here it is working with some Python scripting growing/shrinking the checkout.

http://paulhammant.com/2017/01/27/maven-in-a-google-style-monorepo/

A team could use it like that, right now.

On Wed, Jan 25, 2017 at 6:35 AM, Paul Hammant  wrote:
> OK so I've grappled git's sparse checkout and won (for now).  I can use it
> to subset the checkout (not clone) and make Maven3 do a reduced build graph
> without using profiles.
>
> Details:
> https://github.com/paul-hammant/maven-monorepo-experiment/tree/trick-maven-monorepo
> details
>
> Google has 86 TB of history in their trunk, and you could't use Git for that
> for many reasons, but we' are a couple of inches closer for Maven now.
>
> - Paul
>
> On Tue, Jan 24, 2017 at 10:44 PM, Paul Hammant  wrote:
>>
>> OK, take a look at
>> https://github.com/paul-hammant/maven-monorepo-experiment/compare/trick-maven-monorepo
>>
>> Branch 1 - vanilla-recursive is a branch with HazelCast's core and samples
>> checked in - a 14 minute build IF YOU SKIP TESTS AND YOU ALREADY HAD CACHED
>> DEPS !!.
>>
>> Branch 2 - pom.xml files renamed to pom-template.xml and some shell/python
>> fu to recreate pom.xml files (read-only, .gitignore'd) obeying the directory
>> structure, and excluding  lines where the directory is missing.
>>
>> See
>> https://github.com/paul-hammant/maven-monorepo-experiment/blob/trick-maven-monorepo/README.md
>>
>> That's enough for one night - more tomorrow. I get to find out whether
>> Git's sparse-checkout is elegant or a mess. At least for my use case.
>>
>> - Paul
>
>

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

[VOTE] Release Maven Wagon version 2.12

[Michael Osipov]

Hi,

We solved 28 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12338924

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1321/
https://repository.apache.org/content/repositories/maven-1321/org/apache/maven/wagon/wagon/2.12/wagon-2.12-source-release.zip

Source release checksum(s):
wagon-2.12-source-release.zip sha1: bc948e4a8e56d59b2176892df4ce0f292a461334

Staging site:
https://maven.apache.org/wagon-archives/wagon-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

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

[ANN] Apache Maven Invoker 3.0.0 Released (shared component)

[Robert Scholte]

The Apache Maven team is pleased to announce the release of the Apache  
Maven Invoker, version 3.0.0


This API is concerned with firing a Maven build in a new JVM. It  
accomplishes its task by building up a conventional Maven command line  
from options given in the current request, along with those global options  
specified in the invoker itself. Once it has the command line, the invoker  
will execute it, and capture the resulting exit code or any exception  
thrown to signal a failure to execute. Input/output control can be  
specified using an InputStream and up to two InvocationOutputHandlers.


 http://maven.apache.org/shared/maven-invoker/


  org.apache.maven.shared
  maven-invoker
  3.0.0


You can download the appropriate sources etc. from the download page:

http://maven.apache.org/shared/maven-invoker/download.cgi

Release Notes - Maven Shared Components - Version maven-invoker-3.0.0

** Improvement
* [MSHARED-342] - Maven Invoker still using -r option when such is no  
longer supported

* [MSHARED-459] - Remove deprecated parts from invoker interface
* [MSHARED-460] - Upgrade maven-shared-components parent to version 22
* [MSHARED-529] - Upgrade maven-shared-components parent to version 30
* [MSHARED-568] - Using inherited site descriptor / Style
* [MSHARED-569] - Upgrade plexus-utils to 3.0.24
* [MSHARED-570] - Upgrade plexus-component-metadata plugin /  
plexus-component-annotations

* [MSHARED-571] - Bump version to 3.0.0-SNAPSHOT
* [MSHARED-572] - Drop Maven 2 Support


Enjoy,

-The Apache Maven team

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

Re: Progress check for 3.5.0

[Michael Osipov]

Am 2017-01-25 um 22:08 schrieb Christian Schulte:

Am 01/25/17 um 20:53 schrieb Michael Osipov:

Am 2017-01-22 um 13:58 schrieb Michael Osipov:

Am 2017-01-22 um 11:22 schrieb Stephen Connolly:

I'm currently waiting on Hervé to start the 1.0.3 release of resolver.

Once we get that I'm going to start cutting RCs (I plan 2 a week apart)

Once we have a stable RC I will cut the release, and start a clock
towards
3.5.1 (6 weeks approx)

If you miss the boat, you can catch the next one, but we need to get this
project into a rhythm.



I started already working on the blessed issues. Do I need someone's
else consent to merge my issue branch into master assuming that it
passes the build in Jenkins?




I still have an unagreed list of issues for FIX-3.5.0:

MNG-5538 mvn start script causes cygwin warning

  ^
FIX-3.5.0


MNG-5567 Zip files are not included in classpaths at all

  ^
FIX-3.5.1 as 3.5.0 no longer would be a drop in replacement.


MNG-5579 Unify error output/check logic from shell and batch scripts


  ^
FIX-3.5.0


MNG-5823 mvnDebug doesn't work with M2_HOME with spaces - missing quotes

  ^
FIX-3.5.0


MNG-6144 DefaultWagonManagerTest#testGetMissingJarForced() passed
incorrect value
MNG-6145 Remove non-existent m2 include in component.xml
MNG-6146 Several small stylistic improvements to code and documentation


Haven't looked at those. If they stop making 3.5.0 a drop in replacement
for 3.3.9, I'd say FIX-3.5.1.


The first fixes only a test, no main code change. The second removes a 
non-existent ref, no-op. The last one is either docs or formatting 
improvement.




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

[RESULT][VOTE] Maven Shade Plugin 3.0.0

[Olivier Lamy]

Hi,
Vote has passed with the following result:
+1: Arnaud, Robert, Olivier

I will finish the process.

Cheers
-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Maven Shade Plugin 3.0.0

[Olivier Lamy]

my +1

On 24 January 2017 at 14:34, Olivier Lamy  wrote:

> Hi
> We solved 13 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12331395=Text=12317921=Create
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1319/
> https://repository.apache.org/content/repositories/maven-
> 1319/org/apache/maven/plugins/maven-shade-plugin/3.0.0/
> maven-shade-plugin-3.0.0-source-release.zip
>
> Source release checksum(s):
>
> curl https://repository.apache.org/content/repositories/maven-
> 1319/org/apache/maven/plugins/maven-shade-plugin/3.0.0/
> maven-shade-plugin-3.0.0-source-release.zip.sha1
> Staging site:
> https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>



-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

[RESULT] [VOTE] Release Apache Maven Invoker version 3.0.0 (shared component)

[Robert Scholte]

Hi,

The vote has passed with the following result:

+1 : Karl Heinz Marbaise, Robert Scholte, Hervé BOUTEMY

PMC quorum: reached

I will promote the artifacts to the central repo.

On Sun, 22 Jan 2017 21:03:31 +0100, Robert Scholte   
wrote:



Hi,

We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12331463=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20%20component%20%3D%20maven-invoker%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1316
https://repository.apache.org/content/repositories/maven-1316/org/apache/maven/shared/maven-invoker/3.0.0/maven-invoker-3.0.0-source-release.zip

Source release checksum(s):
maven-invoker-3.0.0-source-release.zip sha1:  
d8b39d6b91f571e8d304feec09b9e955ac7b75d0


Staging site:
https://maven.apache.org/shared-archives/maven-invoker-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

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


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