I followed all the instructions for setting up the environment in eclipse indigo EE. I did it both in ubuntu 12.04 64bit and Windows 7 64bit, and everything goes good till the point when I try to run the imported example (showcase-java). the build fails and following error appears in the eclipse console:
Failed to execute goal on project playn-showcase-java: Could not resolve dependencies for project com.googlecode.playn:playn-showcase-java:jar:1.0-SNAPSHOT: Could not find artifact com.googlecode.playn:playn-showcase-core:jar:1.0-SNAPSHOT in forplay-legacy (http://forplay.googlecode.com/svn/mavenrepo) -> [Help 1]
Note that I follow all the instructions on Getting Started page and I'm sure I'm not missing out on anything mentioned there on the page.
Hi here is a more detailed tutorial on how to set up eclipse with playn link
May be this is helpful for you.
Related
used uno-check to install all the needed prerequisites.
after this i have installed the Uno Platform dotnet templates :
dotnet new -i Uno.ProjectTemplates.Dotnet
and created a new project with this command :
dotnet new unoapp-winui -o MyUnoApp
who give me some errors about failed restoration (MSBUILD : error MSB1009 - project file not exist -)
After that i load the solution in visual studio (2019/2022), select MyUnoApp.Windows.Desktop as starting project (x86) and start the debug session but i got this error:
An unhandled exception of type 'System.DllNotFoundException' occurred in UNO.Windows.Desktop.dll
Unable to load DLL 'Microsoft.ui.xaml.dll' or one of its dependencies
Any hint?
I had the exact same problem, but after fiddling around a bit I found a solution.
Set the '.Windows.Package' project as startup instead of '.Windows.Desktop'
Also make sure you are have the same Platform selected for both Package and Desktop project.
It's my understanding that MyUnoApp.Windows.Desktop is the building target for the Windows desktop, whereas MyUnoApp.Windows.Package is the building target for the UWP app (pls correct me if I'm wrong). Hence, the original poster still would not have the problem of being unable to build the desktop app - which is the same problem I'm facing right now.
I did the basic installation of the SabreRedWeb-SDK-20.11.6 and then clicked on the ConciergeInstaller-5.7.0-1.0.4.exe and it seems to have installed properly. The web instructions found here don't match the video.
Web Instructions (I'm following the Concierge install section)
https://developer.sabre.com/sdks/travel-agency/sabre-red-360/getting-started
Video Explanation here...
https://www.youtube.com/watch?v=ZgwbISnB35Y&list=PLgSinp8nTL3F1IOGQ9Jbuf7m_GDCCHZAF&index=1
At 1:45 of the video they mention doing a ngv...
Well, I assume I do that in the node installation which by default was put here...
C:\Program Files\Concierge\node
But when I do ngv when running node.exe
Thrown:
ReferenceError: ngv is not defined
I'm thinking I need to be running the concierge tool itself and not node directly.
You use a command prompt to do the ngv build etc...
Thereafter I am using Visual Studio Code and everytime I save the files the terminal does the save and "re-build" or I suppose it is "re-run".
I'm using JBDS 11.3.0.GA on Ubuntu 16.04 LTS. I'm generating a Fuse project for Fuse 7.1.0 on standalone Karaf platform, using the camel-spring-cxf-code-first template. The project generates correctly but, trying to run it as described by the ReadMe.txt file fails. For example, after installing the bundle as follows:
karaf#root()> install -s mvn:com.mycompany/camel-spring-cxf-code-first/1.0.0-SNAPSHOT
Bundle ID: 223
karaf#root()>
trying to go to http://localhost:8181/cxf/report/?wsdl (of course, after having replaced in the generated code 9292 by 8181) displays "No service was found." in the browser and shows the following in the log file:
16:33:36.209 WARN [XNIO-4 task-1] Can't find the the request for http://localhost:8181/cxf/report/'s Observe
meaning that the generated project is not valid.
Kind regards,
Nicolas
The deployment of this kind of projects is not working at the moment - see the following statement in the Readme.txt file.
Note: This project does not currently work. It has some issues. It is based
on the archetype.
I raised an issue for developers - https://issues.jboss.org/browse/FUSETOOLS-3177.
I am migrating my application from vaadin 7 to vaadin 8 and following exactly same steps mentioned in the link
But I am getting error
Error: Could not find or load main class com.google.gwt.dev.Compiler
when I run following command to compile the widgetset
mvn -X vaadin:compile -Dvaadin.charts.developer.license= package -Dmaven.test.skip=true
I took out all the addons and kept only the chart one. Can you please help me what might be causing the error. I could upload the POM file, but its big.
Edit:
I noticed that classpath is not set up when I am running mvn vaadin:compile
I figured I had some issues, like incompatible version of add-ons ,etc. When I used the compatible ones, it got fixed.
I just installed a clean install of the new .NET Core SDK on a CentOs 7 box. I had a different Linux VM I was running to test this and received the same error there.
I am building my application in VS 2017 on a Windows box and copying the project file over to the Linux box to test it. I am coming from netframework environment and trying to learn dotnetcore so I am sure this is probably just a newb issue. Here is what I am doing.
I run a dotnet restore, which works without error.
I run a dotnet build, which I receive a
Build succeeded.
0 Warning(s)
0 Error(s)
Then I run a dotnet run and receive the following error:
Error:
An assembly specified in the application dependencies manifest (apf-ws.deps.json) was not found:
package: 'System.Text.Encoding.CodePages', version: '4.3.0'
path: 'runtimes/unix/lib/netstandard1.3/System.Text.Encoding.CodePages.dll'
Nowhere in my code do I actually reference any type of Encoding explicitly. I have tried including System.Text.Encoding.CodePages in my project to see if that would add a reference and bring in the library to ignore the one it is looking for, but it doesn't help. Anyone have any ideas of what would be causing this?
I tried several things before wiping the directory out in Linux and copying the files over again. In doing so it seemed to fix the problem.