Jetspeed 2.0の取得
-
+
ダウンロード
@@ -143,19 +143,19 @@
-
- Jetspeed-2 is currently under development. The first
- production release is expected in Q4 2005. Even
- though it is not officially released, there are
- several production portals using Jetspeed-2 that are
- already on-line.
-
+
+ The first production release of Jetspeed-2 was released
+ on December 8, 2005. Future development areas include
+ improved caching and clustering support, further AJAX integration,
+ new portlet applications, WSRP support, better design
+ and use experience.
+
- Jetspeed-2 は現在開発中です。はじめの製品リリースは、
- 2005年第4四半期の予定です。公式のリリースされなくても、
- 既に、インターネット上に Jetseed-2 を利用したいくつかの製品ポータル
- があります。
+ Jetspeed-2 の初めての製品リリースは、2005 年 12 月 8 日にリリースされました。
+ 今後の開発分野には、キャッシングやクラスタリングの改善とサポート、
+ さらなる AJAX の統合、新しいポータルアプリケーション、
+ WSRP サポート、より良いデザインと使用感などが含まれます。
From shinsuke @ yahoo.co.jp Tue Dec 27 06:22:57 2005
From: shinsuke @ yahoo.co.jp (Shinsuke SUGAYA)
Date: Tue, 27 Dec 2005 06:22:57 +0900
Subject: [Jetspeed-japan-trans] =?iso-2022-jp?b?UmU6IBskQiQkJG0kJCRtGyhC?=
=?iso-2022-jp?b?GyRCSlY/LhsoQg==?=
In-Reply-To: <20051227013105.56793620@appliedjapan.com>
References: <43AC0893.9000605@yahoo.co.jp>
<20051227013105.56793620@appliedjapan.com>
Message-ID: <43B05F31.2050705@yahoo.co.jp>
こんにちは、菅谷です。
お疲れさまでした。今、コミットしてみましたが、
完璧ですね〜。結構、便利だと思うので、他の
プロジェクトでもどんどん使っていきたいところです :)
shinsuke
Applied_MATSUDA Masaaki wrote:
> TigerCatです。
>
>
>
>>>そういえばコミットメールに変更箇所のdiffも付くべきでしょ
>>>うか?もし手持ちのスクリプトが無い場合は,アノ時使った(笑)
>>>CVSROOTの下のperlスクリプトを持ってってもらって構いません。
>>>確か日本語のエンコードも処理する仕組みですが,UTF-8はどう
>>>だったっけかな。たしかバケずにいけてた気がする・・・
>>>ご判断におまかせいたします。(笑)
>>
>>+1
>>簡単にできるようであれば、ぜひとも、お願いいたします :)
>
>
> ぐはぁ,
> 簡単に設定できるはずが,やってみたら違ってた〜〜〜。
> どうもCVSのバージョンが1.11から1.12で,loginfoで書けるマクロ
> が変わってしまっているようで,しかもそのマクロを展開した結果
> たとえば
> %{sVv} だと "proj名 ファイル,新rev,旧rev"
> となるはずだが,"ファイル 新rev 旧rev" となっちまいやがんの。
> 結局新しいCVSに対応するには,マクロは %p %{sVv} と書いておいて
> コンマ区切りでない部分はスクリプト側で挿入しなきゃいかんかった。
>
> ぜーぜー。試行錯誤で実は何十回も無意味コミットを打ちまくって
> ようやく動くようになりました。
> さっき飛んだコミットメールの文中では,ViewCVSへのリンクがおか
> しいのですが,設定はなおしてあるので次回のコミットメールから
> はなおっていることでしょう。
>
> loginfo2mail.plは 結構手直しを入れたので,もし今後のプロジェ
> クトでも使う場合は,一次開発元やインターネットのそこらに転が
> ってるものではなくてココから取っていったほうがよいでせう。
>
> でわでわ。
>
> _______________________________________________
> Jetspeed-japan-trans mailing list
> Jetspeed-japan-trans @ lists.sourceforge.jp
> http://lists.sourceforge.jp/mailman/listinfo/jetspeed-japan-trans
>
--------------------------------------
STOP HIV/AIDS.
Yahoo! JAPAN Redribbon Campaign 2005
http://pr.mail.yahoo.co.jp/redribbon/
From m.matsuda @ appliedjapan.com Tue Dec 27 12:21:05 2005
From: m.matsuda @ appliedjapan.com (Applied_MATSUDA Masaaki)
Date: Tue, 27 Dec 2005 12:21:05 +0900
Subject: [Jetspeed-japan-trans] =?iso-2022-jp?b?UmU6IBskQiQkJG0kJCRtGyhC?=
=?iso-2022-jp?b?GyRCSlY/LhsoQg==?=
In-Reply-To: <43B05F31.2050705@yahoo.co.jp>
References: <43B05F31.2050705@yahoo.co.jp>
Message-ID: <20051227122105.87466196@appliedjapan.com>
TigerCatです。
>お疲れさまでした。今、コミットしてみましたが、
>完璧ですね〜。結構、便利だと思うので、他の
>プロジェクトでもどんどん使っていきたいところです :)
ひさびさにPerlを書きましたよ(笑)。ガキの頃は眠っていても
書けるほどPerlて簡単ね〜と思っていたのに,今や全部忘れて
るもんだからリファレンスを参照しながらで,情けない。
何でも1行で済ませてしまうようなミラクル技とか,忘れたよ。
あ,そうだ,菅谷さんにはひとつお願いがありました。
多分,このMLの保留キューに,差出人が
jetspeed-japan-trans @ lists.sourceforge.jp
なコミットメールが入っていると思います。
破棄しちゃってかまいませんのでよろしくです。
コミットメールの差出人は,loginfo2mail.pl的には固定だった
ので,MLのアドレスを使ったのですが・・・
それが多分投稿可能になっていなかったので・・・
そこらによくあるコミットメールスクリプト同様に,コミット
した人のアカウントをFromにするようにしました。
これでMLのポストはすんなりできたと。
そんな具合なloginfo2mail.plですが,少し気になる点も・・・
・まずはメールタイトルですが
CVS-Update: jetspeed-2-trans/ja/xdocscommitted by shinsuke
という具合にcommittedの前にスペースが無くないですか?
(私のメーラだけかもしれませんが!)
ソースを確認しましたらちゃんとスペース入れてるんスよ。
おかしぃなぁ。スペース2コにすれば改善するかな。(笑)
・差出人の表示名を出したほうがいい?
差出人は,コミットした人のアカウント名@users.sourcegorge.jp
にしていますが,ちまたによくあるスクリプトではちゃんと
"TigerCat"で表示名込みで
送ってくるんですよねぇ。
ためしにfingerで取得しようとしたけど,Permission Denied
だし・・・/etc/passwdからgrepしようとしたら,どうもコレ
使ってなくて,NISなのかLDAPやらで認証してる模様で・・・
まぁ表示名なんて無くても害はないけど,いい方法ないかね。
・返信先はMLがよい?
急遽コミットした人をFromにセットしたのはいいが,返信アド
レスはひょっとしてMLにしといたほうがいいのかね。
loginfo2mail.pl的には元々返信アドレスをセットできたよう
だが,妙にRFCまんま読みな実装で・・・通常のメーラでは
Return-path: とか認識しないようで。(Return-to:だよね普通)
これを手直しして復活させるべきかどうかと・・・
んで返信先をMLとかにする,みたいな?
p.s.
ViewCVSでもUTF-8の文字バケしているようですね・・・
CVSWebではバケないのに・・・
From shinsuke @ yahoo.co.jp Tue Dec 27 21:57:40 2005
From: shinsuke @ yahoo.co.jp (Shinsuke SUGAYA)
Date: Tue, 27 Dec 2005 21:57:40 +0900
Subject: [Jetspeed-japan-trans] =?iso-2022-jp?b?UmU6IBskQiQkJG0kJCRtGyhC?=
=?iso-2022-jp?b?GyRCSlY/LhsoQg==?=
In-Reply-To: <20051227122105.87466196@appliedjapan.com>
References: <43B05F31.2050705@yahoo.co.jp>
<20051227122105.87466196@appliedjapan.com>
Message-ID: <43B13A44.2060905@yahoo.co.jp>
こんにちは、菅谷です。
> あ,そうだ,菅谷さんにはひとつお願いがありました。
> 多分,このMLの保留キューに,差出人が
> jetspeed-japan-trans @ lists.sourceforge.jp
> なコミットメールが入っていると思います。
> 破棄しちゃってかまいませんのでよろしくです。
了解です。あとで処理しておきます。
> ・まずはメールタイトルですが
> CVS-Update: jetspeed-2-trans/ja/xdocscommitted by shinsuke
> という具合にcommittedの前にスペースが無くないですか?
改行とタブが入っているような気がします。
> ・差出人の表示名を出したほうがいい?
> 差出人は,コミットした人のアカウント名@users.sourcegorge.jp
> にしていますが,ちまたによくあるスクリプトではちゃんと
> "TigerCat"で表示名込みで
> 送ってくるんですよねぇ。
> ためしにfingerで取得しようとしたけど,Permission Denied
> だし・・・/etc/passwdからgrepしようとしたら,どうもコレ
> 使ってなくて,NISなのかLDAPやらで認証してる模様で・・・
> まぁ表示名なんて無くても害はないけど,いい方法ないかね。
個人的には、どちらで OK です :)
> ・返信先はMLがよい?
> 急遽コミットした人をFromにセットしたのはいいが,返信アド
> レスはひょっとしてMLにしといたほうがいいのかね。
> loginfo2mail.pl的には元々返信アドレスをセットできたよう
> だが,妙にRFCまんま読みな実装で・・・通常のメーラでは
> Return-path: とか認識しないようで。(Return-to:だよね普通)
> これを手直しして復活させるべきかどうかと・・・
> んで返信先をMLとかにする,みたいな?
ML の方がよいと思います。個人的には、送信されたものには、
ML の方で Reply-To: を付けているので、特に問題がないのですが。
と言う感じで、通常のメーラーはReply-To: を認識すると
思っていたのですが・・・。
shinsuke
--------------------------------------
Yahoo! Mail - supported by 10million people
http://pr.mail.yahoo.co.jp/mail_pr/
From m.matsuda @ appliedjapan.com Wed Dec 28 00:05:47 2005
From: m.matsuda @ appliedjapan.com (Applied_MATSUDA Masaaki)
Date: Wed, 28 Dec 2005 00:05:47 +0900
Subject: [Jetspeed-japan-trans] =?iso-2022-jp?b?UmU6IBskQiQkJG0kJCRtGyhC?=
=?iso-2022-jp?b?GyRCSlY/LhsoQg==?=
In-Reply-To: <43B13A44.2060905@yahoo.co.jp>
References: <43B13A44.2060905@yahoo.co.jp>
Message-ID: <20051228000547.88415385@appliedjapan.com>
こちらTigerCat。
>> ・まずはメールタイトルですが
>> CVS-Update: jetspeed-2-trans/ja/xdocscommitted by shinsuke
>> という具合にcommittedの前にスペースが無くないですか?
>
>改行とタブが入っているような気がします。
そ,それはまことですか?
スクリプト上ではそうなってないのですが・・・
\tの削除とchompかませばOKかな。
>> ・差出人の表示名を出したほうがいい?
>> 差出人は,コミットした人のアカウント名@users.sourcegorge.jp
>> にしていますが,ちまたによくあるスクリプトではちゃんと
>> "TigerCat"で表示名込みで
>> 送ってくるんですよねぇ。
>> ためしにfingerで取得しようとしたけど,Permission Denied
>> だし・・・/etc/passwdからgrepしようとしたら,どうもコレ
>> 使ってなくて,NISなのかLDAPやらで認証してる模様で・・・
>> まぁ表示名なんて無くても害はないけど,いい方法ないかね。
>
>個人的には、どちらで OK です :)
もう近頃UNIXコマンドも忘れがちで・・・
idコマンドとか試してみて, id shinsuke バシッとか
やったら何やら出てきてフフッと思ったのだが,実行に
2〜3秒かかる?!のとお目当てのフルネームカラムが取れ
てないっぽいので・・・
どなたか良い方法に気づいたら報告していただくという
ことでよろしくです。
>> ・返信先はMLがよい?
>> 急遽コミットした人をFromにセットしたのはいいが,返信アド
>> レスはひょっとしてMLにしといたほうがいいのかね。
>> loginfo2mail.pl的には元々返信アドレスをセットできたよう
>> だが,妙にRFCまんま読みな実装で・・・通常のメーラでは
>> Return-path: とか認識しないようで。(Return-to:だよね普通)
がびーん。↑(Reply-to:だよね普通)↑ でした。おおボケ。
>> これを手直しして復活させるべきかどうかと・・・
>> んで返信先をMLとかにする,みたいな?
>
>ML の方がよいと思います。個人的には、送信されたものには、
>ML の方で Reply-To: を付けているので、特に問題がないのですが。
>と言う感じで、通常のメーラーはReply-To: を認識すると
>思っていたのですが・・・。
おおボケかますから意味が通じなかったのだと思います。
すみません。
元のloginfo2mail.plはReturn-path: に指定してたりなので
それが認識されないということなのです。
Reply-to: はさすがに認識されないメーラがあったら驚きで
すから。(笑)
というか,MLにポストするならML側でReply-toをつけて
くれるんですよね。てことはこれで一件落着ですね。
ではでは。
From karma @ jazz.email.ne.jp Wed Dec 28 13:27:55 2005
From: karma @ jazz.email.ne.jp (KATOH Yasufumi)
Date: Wed, 28 Dec 2005 13:27:55 +0900
Subject: [Jetspeed-japan-trans] =?iso-2022-jp?b?UmU6IBskQiQkJG0kJCRtGyhC?=
=?iso-2022-jp?b?GyRCSlY/LhsoQg==?=
In-Reply-To: <20051228000547.88415385@appliedjapan.com>
References: <43B13A44.2060905@yahoo.co.jp>
<20051228000547.88415385@appliedjapan.com>
Message-ID: <87bqz1g81g.wl%karma@jazz.email.ne.jp>
加藤泰文です.
>>> On Wed, 28 Dec 2005 00:05:47 +0900
in message "[Jetspeed-japan-trans] Re: いろいろ返信"
Applied_MATSUDA Masaaki-san wrote:
> 元のloginfo2mail.plはReturn-path: に指定してたりなので
> それが認識されないということなのです。
Return-Path ってメールサーバが付ける物だから,スクリプトが付けてたら変
な気がしますね.まあ普通の MUA は使わないですよね.
--
==============================================
(((( 加藤泰文
○-○ karma @ jazz.email.ne.jp
==============================================
(Web Page) http://park2.wakwak.com/%7Ekarma/
==============================================
From karma @ jazz.email.ne.jp Wed Dec 28 16:45:45 2005
From: karma @ jazz.email.ne.jp (KATOH Yasufumi)
Date: Wed, 28 Dec 2005 16:45:45 +0900
Subject: [Jetspeed-japan-trans] Re: getting-started-source.xml
In-Reply-To: <43AB2040.1000705@yahoo.co.jp>
References: <87k6dx3d5j.wl%karma@jazz.email.ne.jp>
<43AB2040.1000705@yahoo.co.jp>
Message-ID: <87irt9is0m.wl%karma@jazz.email.ne.jp>
加藤泰文です.
とりあえず getting-started-source.xml の翻訳が完成しましたので,お送り
致します.
怪しげな部分もありますが,自分でチェックするよりは,皆さんに見てもらっ
た方がよさそうですし.^^;
--
==============================================
(((( 加藤泰文
○-○ karma @ jazz.email.ne.jp
==============================================
(Web Page) http://park2.wakwak.com/%7Ekarma/
==============================================
-------------- next part --------------
テキスト形式以外の添付ファイルを保管しました...
ファイル名: getting-started-source.xml
型: application/octet-stream
サイズ: 66395 バイト
説明: 無し
URL: http://lists.sourceforge.jp/mailman/archives/jetspeed-japan-trans/attachments/20051228/076e37e2/attachment.obj
From karma @ jazz.email.ne.jp Wed Dec 28 16:48:20 2005
From: karma @ jazz.email.ne.jp (KATOH Yasufumi)
Date: Wed, 28 Dec 2005 16:48:20 +0900
Subject: [Jetspeed-japan-trans] guide-app-servers.xml
Message-ID: <87hd8tirwb.wl%karma@jazz.email.ne.jp>
加藤泰文です.
次は guide-app-servers.xml を翻訳します.
--
==============================================
(((( 加藤泰文
○-○ karma @ jazz.email.ne.jp
==============================================
(Web Page) http://park2.wakwak.com/%7Ekarma/
==============================================
From karma @ jazz.email.ne.jp Wed Dec 28 16:51:46 2005
From: karma @ jazz.email.ne.jp (KATOH Yasufumi)
Date: Wed, 28 Dec 2005 16:51:46 +0900
Subject: [Jetspeed-japan-trans] Re: getting-started-source.xml
In-Reply-To: <87irt9is0m.wl%karma@jazz.email.ne.jp>
References: <87k6dx3d5j.wl%karma@jazz.email.ne.jp>
<43AB2040.1000705@yahoo.co.jp>
<87irt9is0m.wl%karma@jazz.email.ne.jp>
Message-ID: <87fyodirql.wl%karma@jazz.email.ne.jp>
加藤泰文です.
おっと忘れてた.getting-started-source を訳していて気づいたこと.
- 最初のセクション "Naming Conventions and Basic Assumptions" だけ番号
がないですね.きっと "1. Naming Conventions and Basic Assumptions"で
すよね.
- HTML には出てこないかも知れませんが,文書の Property の subtitle に
"Gettin gready to modify Jetspeed" とありますが,きっと "Getting
ready..." かな?
--
==============================================
(((( 加藤泰文
○-○ karma @ jazz.email.ne.jp
==============================================
(Web Page) http://park2.wakwak.com/%7Ekarma/
==============================================
From tigercat @ users.sourceforge.jp Wed Dec 28 20:04:27 2005
From: tigercat @ users.sourceforge.jp (tigercat @ users.sourceforge.jp)
Date: Wed, 28 Dec 2005 20:04:27 +0900
Subject: [Jetspeed-japan-trans] CVS-Update: jetspeed-2-trans/ja/xdocs
committed by tigercat
Message-ID: <20051228110427.5FF1D2AC029@users.sourceforge.jp>
Update of /cvsroot/jetspeed-japan/jetspeed-2-trans/ja/xdocs
In directory sf-cvs:/tmp/cvs-serv4374/ja/xdocs
Modified Files:
getting-started-source.xml
Log Message:
Added Japanese translation. Contributed by KATOH Yasufumi, thank you very much.
jetspeed-2-trans/ja/xdocs/getting-started-source.xml 1.1.1.1 -> 1.2 (modified)
http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/jetspeed-japan/jetspeed-2-trans/ja/xdocs/getting-started-source.xml.diff?r1=1.1.1.1&r2=1.2
===================================================================
RCS file: jetspeed-2-trans/ja/xdocs/getting-started-source.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- getting-started-source.xml 2005/12/16 03:43:36 1.1.1.1
+++ getting-started-source.xml 2005/12/28 11:04:27 1.2
@@ -1,1115 +1,2069 @@
-
-
-
-
-
- Getting Started with Jetspeed 2 using a Source Release
-
- Gettin gready to modify Jetspeed
-
-
-
-
-
-
-
-
-
-
-
-
- Unless otherwise specified, you should be
- running all maven build commands from within the
- Jetspeed directory (if you are just building
- Jetspeed) or from within your custom portal
- directory.
-
-
- You must use "/" as a file seperator on both
- *nix and windows, e.g. c:/windows, and /home.
-
-
-
-
-
- Below is a listing of common conventions used within
- this document.
-
-
- Variables are represented as ${
- some_variable
- }. This may signify a setting in Jetspeed or may
- represent a setting within your environment.
- Properties files are also capable of specifying
- variables within them.
-
-
- For example, ${org.apache.jetspeed.server.home}
- references either a property defined further up in
- the properties file, a variable that has been
- defined somehwere within the build process or
- defined in another build file within Jetspeed.
-
-
-
- ${USER_HOME}
- : This is the user's home directory. For Windows
- systems, this generally c:\Documents and
- Settings\${userName} where ${userName} is the
- name you use to log into windows.
-
- ${USER.HOME} is synonymous with ${USER_HOME}
- within this document.
-
-
- ${CATALINA_HOME}
- : This is the location of your tomcat
- installation, e.g.
- c:/tomcat
- .
-
-
-
-
-
-
- Subversion (SVN)
-
- is used in the Jetspeed project to manage the source
- files. SVN is very similar to CVS. For those user's
- on Windows system who prefer non-command line access
- we suggest using
-
- TortoiseSVN
-
- which plugs into your Windows Explorer view. For
- those using the Eclipse IDE, the
- Subclipse
- plugin is available for SVN access.
-
-
-
-
- We will not go into the specifics of Maven as that
- is beyond the scope of this document. However, here
- are a few bits of standard maven jargon we feel is
- important for you to know.
-
-
- You will see mention of a
- maven repository
- in this document. When you install Maven the .maven/
- directory is created in your ${USER_HOME) directory.
-
- Under .maven/ you will see a
- repository
- directory. This is were Maven stores all the jars
- that it downloads when you run your builds. This is
- also were Maven puts your jars and wars that you
- build. They will be stored in a directory structure
- that has the format of
- ${groupId}/${projectId}/jars/${projectId}-{$version}.jar
- for jar files and
- ${groupId}/${projectId}/wars/${projectId}.war for
- war files. The ${groupId}, ${projectId} and
- ${version} variables are discussed later on in this
- document. Jar and war files will also be created in
- your project in the
- /target
- directory.
-
-
-
-
-
- You need to set a few properties.
-
- Creating your own custom portal is very easy with the
- maven plugin provided by Jetspeed 2. And, it is used
- when you build jetspeed from source as well. In fact,
- the jetspeed-2 build procedure is just one example of a
- custom portal configuration and setup.
-
-
- The Jetspeed 2 maven-plugin defines default values for
- most of the properties you can set, but not all. When
- you download or checkout the jetspeed-2 source tree,
- you'll see it contains a project.properties file in the
- root folder overriding and setting some of these
- properties.
-
-
- As said before: not all properties are provided with a
- default value: you
- must
- specify a few yourself. And you'll most likely want to
- override some others.
-
-
- Set or override the build or maven-plugin properties in
- your
- ${USER_HOME}/build.properties
- file.
-
-
-
-
- Property
- Description
- Default value
-
-
-
- org.apache.jetspeed.portal.home
-
-
- The folder where the maven-plugin will
- (re)create or update your custom portal
- maven project configuration (with goal
- j2:portal.conf.project
- ). This will be where you will be performing
- all of your future custom portal
- development.
-
- Example:
- /home/myportal/
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.portal.groupId
-
-
-
- The (maven) short name of your portal
- project group.
-
- This value is used for the maven repository
- folder in which the project artifacts (like
- the portal war file) is stored.
-
- Example:
- myprojects
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.portal.artifactId
-
-
-
- The (maven) short name of your portal
- project.
-
- This value is used for the portal war file
- and the (portal) web application context
- name.
-
- Example:
- myportal
-
-
- no default
-
-
-
-
- org.apache.jetspeed.portal.name
-
-
- The (maven) full name of your portal
- project.
-
- This value is used by maven for generating
- JavaDoc titles.
-
- Example:
- My Test Portal
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.portal.currentVersion
-
-
-
- The current version of your portal project.
-
- This value is used by maven as name postfix
- for the generated artifacts.
-
- Example:
- 1.0
-
-
- no default
-
-
-
-
-
-
- The following properties all specify a subfolder of
- the
- ${org.apache.jetspeed.portal.home}
- location as defined above.
-
-
-
- Property
- Description
- Default value
-
-
-
-
- org.apache.jetspeed.portal.conf.dir
-
-
-
- The folder where the maven-plugin will
- generate and copy application server
- specific configuration files as a tomcat
- application context descriptor.
-
- This folder and its contents is created or
- updated by plugin goal
- j2:portal.conf.tomcat
- .
-
-
- target/portal-conf
-
-
-
-
-
- org.apache.jetspeed.portal.sql.dir
-
-
-
- The folder where the maven-plugin will
- generate and copy portal and database server
- specific sql DDL and DML scripts.
-
- This folder and its contents is always
- (re)created by plugin goal
- j2:portal.conf.sql
- .
-
-
- target/portal-sql
-
-
-
-
-
- org.apache.jetspeed.portal.db.dir
-
-
-
- The folder where the maven-plugin will
- create its build-in HSQLDB database(s).
-
- This folder and its contents is created or
- updated by plugin goal
- j2:start.production.server
- or
- j2:start.test.server
- .
-
-
- target/portal-db
-
-
-
-
-
- org.apache.jetspeed.portal.webapp.dir
-
-
-
- The folder where the maven-plugin will copy
- the standard jetspeed web application
- resources.
-
- This folder and its contents is created or
- updated by plugin goal
- j2:portal.copy.webapp
- .
-
-
-
- target/${org.apache.jetspeed.portal.artifactId}
-
-
-
-
-
-
- org.apache.jetspeed.portal.target.dir
-
-
-
- The folder where the maven-plugin will
- generate and copy runtime portal
- configuration files.
-
- These configuration files contain values
- derived from build/plugin properties for the
- portal and OJB.
-
- This folder and its contents is created or
- updated by plugin goal
- j2:portal.conf.jetspeed
- and goal
- j2:portal.conf.ojb
- .
-
-
-
- target/${org.apache.jetspeed.portal.artifactId}
-
-
-
-
-
-
-
-
- Note: The maven-plugin currently only supports
- the Tomcat Server 5.0.x or 5.5.x
-
-
-
-
- Property
- Description
- Default value
-
-
-
- org.apache.jetspeed.server.home
-
-
- The root folder of your Tomcat server
- installation.
-
- Example:
- ${CATALINA_HOME}/
- .
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.server.shared
-
-
-
- The location of the shared jars in your
- Tomcat installation.
-
- Example:
-
- ${org.apache.jetspeed.server.home}/shared/lib/
-
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.deploy.war.dir
-
-
-
- The location of web applications in your
- Tomcat installation.
-
- Example:
-
- ${org.apache.jetspeed.server.home}/webapps/
-
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.services.autodeployment.user
-
-
-
- A Tomcat user with the manager role.
-
- Used to access the Tomcat Manager
- application from within the portal,
- explained below.
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.services.autodeployment.password
-
-
-
- The password of the Tomcat user above.
-
- Used to access the Tomcat Manager
- application from within the portal,
- explained below.
-
-
- no default
-
-
-
-
-
- org.apache.jetspeed.catalina.version.major
-
-
-
- The major version of the Tomcat server you
- are using: 5 or 5.5
-
- Example:
- 5.5
-
-
- no default
-
-
-
-
-
-
- Jetspeed-2 and its maven-plugin uses, as well as
- provides, by default a HSQLDB database.
-
-
- If you want to use a different database you will
- need to override the following properties:
-
-
-
- Property
- Description
- Default value
-
-
-
-
- org.apache.jetspeed.production.database.default.name
-
-
-
- The type of database you are using. Used for
- sql script generation with Torque.
-
- Currently supported databases (with
- corresponding Torque target database name):
-
- hsql (hypersonic)
- oracle (oracle)
- mysql (mysql)
- postgres (postresql)
- mssql (mssql)
-
-
- hsql
-
-
-
-
- org.apache.jetspeed.production.database.url
-
-
- The jdbc connection url
- jdbc:hsqldb:hsql://127.0.0.1:9001
-
-
-
-
- org.apache.jetspeed.production.database.user
-
-
- The database user name to connect with.
- sa
-
-
-
-
- org.apache.jetspeed.production.database.password
-
-
-
- The database user its password to connect
- with.
-
-
- empty
-
-
-
-
-
- org.apache.jetspeed.production.database.driver
-
-
- The jdbc driver class name
- org.hsqldb.jdbcDriver
-
-
-
-
- org.apache.jetspeed.production.jdbc.drivers.path
-
-
-
- A Java classpath style path to the jdbc
- driver classes or jar(s) needed for
- connecting to the database.
-
- Example:
-
- /lib/ojdbc14.jar;/lib/nls_charset12.jar
-
-
-
- empty
-
-
-
-
-
-
- Make sure you have define at least the required
- properties as described above in your
- ${USER_HOME}/build.properties
- . A minimal custom portal configuration using the
- default HSQLDB database can be something like:
-
-
-
-
- Note: If you're going to build the default
- Jetspeed 2 portal directly from the source only
- the
- org.apache.jetspeed.portal.home
- property is required from the set of required
- portal configuration properties.
-
-
-
-
-
-
- Now we're going to configure, setup and build a new
- custom portal application using the Jetspeed-2
- maven-plugin.
-
-
-
- To be able to setup a Jetspeed 2 based portal the
- maven remote repository lookup needs to be
- configured properly in your
- ${USER_HOME}/build.properties
- :
-
-
-
-
- Note: the order in which these repositories must
- be specified is significant!
-
-
-
-
-
- The first time, and when you want to upgrade to a
- newer version of Jetspeed 2, you need to install the
- maven-plugin as follows:
-
-
-
-
- Note: you can set the version flag to the
- specific version you want to install,
- 2.0-M4-SNAPSHOT is just an example here.
-
-
-
-
-
- Once you have the maven-plugin installed and set
- properties as needed, generate a default portal
- configuration using the plugin as follows:
-
-
-
-
- This maven goal actually executes several
- subgoals which are further described in the
-
- maven-plugin documentation
-
- itself.
-
-
-
-
-
- This section doesn't specify anything to do. After
- the portal project is generated you can adapt and
- customize it to your taste by overriding and merging
- your own configurations and extensions.
-
-
- You can regenerate or update (part of) your portal
- project with the
- j2:portal.genapp
- goal as described in the previous section or use its
- subgoals directly.
-
-
-
-
- Once your portal configuration and setup is ready,
- you can build and install the portal application in
- your local maven repository (as needed for
- deployment) using the following standard maven goal
- from your custom portal project directory (in
- ${org.apache.jetspeed.portal.home}):
-
-
-
-
-
- You are now ready to deploy the new portal
- application. For this, skip the following section on
- building the Jetspeed 2 portal from source and
- continue with the
- deployment
- section.
-
-
-
-
-
- Build the Jetspeed 2 portal directly from the source is
- somewhat easier to do but should only be done if you
- don't want to create a new, customizable portal.
-
-
-
- The Jetspeed 2 source contains a
- project.properties
- file which provides all of the required portal
- configuration settings as described
-
- above
-
- .
-
-
- You should
-
- not
-
- define any of those properties in your
- ${USER_HOME}/build.properties
- .
-
- Instead, you
- must
- set a
- org.apache.jetspeed.project.home
- property, specifying the location where you expanded
- the downloaded source or checked out the source from
- subversion, like:
-
-
-
-
- Note: you still need to specify the required
- application server properties as described
-
- above
-
- .
-
-
-
- The Jetspeed 2 project.properties uses this property
- to define the required
- org.apache.portal.home
- :
-
-
-
- So, they are the same when you build the Jetspeed 2
- portal from the source.
-
-
- When you are going to deploy the portal as described
- further below, you'll see references to the
- org.apache.jetspeed.portal.home
- which you can translate with the root folder of your
- Jetspeed 2 source.
-
-
- If you want to run the testcases when building the
- Jetspeed 2 sources
- and
- don't want to use the default HSQLDB test database,
- you need to override the default test database
- properties, similar to the production database
- properties as described
-
- above
-
- :
-
-
-
- org.apache.jetspeed.test.database.default.name
-
-
-
-
- org.apache.jetspeed.test.database.url
-
-
-
-
- org.apache.jetspeed.test.database.user
-
-
-
-
- org.apache.jetspeed.test.database.password
-
-
-
-
- org.apache.jetspeed.test.database.driver
-
-
-
-
- org.apache.jetspeed.test.database.drivers.path
-
-
-
-
- Note: due to outstanding issue
-
- JS2-320
-
- you currently
- must
- use hard coded values for the test database
- properties.
-
-
-
-
-
- Instead of downloading and installing the Jetspeed 2
- maven-plugin, you are going to build and install it
- directly from the source. You will need to repeat
- this every time you update to a newer version of
- Jetspeed 2 or change its project configuration, the
- plugin itself or the resources used by the plugin.
-
-
- Build and install the maven-plugin as follows from
- the root directory of the Jetspeed-2 source:
-
-
-
-
-
-
-
- If you are going to run the testcases and are using
- the default HSQLDB database configuration, you will
- need to start the test database before building
- Jetspeed 2 in a
- separate
- console:
-
-
-
-
-
- After the build is finished you can stop the
- database and close this console with a
- Ctrl-C
- .
-
-
-
-
- For a full build and installation of the portal and
- the demo portlet applications in your local maven
- repository run:
-
-
-
-
-
- But, if you also want to run the testcases during
- the build run the following instead:
-
-
-
-
-
- You are now ready to deploy the Jetspeed 2 Portal.
-
-
-
-
-
-
- If you are using the default HSQLDB database you
- need to start it before deploying the portal.
-
-
- To start the HSQLDB production database run the
- following in a
- separate
- console:
-
-
-
-
-
- You need to have this database running during the
- deployment and while running the application server.
- Afterwards you can stop the database and close this
- console with a
- Ctrl-C
- .
-
-
- Note: this is required when using the
- j2:quickStart
- goal as described below. The Jetspeed 2 maven-plugin
- provides other (sub)goals which you can use without
- (re)creating a production database and/or inserting
- default portal configuration data. See the
-
- Plugin documentation
-
- for further information about the available goals.
-
-
-
-
- We currently only cover deploying to Tomcat 5 or
- Tomcat 5.5.
-
-
- Information about deployment to other application
- servers can be found at the The Jetspeed 2
-
- Wiki
-
- .
-
-
- To deploy a default Jetspeed 2 portal, including the
- demo portlet applications, run the following in a
- separate
- console:
-
-
-
-
- Note: the
-
- maven-plugin documentation
-
- described other goals you can use to customize
- the deployment to your taste.
-
-
-
-
-
- The final step is starting up your Tomcat server and
- the portal will automatically install any deployed
- portlet applications.
-
-
- Then you can access the portal with your browser at:
- http://localhost:8080/jetspeed
- or replace "jetspeed" in the above url with the name
- of you own portal application (
-
- ${org.apache.jetspeed.portal.artifactId}
-
- ).
-
-
-
-
- With the default Jetspeed 2 portal deployment,
- several example user accounts are inserted into the
- portal database with which you can logon to the
- portal:
-
-
- username
- password
- roles
-
-
-
- admin
-
-
- admin
-
-
- admin, manager, user
-
-
-
-
- manager
-
-
- manager
-
-
- manager, user
-
-
-
-
- jetspeed
-
-
- jetspeed
-
-
- manager
-
-
-
-
- user
-
-
- user
-
-
- user
-
-
-
-
- tomcat
-
-
- tomcat
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+ [Getting Started with Jetspeed 2 using a Source Release] $B%=!<%9%j%j!<%9$r;H$C$?(B Jetspeed2 $B$N$O$8$a$+$?(B
+
+ [Gettin gready to modify Jetspeed] Jetspeed $B$rJQ99$9$k=`Hw$r$9$k(B
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Unless otherwise specified, you should be
+ running all maven build commands from within the
+ Jetspeed directory (if you are just building
+ Jetspeed) or from within your custom portal
+ directory.
+
+
+ You must use "/" as a file seperator on both
+ *nix and windows, e.g. c:/windows, and /home.
+
+
+
+
+
+ $BFCJL$KDj$a$N$J$$8B$j!"A4$F$N(B maven $B$N%S%k%I%3%^%s%I$O(B (Jetspeed $B$r%S%k%I$9$k$H$-$O(B) Jetspeed $B%G%#%l%/%H%j$G
+ * *nix $B4D6-$G$"$C$F$b!"(BWindows $B4D6-$G$"$C$F$b!"Nc$($P(B c:/windows $B$d(B /home $B$N$h$&$K!"%G%#%l%/%H%j$N%;%Q%l!<%?$H$7$F$O(B "/" $B$r;HMQ$7$J$1$l$P$$$1$^$;$s!#(B
+
+
+
+
+
+
+
+ Below is a listing of common conventions used within
+ this document.
+
+
+ $B$3$NJ8=q$G;HMQ$9$k6&DL$N5,B'$r0J2<$K<($7$^$9!#(B
+
+
+
+ Variables are represented as ${
+ some_variable
+ }. This may signify a setting in Jetspeed or may
+ represent a setting within your environment.
+ Properties files are also capable of specifying
+ variables within them.
+
+
+
+ $BJQ?t$O(B ${ some_variable } $B$H$7$FI=$7$^$9!#$3$l$O(B Jetspeed $B$N @ _Dj$rI=$9$3$H$b=PMh$^$9$7!"$"$J$?$N4D6-Fb$G$N @ _Dj$rI=$9$3$H$b=PMh$^$9!#%W%m%Q%F%#%U%!%$%k$b$=$NCf$GJQ?t$r5-=R$9$k$3$H$,=PMh$^$9!#(B
+
+
+
+
+ For example, ${org.apache.jetspeed.server.home}
+ references either a property defined further up in
+ the properties file, a variable that has been
+ defined somehwere within the build process or
+ defined in another build file within Jetspeed.
+
+
+
+ $BNc$($P!"(B${org.apache.jetspeed.server.home} $B$O%W%m%Q%F%#%U%!%$%kFb$GDj5A$5$l$k$+$bCN$l$^$;$s$7!"%S%k%I%W%m%;%9Fb$N$I$3$+$GDj5A$5$l$kJQ?t$+$bCN$l$^$;$s$7!"(BJetspeed $BFb$NB>$N%S%k%I%U%!%$%kFb$GDj5A$5$l$k$+$bCN$l$^$;$s!#(B
+
+
+
+
+
+ ${USER_HOME}
+ : This is the user's home directory. For Windows
+ systems, this generally c:\Documents and
+ Settings\${userName} where ${userName} is the
+ name you use to log into windows.
+
+ ${USER.HOME} is synonymous with ${USER_HOME}
+ within this document.
+
+
+ ${CATALINA_HOME}
+ : This is the location of your tomcat
+ installation, e.g.
+ c:/tomcat
+ .
+
+
+
+
+
+
+ ${USER_HOME}
+ : $B%f!<%6$N%[!<%`%G%#%l%/%H%j$G$9!#(BWindows $B$G$O!"0lHLE*$K(B c:\Documents and Settings\${userName}\ $B$K$J$j$^$9!#$3$3$G(B ${userName} $B$O(B Windows $B$K%m%0%$%s$9$k$H$-$N%m%0%$%sL>$G$9!#(B
+
+
+ ${CATALINA_HOME}
+ : $B$"$J$?$,(B Tomcat $B$r%$%s%9%H!<%k$7$?>l=j$G$9!#Nc$($P(B c:/tomcat $B$J$I$G$9!#(B
+
+
+
+
+
+
+
+
+
+ Subversion (SVN)
+
+ is used in the Jetspeed project to manage the source
+ files. SVN is very similar to CVS. For those user's
+ on Windows system who prefer non-command line access
+ we suggest using
+
+ TortoiseSVN
+
+ which plugs into your Windows Explorer view. For
+ those using the Eclipse IDE, the
+ Subclipse
+ plugin is available for SVN access.
+
+
+
+
+ Subversion (SVN)
+
+ $B$O(B Jetspeed $B$N%=!<%9%U%!%$%k$r4IM}$9$k$?$a$K;H$o$l$^$9!#(BSVN $B$O(B CVS $B$K$H$F$b;w$F$$$^$9!#(BWindows $B%7%9%F%`$G%3%^%s%I%i%$%s$r;HMQ$7$J$$%f!<%6$O!"(B
+
+ TortoiseSVN
+
+ $B$r;H$C$F$_$k$HNI$$$G$7$g$&!#$3$N%D!<%k$O(B Windows Explorer $B$K%W%i%0%$%s$5$l$^$9!#(BEclipse IDE $B$r;H$C$F$$$k%f!<%6$O(B
+ Subclipse
+ $B%W%i%0%$%s$,(B SVN $B%"%/%;%9$K;HMQ=PMh$^$9!#(B
+
+
+
+
+
+
+
+ We will not go into the specifics of Maven as that
+ is beyond the scope of this document. However, here
+ are a few bits of standard maven jargon we feel is
+ important for you to know.
+
+
+
+ $B$3$NJ8=q$G$O!"(BMaven $B$N;EMM$K$D$$$F$O=R$Y$^$;$s!#$7$+$7!"$3$3$G$"$J$?$,CN$C$F$*$/$Y$-=EMW$J(B maven $B$N4pK\E*$J @ lLgMQ8l$r0J2<$K>/$7$@$15s$2$F$*$-$^$9!#(B
+
+
+
+
+ You will see mention of a
+ maven repository
+ in this document. When you install Maven the .maven/
+ directory is created in your ${USER_HOME) directory.
+
+ Under .maven/ you will see a
+ repository
+ directory. This is were Maven stores all the jars
+ that it downloads when you run your builds. This is
+ also were Maven puts your jars and wars that you
+ build. They will be stored in a directory structure
+ that has the format of
+ ${groupId}/${projectId}/jars/${projectId}-{$version}.jar
+ for jar files and
+ ${groupId}/${projectId}/wars/${projectId}.war for
+ war files. The ${groupId}, ${projectId} and
+ ${version} variables are discussed later on in this
+ document. Jar and war files will also be created in
+ your project in the
+ /target
+ directory.
+
+
+
+ $B$"$J$?$OJ8=qFb$G(B maven repository $B$K$D$$$F?($l$k$N$rL\$K$9$k$3$H$,$"$k$G$7$g$&!#(Bmaven $B$r%$%s%9%H!<%k$9$k$H!"(B.maven/ $B%G%#%l%/%H%j$,(B ${USER_HOME} $B%G%#%l%/%H%j$K:n @ .$5$l$^$9!#(B
+.maven/ $B0J2<$K(B repository $B$H$$$&%G%#%l%/%H%j$,$"$k$O$:$G$9!#$3$3$K$O%S%k%I$r
+
+
+
+
+
+
+
+
You need to set a few properties.
+
+ $B$$$/$D$+%W%m%Q%F%#$r @ _Dj$9$kI,MW$,$"$j$^$9!#(B
+
+
+
+ Creating your own custom portal is very easy with the
+ maven plugin provided by Jetspeed 2. And, it is used
+ when you build jetspeed from source as well. In fact,
+ the jetspeed-2 build procedure is just one example of a
+ custom portal configuration and setup.
+
+
+
+ $B%+%9%?%`$N%]!<%?%k$r:n$k$N$O(B Jetspeed 2 $B$,Ds6!$9$k(B Maven $B%W%i%0%$%s$r;H$($P$H$F$b4JC1$G$9!#%=!<%9$+$i(B Jetspeed $B$r%S%k%I$9$k;~$bF1MM$K(B Maven $B%W%i%0%$%s$r;H$$$^$9!#;v
+
+
+
+ The Jetspeed 2 maven-plugin defines default values for
+ most of the properties you can set, but not all. When
+ you download or checkout the jetspeed-2 source tree,
+ you'll see it contains a project.properties file in the
+ root folder overriding and setting some of these
+ properties.
+
+
+
+ Jetspeed 2 $B$N(B Maven $B%W%i%0%$%s$O @ _Dj2DG=$J$[$H$s$I$N%W%m%Q%F%#$K%G%U%)%k%HCM$rDj5A$7$F$$$^$9!#$7$+$7!"A4$F$KDj5A$5$l$F$$$k$o$1$G$O$"$j$^$;$s!#(BJetspeed 2 $B$N%=!<%9%D%j!<$r%@%&%s%m!<%I$7$?$j!"%A%'%C%/%"%&%H$7$?$H$-!"$3$l$i$N%W%m%Q%F%#$N$$$/$D$+$r @ _Dj$7$?$j>e=q$-$7$?$j$9$k(B project.properties $B%U%!%$%k$,%k!<%H%U%)%k%@$K$"$k$N$,$o$+$k$G$7$g$&!#(B
+
+
+
+
+ As said before: not all properties are provided with a
+ default value: you
+ must
+ specify a few yourself. And you'll most likely want to
+ override some others.
+
+
+
+ $BA0=R$N$h$&$K!"A4$F$N%W%m%Q%F%#$K%G%U%)%k%HCM$,Dj5A$5$l$F$$$k$o$1$G$O$"$j$^$;$s!#$$$/$D$+$N%W%m%Q%F%#$r;XDj(B $B$7$J$1$l$P$J$j$^$;$s(B $B!#$=$7$F!"BgBN$N>l9g$O$$$/$D$+$NCM$r>e=q$-$7$?$/$J$k$G$7$g$&!#(B
+
+
+
+
+ Set or override the build or maven-plugin properties in
+ your
+ ${USER_HOME}/build.properties
+ file.
+
+
+
+ $B%S%k%I%W%m%Q%F%#$b$7$/$O(B Maven $B%W%i%0%$%s$N%W%m%Q%F%#$O(B
+ ${USER_HOME}/build.properties
+ $B$K @ _Dj$b$7$/$O>e=q$-$7$F$/$@$5$$!#(B
+
+
+
+
+
+
+
+ Property
+ Description
+ Default value
+
+
+
+ org.apache.jetspeed.portal.home
+
+
+ The folder where the maven-plugin will
+ (re)create or update your custom portal
+ maven project configuration (with goal
+ j2:portal.conf.project
+ ). This will be where you will be performing
+ all of your future custom portal
+ development.
+
+ Example:
+ /home/myportal/
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.portal.groupId
+
+
+
+ The (maven) short name of your portal
+ project group.
+
+ This value is used for the maven repository
+ folder in which the project artifacts (like
+ the portal war file) is stored.
+
+ Example:
+ myprojects
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.portal.artifactId
+
+
+
+ The (maven) short name of your portal
+ project.
+
+ This value is used for the portal war file
+ and the (portal) web application context
+ name.
+
+ Example:
+ myportal
+
+
+ no default
+
+
+
+
+ org.apache.jetspeed.portal.name
+
+
+ The (maven) full name of your portal
+ project.
+
+ This value is used by maven for generating
+ JavaDoc titles.
+
+ Example:
+ My Test Portal
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.portal.currentVersion
+
+
+
+ The current version of your portal project.
+
+ This value is used by maven as name postfix
+ for the generated artifacts.
+
+ Example:
+ 1.0
+
+
+ no default
+
+
+
+
+
+
+
+ $B%W%m%Q%F%#(B
+ $B @ bL@(B
+ $B%G%U%)%k%HCM(B
+
+
+
+ org.apache.jetspeed.portal.home
+
+
+ Maven $B%W%i%0%$%s$,(B ($B:F(B) $B:n @ .$7$?$j!"%+%9%?%`%]!<%?%k$N(B Mave $B%W%m%8%'%/%H @ _Dj$,(B (
+ j2:portal.conf.project
+ $B%4!<%k$G(B) $B99?7$7$?$j$9$k%U%)%k%@!#$3$N%U%)%k%@$O%+%9%?%`$N%]!<%?%k3+H/$NA4$F$rl=j$G$9!#(B
+ $BNc(B:
+ /home/myportal
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.portal.groupId
+
+
+
+ $B$"$J$?$N%]!<%?%k%W%m%8%'%/%H%0%k!<%W$N(B (Maven $B$G$N(B) $B>JN,L>!#(B
+
+ $B$3$NCM$O(B ($B%]!<%?%k(B war $B%U%!%$%k$N$h$&$J(B) $B%W%m%8%'%/%H$N @ .2LJ*$rJd4V$7$F$*$/(B Maven $B$N%j%]%8%H%j%U%)%k%@$K;H$$$^$9!#(B
+
+ $BNc(B:
+ myprojects
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.portal.artifactId
+
+
+
+ $B$"$J$?$N%]!<%?%k%W%m%8%'%/%H$N(B (Maven $B$G$N(B) $B>JN,L>!#(B
+
+ $B$3$NCM$O%]!<%?%k(B war $B%U%!%$%k$d(B ($B%]!<%?%k(B) $B%&%'%V%"%W%j%1!<%7%g%s$N%3%s%F%-%9%HL>$K;H$$$^$9!#(B
+
+ $BNc(B:
+ myportal
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+ org.apache.jetspeed.portal.name
+
+
+ $B$"$J$?$N%]!<%?%k%W%m%8%'%/%H$N(B (Maven $B$G$N(B) $B%U%k%M!<%`!#(B
+
+ $B$3$NCM$O(B JaveDoc $B$N%?%$%H%k$r @ 8@.$9$k$N$K(B Maven $B$,;H$$$^$9!#(B
+
+ $BNc(B:
+ My Test Portal
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.portal.currentVersion
+
+
+
+ $B$"$J$?$N%]!<%?%k%W%m%8%'%/%H$N8=:_$N%P!<%8%g%s!#(B
+
+ $B$3$NCM$O%W%m%8%'%/%H$N @ 8@.J*$NL>A0$N:G8e$K(B Maven $B$KIU$12C$($i$l$^$9!#(B
+
+ Example:
+ 1.0
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+
+
+
+
+ The following properties all specify a subfolder of
+ the
+ ${org.apache.jetspeed.portal.home}
+ location as defined above.
+
+
+
+ $B$3$N$"$H$K=R$Y$k%W%m%Q%F%#$OA4$F(B
+ ${org.apache.jetspeed.portal.home}
+ $B$N%5%V%U%)%k%@$rDj5A$7$^$9!#(B
+
+
+
+
+
+ Property
+ Description
+ Default value
+
+
+
+
+ org.apache.jetspeed.portal.conf.dir
+
+
+
+ The folder where the maven-plugin will
+ generate and copy application server
+ specific configuration files as a tomcat
+ application context descriptor.
+
+ This folder and its contents is created or
+ updated by plugin goal
+ j2:portal.conf.tomcat
+ .
+
+
+ target/portal-conf
+
+
+
+
+
+ org.apache.jetspeed.portal.sql.dir
+
+
+
+ The folder where the maven-plugin will
+ generate and copy portal and database server
+ specific sql DDL and DML scripts.
+
+ This folder and its contents is always
+ (re)created by plugin goal
+ j2:portal.conf.sql
+ .
+
+
+ target/portal-sql
+
+
+
+
+
+ org.apache.jetspeed.portal.db.dir
+
+
+
+ The folder where the maven-plugin will
+ create its build-in HSQLDB database(s).
+
+ This folder and its contents is created or
+ updated by plugin goal
+ j2:start.production.server
+ or
+ j2:start.test.server
+ .
+
+
+ target/portal-db
+
+
+
+
+
+ org.apache.jetspeed.portal.webapp.dir
+
+
+
+ The folder where the maven-plugin will copy
+ the standard jetspeed web application
+ resources.
+
+ This folder and its contents is created or
+ updated by plugin goal
+ j2:portal.copy.webapp
+ .
+
+
+
+ target/${org.apache.jetspeed.portal.artifactId}
+
+
+
+
+
+
+ org.apache.jetspeed.portal.target.dir
+
+
+
+ The folder where the maven-plugin will
+ generate and copy runtime portal
+ configuration files.
+
+ These configuration files contain values
+ derived from build/plugin properties for the
+ portal and OJB.
+
+ This folder and its contents is created or
+ updated by plugin goal
+ j2:portal.conf.jetspeed
+ and goal
+ j2:portal.conf.ojb
+ .
+
+
+
+ target/${org.apache.jetspeed.portal.artifactId}
+
+
+
+
+
+
+
+
+ $B%W%m%Q%F%#(B
+ $B @ bL@(B
+ $B%G%U%)%k%HCM(B
+
+
+
+
+ org.apache.jetspeed.portal.conf.dir
+
+
+
+ $B$3$N%U%)%k%@$O(B Maven $B%W%i%0%$%s$,%"%W%j%1!<%7%g%s%5!<%P$N @ _Dj%U%!%$%k$r(B Tomcat $B$N%"%W%j%1!<%7%g%s$N%3%s%F%-%9%H5-=R;R$H$7$F @ 8@.$7%3%T!<$7$^$9!#(B
+
+ $B$3$N%U%)%k%@$H%U%)%k%@Fb$N%3%s%F%s%D$O(B
+ j2:portal.conf.tomcat
+ $B%W%i%0%$%s%4!<%k$K$h$C$F:n @ .$5$l$?$j99?7$5$l$?$j$7$^$9!#(B
+
+
+ target/portal-conf
+
+
+
+
+
+ org.apache.jetspeed.portal.sql.dir
+
+
+
+ $B$3$N%U%)%k%@$O(B Maven $B%W%i%0%$%s$,%]!<%?%k$d%G!<%?%Y!<%9%5!<%P$N(B sql DDL $B$H(B DML $B%9%/%j%W%H$r @ 8@.$7%3%T!<$7$^$9!#(B
+
+ $B$3$N%U%)%k%@$H%U%)%k%@Fb$N%3%s%F%s%D$O>o$K(B
+ j2:portal.conf.sql
+ $B%W%i%0%$%s%4!<%k$K$h$C$F(B ($B:F(B) $B @ 8@.$5$l$^$9!#(B
+
+
+ target/portal-sql
+
+
+
+
+
+ org.apache.jetspeed.portal.db.dir
+
+
+
+ $B$3$N%U%)%k%@$O(B Maven $B%W%i%0%$%s$,%S%k%I%$%s$N(B HSQLDB $B%G!<%?%Y!<%9$r:n @ .$7$^$9!#(B
+
+ $B$3$N%U%)%k%@$H%U%)%k%@Fb$N%3%s%F%s%D$O(B
+ j2:start.production.server
+ ??????+ j2:start.test.server
+ $B%W%i%0%$%s%4!<%k$K$h$C$F @ 8@.$5$l$?$j99?7$5$l$?$j$7$^$9!#(B
+
+
+ target/portal-db
+
+
+
+
+
+ org.apache.jetspeed.portal.webapp.dir
+
+
+
+ $B$3$N%U%)%k%@$O(B Maven $B%W%i%0%$%s$,I8=`$N(B Jetspeed $B$N%&%'%V%"%W%j%1!<%7%g%s$N%j%=!<%9$r%3%T!<$7$^$9!#(B
+
+ $B$3$N%U%)%k%@$H%U%)%k%@Fb$N%3%s%F%s%D$O(B
+ j2:portal.copy.webapp
+ $B%W%i%0%$%s%4!<%k$K$h$C$F @ 8@.$5$l$?$j99?7$5$l$?$j$7$^$9!#(B
+ .
+
+
+
+ target/${org.apache.jetspeed.portal.artifactId}
+
+
+
+
+
+
+ org.apache.jetspeed.portal.target.dir
+
+
+
+ $B$3$N%U%)%k%@$O(B Maven $B%W%i%0%$%s$,%i%s%?%$%`$N%]!<%?%k$N @ _Dj%U%!%$%k$r @ 8@.$7$?$j%3%T!<$7$?$j$7$^$9!#(B
+
+ $B$3$l$i$N @ _Dj%U%!%$%k$O%]!<%?%k$d(B OJB $B$N%S%k%I(B/$B%W%i%0%$%s%W%m%Q%F%#$+$i @ 8@.$5$l$?CM$r4^$_$^$9!#(B
+
+ $B$3$N%U%)%k%@$H%U%)%k%@Fb$N%3%s%F%s%D$O(B
+ j2:portal.conf.jetspeed
+ ??????+ j2:portal.conf.ojb
+ $B%W%i%0%$%s%4!<%k$K$h$C$F @ 8@.$5$l$?$j99?7$5$l$?$j$7$^$9!#(B
+
+
+
+ target/${org.apache.jetspeed.portal.artifactId}
+
+
+
+
+
+
+
+
+
+
+
+ Note: The maven-plugin currently only supports
+ the Tomcat Server 5.0.x or 5.5.x
+
+
+
+
+
+ $BCm0U(B: Maven$B%W%i%0%$%s$O8=;~E@$G$O(B Tomcat 5.0.x $B$^$?$O(B 5.5.x $B$N$_$r%5%]!<%H$7$^$9!#(B
+
+
+
+
+
+
+ Property
+ Description
+ Default value
+
+
+
+ org.apache.jetspeed.server.home
+
+
+ The root folder of your Tomcat server
+ installation.
+
+ Example:
+ ${CATALINA_HOME}/
+ .
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.server.shared
+
+
+
+ The location of the shared jars in your
+ Tomcat installation.
+
+ Example:
+
+ ${org.apache.jetspeed.server.home}/shared/lib/
+
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.deploy.war.dir
+
+
+
+ The location of web applications in your
+ Tomcat installation.
+
+ Example:
+
+ ${org.apache.jetspeed.server.home}/webapps/
+
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.services.autodeployment.user
+
+
+
+ A Tomcat user with the manager role.
+
+ Used to access the Tomcat Manager
+ application from within the portal,
+ explained below.
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.services.autodeployment.password
+
+
+
+ The password of the Tomcat user above.
+
+ Used to access the Tomcat Manager
+ application from within the portal,
+ explained below.
+
+
+ no default
+
+
+
+
+
+ org.apache.jetspeed.catalina.version.major
+
+
+
+ The major version of the Tomcat server you
+ are using: 5 or 5.5
+
+ Example:
+ 5.5
+
+
+ no default
+
+
+
+
+
+
+
+ $B%W%m%Q%F%#(B
+ $B @ bL@(B
+ $B%G%U%)%k%HCM(B
+
+
+
+ org.apache.jetspeed.server.home
+
+
+ Tomcat $B$r%$%s%9%H!<%k$7$?%k!<%H%U%)%k%@!#(B
+
+ Example:
+ ${CATALINA_HOME}/
+ .
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.server.shared
+
+
+
+ Tomcat $B$N6&M-$N(B jar $B$NCV>l!#(B
+
+ Example:
+
+ ${org.apache.jetspeed.server.home}/shared/lib/
+
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.deploy.war.dir
+
+
+
+ Tomcat $B$N%&%'%V%"%W%j%1!<%7%g%s$N>l=j!#(B
+
+ Example:
+
+ ${org.apache.jetspeed.server.home}/webapps/
+
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.services.autodeployment.user
+
+
+
+ manager $B%m!<%k$KB0$9$k(B Tomcat $B$N%f!<%6!#(B
+
+ $B8e$G @ bL@$9$k$h$&$K!"%]!<%?%kFb$+$i(B Tomcat Manager $B%"%W%j%1!<%7%g%s$X%"%/%;%9$9$k$N$K;H$$$^$9!#(B
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.services.autodeployment.password
+
+
+
+ $BA0=R$N(B Tomcat $B%f!<%6$N%Q%9%o!<%I!#(B
+
+ $B8e$G @ bL@$9$k$h$&$K!"%]!<%?%kFb$+$i(B Tomcat Manager $B%"%W%j%1!<%7%g%s$X%"%/%;%9$9$k$N$K;H$$$^$9!#(B
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+ org.apache.jetspeed.catalina.version.major
+
+
+
+ $B;HMQ$9$k(B Tomcat $B$N%a%8%c!<%P!<%8%g%s!#(B5 $B$b$7$/$O(B 5.5 $B$,;H$($^$9!#(B
+
+ $BNc(B:
+ 5.5
+
+
+ $B%G%U%)%k%HCM$J$7(B
+
+
+
+
+
+
+
+
+
+ Jetspeed-2 and its maven-plugin uses, as well as
+ provides, by default a HSQLDB database.
+
+
+
+ Jetspeed 2 $B$H(B Jetspeed 2 $B$N(B Maven $B%W%i%0%$%s$O%G%U%)%k%H$G$O(B HSQLDB $B$N%G!<%?%Y!<%9$r;HMQ$7$^$9!#(B
+
+
+
+
+ If you want to use a different database you will
+ need to override the following properties:
+
+
+
+ $B$b$70[$J$k%G!<%?%Y!<%9$r;HMQ$9$k$N$G$"$l$P!"0J2<$N%W%m%Q%F%#$r>e=q$-$9$kI,MW$,$"$j$^$9!#(B
+
+
+
+
+
+ Property
+ Description
+ Default value
+
+
+
+
+ org.apache.jetspeed.production.database.default.name
+
+
+
+ The type of database you are using. Used for
+ sql script generation with Torque.
+
+ Currently supported databases (with
+ corresponding Torque target database name):
+
+ hsql (hypersonic)
+ oracle (oracle)
+ mysql (mysql)
+ postgres (postresql)
+ mssql (mssql)
+
+
+ hsql
+
+
+
+
+ org.apache.jetspeed.production.database.url
+
+
+ The jdbc connection url
+ jdbc:hsqldb:hsql://127.0.0.1:9001
+
+
+
+
+ org.apache.jetspeed.production.database.user
+
+
+ The database user name to connect with.
+ sa
+
+
+
+
+ org.apache.jetspeed.production.database.password
+
+
+
+ The database user its password to connect
+ with.
+
+
+ empty
+
+
+
+
+
+ org.apache.jetspeed.production.database.driver
+
+
+ The jdbc driver class name
+ org.hsqldb.jdbcDriver
+
+
+
+
+ org.apache.jetspeed.production.jdbc.drivers.path
+
+
+
+ A Java classpath style path to the jdbc
+ driver classes or jar(s) needed for
+ connecting to the database.
+
+ Example:
+
+ /lib/ojdbc14.jar;/lib/nls_charset12.jar
+
+
+
+ empty
+
+
+
+
+
+
+
+ $B%W%m%Q%F%#(B
+ $B @ bL@(B
+ $B%G%U%)%k%HCM(B
+
+
+
+
+ org.apache.jetspeed.production.database.default.name
+
+
+
+ $B$"$J$?$,;HMQ$9$k%G!<%?%Y!<%9$N
+ $B8=;~E@$G%5%]!<%H$9$k%G!<%?%Y!<%9$O0J2<$NDL$j$G$9!#(B(Torque $B$N%?!<%2%C%H%G!<%?%Y!<%9L>$H0lCW$7$^$9!#(B)
+
+ hsql (hypersonic)
+ oracle (oracle)
+ mysql (mysql)
+ postgres (postresql)
+ mssql (mssql)
+
+
+ hsql
+
+
+
+
+ org.apache.jetspeed.production.database.url
+
+
+ JDBC $B$N@\B3(B url
+ jdbc:hsqldb:hsql://127.0.0.1:9001
+
+
+
+
+ org.apache.jetspeed.production.database.user
+
+
+ $B%G!<%?%Y!<%9$K@\B3$9$k:]$N%f!<%6L>!#(B
+ sa
+
+
+
+
+ org.apache.jetspeed.production.database.password
+
+
+
+ $B%G!<%?%Y!<%9$K@\B3$9$k%f!<%6$N%Q%9%o!<%I!#(B
+
+
+ $B6u(B
+
+
+
+
+
+ org.apache.jetspeed.production.database.driver
+
+
+ JDBC $B%I%i%$%P$N%/%i%9L>(B
+ org.hsqldb.jdbcDriver
+
+
+
+
+ org.apache.jetspeed.production.jdbc.drivers.path
+
+
+
+ $B%G!<%?%Y!<%9@\B3$KI,MW$J(B JDBC $B%I%i%$%P%/%i%9$d(B jar $B$X$N(B Java $B%/%i%9%Q%9%9%?%$%k$N%Q%9!#(B
+
+ $BNc(B:
+
+ /lib/ojdbc14.jar;/lib/nls_charset12.jar
+
+
+
+ $B6u(B
+
+
+
+
+
+
+
+
+
+ Make sure you have define at least the required
+ properties as described above in your
+ ${USER_HOME}/build.properties
+ . A minimal custom portal configuration using the
+ default HSQLDB database can be something like:
+
+
+
+
+ Note: If you're going to build the default
+ Jetspeed 2 portal directly from the source only
+ the
+ org.apache.jetspeed.portal.home
+ property is required from the set of required
+ portal configuration properties.
+
+
+
+
+ $B>/$J$/$H$bA0=R$NI,?\$N%W%m%Q%F%#$O(B
+ ${USER_HOME}/build.properties
+ $B$GDj5A$9$kI,MW$,$"$k$3$H$KCm0U$7$F$/$@$5$$!#(BHSQLDB $B$r;H$C$?:GDc8B$N%+%9%?%`%]!<%?%k$N @ _Dj$O0J2<$N$h$&$JIw$K$J$j$^$9!#(B
+
+
+
+
+ $BCm0U(B: $B$b$7%G%U%)%k%H$N(B Jetspeed 2 $B%]!<%?%k$r%=!<%9$+$iD>@\%S%k%I$9$k$D$b$j$J$N$G$"$l$P!"I,?\$N%]!<%?%k$N @ _Dj%W%m%Q%F%#$N$&$A!"(B
+ org.apache.jetspeed.portal.home
+ $B$@$1$,I,MW$K$J$j$^$9!#(B
+
+
+
+
+
+
+
+
+ Now we're going to configure, setup and build a new
+ custom portal application using the Jetspeed-2
+ maven-plugin.
+
+
+
+ $B$5$F!"$3$3$G$O(B Jetspeed 2 $B$N(B Maven $B%W%i%0%$%s$r;H$C$F!"?7$7$$%+%9%?%`%]!<%?%k%"%W%j%1!<%7%g%s$r @ _Dj$7!"%;%C%H%"%C%W$7!"%S%k%I$7$^$9!#(B
+
+
+
+
+
+ To be able to setup a Jetspeed 2 based portal the
+ maven remote repository lookup needs to be
+ configured properly in your
+ ${USER_HOME}/build.properties
+ :
+
+
+
+
+ Note: the order in which these repositories must
+ be specified is significant!
+
+
+
+
+ Jetspeed 2 $B%Y!<%9$N%]!<%?%k$N @ _Dj$,=PMh$k$?$a$K$O!"(BMaven $B$N%j%b!<%H%j%]%8%H%j$N>l=j$r(B
+ ${USER_HOME}/build.properties
+ $B$K0J2<$N$h$&$K @ _Dj$9$kI,MW$,$"$j$^$9!#(B
+
+
+
+
+ $BCm0U(B: $B$3$l$i$N%j%]%8%H%j$N=gHV$bF1$8$h$&$K;XDj$7$J$1$l$P$$$1$^$;$s!#(B
+
+
+
+
+
+
+
+ The first time, and when you want to upgrade to a
+ newer version of Jetspeed 2, you need to install the
+ maven-plugin as follows:
+
+
+
+
+ Note: you can set the version flag to the
+ specific version you want to install,
+ 2.0-M4-SNAPSHOT is just an example here.
+
+
+
+
+ $B:G=i$K!"$=$7$F$h$j?7$7$$%P!<%8%g%s$N(B Jetspeed 2 $B$K%"%C%W%0%l!<%I$7$?$/$J$C$?$H$-$O!"(BMaven $B%W%i%0%$%s$r0J2<$N$h$&$K$7$F%$%s%9%H!<%k$9$kI,MW$,$"$j$^$9!#(B
+
+
+
+
+ $BCm0U(B: $B%$%s%9%H!<%k$7$?$$%P!<%8%g%s$r;XDj$9$k$?$a$K%P!<%8%g%s%U%i%0$r @ _Dj$9$k$3$H$,=PMh$^$9!#$3$3$G$NNc$G$O(B 2.0-M4-SNAPSHOT $B$r;XDj$7$F$$$^$9!#(B
+
+
+
+
+
+
+
+ Once you have the maven-plugin installed and set
+ properties as needed, generate a default portal
+ configuration using the plugin as follows:
+
+
+
+
+ This maven goal actually executes several
+ subgoals which are further described in the
+
+ maven-plugin documentation
+
+ itself.
+
+
+
+
+ Maven $B%W%i%0%$%s$r%$%s%9%H!<%k$7!"I,MW$J%W%m%Q%F%#$r @ _Dj$7$?$i!"0J2<$N$h$&$K$7$F%W%i%0%$%s$r;H$C$F%G%U%)%k%H$N%]!<%?%k @ _Dj$r @ 8@.$7$F$/$@$5$$!#(B
+
+
+
+
+ $B$3$N(B Maven $B$N%4!<%k$O
+ maven-plugin documentation
+
+ $B$K5-=R$5$l$k$h$&$J$$$/$D$+$N%5%V%4!<%k$r
+
+
+
+
+
+ This section doesn't specify anything to do. After
+ the portal project is generated you can adapt and
+ customize it to your taste by overriding and merging
+ your own configurations and extensions.
+
+
+
+ $B$3$N%;%/%7%g%s$G$OFCJL2?$+$r9T$&$H$$$&;X<($O$"$j$^$;$s!#%]!<%?%k%W%m%8%'%/%H$, @ 8@.$5$l$?$i!"<+?H$N @ _Dj$d%(%/%9%F%s%7%g%s$r>e=q$-$7$?$j%^!<%8$7$?$j$7$F!"$"$J$?$,9%$_$K9g$o$;$F%+%9%?%^%$%:$r9T$C$F$/$@$5$$!#(B
+
+
+
+ You can regenerate or update (part of) your portal
+ project with the
+ j2:portal.genapp
+ goal as described in the previous section or use its
+ subgoals directly.
+
+
+
+ $BA0$N%;%/%7%g%s$G @ bL@$7$?$h$&$K(B
+ j2:portal.genapp
+ $B%4!<%k$r;H$&$+!"$3$N%4!<%kFb$G@\;H$&$J$j$7$F!"%]!<%?%k%W%m%8%'%/%H(B ($B$N0lIt(B) $B$r:F @ 8@.$7$?$j99?7$7$?$j$7$F$/$@$5$$!#(B
+
+
+
+
+
+ Once your portal configuration and setup is ready,
+ you can build and install the portal application in
+ your local maven repository (as needed for
+ deployment) using the following standard maven goal
+ from your custom portal project directory (in
+ ${org.apache.jetspeed.portal.home}):
+
+
+
+
+
+
+ $B%]!<%?%k$N @ _Dj$H%;%C%H%"%C%W$N=`Hw$,=PMh$?$i!"0J2<$N(BMaven $BI8=`$N%4!<%k$r%+%9%?%`%]!<%?%k%W%m%8%'%/%H$N%G%#%l%/%H%j(B (${org.apache.jetspeed.portal.home} $BFb(B) $B$G
+
+
+ You are now ready to deploy the new portal
+ application. For this, skip the following section on
+ building the Jetspeed 2 portal from source and
+ continue with the
+ deployment
+ section.
+
+
+
+ $B$5$"!"$3$l$G?7$7$$%]!<%?%k%"%W%j%1!<%7%g%s$NG[Hw$N=`Hw$,=PMh$^$7$?!#?7$7$$%]!<%?%k%"%W%j%1!<%7%g%s$NG[Hw$r$9$k$K$O!"B3$/(B Jetspeed 2 $B$N%=!<%9$+$i$N%S%k%I$N%;%/%7%g%s$rHt$P$7!"(B
+ deployment
+ $B$rB3$$$FFI$s$G$/$@$5$$!#(B
+
+
+
+
+
+
+ Build the Jetspeed 2 portal directly from the source is
+ somewhat easier to do but should only be done if you
+ don't want to create a new, customizable portal.
+
+
+
+ $B%=!<%9$+$iD>@\(B Jetspeed 2 $B%]!<%?%k$r%S%k%I$9$k$N$O!"4vJ,4JC1$G$9!#$7$+$7!"$3$l$O$"$J$?$,?7$7$$%+%9%?%^%$%:$5$l$?%]!<%?%k$r:n$j$?$/$J$$>l9g$N$_$=$&$9$Y$-$G$9!#(B
+
+
+
+
+ The Jetspeed 2 source contains a
+ project.properties
+ file which provides all of the required portal
+ configuration settings as described
+
+ above
+
+ .
+
+
+
+ Jetspeed 2 $B$N%=!<%9$K$O(B
+ project.properties
+ $B%U%!%$%k$,4^$^$l$F$$$^$9!#$3$l$O!"(B
+
+ $BI,?\$N%]!<%?%k @ _Dj%W%m%Q%F%#(B
+
+ $B$K=R$Y$?$h$&$J%]!<%?%k$N @ _Dj$KI,?\$NA4$F$N%W%m%Q%F%#$,Ds6!$5$l$F$$$^$9!#(B
+
+
+
+ You should
+
+ not
+
+ define any of those properties in your
+ ${USER_HOME}/build.properties
+ .
+
+ Instead, you
+ must
+ set a
+ org.apache.jetspeed.project.home
+ property, specifying the location where you expanded
+ the downloaded source or checked out the source from
+ subversion, like:
+
+
+
+
+ Note: you still need to specify the required
+ application server properties as described
+
+ above
+
+ .
+
+
+
+
+ ???$B*c(B???+ ${USER_HOME}/build.properties
+ $B%U%!%$%kCf$K$O$3$l$i$N%W%m%Q%F%#$r0l @ Z4^$s$G$O$$$1$^$;$s!#(B
+
+ $BBe$o$j$K!"(B
+ org.apache.jetspeed.project.home
+ $B%W%m%Q%F%#$r @ _Dj$7$J$1$l$P$$$1$^$;$s!#$3$N%W%m%Q%F%#$O!"0J2<$N$h$&$K!"%@%&%s%m!<%I$7$?%=!<%9$,E83+$5$l$?$+!"(Bsubversion $B$+$i%=!<%9$r%A%'%C%/%"%&%H$7$?>l=j$rI=$7$^$9!#(B
+
+
+
+
+ $BCm0U(B:
+
+ $BI,?\$N%"%W%j%1!<%7%g%s%5!<%P$N%W%m%Q%F%#(B
+
+ $B$G=R$Y$?%W%m%Q%F%#$K$D$$$F$O!";XDj$9$kI,MW$,$"$j$^$9!#(B
+
+
+
+
+ The Jetspeed 2 project.properties uses this property
+ to define the required
+ org.apache.portal.home
+ :
+
+
+
+ So, they are the same when you build the Jetspeed 2
+ portal from the source.
+
+
+
+ Jetspeed 2 $B$N(B project.properties $B%U%!%$%k$OI,?\$N(B
+ org.apache.portal.home
+ $B$rDj5A$9$k$?$a$K!"0J2<$N$h$&$J%W%m%Q%F%#$r;H$$$^$9!#(B
+
+
+
+ Jetspeed 2 $B%]!<%?%k$r%=!<%9$+$i%S%k%I$9$k>l9g$HF1$8$G$9!%(B
+
+
+
+ When you are going to deploy the portal as described
+ further below, you'll see references to the
+ org.apache.jetspeed.portal.home
+ which you can translate with the root folder of your
+ Jetspeed 2 source.
+
+
+
+ $B8e$K=R$Y$k$h$&$K%]!<%?%k$rG[Hw$7$?$$$H$-$O!"(B
+ org.apache.jetspeed.portal.home
+ $B$r;2>H$7$^$9!#$3$l$O$"$J$?$N(B Jetspeed 2 $B$N%=!<%9$N%k!<%H%U%)%k%@$HFI$_BX$($k$3$H$b$G$-$^$9!#(B
+
+
+
+ If you want to run the testcases when building the
+ Jetspeed 2 sources
+ and
+ don't want to use the default HSQLDB test database,
+ you need to override the default test database
+ properties, similar to the production database
+ properties as described
+
+ above
+
+ :
+
+
+
+ org.apache.jetspeed.test.database.default.name
+
+
+
+
+ org.apache.jetspeed.test.database.url
+
+
+
+
+ org.apache.jetspeed.test.database.user
+
+
+
+
+ org.apache.jetspeed.test.database.password
+
+
+
+
+ org.apache.jetspeed.test.database.driver
+
+
+
+
+ org.apache.jetspeed.test.database.drivers.path
+
+
+
+
+ Note: due to outstanding issue
+
+ JS2-320
+
+ you currently
+ must
+ use hard coded values for the test database
+ properties.
+
+
+
+
+ $B$b$7!"(BJetspeed 2 $B$N%=!<%9$r%S%k%I$7$F$$$F!"%G%U%)%k%H$N(B HSQL $B%F%9%H%G!<%?%Y!<%9$r;H$o$J$$;~$K%F%9%H%1!<%9$rAv$i$;$?$$>l9g$O!$(B
+
+ $B%*%W%7%g%J%k$N%G!<%?%Y!<%9%5!<%P$N%W%m%Q%F%#(B
+
+ $B$G=R$Y$?%W%m%@%/%7%g%s%G!<%?%Y!<%9$N%W%m%Q%F%#$HF1$8$h$&$K!"%G%U%)%k%H$N%F%9%H$N%G!<%?%Y!<%9%W%m%Q%F%#$r=$@5$9$kI,MW$,$"$j$^$9!#(B
+
+
+
+ org.apache.jetspeed.test.database.default.name
+
+
+
+
+ org.apache.jetspeed.test.database.url
+
+
+
+
+ org.apache.jetspeed.test.database.user
+
+
+
+
+ org.apache.jetspeed.test.database.password
+
+
+
+
+ org.apache.jetspeed.test.database.driver
+
+
+
+
+ org.apache.jetspeed.test.database.drivers.path
+
+
+
+
+ $BCm0U(B: $BL$2r7h$N(B
+
+ JS2-320
+
+ $B$NLdBj$N$?$a!"8=;~E@$G$O%F%9%H%G!<%?%Y!<%9$N%W%m%Q%F%#$O%O!<%I%3!<%I$5$l$?CM$r(B$B;H$o$J$1$l$P$$$1$^$;$s(B $B!#(B
+
+
+
+
+
+
+ Instead of downloading and installing the Jetspeed 2
+ maven-plugin, you are going to build and install it
+ directly from the source. You will need to repeat
+ this every time you update to a newer version of
+ Jetspeed 2 or change its project configuration, the
+ plugin itself or the resources used by the plugin.
+
+
+
+ Jetspeed 2 $B$N(B Maven $B%W%i%0%$%s$r%@%&%s%m!<%I$7!"%$%s%9%H!<%k$9$kBe$o$j$K!"%=!<%9$+$iD>@\%S%k%I$7$F @ 8@.$7$^$9!#$3$N:n6H$O(B Jetspeed 2 $B$N?7$7$$%P!<%8%g%s$K99?7$7$?$H$-$d%W%m%8%'%/%H$N @ _Dj$rJQ$($?$H$-!"%W%i%0%$%s<+?H$rJQ$($?$H$-!"%W%i%0%$%s$,;H$&%j%=!<%9$rJQ$($?$H$-$KKh2s
+
+
+ Build and install the maven-plugin as follows from
+ the root directory of the Jetspeed-2 source:
+
+
+
+
+
+
+ Jetspeed 2 $B%=!<%9$N%k!<%H%G%#%l%/%H%j$G0J2<$N$h$&$K$7$F(B Maven $B%W%i%0%$%s$N%S%k%I$H%$%s%9%H!<%k$r$7$^$9!#(B
+
+
+
+
+
+
+
+
+ If you are going to run the testcases and are using
+ the default HSQLDB database configuration, you will
+ need to start the test database before building
+ Jetspeed 2 in a
+ separate
+ console:
+
+
+
+
+
+
+ $B%F%9%H%1!<%9$rAv$i$;!"%G%U%)%k%H$N(B HSQLDB $B%G!<%?%Y!<%9$N @ _Dj$r;H$&$N$J$i!"(BJetspeed 2 $B$r%S%k%I$9$kA0$K%F%9%H%G!<%?%Y!<%9$r(B$BJL$N(B $B%3%s%=!<%k$G3+;O$7$F$*$/I,MW$,$"$j$^$9!#(B
+
+
+
+
+
+
+ After the build is finished you can stop the
+ database and close this console with a
+ Ctrl-C
+ .
+
+
+
+ $B%S%k%I$,=*$o$C$?8e$G!"(B
+ Ctrl-C
+ $B$r2!$7$F!"%G!<%?%Y!<%9$r$r;_$a!"%3%s%=!<%k$rJD$8$^$9!#(B
+
+
+
+
+
+ For a full build and installation of the portal and
+ the demo portlet applications in your local maven
+ repository run:
+
+
+
+
+
+
+ $B%m!<%+%k$N(B Maven $B%j%]%8%H%j$K%]!<%?%k$H%G%b%]!<%H%l%C%H$rA4$F%S%k%I$7%$%s%9%H!<%k$9$k$K$O!"(B
+
+
+
+ $B$r
+
+
+ But, if you also want to run the testcases during
+ the build run the following instead:
+
+
+
+
+
+
+ $B$7$+$7!"$b$7%S%k%I$N4V$K%F%9%H%1!<%9$r
+
+
+
+
+
+ You are now ready to deploy the Jetspeed 2 Portal.
+
+
+
+ $B$5$"!"$3$l$G(B Jetspeed 2 $B%]!<%?%k$rG[Hw$9$k=`Hw$,=PMh$^$7$?!#(B
+
+
+
+
+
+
+
+ If you are using the default HSQLDB database you
+ need to start it before deploying the portal.
+
+
+
+ $B$b$7%G%U%)%k%H$N(B HSQLDB $B%G!<%?%Y!<%9$r;H$&$N$G$"$l$P!"%]!<%?%k$rG[Hw$9$kA0$K%G!<%?%Y!<%9$r3+;O$9$kI,MW$,$"$j$^$9!#(B
+
+
+
+ To start the HSQLDB production database run the
+ following in a
+ separate
+ console:
+
+
+
+
+
+
+ HSQLDB $B%W%m%@%/%7%g%s%G!<%?%Y!<%9$r$BJL$N(B$B%3%s%=!<%k$G
+
+
+
+
+
+ You need to have this database running during the
+ deployment and while running the application server.
+ Afterwards you can stop the database and close this
+ console with a
+ Ctrl-C
+ .
+
+
+
+ $BG[Hw$N4V$H%"%W%j%1!<%7%g%s%5!<%P$,Ctrl-C
+ $B$r2!$7$F%G!<%?%Y!<%9$rDd;_$7!"%3%s%=!<%k$rJD$8$^$9!#(B
+
+
+
+ Note: this is required when using the
+ j2:quickStart
+ goal as described below. The Jetspeed 2 maven-plugin
+ provides other (sub)goals which you can use without
+ (re)creating a production database and/or inserting
+ default portal configuration data. See the
+
+ Plugin documentation
+
+ for further information about the available goals.
+
+
+
+ $BCm0U(B: $B$3$l$O8e$G=R$Y$k(B
+ j2:quickStart
+ $B%4!<%k$r;H$&;~$KI,MW$G$9!#(BJetspeed 2 $B$N(B Maven $B%W%i%0%$%s$K$O%W%m%@%/%7%g%s%G!<%?%Y!<%9$N(B ($B:F(B) $B:n @ .$J$7$K!"$=$7$F(B/$B$^$?$O%G%U%)%k%H$N%]!<%?%k @ _Dj%G!<%?$rA^F~$9$k;v$J$/;H$($k!"B>$N(B ($B%5%V(B) $B%4!<%k$,$"$j$^$9!#MxMQ2DG=$J%4!<%k$N$5$i$J$k>pJs$O(B
+
+ Plugin documentation
+
+ $B$r8+$F$/$@$5$$!#(B
+
+
+
+
+
+ We currently only cover deploying to Tomcat 5 or
+ Tomcat 5.5.
+
+
+
+ $B8=;~E@$G$O(B Tomcat 5 $B$+(B 5.5 $B$X$NG[Hw$N$_%+%P!<$7$F$$$^$9!#(B
+
+
+
+ Information about deployment to other application
+ servers can be found at the The Jetspeed 2
+
+ Wiki
+
+ .
+
+
+
+ $BB>$N%"%W%j%1!<%7%g%s%5!<%P$X$NG[Hw$K$D$$$F$N>pJs$O(B Jetspeed 2
+
+ Wiki
+
+ $B$G8+IU$+$k$G$7$g$&!#(B
+
+
+
+ To deploy a default Jetspeed 2 portal, including the
+ demo portlet applications, run the following in a
+ separate
+ console:
+
+
+
+
+ Note: the
+
+ maven-plugin documentation
+
+ described other goals you can use to customize
+ the deployment to your taste.
+
+
+
+
+ $B$G$b%]!<%H%l%C%H%"%W%j%1!<%7%g%s$r4^$`!"%G%U%)%k%H$N(B Jetspeed 2 $B%]!<%?%k$rG[Hw$9$k$?$a$K!"0J2<$N$h$&$J%3%^%s%I$r(B$BJL$N(B $B%3%s%=!<%k$G
+
+
+
+ $BCm0U(B:
+
+ maven-plugin documentation
+
+ $B$K$"$J$?9%$_$NG[Hw$K%+%9%?%^%$%:$9$k$N$K;H$($kB>$N%4!<%k$K4X$9$k5-=R$,$"$j$^$9!#(B
+
+
+
+
+
+
+ The final step is starting up your Tomcat server and
+ the portal will automatically install any deployed
+ portlet applications.
+
+
+
+ $B:G=i$N%9%F%C%W$O(B Tomcat $B%5!<%P$r5/F0$9$k$3$H$G$9!#$9$k$H!"%]!<%?%k$O<+F0E*$KG[Hw$9$Y$-%]!<%H%l%C%H%"%W%j%1!<%7%g%s$r<+F0E*$K%$%s%9%H!<%k$9$k$G$7$g$&!#(B
+
+
+
+ Then you can access the portal with your browser at:
+ http://localhost:8080/jetspeed
+ or replace "jetspeed" in the above url with the name
+ of you own portal application (
+
+ ${org.apache.jetspeed.portal.artifactId}
+
+ ).
+
+
+
+ $B$=$N8e$G!"%V%i%&%6$G%]!<%?%k$K0J2<$+(B
+ http://localhost:8080/jetspeed
+ $B$b$7$/$O!"$3$N(B URL $B$N(B "jetspeed" $B$r$"$J$?$N%]!<%?%k%"%W%j%1!<%7%g%s$NL>A0(B (
+
+ ${org.apache.jetspeed.portal.artifactId}
+
+ ) $B$KCV$-49$($k;v$G!"%]!<%?%k$K%"%/%;%9=PMh$^$9!#(B
+
+
+
+
+
+ With the default Jetspeed 2 portal deployment,
+ several example user accounts are inserted into the
+ portal database with which you can logon to the
+ portal:
+
+
+ username
+ password
+ roles
+
+
+
+ admin
+
+
+ admin
+
+
+ admin, manager, user
+
+
+
+
+ manager
+
+
+ manager
+
+
+ manager, user
+
+
+
+
+ jetspeed
+
+
+ jetspeed
+
+
+ manager
+
+
+
+
+ user
+
+
+ user
+
+
+ user
+
+
+
+
+ tomcat
+
+
+ tomcat
+
+
+
+
+
+
+
+ $B%G%U%)%k%H$N(B Jetspeed 2 $B$N%]!<%?%k$NG[Hw$G$O!"$$$/$D$+$N%5%s%W%k%f!<%6$N%"%+%&%s%H$,%]!<%?%k%G!<%?%Y!<%9$KEPO?$5$l$F$$$^$9!#$=$l$r;H$C$F!"%]!<%?%k$X$N%m%0%*%s$,2DG=$G$9!#(B
+
+
+ username
+ password
+ roles
+
+
+
+ admin
+
+
+ admin
+
+
+ admin, manager, user
+
+
+
+
+ manager
+
+
+ manager
+
+
+ manager, user
+
+
+
+
+ jetspeed
+
+
+ jetspeed
+
+
+ manager
+
+
+
+
+ user
+
+
+ user
+
+
+ user
+
+
+
+
+ tomcat
+
+
+ tomcat
+
+
+
+
+
+
+
+
+
+
+
From m.matsuda @ appliedjapan.com Wed Dec 28 20:23:25 2005
From: m.matsuda @ appliedjapan.com (Applied_MATSUDA Masaaki)
Date: Wed, 28 Dec 2005 20:23:25 +0900
Subject: [Jetspeed-japan-trans] Re: getting-started-source.xml
In-Reply-To: <87irt9is0m.wl%karma@jazz.email.ne.jp>
References: <87irt9is0m.wl%karma@jazz.email.ne.jp>
Message-ID: <20051228202325.39026758@appliedjapan.com>
TigerCatです。こんにちわ。
To) 加藤さん
>とりあえず getting-started-source.xml の翻訳が完成しましたので,お送り
>致します.
早速コミットしておきました。
サイトも置き換えしてみました。
ちなみにいただいたファイルの改行コードを念のためLFに
変更してからコミットしてあります。
念のため再チェックアウトしていただけると安心かと。
どうもありがとうございます!!
p.s.
CVSコミットメールの表題において,"committed..."の前に
スペースが入っていないっぽい件,
タブとか改行とかしない処理を入れたのに効果がないみたい
ですね。
これはもうSourceForgeのsendmailが勝手に折り返してるん
ではないかなと推測するがいかに。
From shinsuke @ users.sourceforge.jp Thu Dec 29 06:35:23 2005
From: shinsuke @ users.sourceforge.jp (shinsuke @ users.sourceforge.jp)
Date: Thu, 29 Dec 2005 06:35:23 +0900
Subject: [Jetspeed-japan-trans] CVS-Update: jetspeed-2-trans/xdocs committed
by shinsuke
Message-ID: <20051228213523.28A4B2AC04D@users.sourceforge.jp>
Update of /cvsroot/jetspeed-japan/jetspeed-2-trans/xdocs
In directory sf-cvs:/tmp/cvs-serv3676/xdocs
Modified Files:
assignment.xml
Log Message:
updated assignment table
jetspeed-2-trans/xdocs/assignment.xml 1.6 -> 1.7 (modified)
http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/jetspeed-japan/jetspeed-2-trans/xdocs/assignment.xml.diff?r1=1.6&r2=1.7
===================================================================
RCS file: jetspeed-2-trans/xdocs/assignment.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- assignment.xml 2005/12/22 22:11:11 1.6
+++ assignment.xml 2005/12/28 21:35:23 1.7
@@ -111,8 +111,8 @@
guides/guide-app-servers.xml
???
$BLuJ8(B
-
-
-
$BJg=8Cf(B
+
$B2CF#BYJ8(B
+
$BK]LuCf(B
guides/guide-components.xml
From shinsuke @ yahoo.co.jp Thu Dec 29 06:42:05 2005
From: shinsuke @ yahoo.co.jp (Shinsuke SUGAYA)
Date: Thu, 29 Dec 2005 06:42:05 +0900
Subject: [Jetspeed-japan-trans] Re: guide-app-servers.xml
In-Reply-To: <87hd8tirwb.wl%karma@jazz.email.ne.jp>
References: <87hd8tirwb.wl%karma@jazz.email.ne.jp>
Message-ID: <43B306AD.9040806@yahoo.co.jp>
KATOH Yasufumi wrote:
> 加藤泰文です.
>
> 次は guide-app-servers.xml を翻訳します.
>
ありがとうございます。
更新しました。
shinsuke
--------------------------------------
Yahoo! Mail - supported by 10million people
http://pr.mail.yahoo.co.jp/mail_pr/
From shinsuke @ yahoo.co.jp Thu Dec 29 06:47:26 2005
From: shinsuke @ yahoo.co.jp (Shinsuke SUGAYA)
Date: Thu, 29 Dec 2005 06:47:26 +0900
Subject: [Jetspeed-japan-trans] navigation.xml
Message-ID: <43B307EE.3060206@yahoo.co.jp>
こんにちは、菅谷です。
navigation.xml を担当しようと思いますが、これを手順に従って
処理すると、[english]日本語 という感じで、メニューが長くなって
読みにくくなると思うので、例外的に原文を置くのをやめておこうと
思います。何か問題やコメントがあれば、お知らせください。
navigation.xml は前ページに出て、他にも影響があるかと思うので、
こうした方が良いというのがあれば、お知らせください。
shinsuke
--------------------------------------
Yahoo! Mail - supported by 10million people
http://pr.mail.yahoo.co.jp/mail_pr/
From shinsuke @ users.sourceforge.jp Thu Dec 29 06:45:18 2005
From: shinsuke @ users.sourceforge.jp (shinsuke @ users.sourceforge.jp)
Date: Thu, 29 Dec 2005 06:45:18 +0900
Subject: [Jetspeed-japan-trans] CVS-Update: jetspeed-2-trans/xdocs committed
by shinsuke
Message-ID: <20051228214518.243DA2AC00F@users.sourceforge.jp>
Update of /cvsroot/jetspeed-japan/jetspeed-2-trans/xdocs
In directory sf-cvs:/tmp/cvs-serv8255/xdocs
Modified Files:
assignment.xml
Log Message:
updated assignment table
jetspeed-2-trans/xdocs/assignment.xml 1.7 -> 1.8 (modified)
http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/jetspeed-japan/jetspeed-2-trans/xdocs/assignment.xml.diff?r1=1.7&r2=1.8
===================================================================
RCS file: jetspeed-2-trans/xdocs/assignment.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- assignment.xml 2005/12/28 21:35:23 1.7
+++ assignment.xml 2005/12/28 21:45:18 1.8
@@ -307,8 +307,8 @@
navigation.xml
???
$BLuJ8(B
- -
- $BJg=8Cf(B
+ $B?{C+?.2p(B
+ $BK]LuCf(B
portlets-community.xml
From shinsuke @ users.sourceforge.jp Thu Dec 29 06:58:02 2005
From: shinsuke @ users.sourceforge.jp (shinsuke @ users.sourceforge.jp)
Date: Thu, 29 Dec 2005 06:58:02 +0900
Subject: [Jetspeed-japan-trans] CVS-Update: jetspeed-2-trans/ja/xdocs
committed by shinsuke
Message-ID: <20051228215802.272F02AC04D@users.sourceforge.jp>
Update of /cvsroot/jetspeed-japan/jetspeed-2-trans/ja/xdocs
In directory sf-cvs:/tmp/cvs-serv14671/ja/xdocs
Modified Files:
navigation.xml
Log Message:
translated
jetspeed-2-trans/ja/xdocs/navigation.xml 1.2 -> 1.3 (modified)
http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/jetspeed-japan/jetspeed-2-trans/ja/xdocs/navigation.xml.diff?r1=1.2&r2=1.3
===================================================================
RCS file: jetspeed-2-trans/ja/xdocs/navigation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- navigation.xml 2005/12/18 04:18:46 1.2
+++ navigation.xml 2005/12/28 21:58:02 1.3
@@ -20,42 +20,42 @@
-
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-
-
+
+
+
-
-
+
+
-
+
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
-
-
+
+
+
-
+