{"id":14983128,"url":"https://github.com/unic/neba","last_synced_at":"2025-04-06T14:12:51.232Z","repository":{"id":16073145,"uuid":"18817575","full_name":"unic/neba","owner":"unic","description":"Lightning fast and simple content mapping for Apache Sling and Adobe AEM","archived":false,"fork":false,"pushed_at":"2025-03-12T15:16:39.000Z","size":14385,"stargazers_count":56,"open_issues_count":5,"forks_count":14,"subscribers_count":15,"default_branch":"develop","last_synced_at":"2025-03-30T13:08:55.593Z","etag":null,"topics":["adobe-aem","aem","apache-sling","mappings","models","pojo","sling","spring","spring-mvc"],"latest_commit_sha":null,"homepage":"https://neba.io","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/unic.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2014-04-15T22:02:55.000Z","updated_at":"2025-03-12T15:16:09.000Z","dependencies_parsed_at":"2022-07-23T00:46:22.331Z","dependency_job_id":"8ffb8666-cbb7-4075-8985-3d36851c1938","html_url":"https://github.com/unic/neba","commit_stats":{"total_commits":592,"total_committers":12,"mean_commits":"49.333333333333336","dds":"0.21959459459459463","last_synced_commit":"e34e890a42c9f319118e2108ca3e63503abba7ba"},"previous_names":[],"tags_count":39,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/unic%2Fneba","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/unic%2Fneba/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/unic%2Fneba/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/unic%2Fneba/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/unic","download_url":"https://codeload.github.com/unic/neba/tar.gz/refs/heads/develop","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247492565,"owners_count":20947545,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["adobe-aem","aem","apache-sling","mappings","models","pojo","sling","spring","spring-mvc"],"created_at":"2024-09-24T14:06:46.646Z","updated_at":"2025-04-06T14:12:51.206Z","avatar_url":"https://github.com/unic.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"\n\n![NEBA](README/neba-logo.png \"NEBA logo\") \n\nLightning fast and simple content mapping for Apache Sling and Adobe AEM\n====\n\n[![codecov](https://codecov.io/gh/unic/neba/branch/develop/graph/badge.svg)](https://codecov.io/gh/unic/neba/)\n[![CI workflow](https://github.com/unic/neba/actions/workflows/ci.yml/badge.svg)](https://github.com/unic/neba/actions/workflows/ci.yml)\n[![Maven Central](https://img.shields.io/maven-central/v/io.neba/io.neba.neba-parent.svg)](https://search.maven.org/search?q=a:io.neba.neba-parent)\n\nNEBA in a nutshell\n--------------------\nMap Content using a lightweight, [well documented API](https://neba.io/documentation.html).\nUse lazy loading and great tooling to deliver high-performance applications. Completely compatible\nwith Sling Models, HTL (Sightly), JSP and any application build atop the Sling API.\n\nOptional Spring integration\n----------------------\nNEBA optionally integrates the Spring framework, making available all of Spring's features, including Spring MVC.\nSpring is integrated using [gemini blueprint](https://www.eclipse.org/gemini/blueprint/), the OSGi Blueprint specification reference implementation.  \n\nDownloading artifacts\n----------------------\nNEBA releases are published to maven central. The configuration as well as further information are available at [https://neba.io/download.html](https://neba.io/download.html).\n\nDocumentation\n--------------------\nThe project documentation resides at [https://neba.io/](https://neba.io/).\n\nLicense and included licenses\n--------------------\nNEBA is licensed under the terms of the Apache License, version 2.0. For the licenses of included products,\nsee [NOTICE](NOTICE.txt)\n\nGetting support\n--------------------\nConsult the documentation or ask a question in the site comments at [https://neba.io](https://neba.io), Tweet to [@nebaframework](https://www.twitter.com/nebaframework) ask a question at [Stack overflow](https://stackoverflow.com/search?q=neba) or drop us a mail at neba at unic.com.\n\nBuilding from source\n--------------------\nNEBA uses a [Maven](https://maven.apache.org/) based build. invoking\n\n    mvn clean install\n    \nIn the project's root directory will build and install NEBA. We are using [git flow](https://nvie.com/posts/a-successful-git-branching-model/),\nyo you might want to do so on the \"develop\" branch.\n\nReleasing NEBA\n--------------------\n\n### Summary\nNEBA is released using the [maven jGitFlow plugin] (https://bitbucket.org/atlassian/jgit-flow/wiki/Home). Releasing requires modification rights for the neba github repository and the ability to sign and upload the artifacts to the sonatype OSS staging repository. Finally, the release must be accompanied by a release notes blog post published via the gh-pages branch and an announcement on Twitter. \n\n### Prerequisites\n\nTo release NEBA, credentials for the sonatype [OSS repository](https://oss.sonatype.org/content/repositories/) are required, and must be configured in the maven settings.xml, like so:\n\n````\n \u003cserver\u003e\n   \u003cid\u003eossrh\u003c/id\u003e\n   \u003cusername\u003e...\u003c/username\u003e\n   \u003cpassword\u003e...\u003c/password\u003e\n \u003c/server\u003e\n````\n\nIn addition, a GPG installation executable from the [maven-gpg-plugin](https://maven.apache.org/plugins/maven-gpg-plugin/) must be installed on the local system, e.g. [GPG4Win](https://www.gpg4win.org/) on windows. As the delivery artifacts are signed, you require a valid key pair, and the public key must have been [distributed to a public key server](https://www.gnupg.org/gph/en/manual/x457.html).\n \nFurthermore, JDK 1.8 is required for building and releasing NEBA.\n \n### Write a release post for the neba.io site\nIn a separate clone of the neba.io git repo, checkout the gh-pages branch and write a release post, such as https://github.com/unic/neba/blob/gh-pages/_posts/2016-01-22-neba-release-3.9.0.html. Testing the site locally requires running Jekyll, see https://jekyllrb.com/docs/installation/.\n\n### Perform the release\nInvoke\n\n    mvn -Prelease jgitflow:release-start\n \nand enter the desired release version. We are using the versioning scheme x.x.x, e.g. \"4.10.1\". All artifacts must have the same release version.\n\nThen, invoke\n\n    mvn -Prelease jgitflow:release-finish\n\nResulting, the artifacts are pushed to the sonatype OSS staging repository\n\n### Test staged release artifacts\n\nLogin to https://oss.sonatype.org/ and select \"Staging Repositories\". \n\n![](README/repository.png)\n\n\nIn the list of repositories, select the io-neba staging repo. Download the AEM and Sling deliveries and test them on the local system by installing them and testing that\nall contained bundles are started properly.\n\nThen, browse the remaining artifacts (e.g. api, core) in the repository and make sure that the jar, source-jar and javadoc-jar artifacts are present.\n\n### Release the staged repository\nIn https://oss.sonatype.org/, select the tested neba staging repository and click \"close\".\n\n![](README/close-repository.png)\n\n \nThis triggers an automated workflow testing the repository for compliance. Once this process has finished (after a few minutes), click on \"Release\".\n\n### Push the release\nOn you local system, push the *develop* and *master* branch as well as the tags, e.g. using\n\n    git push --tags\n    \n### Publish the release blog post\nsimply push the new blog post on the gh-pages branch - the neba.io site is updated automatically. \n\n### Publication on twitter\nPublications are announced via the official [@nebaframework](https://twitter.com/nebaframework) twitter channel and must contain the tag #nebaframework. Tweets with this tag are automatically featured on the neba.io home page.\n    ","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Funic%2Fneba","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Funic%2Fneba","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Funic%2Fneba/lists"}