Openlaszlo migration issues - openlaszlo

When i am trying to migrate the code from OL 3.3 to 4.9 i am getting this error. I have followed the steps mentioned here.
http://wiki.openlaszlo.org/Runtime_Differences
But still i am getting this error.
[exec] Exception in thread "main" java.lang.NullPointerException
[exec] at org.openlaszlo.compiler.ClassModel.sortKey(ClassModel.java:235)
[exec] at org.openlaszlo.compiler.ClassModel.compareTo(ClassModel.java:244)
[exec] at java.util.TreeMap.put(TreeMap.java:560)
[exec] at java.util.TreeSet.add(TreeSet.java:255)
[exec] at java.util.AbstractCollection.addAll(AbstractCollection.java:334)
[exec] at java.util.TreeSet.addAll(TreeSet.java:312)
[exec] at java.util.TreeSet.<init>(TreeSet.java:160)
[exec] at org.openlaszlo.compiler.ViewSchema.resolveClassModels(ViewSchema.java:362)
[exec] at org.openlaszlo.compiler.Compiler.updateRootSchema(Compiler.java:809)
[exec] at org.openlaszlo.compiler.Compiler.compile(Compiler.java:452)
[exec] at org.openlaszlo.compiler.Compiler.compile(Compiler.java:199)
[exec] at org.openlaszlo.compiler.Main.compile(Main.java:463)
[exec] at org.openlaszlo.compiler.Main.lzc(Main.java:402)
[exec] at org.openlaszlo.compiler.Main.main(Main.java:105)
Has anyone come across the same type. Please let me know what is the solution.

The problem existed even in the 5.0 version but later by removing the dependencies one by one, i found that one of the class's default placement value is a constraint when i remove the constraint and give the proper name. The error was resolved.

Related

app:compileDebugJavaWithJavac task failing, erroring out on its own code

