Some time my project in MyEclipse show me the following error on compilation. Sometime by restarting MyEclipse the error message disappear.
Can you please tell me why this error occurs ?
Error message :
The container 'Struts 1.1 Libraries' references non existing library 'C:\MyEclipse\.......\org.eclipse.osgi\bundles\16\1\.cp\data\1.1\lib\commons-beanutils.jar' ROMO_ETD Build path Build Path Problem
Thanks a lot.
Looks like you might be using an old unsupported release of MyEclipse, so one option would be to upgrade to the latest release. Another would be to run MyEclipse with the -clean argument, once. The argument is mentioned here (for the eclipse Juno release, but it's similar for earlier releases): http://help.eclipse.org/juno/topic/org.eclipse.platform.doc.user/tasks/running_eclipse.htm?cp=0_3_0
Basically, the argument is added to the command line or to the top of the myeclipse.ini file, in the folder containing the myeclipse.exe file. The argument can be removed after the first launch, as it slows down the launch.
Related
i just wanted to publish my changes to my .Net6 blazor wasm app to azure to update it like i did a dozen times. Since yesterday that does not work anymore. I can build and run it locally with no problem but when I try to publish it, I get a window telling me:
Publish has encountered an error. Build failed. Check the Output
window for more details.
A diagnostic log has been written to the following location:
"C:\Users\user\AppData\Local\Temp\tmpE865.tmp"
Content of that file:
16.06.2022 08:20:08 System.AggregateException: One or more errors occurred. ---> Microsoft.WebTools.Shared.Exceptions.WebToolsException:
Build failed. Check the Output window for more details. --- End of
inner exception stack trace ---
---> (Inner Exception #0) Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
Check the Output window for more details.<---
Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
Check the Output window for more details.
===================
Console Output:
C:\Program Files\dotnet\sdk\6.0.400-preview.22301.10\Sdks\Microsoft.NET.Sdk.BlazorWebAssembly\targets\Microsoft.NET.Sdk.BlazorWebAssembly.6_0.targets(614,5): Error MSB6006: "dotnet.exe" exited with code 1.
Tried fetching older versions of the code that I successfully published a few days ago. Still does not work. My coworker can still publish the same code.
But I can publish my API Backend...so this error seems to be related to blazor wasm.
Tried this with the latest release of VS 2022 and just gave the preview version a try - no luck.
I've also done a repair installation of the .Net 6 SDK.
Edit: I've tried to publish my project to a folder and got the same error. So no relation to azure. Then I've created a new blank Blazor app...I can publish this one to a folder with no error. So my project is somehow broken...but even older code can't be published. This is so odd...
Same issue for me. Publish stopped working after the latest VS update.
Removing blanks in path resolved it
#XSharp is correct.
We had same issue started occurring yesterday.
We were using version '6.0.x' of DotNet which seems to have started using version '6.0.301' that seems to be causing this issue. Force it to use the previous version '6.0.106' instead
Just add the following at the top of your tasks in your YAML
- task: UseDotNet#2
inputs:
packageType: 'sdk'
version: '6.0.106'
Looks like someone has reported it as an issue when having a blank space in your project path: https://github.com/dotnet/core/issues/7548
I kept getting error "Microsoft.NET.Sdk.Blazor WebAssembly.6_0.targets(614,5): error MSB6006".
I can confirm once I removed spaces (my directory to mydirectory) on the build environment, the blazor build was successful.
In my case, changing the SDK in the YAML of the pipeline fixed the issue for us.
In UseDotNet#2 task:
Changed : version: '6.0.x'
To : version: '6.0.106'
It was working before so it seems like something has changed in the hosts.
I've had this problem off-and-on for more than a year. Sometimes it seems to be caused by a Visual Studio update and sometimes a dependency (nuget) update, but sometimes it seems spontaneous; I can't seem to figure out the real cause. This time I tried removing spaces from the path, but that did not work.
I got it to publish again after (1) removing spaces from the path, (2) deleting the publish profiles, (3) deleting the hidden ".vs" folder from the solution directory, (4) running "Clean Solution" in VS, (5) deleting all "bin" and "obj" folders from the solution tree, (6) re-importing the publish profile, building, and publishing. I wish I knew which of those really affected the problem, or better yet, I wish MS would fix this bug.
i am facing PhaseScriptExecution error
when i try to build IOS then project not build this give the following error
the following build commands failed:
PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/ali/Library/Developer/Xcode/DerivedData/NassauTennisMobileApp-akwowvjtagvlxbalhbsvukoitagy/Build/Intermediates.noindex/NassauTennisMobileApp.build/Debug-iphonesimulator/NassauTennisMobileApp.build/Script-00DD1BFF1BD5951E006B06BC.sh
For me: It seems that react native doesn't like spaces in the directory. I was able to build my ios after removing all of the spaces in my directory.
Potential solution to your problem, didn't fix mine but it might help you: The author suggests there is a mismatch between the node version that you're using and the one that xcode is calling/using. The author provides a way to check the versions installed as well as a way to symlink between the two versions => https://dev.to/glocore/react-native-command-phasescriptexecution-failed-of9
I am facing similar issue like this mentioned in the post:
Triying to run VLC for unity plugin demo
Build platform is WIN 10 x64 (build 2004).
I am using LibVLC from the nightly build: https://artifacts.videolan.org/vlc/nightly-win64-llvm/20200914-0434/
LibVLCSharp gets built successfully (https://code.videolan.org/videolan/LibVLCSharp/-/tree/master/).
I was trying to build "VLCUnityPlugin.dll" but failing (have installed https://github.com/mstorsjo/llvm-mingw/tree/20200325 (LLVM MinGW)), using MSYS64 to run ./build.sh and it was coming up with this error:
MSYS error while building VLCUnity plugin dll
I thought maybe since "VLCUnityPlugin.dll" is NOT present, Unity x64 (v 2019.4.8f1) keeps on complaining with the following errors:
UNITY errors
But after, I hacked "common" make file as shown below:
make file changes to build VLCUnityPlugin.dll
I successfully built VLCUnityPlugin.dll and my plugin file structure looks like this now:
Plugin directory structure
Still, I do see UNITY Errors:
"Assets\VLCUnity\Demos\Scripts\MinimalPlayback.cs(99,39): error CS1061: 'MediaPlayer' does not contain a definition for 'GetTexture' and no accessible extension method 'GetTexture' accepting a first argument of type 'MediaPlayer' could be found (are you missing a using directive or an assembly reference?)"
The free trial version is available for download here https://videolabs.io/vlc-unity/vlc-unity-windows-trial.unitypackage.
That being said, if you want to build it yourself, you should follow what the CI does https://code.videolan.org/videolan/vlc-unity/-/blob/master/.gitlab-ci.yml
The libvlcsharp build is a special one, you need to define UNITY when you build it. It has the added GetTexture method.
For VLCPlugin.dll, you should crosscompile from Linux, where you install llvm-mingw and run it from bash (for example). MSYS not needed.
I'm working on updating my project from using electron version 1.2.5
to the newest electron at this time which is 1.7.7 (atleast it was when I downloaded it). My node version 6.9.1.
I've encountered a problem when I start my project with this new electron version,
the error in general is about "could not locate the binding files. and it mostly regards the async module.
There is also some part of the exception regarding node-etcd module which I use in my project (version 5.0.3)
I found some information about this type of exception online but most of them says stuffs about rebuilding some node module using some npm commands which I didn't quiet understand. I tried to install async module again in a new folder and replace it (with its deps) in the node modules folder im currently using for my project, but I still got the same error.
I'm working in an offline enviorment where I can't take my project "out" to a computer with internet access, I can only bring things from the web to my project (like installing in some folder and then copying that into my project) so any npm or other commands that require web connection are not available to me directly on my work computer. (I can only use them in a different computer and copy the results to a flash drive and bring them to th
Here's 2 pictures of the error (sorry about the quality, its the best I could get):
First part of error
Second part of error
The solution that fixed the problem in my case was going into node_modules - > deasync - > index.js
Before line 31 I added a newline (next to the binding line)
and wrote:
modPath = __dirname;
This solution is hacky, it was accually ly found by an associate a while back, so I am not sure why it works, it might be an issue in deasync, but it fixed the problem.
Orchard 1.8. While I can package the default theme successfully (TheThemeMachine) Using the command line instructions from here E.g
orchard> package create TheThemeMachine C:\Temp
packaging my own themes I get the following error
"Cannot create a package that has no dependencies nor content."
(the theme indeed has content)
Anybody have the same issue ? Rookie error I'm guessing..But help much appreciated as error appears undocumented.
This error happens when you have set wrong version for the module/theme. For NuGet it's important to have correct versioning. Make sure you have version in your Theme.txt following formats {x.x}, {x.x.x}, {x.x.x.x} (where x are only digits, each up to 10)
Valid:
1.0
0.0.0.1
01.4423.455.112312
1234567890.1234567890.1234567890.1234567890
Invalid:
1
.1
1.1.1.1.1
1.12345678901