[jira] [Updated] (MNGSITE-262) Add book under 'Books and Resources'
[ https://issues.apache.org/jira/browse/MNGSITE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zico Fernandes updated MNGSITE-262: --- Issue Type: Task (was: Wish) > Add book under 'Books and Resources' > > > Key: MNGSITE-262 > URL: https://issues.apache.org/jira/browse/MNGSITE-262 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Zico Fernandes > Attachments: 6124OS_Apache Maven Cookbook.jpg > > > Apache Maven Cookbook > Covers: Maven 3 > Published: Packt Publishing (August 2015) > Authors: Raghuram Bharathan > Buy the Book: Packt, Amazon -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
[
https://issues.apache.org/jira/browse/MCHANGES-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973539#comment-14973539
]
ASF GitHub Bot commented on MCHANGES-361:
-
Github user dadoonet closed the pull request at:
https://github.com/apache/maven-plugins/pull/66
> GitHub issue ids don't appear in announcement.vm
>
>
> Key: MCHANGES-361
> URL: https://issues.apache.org/jira/browse/MCHANGES-361
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: github
>Affects Versions: 2.11
>Reporter: David Pilato
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Fix For: 2.12
>
>
> When you generate a github announcement velocity file with default
> configuration for {{announcement.vm}}, you get:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade
> Changes:
> o Update to beyonder 2.0.0
> o Update to elasticsearch 2.0.0
> {noformat}
> As links and github ids exist, it should be:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade Issue: 74.
> Changes:
> o Update to beyonder 2.0.0 Issue: 76.
> o Update to elasticsearch 2.0.0 Issue: 73.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
[
https://issues.apache.org/jira/browse/MCHANGES-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MCHANGES-361.
---
Resolution: Fixed
Applied.
Thanks buddy!!
> GitHub issue ids don't appear in announcement.vm
>
>
> Key: MCHANGES-361
> URL: https://issues.apache.org/jira/browse/MCHANGES-361
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: github
>Affects Versions: 2.11
>Reporter: David Pilato
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Fix For: 2.12
>
>
> When you generate a github announcement velocity file with default
> configuration for {{announcement.vm}}, you get:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade
> Changes:
> o Update to beyonder 2.0.0
> o Update to elasticsearch 2.0.0
> {noformat}
> As links and github ids exist, it should be:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade Issue: 74.
> Changes:
> o Update to beyonder 2.0.0 Issue: 76.
> o Update to elasticsearch 2.0.0 Issue: 73.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
[
https://issues.apache.org/jira/browse/MCHANGES-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) updated MCHANGES-361:
Fix Version/s: 2.12
> GitHub issue ids don't appear in announcement.vm
>
>
> Key: MCHANGES-361
> URL: https://issues.apache.org/jira/browse/MCHANGES-361
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: github
>Affects Versions: 2.11
>Reporter: David Pilato
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Fix For: 2.12
>
>
> When you generate a github announcement velocity file with default
> configuration for {{announcement.vm}}, you get:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade
> Changes:
> o Update to beyonder 2.0.0
> o Update to elasticsearch 2.0.0
> {noformat}
> As links and github ids exist, it should be:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade Issue: 74.
> Changes:
> o Update to beyonder 2.0.0 Issue: 76.
> o Update to elasticsearch 2.0.0 Issue: 73.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
[
https://issues.apache.org/jira/browse/MCHANGES-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) reassigned MCHANGES-361:
---
Assignee: Olivier Lamy (*$^¨%`£)
> GitHub issue ids don't appear in announcement.vm
>
>
> Key: MCHANGES-361
> URL: https://issues.apache.org/jira/browse/MCHANGES-361
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: github
>Affects Versions: 2.11
>Reporter: David Pilato
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
>
> When you generate a github announcement velocity file with default
> configuration for {{announcement.vm}}, you get:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade
> Changes:
> o Update to beyonder 2.0.0
> o Update to elasticsearch 2.0.0
> {noformat}
> As links and github ids exist, it should be:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade Issue: 74.
> Changes:
> o Update to beyonder 2.0.0 Issue: 76.
> o Update to elasticsearch 2.0.0 Issue: 73.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1189) Prevent from I/O leakage. Thus close streams in finally block.
[ https://issues.apache.org/jira/browse/SUREFIRE-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1189: --- Summary: Prevent from I/O leakage. Thus close streams in finally block. (was: Prevent from I/O leaked and close streams in finally block) > Prevent from I/O leakage. Thus close streams in finally block. > -- > > Key: SUREFIRE-1189 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1189 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, JUnit 3.x support, Junit 4.7+ (parallel) > support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, > Maven Surefire Report Plugin, process forking, TestNG support, xml generation >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.1 > > > On Sun, Oct 25, 2015 at 11:49 AM, Kristian Rosenvold-4 [via Maven] > wrote: > Based on code review I found a large number of close-statements that > were not in the mandated finally blocks, which would create resource > leakage on kill. > I fixed this in bb99b232da0e93f2772be6945a410ea9ba666c4f, hope this > will help the situation on windows. > Kristian -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1189) Prevent from I/O leaked and close streams in finally block
[ https://issues.apache.org/jira/browse/SUREFIRE-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1189: --- Description: On Sun, Oct 25, 2015 at 11:49 AM, Kristian Rosenvold-4 [via Maven] wrote: Based on code review I found a large number of close-statements that were not in the mandated finally blocks, which would create resource leakage on kill. I fixed this in bb99b232da0e93f2772be6945a410ea9ba666c4f, hope this will help the situation on windows. Kristian > Prevent from I/O leaked and close streams in finally block > -- > > Key: SUREFIRE-1189 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1189 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, JUnit 3.x support, Junit 4.7+ (parallel) > support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, > Maven Surefire Report Plugin, process forking, TestNG support, xml generation >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.1 > > > On Sun, Oct 25, 2015 at 11:49 AM, Kristian Rosenvold-4 [via Maven] > wrote: > Based on code review I found a large number of close-statements that > were not in the mandated finally blocks, which would create resource > leakage on kill. > I fixed this in bb99b232da0e93f2772be6945a410ea9ba666c4f, hope this > will help the situation on windows. > Kristian -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1189) Prevent from I/O leaked and close streams in finally block
Tibor Digana created SUREFIRE-1189: -- Summary: Prevent from I/O leaked and close streams in finally block Key: SUREFIRE-1189 URL: https://issues.apache.org/jira/browse/SUREFIRE-1189 Project: Maven Surefire Issue Type: Bug Components: classloading, JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, Maven Surefire Report Plugin, process forking, TestNG support, xml generation Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1189) Prevent from I/O leaked and close streams in finally block
[ https://issues.apache.org/jira/browse/SUREFIRE-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1189. -- Resolution: Fixed commit bb99b232da0e93f2772be6945a410ea9ba666c4f > Prevent from I/O leaked and close streams in finally block > -- > > Key: SUREFIRE-1189 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1189 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, JUnit 3.x support, Junit 4.7+ (parallel) > support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, > Maven Surefire Report Plugin, process forking, TestNG support, xml generation >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
[
https://issues.apache.org/jira/browse/MCHANGES-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973403#comment-14973403
]
ASF GitHub Bot commented on MCHANGES-361:
-
GitHub user dadoonet opened a pull request:
https://github.com/apache/maven-plugins/pull/66
GitHub issue ids don't appear in announcement.vm
Fix for [MCHANGES-361](https://issues.apache.org/jira/browse/MCHANGES-361)
When you generate a github announcement velocity file with default
configuration for `announcement.vm`, you get:
```
Fixed Bugs:
o Async initialization of Node and Client are broken after Elasticsearch 2
upgrade
Changes:
o Update to beyonder 2.0.0
o Update to elasticsearch 2.0.0
```
As links and github ids exist, it should be:
```
Fixed Bugs:
o Async initialization of Node and Client are broken after Elasticsearch 2
upgrade Issue: 74.
Changes:
o Update to beyonder 2.0.0 Issue: 76.
o Update to elasticsearch 2.0.0 Issue: 73.
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dadoonet/maven-plugins MCHANGES-361
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-plugins/pull/66.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 #66
commit 7ebad7cb2a09948039bde2c12056fcd5f6472a38
Author: David Pilato
Date: 2015-10-25T19:34:49Z
GitHub issue ids don't appear in announcement.vm
Fix for [MCHANGES-361](https://issues.apache.org/jira/browse/MCHANGES-361)
When you generate a github announcement velocity file with default
configuration for `announcement.vm`, you get:
```
Fixed Bugs:
o Async initialization of Node and Client are broken after Elasticsearch 2
upgrade
Changes:
o Update to beyonder 2.0.0
o Update to elasticsearch 2.0.0
```
As links and github ids exist, it should be:
```
Fixed Bugs:
o Async initialization of Node and Client are broken after Elasticsearch 2
upgrade Issue: 74.
Changes:
o Update to beyonder 2.0.0 Issue: 76.
o Update to elasticsearch 2.0.0 Issue: 73.
```
> GitHub issue ids don't appear in announcement.vm
>
>
> Key: MCHANGES-361
> URL: https://issues.apache.org/jira/browse/MCHANGES-361
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: github
>Affects Versions: 2.11
>Reporter: David Pilato
>Priority: Minor
>
> When you generate a github announcement velocity file with default
> configuration for {{announcement.vm}}, you get:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade
> Changes:
> o Update to beyonder 2.0.0
> o Update to elasticsearch 2.0.0
> {noformat}
> As links and github ids exist, it should be:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade Issue: 74.
> Changes:
> o Update to beyonder 2.0.0 Issue: 76.
> o Update to elasticsearch 2.0.0 Issue: 73.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
[
https://issues.apache.org/jira/browse/MCHANGES-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Pilato updated MCHANGES-361:
--
Flags: Patch
External issue URL: https://github.com/apache/maven-plugins/pull/66
> GitHub issue ids don't appear in announcement.vm
>
>
> Key: MCHANGES-361
> URL: https://issues.apache.org/jira/browse/MCHANGES-361
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: github
>Affects Versions: 2.11
>Reporter: David Pilato
>Priority: Minor
>
> When you generate a github announcement velocity file with default
> configuration for {{announcement.vm}}, you get:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade
> Changes:
> o Update to beyonder 2.0.0
> o Update to elasticsearch 2.0.0
> {noformat}
> As links and github ids exist, it should be:
> {noformat}
> Fixed Bugs:
> o Async initialization of Node and Client are broken after Elasticsearch 2
> upgrade Issue: 74.
> Changes:
> o Update to beyonder 2.0.0 Issue: 76.
> o Update to elasticsearch 2.0.0 Issue: 73.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MCHANGES-361) GitHub issue ids don't appear in announcement.vm
David Pilato created MCHANGES-361:
-
Summary: GitHub issue ids don't appear in announcement.vm
Key: MCHANGES-361
URL: https://issues.apache.org/jira/browse/MCHANGES-361
Project: Maven Changes Plugin
Issue Type: Bug
Components: github
Affects Versions: 2.11
Reporter: David Pilato
Priority: Minor
When you generate a github announcement velocity file with default
configuration for {{announcement.vm}}, you get:
{noformat}
Fixed Bugs:
o Async initialization of Node and Client are broken after Elasticsearch 2
upgrade
Changes:
o Update to beyonder 2.0.0
o Update to elasticsearch 2.0.0
{noformat}
As links and github ids exist, it should be:
{noformat}
Fixed Bugs:
o Async initialization of Node and Client are broken after Elasticsearch 2
upgrade Issue: 74.
Changes:
o Update to beyonder 2.0.0 Issue: 76.
o Update to elasticsearch 2.0.0 Issue: 73.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5916) Regression from 3.0: Allow filtering out certain loggers from within a plugin
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973400#comment-14973400 ] Axel Fontaine commented on MNG-5916: You can define regression how you want, but fact is it was working (and very useful) with Maven 3.0 and it isn't anymore now. I am open for any alternative solutions to this problem, including shipping better defaults for the http client wire logger (always off) as suggested above and implemented by Gradle. > Regression from 3.0: Allow filtering out certain loggers from within a plugin > - > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Regression from 3.0: Allow filtering out certain loggers from within a plugin
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973399#comment-14973399 ] Axel Fontaine commented on MNG-5916: The main thing I want have turned off here is the wire logger of the HTTP client. My point isn't that this should affect the entire build, but that there should be a mechanism of doing this on a plugin by plugin base if necessary. This was possible before and this should probably be doable as each plugin already has some level of isolation by having its own classloader. I would be happy with any solution that re-enables what was available with 3.0. P.S.: The wire logger makes very little sense and Gradle for example has it set to off by default. Would shipping Maven with it off by default be possible? > Regression from 3.0: Allow filtering out certain loggers from within a plugin > - > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Regression from 3.0: Allow filtering out certain loggers from within a plugin
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973398#comment-14973398 ] Michael Osipov commented on MNG-5916: - This is neither a regression, imho. Your usecase was never supported but was simply possible as a matter of fact. One can correct me if I am wrong. > Regression from 3.0: Allow filtering out certain loggers from within a plugin > - > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Regression from 3.0: Allow filtering out certain loggers from within a plugin
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973397#comment-14973397 ] Michael Osipov commented on MNG-5916: - Shutting off HTTP client means shutting it off for the entire build. Wagon would be affacted. Is that your intention actually? > Regression from 3.0: Allow filtering out certain loggers from within a plugin > - > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-5916) Regression from 3.0: Allow filtering out certain loggers from within a plugin
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Axel Fontaine updated MNG-5916: --- Summary: Regression from 3.0: Allow filtering out certain loggers from within a plugin (was: Replace slf4j-simple with logback or allow filtering out certain loggers) > Regression from 3.0: Allow filtering out certain loggers from within a plugin > - > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973390#comment-14973390 ] Axel Fontaine edited comment on MNG-5916 at 10/25/15 7:14 PM: -- While you may be correct in theory, in practice this is couldn't be further from the truth. As a plugin writer, the output of the plugin is a very important part of the UI. To ensure an optimal user experience it is important to think carefully about what should be output at which logging level by the plugin. The exact set of libraries a plugin uses should not be of concern to users of the plugin. And they certainly shouldn't all have to perform some manual configuration to ensure proper output. As THAT would be a fundamental misconception of UX and a very leaky abstraction. I don't have code for this for 3.1+ as filtering logging output is not possible anymore. was (Author: axel.fontaine): While you may be correct in theory, in practice this is couldn't be further from the truth. As a plugin writer, the output of the plugin is a very important part of the UI. To ensure an optimal user experience it is important to think carefully about what should be output at which logging level by the plugin. The exact set of libraries a plugin uses should not be of concern to users of the plugin. And they certainly shouldn't all have to perform some manual configuration to ensure proper output. As THAT would be a fundamental misconception of UX and a very leaky abstraction. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973396#comment-14973396 ] Axel Fontaine commented on MNG-5916: Well it is a functional regression compared to 3.0. For me that qualifies as a bug. Maybe just the second part of the title would capture the issue better and be less prescriptive of a possible solution: Allow filtering out certain loggers from within a plugin > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973393#comment-14973393 ] Michael Osipov commented on MNG-5916: - I second this one. At least the title is misleading and this is not a bug but at most a improvement request. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973390#comment-14973390 ] Axel Fontaine commented on MNG-5916: While you may be correct in theory, in practice this is couldn't be further from the truth. As a plugin writer, the output of the plugin is a very important part of the UI. To ensure an optimal user experience it is important to think carefully about what should be output at which logging level by the plugin. The exact set of libraries a plugin uses should not be of concern to users of the plugin. And they certainly shouldn't all have to perform some manual configuration to ensure proper output. As THAT would be a fundamental misconception of UX and a very leaky abstraction. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973385#comment-14973385 ] Michael Osipov commented on MNG-5916: - You approach has a fundemantal misconception. You are imposing logging configuration to the client. It is up to the client to configure logging. I wrote [this|http://stackoverflow.com/a/7107934/696632] already on SO. How does your code look now with 3.1+? > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MCHANGES-360) Add support for issues with more than one label
[
https://issues.apache.org/jira/browse/MCHANGES-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Pilato updated MCHANGES-360:
--
Description:
If your github issues have more than one label, the announcement.vm file is not
generated correctly.
For example, I added to an issue labels:
* 2.0.0
* update
When I generate the report, the report is empty.
If I remove 2.0.0, the report is correct.
This issue is caused by this:
https://github.com/apache/maven-plugins/blob/trunk/maven-changes-plugin/src/main/java/org/apache/maven/plugin/github/GitHubDownloader.java#L169-L173
We extract here only the first label.
{code:title=GitHubDownloader.java}
List labels = githubIssue.getLabels();
if ( labels != null && !labels.isEmpty() )
{
issue.setType( labels.get( 0 ).getName() );
}
{code}
was:
If your github issues have more than one label, the announcement.vm file is not
generated correctly.
For example, I added to an issue labels:
* 2.0.0
* update
When I generate the report, the report is empty.
If I remove 2.0.0, the report is correct.
> Add support for issues with more than one label
> ---
>
> Key: MCHANGES-360
> URL: https://issues.apache.org/jira/browse/MCHANGES-360
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.11
>Reporter: David Pilato
>Priority: Trivial
>
> If your github issues have more than one label, the announcement.vm file is
> not generated correctly.
> For example, I added to an issue labels:
> * 2.0.0
> * update
> When I generate the report, the report is empty.
> If I remove 2.0.0, the report is correct.
> This issue is caused by this:
> https://github.com/apache/maven-plugins/blob/trunk/maven-changes-plugin/src/main/java/org/apache/maven/plugin/github/GitHubDownloader.java#L169-L173
> We extract here only the first label.
> {code:title=GitHubDownloader.java}
> List labels = githubIssue.getLabels();
> if ( labels != null && !labels.isEmpty() )
> {
>issue.setType( labels.get( 0 ).getName() );
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[
https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973340#comment-14973340
]
Axel Fontaine commented on MNG-5916:
[~afloom] Up until 3.0 we were using a log4j appender like this:
import org.apache.log4j.AppenderSkeleton;
import org.apache.log4j.Level;
import org.apache.log4j.Logger;
import org.apache.log4j.spi.LoggingEvent;
import org.apache.maven.plugin.logging.Log;
/**
* Log4J appender that writes to the Maven log.
*/
public class MavenLogAppender extends AppenderSkeleton {
private static Log log;
public static void init(Log mavenLog) {
log = mavenLog;
if (log.isDebugEnabled()) {
Logger.getRootLogger().setLevel(Level.DEBUG);
}
}
@Override
protected void append(LoggingEvent event) {
Level level = event.getLevel();
String message = event.getRenderedMessage();
@SuppressWarnings("ThrowableResultOfMethodCallIgnored") Throwable
throwable =
event.getThrowableInformation() == null ? null :
event.getThrowableInformation().getThrowable();
if (event.getLogger().getEffectiveLevel().isGreaterOrEqual(level)) {
if (level == Level.DEBUG) {
if (throwable == null) {
log.debug(message);
} else {
log.debug(message, throwable);
}
} else if (level == Level.INFO) {
if (throwable == null) {
log.info(message);
} else {
log.info(message, throwable);
}
} else if (level == Level.WARN) {
if (throwable == null) {
log.warn(message);
} else {
log.warn(message, throwable);
}
} else if ((level == Level.ERROR) || (level == Level.FATAL)) {
if (throwable == null) {
log.error(message);
} else {
log.error(message, throwable);
}
}
}
}
@Override
public void close() {
}
@Override
public boolean requiresLayout() {
return false;
}
}
This allowed us to ship a log4j.xml file as part of our plugin jar that
suppressed the output of the HTTP Client wire log:
We then binded everything together in the mojo with a non-static initializer:
public class MyMojo extends AbstractMojo {
{
MavenLogAppender.init(getLog());
}
...
}
This is not possible anymore since 3.1 due to the logging changes.
[~michael-o] This is not intuitive compared to -X and having everything work as
expected. We cannot expect all our users to have to manually copy a logback.xml
file and invoke maven with special arguments whenever they want to see debug
output.
> Replace slf4j-simple with logback or allow filtering out certain loggers
>
>
> Key: MNG-5916
> URL: https://issues.apache.org/jira/browse/MNG-5916
> Project: Maven
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.3.3
>Reporter: Axel Fontaine
>
> We are developing a Maven plugin that uses Apache HTTP client. When switching
> Maven to debug mode with -X Apache HTTP client produces gazillions of output
> messages as all wire traffic is being logged. It is not only annoying, it
> also makes this unusable in systems like Travis CI that limit output to some
> sane amount..
> We need some way of disabling the output of the org.apache.http.wire log from
> our within our plugin jar. (Patching existing Maven installations is not an
> option as we do not have this kind of control over our user's machines).
> Any help/suggestions/solutions welcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[
https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973334#comment-14973334
]
Michael Osipov commented on MNG-5916:
-
What about setting {{maven.ext.class.path}} and put a directory with
{{logback.xml}}?
> Replace slf4j-simple with logback or allow filtering out certain loggers
>
>
> Key: MNG-5916
> URL: https://issues.apache.org/jira/browse/MNG-5916
> Project: Maven
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.3.3
>Reporter: Axel Fontaine
>
> We are developing a Maven plugin that uses Apache HTTP client. When switching
> Maven to debug mode with -X Apache HTTP client produces gazillions of output
> messages as all wire traffic is being logged. It is not only annoying, it
> also makes this unusable in systems like Travis CI that limit output to some
> sane amount..
> We need some way of disabling the output of the org.apache.http.wire log from
> our within our plugin jar. (Patching existing Maven installations is not an
> option as we do not have this kind of control over our user's machines).
> Any help/suggestions/solutions welcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MCHANGES-316) GitHub report doesn't find any issues
[ https://issues.apache.org/jira/browse/MCHANGES-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973327#comment-14973327 ] David Pilato edited comment on MCHANGES-316 at 10/25/15 4:55 PM: - I hit a similar issue recently. It was caused by the fact I was using more than one label per issue. I think this is a bug IMO. As soon as the issue contains one of the expected labels, the issue should be used to generate the report whatever other labels. Hope this helps. I thInk it's a different issue though so I created MCHANGES-360 was (Author: dadoonet): I hit a similar issue recently. It was caused by the fact I was using more than one label per issue. I think this is a bug IMO. As soon as the issue contains one of the expected labels, the issue should be used to generate the report whatever other labels. Hope this helps. > GitHub report doesn't find any issues > - > > Key: MCHANGES-316 > URL: https://issues.apache.org/jira/browse/MCHANGES-316 > Project: Maven Changes Plugin > Issue Type: Bug > Components: github >Affects Versions: 2.9 >Reporter: John Schneider > Attachments: MavenChangeGitHubRun.txt > > > When I try to generate a GitHub report I get that message: > [WARNING] No issue was matched. > I tried to debug this and could pin down the problem to the following request: > https://api.github.com/repos/jschneider/com.cedarsoft.open/issues?per_page=100&page=1 > This request does return an empty result set. Because per default only open > issues are returned. > To get the closed issues it is necessary to add "state=closed" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCHANGES-360) Add support for issues with more than one label
David Pilato created MCHANGES-360: - Summary: Add support for issues with more than one label Key: MCHANGES-360 URL: https://issues.apache.org/jira/browse/MCHANGES-360 Project: Maven Changes Plugin Issue Type: Bug Components: announcement Affects Versions: 2.11 Reporter: David Pilato Priority: Trivial If your github issues have more than one label, the announcement.vm file is not generated correctly. For example, I added to an issue labels: * 2.0.0 * update When I generate the report, the report is empty. If I remove 2.0.0, the report is correct. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MCHANGES-316) GitHub report doesn't find any issues
[ https://issues.apache.org/jira/browse/MCHANGES-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973327#comment-14973327 ] David Pilato edited comment on MCHANGES-316 at 10/25/15 4:51 PM: - I hit a similar issue recently. It was caused by the fact I was using more than one label per issue. I think this is a bug IMO. As soon as the issue contains one of the expected labels, the issue should be used to generate the report whatever other labels. Hope this helps. was (Author: dadoonet): I hit a similar issue recently. It was caused by the fact I was using more than one label per issue. I think this is a bug IMO. As soon as the issue contains one of the expected labels, the issue should be used to generate the report whatever other labels. Hope this helps. I'm +1 to reopen this issue. > GitHub report doesn't find any issues > - > > Key: MCHANGES-316 > URL: https://issues.apache.org/jira/browse/MCHANGES-316 > Project: Maven Changes Plugin > Issue Type: Bug > Components: github >Affects Versions: 2.9 >Reporter: John Schneider > Attachments: MavenChangeGitHubRun.txt > > > When I try to generate a GitHub report I get that message: > [WARNING] No issue was matched. > I tried to debug this and could pin down the problem to the following request: > https://api.github.com/repos/jschneider/com.cedarsoft.open/issues?per_page=100&page=1 > This request does return an empty result set. Because per default only open > issues are returned. > To get the closed issues it is necessary to add "state=closed" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-316) GitHub report doesn't find any issues
[ https://issues.apache.org/jira/browse/MCHANGES-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973327#comment-14973327 ] David Pilato commented on MCHANGES-316: --- I hit a similar issue recently. It was caused by the fact I was using more than one label per issue. I think this is a bug IMO. As soon as the issue contains one of the expected labels, the issue should be used to generate the report whatever other labels. Hope this helps. I'm +1 to reopen this issue. > GitHub report doesn't find any issues > - > > Key: MCHANGES-316 > URL: https://issues.apache.org/jira/browse/MCHANGES-316 > Project: Maven Changes Plugin > Issue Type: Bug > Components: github >Affects Versions: 2.9 >Reporter: John Schneider > Attachments: MavenChangeGitHubRun.txt > > > When I try to generate a GitHub report I get that message: > [WARNING] No issue was matched. > I tried to debug this and could pin down the problem to the following request: > https://api.github.com/repos/jschneider/com.cedarsoft.open/issues?per_page=100&page=1 > This request does return an empty result set. Because per default only open > issues are returned. > To get the closed issues it is necessary to add "state=closed" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973229#comment-14973229 ] Anders Hammar commented on MNG-5916: [~axel.fontaine]Could you please attach a project or similar for us to reproduce the issue? You're probably aware of it but just to be clear, the logging was changed in v3.1 of Maven core and what you're experiencing is likely due to this. Also, possibly the issue should be changed to an improvement based on the wording in the title. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973156#comment-14973156 ] Axel Fontaine commented on MNG-5916: I believe you didn't read my description properly. This is not a request for help. It is a bug/regression compared to Maven 3.0.x where I could influence this by filtering logging output via a custom log4j/logback appender to the Maven log. This is not possible anymore and a real issue for us. I HAVE read the Maven guide guide thoroughly and it does NOT provide a solution, since filtering out certain loggers requires modifying the Maven installation (something we cannot do on our users' machines as I mentioned in the original description) and CANNOT be done from WITHIN a plugin. This also has nothing to do with HTTPCLIENT-1664 as commons logging output can already be easily be redirected to slf4j. My apologies if I wasn't clear enough in my initial description. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973141#comment-14973141 ] Michael Osipov edited comment on MNG-5916 at 10/25/15 8:57 AM: --- This is not a bug you are experiencing, you are seeking for help. This is best done on the mailing list or stackoverflow. Please read [this|https://maven.apache.org/maven-logging.html] guide on logging. It will do exactly what you want. To make it even easier, you might want to vote/comment on HTTPCLIENT-1664. was (Author: michael-o): This is not a bug you are experiencing, you are seeking for help. This is best done on the mailing list or stackoverflow. Please [this|https://maven.apache.org/maven-logging.html] guide on logging. It will do exactly what you want. To make it even easier, you might want to vote/comment on HTTPCLIENT-1664. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973141#comment-14973141 ] Michael Osipov edited comment on MNG-5916 at 10/25/15 8:52 AM: --- This is not a bug you are experiencing, you are seeking for help. This is best done on the mailing list or stackoverflow. Please [this|https://maven.apache.org/maven-logging.html] guide on logging. It will do exactly what you want. To make it even easier, you might want to vote/comment on HTTPCLIENT-1664. was (Author: michael-o): This is not a bug you are experiencing, you are seeking for help. This is best done on the mailing list or stackoverflow. Please [this|https://maven.apache.org/maven-logging.html] guide on logging. It will do exactly what you want. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-5916) Replace slf4j-simple with logback or allow filtering out certain loggers
[ https://issues.apache.org/jira/browse/MNG-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-5916. --- Resolution: Incomplete This is not a bug you are experiencing, you are seeking for help. This is best done on the mailing list or stackoverflow. Please [this|https://maven.apache.org/maven-logging.html] guide on logging. It will do exactly what you want. > Replace slf4j-simple with logback or allow filtering out certain loggers > > > Key: MNG-5916 > URL: https://issues.apache.org/jira/browse/MNG-5916 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.3.3 >Reporter: Axel Fontaine > > We are developing a Maven plugin that uses Apache HTTP client. When switching > Maven to debug mode with -X Apache HTTP client produces gazillions of output > messages as all wire traffic is being logged. It is not only annoying, it > also makes this unusable in systems like Travis CI that limit output to some > sane amount.. > We need some way of disabling the output of the org.apache.http.wire log from > our within our plugin jar. (Patching existing Maven installations is not an > option as we do not have this kind of control over our user's machines). > Any help/suggestions/solutions welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
