[wildfly-dev] Building WildFly 9.0.0.Alpha2-SNAPSHOT

[Stuart Douglas]

The approach that should be taken is the one mentioned by David, about
adding support for a script consumable format that strips spaces to the
logmanager project.

We really don't want to just have some kind of configurable property to
control the delimiter. Putting this in the management model would be
massive overkill, and we don't generally go in for using random system
properties to control behaviour.

Also when this is desirable depends a lot on the logger that is being used.
If may be that the spaces are required for the console output and not
wanted for the file based logger.

Stuart

On Tue, Oct 21, 2014 at 6:10 AM, Sandeep Samdaria <sandyridgeracer at gmail.com
> wrote:

> Hi Jaikiran,
> As you suggested I have picked up a JIRA from the list. I think that I can
> work on this issue WFLY-694 <https://issues.jboss.org/browse/WFLY-694>.(multi-line
> log output makes munging logs difficult).
>
> For the jira description, I found out that
> EjbJndiBindingsDeploymentUnitProcessor.java needs to be changed, which
> lists the JNDI Bindings. The *logBinding* function appends a new line
> character. I believe this hard-coded new line character needs to be
> replaced with a configurable property.
> Please let me know if this approach is correct, so that I can proceed to
> find a suitable solution for the same.
>
> Thanks,
> Sandeep.
>
> P.S. : I had posted the same on IRC, but I guess that my timing was not
> right as not many developers were present at that moment.
>
> On Thu, Oct 16, 2014 at 9:18 AM, Jaikiran Pai <jai.forums2013 at gmail.com>
> wrote:
>
>>  Sandeep,
>>
>> The WFLY JIRA has some issues which have been marked as "Awaiting for
>> volunteers". Here's a link to such unresolved issues
>> https://issues.jboss.org/issues/?jql=fixVersion%20%3D%20%22Awaiting%20Volunteers%22%20AND%20project%20%3D%20WFLY%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC.
>> You can choose from one of them that interests you. You might want to hang
>> around in the #wildfly-dev channel on IRC (irc.freenode.net server)
>> where the WildFly developers can help you in getting started or working on
>> the issue that you pick.
>>
>> -Jaikiran
>>
>> On Tuesday 14 October 2014 06:08 PM, Sandeep Samdaria wrote:
>>
>> Yup, that worked for me. In addition to updating the jdk from u5 to u67,
>> I also had to point JAVA_HOME to the latest.
>>
>>
>>  I wanted to contribute to wildfly project. Any minor/trivial ticket
>> which I can take a look into it as a newbie?
>>
>>  -Sandeep.
>>
>> On Tue, Oct 14, 2014 at 2:47 PM, Tomaž Cerar <tomaz.cerar at gmail.com>
>> wrote:
>>
>>>
>>> On Tue, Oct 14, 2014 at 9:28 AM, Sandeep Samdaria <
>>> sandyridgeracer at gmail.com> wrote:
>>>
>>>> *Java* : version "1.7.0"
>>>> Java(TM) SE Runtime Environment (build 1.7.0-b147)
>>>> Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
>>>>
>>>
>>>
>>>  Not completely sure what is your problem, but it would start with
>>> updating JDK 7 to something more recent.
>>>  you are running u5, while latest is u67
>>>
>>
>>
>>
>> _______________________________________________
>> wildfly-dev mailing listwildfly-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20141021/5f7e9882/attachment.html