Closed ericbottard closed 4 years ago
Maybe a different case from #107 , maybe not
Could you try again with the updated buildpack?
Still not working, but I think you mean that you "fixed" #107
This is a bit more involved I think
Yes, I do hope you are getting a different exception at least.
Yes, that is now throwing a different exception, so #107 is rightfully closed.
Using the Boot plugin with layout=NONE
is kind of pointless isn't it (can't you just build a regular jar)?
I believe this function would be deployable if you set a Start-Class
(or Main-Class
but it isn't one of those really) in your MANIFEST.MF
, or if you supply the main=
parameter to the function.uri
when you start the invoker. Is that not "magic" enough? How would the invoker detect a start class automatically with no configuration?
My understanding was that the invoker could blend in everything it finds in that jar to whatever context it creates (child or otherwise). That is, as a function author, I assume that everything I provide will be (the equivalent of) @ComponentScan
' ed by the runtime
You can’t @ComponentScan
without a package to start from (nobody wants to scan the whole classpath).
Closing as WONTFIX
I tried with a single
@Bean
annotated function, inside a@Configuration
class. The whole thing being packaged with the boot plugin, but inlayout=NONE
mode. So nomain()
provided by me, and no@SpringBootApplication
provided by me.I believe this should be supported, but got