Problem migrating from eclipse 2021-12 to 2022-3 #630
Replies: 7 comments 4 replies
-
|
This should be reported to https://github.com/tesla/m2eclipse-mavenarchiver . A workaround is to remove the mavenarchiver connector. |
Beta Was this translation helpful? Give feedback.
-
|
@mickaelistria I don't think that the configurator is to blame here from the stacktrace it seems an operation was canceled (or an old monitor is used here) and it is never checked by m2e in |
Beta Was this translation helpful? Give feedback.
-
|
And then ? |
Beta Was this translation helpful? Give feedback.
-
|
But it seems to be unattended. |
Beta Was this translation helpful? Give feedback.
-
|
same issue！any resolution？ |
Beta Was this translation helpful? Give feedback.
-
|
Not yet, the best would be to have a smalls and simple reproducer to one can investigate further here. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know what the problem could be but the problem is present and I don't know ho to solve it. |
Beta Was this translation helpful? Give feedback.
-
|
Well, you don't say much about your "migration" process. When I upgrade Eclipse, I create an entirely new workspace. I copy my preferences over, but I reimport all of my projects from my local git repositories. Before I import each one, I remove all the "." files (rename them, just in case) so the import is done fresh without any leftover Eclipse or m2e artifacts. |
Beta Was this translation helpful? Give feedback.
-
|
I simply opened an existing project (I tested it with more than one) with Eclipse 2022-03 and I got the error.
If I reopen the same project with Eclipse 2021-12 it works normally.
Tks
Dott. Tullio Bettinazzi
Responsabile R&D
Axioma Srl
Via Gerardo e Antonio Philips, 12
20900 Monza (MB)
***@***.***
+39 03922511
+39 335 1048626
www.axioma.it
The content of this e-mail and any attachments, is strictly confidential, not to be produced in court and intended for the person (s) to whom it is addressed. If you have received this email in error, please let us know immediately and delete it. It is forbidden to copy and disclose the contents of this email. Any unauthorized use of the information contained herein by third parties or in any case not indicated in this email may be prosecuted according to the law. We inform you that for the exercise of the rights provided for by the articles 15 and ss. of the 2016/679 EU Regulation (GDPR), you can contact the following address: ***@***.***
…----- Messaggio Originale -----
Da: "David M. Karr (fullname at gmail.com)" ***@***.***>
A: "eclipse-m2e/m2e-core" ***@***.***>
Cc: "tullio0106" ***@***.***>, "Author" ***@***.***>
Inviato: 03/05/2022 22:03
Oggetto: Re: [eclipse-m2e/m2e-core] Problem migrating from eclipse 2021-12 to 2022-3 (Discussion #630)
Well, you don't say much about your "migration" process. When I upgrade Eclipse, I create an entirely new workspace. I copy my preferences over, but I reimport all of my projects from my local git repositories. Before I import each one, I remove all the "." files (rename them, just in case) so the import is done fresh without any leftover Eclipse or m2e artifacts.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
--
This message has been checked by Libraesva ESG and is found to be clean.
Mark it as spam
Blacklist sender
|
Beta Was this translation helpful? Give feedback.
-
|
So, as I suggested, in the existing project you are opening/importing, first remove (move out of the way) the .project and .classpath files and .settings directory, and then try importing it. |
Beta Was this translation helpful? Give feedback.
-
|
Creating a brand new project with same files it seems to work.
However it doesn't seem a viable solution : all my configurations would be lost..
Could You explain me better why it doesn't work ?
Tks
Dott. Tullio Bettinazzi
Responsabile R&D
Axioma Srl
Via Gerardo e Antonio Philips, 12
20900 Monza (MB)
***@***.***
+39 03922511
+39 335 1048626
www.axioma.it
The content of this e-mail and any attachments, is strictly confidential, not to be produced in court and intended for the person (s) to whom it is addressed. If you have received this email in error, please let us know immediately and delete it. It is forbidden to copy and disclose the contents of this email. Any unauthorized use of the information contained herein by third parties or in any case not indicated in this email may be prosecuted according to the law. We inform you that for the exercise of the rights provided for by the articles 15 and ss. of the 2016/679 EU Regulation (GDPR), you can contact the following address: ***@***.***
…----- Messaggio Originale -----
Da: "David M. Karr (fullname at gmail.com)" ***@***.***>
A: "eclipse-m2e/m2e-core" ***@***.***>
Cc: "tullio0106" ***@***.***>, "Author" ***@***.***>
Inviato: 04/05/2022 17:02
Oggetto: Re: [eclipse-m2e/m2e-core] Problem migrating from eclipse 2021-12 to 2022-3 (Discussion #630)
So, as I suggested, in the existing project you are opening/importing, first remove (move out of the way) the .project and .classpath files and .settings directory, and then try importing it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
--
This message has been checked by Libraesva ESG and is found to be clean.
Mark it as spam
Blacklist sender
|
Beta Was this translation helpful? Give feedback.
-
I migrated my eclipse version from 2021-12 to 2022-03.
On every project I tried to open I get one or more maven build problem.
If I reopen the same project with the 2012-12 (I saved it) it works again .
How can I solve that blocking issue ?
Tks
`Description Resource Path Location Type
null (org.apache.maven.plugins:maven-jar-plugin:3.2.2:jar:default-jar:package)
org.eclipse.core.runtime.OperationCanceledException
at org.eclipse.core.runtime.SubMonitor.checkCanceled(SubMonitor.java:602)
at org.eclipse.core.internal.resources.Resource.setDerived(Resource.java:1620)
at org.eclipse.m2e.core.internal.M2EUtils.createFolder(M2EUtils.java:86)
at org.sonatype.m2e.mavenarchiver.internal.AbstractMavenArchiverConfigurator.writePom(AbstractMavenArchiverConfigurator.java:840)
at org.sonatype.m2e.mavenarchiver.internal.AbstractMavenArchiverConfigurator$1.build(AbstractMavenArchiverConfigurator.java:180)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:135)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:169)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$1(MavenBuilder.java:114)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:182)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:117)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$0(MavenBuilder.java:105)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:182)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:156)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:103)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:88)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:198)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:860)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:281)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:334)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:337)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:392)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:417)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:161)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:255)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
pom.xml /izpack-custom line 4 Maven Build Problem`
Beta Was this translation helpful? Give feedback.
All reactions