Hi,
here is the report content:
2 Unknown Licenses
***
Unapproved licenses:
/home/jenkins/jenkins-slave/workspace/maven-plugins-ITs-m3/maven-ear-
plugin/src/test/resources/m2repo/eartest/har-sample-one/1.0/har-sample-
one-1.0.har
/home/jenkins/jenkins-slave/works
Hi,
currently the maven-ear-plugin fails with RAT report problems...which i
can't reproduce..unfortunately i don't have workspace access...created
already https://issues.apache.org/jira/browse/INFRA-8577
Kind regards
Karl Heinz Marbaise
---
+1
Op Sun, 02 Nov 2014 09:50:26 +0100 schreef Karl Heinz Marbaise
:
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085&version=19853
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20JXR%20AND%20stat
+1
Regards,
Hervé
Le dimanche 2 novembre 2014 09:50:26 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 13 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085&version=198
> 53
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=pr
+1
Regards,
Hervé
Le samedi 1 novembre 2014 20:59:10 Andreas Gudian a écrit :
> Hi,
>
>
> We solved 31 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=20
> 175
>
> There are still lots of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator
Here my +1...
Kind regards
Karl Heinz Marbaise
On 11/2/14 9:50 AM, Karl Heinz Marbaise wrote:
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085&version=19853
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%2
My own +1.
Am Sonntag, 2. November 2014 schrieb Karl Heinz Marbaise :
> Hi,
>
> first to say trying to build surefire with Maven 2.2.1 will fail with a
> circular dependency...problem (as Kristian mentioned)...so best would be to
> require such things not by a README better by prerequisites/enfo
Op Sun, 02 Nov 2014 21:52:07 +0100 schreef Hervé BOUTEMY
:
Le samedi 1 novembre 2014 20:52:56 Robert Scholte a écrit :
Hi,
I've been working on the merger for Toolchains and my conclusion is that
we shouldn't add it to the settings.xml like it is specified right now.
Merging the settings.xm
The Apache Maven team is pleased to announce the release of the
Apache Maven Clean Plugin, version 2.6.1
The Clean Plugin is used when you want to remove files generated at build-time
in a project's directory.
http://maven.apache.org/plugins/maven-clean-plugin/
You should specify the version in
Hi Dan,
On 11/3/14 5:15 PM, Dan Tran wrote:
FYI, maven-clean-plugin 2.6.1 is not at Central yet.
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/
That's the reason why i didn't sent out the announcement mail...
till now
Kind regards
Karl Heinz Marbaise
Thanks
Hi Dan,
got response from sonatype...
https://issues.sonatype.org/browse/MVNCENTRAL-523
now the problem was fixed..
Kind regards
Karl Heinz Marbaise
On 11/3/14 7:48 PM, Dan Tran wrote:
It just arrived
-D
On Mon, Nov 3, 2014 at 8:15 AM, Dan Tran wrote:
FYI, maven-clean-plugin 2.6.1 is not
Hi Robert & Kristian,
JDK 9 Early Access with Project Jigsaw build b36 is available on
java.net [1]
The goal of Project Jigsaw [2] is to design and implement a standard
module system for the Java SE Platform,
and to apply that system to the Platform itself and to the JDK.
As described in J
It just arrived
-D
On Mon, Nov 3, 2014 at 8:15 AM, Dan Tran wrote:
> FYI, maven-clean-plugin 2.6.1 is not at Central yet.
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/
>
> Thanks
>
> -D
>
> On Sat, Nov 1, 2014 at 2:58 AM, Karl Heinz Marbaise
> wrote:
>
>> The vot
On 3 November 2014 16:57, Kristian Rosenvold
wrote:
> So for something like MASSEMBLY-474 I actually committed a testcase
> for 2.5.1, which makes it a bit more logical to tag it with both 2.5
> and 2.5.1.
There were commits related to the fix in 2.5.1, thus it seems legitimate to
tag both vers
So for something like MASSEMBLY-474 I actually committed a testcase
for 2.5.1, which makes it a bit more logical to tag it with both 2.5
and 2.5.1. But something like MASSEMBLY-597 only requires some
triaging on windows and should be closed without further ado if it
turns out to be fixed; should it
The bit about the "announcement" mail is fairly obvious; that cannot change.
I also think the issue should *at least* be tagged with the correct
version for the fix. Our jira supports multiple versions for "fixed",
so I could theoretically flag it as fixed for *both* 2.5 and the next
version, whi
I would opt to mark them Fixed in the version they were fixed. Although the
release notes emailed out are static, the JIRA release notes are dynamic. I
would look at the latter as the official list.
Cheers,
Paul
On Mon, Nov 3, 2014 at 10:16 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com>
I would like to configure surefire's providers in the plugin configuration.
My problem is that the aggregator POM defines surefire version in
pluginManagement, and the surefire's dependency has to declare the same
version.
This can be done via property ${surefire.version} antipattern. Then the
plu
On 3 November 2014 16:11, Kristian Rosenvold
wrote:
> For some projects like assembly, there are a whole bunch of issues
> that "later" will turn out to be fixed.
>
> For instance assembly plugin had 32 fixed issues at release time, but
> currently has 35 fixed issues in jira.
>
> The problem wit
FYI, maven-clean-plugin 2.6.1 is not at Central yet.
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/
Thanks
-D
On Sat, Nov 1, 2014 at 2:58 AM, Karl Heinz Marbaise
wrote:
> The vote has passed with the following result:
>
> +1 binding by
> Kristian Roselvold,
>
For some projects like assembly, there are a whole bunch of issues
that "later" will turn out to be fixed.
For instance assembly plugin had 32 fixed issues at release time, but
currently has 35 fixed issues in jira.
The problem with this is that these issues never make it into any kind
of release
Here's the link for this week:
https://plus.google.com/u/0/events/c7v61ah88ifc9e0vh6hnum87vro
There are a couple things I plan to talk about:
- demo of a new lifecycle profiling and visualization tool i've been working on
- discussion of the history of Maven Central and how I'd like to see the
c
22 matches
Mail list logo