I'm getting this error after running npx react-native run-android, and I'm new to react and node in general so I'm not sure what could be going on.
gradle build --warning-mode all runs successfully with no issue. Not sure what could be going on. Running react-native upgrade doesn't help as suggested in similar questions, but it does give the error "Accessing non-existent property 'padLevels' of module exports inside circular dependency", though I think it's unrelated.
I'm on npm 6.14.10, node v14.15.4, Gradle 6.4, react-native-cli 2.0.1, react-native 0.63.4, openjdk 14.0.2
> Task :app:compileDebugJavaWithJavac FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.4/userguide/command_line_interface.html#sec:command_line_warnings
106 actionable tasks: 2 executed, 104 up-to-date
/android/app/src/main/java/com/test/MainApplication.java:20: error: cannot find symbol
return BuildConfig.DEBUG;
^
symbol: variable BuildConfig
/android/app/src/main/java/com/test/MainApplication.java:59: error: cannot find symbol
if (BuildConfig.DEBUG) {
^
symbol: variable BuildConfig
location: class MainApplication
/android/app/src/main/java/com/test/MainApplication.java:59: error: illegal parenthesized expression
if (BuildConfig.DEBUG) {
^
Note: /android/app/src/debug/java/com/test/ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

Building Nuxeo source code, dart issue

I am trying to build nuxeo source code & noticing below build issue. I noticed similar reported issue here. Has anyone faced similar issue?
Build error:
[exec] Transform Dart2JS on nuxeo_api_playground|web/index.web_components.bootstrap.dart threw error: type 'PrefixElementX' is not a subtype of type 'MemberEntity' in type cast where
An Ant BuildException has occured: The following error occurred while executing this line:
[ERROR] /Users/kalava/Documents/Work/DAM/NuxeoOpenSource/nuxeo/addons/nuxeo-api-playground/src/main/dart/build.xml:9: exec returned: 65
[ERROR] around Ant part ...... # 4:278 in /Users/kalava/Documents/Work/DAM/NuxeoOpenSource/nuxeo/addons/nuxeo-api-playground/target/antrun/build-main.xml
Do you have the proper Dart version, as documented at https://doc.nuxeo.com/corg/installing-dart-and-related-tools/? Currently Nuxeo build requires Dart 1.23.x.

Unable to make Mod_mono in Red Hat even after configure has completed without errors

I have successfully run the configure script for mod_mono, but get multiple error messages while making mod_mono in my RHEL 5 server. I ran configure with the following options: ./configure --with-apr-config=/usr/local/bin/apr-1-config --with-apu-config=/usr/local/bin/apu-1-config --with-apxs=/usr/local/bin/apxs --prefix=/usr/local
I have apache 2.4.6 installed along with mono 2.10.2. These are my error messages from make:
mod_mono.c: In function âapache_get_useridâ:
mod_mono.c:389: error: âunixd_configâ undeclared (first use in this function)
mod_mono.c:389: error: (Each undeclared identifier is reported only once
mod_mono.c:389: error: for each function it appears in.)
mod_mono.c: In function âapache_get_groupidâ:
mod_mono.c:399: error: âunixd_configâ undeclared (first use in this function)
mod_mono.c: In function âapache_get_usernameâ:
mod_mono.c:409: error: âunixd_configâ undeclared (first use in this function)
mod_mono.c: In function âensure_dashboard_initializedâ:
mod_mono.c:488: warning: implicit declaration of function âunixd_set_global_mutex_permsâ
mod_mono.c: In function âconnection_get_remote_portâ:
mod_mono.c:854: warning: implicit declaration of function âapr_sockaddr_port_getâ
mod_mono.c:854: error: âconn_recâ has no member named âremote_addrâ
make[1]: *** [mod_mono_la-mod_mono.lo] Error 1
I am totally stuck at this point and have been searching for a solution for days, but to no avail. Any help in this regard would be much appreciated.
I have resolved my issue. The easiest way is to install monodevelop using yum by following the steps mentioned in the below url :
http://mostlylinux.com/tmp/?p=91

Ant LibusbJava compile error: "jni.h: No such file"...fixed, now a memset error

There appears to be a Ant / jni.h problem (for my setup) with LibusbJava. I get the following error when setting up LibusbJava by running
ant linux
in CentOS 6.3 as root (quick and dirty test, thanks for those concerned about user level =0). I will redo with proper restrictions as shown on a libusbjava reference after reflection when first install works. LibusbJava, is a Java wrapper for the libusb library.
The output starts out like this:
[root#somebox LibusbJava]# ant linux -lib $JAVA_HOME/include -lib $JAVA_HOME/include/linux
Buildfile: build.xml
clean:
Build LibusbJava Test Linux:
Build LibusbJava Test:
[echo] Building Library for unit tests:
[exec] /.../libusbjava/trunk/LibusbJava/LibusbJava.cpp:27:17: error: jni.h: No such file or directory
[exec] /.../libusbjava/trunk/LibusbJava/LibusbJava.cpp:34:26: error: test/CuTest.h: No such file or directory
`...`
as it was not set on my system. It appears that jni.h is a header called by C++ code, which I had to add to the LibusbJava.cpp file. This is the new include, /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/include/jni.h. I then get an error with jni.h not being able to fine jni_md.h which is an include in jni.h #include "jni_md.h".
Clearly this is not the right approach, so perhaps I need a correct Ant reference, but I cannot seem to do it with a -lib switch. Besides, this just creates thousands of jni.h file errors during the Ant build attempt.
How can I fix this problem?
Notes: I've set$JAVA_HOME up like JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64 and javac and java work fine.
New discovery... after helpful questions which guided me, I am much closer to successful compilation.
When I install LibusbJava and manually install all the library references in build.xml there is still an error compiling the LibusbJava based on a memset error. I see memset patches for libusb that appeared in 2007 and it's unclear how to use or if they relate. Investigating... Hints, comments and questions welcome. My most sincere thanks for the help thus far.
[exec] /.../libu/libusbjava/trunk/LibusbJava/objects/Usb_Device.cpp: In function ‘void Usb_Device_disconnect(JNIEnv*)’:
[exec] /.../libu/libusbjava/trunk/LibusbJava/objects/Usb_Device.cpp:88: error: ‘memset’ was not declared in this scope
[antcall] Exiting /.../libu/libusbjava/trunk/LibusbJava/build.xml.
BUILD FAILED
but I find no referece to an include string.h or cstring. The header of Usb_Device.cpp mentions it is a C++ Stub for the java class of a java class ch.ntb.inf.libusbJava.Usb_Device. which only has this include #include "Usb_Device.h" which also does not appear to have a string include. Perhaps just insertion of#include`?

ant build script for behat error

I am trying to setup an ant build script for behat tests so I can run them from jenkins. When I run behat from the command line with bin/behat or ./bin/behat, the output works as expected. But when I use the following ant script
<project name="behat" basedir=".">
<exec dir="bin" executable="./behat">
</exec>
</project>
I get this error:
Buildfile: <mydir>/build.xml
[exec]
[exec]
[exec]
[exec] [RuntimeException]
[exec] Context class not found.
[exec] Maybe you have provided wrong or no `bootstrap` path in your behat.yml:
[exec] http://docs.behat.org/guides/7.config.html#paths
[exec]
[exec]
[exec]
[exec] behat [--init] [-f|--format="..."] [--out="..."] [--lang="..."] [--[no-]ansi] [--[no-]time] [--[no-]paths] [--[no-]snippets] [--[no-]snippets-paths] [--[no-]multiline] [--[no-]expand] [--story-syntax] [-d|--definitions="..."] [--name="..."] [--tags="..."] [--cache="..."] [--strict] [--dry-run] [--rerun="..."] [--append-snippets] [--append-to="..."] [features]
[exec]
[exec]
[exec] Result: 1
BUILD SUCCESSFUL
Total time: 0 seconds
You shouldn't be running behat from the bin directory. It won't find your behat.yml file.
You should either run it like this:
./bin/behat
or pass a path to the config file:
cd bin
./bin/behat --config ../behat.yml
I haven't tried the later. Your ant script might look something like:
<project name="behat" basedir=".">
<exec dir="${basedir}" executable="./bin/behat" />
</project>
I took ant out of the equation and just used jenkins to run the behat commands directly:
cd <mydir>
bin/behat
One thing I need to check is the build from jenkins returns failed, but it may be due to the behat tests are failing.

Resources