I'm trying to set up IntelliJ to deploy Mule project that depends on a domain project, but the result builded by Maven does not have META-INF directory and mule_export.properties in it. However, the same build within AnyPoint Studio does produce these artifacts, which make the deployment successful.
Does anyone know how can I force Maven to create these? Either through Maven plugin or IntelliJ associations, as it seems that associations within IDE are the reason this is being produced by AnyPoint Studio.
I'm not sure why do you need the mule_export.properties. It seems to be only generated by Anypoint Studio when exporting a project. However I don't think it is used at all to deploy an application. Probably you are having a different problem. Usually that happens by differences between Maven dependencies and Studio build path.
What is the exact error you are having at deployment?
Related
I'm receiving a build error in DevOps for a .Net Core 3 web application using a project dependent Razor Class Library from another solution.
For the DevOps pipeline, I receive the following build solution error:
##[error]d:\a\1\s\consumer.app.sln.metaproj(0,0): Error MSB3202: The project file "d:\a\1\s\..\framework.app\framework.rcl\framework.rcl.csproj" was not found.
I have another pipeline for the framework.app project (which also uses framework.rcl as a project dependency) but because the framework.rcl project is within that solution (and the same repo), it works flawlessly.
Is there any way (preferably without nuget) to access the framework.rcl razor class library from the consumer.app pipeline?
Everything works perfect locally as the project has been added in visual studio (via Add Existing project), but obviously that linked project is not included in source control for the consumer.app solution.
Please Help :)
I tripped over myself here. I was deep into managing project dependencies and using Azure Artifacts to do so.
However, the problem here wasn't a dependency issue. Msbuild in the Azure DevOps pipeline was simply trying to build a shared project used in the solution that wasn't available in the repo.
In Visual Studio, I simply unticked the build for the 'Release' configuration in Configuration Manager and DevOps no longer wants to build it.
I get a warning, but no error and my package reference to my Azure artifact (nuget) ensures everything wires up correctly.
I am using dbup for my database migration and my dbup project in visual studio solution definitely produces required exe and exe.config file. Now when I deploy my project through octopus deploy I have no exe.confog file in nupkg generated by octo however I can confirm that exe.config is in the release folder on the server.
I found that octopus had a bug with similar issue https://github.com/OctopusDeploy/Issues/issues/970 which is resolved now. in version 2.5.1 (https://octopus.com/downloads/compare?from=2.2.1&to=3.4.10) and I am using octopus version 3.3.17 , however I am facing same behaviour..
Can anyone please point me in the right direction?
Many thanks.
If you run MSBuild myProjectFile.csproj /p:RunOctoPack=true inside the project folder, you will see some OctoPack logging showing you what it did exactly. It will tell you where it put all the files, which .nuspec file was used, etc. Maybe that'll clear some things up.
I am trying to move my Mule ESB project from gradle to maven due to test case issues. I understand I need to remove the .gradle file from the project and when I click on mavenize , nothing happens in Anypoint studio. Any suggestions ?
To mavenize your project you may use Eclipse because this IDE is best suitable with Maven. You'll need to download eclipse, and then add mule support in it. Follow this tutorial to do the same. After that import your project in eclipse and mavenize it. You make take help from this example by David Dossot, to configure a mule project with maven.
If you have AnyPoint Studio, you can create a Mule application and it will already be set up for use with Maven. I would then bring my application artifacts into the newly created project. This way you start with a fresh project that's set up correctly for Maven. Also, you will learn more about things by bring in your mule config, app properties, deploy properties, java classes, and tests into a correctly formatted project structure. You will leave any Gradle artifacts behind. I don't know what button you are clicking called "Mavenize" but Anypoint Studio will allow you to create a shell project that works with Maven. Just create a Mule Application project and copy/paste in the pieces from your existing application. Don't use Eclipse to set up a Maven Mule application project. That's backing up and not utilizing what's available to you.
I am trying to introduce MUnit unit tests to an existing Mule project which is using Maven for builds and dependency management.
However I am unable to run the tests visually through Mule Anypoint Studio, when I try to debug them I get the error:
MUnit test could not be run, The Archive
C:/pathtomyuserfolder/.m2/commons-logging/1.2/commons-logging-1.2.jar which is
referenced by the classpath, does not exist.
I can however run the test using Maven using the command "mvn test" but this is not ideal as I want to be able to debug the test, pausing at breakpoints etc.
I can reproduce this problem using the Mule Anypoint Exchange sample here: https://www.mulesoft.com/exchange/#!/munit-example. When I open this project I can debug the tests with no problems, but if I then right click on the project and select Maven Support In Studio -> Mavenize. I am then unable to debug the tests in Studio.
What am I doing wrong? Is this behavior supported?
This turned out to be a problem with the build path on my machine and nothing to do with MUnit.
The clue was in the actual error message above - that the path was missing the /repository folder under my /.m2 folder. I'm not sure how it happened by my M2_REPO was pointing to the wrong level.
The strange thing is that the two projects I tried would still actually run ok, so that's why I thought it was just a problem with MUnit. Sorry for the confusion and thanks to #Ryan and #Dds for your comments. I should have first tried to fix the problems highlighted in Mule Studio before posting.
Mule Studio is afaik supposed to replace Mule IDE as the development tool for Mule ESB. I am trying to understand how I am supposed to get full Maven integration in Mule Studio. All tutorials I find show how to create and package project inside the IDE but that is not workable for me as I need Maven for dependency management, automated builds and so on.
Basically I would like the same Maven support as in Mule IDE with m2eclipse. Maybe I am totally off base? Does anyone have an idea?
Thanks,
Olof
This is a much required and expected feature: STUDIO-1393. Please vote it up!
Update:
Check the following instructions: m2eclipse in MuleStudio