apupier commented on issue #1538: URL: https://github.com/apache/camel-k/issues/1538#issuecomment-658766272
> > > In camel-k the name of the file is used to determine the name of the integration so we would need to remove `.camelk.*` which is not a huge issue but then it would become inconsistent and source of issues as i.e. a Java route named `MyIntegration.camelk.java` would trigger an error in the IDE as the name of the file is not the name of the class and in the code and then the use would need to code it's java bits in a different way. > > > > > > Given that it is possible to provide a specific name using `name` parameter, I would not expect to be really a problem. > > Also, we can always include in examples a specific name in Camel K modeline to have even less probability to hit a potential bug in Camel K. > > But it won't solve the Java issue There is no need of `.camelk.java`. There is no yaml schema for the Java part. I don't understand why there is an issue. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
