As mentioned in #7 (comment),
If the plugin.yml is to be replaced by a better plugin definition system in the code, then at least the project properties from the build files (such as pom.xml, build.sbt) should be available to the source code. (e.g. ${project.version})
This is best done using plugins for those buildsystems. For SBT there is https://github.com/sbt/sbt-buildinfo, but for Maven I'm not aware of such a plugin (I haven't really searched a lot either tbf..). Either I need to find such a Maven plugin or create one myself.
There is one more feature that needs to be addressed, which is library loading, which currently can't be done any other way than in the plugin.yml. For a detailed explaination of what this system should be able to do, please refer to #4 (comment)
It would be very cool if these extra thirdparty library definitions could also be read from the build definition.
As mentioned in #7 (comment),
If the plugin.yml is to be replaced by a better plugin definition system in the code, then at least the project properties from the build files (such as pom.xml, build.sbt) should be available to the source code. (e.g.
${project.version})This is best done using plugins for those buildsystems. For SBT there is https://github.com/sbt/sbt-buildinfo, but for Maven I'm not aware of such a plugin (I haven't really searched a lot either tbf..). Either I need to find such a Maven plugin or create one myself.
There is one more feature that needs to be addressed, which is library loading, which currently can't be done any other way than in the plugin.yml. For a detailed explaination of what this system should be able to do, please refer to #4 (comment)
It would be very cool if these extra thirdparty library definitions could also be read from the build definition.