@EnableDiscoveryClient does not working in traditional deployment

Have application

@SpringBootApplication
@EnableDiscoveryClient
@EnableAutoConfiguration
public class PortalApplication extends SpringBootServletInitializer {

    private static final Logger LOG = LoggerFactory.getLogger(PortalApplication.class);

    @Override
    protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
        LOG.info("Init web app");
        return application.sources(PortalApplication.class);
    }


    public static void main(String[] args) {
        LOG.info("Running app");
        SpringApplication.run(PortalApplication.class, args);
    }

}

When running using gradle bootRun everything works fine and Eureka client initializes properly.
But when I'm try to deploy war into standalone Tomcat server, Eureka client did not initializes.
Tried all the combinations of annotations with no luck.

Gradle config:

buildscript {
    ext {
        springBootVersion = '1.2.4.RELEASE'
    }
    repositories {
        mavenCentral()
        jcenter()
    }
    dependencies {
        classpath("org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}")
        classpath("io.spring.gradle:dependency-management-plugin:0.5.1.RELEASE")
    }
}

apply plugin: 'java'
apply plugin: 'idea'
apply plugin: 'spring-boot'
apply plugin: 'war'
apply plugin: 'io.spring.dependency-management'

springBoot {
    requiresUnpack = ['com.netflix.eureka:eureka-core', 'com.netflix.eureka:eureka-client']
}

jar {
    baseName = 'portal-service'
    version = '0.0.1-SNAPSHOT'
}

war {
    baseName = 'portal-service'
//    version = '0.0.1-SNAPSHOT-' + System.currentTimeMillis();
    version = '0.0.1-SNAPSHOT';
}

sourceCompatibility = 1.8
targetCompatibility = 1.8
group = 'demo'
mainClassName = 'com.demo.portal.PortalApplication'

repositories {
    mavenCentral()
    maven { url "http://repo.spring.io/libs-snapshot" }
}

configurations {
    providedRuntime
}

dependencies {
    compile("org.springframework.boot:spring-boot-starter-web") {
//        exclude module: 'spring-boot-starter-tomcat'
    }
    compile('org.springframework.cloud:spring-cloud-starter-eureka')
    compile('org.springframework.cloud:spring-cloud-starter-eureka-server:1.0.0.RELEASE') {
        exclude(module: 'servlet-api')
    }

    compile("org.springframework.boot:spring-boot-starter-web")
    providedRuntime("org.springframework.boot:spring-boot-starter-tomcat")

    testCompile('org.springframework.boot:spring-boot-starter-test')
}

dependencyManagement {
    imports {
        mavenBom "org.springframework.cloud:spring-cloud-starter-parent:1.0.2.RELEASE"
    }
}

task wrapper(type: Wrapper) {
    gradleVersion = '2.4'
}

Think there is some issues with classpath but don't know where to start looking.

Same app but with EurekaServer works fine somehow.

This issue was moved from spring-projects/spring-boot#3161

Thanks,

Start with PortalApplication and the Gradle build configuration, comparing the bootRun classpath with the WAR deployed to standalone Tomcat. Investigate how the Eureka client dependency and provided Tomcat runtime are packaged and initialized in the traditional deployment. Done means the deployed WAR initializes the Eureka client as bootRun does.