One of the New Year presents to all Oracle Fusion Middleware user was the creation of a Maven repository by Oracle. A big problem for many application developers using the WebLogic server was dealing with the dependencies. Typically the dependencies supplied by WebLogic would be taken out of the installation and brought onto the classpath of the project compilation. I have seen the JARs from WebLogic checked into the version control system for each project, provided via a fileshare or more or less manually uploaded to a repository manager. And you needed to decide to either use the JARs as they were shipped or figure out what upstream project they come from and what coordinates you should be using if you upload them to a repository.
Hopefully you did it consistently with each release of WebLogic. Any of the solutions used was labour intensive and needed to be performed for each release and it needed to be done in each organization using WebLogic.
Mark Nelson and his team have now gone to the effort to provide such a repository full of all the necessary components and therefore save developers and organizations a lot of time. The Maven repository they provide at http://maven.oracle.com includes documentation on the contents as well as many example projects, tutorials and demos. In addition, it shows you how to get the necessary registration, that you need to use to authenticate.
With the new Nexus 2.11.2 release we are supporting the authentication mechanism used for the Oracle Maven repository in both Nexus OSS and Nexus Pro. This allows you to proxy the repository in Nexus and makes the components discoverable via browsing the index as well as searching for components. You will only need to set this up once in Nexus and all your projects. Developers and CI servers get access to the components and the need for any manual work disappears. On the Nexus side, the configuration changes can be done easily as part of your upgrade to the new release. Check it all out in action:
Now all you have to do is keep your dependency references in your Maven POM files up to date and wait for Oracle to provide new ones with the next updates and see them appear in Nexus. No more manual dependency management. We hope you like it …
Note: This is a sample video from the “Tips from the Trenches” series in the Members Only area. Other videos in this series include:
- Proxing Nexus with nginx
- Node.js and NPM Registries with Nexus
- Ruby, RubyGems and Gem Repositories with Nexus
- Automating Nexus with the Nexus REST API
- Exploring Nexus 3.0 Milestone 3
Join the community for full access to all video galleries and content.
Latest posts by Manfred Moser (see all)
- Integration with Nexus Repository 3 - June 8, 2016
- Sonatype Automated Deployments with Atlassian Bitbucket Pipelines - May 24, 2016
- Migrating to Nexus Repository 3 – Easy Peasy - May 11, 2016
- Puppet-eering the Nexus Repository Manager - May 2, 2016
- Impressions from DevOpsDays Vancouver 2016 - April 19, 2016