I get this annoying bug after upgrading Intellij IDEA from version 2019.1
to version 2019.2.1 or later
When compiling my code using the IDEA maven build tool, I now can't manage to navigate to the source file containing the error (from clicking at one of the errors out of the list of found errors listed on the side).
Update: a bug was submitted 2 days ago at jetbrains support: https://youtrack.jetbrains.com/issue/IDEA-220999
When I run maven compile from the the maven window, I expect my
compilation errors to be in the run window with hyperlinks that take
to the compilation error in the source file. Since upgrade to version
2019.2 I can't get this functionality anymore. The screen shot below is where I just reproduced the error and you can see there are no
hyperlinks
In order to solve:
edit the file: ~/.IdeaIC2019.2/config/options/other.xml
change these stored values:
<property name="build.toolwindow.Build Output.selection.state" value="consoleView" />
<property name="build.toolwindow.Sync.selection.state" value="consoleView" />
<property name="build.toolwindow.run.selection.state" value="consoleView" />
to be:
<property name="build.toolwindow.Build Output.selection.state" value="com.intellij.build.BuildTreeConsoleView" />
<property name="build.toolwindow.Sync.selection.state" value="com.intellij.build.BuildTreeConsoleView" />
<property name="build.toolwindow.run.selection.state" value="com.intellij.build.BuildTreeConsoleView" />
save&restart Intellij
Related
React native application. Despite having entered in the manifest android:exported="true" i still have this problem in the build phase. It almost seems that some installed plugins did not insert it.
I read in some posts that proposed as a temporary solution to downgrade to version 30 of the android SDK, but i cannot because with that version it does not allow me to compile.
React Native 0.68
Android SDK version 33
Android Gradle Plugin version 7.3.0
From Merged Manifest
Error: android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for android:exported when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details. mobile_app.app debug manifest, line 26 Error: android:exported needs to be explicitly specified for element <activity#androidx.test.core.app.InstrumentationActivityInvoker$EmptyFloatingActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for android:exported when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details. mobile_app.app debug manifest, line 33
Based on the response from Aleja Duque-Torres, here's a temporary solution by adding the following code segment to your AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="...your package name"
xmlns:tools="http://schemas.android.com/tools"> <!-- ADD THIS LINE -->
<!-- Other Content -->
<application
.../>
<!-- ADD STARTS HERE -->
<activity
android:name="androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity"
android:exported="false"
tools:replace="android:exported"/>
<activity
android:name="androidx.test.core.app.InstrumentationActivityInvoker$EmptyActivity"
android:exported="false"
tools:replace="android:exported"/>
<activity
android:name="androidx.test.core.app.InstrumentationActivityInvoker$EmptyFloatingActivity"
android:exported="false"
tools:replace="android:exported"/>
<!-- ADD ENDS HERE -->
</application>
</manifest>
Then do a build folder clean and run the project again. Hope this helps!
P.s. my guess is that this problem is due to some dependency package getting messed up. If someone else has any insight please feel free to shed some light on it!
solution:
In Git-bash run: * ./gradlew assembleDebug --stacktrace --info | tee my-logs.txt
Search "InstrumentationActivityInvoker"
Open file and add android:exported="true" on activity
Same issue, But I can't know the reason for it. It happens when I have updated macos, Do you have any information?
First ,it works well when the config is :
<property name="location" value="./files/store"/>
But could't get anything when I changed it to
<property name="location" value="~/tem/files/store/"/>
and copy all the files to ~/tem/files
why?
Support for relative file store paths is not available yet. However, I've created an issue to track your issue and I already have a fix for it which I'll submit in the next few minutes.
I'm using specflow v1.9.0 Baseclass.Contrib.SpecFlow.Selenium.NUnit v1.3.1 and when I try to build the project, I'm seeing the below error
`#error Generation error: Unable to find plugin in the plugin search path: Baseclass.Contrib.SpecFlow.Selenium.NUnit. Please check http://go.specflow.org/doc-plugins for details.`
And in the App.config I got the below code
<specFlow>
<unitTestProvider name="SeleniumNUnit" />
<plugins>
<add name="Baseclass.Contrib.SpecFlow.Selenium.NUnit" path="..\packages\Baseclass.Contrib.SpecFlow.Selenium.NUnit.1.3.1\tools" />
</plugins>
<stepAssemblies>
<stepAssembly assembly="Baseclass.Contrib.SpecFlow.Selenium.NUnit.Bindings" />
</stepAssemblies>
</specFlow>
I encountered a similar error but with a different plugin and the steps outlined in Unable to find plugin in the plugin search path: SpecRun when saving / generating feature files resolved it for me:
1. Make sure the NuGet folders are properly restored.
2. Close Visual Studio.
3. Delete the bin\Debug folder from your project(s).
4. Reopen your solution in Visual Studio.
Make sure that in the given path the file "Baseclass.Contrib.SpecFlow.Selenium.NUnit.SpecFlowPlugin.dll" exists.
When are your *.feature.cs files generated? When you save the file or at build?
If it is at saving, regenerate the code behind file.
The solution above didnt work for me. The issue was only resolved when I've tried the following:
Go to VS->Tools->Options
Go to SpecFlow
Go to Test Execution
Change Test Runner Tool to something else than SpecRun and Auto (NUnit, MS...)
Build the project. This time it should work.
Change the Test Runner Tool back to SpecRun
Enjoy :)
Test Runner Tool option in Tools->Options
Still if you are facing same issue uninstall the plugin Baseclass.Contrib.SpecFlow.Selenium.NUnit and install it again
I have a project in ASP.NET MVC 3, the solution file contains 28 projects in total. This all is in a directory which is configured with tortoise SVN to always get the latest updates from SVN.
I have also installed curisecontrol on my VPS box, where these whole solution exist. I have also created a website in my IIS and everything is in order now.
Can anyone guide me into some tutorials for the following:
How to setup curise control web dashboard, so my clients can have look on the builds and its reports
How to use MSBuild with Cruise Control in some step by step tuts
Any sample build script with following features
Email notification on build fail or successful build
stop the deployment if build is not successfull and create a build report
Thanks in advance
How to use MSBuild with Cruise Control in some step by step tuts
http://www.codeproject.com/Articles/12985/Practical-NET2-and-C-2-An-introduction-to-MSBuild
By default, the web dashboard of ccnet displays the result of build without exact error messages. To display the error in web dashboard, go to “C:\Program Files\CruiseControl.NET\webdashboard” and open file “dashboard.config”.
There, you will find the below code:
Collapse | Copy Code
xsl\header.xsl
xsl\modifications.xsl
xsl\unittests.xsl
xsl\MsTestSummary.xsl
xsl\fxcop-summary.xsl
xsl\NCoverSummary.xsl
xsl\SimianSummary.xsl
xsl\fitnesse.xsl
Now add this line in the above code:
Collapse | Copy Code
xsl\compile-msbuild.xsl
Therefore the code will become:
<buildReportBuildPlugin>
<xslFileNames>
<xslFile>xsl\header.xsl</xslFile>
<xslFile>xsl\modifications.xsl</xslFile>
<xslFile>xsl\compile-msbuild.xsl</xslFile>
<xslFile>xsl\unittests.xsl</xslFile>
<xslFile>xsl\MsTestSummary.xsl</xslFile>
<xslFile>xsl\fxcop-summary.xsl</xslFile>
<xslFile>xsl\NCoverSummary.xsl</xslFile>
<xslFile>xsl\SimianSummary.xsl</xslFile>
<xslFile>xsl\fitnesse.xsl</xslFile>
</xslFileNames>
</buildReportBuildPlugin>
We can also send the email to the user groups if the build fails.
<workingDirectory>D:\Projects\TheWorks\Applications\ProjectFolder</workingDirectory>
<buildArgs>ProjectName.msbuild /p:Configuration=Debug</buildArgs>
<timeout>1800</timeout>
<!-- 30 minutes -->
<logger>C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MSBuild.dll
</logger>
</msbuild>
</tasks>
<publishers>
<statistics />
<xmllogger />
<email from="EMAIL ADDRESS" mailhost="HOSTNAME"
mailhostPassword="PASSWORD" mailhostUsername="USERNAME"
includeDetails="true">
<users>
<user name="Jitendra Zaa"
address=ilovenagpur#gmail.com
group="AdminGroup" />
<user name="Santosh Karemore"
address=santosh.karemore#gmail.com
group="AdminGroup" />
<user name="Manoranjan sahoo"
address=manoranjan.sahoo#gmail.com
group="AdminGroup" />
<user name="Minal Shirsikar"
address="admin#shivasoft.in" group="Emul" />
</users>
<groups>
<group name="Emul" notification="failed" />
<group name="AdminGroup"
notification="failed" />
</groups>
</email>
</publishers>
</project>
The tags are self explanatory.
There may be following types of notification:
Failed
Fixed
Always
How to setup curise control web dashboard, so my clients can have look on the builds and its reports
-> you have to set a pwd in dashboard config file first and in web page, after set pwd you will be able to add plugin to make report like build report project report unit test report nant report check this url http://www.codeproject.com/Articles/70955/Set-up-the-Web-Dashboard-of-CCNet-to-Display-the-C
in ccnet documentation you will see all samples and step:
http://confluence.public.thoughtworks.org/display/CCNET/Documentation
I have a simple CXF RS bundle deployed in Fuse 4.2 that works fine upon initial installation. But, when I update or re-install the bundle, the REST service in no longer accessible.
I tried a various configurations and found that using cxf-extension-osgi was the issue...
from this...
<import resource="classpath:META-INF/cxf/osgi/cxf-extension-osgi.xml"/>
to this...
<import resource="classpath:META-INF/cxf/cxf-extension-http-jetty.xml"/>
Also, I updated the address to be non-relative...ending up with this configuration (that works after bundle restarts, etc)
<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-jaxrs-binding.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-http.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-http-jetty.xml" />
<jaxrs:server id="testService" address="http://localhost:9000/">
<jaxrs:serviceBeans>
<ref bean="testBean" />
</jaxrs:serviceBeans>
</jaxrs:server>
Any idea what is causing this issue when using cxf-extension-osgi? Also, what is the trade-off when using cxf-extendsion-http-jetty instead (functional, performance, etc)?
thanks
Sorry, it seems to be error in cxf/servicemix integration. The problem is, cxf tries to register service under the address that is already used (by older version of this service).
Both REST and SOAP services are unaccessible after bundle restart/update. Restart of whole servicemix. Hovewer, when business logic is in other bundle, and the bundle with SOAP/REST service contains only interface, restart is needed only when interface has changed.
We were fighting with this error long, but unfortunatelly without effort.
I just tested this in Fuse 4.3.0-fuse-03-00 and it seems to work fine. The related issue below must have addressed my issue as well...
https://issues.apache.org/jira/browse/CXF-2947