Return-Path: X-Original-To: apmail-deltaspike-commits-archive@www.apache.org Delivered-To: apmail-deltaspike-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 011BBFCD4 for ; Fri, 12 Dec 2014 17:47:57 +0000 (UTC) Received: (qmail 44882 invoked by uid 500); 12 Dec 2014 17:47:56 -0000 Delivered-To: apmail-deltaspike-commits-archive@deltaspike.apache.org Received: (qmail 44837 invoked by uid 500); 12 Dec 2014 17:47:56 -0000 Mailing-List: contact commits-help@deltaspike.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltaspike.apache.org Delivered-To: mailing list commits@deltaspike.apache.org Received: (qmail 44827 invoked by uid 99); 12 Dec 2014 17:47:56 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 17:47:56 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id AC319AC094A for ; Fri, 12 Dec 2014 17:47:56 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r932470 [1/2] - /websites/staging/deltaspike/trunk/content/ Date: Fri, 12 Dec 2014 17:47:56 -0000 To: commits@deltaspike.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20141212174756.AC319AC094A@hades.apache.org> Author: buildbot Date: Fri Dec 12 17:47:56 2014 New Revision: 932470 Log: Staging update by buildbot for deltaspike Added: websites/staging/deltaspike/trunk/content/community.html websites/staging/deltaspike/trunk/content/documentation.html websites/staging/deltaspike/trunk/content/download.html websites/staging/deltaspike/trunk/content/examples.html websites/staging/deltaspike/trunk/content/javadoc.html websites/staging/deltaspike/trunk/content/migration-guide.html websites/staging/deltaspike/trunk/content/news.html websites/staging/deltaspike/trunk/content/release-preparation.html websites/staging/deltaspike/trunk/content/steps_for_a_release.html websites/staging/deltaspike/trunk/content/suggested-git-workflows.html Modified: websites/staging/deltaspike/trunk/content/ (props changed) Propchange: websites/staging/deltaspike/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Dec 12 17:47:56 2014 @@ -1 +1 @@ -1644993 +1644994 Added: websites/staging/deltaspike/trunk/content/community.html ============================================================================== --- websites/staging/deltaspike/trunk/content/community.html (added) +++ websites/staging/deltaspike/trunk/content/community.html Fri Dec 12 17:47:56 2014 @@ -0,0 +1,384 @@ + + + + + + + + +Community + + + + + + + + + + + + + + + + +

Community

+ +

Introduction
Users
Getting Involved +
- Contributors
- Committers
+
Mailing lists
JIRA
Spread the word
IRC

+ +

Introduction

+ +

Users

If you are a new user and you would like to start using DeltaSpike, you +can have a look at the Documentation and +subscribe our +mailing list for users. If you have +troubles to find the information you are looking for, you can also ask +in our IRC-Channel.

Furthermore, you can check our mail-archives.

Before you file a ticket in our +Jira, please ask on +the mailing list if it’s a known issue in case of a bug or if there is +an ongoing discussion in case of a feature.

You are very welcome to follow our twitter account +@DeltaSpikeTeam and spread the +word of DeltaSpike with Tweets, Blog-Entries,…

Getting Involved

Everybody is welcome to get involved with our community. You can find +general information at http://apache.org/foundation/getinvolved.html and +http://apache.org/foundation/how-it-works.html. The following sections +provides some details about the different levels of getting involved.

If you want to contribute with DeltaSpike +Documentation, please read the instructions +about the Documentation that adresses how to contribute, render and +publish it.

Contributors

Before you get a committer you have to contribute to our effort. E.g. +you can help users, participate in discussions on the dev list, submit +patches,… . Therefore, it’s essential to file a/n +(I)CLA or +CLA and send it to +secretary at apache dot org (or fax it) as early as possible.

If you would like to submit a patch through Jira, you can have a look at +the suggested approach.

Here is the contributors/committers page: +Contributors.

Committers

Before you read this section, please ensure that you have read the +contributor section. All of you are welcome to join our development +effort. Subscribe our +mailing list for developers and start +contributing and help users.

Optionally subscribe our +mailing list for commits.

Furthermore, you can check our +mail-archives.

Further details are available at http://www.apache.org/dev/.

Mailing lists

+ ++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

