I am using angular2-datatable version 0.6.0 in my angular application which used
Angular Version 2.
We upgraded Angular to use 13.2.0 recently, the application build and compiles successfully.
But I see some console error when I did ng serve.
The errors are related to angular2-datatable saying that is is not compatible with Ivy.
The error is shown below.
Error: node_modules/angular2-datatable/lib/DataTableModule.d.ts:1:22 - error NG6002: Appears in the NgModule.imports of XXXXXXX, but could not be resolved to an NgModule class.
This likely means that the library (angular2-datatable) which declares DataTableModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
I see the latest version of angular2-datatable is 0.6.0.
I tried changing "aot": true or false in Angular.json file and also modified "enableIvy" property in tsconfig.json to true or false, nothing seems to clear those errors.
Any clue on how to resolve this..
In angular.json setting both buildOptimizer and aot properties to false did the job for me.
Related
I am using logback-classic 1.3.5 in my project but it is giving me UnsupportedOperationException. My project is on JDK 8 and when I saw in manifest file of logback-classic-1.3.5, it shows build-jdk-spec version as 19. I just want to know what exactly this "build-jdk-spec" version specifies
The build-jdk-spec attribute is a "default" attribute added by the Maven "maven-archiver-plugin" (reference). The value is the value of the ${java.specification.version} property for the build. It is (I think) the JDK version of the JVM that was running the build tool (Maven).
The [build-jdk-spec] version number most likely doesn't signify anything that is relevant to your problem. (It is NOT the the target Java version for the build!!)
The real cause of your problem can be deduced by looking at the details of the UnsupportedOperationException stacktrace.
after I upgraded constraintLayout version from 1.1.2 -> 2.0.0-alpha2
I'm getting this error
java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource compilation failed
/Users/x/.gradle/caches/transforms-1/files-1.1/appcompat-v7-28.0.0-rc01.aar/
d5741c4d219b7f0eeb18436ff6f46f63/res/values/values.xml:1104:5-1169:25: AAPT: error: duplicate value for resource 'attr/mode' with config ''.
/Users/x/.gradle/caches/transforms-1/files-1.1/appcompat-v7-28.0.0-rc01.aar/
d5741c4d219b7f0eeb18436ff6f46f63/res/values/values.xml:1104:5-1169:25: AAPT: error: resource previously defined here.
appCompat version is v7:28.0.0-rc01
this issue is reproducible on AS 3.3 canary 3 & 3.2 stable & 3.1.4 & 3.0.1 version
how can I figure out this issue?
The error message looks like the kind you can get if you mix Android X with Support Library, at least that is how it was when I found it.
If you use any Android X dependencies, you can't use any of the old Android Support Library dependencies, or else you're going to get duplicate resources and other problems when merging them all into one apk.
Make sure you are on either all Android X, or all Support Library. If you're moving to Android X, make sure you have
android.useAndroidX=true
android.enableJetifier=true
in your gradle.properties so that your other dependencies get treated as if they were Android X.
why you use appcompat-v7-28.0.0-rc01 instead of appcompat-v7-28.0.0 ?
or even androidx.appcompat:appcompat:1.0.0 ?
rc01 means release candidate; for testing purposes only.
I'm attempting to transform a Swift v1.2 project into a Swift v2.0 project via Xcode 7.0.
I got this during the build:
Swift had fatal errors constructing the ast context for this module:
missing required module 'SwiftShims' Debug info from this module will
be unavailable in the debugger.
What is the module 'SwiftShims'?
And how would I install it if it is missing?
I was getting a similar error message regarding the SwiftShims module, so this is probably only a partial solution to your case.
I had to clean all the user data Xcode was using and empty all caches. This did the job for me:
How to Empty Caches and Clean All Targets Xcode 4
I am trying to implement uglifyjs-maven-plugin.
While using the configuration mentioned here, I am getting error like sourceDirectory is undefined or invalid.
Using the configuration like
<configuration>
<sourceDirectory>target/snapshot/javascript</sourceDirectory>
<outputDirectory>target/snapshot/javascript</outputDirectory>
</configuration>
its working fine. But how will I add exclude file list in the above configuration.
I have a js file of 900kb, when i am including that js file inside source directory, i am getting exception during maven build as " Exception in thread "main" java.lang.StackOverflowError". Can anyone help me out of this.
It looks like that while the documentation (and probably the current implementation) supports file exclusions, the version available in the repository (1.0) is older and supports only sourceDirectory.
I have not found any newer version published anywhere, so I guess the best thing we can do is compile the latest version of the plugin manually and see if it supports what the documentation says.
I have recently updated my STS from 2.5.2 to 2.6. Since then, each grails project shows an error in the conf/spring/resources.groovy file reading: Description Resource Path Location Type
Internal compiler error: java.lang.VerifyError: (class: org/codehaus/jdt/groovy/internal/compiler/ast/JDTClassNode, method: initialize signature: ()V) Bad access to protected data at org.codehaus.jdt.groovy.internal.compiler.ast.JDTResolver.createClassNode(JDTResolver.java:461) resources.groovy /GrailsProject/grails-app/conf/spring line 0 Java Problem
The resources.groovy file is as good as empty (in default state), and if I delete it, the error is shown on the DataSource.groovy, so the file itself seems not to be the cause.The used groovy compiler version is 1.7.3.I have made a clean STS 2.6 install, installed the groovy and grails plugins and got the same error.What could be the problem? And is there a solution to this not resulting in downgrading to 2.5.2 again? Thank you
Take a look at your preferences Groovy -> Compiler. Are you by any chance accidentally using Groovy 1.6?
EDIT
That didn't solve the problem, but as described in http://forum.springframework.org/showthread.php?p=357361, upgrade to the latest dev build of Groovy-Eclipse as well as Grails Tooling and that should work.