plugin fails to start if version has not patch number in version (only major.minor release)

[Francesco R]

I made my plugin dummy-plugin-1.0.jar and it was working with release number 1.0 in pom.xml
Then I made some modifications and it was no more enabled.
Then I realized, don't ask me in whch way :), that ONLY changing version in pom.xml from 1.0 to 1.0.0 and rebuilding all, not it's enabled without any problem.

Am I missing something? Why this could happen ? Is this a maven versioning problem ?

Thank you

[Francesco R · Accepted solution]

Let's say that I solved it by myself but I'd like to know if there is a particular reason for which I have to set version in the form of major.minor.patch instead of simply major.minor.

[Paul Pasler]

I could not reproduce your problem, changing the pluginversion shouldn be a problem.

Do you mean this property in the pom:

<groupId>...</groupId>
    <artifactId>...</artifactId>
    <version>1.0.0</version>

Try to clear everything (atlas-clean) and install via atlas-cli

[Francesco R]

Yes, I mean this. Having version 1.0 there is a moment into which a well working plugin is no more enabled at jira server startup. Just changing version from 1.0 to 1.0.0 and rebuilding with atlas-clean and atlas-package all is working again.
I didn't tried to go back to 1.0 version to see what happens

[Paul Pasler]

so is this issue solved?