topic Re: Building a standalone job does nothing, Non-readable POM in Talend Studio

Building a standalone job does nothing, Non-readable POM

Jj5 — Tue, 18 Jun 2019 19:23:13 GMT

Thanks for taking the time to view my post. I'm using Talend 6.3 on both my work PC and my home PC and the copy at home works but when I try to build on the work build, it does nothing (not files get created). No errors are thrown from the studio, but when I check the lastGenerated.log file I get the following errors:

[INFO] Scanning for projects...
[ERROR] The build could not read 2 projects -> [Help 1]
[ERROR]   
[ERROR]   The project org.talend.code.freemontcomm:routines:6.3.1 (\\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom_routines.xml) has 1 error
[ERROR]     Non-readable POM \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom.xml: \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom.xml (The system cannot find the file specified) @ \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom.xml
[ERROR]   
[ERROR]   The project org.talend.job.freemontcomm:OSC8260001:0.1 (\\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom_OSC8260001_0.1.xml) has 1 error
[ERROR]     Non-readable POM \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom.xml: \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom.xml (The system cannot find the file specified) @ \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\pom.xml
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

My workspace is on a network path under \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\ so I'm not sure why it's going to \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\ so I think this is where my trouble is coming from.

Any suggestions would be amazing

Re: Building a standalone job does nothing, Non-readable POM

Anonymous — Thu, 20 Jun 2019 07:41:45 GMT

Hello,

Did you select maven when you use talend studio to build a standalone job?

Are you running on Unix or Windows?

Best regards

Sabrina

Re: Building a standalone job does nothing, Non-readable POM

Jj5 — Thu, 20 Jun 2019 16:05:58 GMT

Thanks for the reply xdshi,

I don't think that I select maven when I create the stand-alone job, I just right click and hit build job. It works correctly on my home pc and I'm not doing anything different there. I think the issue is related to Talend thinking the pom file is in a different directory, it seems to be doubling down on the workspace path:

\\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\

I'm not sure why Talend is looking there when that path doesn't exist, my workspace is just \\uswefile1.oscis.kdc.org\universe\Talend\Dev\Jj\.Java\.

I have a Windows OS.

Re: Building a standalone job does nothing, Non-readable POM

Jj5 — Thu, 27 Jun 2019 19:32:49 GMT

Any ideas?

Re: Building a standalone job does nothing, Non-readable POM

Anonymous — Fri, 28 Jun 2019 04:30:47 GMT

one quick question,
Do you copy the studio installation folder from work PC to home PC or you install a new studio on home PC? I see you mentioned 'the copy at home works' in your first post.

Regards
Shong