Details
Sub-task
Closed
Major
Description
Activity
Hide
Arnaud Heritier
added a comment -
In theory yes 
You have to know that our users have the habit to take a release and to not update their plugins.
Why ? Because in maven 1 you can't easily update them like in maven 2.
You have to ensure that all the developers in the team use the same set of plugins.
It's based on my own experience.... I saw that several times ...
It's why the users consider we didn't make a release since september, even if we republished a lot of plugins
Show
Arnaud Heritier
added a comment - In theory yes
You have to know that our users have the habit to take a release and to not update their plugins.
Why ? Because in maven 1 you can't easily update them like in maven 2.
You have to ensure that all the developers in the team use the same set of plugins.
It's based on my own experience.... I saw that several times ...
It's why the users consider we didn't make a release since september, even if we republished a lot of plugins
You have to know that our users have the habit to take a release and to not update their plugins.
Why ? Because in maven 1 you can't easily update them like in maven 2.
You have to ensure that all the developers in the team use the same set of plugins.
It's based on my own experience.... I saw that several times ...
It's why the users consider we didn't make a release since september, even if we republished a lot of plugins
Not sure this is really necessary. We should only schedule plugin issues if they are relevant for a core release.
MPXDOC-197is is just a minor issue that can be fixed independently.MPXDOC-197is is just a minor issue that can be fixed independently.