...
You can also easily do it using Intellij. Just right click on the top level "CDAP" project and select New->Module and follow the screen.
How To Create Debian Packages
To be completed.
Working With Our Nexus Repositories
We use Nexus Professional as our repository manager. It is available at https://repository.continuuity.com.
Our Repositories:
Our hosted repositories:
Repository Name | Type | Public/Private | Description |
---|---|---|---|
Snapshots | Hosted | Private | Where our snapshot build artifacts are stored |
Releases | Hosted | Public | This is our public release repository, where our tested api jars and singlenode distribution are made available to the public |
Releases-Internal | Hosted | Private | This is where our tested internal releases (cloud distribution, non-api jars) are made available (authentication required) |
3rd Party | Hosted | Public | This is where we can put any custom third-party artifacts that are not available in Maven Central (for example, our patched version of hbase, latest kryo, etc); note this is a public repo |
Additionally, we proxy many public repos:
Repository Name | Type | Public/Private | Description |
---|---|---|---|
Central | Proxy | Public | Maven Central |
Apache Snapshots | Proxy | Public | Apache |
Codehaus | Proxy | Public | Codehaus |
Typesafe Releases | Proxy | Public | Typesafe - we use it for akka |
For convenience, we have defined several repository Groups:
Repository Group Name | Type | Public/Private | Description |
---|---|---|---|
Smartifacts | Group | Private | This contains everything required for gradle to build CDAP: (Snapshots, 3rd party, central, typesafe) |
Release-Candidates | Group | Private | Release builds publish artifacts here (public or private), where they are available as part of the build promotion process |
Public Repositories | Group | Public | This contains everything publicly accessible (anonymously): Releases, 3rd Party, Central, Typesafe |
Access Permission Levels:
Anonymous: Can access all "public" repos as noted above.
Nexus-users (crowd): users have read-only access to everything. All Cask engineers should be able to login via the Nexus UI.
Nexus-administrators (crowd): administrative users with full privileges. Any Cask engineer that needs it.
Gradle: gradle user is password protected and has deploy (update) permissions.