
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
could not read pom.xml when guessing schema
Hi All,
I just moved from talend 6 to talend 7.0 and imported the same workspace.
Since then i am not able to change schemas for any job.
The error say rg.eclipse.core.runtime.CoreException: could not read pom.xml
when i tried to check the pom.xml from Java it said
Plugin not covered by life cycle configuration: org.apache.maven.plugin
I am new to talend and not able to fix the issue, please let me know the solution

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Did you follow up this documentation to upgrade your Talend projects in Talend studio?
TalendHelpCenter:Upgrading your Talend products
Best regards
Sabrina

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi abhijeetnaib,
we are also facing this issue, we upgraded from 6.3.1 to 7.2.1, in one of our project we are facing this
"Could not read pom.xml" issue while opening all our existing jobs, can you or anyone tell me how we can handle this ?
org.apache.maven.model.io.ModelParseException: unexpected character in markup < (position: END_TAG seen ...jobs/process/PurgeFiles/BKP/copy_of_seq_db_purge_c_0.1</module>\n<<... @484:3)
at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:114)
at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:82)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.readModel(MavenImpl.java:557)
at org.talend.designer.maven.tools.AggregatorPomsHelper.addToParentModules(AggregatorPomsHelper.java:372)
at org.talend.designer.maven.tools.AggregatorPomsHelper.addToParentModules(AggregatorPomsHelper.java:342)
at org.talend.designer.maven.tools.creator.CreateMavenCodeProject.afterCreate(CreateMavenCodeProject.java:143)
at org.talend.designer.maven.tools.creator.CreateMavenCodeProject.create(CreateMavenCodeProject.java:164)
at org.talend.designer.runprocess.java.TalendJavaProjectManager.createMavenJavaProject(TalendJavaProjectManager.java:518)
at org.talend.designer.runprocess.java.TalendJavaProjectManager.getTalendJobJavaProject(TalendJavaProjectManager.java:294)
at org.talend.designer.runprocess.java.TalendJavaProjectManager.getTalendJobJavaProject(TalendJavaProjectManager.java:256)
at org.talend.designer.runprocess.java.JavaProcessor.<init>(JavaProcessor.java:243)
at org.talend.designer.runprocess.maven.MavenJavaProcessor.<init>(MavenJavaProcessor.java:73)
at org.talend.designer.runprocess.DefaultRunProcessService.createJavaProcessor(DefaultRunProcessService.java:341)
at org.talend.designer.runprocess.DefaultRunProcessService.createCodeProcessor(DefaultRunProcessService.java:195)
at org.talend.designer.runprocess.RunProcessService.createCodeProcessor(RunProcessService.java:75)
at org.talend.designer.runprocess.ProcessorUtilities.getProcessor(ProcessorUtilities.java:312)
at org.talend.designer.runprocess.ProcessorUtilities.getProcessor(ProcessorUtilities.java:293)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I too was getting this error. It had been working without issue for a number of weeks after we had upgraded. I tried a number approaches to correct it. I finally landed on needing to clear the .Java folder in the project folder. I stopped Talend, deleted that folder (actually renamed it just in case) and then restarted Talend. The folder will get created when the code is generated again or you attempt to do the Guess Schema. The issue went away for me at this point.
