[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039701#comment-14039701
]
Ralph Goers commented on LOG4J2-461:
Is there a link to the enhancement request that y
[
https://issues.apache.org/jira/browse/LOG4J2-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-622.
Resolution: Fixed
Fix Version/s: 2.0-rc2
Fixed in revision 1604312.
Please verify and close
[
https://issues.apache.org/jira/browse/LOG4J2-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-674.
Resolution: Fixed
Fixed in revision 1604312.
> Make RollingFile buffer size configurable
> ---
Remko Popma created LOG4J2-674:
--
Summary: Make RollingFile buffer size configurable
Key: LOG4J2-674
URL: https://issues.apache.org/jira/browse/LOG4J2-674
Project: Log4j 2
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LOG4J2-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-141.
--
Nice catch, thank you!
Fixed in revision 1604303.
> Documentation is lacking info about valid status level
I'd like to try this, so I'm looking forward to such a wiki page!
Ralph, we could add "Vagrant*" to the excludes in the assembly. That would make
sense to me as we're already excluding IDE files like .project etc there. I do
agree that a wiki page would be a better "home" for this file, again s
Probably a combination of both.
On 19 June 2014 22:43, Ralph Goers wrote:
> Either our the checkstyle rules must not match the IDE rules as we have
> hundreds of checkstyle errors in the reports.
>
> Ralph
> -
> To unsubscribe,
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039345#comment-14039345
]
Matt Sicker commented on LOG4J2-673:
I do object to using the shade plugin as it's lik
[
https://issues.apache.org/jira/browse/LOG4J2-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039251#comment-14039251
]
Joern Huxhorn commented on LOG4J2-141:
--
The "is one of the first things tools availab
[
https://issues.apache.org/jira/browse/LOG4J2-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-340.
--
Resolution: Fixed
Fix Version/s: 2.0-beta9
Closing per user
> Is there a replacement for DomCon
And for other VMs, well, there'd have to be different configurations.
There's a way to configure multiple VMs in a single Vagrantfile (e.g., for
making a cluster of VMs), so I'll take a look into that as well.
On 20 June 2014 12:29, Matt Sicker wrote:
> It's in the root directory (i.e., /vagran
It's in the root directory (i.e., /vagrant, next to /var, /home, /etc).
It's easiest to set up in the root of your project because it automatically
shares that directory in the VM. Otherwise, you need to add more shared
directories and such.
So yes, if you navigate to /vagrant (not /home/vagrant),
I should also add that the wiki is the perfect place for this because you can
also document how to install vagrant and virtualbox as well as how to start,
stop and use the VM.
Ralph
On Jun 20, 2014, at 9:51 AM, Ralph Goers wrote:
> OK, so this builds an ubuntu VM. What if I want a Windows VM,
So I installed vagrant and virtual box. After doing the ssh I get a command
prompt. I’m in /home/vagrant, which has nothing in it. If it had the source
for log4j as its root directory I could understand why the file needs to be in
svn. As it stands I really think it belongs on the wiki.
Ralph
OK, so this builds an ubuntu VM. What if I want a Windows VM, or a CentOS or
Redhat VM? I am just having a problem understanding why this file would be in
the root of the project. I could understand if we had a tools sub-project or
something outside of the project. I just don’t know why this w
It's a quick and easy way for any developer to get up and running with a VM
for testing. You just run "vagrant up", then "vagrant ssh", then everything
from the project is available in the /vagrant directory in the VM. You can
compile, run tests, etc.
On 20 June 2014 09:23, Ralph Goers wrote:
>
I don't really understand. I use VMware fusion and don't need this file. Now
matter what OS I want. Why does it need to be part of the project?
Ralph
> On Jun 20, 2014, at 6:48 AM, Matt Sicker wrote:
>
> I added that. See
> http://www.vagrantup.com/
>
> It's for creating a Linux VM to test
[
https://issues.apache.org/jira/browse/LOG4J2-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038825#comment-14038825
]
Remko Popma edited comment on LOG4J2-141 at 6/20/14 2:15 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-141:
---
Fix Version/s: (was: 2.0-rc1)
> Documentation is lacking info about valid status levels
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-141.
Resolution: Fixed
Fix Version/s: 2.0-rc1
2.0-rc2
Fixed in revision 160417
[
https://issues.apache.org/jira/browse/LOG4J2-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038806#comment-14038806
]
Kurt Lehrke commented on LOG4J2-340:
Yes. Thanks.
> Is there a replacement for DomCon
It was for using the Travis CI system on GitHub, but it doesn't really
work. It can be removed.
On 19 June 2014 23:01, Ralph Goers wrote:
> What is .travis.yml checked in to the root of trunk? It doesn’t have an
> Apache license header so shows up in the RAT report which is grounds for
> faili
I added that. See
http://www.vagrantup.com/
It's for creating a Linux VM to test log4j in since we all use Windows or
Mac.
On 19 June 2014 22:58, Ralph Goers wrote:
> What is the file “Vagrantfile” checked in to the root of trunk for? Was
> it committed by accident?
>
> Ralph
> --
[
https://issues.apache.org/jira/browse/LOG4J2-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038766#comment-14038766
]
Remko Popma commented on LOG4J2-441:
It would be whatever level is most strict. So, fa
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: 0002-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch
> plugin preloading f
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: (was:
0001-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch)
> plugin
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: 0001-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch
> plugin preloading f
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: (was:
0001-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch)
> plugin
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038690#comment-14038690
]
Mck SembWever edited comment on LOG4J2-673 at 6/20/14 11:23 AM:
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: (was:
0001-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch)
> plugin
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: 0001-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch
New patch.
- uses C
[
https://issues.apache.org/jira/browse/LOG4J2-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038679#comment-14038679
]
Jan Winter commented on LOG4J2-441:
---
As I know is this issue affected to beta4 version.
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038592#comment-14038592
]
Mck SembWever commented on LOG4J2-673:
--
[~jvz] the point is that there are now multip
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038586#comment-14038586
]
Mck SembWever commented on LOG4J2-673:
--
[~ralph.go...@dslextreme.com]
{noformat}
gi
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038581#comment-14038581
]
Mck SembWever commented on LOG4J2-673:
--
[~ralph.go...@dslextreme.com] tests don't wor
35 matches
Mail list logo