List (Address)	Subscribe	Unsubscribe	Archive	Mirrors
User List	Subscribe	Unsubscribe	Archive	Nabble	MarkMail
Developer List	Subscribe	Unsubscribe	Archive	Nabble	MarkMail
Committer List	Subscribe	Unsubscribe	Archive

List (Address)

Unsubscribe

Archive

Mirrors

JIRA

Any kind of issue has to be filed in our +issue-tracker. If you +have any question, you can ask us (e.g. via the mailing list for users).

Spread the word

You are very welcome e.g. to write blog entries, tweet (#DeltaSpike) +about the project or just follow our twitter account +@DeltaSpikeTeam, …

IRC

Usually discussions happen on the mailing list. Some informal +discussions take place in our IRC-Channel +irc://irc.freenode.net/deltaspike

//with the irssi command-line client:
+$ irssi
+
+> /connect irc.freenode.net
+> /join #deltaspike

If you are new to IRC you can use the pre-configures web-client you can +find here.

+ +

+ + + +

+ + + + \ No newline at end of file Added: websites/staging/deltaspike/trunk/content/documentation.html ============================================================================== --- websites/staging/deltaspike/trunk/content/documentation.html (added) +++ websites/staging/deltaspike/trunk/content/documentation.html Fri Dec 12 17:47:56 2014 @@ -0,0 +1,282 @@ + + + + + + + + +Documentation + + + + + + + + + + + + + + + + +

Documentation

+ +

Sources
Format
Rendering documentation as HTML
Contribute
Publish procedure (for committers only)

+ +

Sources

DeltaSpike Documentation is available with DeltaSpike Source.

Format

The format used for DeltaSpike documentation is ASCIIDOC because it’s easily +exportable to PDF, HTML, and it’s also easy to contribute. It can be used to export also to epub and also be used to write books

Rendering documentation as HTML

Requirenment: Have Maven installed.

If you cloned the source repository and want to render the documentation +as HTML, you just need to run the following command:

$ cd REPO_ROOT/documentation
+$ mvn site

The generate documentation will be available at REPO_ROOT/documentation/target/site

Contribute

If you would like to submit a documentation patch through Jira, you can +have a look at the suggested approach.

Publish procedure (for committers only)

If you’re a committer and want to publish the documentation at DeltaSpike Site you have do the following steps:

Put the following information in your ~/.m2/settings.xml file

<server>
+  <id>deltaspike-site</id>
+  <username><YOUR_USERNAME></username>
+  <password><YOUR_PASSWORD></password>
+</server>

To publish to staging area, run:

$ mvn site-deploy -P staging

To publish to production area, run:

$ mvn site-deploy

Then run:

After log in to https://cms.apache.org/deltaspike/publish and click on the Submit button.

+ +

+ + + +

+ + + + \ No newline at end of file Added: websites/staging/deltaspike/trunk/content/download.html ============================================================================== --- websites/staging/deltaspike/trunk/content/download.html (added) +++ websites/staging/deltaspike/trunk/content/download.html Fri Dec 12 17:47:56 2014 @@ -0,0 +1,316 @@ + + + + + + + + +Download + + + + + + + + + + + + + + + + +

Download

+ +

Latest Release
Binary Distribution
Source Distribution
Maven Dependencies
Previous Releases
Verifying Releases

+ +

Latest Release

v1.2.0

Binary Distribution

Source Distribution

Maven Dependencies

Details are available here.

Previous Releases

See Release-Archive

Verifying Releases

It is essential that you verify the integrity of any downloaded files +using the PGP or MD5 signatures. For more information on signing +artifacts and why we do it, check out the +Release Signing FAQ.

The PGP signatures can be verified using PGP or GPG. First download the +KEYS as well as the asc +signature file for the artifact. Make sure you get these files from the +main distribution directory, +rather than from a +mirror. Then verify +the signatures using e.g.:

$ pgpk -a KEYS
+$ pgpv deltaspike-project-1.2.0-source-release.zip.asc

$ pgp -ka KEYS
+$ pgp deltaspike-project-1.2.0-source-release.zip.asc

$ gpg --import KEYS
+$ gpg --verify deltaspike-project-1.2.0-source-release.zip.asc

+ +

+ + + +

+ + + + \ No newline at end of file Added: websites/staging/deltaspike/trunk/content/examples.html ============================================================================== --- websites/staging/deltaspike/trunk/content/examples.html (added) +++ websites/staging/deltaspike/trunk/content/examples.html Fri Dec 12 17:47:56 2014 @@ -0,0 +1,229 @@ + + + + + + + + +Examples + + + + + + + + + + + + + + + + +

Examples

+ +

Introduction +
- #1
+
External

+ +

Introduction

#1

artifact-id: deltaspike-jse-owb-example (the shown use-cases also work +with Weld - only the bootstrapping of the container is different, +because this example is based on Java-SE and therefore outside of an +Java-EE(6+) application server.

External

+ +

+ + + +

+ + + + \ No newline at end of file Added: websites/staging/deltaspike/trunk/content/javadoc.html ============================================================================== --- websites/staging/deltaspike/trunk/content/javadoc.html (added) +++ websites/staging/deltaspike/trunk/content/javadoc.html Fri Dec 12 17:47:56 2014 @@ -0,0 +1,261 @@ + + + + + + + + +Javadoc + + + + + + + + + + + + + + + + +

Javadoc

+ +

Latest version
Stable Releases
Contribute
Publish procedure (for committers only)

+ +

Latest version

+
1.2.1-SNAPSHOT
+

Stable Releases

+
1.2.0
+
+
1.1.0
+

Contribute

If you would like to submit a javadoc patch through Jira, you can have a +look at the suggested approach.

Publish procedure (for committers only)

If you’re a committer and want to publish the javadoc, you have do the +following steps:

Put the following information in your ~/.m2/settings.xml file

<server>
+  <id>deltaspike-site</id>
+  <username><YOUR_USERNAME></username>
+  <password><YOUR_PASSWORD></password>
+</server>

Then run:

$ cd REPO_ROOT/deltaspike
+$ ./javadoc.sh

After log in to https://cms.apache.org/deltaspike/publish and click onthe Submit button.

+ +

+ + + +

+ + + + \ No newline at end of file Added: websites/staging/deltaspike/trunk/content/migration-guide.html ============================================================================== --- websites/staging/deltaspike/trunk/content/migration-guide.html (added) +++ websites/staging/deltaspike/trunk/content/migration-guide.html Fri Dec 12 17:47:56 2014 @@ -0,0 +1,374 @@ + + + + + + + + +Migrate from MyFaces CODI-Core to DeltaSpike + + + + + + + + + + + + + + + + +

Migrate from MyFaces CODI-Core to DeltaSpike

+ +

Introduction

+ +

Apache MyFaces CODI to Apache DeltaSpike

Example Overview

+
Fullstack CODI to DeltaSpike @ os890
+

Basically unchanged parts

Here you can see features which were added and the concept itself didn’t change (only the packages, config keys,…)

Project-stage

Only the config key changed (TODO)

Deactivatable and ClassDeactivator

The concept hasn’t changed.

CodiConfig

The concept hasn’t changed.

Annotation literals

The concept hasn’t changed. We just added further implementations.

BeanManagerProvider

The concept hasn’t changed. We just splitted the functionality. The util +methods are available in BeanProvider and their name and signature have +been unified.

Extended concepts

Here you can see features which were added and the concept itself +changed a bit or got merged with concepts from Seam3

ConfiguredValueResolver

Here we added more flexibility (esp. re-ordering the default lookup +mechanisms). See ConfigResolver, ConfigSourceProvider and +ConfigSource.

ProjectStageActivated and ExpressionActivated

We merged them with a feature of Seam3 and now it’s called @Exclude. +That means the basic functionality is still in place (nothing was +removed), but the logic is now inverse.

DefaultAnnotation

(In progress) We merge it with a similar helper of Seam-Solder to +provide custom values for annotation attributes.

Postponed concepts

We couldn’t agree on these features. If you find them useful, please +contact the mailing-list. If we see that users need it for reasons we +might haven’t seen so far, we will discuss it again.

BeanNames

+ +

Dropped concepts

Java 1.5 Support

+ +

JSF Module

Type-safe view config

+
Changed names
+
+
Annotations are optional
+
+
1. +
  (TODO)
  +
+
+

JBoss Seam2 to Apache DeltaSpike

(TODO)

JBoss Seam3 to Apache DeltaSpike

(TODO)

+ +

+ + + +

+ + + + \ No newline at end of file