About the title issue (impossibility to access the package repository from R 3.3.3), now I tried to install version 3.1.1 again: it works and all the repositories can be reached.
Are there any environment variables or registers whose differences between the two versions I can check?
An update. I tried other R installations on different PCs.
I remind that the question concerns impossibility to connect to any package repository (even if packages can be downloaded by a browser and then installed locally).
So I resume the results so far obtained:
3.1.1 "Sock it to me" - windows 8 not proxied - ok
3.3.1 "Bug in your hair" - windows 7 proxied - ok
3.3.1 "Bug in your hair" - windows 8 not proxied - notok
3.3.3 "Another canoe" - windows 8 not proxied - notok
3.3.3 "Another canoe" - windows 7 proxied - ok
So, it seems something come with version 3.3.x which likely does not like windows 8, even if I do not know any reported incompatibility.
Unfortunately, my current working machine is precisely the windows 8 machine ...
Related
I am using Alfresco Community v6.0.7.
When I try to query the default path by searching just PATH:"/" in the Node Browser of Alfresco Share, I get No results and 07100085 is displayed at the Name column in the grid below.
Can anyone tell me what could be causing this issue and where do we declare the app:company_home property?
Issue solved. I tried running Solr search services using following command
./solr/bin/solr start -a "-Dcreate.alfresco.defaults=alfresco,archive"
It did not give any error on the console, but when I checked Solr logs it was throwing error.
ERROR (main) [ ] o.a.s.c.SolrCore null:java.lang.UnsupportedClassVersionError: org/alfresco/error/AlfrescoRuntimeException has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
This was because I was running JDK on the machine whereas Alfresco Search Services 1.4 requires JDK 11. After upgrading to JDK 11 both core and archive got created and I was able to run queries again in the Node Browser.
I am newbie to web services. i am trying to generate stubs using Apache CFX on eclipse. when i try to add CFX in preferences using Windows >> Preference eclipse gives error "Invalid Type Name". i tried to change the JRE from JDK 6 to 7. change the versions of CFX but still problem persists.
Please help in resolve the problem
I found the solution. The problem because of multiple java version installed on my machine and CFX found two different versions of JAXB. I uninstalled java 7 from my machine and then it worked with java 6.
I am attempting to start Apache Geronimo using the command:
./bin/geronimo run
When I do this, it spins for a minute, issues the message "Main not found" and exits.
This article suggests that it is a system resource issue:
http://apache-geronimo.328035.n3.nabble.com/jira-Created-GERONIMO-5551-Failing-to-start-the-server-with-the-error-quot-Main-not-found-quot-td1324013.html
I have tried it on both an Amazon EC2 box (running Linux), and an Azure A1 box (running Windows Server), and I have tried the "Full Profile Release" and "Web Profile Release" of Geronimo, all with no change.
I'm at a complete loss as to what I could try. I am led to believe that the EC2 box, at the very least, should have the muscle to run Geronimo.
Any suggestions would be welcome.
Version 3 of Apache Geronimo is designed to run on JRE 1.7 instead of JRE 1.8. As stated in the other answers, the issue was caused by Geronimo being run on JRE 1.7 instead of 1.8.
You are not limited to JRE 1.7 and earlier in order to run Geronimo though. Therefore, all you have to do is to rename or copy the property jre-1.7 in the file etc/config.properties in your installation to jre-1.8. Afterwards, you should be able to run Geronimo without an error.
This has a huge benefit, since now you will be able to run programs on Geronimo that use Java 8 features.
It turns out that the issue is that I had the wrong version of the JDK installed. I had installed the most recent version (8), but Geronimo apparently won't work with that. When I instead installed version 6, everything worked fine.
I was getting the same error with Java 8. I tried the latest version of Java SE 7 and that resolved the problem. So I wouldn't use Java 6, since it is and has been out of support for awhile now (read: security issue).
I seem to have some problems initialising the CloudBees SDK locally to be able to run a simple application.
I've downloaded the SDK, added the required paths; everything ok up to the point where I am trying to execute the bees run command from my newly created application folder.
The error I get seems related to the JDK installation on my computer - JAVA_HOME is pointing to C:\Program Files\Java\jre7 and not to jdk .
I've checked all the local PATHS and they seem ok.
By the way I am using Windows 8.0 Enterprise 64 bit.
Fully uninstalling Java from my system followed by installing only the 64bit version and recreating System paths seems to have fixed the problem.
I am not able to find "Application Server Apache Tomcat 6.0.18" i need this for ubuntu. Can any one help me with knowing the difference between this version and available version i.e "Application Server Apache Tomcat 6.0.32" ..
Is it safe to use the advance version when in project documentation it is mentioned that earlier version is required ?
In 6.0.32, 6 is the major release number, 0 is the minor release number, 32 is the patch number.
And since this is a patch version and there are no new features/major changes, it is safe to use it in production.