Gradle plugin cannot resolve a main class from "run" task

[tomaslin]

When you specify a main class that is found in a jar file, get an error > No main class specified

This seems to happen because the findMainClass call happens before compile time dependencies are resolved. It should happen after.

[tomaslin]

The definition of main is

run {
    main = 'com.netflix.blah.Application'
}

but seems that it is expecting

springBoot {
    mainClass = '...'
}

[dsyer]

I can confirm that the second form in your last comment works. Is that a problem still?

[tomaslin]

Our problem is that we're upgrading from 1.0.2.RELEASE. In this version, we use the same run configuration as the Gradle application plugin.

From the perspective of someone upgrading, if the first form is no longer being supported, it should at least be mentioned in the release notes.

[dsyer]

And the first form doesn't necessarily fail the build, it just puts the wrong start-class in the MANIFEST. Is that what you see too (just checking)?

[tomaslin]

We see a build failure when trying to do a bootRun

:bootRun FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':bootRun'.
> No main class specified

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

This is with 1.1.1.RELEASE and the following run block

run {
    main = 'com.netflix.mypackage.Application'
}

One issue might be that this main class is not found in the current project's src directory, but is pulled down from a jar in artifactory, but we see this works fine with the SpringBoot{} ( second form ) declaration