Closed Ingvord closed 5 years ago
Problematic artifact is JTangoIDL, I suggest to remove it as it is basically immutable code generated from idl - does not make much sense to generate it everytime build JTango but rather - once for new idl version, see ~#69~
Then there is a couple of versions e.g. 9.5.11 or 9.5.14 where javadoc is missing in other artifacts. I would simply delete these versions, deploy a new good version and then sync. It is safe because last synced version 9.5.9 and we have public users they won't notice any difference, but will be happy to get a new version (it is okay if it jumps over a few numbers). Internall users AFAIK use latest version anyway -> again no difference. Anyway we have to hurry, as it is not possible to delete a version after an year. So we have time till Sep 25th
@gwen-soleil , should I do it? Or you will take care of this issue?
It seems I was totally wrong saying that when syncing with maven central it syncs all previous versions as well. I have tried with the latest 9.5.17 and it works!
So we do not need to delete any versions from bintray and this issue may be now closed!
We need to find a way to disable doclint while preserving javadoc.jar (try to uncomment configuration in parent/pom.xml)