RE: Need help with testing of MEAR-153 implementation
Hi, I was able to modify & extend documentation of Maven EAR Plugin and https://github.com/apache/maven-ear-plugin/pull/24 is self-contained now. I still need help with testing of this pull request with skinnyModules option turned off (the default behavior) and turned on (the new behavior) for the case when EAR archive contains WAR, SAR, HAR, RAR and WSR modules. I need to test that on real code (i.e. smth which is deployed into Java EE container and can be validated though invocation) which uses SAR, HAR, RAR and WSR modules of EAR archive to ensure that things work as expected, so volunteers wanted. Thank you. Regards, Marat Abrarov. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] michael-o commented on a change in pull request #212: [/MNGSITE-393} Remove legacy Maven 2 info
michael-o commented on a change in pull request #212:
URL: https://github.com/apache/maven-site/pull/212#discussion_r510405068
##
File path: content/apt/guides/mini/guide-http-settings.apt
##
@@ -30,31 +30,13 @@ Advanced Configuration of the HttpClient HTTP Wagon
%{toc}
-*Notice on Maven Versioning and Availability
-
-**Maven 2.2.0
-
- Starting in <>, the HttpClient wagon was the implementation in
use. The remainder of this document
- deals specifically with the differences between the HttpClient- and
Sun-based HTTP wagons.
-
-**Maven 2.2.1
-
- Due to several critical issues introduced by the HttpClient-based HTTP
wagon, <> reverted back to
- the Sun implementation (a.k.a. 'lightweight') of the HTTP wagon as the
default for HTTP/HTTPS transfers.
- The issues with the HttpClient-based wagon were mainly related to checksums,
transfer timeouts, and NTLM proxies,
- and served as the primary cause for the release of <<2.2.1>> in the first
place.
-
- <>, starting in <> you have a choice: you can use the
default wagon implementation for a given
- protocol, or you can select an alternative wagon <<>> you'd like
to use on a per-protocol basis.
+ You can use the default wagon implementation for a given
+ protocol, or you can select an alternative wagon <<>> on a
per-protocol basis.
For more information, see the {{{./guide-wagon-providers.html}Guide to Wagon
Providers}} \[3\].
-
-**Maven 3.0.4
-
- With 3.0.4, the default wagon http(s) is now the HttpClient based on
{{{http://hc.apache.org/httpcomponents-client-ga}Apache Http Client 4.1.2}}.
- There is now a http connection pooling to prevent reopening http(s) to
remote server for each requests.
+ The default wagon http(s) is the HttpClient based on
{{{http://hc.apache.org/httpcomponents-client-ga}Apache Http Client 4.1.2}}.
+ HTTP connection pooling prevents reopening http(s) to remote server for each
requests.
Review comment:
This sentence is non-sense. It should read: HTTP connection pooling
prevents opening new ones to remote server for each request.
##
File path: content/apt/guides/mini/guide-http-settings.apt
##
@@ -30,31 +30,13 @@ Advanced Configuration of the HttpClient HTTP Wagon
%{toc}
-*Notice on Maven Versioning and Availability
-
-**Maven 2.2.0
-
- Starting in <>, the HttpClient wagon was the implementation in
use. The remainder of this document
- deals specifically with the differences between the HttpClient- and
Sun-based HTTP wagons.
-
-**Maven 2.2.1
-
- Due to several critical issues introduced by the HttpClient-based HTTP
wagon, <> reverted back to
- the Sun implementation (a.k.a. 'lightweight') of the HTTP wagon as the
default for HTTP/HTTPS transfers.
- The issues with the HttpClient-based wagon were mainly related to checksums,
transfer timeouts, and NTLM proxies,
- and served as the primary cause for the release of <<2.2.1>> in the first
place.
-
- <>, starting in <> you have a choice: you can use the
default wagon implementation for a given
- protocol, or you can select an alternative wagon <<>> you'd like
to use on a per-protocol basis.
+ You can use the default wagon implementation for a given
+ protocol, or you can select an alternative wagon <<>> on a
per-protocol basis.
For more information, see the {{{./guide-wagon-providers.html}Guide to Wagon
Providers}} \[3\].
-
-**Maven 3.0.4
-
- With 3.0.4, the default wagon http(s) is now the HttpClient based on
{{{http://hc.apache.org/httpcomponents-client-ga}Apache Http Client 4.1.2}}.
- There is now a http connection pooling to prevent reopening http(s) to
remote server for each requests.
+ The default wagon http(s) is the HttpClient based on
{{{http://hc.apache.org/httpcomponents-client-ga}Apache Http Client 4.1.2}}.
Review comment:
`{{{https://hc.apache.org/httpcomponents-client-4.5.x/}Apache Http
Client 4.5.x}}
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] elharo opened a new pull request #212: [/MNGSITE-393} Remove legacy Maven 2 info
elharo opened a new pull request #212: URL: https://github.com/apache/maven-site/pull/212 @michael-o This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] mattjohnson opened a new pull request #211: Fixes custom header configuration example
mattjohnson opened a new pull request #211: URL: https://github.com/apache/maven-site/pull/211 Fixes headers configuration to use property instead of header This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Script Interpreter version 1.3
that will be a future discussion to have Le lundi 19 octobre 2020, 13:03:04 CEST Elliotte Rusty Harold a écrit : > On Sun, Oct 18, 2020 at 12:57 PM Hervé BOUTEMY wrote: > > +1 > > > > sadly, I could not reproduce the build: the reference was done with JDK 15 > > on Windows, and it seems my -Dline.separator=$'\r\n' workaround to inject > > Windows newline to my Linux environment does not work any more... > That's unfortunate. Should we start requiring reference builds to be > done on Linux? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: How does maven-site publishing work?
Hi Michael, I did the majority of the setup. Seen by infra, our site is using svnpubsub, which is the key for us to publish 100 independant component sites without checkout out the whole aggregated site. (no, gitpubsub is not the best option in our case) We basically use maven-site-plugin to generate html, then commit it to svn (for svnpubsub) with maven-scm-publish-plugin: you can for example publish maven-site with "mvn site-deploy" from your machine, same for every component documentation. Next step is CI integration, to avoid requiring everybody to build maven-site on his machine: infra provides a Jenkins agent for that, see our job [1] The last step for easy use is to provide the "edit" icon in the skin's breadcrumb like added a few years ago [2] More details can be found at [3]. But the setup is not that complex: it's just maven-site, svnpubsub, a normal CI job, and a few ideas to ease navigation Don't hesitate to ping me and tell me where to involve if I can be of any help. Regards, Hervé [1] https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-site/job/ master/ [2] https://maven.apache.org/ [3] https://maven.apache.org/developers/website/index.html Le lundi 19 octobre 2020, 20:38:38 CEST Michael Osipov a écrit : > Folks, > > we at the HttpComponents TLP we'd like use the same approach as > maven-site does. We'd ilke to automatate as much as possible, means: > push to repo should trigger a a push to the website. I can see that > svnpubub is obviously used in the POM. But the question is, where is the > trigger performing the actual step? Who knows best? > > See discussion [1] > > Thanks, > > Michael > > [1] https://www.mail-archive.com/dev@hc.apache.org/msg27650.html > > - > 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
