Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Save $650 on Qlik Connect, Dec 1 - 7, our lowest price of the year. Register with code CYBERWEEK: Register
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Mac OS X Installation Issue

I had some dummy question about first time run Open Studio:


OS=mac os x 10.9.5, ARCH=x86_64, WS=cocoa, NL=en_US
java version "1.8.0_25" Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Maven


Thanks for your help in advance!
Trying to run an Open Studio and getting java errors, see the log:

[INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
ERROR: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.7 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.7org.eclips


To see the whole post, download it here
Labels (2)
3 Replies
Anonymous
Not applicable
Author

Hello,
Please try one of the workaround available on this jira: https://jira.talendforge.org/browse/TDI-33091
Hope this help,
Thanks
Anonymous
Not applicable
Author

Thanks Abdoul, It's helps!

PROXY - it's a main problem, that cause such a strange BUG in the studio.
I guess developers shall expect users behind proxy and provide more meaningful ERROR_MESSAGE and not the " java.lang.NullPointerException "

So, what is the solution:

0. Be sure, maven is installed and in the path!
1. Delete folder ".m2" under user directory
2. Find a way to connect computer without proxy (open internet)
3. Open studio again and wait until all packages will be downloaded and installed in local machine.

That's it
Bone appetite!   
Anonymous
Not applicable
Author

Hi mikich,

Thanks for sharing your solution with us.
Have you tried this issue on 6.1.0 M to see if it repro? Feel free to add your comment and suggestion into this jira issue.

Best regards
Sabrina