[jbosstools-issues] [JBoss JIRA] (JBIDE-13894) 'Tail files...' dialog ignores -n parameter value

[Stefan Bunciak (JIRA)]

Stefan Bunciak created JBIDE-13894:
--------------------------------------

             Summary: 'Tail files...' dialog ignores -n parameter value
                 Key: JBIDE-13894
                 URL: https://issues.jboss.org/browse/JBIDE-13894
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: openshift
    Affects Versions: 4.0.x
            Reporter: Stefan Bunciak
            Assignee: Andre Dietisheim
            Priority: Critical
             Fix For: 4.1.0.Beta1
         Attachments: tail1.png

I set -n parameter to 3:

!tail1.png|thumbnail!

but the console output contains much more lines right away:

{code}
Loading....
==> jbosseap-6.0/logs/server.log <==
2013/04/02 07:57:42,044 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment ROOT.war
2013/04/02 07:57:44,331 INFO  [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: 
2013/04/02 07:57:48,743 INFO  [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /jboss-as-helloworld-errai
2013/04/02 07:57:48,933 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "jboss-as-helloworld-errai.war"
2013/04/02 07:57:48,934 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "ROOT.war"
2013/04/02 07:57:49,138 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.9.25.129:9990/management
2013/04/02 07:57:49,141 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.9.25.129:9990
2013/04/02 07:57:49,141 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 67688ms - Started 319 of 462 services (140 services are passive or on-demand)
2013/04/02 08:03:58,941 INFO  [org.jboss.resteasy.cdi.CdiInjectorFactory] (http-127.9.25.129/127.9.25.129:8080-4) Found BeanManager at java:comp/BeanManager
2013/04/02 08:03:59,130 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (http-127.9.25.129/127.9.25.129:8080-4) Deploying javax.ws.rs.core.Application: class org.jboss.tools.example.html5.rest.JaxRsActivator$Proxy$_$$_WeldClientProxy

==> jbosseap-6.0/logs/boot.log <==
	user.name = 515ac573e0b8cd1da6000005
	user.timezone = America/New_York
07:56:45,930 DEBUG [org.jboss.as.config] VM Arguments: -D[Standalone] -XX:+TieredCompilation -Xmx256m -XX:MaxPermSize=102m -XX:+AggressiveOpts -Dorg.apache.tomcat.util.LOW_MEMORY=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djboss.node.name=binary-pipistiks.rhcloud.com -Djgroups.bind_addr=127.9.25.129 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.jboss.boot.log.file=/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/configuration/logging.properties 
07:56:56,854 WARN  [org.jboss.as.server] JBAS015883: No security realm defined for native management service; all access will be unrestricted.
07:56:56,853 INFO  [org.xnio] XNIO Version 3.0.7.GA-redhat-1
07:56:57,037 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
07:56:57,038 WARN  [org.jboss.as.server] JBAS015884: No security realm defined for http management service; all access will be unrestricted.
07:56:56,959 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
07:56:57,148 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
07:56:57,938 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
{code}

I would expect the same behaviour like on linux system - to output just the specified 3 lines...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira