[GitHub] maven-plugins pull request #129: MPDF-81 merging in the needed doxia modules...

[spyhunter99]

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 FoAggregatedSink

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/spyhunter99/maven-plugins feature/MPDF-81

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/129.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #129


commit 27c221e8cece7a5b8574a0aeb593efbd02547ccf
Author: Alex O'Ree 
Date:   2017-09-09T02:14:14Z

MPDF-81 merging in the needed doxia modules required for copyright 
overrides, Add property based overrides for the copyright headers. Most of the 
real changes were in FoAggregatedSink




---

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

[GitHub] maven-surefire issue #163: Surefire-report

[Tibor17]

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 commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-surefire issue #163: Surefire-report

[Tibor17]

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:
[SUREFIRE-12345] Same issue title as current GitHub.


---

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

[GitHub] maven-surefire pull request #163: Surefire-report

[Tibor17]

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 @@
 import org.apache.maven.shared.utils.PathTool;
 import org.apache.maven.shared.utils.StringUtils;
 
+import java.io.File;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Iterator;
+import java.util.List;
+import java.util.Locale;
+import java.util.ResourceBundle;
+
 /**
  * Abstract base class for reporting test results using Surefire.
  *
  * @author Stephen Connolly
  */
 public abstract class AbstractSurefireReportMojo
-extends AbstractMavenReport
+extends AbstractMavenReport
--- End diff --

Do not change lines only because of checkstyle. Do it again and fix only 
lines for the purpose of this issue only.


---

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

[GitHub] maven-surefire issue #143: maven-surefire-parser: add new method isError in ...

[Tibor17]

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 the commit 
should be renamed to something like:
`[SUREFIRE-12345] Same issue title as in GitHub`.


---

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

[GitHub] maven-surefire issue #141: SUREFIRE-1331: Bump version number for 3.0.0 rele...

[Tibor17]

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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-surefire issue #159: SUREFIRE-1391: Eliminate redundant call in calcul...

[Tibor17]

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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-surefire issue #114: Parallel runner should not drop away runners that...

[Tibor17]

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, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Want to cut release Version 2.20.1 in Surefire project

[Robert Scholte]

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

Maven/System Properties and introduce JUnit5.

I think we can think of version 2.0 for Jigsaw.
Robert, I did not have time to analyse your branch yet because I was busy
this week.
Question: Why you need Java 7?


Plexus-Java requires Java 7.



On Fri, Sep 8, 2017 at 10:09 AM, Robert Scholte 
wrote:


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 think it is better to do that in a 3.0.0 release together
with an upgrade of the Maven dependencies to 3.0

Robert



On Thu, 07 Sep 2017 23:34:17 +0200, Tibor Digana <
tibor.dig...@googlemail.com> 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 simple fixes, the most of them offered by our
contributors, in Version 2.20.2, and one important issue in 2.20.3.

[1]:
https://issues.apache.org/jira/issues/?jql=project%20%3D%
20SUREFIRE%20AND%20fixVersion%20%3D%202.20.1






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

Re: Want to cut release Version 2.20.1 in Surefire project

[Tibor Digana]

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.
Robert, I did not have time to analyse your branch yet because I was busy
this week.
Question: Why you need Java 7?

On Fri, Sep 8, 2017 at 10:09 AM, Robert Scholte 
wrote:

> 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 think it is better to do that in a 3.0.0 release together
> with an upgrade of the Maven dependencies to 3.0
>
> Robert
>
>
>
> On Thu, 07 Sep 2017 23:34:17 +0200, Tibor Digana <
> tibor.dig...@googlemail.com> 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 simple fixes, the most of them offered by our
>> contributors, in Version 2.20.2, and one important issue in 2.20.3.
>>
>> [1]:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20SUREFIRE%20AND%20fixVersion%20%3D%202.20.1
>>
>>


-- 
Cheers
Tibor

Re: Users can assign Fix Version/s in Jira

[Karl Heinz Marbaise]

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 to be enhanced for the 
requested part assigning a version to a ticket...


Kind regards
Karl Heinz Marbaise

[1]: https://issues.apache.org/jira/browse/INFRA-14898

On 08/09/17 18:20, Robert Scholte wrote:
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



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, 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 Jira.
So I decide to report a ticket in INFRA.

Do you have the same experiences?
What's your opinion about it?

[1]: https://issues.apache.org/jira/browse/INFRA-15047


This is an annoying bug. I constantly remove
user-assigned version when I
see it, because this decision should only be upto us,
not them.

Michael


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

Re: Users can assign Fix Version/s in Jira

[Robert Scholte]

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



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, 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 Jira.
So I decide to report a ticket in INFRA.

Do you have the same experiences?
What's your opinion about it?

[1]: https://issues.apache.org/jira/browse/INFRA-15047



This is an annoying bug. I constantly remove user-assigned version  
when I

see it, because this decision should only be upto us, not them.

Michael

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





--Cheers
Tibor

Re: Users can assign Fix Version/s in Jira

[Tibor Digana]

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
>
>
>
> 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, 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 Jira.
 So I decide to report a ticket in INFRA.

 Do you have the same experiences?
 What's your opinion about it?

 [1]: https://issues.apache.org/jira/browse/INFRA-15047


>>> This is an annoying bug. I constantly remove user-assigned version when I
>>> see it, because this decision should only be upto us, not them.
>>>
>>> Michael
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>


-- 
Cheers
Tibor

Website redesign

[Robert Scholte]

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 issue tracking system instead of a MNGSITE-issue to  
make it easier for the designers to do their work.
For those interested in contributing and to help this forward are free to  
join.

Once there are results worth sharing here we'll do so.

thanks,
Robert

[1] https://github.com/opensourcedesign/jobs/issues/246

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

Re: Want to cut release Version 2.20.1 in Surefire project

[Robert Scholte]

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 think it is better to do that in a 3.0.0 release together  
with an upgrade of the Maven dependencies to 3.0


Robert


On Thu, 07 Sep 2017 23:34:17 +0200, 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 simple fixes, the most of them offered by our
contributors, in Version 2.20.2, and one important issue in 2.20.3.

[1]:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20fixVersion%20%3D%202.20.1



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

Re: Users can assign Fix Version/s in Jira

[Robert Scholte]

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, 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 Jira.
So I decide to report a ticket in INFRA.

Do you have the same experiences?
What's your opinion about it?

[1]: https://issues.apache.org/jira/browse/INFRA-15047



This is an annoying bug. I constantly remove user-assigned version when  
I

see it, because this decision should only be upto us, not them.

Michael

-
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

Re: Users can assign Fix Version/s in Jira

[Anders Hammar]

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 Jira.
>> So I decide to report a ticket in INFRA.
>>
>> Do you have the same experiences?
>> What's your opinion about it?
>>
>> [1]: https://issues.apache.org/jira/browse/INFRA-15047
>>
>
> This is an annoying bug. I constantly remove user-assigned version when I
> see it, because this decision should only be upto us, not them.
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Users can assign Fix Version/s in Jira

[Michael Osipov]

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]: https://issues.apache.org/jira/browse/INFRA-15047


This is an annoying bug. I constantly remove user-assigned version when 
I see it, because this decision should only be upto us, not them.


Michael

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

Re: Want to cut release Version 2.20.1 in Surefire project

[Enrico Olivelli]

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 simple fixes, the most of them offered by our
> contributors, in Version 2.20.2, and one important issue in 2.20.3.
>
> [1]:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20fixVersion%20%3D%202.20.1
>
>
> --
> Cheers
> Tibor
>
-- 


-- Enrico Olivelli