Hey Tijs, Yes, as far as I know MIT is compatible with Apache 2.0.
My only concern is at the time the Oryx components were forked for KissBPM, they were LGPL licensed.
Now, you may have pulled a newer version after Signavio abandoned the project (or at least pulled it in house) which may be MIT.

This license stuff gets really tricky when you change from one license to another. Some code is still protected by the original license, some with the new license.

The Oryx components that are part of Flowable (and of Activiti) are MIT licensed. I agree that the change from LGPL to Apache license isn’t very clear, but all of the code that’s part of the Flowable project is Apache licensed, there’s no exception. So we might have made things unclear in the past, but no it’s very easy, it’s all Apache license.

We’ll do a full scan through the sources to make sure the license headers are correct. The Oryx components should have the original license headers from the Oryx project, which is an MIT license.

Running mvn clean install -DskipTests -Pdistro from the root of the project and then from modules/flowable-ui-modeler ./start-modeler.sh should work. We also require to run the idm app for single sign-on between the different ui apps as well. You can start the idm app from the modules/flowable-ui-idm folder with ./start-idm.sh

/* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.flowable.app.filter;
import com.google.common.cache.CacheBuilder;
import com.google.common.cache.CacheLoader;
import com.google.common.cache.LoadingCache;
import java.io.IOException;
import java.util.ArrayList;

Hello!Tijs, I want to put the modeler source in my project, but after consolidation, found my original request mapping address blocked off, not normal visit, return a 403 error, what is the intercept strategy of flowable source code?What I introduced was
Gradle compile (’ org. Flowable: flowable - spring - the boot - starter - basic: 6.2.1 ‘), the compile (’ org. Flowable: flowable - UI - modeler - logic: 6.2.1 ').I springboot project, in the application class I joined @ ComponentScan (basePackages = {" com. Augurit ", “org. Flowable. App. Service”, “org. Flowable. App. The repository”}) package path scanning, the first local application path for me;This is not the problem with the introduction of flowable-spring-boot-starter-basic, which will be followed by the introduction of org.flowable:flowable-ui-modeler-logic.Please answer it, thank you very much!

There’s no current plans to move away from the Oryx core, but things can always change. There’s not another liberally licensed alternative at the moment, so that does limit options. In terms of extending the modeler, there are possibilities and we are going to do some more on this in the future.

Running mvn clean install -DskipTests -Pdistro from the root of the project and then from modules/flowable-ui-modeler ./start-modeler.sh should work. We also require to run the idm app for single sign-on between the different ui apps as well. You can start the idm app from the modules/flowable-ui-idm folder with ./start-idm.sh

Issue: mysql was not setup locally, after mysql setup i have to create ‘flowable’ user and ‘flowable’ password in db followed by ‘flowable’ database. then there was a port collision issue - have to kill other processes running on 8080 port. after all these, finally ./start-idm.sh was running successfully.