The idea of the quasi-standard files is to have them in a structure in
which IDEs can pull them in automatically.
We only have few plugins that use a build system that could make use of
such a functionality. And as far as I have seen, most of them use git
and are outside of the source tree anyways.
This would only really make sense if we convert the plugins to not
depend on jar-Files but instead use some more modern dependency system
that supports dependency versioning. That way it would be easier to test
plugins that depend on each other in different version combinations and
it would be easier for us to reporduce plugin errors by not only loading
the plugin list of that user, but instead loading the exact plugin
versions the user used including the source tree to our IDE for debugging.
This would require many changes to JOSM and the way JOSM is built. We
are far away from this (e.g. see #8269).
Michael
On 31.05.2018 08:27, Dirk Stöcker wrote:
On Wed, 30 May 2018, Holger Mappt wrote:
Build the files to do what with them?
Hmm. I think because these are a Quasi-Standard :-) Don't know.
Would a nodist directory parallel to dist be an option if the JARs
are not to be uploaded to the repository?
They could be in the <plugin>/dist. Would that be ok?
Ciao
