I know I don't have a m2e connector but I did configure the lifecycle mapping properly in the pom. In fact, it was working fine. But now, it keeps giving me the above error marker which indicates the goal was mapped properly but the invocation of the goal failed within eclipse. Manually executing the goal from the command line works fine (the resources generated properly). What could be the problem?
It seems to be an eclipse issue. This happened whenever I updated the plugin and installed it locally. I had to restart eclipse and clean the project to make the above error go away.
Related
I am trying to figure out how my VSIX project stopped working [VS2022]. following this article, I was able to run and debug my VSIX project with an IWizard implementation. Something changed, I'm not sure what. I can F5-run and everything works but the code executing is not the latest code and I'm unable to hit any breakpoints (VS says No Symbols have been loaded for this document). I can tell its not the latest code because of the debug console messages and the UI is an older version.
I've tried a number of things including
Clean install
Made sure I'm in debug
Removed the extension from VS, and just tried running debug from VS
Verified compiled output is in AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions\ {myextension}
Property settings are set
Assets have not changed
I did mess around adding additional install targets but I don't think this caused any issues
Any ideas how the the project can be out of sync with the code?
I could go back to the start and implement a new project but hoping someone out there can help resolve this issue. Appreciate the help.
I figured this out. I don't know why it works the way it does, but this definitely fixed the problem.
I removed ALL extensions from VS using the extensions manager interface. So, all old instances are gone (but are they?)
In my VSIXProject I would do a clean solution, rebuild, run. I verified that the latest DLL's were being output to
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Acme Project Template\1.0\VSIProject1.dll - VS Build output went here
In the debugger, when my little windows form loaded, I could tell it was old code and caught the reference in the output windows that it was loading an older version of the package.
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Multi Project Name\1.0\VSIProject1.dll - debugger loaded this
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Acme Project Name\1.0\VSIProject1.dll - debugger loaded this after deleting above
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Acme Project Template\1.0\VSIProject1.dll - VS Build output went here
After I deleted all the previous extensions in file explorer and re-ran my project, the right code executed and debugging was enabled. IDK why the older versions were picked during debugging but it's fixed. HTH someone.
I took a fully working Xcode project and added a Podfile to it. After doing the pod install, opening the newly created workspace and trying to build, it no longer works. When I compile now I get errors from a couple system header files. For example, NSFetchRequestExpression.h tells me:
Attempting to use the forward class 'NSExpression' as superclass of 'NSFetchRequestExpression'
I manually went in and added $(inherited) to the front of the "Framework Search Paths" and "Other Linker Flags" build settings. Any ideas on what I need to change to make this work?
Finally figured this out. CocoaPods actually changes the way includes work. I had a core data entity called Time, which creates and NSManagedObject subclass called Time.h. When CocoaPods mucks with the header include search paths, suddenly the system files which asked for found my time file instead. I renamed that class (which I shouldn't have had to do!) and now everything works fine.
I've gone through Jaime's deployer tutorial.
I've successfully created my deployer extension, which when integrating with SDL Tridion, the functionality works exactly as required.
But, what i can't get to work is the local debugging / running with the deployer inside eclipse (documented here)
The eclipse based deployer does run. If I drop my zip file into my test incoming folder the zip is picked up and processed. However, the customdeployer code I have written is never entered or executed.
I don't get any errors in the 'eclipse' deployer logs, but it always stops on the following line:
2012-04-13 20:24:51,642 DEBUG QueueLocationHandler - Removing exclusive lock on Deployment package: tcm:0-1026-66560 with type: CONTENT.
As we've three developers here also stuck on the same problem on all their machines I was wondering (hoping!) that this was a common problem and someone knew what we're doing wrong.
Thanks
Can you check which cd_deployer_conf.xml is it loaded by the Deployer? Just check the Deployer startup logs (in debug mode).
I suspect your Eclipse project at Debug/Run time doesn't load the the cd_*_config.xml files from the config folder in Eclipse. This will prevent your deployer module (which I supposed you configured in your cd_deployer_conf.xml) from being loaded and called.
What I normally do is to declare this config folder as an Eclipse Source Folder. Then at Debug/Run time, Eclipse will be included in the classpath automatically. This makes point #8 from http://www.sdltridionworld.com/articles/sdltridion2011/tutorials/Deployer_Extensions_With_Eclipse_3.aspx redundant.
I ran into exactly the same problem after following the same deployer extension tutorial.
I managed to solve it by changing the name of the package that my module was in to be com.tridion.deployer.extensions
Previously my module had been in a package I had named com.yourcompany.tridion.deployer.extensions and this appeared to have the affect of preventing the deployer from loading my extension module.
I had this issue, with a slight variation in that originally it worked, but then it stopped working.
Turns out the deployment package was somehow getting corrupted(locked?) in the process, as when i tried with a backup of the deployment package from the previous day it worked just fine.
I am having a trouble to get IntelliJ IDEA 9.0.2 to run FlexUnit4 tests. The tests won't be performed because of the following error:
Error: Unable to resolve resource bundle "<some name>"
So I checked the build.xml whether the path-elements are set properly:
<path-element>resources/locale/{locale}</path-element>
This is working for the normal build process perfectly fine. Therefore, I am pretty confused and would appreciate any ideas that help to get the tests to run.
The Flex libraries have resource bundles that sometimes need to be included. I added
<Flex_SDK_location>/sdks/4.1.0/frameworks/locale/en_US
to the build path and it fixed an "Unable to resolve resource bundle" error for me.
I had this same problem. I saw the suggestion in the other answer to add a path with the locale in it, and though my framework was set up correctly (and I couldn't manually edit any build path in the IntelliJ configuration), it did lead me to the problem.
Go to the "Flex" Facet in the module and click onto the Advanced tab. The problem is if the Non-default locale settings is checked and blank, then it doesn't assemble the correct path and find your framework.
To fix it, simply uncheck the "Non-default locale settings":
I have a Flex/WTP project within Eclipse that was running within Eclipse for a short time but then all of a sudden stopped working. Specifically, it was complaining about not being able to find a Java class on the server-side. I have not made any configuration or path changes to the project.
The specific error is:
[FaultEvent fault=[RPC Fault faultString="Cannot create class of type 'com.company.project.business.LoginService'." faultCode="Server.ResourceUnavailable" faultDetail="Type
But, the problem actually looks like the classes are never being published to the temp version of tomcat that Eclipse sets up for the WTP project.
Has anyone seen this case where the Eclipse/Flex/WTP project stops publishing portions of the application.
NOTE: If I export the WAR file from the project and run it on Tomcat myself, it works fine.
Any help would greatly be appreciated.
-FortPointUIGuy