OK. I will fix the plugin to deal with this new formatting correctly.
vbk
Carla Mott wrote:
> the new format is intentional. Previously we didn't format the
> messages going to the console with the same formatter as the message
> going to the server log file. As a result, some messages were
> displaying message keys because the resource bundles were not picked
> up correctly.
>
>
> Carla
>
> vince kraemer wrote:
>> It looks like the output from --verbose has changed very recently...
>>
>> With v3 b71 (promoted), the output looks like this...
>>
>> INFO: felix.fileinstall.bundles.new.start true
>> Nov 10, 2009 2:22:53 PM com.sun.grizzly.jruby.rack.JRubyRuntime <init>
>> INFO: New instance of JRuby runtime created in 4,397 milliseconds
>> Nov 10, 2009 2:23:00 PM SEVERE: JRuby limited openssl loaded. gem
>> install jruby-openssl for full support.
>> http://wiki.jruby.org/wiki/JRuby_Builtin_OpenSSL
>> Nov 10, 2009 2:23:01 PM
>> com.sun.grizzly.jruby.rack.RackApplicationPoolFactory
>> getRackApplocationPool
>> SEVERE: Please install the derby adapter: `gem install
>> activerecord-derby-adapter` (Could not find RubyGem jdbc-derby (>= 0)
>> )
>> from
>> /Users/vkraemer/nbhg/web-main/nbbuild/netbeans/ruby2/jruby-1.3.1/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_specification.rb:60:in
>> `establish_connection'
>> from
>> /Users/vkraemer/nbhg/web-main/nbbuild/netbeans/ruby2/jruby-1.3.1/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_specification.rb:55:in
>> `establish_connection'
>> from
>> /Users/vkraemer/nbhg/web-main/nbbuild/netbeans/ruby2/jruby-1.3.1/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/initializer.rb:438:in
>> `initialize_database'
>>
>>
>> In v3 b72 (2009-11-09), the output looks like this...
>>
>> [#|2009-11-10T14:28:21.843-0800|INFO|glassfishv3.0|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=11;_ThreadName=FelixStartLevel;|Security
>> service(s) started successfully....|#]
>>
>> [#|2009-11-10T14:28:22.079-0800|INFO|glassfishv3.0|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=11;_ThreadName=FelixStartLevel;|Created
>> HTTP listener http-listener-1 on port 8080|#]
>>
>> [#|2009-11-10T14:28:22.098-0800|INFO|glassfishv3.0|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=11;_ThreadName=FelixStartLevel;|Created
>> HTTP listener http-listener-2 on port 8181|#]
>>
>> [#|2009-11-10T14:28:22.108-0800|INFO|glassfishv3.0|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=11;_ThreadName=FelixStartLevel;|Created
>> HTTP listener admin-listener on port 4848|#]
>>
>> [#|2009-11-10T14:28:22.151-0800|INFO|glassfishv3.0|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=11;_ThreadName=FelixStartLevel;|Created
>> virtual server server|#]
>>
>>
>> Is this change intentional or is it a side-effect that will be
>> corrected?
>>
>> Note: Either answer is fine with me... but I do need to know the
>> answer, since NB parses the output to do things like message
>> coloring. If the change is intentional, I will fix the plugin so
>> things work again (currently the plugin does not know what to output
>> to the user, so we do not send any of the log data to the output
>> window). If this is something that is considered a bug (and will be
>> fixed before the next promoted build), I won't make any plugin code
>> changes.
>>
>> Thanks,
>> vbk
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>