Re: Publish plugin issue

Hi Vincent, I restored to original behavior without the SVN update and commit part (in r34244). Regards, Holger On 2018-06-03 at 18:58 +0200 Vincent Privat wrote: Hello, This involves unneeded work from us. As said before, please restore the previous mechanism, which is being used for

Re: Publish plugin issue

Hello, This involves unneeded work from us. As said before, please restore the previous mechanism, which is being used for Nexus, and simply make sure only the plugin jar is commited, this is the only change that is required. Best regards, Vincent 2018-06-01 11:07 GMT+02:00 Holger Mappt : > On

Re: Publish plugin issue

On 2018-05-31 at 21:00 +0200 Dirk Stöcker wrote: On Thu, 31 May 2018, Michael Zangl wrote: We currently have all snapshot plugin jars including source/javadoc on the nexus server: https://josm.openstreetmap.de/nexus/content/groups/public/org/openstreetmap/josm/plugins/ You can pull them

Re: Publish plugin issue

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

Re: Publish plugin issue

On Thu, 31 May 2018, Michael Zangl wrote: I'm not a fan of having distribution binary files in the source code repository or in any other repository that has to be at a specific place in the directory tree. That may be the case, but it is the way it is and the task is not the reinvent the

Re: Publish plugin issue

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

Re: Publish plugin issue

Hi, I'm not a fan of having distribution binary files in the source code repository or in any other repository that has to be at a specific place in the directory tree. We currently have all snapshot plugin jars including source/javadoc on the nexus server:

Re: Publish plugin issue

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 /dist. Would

Re: Publish plugin issue

On 2018-05-30 at 11:57 +0200 Dirk Stöcker wrote: On Wed, 30 May 2018, Holger Mappt wrote: I don't see how that can be done without conflicts. If the sources and javadoc JARs are generated but not svn added and svn committed then those JARs are SVN private files. Everyone who runs the

Re: Publish plugin issue

On Wed, 30 May 2018, Holger Mappt wrote: I don't see how that can be done without conflicts. If the sources and javadoc JARs are generated but not svn added and svn committed then those JARs are SVN private files. Everyone who runs the according target will have those private files in her/his

Re: Publish plugin issue

Hi Vincent, I don't see how that can be done without conflicts. If the sources and javadoc JARs are generated but not svn added and svn committed then those JARs are SVN private files. Everyone who runs the according target will have those private files in her/his working copy dist directory.

Re: Publish plugin issue

Ah sorry I totally misunderstood your change. Please restore what I did, I thought you would only modify the "publish" target to ignore the files when committing to SVN, not delete the targets! 2018-05-29 22:03 GMT+02:00 Holger Mappt : > Hi, > > I implemented the two changes in r34224 and

Re: Publish plugin issue

Hi, I implemented the two changes in r34224 and r34225. This undid most of the changes to build-common.xml from r34045 where plugin-sources.jar and plugin-javadoc.jar were added. Marián, it should work for you now. Regards, Holger On 2018-05-27 at 12:18 +0200 Vincent Privat wrote: No

Re: Publish plugin issue

No objections:) Le sam. 26 mai 2018 à 22:54, Holger Mappt a écrit : > Hi Marián, > > There are two problems and I can confirm your issue. > > Problem one is "ant update-current" which expands ../dist/${plugin.jar} > to

Re: Publish plugin issue

Hi Marián, There are two problems and I can confirm your issue. Problem one is "ant update-current" which expands ../dist/${plugin.jar} to ../dist/home/marian/projekty/josm/josm_plugins/dist/pointInfo.jar instead of ../dist/pointInfo.jar. The ../dist/ must be removed in the target, the path

Re: Publish plugin issue

Hi, sorry for the late reply. Dne 17.5.2018 v 22:03 Holger Mappt napsal(a): > Hi Marián, > > Looks like you managed to publish the PointInfo plugin in the meantime > (r34195). Yes, I did it manually by committing the binary with proper commit message. > An SVN status with ! is never good. I

Re: Publish plugin issue

Hi Marián, Looks like you managed to publish the PointInfo plugin in the meantime (r34195). An SVN status with ! is never good. I assume there was a newer version in the repo that was not fetched because you had a modified dist/pointInfo.jar. Run svn status with option -u (to see what updates

Publish plugin issue

Hi, It is a long time when I published new version of pointInfo plugin. Now I want to publish updated version, but it does not work :-( I've commited changes in code: r34168 | mkyral | 2018-04-24 07:48:05 +0200 (Út, 24