Publish plugin issue

[Florian Schäfer]

Yes, absolutely!

If these files are published (and I think they should be), the Nexus repository is the right place to do so.
AFAICS these files are even already published over there, see e.g. https://josm.openstreetmap.de/nexus/content/repositor
ies/snapshots/org/openstreetmap/josm/plugins/apache-commons/SNAPSHOT/

The source code repository should not be used for build artifacts, amongst other reasons it will drastically increase
the size of the repo. For now the main *.jar of the plugins will have to remain in the SVN repo, because as Michael
explained, the JOSM plugin updater depends on that and would require significant work to change that. But other build
artifacts should not be added to the SVN, that would be a step in the wrong direction.

Actually, thank you for bringing this topic up here! I'll change the defaults of the gradle-josm-plugin a bit for the
next release, so JOSM plugins built with Gradle will have JavaDocs and source code for required plugins in at least
Eclipse and IntelliJ Idea.
For the `tested` JOSM versions this was already possible, but not for required plugins, because I wasn't aware that
JavaDoc and sources were published to the Nexus repo.

Cheers,
Florian


Am Donnerstag, den 31.05.2018, 14:50 +0200 schrieb Michael Zangl:
> 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
> 
>