Github user rajivpjs commented on the issue:
https://github.com/apache/maven/pull/88
@khmarbaise - I have it working now. Please see changes. This works by
enabling @Test annotations together with @Rule.
---
If your project is set up for it, you can reply to this email and have your
Am 07/18/16 um 20:39 schrieb Robert Scholte:
> On Mon, 18 Jul 2016 15:54:24 +0200, Christian Schulte
> wrote:
>
>> Am 07/18/16 um 15:02 schrieb Christofer Dutz:
>>> Hi,
>>>
>>>
>>> Unfortuantely I wrote this down as a Jira ticket, but it seems it
>>> wasn't created in the end so I'll post thi
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
http://www.simpligility.com/2016/07/android-mave
Github user rajivpjs commented on the issue:
https://github.com/apache/maven/pull/88
I agree.
I have applied the following to the test class:
@Rule
private ExpectedException expectedException = ExpectedException.none();
Within the test I have added:
Github user khmarbaise commented on the issue:
https://github.com/apache/maven/pull/88
The @Test (expected =...) approach has one drawback, cause you can't check
the message of the exceptionWould be great...
---
If your project is set up for it, you can reply to this email and ha
Github user rajivpjs commented on a diff in the pull request:
https://github.com/apache/maven/pull/88#discussion_r71407078
--- Diff:
maven-model-builder/src/test/java/org/apache/maven/model/building/ComplexActivationTest.java
---
@@ -56,5 +56,26 @@ public void testAndConditionInAc
Github user khmarbaise commented on a diff in the pull request:
https://github.com/apache/maven/pull/88#discussion_r71406374
--- Diff:
maven-model-builder/src/test/java/org/apache/maven/model/building/ComplexActivationTest.java
---
@@ -56,5 +56,26 @@ public void testAndConditionIn
Github user rajivpjs commented on a diff in the pull request:
https://github.com/apache/maven/pull/88#discussion_r71405276
--- Diff:
maven-model-builder/src/test/java/org/apache/maven/model/building/ComplexActivationTest.java
---
@@ -56,5 +56,26 @@ public void testAndConditionInAc
Thanks Robert. Congratulations on the outstanding research.
Personally I am surprised that the Maven Plugin Plugin was scanning *all*
my dependencies. I have nothing to offer it. :-) My project source is where
my Mojo annotations are and not in any dependencies. So when I reported a
suspected ASM
Github user khmarbaise commented on a diff in the pull request:
https://github.com/apache/maven/pull/88#discussion_r71401238
--- Diff:
maven-model-builder/src/test/java/org/apache/maven/model/building/ComplexActivationTest.java
---
@@ -56,5 +56,26 @@ public void testAndConditionIn
Hi,
after some investigation Paul and I have good news: *none* of the classes
is leaking into the plugin.
Some details: the Annotation scanners doesn't only scan the compiled
classes in the outputDirectory, but also in all the dependencies in search
for other (Abstract)Mojo's.
One of the
The code for the project formerly known as Aether is being migrated to
Maven as the Eclipse Aether project has been retired.
Ideally we do not want to expose the code known as Aether to plugins, so we
will probably expose APIs targeted for the use-cases of Maven plugins...
We were somewhat hamper
+1 to explicitly marke them as deprecated
On Mon, Jul 18, 2016 at 5:23 PM, Paul Benedict wrote:
> Any thoughts on this? Could it coincide with the new skinning initiative?
>
> Cheers,
> Paul
>
> On Wed, Jun 29, 2016 at 4:31 PM, Paul Benedict
> wrote:
>
> > All,
> >
> > Today I googled for "mave
Hi Karl,
Thanks again for the argument. For me it's still a valid question of how
for example the license plugin
would apply itself on its source structure to fix/update Java header before
a release? (Of course, I
understand the principle of linearizability to fix the circular issue).
Just in cas
14 matches
Mail list logo
