Unexpected result for MatchPatterns

Hi, could anyone explain to me, why the following unit test fails. (I am using MatchPatterns from maven-shared-utils 3.0.1:) final MatchPatterns mp = MatchPatterns.from("ORG/APACHE/**/*"); assertTrue(mp.matches("ORG/APACHE/TEST.JAVA", true)); Thanks, Jochen -- The next time

Re: Resolving an Artifact from Remote Repository instead of Local

Does that all make sense or do you need anything else to make it clearer? Thanks, Jordan On 7/18/16, 3:56 PM, "Jordan Lewis" wrote: >The plug-in does have a configuration that tries to ignore the local repo, but >whenever it resolves an artifact using

Re: Resolving an Artifact from Remote Repository instead of Local

Yes. It does seem that you do not have a Maven problem but have an Aether problem https://dev.eclipse.org/mailman/listinfo/aether-users Ron On 19/07/2016 9:54 AM, Jordan Lewis wrote: Does that all make sense or do you need anything else to make it clearer? Thanks, Jordan On 7/18/16, 3:56

Re: Resolving an Artifact from Remote Repository instead of Local

Correct. However, I used that mailing list that you listed and they pointed me to your list because you have taken the project over, correct? Jordan On 7/19/16, 10:25 AM, "Ron Wheeler" wrote: >Yes. >It does seem that you do not have a Maven problem but have

Re: Unexpected result for MatchPatterns

Hi Jochen, the ** means zero or more directories the * means exactly one file or directory Robert On Tue, 19 Jul 2016 08:00:57 +0200, Jochen Wiedmann wrote: Hi, could anyone explain to me, why the following unit test fails. (I am using MatchPatterns from

Re: Resolving an Artifact from Remote Repository instead of Local

Here is the email I received from them about it. Hi Jordan, … > Does anyone have any suggestions for me to resolve this or is there > another email list where this question would fit better? sadly, Aether has left Eclipse for Apache, to be developed there in closer collaboration with the

New Releases - Android Maven Plugin and Android NDK Maven Plugin

Hi all, Just a quick heads up that we cut two new releases of the Android-related Maven plugins. Android NDK Maven Plugin 1.1.2 - see http://www.simpligility.com/2016/07/android-ndk-maven-plugin-1-1-2-released/ Android Maven Plugin 4.4.3 - see

re: re-using server credentials for repositories

Hi, Looking at the code, there is really a one-to-one implicit mapping between the repository id and the server id used to look-up authentication information. Maven adds to a DefaultAuthenticationSelector the server id [1] as key of a map Id -> authentication info [2]. Then, a possible

re-using server credentials for repositories

I'm curious why there doesn't seem to be a way to reuse server credentials across multiple repositories (at least without a warning for those fortunate few on stack-overflow who claim success). For reference I mean as exemplified in [1], I have to define in my settings.xml a unique