[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] Migration from 0.12 to 1.0
|
It was not our choice to break compatibility, but we had to due to
Eclipse Foundation policy to use org.eclipse.<project> namespace for
code and extension points. We did try to provide migration and
actually spent far more time than one man-day on this, but unfortunately
the problem proved to be difficult so we decided against providing
workspace migration. This was last December, IIRC, which I believe gave
m2e user community enough time to express their concerns and help
m2e developers to write "a migration script".
--
Regards,
Igor
On 11-06-27 6:23 PM, Ullrich Hafner wrote:
Wow.
Well the next time when you are considering to break backward
compatibility it would make sense that one person of the m2 team would
spend 1 day of writing a migration script rather than 10000 people (or
how many users do you already have?) spend one day.
Ulli
On 06/27/2011 03:59 PM, Igor Fedorenko wrote:
There is no workspace migration from m2e 0.12 to 1.0. You need to start
new workspace and re-import all projects.
--
Regards,
Igor
On 11-06-27 5:54 PM, Ullrich Hafner wrote:
Are there any migrations available to convert existing m2 projects from
0.12 to 1.0? Currently every of our projects is now a simple java
project rather than a maven project since the IDs changed...
Ulli
