I have my bundle jar file along with other code(component JSPs) in a package(under apps/mytest/install).
When I upload and build the bundle from my local to stage environment, I don't see the "apps/mytest/install" folder itself in crx/de and the bundle doesn't get installed in the stage environment.
I can see a post here URLrelated to this but cannot find "org.eclipse.equinox.region" bundle in any of our environments. Anyone has any other solution to resolve this issue?
Related
Under same ORG, i have 2 projects. One is a class library project. Another one is a web site project. Both have their own build and release definition. I want to include dlls from the class library project when i do a release of the web site project. Web site project uses IIS deployment tasks in it's release. This IIS deployment task deploy the zip file created from the build of the web site project only (this project will have reference of the dll from class library already added). What i need is when the release of web site happen , it should pick the latest dll from class library project added in to it's bin folder. How do i do that in devops release definition.
Azure DevOps - Linking Class Library project into the release of another project
The easiest way is add the class library project in the solution of web site project and set it as project reference instead of reference the dll file.
Then we build the solution of the web site project, the latest dll from class library project will be added in to bin folder of web site project each time when we build the solution.
If you do not want to use project refernce, you can also use the Download Pipeline Artifacts task in the build pipeline of web site project to download the latest dll from class library project, then use the Copy Files task to copy the dll from the default folder to the bin folder.
Hope this helps.
I am working on a project to manage and orchestrate a legacy Wildfly Java/Maven web application. I know very little about the application itself, and frankly, not much about Wildfly. I am using Eclipse Oxygen and Wildfly 10.1.0 with the JBoss plugin.
I am following sketchy deployment instructions for the app and they're not working. However, this application has deployed for other folks on the project.
When publishing the app (I've tried clean, publish, full publish etc.), the resultant exploded war in standalone/deployment is missing .class files. However, the missing .class files are present in the taget directory and they are in the .WAR file, they're just not in the Widlfly deployment.
This application builds two base 'com' packages. Let's call them com.rrr and com.ttt for anonymity.
When the application builds, there is the expected WEB-INF/classes/com directory structure (in target and the war) with all package directories and all .class files present.
When deployed to Wildfly, all of the package directories are present for both com.rrr and com.ttt, however, there are .class files in the com.ttt packages, but there are NO .class files in the com.rrr packages.
So, when I try and deploy the app using the JBoss/Eclipse plugin, I'm getting:
Caused by: java.lang.ClassNotFoundException: com.rrr.ui.servlet.ActionServlet from [Module "deployment.myapp-18.1.0.0.war:main" from Service Module Loader]
Again, this deployment works for others (who are unavailable at this time) so I don't think it's a project issue. Perhaps I have configured something wrong based on the sketchy instructions?
Any guidance on what to look for or how to solve this would be appreciated.
Our first step is a MsBuild for our .sln file. We pass in our platform and config and everything is built correctly.
Next we want to NuGet pack all the files for Octopus Deploy to use. In this step we specify all of our .csproj files (not sure why, everything is already built)
The package that is created contains 2 folders, Content which contains all the files needed minus bin and the Lib folder which contains only the projects compiled dlls. It's not including any of the other dlls referenced in the project.
It sounds like it might be easier for you to use Octopack to handle the creation of the NuGet packages to be deployed.
Step 1. Install the Octopack NuGet package into the projects that are your deployable applications.
Install-Package OctoPack
Step 2. Ensure you have a build step before the main compilation that will install any referenced NuGet packages.
Step 3. Install the TeamCity plugin for Octopus deploy from the downloads page and restart the TeamCity server service
Step 4. You'll now see additional options in your MSBuild runner configuration and if you check the following box in your build configurations, it will produce a NuGet package for you which should have everything required for a successful deployment.
As a small tip, I publish the package straight to Octopus by referencing the output package (rather than waiting for it to be attached as an artifact at the end of the build and thus requiring two build configurations)
Hope this helps
If NuGet pack is not packaging your application as you expected from your project file, you have to create a NuGet spec file and specify how things should be packaged. For a web application that is as simple as creating a simple .spec file and putting it into your web application directory, but for other projects that can be a little more complicated. Check out the Nuspec Reference to see how to add your content and dependencies. https://docs.nuget.org/create/nuspec-reference
I have a web app with a few NuGet packages. The web project targets .net 4.5. Now, one package is behaving strange. I get to download it from the official repository, but it's just not added to my bin folder.
I guess the reason is that the package downloaded contains a .dll under /net40/ folder. Adding it manually works, but NuGet is not picking it up. Is there a way I can setup this to work?
I am pulling JavaScript from a jar as part of my build process. I wish this js to be part of my web resources for the app deployed on tomcat and I have updated my build process to allow this to happen. Doing a maven build (outside eclipse) works as expected and I can package up a war with everything in its proper order.
However, when building with eclipse I have run into some headaches. My understanding was in order to have web resources deployed to tomcat through an incremental build, I needed to put these build-time generated js files into the target/m2e-wtp/web-resources directory. However, when I publish these new files are ignored and the web-resources deployed to tomcat seem to be pulled from my source.
I also adjusted my project's deployment assembly settings. Through this I still don't have it working. I have the entry [source:/target/m2e-wtp/web-resources, DeployPath:/] which should find the newly generated files when I perform a "publish" to the server. However, the same thing happens where m2e-wtp seems to be pulling from source.
Am I missing something? How can I get standard behavior from m2e-wtp (i.e. make it comparable to a build done outside of eclipse)? Or can I have eclipse just build the war and deploy it as such (not do the incremental builds, I can sacrifice some speed)?
FYI (versions):
eclipse: (Using Spring Tool Suite) 3.2.0
m2e: 1.3.1
m2e-wtp: 0.17.0
tomcat: 7.0
Experiment added later:
After deleting my target dir, I performed a publish to Tomcat and all the web-resources were copied from my source. I also got a popup about files not found, most of which are compiled classes. However, it was looking for three files in the /target/m2e-wtp/web-resources/META-INF. Does the m2e-wtp plugin only look for specific files in a folder rather than the entire specified folder?
The problem is that the target directory was not being refreshed. Eclipse (or m2e plugin for that matter) doesn't recognize or care that files change in the target directory during a build, something that I was assuming. For now I have the auto-refresh (for the workspace) option on. The refresh on access option didn't working as it seemed to trigger the refresh only when I was publishing to tomcat for the first time.