I used Nuxeo Studio for research purposes and created a Schema and added it to my local server using the Nuxeo Chrome Extension is hot deploy.
Now, what if I need to uninstall the package?
I tried to use the ./nuxeoctl mp-uninstall <package-name-installer-by-studio> to achieve that. Apparently, it worked. However, my local server fails to start again and, when the hot reload is called again, it hangs up saying:
data/myWorkflow.zip not found in <path>/nuxeo-server-10.10-tomcat/nxserver/bundles/<package>.jar
also:
org.nuxeo.ecm.webengine.app.WebEngineExceptionMapper] org.nuxeo.ecm.core.api.NuxeoException: Failed to invoke operation: Service.HotReloadStudioSnapshot
I am led to think that this is badly done/programmed: there should be an error proof way to uninstall the packages installed by Studio, since Studio won't be the only tool to be used in a big project.
I managed to install/uninstall the package with another strategy: I didn't hot reload it with Nuxeo Chrome Extension. I just downloaded the package and installed it using Nuxeo-CLI. Then, I was able to uninstall it without any issues.
I noticed that this gives me more control since I can keep the package that was generated, I can inspect what changes were made (and understand what happened in a more open way), and then install/uninstall it manually.
Since I didn't figure out the problem that is with Nuxeo Chrome Extension, I chose not to use it for a while.
Related
this might be a quick one.
I've imported a Flutter project which a colleague created via VS Code into Android Studio (via Git - Bitbucket).
(I've worked on another new Flutter project just this day.)
The problem is: some icons he used aren't found by the compiler for me.
Examples of working icons:
Icons.pregnant_woman
Icons.person
Icons.calendar_today
Not working:
Icons.qr_code
Icons.biotech
Also, no matter in which file I'm in, there's a hint window above stating: 'Pub get' has not been run and I get the option to run get dependencies (pub get) or upgrade dependencies (pub upgrade).
When I first imported the project, the compiler didn't even know what Flutter is. After I executed pub get the first time, most of the errors were gone. The only ones missing are the few icons. But the hint saying I didn't do pub get is still there which was never like this in my other projects.
What can I do?
Btw, pub outdated says dev_dependencies: all up-to-date and
Dependencies are all on the latest resolvable versions.
Newer versions, while available, are not mutually compatible.
I run into this problem a while ago. The way I managed to solve it is:
go to Vs code setting and search flutter create and disable Flutter Create Offline
I hope this is helpful!
Got it! Turns out I changed some internal flutter file some while back and it wouldn't upgrade the flutter version automatically until I did "flutter upgrade -force".
Good day everyone; having project and must update to cordova 9.0.0 and at least to android 8.0.0 to publish in google play, when i try to build the build fail because (Could not resolve all artifacts for configuration ':classpath'), the most likely cause is connections errors the question is
can i set a proxy program (say for example tor) through the node.js command prompt (and not through android studio because it doesn't work)
if that not possible, if i manged to download the required files manually (example bundletool-0.13.2.jar https://dl.google.com/dl/android/maven2/com/android/tools/build/bundletool/0.13.2/bundletool-0.13.2.jar) is there a way to integrate them somehow to the project as a work around
Thanks in advance
I downloaded Google's Android Sceneform example project, solarsystem, under the samples folder in the hyperlink. I intend to use it as a base for an AR Application I need to create. However, I need to take the project to an offline environment.
While I am connected to the internet, the project builds without issue. However, when I go offline, I end up with a
No cached version of com.android.tools.build:aapt2:3.4.1-5326820 available for offline mode.
I have no problem syncing the project, but I am unable to build anything. I have tried downloading the appt2 dependency from Google's Maven Repository directly and including it in my project's dependencies in the build.gradle folder but I still get the same error. My project MUST be built offline.
I have also searched online for a few solutions, but none have worked for me so far. I found out that Google did remove the version of aapt2 that I am using, but I was still able to download it from their repository. As I understand, Android should be able to build my project so long as the dependencies have been cached. I am just trying to identify the problem at this point. Why has this one dependency not been cached and why despite including it's jar directly have I not been able to run it?
I installed Enide Studio yesterday (decompressed the zip to /opt/enide-studio and had to make eclipse executable). I then attempted to import an existing project. It seemed to successfully import, but the project explorer shows nothing (it's completely blank). I restarted the IDE, etc. -- still nothing.
Figuring it actually did not import the project, I tried again to import it this time from its git repo. I was met with the error that the project already exists in the workspace; so, it's there, but the IDE is not showing it.
I then tried creating a new Node.js project. It again seems to successfully create a project, but the UI is still white in all panels. I see the perspective buttons for JS, Node, etc., but panels like Console are also completely blank white.
Also, attempting to create an express project fails outright because it can't find express (despite installing it as directed with npm install -g express).
I've logged out and back in as well as a reboot. Still nothing...
Has anyone else encountered this and have a work-around/fix for Enide Studio?
You have too many issues put together as one.
Answering what is in question topic: "Nodeclipse does not show projects in Mint 17 64-bit"
Nodeclipse is plugin to Eclipse and displaying project in Project Explorer is implemented inside Eclipse core module called Eclipse Workbench. You can switch to other perspective e.g. Java and see that actually it displays the same list of projects.
General recommendation is to get latest Eclipse 4.4 Luna and install Nodeclipse (or get Enide Studio released after June 2014, not yet)
For other issues create separate tickets
http://www.nodeclipse.org/#support
Setup:
I have created a module that works fine in the solution where it was created, ie, the orchard source code. I then package it up using package create.
Edit: I now realize that the problem appeared IMMEDIATELY after installing visual studio 2012.
Problem:
If I now install the module on a different app using the package and install from file, all the alerts show the module is installed, it appears in the features list, it is enabled... but there are no menu items, no entry in the migrations table, nothing.
Edit: Nothing appears in the logs. The files are, however, installed correctly in the modules folder of the site.
Question:
What could be going wrong that stops the module being properly installed using the package given that the module works fine in the source code solution where it was created??
Any suggestions?
Edit:
How could installing visual studio 2012 have affected Orchard?
I notice that installing visual studio 2012 resulted in various bits of sql server 2012 being installed at the same time. Could this be relevant? EG, is this why the migrations code never runs?
Edit on the basis of Bertrand Le Roy's comments (see below this question):
BertrandLeRoy says that having ASP.NET MVC 4 installed in the GAC, as well as Razor 2 (both of which came with VS 2012), is the problem.
He suggests upgrading to Orchard 1.5.x.
However:
I have tried using a new install of Orchard 1.5.1, and the problem is the same:
Creating a new module using VS 2012 and Source Code for Orchard 1.5.1 and the module appears correctly when running the orchard site from VS.
Creating a package and then installing that into an Orchard 1.5.1 site, eg, using WebMatrix, running and then installing the package has the following effect:
2.1. The alerts in the dashboard tell me that the package has installed correctly.
2.2. However, enabling the feature does nothing.
2.3. This is hardly surprising, as installing the package has not even run the migrations.
The last test I can do is to see if the package runs on a web server that doesn't have asp.net mvc4 installed. I will post back once that is done.
However, the main point is that using Orchard 1.5.1 produces the exact same result. So, if the problem really is the fact that MVC 4 and Razor 2 are on the machine, then Orchard 1.5.1 is not solving it.
Ie, what will happen when I install mvc 4 on the web server as I will inevitably have to for other, non Orchard apps?
I experienced the same thing on version 1.8.1. That is, the module appeared to install fine, but it didn't actually perform migrations or load correctly.
Initially, I saw nothing in the log to indicate a problem. However, after adjusting the /Config/log4net.config file to log ALL instead of just ERROR messages. I got this:
... Orchard.Environment.Extensions.Loaders.PrecompiledExtensionLoader -
- Extension "Transformalize" will not be loaded as pre-compiled extension
because one or more referenced extension is dynamically compiled
The part saying my module "will not be loaded as pre-compiled extension because one or more referenced extension is dynamically compiled" seemed to explain why my module wasn't loading. So, I Googled and found this documentation regarding the Orchard module loader and dynamic compilation. It's a bit complicated at 2 AM, but what I gathered is my module's reference to another module (Orchard.Autoroute in this case) caused the log message (above) in the production environment. I removed my module's reference and dependency on Orchard.Autoroute, and then it installed fine.
The documentation explains how modules are dynamically compiled and how the settings in /Config/HostComponents.config can change how things work.