GitHub user spyhunter99 opened a pull request:
https://github.com/apache/maven-plugins/pull/129
MPDF-81 merging in the needed doxia modules required for copyright ovâ¦
â¦errides, Add property based overrides for the copyright headers. Most of
the real changes were in
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/163
@shafiullas
Please rebase your branch.
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/163
@shafiullas
Register in Jira and open issue in
https://issues.apache.org/jira/browse/SUREFIRE. The message of the commit and
GitHub issue should be renamed to something like:
Github user Tibor17 commented on a diff in the pull request:
https://github.com/apache/maven-surefire/pull/163#discussion_r137895395
--- Diff:
maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/AbstractSurefireReportMojo.java
---
@@ -34,13 +27,21
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/143
@surli
You have not answered my questions yet. Let's do it now about making
releases. Register in Jira and open issue in
https://issues.apache.org/jira/browse/SUREFIRE. The message of
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@britter
I think this was forgotten. Should I process it?
---
-
To unsubscribe, e-mail:
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/159
@andrew-j-cohen
We do not have rights to close this issue. Please close it!
---
-
To unsubscribe, e-mail:
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/114
@Fuud
This branch was rebased and pushed to master. Please close it.
Thx for contributing.
---
-
To unsubscribe,
On Fri, 08 Sep 2017 22:31:55 +0200, Tibor Digana
wrote:
Releasing 3.0 is not possible within one month.
It can be only 3.0-M1. It's not about new API only however old 3.0 branch
exists, we plan to introduce Extensions, break backwards compatibility
with
Releasing 3.0 is not possible within one month.
It can be only 3.0-M1. It's not about new API only however old 3.0 branch
exists, we plan to introduce Extensions, break backwards compatibility with
Maven/System Properties and introduce JUnit5.
I think we can think of version 2.0 for Jigsaw.
Hi,
based on my earlier request in INFRA ticket[1] a new schema is already
there cause there were things not the best for example having an entry
"Question" which often lead people to use JIRA as a user forum..which is
now no possible anymore...
From my point of view this schema only needs
AFAIK the scheme still has to be created and verified, this is just
another part of that.
I don't think it's worth voting for every (little) change, especially not
now there's no final scheme yet.
Robert
On Fri, 08 Sep 2017 17:46:13 +0200, Tibor Digana
wrote:
Does it mean that we have to post new Vote on separate Maven Scheme?
On Fri, Sep 8, 2017 at 10:05 AM, Robert Scholte
wrote:
> This is part of the scheme in Jira.
> Since there's a proposal to make a separate Maven Scheme, this request
> should be added as well.
>
> Robert
Hi,
from the opensourcedesign we've received a couple of messages from
designers wanting to help us on this topic.
We've decided to create a separate issue for it on the github project of
opensourcedesign[1].
This will make it easier to communicate with each other.
We've chosen for their
On top of that I'd like to do a 2.20.1-jpms (or 2.20.1-jigsaw) release.
This has the same fixes as 2.20.1, but adds to support to run modular
projects with the module path.
It can't be part of the same release, because I had to push the Java
version for source/target to 1.7
For surefire I
This is part of the scheme in Jira.
Since there's a proposal to make a separate Maven Scheme, this request
should be added as well.
Robert
On Fri, 08 Sep 2017 08:53:31 +0200, Anders Hammar
wrote:
I agree, it's for us as committers to decide.
/Anders
On Fri, Sep 8,
I agree, it's for us as committers to decide.
/Anders
On Fri, Sep 8, 2017 at 8:51 AM, Michael Osipov wrote:
> Am 2017-09-08 um 00:42 schrieb Tibor Digana:
>
>> I found out that users create an issue in Jira and *assign version* [1].
>> I remember this did not happen in old
Am 2017-09-08 um 00:42 schrieb Tibor Digana:
I found out that users create an issue in Jira and *assign version* [1].
I remember this did not happen in old Jira.
So I decide to report a ticket in INFRA.
Do you have the same experiences?
What's your opinion about it?
[1]:
Great!
Enrico
On gio 7 set 2017, 23:34 Tibor Digana wrote:
> Hi All,
>
> I would like to stop development in Surefire master till Version 2.20.1 [1]
> is released. The reason is that an important issue with Out Of Memory Error
> is fixed.
>
> I have planned only 5
19 matches
Mail list logo