Publish plugin issue

[Holger Mappt]

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 according 
>> target will have those private files in her/his working copy dist 
>> directory. If someone svn adds and svn commits the JARs then the next 
>> svn update will show merge conflicts because the JARs are now in the 
>> repository and the working copy as private files and SVN doesn't know 
>> what to do.
>>
>> A clean solution is to either add the sources and javadoc JARs to all 
>> targets and to create+commit them for all plugins in dist, or not to 
>> do that. The sources and javadoc JARs that were added in r34045 were 
>> deleted in the next revision, so my assumption is that we don't want 
>> those JARs in dist.
>>
>> So what's the plan with sources and javadoc JARs?
> 
> Vincent wants these files to build, but they should not to be released.
> 
> Add an svn:ignore in build directory?
> 
> Ciao

Hi,

Build the files to do what with them? Would a nodist directory parallel 
to dist be an option if the JARs are not to be uploaded to the repository?

The conflict will occur if the JARs are released later on. An svn:ignore 
will not help in that case. It is better to have separate directories 
for released and not released files.

Regards,
Holger