[
https://issues.apache.org/jira/browse/MARMOTTA-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600041#comment-13600041
]
Sebastian Schaffert commented on MARMOTTA-131:
----------------------------------------------
Here is a short update on what artifacts the release process should create and
at which phases when the release profile is active:
package:
- create Maven artifacts
- create apache-marmotta-x.x.x-src.[zip|tar.gz] (complete source archive)
- create apache-marmotta-x.x.x-webapp.[zip|tar.gz] (an archive containing the
WAR file, the license, and a short README)
- create apache-marmotta-x.x.x-installer.[zip|tar.gz] (an archive containing
the installer JAR, the license, and a short README)
deploy:
- sign and upload Maven artifacts to repository.apache.org (already working)
- create distribution directory, move all relevant distribution packages there,
create checksums, sign with GPG
- generate the description where to upload the distribution
- generate the vote email to the development mailinglist (like Jackrabbit does)
> Create distribution tasks for releasing the software
> ----------------------------------------------------
>
> Key: MARMOTTA-131
> URL: https://issues.apache.org/jira/browse/MARMOTTA-131
> Project: Marmotta
> Issue Type: Task
> Components: Build Environment
> Reporter: Sebastian Schaffert
> Assignee: Sebastian Schaffert
> Priority: Blocker
> Fix For: 3.0-incubating
>
>
> The project build currently mainly builds the Maven artifacts, but we also
> need to configure the different distributions we'd like to have. A copy from
> my mail to dev@...:
> The release of Marmotta is a bit different from both, Jena and Stanbol:
> - there is a common release number over all artifacts (different to Stanbol,
> easier maintenance)
> - the primary means of release is the Maven repository
> - there are two binary "launchers" we would like to release in addition: a
> .war file and a izPack installer that bundles also Tomcat
> - there are a number of libraries that are worth releasing separately as
> libraries (Maven and download):
> * ldclient as a Linked Data Client library
> * ldcache as a Linked Data Caching library (builds on ldclient)
> * ldpath as a RDF/Linked Data Query Language (builds on Jena or Sesame, can
> use ldcache)
> * kiwi as a RDBMS-based Sesame backend with some advanced functionality
> (reasoning, versioning, transactions)
> - there is a common source release consisting of the combined source code
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
