Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Francesco R
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 24, 2013

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

2 answers

1 accepted

0 votes
Answer accepted
Francesco R
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 24, 2013

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.

0 votes
Paul Pasler
Atlassian Partner
July 24, 2013

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 24, 2013

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
Atlassian Partner
July 24, 2013

so is this issue solved?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events