Re: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-03 Thread Hervé BOUTEMY 
on git, AFAIK, going to 2.11.1 seems the best practice (removing tag in origin 
repo is not reliable given people who have copied it won't have it removed 
automatically)

Regards,

Hervé

Le mardi 3 janvier 2017, 18:59:15 CET Dan Tran a écrit :
> I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now since
> some ppl may object removing remote history.
> 
> so we can keep the tag and move to 2.11.1-SNAPSHOT or remove wagon-2.11 tag
> and move on
> 
> -Dan
> 
> On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran  wrote:
> > yes I can.  so it is ok to remove the tag?
> > 
> > -D
> > 
> > On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov 
> > 
> > wrote:
> >> Am 2016-12-28 um 19:46 schrieb Dan Tran:
> >>> Hi
> >>> 
> >>> I am going to cancel this vote due to inconsistent test failure at
> >>> wagon-http provider on huge download test.
> >> 
> >> Can you please rollback release commits in the repo?
> >> 
> >> Michael
> >> 
> >> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov  wrote:
> >>> Am 2016-12-28 um 06:05 schrieb Dan Tran:
>  i still see the same timeout error on the jetty8 branch. No issue at
>  
> > master
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> > (default-test) on project wagon-http: There was a timeout or other
> > error in the fork -> [Help
> > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> > execute goal org.apache.maven.plugins:maven
> > -surefire-plugin:2.18.1:test
> > (default-test) on project wagon-http: There was a timeout or other
> > error in the fork
> > 
> > at org.apache.maven.lifecycle.int
> > 
> > ernal.MojoExecutor.execute(Moj
> > oExecutor.java:212)
>  
>  I have now extended tests to other Linux distros:
>  
>  Fedora 25, 64 bit:
>  OpenJDK 8 Update 111: pass
>  
>  CentOS 7, 64 bit:
>  OpenJDK 8 Update 111: pass
>  OpenJDK 7 Update 121: pass*
>  
>  *This is actually your combo which works for me, but not for you...
>  
>  Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs
>  on
>  Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
>  
>  
>  
>  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



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

Re: Cannot edit or comment on Wiki pages

2017-01-03 Thread Hervé BOUTEMY 
Hi,

I don't know how it was done (a good number of years ago) for me to have edit 
karma, but I have.
I looked for INFRA documentation on the topic, and found related procedure I 
didn't know [1]

I don't know who is the "Space Admin" for Maven Wiki, but we'll need to figure 
out and add this point in our new committer process: looks like new committers 
don't get access to the necessary toolset currently to work efficiently within 
the team...

BTW, is the Jenkins admin question fixed also?

Since if I contact INFRA on the Wiki topic, I'll see the Jenkins topic also.

Regards,

Hervé

[1] https://cwiki.apache.org/confluence/display/INFRA/Managing+permissions+on
+your+project%27s+Confluence+Space

Le mercredi 4 janvier 2017, 04:25:34 CET Christian Schulte a écrit :
> Hi,
> 
> user name is "schulte". I am not sure about this, but I think I do not
> have permission to do anything in the Wiki. I can read everything, but
> cannot edit things or comment on things.
> 
> Regards,



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

Re: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-03 Thread Michael Osipov 

Am 2017-01-04 um 03:59 schrieb Dan Tran:

I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now since
some ppl may object removing remote history.

so we can keep the tag and move to 2.11.1-SNAPSHOT or remove wagon-2.11 tag
and move on


I'd drop 2.11 altogether and re-run 2.11. I have two more open issues 
left. Those I have fixed for 2.12, I will reassign for 2.11.



Michael

On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran  wrote:


yes I can.  so it is ok to remove the tag?

-D

On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov 
wrote:


Am 2016-12-28 um 19:46 schrieb Dan Tran:


Hi

I am going to cancel this vote due to inconsistent test failure at
wagon-http provider on huge download test.



Can you please rollback release commits in the repo?

Michael


On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov  wrote:


Am 2016-12-28 um 06:05 schrieb Dan Tran:


i still see the same timeout error on the jetty8 branch. No issue at

master

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or other
error in the fork -> [Help
1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven
-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or other
error in the fork
at org.apache.maven.lifecycle.int
ernal.MojoExecutor.execute(Moj
oExecutor.java:212)



I have now extended tests to other Linux distros:

Fedora 25, 64 bit:
OpenJDK 8 Update 111: pass

CentOS 7, 64 bit:
OpenJDK 8 Update 111: pass
OpenJDK 7 Update 121: pass*

*This is actually your combo which works for me, but not for you...

Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs
on
Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.



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









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

Cannot edit or comment on Wiki pages

2017-01-03 Thread Christian Schulte 
Hi,

user name is "schulte". I am not sure about this, but I think I do not
have permission to do anything in the Wiki. I can read everything, but
cannot edit things or comment on things.

Regards,
-- 
Christian

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

Re: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-03 Thread Dan Tran 
I reverted the poms back to 2.11-SNAPSHOT not keep the tag for now since
some ppl may object removing remote history.

so we can keep the tag and move to 2.11.1-SNAPSHOT or remove wagon-2.11 tag
and move on

-Dan

On Tue, Jan 3, 2017 at 6:08 PM, Dan Tran  wrote:

> yes I can.  so it is ok to remove the tag?
>
> -D
>
> On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov 
> wrote:
>
>> Am 2016-12-28 um 19:46 schrieb Dan Tran:
>>
>>> Hi
>>>
>>> I am going to cancel this vote due to inconsistent test failure at
>>> wagon-http provider on huge download test.
>>>
>>
>> Can you please rollback release commits in the repo?
>>
>> Michael
>>
>>
>> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov  wrote:
>>>
>>> Am 2016-12-28 um 06:05 schrieb Dan Tran:

 i still see the same timeout error on the jetty8 branch. No issue at
> master
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> (default-test) on project wagon-http: There was a timeout or other
> error in the fork -> [Help
> 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven
> -surefire-plugin:2.18.1:test
> (default-test) on project wagon-http: There was a timeout or other
> error in the fork
> at org.apache.maven.lifecycle.int
> ernal.MojoExecutor.execute(Moj
> oExecutor.java:212)
>
>
 I have now extended tests to other Linux distros:

 Fedora 25, 64 bit:
 OpenJDK 8 Update 111: pass

 CentOS 7, 64 bit:
 OpenJDK 8 Update 111: pass
 OpenJDK 7 Update 121: pass*

 *This is actually your combo which works for me, but not for you...

 Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs
 on
 Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.



 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: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-03 Thread Dan Tran 
yes I can.  so it is ok to remove the tag?

-D

On Tue, Jan 3, 2017 at 2:01 PM, Michael Osipov  wrote:

> Am 2016-12-28 um 19:46 schrieb Dan Tran:
>
>> Hi
>>
>> I am going to cancel this vote due to inconsistent test failure at
>> wagon-http provider on huge download test.
>>
>
> Can you please rollback release commits in the repo?
>
> Michael
>
>
> On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov  wrote:
>>
>> Am 2016-12-28 um 06:05 schrieb Dan Tran:
>>>
>>> i still see the same timeout error on the jetty8 branch. No issue at
 master

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
 (default-test) on project wagon-http: There was a timeout or other
 error in the fork -> [Help
 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
 execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
 (default-test) on project wagon-http: There was a timeout or other
 error in the fork
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
 oExecutor.java:212)


>>> I have now extended tests to other Linux distros:
>>>
>>> Fedora 25, 64 bit:
>>> OpenJDK 8 Update 111: pass
>>>
>>> CentOS 7, 64 bit:
>>> OpenJDK 8 Update 111: pass
>>> OpenJDK 7 Update 121: pass*
>>>
>>> *This is actually your combo which works for me, but not for you...
>>>
>>> Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs on
>>> Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.
>>>
>>>
>>>
>>> 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: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2017-01-03 Thread Stephen Connolly 
Seconded on both

I'll update the wiki page tomorrow

On Tue 3 Jan 2017 at 21:44, Michael Osipov  wrote:

> Am 2017-01-02 um 21:34 schrieb Stephen Connolly:
>
> > On 2 January 2017 at 20:15, Michael Osipov  wrote:
>
> >
>
>  MNG-6029,
>
> >
>
> > I'd second this for 3.5.1
>
> > I have concerns with introducing for 3.5.0 as it affects how the
>
> > classpath
>
> > gets built and could cause behaviour differences between 3.3.9 and
> 3.5.0
>
> > (as it causes the test classpath to actually get resolved)
>
> >
>
> > -1 for 3.5.0 but I am open to change my position
>
> >
>
> >
>
>  It is actually two-fold, duplicate code and wrong scope. Fix has been
>
>  there for seven months without causing any IT failures. I think is is
> a
>
>  safe bet for an RC.
>
> 
>
> >>>
>
> >>>
>
> >>> But it breaks my goal for 3.5.0... the duplicate code part is OK for
>
> >>> 3.5.0... but the fixing the scope bug is why I remain -1. Perfectly
> fine
>
> >>> for 3.5.1
>
> >>>
>
> >>
>
> >> Let's split it! What do you think?
>
> >
>
> >
>
> > I am fine on the duplicate code removal for 3.5.0 as it should be a
> no-op.
>
> >
>
> > Create a new JIRA for the test scope change then and we can include that
> in
>
> > for 3.5.1?
>
>
>
> Here are the splitted issues:
>
> > [MNG-6147] MetadataResolutionResult#getGraph() contains duplicate if
> clause
>
>
>
> FIX-3.5.0
>
>
>
> > [MNG-6149] MetadataResolutionResult#getGraph() never resolves request
> type 'test'
>
>
>
> FIX-3.5.1
>
>
>
> Is that ok for you?
>
>
>
> Michael
>
>
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
> --
Sent from my phone

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2017-01-03 Thread Christian Schulte 
Am 01/03/17 um 14:55 schrieb Robert Scholte:
> Unscrubbed:
> MNG-5670 - ConcurrentModificationException during  
> DefaultMaven.newRepositorySession

This is related to MNG-6053 and MNG-6105. You can see that there is a
commit @MNG-6105 touching 'MavenRepositorySystemUtils' as well.  Should
be part of 3.5.0, IMHO. Maybe already is part of 3.5.0 due to MNG-6105
having the final fix to this.


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

Re: [VOTE] Releasing Wagon 2.11 - Cancel

2017-01-03 Thread Michael Osipov 

Am 2016-12-28 um 19:46 schrieb Dan Tran:

Hi

I am going to cancel this vote due to inconsistent test failure at
wagon-http provider on huge download test.


Can you please rollback release commits in the repo?

Michael


On Wed, Dec 28, 2016 at 7:08 AM, Michael Osipov  wrote:


Am 2016-12-28 um 06:05 schrieb Dan Tran:


i still see the same timeout error on the jetty8 branch. No issue at
master

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or other
error in the fork -> [Help
1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
(default-test) on project wagon-http: There was a timeout or other
error in the fork
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
oExecutor.java:212)



I have now extended tests to other Linux distros:

Fedora 25, 64 bit:
OpenJDK 8 Update 111: pass

CentOS 7, 64 bit:
OpenJDK 8 Update 111: pass
OpenJDK 7 Update 121: pass*

*This is actually your combo which works for me, but not for you...

Additionally, I added this version to Maven 3.4.0-SNAPSHOT and ran ITs on
Windows 10, Fedora 25 and FreeBSD 10.3-RELEASE. All passed.



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: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2017-01-03 Thread Michael Osipov 

Am 2017-01-02 um 21:34 schrieb Stephen Connolly:

On 2 January 2017 at 20:15, Michael Osipov  wrote:


MNG-6029,


I'd second this for 3.5.1
I have concerns with introducing for 3.5.0 as it affects how the
classpath
gets built and could cause behaviour differences between 3.3.9 and 3.5.0
(as it causes the test classpath to actually get resolved)

-1 for 3.5.0 but I am open to change my position



It is actually two-fold, duplicate code and wrong scope. Fix has been
there for seven months without causing any IT failures. I think is is a
safe bet for an RC.




But it breaks my goal for 3.5.0... the duplicate code part is OK for
3.5.0... but the fixing the scope bug is why I remain -1. Perfectly fine
for 3.5.1



Let's split it! What do you think?



I am fine on the duplicate code removal for 3.5.0 as it should be a no-op.

Create a new JIRA for the test scope change then and we can include that in
for 3.5.1?


Here are the splitted issues:

[MNG-6147] MetadataResolutionResult#getGraph() contains duplicate if clause


FIX-3.5.0


[MNG-6149] MetadataResolutionResult#getGraph() never resolves request type 
'test'


FIX-3.5.1

Is that ok for you?

Michael

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

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2017-01-03 Thread Robert Scholte 

MNG-   WONTFIX  upgrade m-assembly-p to 3.0.0

Created MNG-6148 for this. There are more plugins effected by this, but I  
guess these were updated in the general "update plugins" ticket.

IMO we should bind all plugin updates required for Java9 to this issue.

For me M3.5.1 is good enough as target, I've seen it working with Java9.

Robert

On Tue, 03 Jan 2017 15:19:06 +0100, Stephen Connolly  
 wrote:



https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 is updated
with these scope changes.

We still have 24 JIRAs under consideration... plus we need to decide on  
the

commits that do not have a JIRA

On Tue, 3 Jan 2017 at 13:55 Robert Scholte  wrote:


Just to confirm: I agree on the "Agreed changes" too

I'd like to add for 3.5.0:

By Stephen:
MNG-5824 - Support MAVEN_ARGS environment variable as a way of supplying
default command line arguments
MNG-5836 - logging config is overwritten by $M2_HOME/lib/ext/*.jar
MNG-5946 - Fix links etc. in README.txt which is part of the delivery

By Christian:
MNG-6023 - Upgrade of slf4j-simple to a version later than 1.7.16  
blocked

by upstream issue.

By Guillaume:
MNG-6117 - ${session.parallel} not correctly set

By Michael:
MNG-5954 - Remove outdated
maven-embedder/src/main/resources/META-INF/MANIFEST.MF
MNG-6102 - Introduce ${maven.conf} in m2.conf

 From Hervé:
MNG-6088 - after forked execution success, add an empty line
MNG-6092 - warn if prerequisites.maven is used for non-plugin projects

Unscrubbed:
MNG-5670 - ConcurrentModificationException during
DefaultMaven.newRepositorySession
MNG-6078 - Can't overwrite properties which have been defined in
.mvn/maven.config
MNG-6109   PluginDescriptor doesn't read since value of parameter


thanks,
Robert

-
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: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2017-01-03 Thread Michael Osipov 

Am 2017-01-03 um 15:19 schrieb Stephen Connolly:

https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 is updated
with these scope changes.

We still have 24 JIRAs under consideration... plus we need to decide on the
commits that do not have a JIRA


For my issue-less commits:

4f4690cb9ab2ed6e7ad421c28c05c27994e57800 Avoid implicit conversions of int to 
long
d99f9ef8c7ffe56966945d6f1b66f0280866ded5 Fix checkstyle error
1c9362be4328713386bd23b01f9e2c87674cb952 Use static final values instead of 
literals
8d16c2256d591d0a567dbadec9cc933f15a53fcc Fix Checkstyle error
5a3332ca347628605bec7d3e9f9309081aaba46c Remove ancient Subversion keywords
52945a679ec8f3f571d77658eda2fce06d637aa7 Use proper spelling of "e.g."
a26cc1b9636e19c28cd32ed1c844fec64dec55b6 Use the proper term for char U+002D 
(-) hyphen(-minus) instead of dash


Will be squashed into one commit/issue: MNG-6146


0eb1e937bf377b1c81193da3d9fca7ef344511b6 Remove trailing whitespace
9ea4ef4b609199e2207bc5638a14a44f6697072a Update Maven Dependency Plugin in 
Super POM to 2.10


Drop them.


65a928462d4b0ff30c49f619abd341069aefcb98 Pass force=true to 
DefaultWagonManagerTest#testGetMissingJarForced()


MNG-6144


f1c9f3fa859a3e2fe4c30d7c067735af93edb37e Remove non-existent m2 include in 
component.xml


MNG-6145


96a75579567efd52927f559ce811528c3e4429fc Language style improvements for commit 
5dab4940c9a7d3b362bd2a8b078b183e4eb521bb


Already agreed with Hervé to squash this into MNG-3507, please note that.


6518f1f364d9085d21a711ef31e2d43cdf4fa443 Added some docs in CLIReporting Utils


Trivial.


0a5351340df0df48c4c1d95c021bdf3f4f278ee6 Work around a rounding bug existed 
upto Java 7
cfaee84adf44c53e7a169ddaf11e16308708cb88 Removing redundant test


Will be squashed into one commit/issue: MNG-5977

Michael




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

Re: [VOTE] Releasing Wagon 2.11

2017-01-03 Thread Michael Osipov 
I have made some concluding tests on my machine at work because my home 
machine is so fast that you don't see a difference if you change something.
My tests are two-fold: improve HugeFileDownloadTest and manually 
reconstruct with pure Jetty and HttpClient (same versions).


First of all sparse files work with pure Java within tens of milliseconds:

Path tempDirectory = Files.createTempDirectory("jetty");
final ByteBuffer buf = ByteBuffer.allocate(4).putInt(2);
buf.rewind();

final OpenOption[] options = { StandardOpenOption.WRITE, 
StandardOpenOption.CREATE_NEW , StandardOpenOption.SPARSE };

final Path hugeFile = tempDirectory.resolve("hugefile.txt");

try (final SeekableByteChannel channel = 
Files.newByteChannel(hugeFile, options);) {

channel.position(HUGE_FILE_SIZE);
channel.write(buf);
}

Handmade tests are always faster than Wagon tests (all times approx.):
Wagon:
Create file: 80 s to 90 s
Download w/ content length: 3,5 min (optimized)
Download w/ chunks: 2,5 min


Handmade:
Create file: 60 s to 70 s (with NIO.2 and without sparse)
Download w/ content length: 2,5 min
Download w/ chunks: < 1,5 min

There is a similar issue: http://stackoverflow.com/q/9031311/696632

I started to play with buffer sizes in Wagon, the anonymous inner class 
and DefaultServlet. It seems to me that Jetty's IO class
buffer size of 64 KiB -- which is used by the DefaultServlet -- makes 
downloads slower in this use case.
I have turned the anonymous inner HttpServlet to 8 KiB as well as 
Wagon's internal buffer to 8 KiB (default 4 KiB has been tried too).
Unfortunately, the results sometimes vary but the smaller buffer most of 
the time wins against Jetty's IO. I will commit a changed version to 
that test and raise to 800 seconds. This should do it, in my opinion. 
There is nothing we can do anymore with spinning disks and the 
non-available sparse files on Windows. Note that RandomAccessFile 
creates them on Unix.


Additionally, I tried to download with curl from Jetty, it is a bit 
faster than the handmade version. Personally, there must be some 
misconfiguration in the HttpClient if it performs slower than my cheap 
hand-written code.


To finalize this. I ran the tests on an old Pentium 4 2,4 GHz, 2 GiB RAM 
with FreeBSD 11.0-STABLE:
2017-01-02T21:39:53.542 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - Creating 
test file
2017-01-02T21:39:53.549 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - Test file 
created
2017-01-02T21:39:53.552 [main] INFO org.eclipse.jetty.server.Server - 
jetty-8.1.22.v20160922
2017-01-02T21:39:53.556 [main] INFO 
org.eclipse.jetty.server.AbstractConnector - Started 
SelectChannelConnector@0.0.0.0:20435

http://localhost:20435 - Session: Opened
2017-01-02T21:39:53.569 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - Fetching 
'hugefile.txt' in chunks
2017-01-02T21:44:51.315 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - The file 
was successfully fetched

http://localhost:20435 - Session: Disconnecting
http://localhost:20435 - Session: Disconnected
2017-01-02T21:44:51.329 [main] INFO 
org.eclipse.jetty.server.handler.ContextHandler - stopped 
o.e.j.s.ServletContextHandler{/,file:/usr/home/mosipov/Projekte/maven-wagon/wagon-providers/wagon-http/target/}
2017-01-02T21:44:51.868 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - Creating 
test file
2017-01-02T21:44:51.893 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - Test file 
created
2017-01-02T21:44:51.894 [main] INFO org.eclipse.jetty.server.Server - 
jetty-8.1.22.v20160922
2017-01-02T21:44:51.905 [main] INFO 
org.eclipse.jetty.server.AbstractConnector - Started 
SelectChannelConnector@0.0.0.0:23105

http://localhost:23105 - Session: Opened
2017-01-02T21:44:52.019 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - Fetching 
'hugefile.txt' with content length
2017-01-02T21:48:03.017 [main] INFO 
org.apache.maven.wagon.providers.http.HugeFileDownloadTest - The file 
was successfully fetched

http://localhost:23105 - Session: Disconnecting
http://localhost:23105 - Session: Disconnected
2017-01-02T21:48:03.030 [main] INFO 
org.eclipse.jetty.server.handler.ContextHandler - stopped 
o.e.j.s.ServletContextHandler{/,file:/usr/home/mosipov/Projekte/maven-wagon/wagon-providers/wagon-http/target/}


For such an old hardware, this is still decent.

Michael

Am 2016-12-31 um 21:20 schrieb Guillaume Boué:

Thanks for the analysis! Agree with dropping fsutil then; I committed
the addition of the logs with it just so that we can have concrete
numbers for comparison (the last build indicates there was no permission
issues in using it, otherwise it wouldn't have timed out but just failed
to find the file). NIO.2 requires Java 7 though, so looks like a good
reason to try and update to it (and Jetty 9 in the process, as Olivier

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

2017-01-03 Thread Manfred Moser 
I am +100 on that. Thanks for taking the initiative to get things back on track.

Manfred

Stephen Connolly wrote on 2017-01-03 09:40:

> I believe we have consensus, here is the final call for anyone objecting to
> the plan to have their opinions considered.
> 
> Here is the draft of the proposal for the vote:
> 
> NOTE: THIS IS *NOT* THE VOTE
> 
> -BEGIN DRAFT-
> Hi,
> 
> We have collectively managed to mess up our ability to follow the original
> release plan for 3.4.0 which was originally supposed to consist of an
> effective no-op change of Eclipse's Aether for the code after migration to
> Apache's Maven Resolver plus some other orthogonal changes around logging
> colourization and launcher script bug fixes.
> 
> Given that some developer private builds of the current master branch have
> been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
> closed with a fixed version of 3.4.0.
> 
> For us to release a 3.4.0 with those fixes reverted, could cause confusion
> with our user community.
> 
> Additionally the informal practice of keeping existing integration tests as
> RTC has not been followed, leading to some people to question whether the
> integration tests remain valid.
> 
> For all the above reasons it is proposed to do *all* the following as an
> whole:
> 
> 1. In git://git.apache.org/maven.git we will rename the current master
> branch to `pre-reset-master` and recreate `master` as (TODO HASH
> corresponding to a commit that does a version bump to 3.5.0-SNAPSHOT on top
> of 737de43e392fc15a0ce366db98d70aa18b3f6c03 - by having a commit that is
> not on the current master branch it will prevent accidental fast-forward
> commits)
> 
> 2. In git://git.apache.org/maven-integration-testing.git we will rename the
> current master branch to `pre-reset-master` and recreate `master` as (TODO
> HASH corresponding to a commit on top of 94bd771c88cc96014ca0ddaa07ac6f
> 778b3c7501)
> 
> 3. In git://git.apache.org/maven-resolver.git we will rename the current
> master branch to `pre-reset-master` and recreate `master`
> as b74f7a1e8837875b4780199f644119f55d22465d (i.e. the 1.0.x branch)
> 
> We will then proceed to have (ideally) the original committers cherry-pick
> (and tidy up an squash... if the original committers are not able to assist
> then squashing may not be practicable) those changes that have been agreed
> for 3.5.0 as summarized on the
> https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
> (authorative source of the decisions summarized in the wiki page is the
> mail thread:
> https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
> ).
> 
> As this involves a --force push on the `master` branch, we want to get the
> approval of the committers before continuing.
> 
> The vote will be open for at least 72 hours.
> 
> The vote will be decided by a simple majority of valid votes cast. There is
> no veto.
> 
> The vote is open to all committers.
> 
> In addition, for the vote to be valid, there must be at least 3x+1 votes
> from PMC members
> 
> TODO: insert voting options template
> 
> -Stephen
> -END DRAFT-
> 
> I'm going to start the vote in a clean thread some time tomorrow. Any
> suggested changes will need to be provided before say 12:00 UTC,
> 
> If you do not agree that we have consensus (i.e. you are likely to vote -1)
> please stand up and let us know your concerns so that we may adapt the plan
> to include your concerns. There is no harm in not liking the current plan,
> we would rather delay and alter our plan to address your concerns and have
> the vote thread as a formality rather than the vote thread becoming a
> source of conflict and disharmony in our community.
> 
> Before I call the vote I will push the forking changes to maven and
> maven-integration-testing onto a separate branch so that the vote thread
> can include those hashes. I am delaying doing that until tomorrow in case
> there is a change in plan on which hash to base off.
> 
> Fun times!
> 


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

Re: [DISCUSS] Resetting Master branch to 737de43e392fc15a0ce366db98d70aa18b3f6c03

2017-01-03 Thread Stephen Connolly 
I believe we have consensus, here is the final call for anyone objecting to
the plan to have their opinions considered.

Here is the draft of the proposal for the vote:

NOTE: THIS IS *NOT* THE VOTE

-BEGIN DRAFT-
Hi,

We have collectively managed to mess up our ability to follow the original
release plan for 3.4.0 which was originally supposed to consist of an
effective no-op change of Eclipse's Aether for the code after migration to
Apache's Maven Resolver plus some other orthogonal changes around logging
colourization and launcher script bug fixes.

Given that some developer private builds of the current master branch have
been shared with as 3.4.0-SNAPSHOT. More critically, JIRA issues have been
closed with a fixed version of 3.4.0.

For us to release a 3.4.0 with those fixes reverted, could cause confusion
with our user community.

Additionally the informal practice of keeping existing integration tests as
RTC has not been followed, leading to some people to question whether the
integration tests remain valid.

For all the above reasons it is proposed to do *all* the following as an
whole:

1. In git://git.apache.org/maven.git we will rename the current master
branch to `pre-reset-master` and recreate `master` as (TODO HASH
corresponding to a commit that does a version bump to 3.5.0-SNAPSHOT on top
of 737de43e392fc15a0ce366db98d70aa18b3f6c03 - by having a commit that is
not on the current master branch it will prevent accidental fast-forward
commits)

2. In git://git.apache.org/maven-integration-testing.git we will rename the
current master branch to `pre-reset-master` and recreate `master` as (TODO
HASH corresponding to a commit on top of 94bd771c88cc96014ca0ddaa07ac6f
778b3c7501)

3. In git://git.apache.org/maven-resolver.git we will rename the current
master branch to `pre-reset-master` and recreate `master`
as b74f7a1e8837875b4780199f644119f55d22465d (i.e. the 1.0.x branch)

We will then proceed to have (ideally) the original committers cherry-pick
(and tidy up an squash... if the original committers are not able to assist
then squashing may not be practicable) those changes that have been agreed
for 3.5.0 as summarized on the
https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 wiki page
(authorative source of the decisions summarized in the wiki page is the
mail thread:
https://mail-archives.apache.org/mod_mbox/maven-dev/201612.mbox/%3CCA%2BnPnMxERdjJq5ChMNP-HN_AvZOs8sm7Ud5aVcEza0BPnm5ZOw%40mail.gmail.com%3E
).

As this involves a --force push on the `master` branch, we want to get the
approval of the committers before continuing.

The vote will be open for at least 72 hours.

The vote will be decided by a simple majority of valid votes cast. There is
no veto.

The vote is open to all committers.

In addition, for the vote to be valid, there must be at least 3x+1 votes
from PMC members

TODO: insert voting options template

-Stephen
-END DRAFT-

I'm going to start the vote in a clean thread some time tomorrow. Any
suggested changes will need to be provided before say 12:00 UTC,

If you do not agree that we have consensus (i.e. you are likely to vote -1)
please stand up and let us know your concerns so that we may adapt the plan
to include your concerns. There is no harm in not liking the current plan,
we would rather delay and alter our plan to address your concerns and have
the vote thread as a formality rather than the vote thread becoming a
source of conflict and disharmony in our community.

Before I call the vote I will push the forking changes to maven and
maven-integration-testing onto a separate branch so that the vote thread
can include those hashes. I am delaying doing that until tomorrow in case
there is a change in plan on which hash to base off.

Fun times!

[GitHub] maven-surefire issue #137: Fix SUREFIRE-1239

2017-01-03 Thread jsdima 
Github user jsdima commented on the issue:

https://github.com/apache/maven-surefire/pull/137
  
you are welcome



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-surefire pull request #137: Fix SUREFIRE-1239

2017-01-03 Thread jsdima 
Github user jsdima closed the pull request at:

https://github.com/apache/maven-surefire/pull/137


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2017-01-03 Thread Stephen Connolly 
https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 is updated
with these scope changes.

We still have 24 JIRAs under consideration... plus we need to decide on the
commits that do not have a JIRA

On Tue, 3 Jan 2017 at 13:55 Robert Scholte  wrote:

> Just to confirm: I agree on the "Agreed changes" too
>
> I'd like to add for 3.5.0:
>
> By Stephen:
> MNG-5824 - Support MAVEN_ARGS environment variable as a way of supplying
> default command line arguments
> MNG-5836 - logging config is overwritten by $M2_HOME/lib/ext/*.jar
> MNG-5946 - Fix links etc. in README.txt which is part of the delivery
>
> By Christian:
> MNG-6023 - Upgrade of slf4j-simple to a version later than 1.7.16 blocked
> by upstream issue.
>
> By Guillaume:
> MNG-6117 - ${session.parallel} not correctly set
>
> By Michael:
> MNG-5954 - Remove outdated
> maven-embedder/src/main/resources/META-INF/MANIFEST.MF
> MNG-6102 - Introduce ${maven.conf} in m2.conf
>
>  From Hervé:
> MNG-6088 - after forked execution success, add an empty line
> MNG-6092 - warn if prerequisites.maven is used for non-plugin projects
>
> Unscrubbed:
> MNG-5670 - ConcurrentModificationException during
> DefaultMaven.newRepositorySession
> MNG-6078 - Can't overwrite properties which have been defined in
> .mvn/maven.config
> MNG-6109   PluginDescriptor doesn't read since value of parameter
>
>
> thanks,
> Robert
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

2017-01-03 Thread Robert Scholte 

Just to confirm: I agree on the "Agreed changes" too

I'd like to add for 3.5.0:

By Stephen:
MNG-5824 - Support MAVEN_ARGS environment variable as a way of supplying  
default command line arguments

MNG-5836 - logging config is overwritten by $M2_HOME/lib/ext/*.jar
MNG-5946 - Fix links etc. in README.txt which is part of the delivery

By Christian:
MNG-6023 - Upgrade of slf4j-simple to a version later than 1.7.16 blocked  
by upstream issue.


By Guillaume:
MNG-6117 - ${session.parallel} not correctly set

By Michael:
MNG-5954 - Remove outdated  
maven-embedder/src/main/resources/META-INF/MANIFEST.MF

MNG-6102 - Introduce ${maven.conf} in m2.conf

From Hervé:
MNG-6088 - after forked execution success, add an empty line
MNG-6092 - warn if prerequisites.maven is used for non-plugin projects

Unscrubbed:
MNG-5670 - ConcurrentModificationException during  
DefaultMaven.newRepositorySession
MNG-6078 - Can't overwrite properties which have been defined in  
.mvn/maven.config

MNG-6109   PluginDescriptor doesn't read since value of parameter


thanks,
Robert

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