I have built the source code (4.5.3). I have built it in the order orbit and all its patch releases and kernel and all its patch releases and platform and built directly greg 4.5.3 version and my built was successful. But, how can I configure that in developer studio IDE ?
I am trying to import as Existing WSO2 Projects into workspace and I started importing orbit first and then kernel, so after importing kernel I have many build path errors like 'Project 'kernel_4.0.5' is missing required library: 'core/feature-manager/org.wso2.carbon.feature.mgt.core/4.0.0/target/org.wso2.carbon.feature.mgt.core-4.0.0.jar' and like wise many of them. And When I try to import platform I am getting - resource'/${artifactId}' already exits. So, how to configure WSO2 Governance Registry(4.5.3) into IDE ?? Please help !
Take a look here at this similar question - in particular read the comments.
I don't think WSO2 developers import the whole source tree into eclipse, instead they only import the maven modules that they need to work on. Also, don't import the modules into eclipse using the maven eclipse plugin. Instead, run mvn eclipse:eclipse on the module and then import the module as a general project. Don't import as a maven project.
Related
I'm building a django application using Pyinstaller.
When I run the application i get an error from dapne server.
"daphne\server.py:13: UserWarning: Something has already installed a non-asyncio Twisted reactor. Attempting to uninstall it; you can fix this warning by importing daphne.server early in your codebase or finding the package that imports Twisted and importing it later on."
In addition, when I compare the console log of the EXE application and a regular run of the django application I notice the following difference.
In the regular run which works as expected I see the following print:
"Django version 2.1.5, using settings 'cfehome.settings'
Starting ASGI/Channels version 2.1.5 development server at http://0.0.0.0:8000/"
however, when I run the application from the EXE I see:
"Django version 2.1.5, using settings 'cfehome.settings'
Starting development server at http://0.0.0.0:8000/"
Appreciate any lead to understand this behavior and ways to fix it.
I know this is old but for others seeking answer. There's a simple fix:
Before importing raven in settings.py, import daphne.server So, your settings.py will look like this:
import daphne.server
import raven
For further information you can read: https://github.com/django/channels/issues/793
I hope it will help.
I'm following a tutorial to create a cross-platform app using xamarin.forms
except that I'm using Windows 7 and hence I skipped those steps for UWP part.
Now when I trying to build the solution, I'm getting the below error message
1> No way to resolve conflict between "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
Based on findings on the net it seems that something to do with versioning messed up however this should not happen as it's a new solution from scratch.
I've also checked the properties that stated as below:
- "Compile using android version (Android 7.1(Nougat))"
- Android Manifest "Target Android version" Use compile using SDK version
Well to be exact, the build was successful but with error logging as output. Please refer to below image
May I know what else I can try?
You can fix this by issuing an update-package -reinstall command in the Package Manager Console.
Make sure that your Xamarin (Visual Studio) installation version is the same as the Xamarin NuGet packages your using.
I recommend to:
Update Xamarin and your Xamarin NuGet packages to the latest versions.
Clean (in build menu)
Rebuild (in build menu)
Try again, if it does not work, continue steps:
Update all your Android related installations (using the SDK manager)
Check the paths for JDK, SDK and NDK in Visual Studio => Options => Xamarin
Try again
It could also be, that you are using a third-party NuGet package that is not compatible with your installed versions. Try removing NuGet packages to isolate the problem.
Unfortunately, there could be many things wrong here, but mostly it is related to versions and installations. Hope this helps.
It looks like you're trying to deploy to a device that does not meet the target requirements.
Verify that the version of the device or emulator you're working on is at least what is shown in your Android Build Options.
To troubleshoot any issues, I'd recommend opening the Android SDK Manager and downloading the Build and SDK tools that match the device you're planning to test on, and rebuild your project targeting the new SDK.
I want to do some cutomization to the wso2 mdm-product source code (EMM version 2) : https://github.com/wso2/product-mdm
Indeed, when i made some modification to the source code, i need at least 15 min to build the maven projet with eclipce IDE.
Is there other solution to build project directly on carbon server?
How can we debug project with eclipse IDE on carbon IDE?
Usually, it takes some amount of time to build the WSO2 product-mdm, in your case, 15 minutes looks perfectly normal. I'd recommend building the source code using the terminal as follows.
Navigate to the repository directory
cd [path-to-dir]/product-mdm
Perform a clean Maven Build
mvn clean install
If you're unclear about the building process of WSO2 EMM Repositories, the answer on below question might help you to understand the building order.
How to use and understand wso2 git repositories?
Debugging
Remote debugging the project is easy.
Setup the Eclipse IDE for remote debugging as described in this link,
Debugging With Eclipse
Navigate to "[EMM_HOME]/bin/" folder and run the server in debug mode.
sh ./wso2server.sh -debug [specify-port-here]
eg: sh ./wso2server.sh -debug 5005
Once the server is up, you can start debugging.
I just downloaded the latest version of WSO2 Dev Studio - Eclipse Luna v3.8. After upgrading my mediator projects all getting the same error "the import org.apache.synapse cannot be resolved" though I've tried several way such as Clean project.
Also, if I choose to Import an existing Maven project, it takes quite long to load Maven dependencies.
Anyone can help ?
It seems a build path issue, As a solution we can do following.
delete the .classpath file(s) before importing to developerstudio-380
Import the project.
Then convert the project to a maven project ( right click on project -> configure ->Convert to Maven project)
Update project ( right click on project -> Maven -> Update project), this step will download the dependencies and resolve the build path issues.
I am using Eclipse EE version and CloudBees plugin to create a ClickStart JBoss 7 project. However, I am not very familiar with the EE version of Eclipse, and used Netbeans to edit my JSP.
Then I used CloudBees SDK to run and deploy my new project but it failed (the command prompt):
D:\Personel\Java EE\HelloCloudBees>bees run
ERROR: java.io.FileNotFoundException: D:\Personel\Java
EE\HelloCloudBees\build.xml (The system cannot find the file
specified)
I found no build.xml file in my folder. How can I create it?
bees run command expect an ant-based project structure, so the build.xml. As documented
CloudBees project commands are only available for applications
generated using the Bees wizard (on the web), built using the
CloudBees SDK style.
This is more or less some legacy stuff, as is now superseded by ClickStart. Equivalent command would be bees app:run but require your app to first be packaged as a WAR and only support the default tomcat6 runtime. So for your specific use-case would be simpler to package and deploy on a local JBoss 7 server. To deploy on RUN#Cloud, use bees app:deploy or just git push and let DEV#Cloud Jenkins build and deploy for you (assuming you created app with a clickstart).
Also, there's no need to use Eclipse if you're familiar with NetBeans.
Have you tried out maven?If yes you can download it and then use mvn eclipse:eclipse and then you can import your project in your workspace using eclipse import capabilities.File -> Import -> Maven -> Existing Maven Project...you point to the file where your pom.xml file is..and is imported. Take into accoutn m2eclipse plugin in eclipse must be installed prior.
regards
\n\m