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.
Related
Project pom editor doesn't show any dependencies in CompositeApplicationProject, except Custom Mediator Project. Rest of project (dependencies) like ESB Config Project, DSS Project, in same eclipse workspace are invisible.
I download old release of WsoTooling 3.8.0 and that one able add to CompositeApplicationProject dependency Registry Project only.
Is it possible manually manage dependencies(projects) in CompositeApplicationProject ?
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
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.
I am starting to learn gradle.
However when I am building Spring with Gradle; it downloads the dependency jars to
C:\Users\UserName\.gradle
Is there any way I can specify Gradle to download the dependency jars to a specific location?
Just like I can specify repository location in Maven.
System information:
Windows 7 64bit
Gradle version 1.0
You can set the GRADLE_USER_HOME environment variable, gradle.user.home system property, or --gradle-user-home command line parameter.
On android studio just go to File > Settings > Build Execution, Deployment > Gradle > Service directory path choose directory what you want.
You can also try to go in eclipse at window ->preferences -> gradle and change the directory there
You can add following line to your gradle.properties:
systemProp.gradle.user.home=/tmp/changed-gradle
Steps:
Set the GRADLE_USER_HOME environment variable to new path
On android studio just go to File > Settings > Build Execution, Deployment > Gradle > Service directory path choose directory what you want.
Restart the PC (important step, no one mentioned this surprisingly)
If you are using gradle plugin in your eclipse and trying to import the gradle project than your gradle home is set to
C:\Users\UserName.gradle
In some cases your import build model will not work because of your user directory permission issue.
In this case you can copy your .gradle directory from below path
C:\Users\UserName\**.gradle**
paste into some directory where you have all permission and import the project.
In my case i moved my .gradle dir to z drive and than imported the project than made build model and it worked.
If you want to run gradle tasks through IDE then:
You can also set in intelliJ editor>File>settings:
Then restart the IDE.
If you want to run gradle tasks through command line then you have to set GRADLE_USER_HOME in environment system variables. Then restart the pc as others also said.
I have a WCF DataService build in VS 2010, targetting .Net 4.0. This all works fine. I've created a deployment package and have the application deployed to a web server using MSDeploy and a zip file. When I set up an automated build on a TFS Build Agent the contents of the deployment package changed. I no longer get the strong named assemblies in my deployment package. These excluded assemblies are projects within the solution and are built on the Build Server.
I don't see a lot of configuration options for the deployment package, but I would like to know why the build server creates a different package than my workstation, using the same settings.
I am using "Only files needed to run this application", I have ticked "Exclude generated debug symbols" and "Exclude files from App_Data folder". I _do_not_ include database packages. I do create a zip file (which is missing the strong named assemblies)
Thanks for any information you may have explaining why this occurs. Then maybe I can solve the problem.
Beezler
On the build server I've ungaced the assemblies I was concerned about and that got my deployment package to the state I want it. So it appears the deployment package does not include the GACed assemblies, which is a good thing. I would still like to know how to override this behavior on certain referenced assemblies.
Thanks,
If you want to include a DLL files for a GAC assembly do the following:
In your project, expand the "References" folder
right-click on the reference you want to include the DLL and click "properties" to bring up the properties pane
set "Copy Local" to "True"
That's it! When publishing your project, it will include the DLL in the bin folder for that reference!