I am trying to upload a new version of one of my add-ons and I am getting an error:
Missing attribute Vaadin-Package-Version in the manifest file of so-helper-4.1.1.jar.
My zip file contains the correct details in the META-INF/MANIFEST.MF file:
Manifest-Version: 1.0
Vaadin-Package-Version: 1
Vaadin-Addon: so-helper-4.1.1.jar
Implementation-Vendor: Syam Pillai
Implementation-Title: SO Helper
Implementation-Version: 4.1.1
Hi Syam! Do you also have the manifest data in the jar file itself? I remember that being an issue for some.
BTW. My pro tip is to publish through Maven central. Better for end users (no need for extra repository → speed & stability) and those special manifest entries are optional if published that way (Directory reads pretty much the same data from the the pom.xml instead).
Looks like you got it through? Spotted this from the logs: “not allowed to use Maven coordinates [groupId: com.vaadin.addons.so, artifactId: so-helper”. So Maven groupd id needs to start with org.vaadin.addons if you publish via Directory, but I guess you already figured that out 
Yes, Matti, when I saw the message I tried to change the groupId but made a mistake.
Anyway, now, it’s looking Ok after I changed it to org.vaain.addons.so.
Earlier, the jar plugin was overriding some stuff from my parent POM and it was corrected.
Thanks.
How does this work? Does the Vaadin Directory auto-detect new versions?
One of our dependencies, LeafletMap for Vaadin - Vaadin Add-on Directory, has version 4.2.0 in the directory but has 4.6.0 (which we use) in https://mvnrepository.com/artifact/software.xdev/vaadin-maps-leaflet-flow
It should check new versions automatically indeed (“cron” job). Thanks for the heads up, need to check what is going on with that add-on.