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 ?
Related
Currently I am working on a project that needs .NET 4.0 to work properly but when I configure the windows installer and try to install it is trying to install the latest version of .NET. So how can I configure the windows installer to install the .NET version on which the project was created. Also I would like to know how to include the Visual C++ Redistributable in my installer.
When you create a setup project and add primary output of a project to the setup project, the setup project automatically detect dependencies including Microsoft .Net Framework. To see if the detected dependency is correctly what you need, you cam see the following locations:
First of all, right click on Dependencies and click on Refresh Dependencies.
Check prerequisites for your project:
Right click on setup project and choose Properties.
In Properties dialog, from the Configurations combo box choose the configuration, and repeat the following steps for both Debug and Release.
Click on Prerequisites... button to open Prerequisites.
In the Prerequisites dialog, check the desired .Net Framework version.
Press OK and Make sure you repeat above steps for both Debug and Release.
Check Launch Conditions for your setup project:
Right click on setup project and from View select Launch Conditions:
Then under Launch COnditions node, select .Net Framework node and right click and select Properties Window.
In Properties Window check the Version property for .Net Framework launch condition.
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 have created a test framework for testing .jsp files and .tag files using embedded jetty. I'm starting Jetty server programmatically using Java API, adding servlet holder and wrapper test JSP and initializing the server passing the project's web root.
There were some issues with Jasper discovering TLD locations during runtime when run from maven surefire plugin. I fixed it by providing
<useManifestOnlyJar>false</useManifestOnlyJar>
plugin classpath settings. Everything works good when I run tests using mvn clean install now.
Running tests from eclipse context menu has one issue. If there is any other project in workspace in the multi module maven build, TLD's in that project are not resolved. One workaround I tried was to 'close' the project in eclipse workspace and it worked out.
However I would want it to work with all the projects open in workspace and running from the eclipse JUnit context menu. The problem is in the jasper TldScanner that looks for tld files in jar and WEB-INF of current project only.
TldScanner.scanTlds()
processWebDotXml();
scanJars();
processTldsInFileSystem("/WEB-INF/");
I'm using org.glassfish.web.jsp-impl 2.2.2-b06 version with Jetty-8.1.0-RC5.
Is there a way to specify file based TLD scanning for jasper for extra classpath items?
I have the carbon source tree set up in eclipse - and have made some code changes.
Can I build just one component (e.g. org.wso2.carbon.feature.mgt.ui-4.1.0.jar) using maven / eclipse, and then deploy that to an existing carbon server?
I have tried dropping the built jar in the repository\deployment directory and restarting the server, but the changes don't appear to have been picked up.
Am I doing something wrong?
Place the jars at <CARBON_HOME>/repository/components/plugins. Also delete the relevant existing jars from repository/components/plugins
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!