After using the install guide provided by Chon I wasn't able to edit any report. The error I'm getting is
Description Resource Path Location Type The library with the namespace
"MaximoSystemLibrary" is not
found. poprint.rptdesign /MaximoReport/PO line 2 Report Problem
I already tried solutions explained by Cherin in his answer here
Please verify that the MaximoSystemLibrary is located in the Libraries folder of your Workspace.
/Workspace/libraries/MaximoSystemLibrary.rptlibrary
Related
The requirement is to use of the node modules in my controller file of a UI5 app. I've installed the module and it resides in my npm_module folder. Based on the below blog, I've added some configurations in my ui5.yaml, yet I get the error pasted below.
Can anyone help me in this regard?
Blog Referred: https://blogs.sap.com/2020/07/30/project-shims-using-npm-modules-with-ui5/
Code screenshot
Error: failed to load 'thirdparty/aws-sdk.js' from resources/thirdparty/aws-sdk.js: script load error
Update: The issue was the path mentioned in the controller. I changed it to refer to the dist folder where the actual aws-sdk.js existed. And it resolved the error.
I want to create an Eclipse installer which installs an Eclipse that doesn't show a welcome page.
This blog post suggests to create a settings file with a ResourceCreationTask:
<setupTask
xsi:type="setup:ResourceCreationTask"
id="rtt.suppress.welcome.page"
content="eclipse.preferences.version=1\nshowIntro=false"
targetURL="${workspace.location|uri}/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.prefs"
encoding="UTF-8">
<description>Suppress showing of the Welcome page.</description>
</setupTask>
The author then adds a comment that this leads to a problem because ${workspace.location} is undefined during installation. The suggested solution however is to replace ${workspace.location} with ${install.location}/ws. That would create a file in a subdirectory of the install location and doesn't help unless this location happens to be the workspace.
Another suggestion is to targetURL="${osgi.instance.area|file}.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.prefs". That doesn't help either.
Unfortunately I was unable to find a documentation on which variables can be used with Oomph.
I added a build step for my project in teamcity which consists on using the plugin Parasoft Findings to publish an XML report of all the code violations. the problem is that teamcity is failing to parse XML report. It says there is an unexpected report format and to see log (which I couldn't find).
I already checked the report location pattern which is right. I don't use SOAtest but C++ test so I only put "Parasof analyzers 10.x" for the report type
I'm sorry but you did not provide any additional details regarding your question and it's hard to help you.
Please, provide:
error message
your configuration of build step and version of TeamCity and C++test
command line used to start C++test ( if you are using variables,
replace variables with real values used in your run)
By log I think, you should check your build step log, and provide us the right content.
You can find such logs on two different ways:
You can download it by clicking "Download full build log" on build
log page (Recommended).
Try to find the raw output from the build agent by looking in the
agents logs directory, for example in
c:\TeamCity_dir_agent\logs\teamcity-build.log
Following article from JetBrains' TeamCity manual might good point to start
Edit:
Parasoft updated the plugin which fixed the issue:
https://plugins.jetbrains.com/plugin/9949-parasoft-findings
I have the same issue. Error messages in build log:
Unexpected report format: <path-to>\report.xml. See log for details.
Failed to parse XML report
Failed to parse XML report
Step test results (Parasoft Findings) failed
teamcity-agent.log and teamcity-build.log are having no entries within this build step because there is no piece of code which would write that into during this error case.
Edit/Workaround:
In the report the node <ExecutedTestsDetails> must be below the node <Exec>. The node still has the right indendation but it is at the same level as <Exec>. The xsl of TeamCity Plugin works perfectly if you fix the report xml manually.
To make it work you can add the Build Feature "File Content Replacer" like that:
Regex: (?s)(<ExecutedTestsDetails.*?<\/ExecutedTestsDetails>).*?(<Exec.*?>)
Replace with: $2 $1
I have installed Jasper reports server 6.3.0 along with Icinga-reporting (from the git repo)
I can run sample reports without any problem, but when I try and run specific Icinga reports which have a time period they fail and error out with;
Errors were encountered when compiling report expressions class file: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: calculator_Service32activity32report32in32given32time_1484836971660_629753: 13: unable to resolve class org.icinga.reporting.DateHelper # line 13, column 1. 1 error .
If you want the full stack trace please leave a comment and I will update the question.
I have done lots of googleing and have found afew links which reference the issue, but no one has actually said in (still valid) steps how to resolve the problem.
This looks like the closest fit - but the info referenced no longer exists (The entire Icinga wiki has been removed!)
I also found this but it links to very old jars which I've included in the WEB-INF/lib path but still getting the same error.
If I run a report that does not have a time/date then the report works (So I know Jasper is actually working)
If you need any additional info please leave a comment & I will update the question.
The problem turned out to be cause by icinga-reporting.jar missing from the tomcat WEB-INF/lib/ folder.
When you build icinga-reporting.jar it includes the org.icinga.reporting.DateHelper functions that where the cause of the original error.
When I installed the reporting the post deployment scripts where run and I'm sure it had copied the .jar file to the correct path, but when I later searched for it it was missing...
Manually copying the file to the correct path resolved the issue & reports with a time/date element now run without errors.
I have a label in my project
When I queue a build, and put the label in the "Source Version" field, prefixed with a L, it always comes up the following error:
500: TF14064: Could not find label mylabel#$/.
Anyone been able to get this functionality to work?
Most likely the problem is that your label is not collection-scoped and therefore you need to provide a scope with your label. If you created your label in Visual Studio, the scope is probably project-scoped. So for example if your label is 'mylabel' and your project name is 'myproject' then in the Source Version field you should enter this:
Lmylabel#$/myproject
Here are a couple links that help explain labels and scopes if you are interested.
https://msdn.microsoft.com/en-us/library/9ew32kd1(v=vs.100).aspx
http://teamfoundation.blogspot.com/2008/03/label-scope-revealed.html
I'll update the Microsoft Connect Page with this information too.
I can reproduce this issue and have help you submit a feedback on Microsoft Connect Page, you can track the status here: https://connect.microsoft.com/VisualStudio/feedback/details/2345698/500-tf14064-could-not-find-label-error-occurs-when-queue-a-build-with-specified-label
I was facing the same issue for TFS build and the error says like: “Cannot find the current label tfs build”.
How to resolve the issue:
Go to Configuration of your TFS build
Make the Label sources as true
Build the solution now and it's building fine.
Please reach out if any issues.