+1
Answered

How to start this project in locally

Tejeswar Reddy V 2 years ago updated by Nguyen 2 years ago 8

I followed the steps and clonned the project from https://community.mycollab.com/docs/developing-mycollab/setup-mycollab-projects-with-intellij-ide/

but in Run MyCollab

This is the error in the console "DefaultServerRunner" is in mycollab-server-runner is having the main class


"C:\Program Files\Java\jdk-10.0.1\bin\java.exe" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2018.3.2\lib\idea_rt.jar=58705:C:\Program Files\JetBrains\IntelliJ IDEA 2018.3.2\bin" -Dfile.encoding=UTF-8 -classpath C:\Users\pavan\work\MyCollab\mycollab-app-community\src\main\installer-resources\executor.jar com.mycollab.server.DefaultServerRunner
Error: Could not find or load main class com.mycollab.server.DefaultServerRunner
Caused by: java.lang.ClassNotFoundException: com.mycollab.server.DefaultServerRunner

Process finished with exit code 1

Under review

If you want to run MyCollab in the IntelliJ then you should follow the instruction in the above link.

If you want to run MyCollab outside the IntelliJ. For example, you customized MyCollab, and you want to create the zip file as you downloaded the MyCollab library, then you follow this link to create the zip file https://community.mycollab.com/docs/developing-mycollab/create-the-mycollab-installer/

Does it make sense?

No im saying that i used that link to setup in intelliJ

but i was getting an error.

"C:\Program Files\Java\jdk-10.0.1\bin\java.exe" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2018.3.2\lib\idea_rt.jar=58705:C:\Program Files\JetBrains\IntelliJ IDEA 2018.3.2\bin" -Dfile.encoding=UTF-8 -classpath C:\Users\pavan\work\MyCollab\mycollab-app-community\src\main\installer-resources\executor.jar com.mycollab.server.DefaultServerRunner
Error: Could not find or load main class com.mycollab.server.DefaultServerRunner
Caused by: java.lang.ClassNotFoundException: com.mycollab.server.DefaultServerRunner

Do you want to run in the IntelliJ or out of the IntelliJ?If you only want to run the MyCollab in the IntelliJ then you follow the instruction in the link to set up IntelliJ such as configuring DefaultServerRunner as main class, setting up the working directory, etc.


We don't use the executor.jar to run MyCollab. The executor.jar is only used to run MyCollab outside the IntelliJ (such as in our distribution) as it will load the MyCollab libraries in the specific order (lib folder), and use to start / stop MyCollab process.

In your question, I saw you use the executor.jar file and it is not our intention to use this file in IntelliJ.

i want to run in IntelliJ but the steps in that link are not sufficient.
i'm running the com.mycollab.server.DefaultServerRunner file but i got that error. 

i used 

not sure why it is showing executor.jar
do i need to rebuild the application like mvn clean package under the subproject "mycollab-deployer-community"
i didn't use executor.jar 

it should work with this configuration! you should rebuild the entire application as you said then run MyCollab again. Then give me the log in the IntelliJ profile if the issue is persisted. 

thank you Nguyen.
after the entire build and run in IntelliJ. It started working.

Does this has any mobile application?



and let me know who can i join in your team to contribute any stuff.

Thanks

Answered

We don't have a dedicated mobile app. We refactor the MyCollab and version it as 7. We will remove the mobile application (module mycollab-mobile), and redesign the layout to support responsive layout for mobile, tablet and desktop. Maybe in the future, we will have a mobile app, but it is not our goal now. 

We are refactoring the code in this new branch https://github.com/MyCollab/mycollab/tree/newdist and we change a lot, from the UI architect, layout, libraries, and it is rather messy now :). I think if you want to contribute then you can consider providing the solution to make MyCollab can run on multiple databases such as H2, Postgre, MS SQL Server, Oracle. It is an important task we are planning to do in the new release, and it is independent of the current codebase. However, it is not an easy task.