[jboss-cvs] JBossAS SVN: r96474 - projects/docs/enterprise/5.0/Release_Notes_GA/ja-JP.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Nov 17 20:43:26 EST 2009
Author: jito at redhat.com
Date: 2009-11-17 20:43:21 -0500 (Tue, 17 Nov 2009)
New Revision: 96474
Modified:
projects/docs/enterprise/5.0/Release_Notes_GA/ja-JP/Release_Notes.po
Log:
translation in progress
Modified: projects/docs/enterprise/5.0/Release_Notes_GA/ja-JP/Release_Notes.po
===================================================================
--- projects/docs/enterprise/5.0/Release_Notes_GA/ja-JP/Release_Notes.po 2009-11-18 01:25:15 UTC (rev 96473)
+++ projects/docs/enterprise/5.0/Release_Notes_GA/ja-JP/Release_Notes.po 2009-11-18 01:43:21 UTC (rev 96474)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: Release_Notes\n"
"POT-Creation-Date: 2009-11-16T06:49:43\n"
-"PO-Revision-Date: 2009-11-17 15:56+1000\n"
+"PO-Revision-Date: 2009-11-18 11:37+1000\n"
"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
"Language-Team: Japanese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -680,12 +680,12 @@
#. Tag: para
#, no-c-format
msgid "<filename>Administration and Configuration Guide</filename> explains all administrative and server configuration functions in detail."
-msgstr "<filename>Administration and Configuration Guide</filename> ã¯ãã¹ã¦ã®ç®¡çããã³ãµã¼ãã¼è¨å®æ©è½ã詳細ã«èª¬æãã¾ãã"
+msgstr "<filename>Administration and Configuration Guide</filename> ã¯ãã¹ã¦ã®ç®¡çããã³ãµã¼ãã¼è¨å®é¢æ°ã詳細ã«èª¬æãã¾ãã"
#. Tag: para
#, no-c-format
msgid "The online documentation will be updated as necessary so be sure to check back, especially when a new version of the JBoss Enterprise Application Platform is released."
-msgstr ""
+msgstr "ãªã³ã©ã¤ã³ããã¥ã¡ã³ãã¯å¿
è¦ã«å¿ãã¦æ´æ°ããããããæ°ãããã¼ã¸ã§ã³ã® JBoss Enterprise Application Platform ããªãªã¼ã¹ãããæã¯å¿
ããã§ãã¯ããããã«ãã¦ãã ããã"
#. Tag: title
#, no-c-format
@@ -695,22 +695,22 @@
#. Tag: para
#, no-c-format
msgid "Following is a list of issues fixed in this release:"
-msgstr ""
+msgstr "æ¬ãªãªã¼ã¹ã§ä¿®æ£ãããåé¡ã®ä¸è¦§ã¯æ¬¡ã®éãã§ãã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2866\">JBPAPP-2866</ulink>: The JGroups protocol stack included an incorrect diagnostic address, <literal>224.0.0.75</literal>. The address has been corrected to <literal>224.0.75.75</literal>."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2866\">JBPAPP-2866</ulink>: JGroups ãããã³ã«ã¹ã¿ãã¯ã«ä¸é©åãªè¨ºæã¢ãã¬ã¹ <literal>224.0.0.75</literal> ãå«ã¾ãã¦ãã¾ããã ãã®ã¢ãã¬ã¹ã¯ <literal>224.0.75.75</literal> ã«ä¿®æ£ããã¾ããã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2306\">JBPAPP-2306</ulink>: The HP-UX init script in the First Customer Ship, <filename>jboss_init_hpux.sh</filename>, did not let users define a bind address with the <code>-b</code> option. Support for this option has since been added to the script."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2306\">JBPAPP-2306</ulink>: First Customer Ship ã® HP-UX åæã¹ã¯ãªãã <filename>jboss_init_hpux.sh</filename> ã«ããã ãã¤ã³ãã¢ãã¬ã¹ã« <code>-b</code> ãªãã·ã§ã³ãå®ç¾©ãããã¨ãã§ãã¾ããã§ããã ãã®ãªãã·ã§ã³ã«å¯¾ãããµãã¼ããã¹ã¯ãªããã«è¿½å ããã¾ããã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2924\">JBPAPP-2924</ulink>: Between the First Customer Ship and General Availability releases of JBoss Enterprise Application Platform 5.0, the included version of JBoss Messaging was upgraded from 1.4.3 to 1.4.6 to provide better support for JBoss Enterprise Application Platform 5.0. For further information about the differences between JBoss Messaging 1.4.3 and JBoss Messaging 1.4.6, check the JBoss Messaging Release Notes."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2924\">JBPAPP-2924</ulink>: JBoss Enterprise Application Platform 5.0 ã® First Customer Ship ãªãªã¼ã¹ã¨ General Availability ãªãªã¼ã¹ã®éã«ã å梱㮠JBoss Messaging ã 1.4.3 ãã 1.4.6 ã¸æ´æ°ããã JBoss Enterprise Application Platform 5.0 ã«å¯¾ãããµãã¼ããåä¸ããã¾ããã JBoss Messaging 1.4.3 㨠JBoss Messaging 1.4.6 ã®éãã«é¢ãã詳細ã¯ã JBoss Messaging ã®ãªãªã¼ã¹ãã¼ããåç
§ãã¦ãã ããã"
#. Tag: title
#, no-c-format
@@ -720,12 +720,12 @@
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2154\">JBPAPP-2154</ulink>: Some unsupported components such as IceFaces, Seam-jul and Wicket integration were included in the First Customer Ship. These unsupported components and the examples related to them have been removed."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2154\">JBPAPP-2154</ulink>: IceFacesã Seam-julã Wicket çµ±åãªã©ãµãã¼ãããã¦ããªãã³ã³ãã¼ãã³ãã®ä¸é¨ã First Customer Ship ã«å梱ããã¦ãã¾ããã ãµãã¼ãããã¦ããªãã³ã³ãã¼ãã³ããé¢é£ãããµã³ãã«ãåé¤ããã¾ããã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2155\">JBPAPP-2155</ulink>: The Seam documentation included in the First Customer Ship contained unverified and unsupported information about non-JBoss containers. Unsupported information has been removed from the documentation, and the examples to do with unsupported containers have been removed."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2155\">JBPAPP-2155</ulink>: First Customer Ship ã«å«ã¾ãã¦ãã Seam ããã¥ã¡ã³ãã«ã JBoss ã§ãªãã³ã³ããã«é¢ããæªè¨¼æã®æ
å ±ããµãã¼ãããã¦ããªãæ
å ±ãå«ã¾ãã¦ãã¾ããã ãµãã¼ãããã¦ããªãæ
å ±ã¯ããã¥ã¡ã³ãããåé¤ããã ãµãã¼ã対象ã§ãªãã³ã³ããã®ãµã³ãã«ãåé¤ããã¾ããã"
#. Tag: title
#, no-c-format
@@ -735,17 +735,17 @@
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2900\">JBPAPP-2900</ulink>: MySQL uses the <literal>TEMPORARY</literal> keyword to bypass implicit transaction commits. Previously, Hibernate used <code><CREATE TEMPORARY TABLE></code> with <code><DROP TABLE></code>. Omitting the <literal>TEMPORARY</literal> keyword caused an implicit commit, and immediate failure within an XA Transaction. <code><DROP TEMPORARY TABLE></code> is now supported and this issue no longer presents."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2900\">JBPAPP-2900</ulink>: MySQL 㯠<literal>TEMPORARY</literal> ãã¼ã¯ã¼ãã使ç¨ãã¦æé»ã®ãã©ã³ã¶ã¯ã·ã§ã³ã³ããããè¿åãã¾ãã 以åãHibernate 㯠<code><CREATE TEMPORARY TABLE></code> ã <code><DROP TABLE></code> ã¨å
±ã«ä½¿ç¨ãã¦ãã¾ããã <literal>TEMPORARY</literal> ãã¼ã¯ã¼ããçç¥ããã¨ã æé»ã³ããããçºçãã XA ãã©ã³ã¶ã¯ã·ã§ã³å
ã§å³åº§ã«é害ãçºçãã¾ããã <code><DROP TEMPORARY TABLE></code> ããµãã¼ããããããã«ãªã£ãããã ãã®åé¡ã¯è§£æ¶ããã¾ããã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2948\">JBPAPP-2948</ulink>: The <filename>deploy/jmx-remoting.sar</filename> service instantiates a JSR-160 adapter for standardized remote access to the JBoss MBeanServer. This service is used with tools such as the JConsole. At present, this service does not support secure access. In production environments where the server binds to a specific address other than <literal>localhost</literal> this presents a potential security risk, so the adapter has been moved from the <filename>deploy</filename> directory into <filename>docs/examples/jmx</filename>. We do not recommend enabling it for production usage. If during development you wish to re-enable the adapter, copy it back to the <filename>deploy</filename> directory."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2948\">JBPAPP-2948</ulink>: <filename>deploy/jmx-remoting.sar</filename> ãµã¼ãã¹ã¯ã JBoss MBeanServer ã¸ã®æ¨æºãªã¢ã¼ãã¢ã¯ã»ã¹ãè¡ãããã« JSR-160 ã¢ããã¿ã®ã¤ã³ã¹ã¿ã³ã¹ãä½æãã¾ãã ãã®ãµã¼ãã¹ã¯ã JConsole ã®ãããªãã¼ã«ã¨å
±ã«ä½¿ç¨ããã¾ãã ç¾å¨ã ãã®ãµã¼ãã¹ã¯å®å
¨ãªã¢ã¯ã»ã¹ããµãã¼ããã¦ãã¾ããã ãµã¼ãã¼ã <literal>localhost</literal> 以å¤ã®ã¢ãã¬ã¹ã«ãã¤ã³ãããå®ç¨¼åç°å¢ã§ã¯ã æ½å¨çãªãªã¹ã¯ãä¼´ãããã ã¢ããã¿ã <filename>deploy</filename> ãã£ã¬ã¯ããªãã <filename>docs/examples/jmx</filename> ã¸ç§»åããã¾ããã å®ç¨¼ååãã«ãã®ã¢ããã¿ãæå¹ã«ãããã¨ã¯æ¨å¥¨ããã¾ããã éçºä¸ã«ã¢ããã¿ãå度æå¹ã«ããã«ã¯ã ã¢ããã¿ã <filename>deploy</filename> ãã£ã¬ã¯ããªã«ã³ãã¼ãã¦ãã ã!
ãã"
#. Tag: para
#, no-c-format
msgid "The adapter has been moved to <filename>/docs/examples</filename>. If you wish to re-enable it, move it back to the <filename>deploy</filename> directory."
-msgstr ""
+msgstr "ã¢ããã¿ã <filename>/docs/examples</filename> ã«ç§»åããã¾ããã å度æå¹ã«ããã«ã¯ãã¢ããã¿ã <filename>deploy</filename> ãã£ã¬ã¯ããªã«æ»ãã¦ãã ããã"
#. Tag: title
#, no-c-format
@@ -755,7 +755,7 @@
#. Tag: para
#, no-c-format
msgid "Following is a list of known issues at the time of release."
-msgstr ""
+msgstr "ãªãªã¼ã¹æç¹ã®æ¢ç¥ã®åé¡ã¯æ¬¡ã®éãã§ãã"
#. Tag: title
#, no-c-format
@@ -765,52 +765,52 @@
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2571\">JBPAPP-2571</ulink>: Running the Microsoft SQL server with Microsoft JDBC drivers 2.0 causes unstable builds in JBoss Messaging. This issue is created by the <literal>Adaptive Buffering</literal> being the default behavior for the driver as this only allows for large values ot be read once by using the <methodname>get<Type>Stream</methodname> method. The current workaround for this issue is to change the <parameter>responseBuffering</parameter> parameter of the JDBC connection URL from being <literal>adaptive</literal>, to being <literal>full</literal> (as it was for version 1.2 of the JDBC driver)."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2571\">JBPAPP-2571</ulink>: Microsoft SQL ãµã¼ãã¼ã Microsoft JDBC ãã©ã¤ã 2.0 ã§å®è¡ããã¨ã Jboss Messaging ã«ããããã«ããä¸å®å®ã«ãªãã¾ãã ãã®åé¡ã¯ã <literal>Adaptive Buffering</literal> ããã©ã¤ãã®ããã©ã«ãåä½ã§ããããã <methodname>get<Type>Stream</methodname> ã¡ã½ããã使ç¨ãã¦å¤§ããªå¤ãä¸åº¦ã«èªã¿åããã¨ãåå ã¨ãªã£ã¦ãã¾ãã ç¾å¨ã®åé¿çã¨ãã¦ã¯ã JDBC æ¥ç¶ URL ã® <parameter>responseBuffering</parameter> ãã©ã¡ã¼ã¿ã <literal>adaptive</literal> ãã <literal>full</literal> ã«å¤æ´ãã¾ã (ãã¼ã¸ã§ã³ 1.2 ã® JDBC ãã©ã¤ãã¨åæ§ã«ãã¾ã)ã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBAS-7049\">JBAS-7049</ulink>: The server manager does not function correctly when Open JDK 6 is used because a <exceptionname>NullPointerException</exceptionname> check is missing in Open JDK 6. The workaround is to comment out the <property>java.security.debug</property> statement in the <filename>imports/server-config.xml</filename> file."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBAS-7049\">JBAS-7049</ulink>: Open JDK 6 ã« <exceptionname>NullPointerException</exceptionname> ãã§ãã¯ããªãã£ããããOpen JDK 6 ã使ç¨ãããã¨ãµã¼ãã¼ããã¼ã¸ã£ãæ£å¸¸ã«åä½ãã¾ããã§ããã <filename>imports/server-config.xml</filename> ãã¡ã¤ã«ã® <property>java.security.debug</property> ã¹ãã¼ãã¡ã³ããã³ã¡ã³ãã¢ã¦ãããã¨ãã®åé¡ãåé¿ã§ãã¾ãã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2598\">JBPAPP-2598</ulink>: Once the workaround for the <ulink url=\"https://jira.jboss.org/jira/browse/JBAS-7049\">JBAS-7049</ulink> issue is applied a new issue presents itself. A server running the surity manager using Open JDK 6 still fails to start, now with an access denied error. There is no currently known workaround for this issue."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2598\">JBPAPP-2598</ulink>: <ulink url=\"https://jira.jboss.org/jira/browse/JBAS-7049\">JBAS-7049</ulink> ã®åé¡ã®åé¿çãé©å¿ããã¨ã æ°ããåé¡ãçºçãã¾ãã Open JDK 6 ã使ç¨ããã»ãã¥ãªãã£ããã¼ã¸ã£ãå®è¡ãã¦ãããµã¼ãã¼ãä¾ç¶èµ·åããã ã¢ã¯ã»ã¹æå¦ã¨ã©ã¼ãçºçãã¾ãã ç¾å¨ã ãã®åé¡ã«å¯¾ããæ¢ç¥ã®åé¿çã¯ããã¾ããã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2590\">JBPAPP-2590</ulink>: An issue exists in the <filename>policy.provider</filename> defined in <filename>${JAVA_HOME}/jre/lib/security/java.security</filename> when IBM JDK 6 is used. By default <filename>org.apache.harmony.security.fortress.DefaultPolicy</filename> is used and this should be <filename>policy.provider=sun.security.provider.PolicyFile</filename>. The workaround for this issue is to manually make this adjustment."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2590\">JBPAPP-2590</ulink>: IBM JDK 6 ã使ç¨ããå ´åã <filename>${JAVA_HOME}/jre/lib/security/java.security</filename> ã«å®ç¾©ããã¦ãã <filename>policy.provider</filename> ã«åé¡ãçºçãã¾ãã ããã©ã«ãã§ã¯ <filename>org.apache.harmony.security.fortress.DefaultPolicy</filename> ã使ç¨ããã¾ããã <filename>policy.provider=sun.security.provider.PolicyFile</filename> ã使ç¨ãããªããã°ãªãã¾ããã æä½æ¥ã§èª¿æ´ãããã¨ããã®åé¡ã®åé¿çã«ãªãã¾ãã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2576\">JBPAPP-2576</ulink>: The MySQL JDBC driver does not currently implement XA Recovery correctly."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2576\">JBPAPP-2576</ulink>: ç¾å¨ã MySQL JDBC ãã©ã¤ã㯠XA ãªã«ããªãæ£ããå®è£
ãã¾ããã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2871\">JBPAPP-2871</ulink>: High CPU utilization and reduced performance and transaction throughput has been observed when MySQL 5.0.41 when optimized settings are in use, as described in <ulink url=\"https://jira.jboss.org/jira/browse/JBQA-2610\">JBQA-2610</ulink>. We recommend upgrading to MySQL 5.0.86 and applying optimized settings as described in <ulink url=\"https://jira.jboss.org/jira/browse/JBQA-2610\">JBQA-2610</ulink> to reduce CPU utilization and increase performance."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2871\">JBPAPP-2871</ulink>: <ulink url=\"https://jira.jboss.org/jira/browse/JBQA-2610\">JBQA-2610</ulink> ã®éãã MySQL 5.0.41 ã®æé©åè¨å®ã使ç¨ãããã¨ã CPU ã®ä½¿ç¨çãä¸æã ãããã©ã¼ãã³ã¹ããã©ã³ã¶ã¯ã·ã§ã³ã¹ã«ã¼ããããä½ä¸ãã¾ããã CPU ã®ä½¿ç¨çãä½æ¸ãã ããã©ã¼ãã³ã¹ãåä¸ãããããã MySQL 5.0.86 ã¸ã¢ããã°ã¬ã¼ããã <ulink url=\"https://jira.jboss.org/jira/browse/JBQA-2610\">JBQA-2610</ulink> ã®éãã«æé©åè¨å®ãé©å¿ãããã¨ãæ¨å¥¨ããã¾ãã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2162\">JBPAPP-2162</ulink>: Sun JAXB silently accepts messages with non-fatal errors where they should be rejected. The fix for <ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2114\">JBPAPP-2114</ulink> corrects this, so that badly-formed messages are rejected."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2162\">JBPAPP-2162</ulink>: Sun JAXB ã¯æå¦ãã¹ãã§ããè´å½çã§ãªãã¨ã©ã¼ã®ã¡ãã»ã¼ã¸ã許å¯ãã¾ãã <ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2114\">JBPAPP-2114</ulink> ã®ä¿®æ£ããã®åé¡ãä¿®æ£ããããã æªãã¡ãã»ã¼ã¸ã¯æå¦ããã¾ãã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2765\">JBPAPP-2765</ulink>: <literal>LoadMgr3</literal> logs a failure to load a class as an error even when the failure to load is expected and intentional. (Seam, for example, catches exceptions in order to disable unnecessary components if a particular class is not found.)"
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2765\">JBPAPP-2765</ulink>: ãã¼ãã®å¤±æãäºæããã¦ãããæå³çã§ãã£ã¦ãã <literal>LoadMgr3</literal> ã¯ã¯ã©ã¹ã®ãã¼ãã«å¤±æããéã«ã¨ã©ã¼ã¨ãã¦ãã°ãã¾ã (ä¾ãã°ãSeam ã®å ´åã ç¹å®ã®ã¯ã©ã¹ãè¦ã¤ãããªãã¨ä¸å¿
è¦ãªã³ã³ãã¼ãã³ããåããã«ããããä¾å¤ããã£ãããã¾ã)ã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2894\">JBPAPP-2894</ulink>: Setting the <literal>hibernate.bytecode.provider</literal> system property in <filename>jpa-deployers-jboss-beans.xml</filename> is unreliable. The workaround for this issue is to add <code>-Dhibernate.bytecode.provider=cglib</code> to <literal>$JAVA_OPTS</literal> in <filename>jboss-as/bin/run.conf</filename>."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2894\">JBPAPP-2894</ulink>: <filename>jpa-deployers-jboss-beans.xml</filename> å
ã® <literal>hibernate.bytecode.provider</literal> ã·ã¹ãã ããããã£ã¯ä¿¡é ¼ã§ãã¾ããã ãã®åé¡ãåé¿ããã«ã¯ã <code>-Dhibernate.bytecode.provider=cglib</code> ã <filename>jboss-as/bin/run.conf</filename> ã® <literal>$JAVA_OPTS</literal> ã«è¿½å ãã¾ãã"
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2818\">JBPAPP-2818</ulink>: The current <filename>main/src/bin/run.sh</filename> does not allow users to override <filename>$JBOSS_HOME/bin/run.conf</filename> with a profile-specific <filename>$JBOSS_HOME/server/$PROFILE/run.conf</filename>."
-msgstr ""
+msgstr "<ulink url=\"https://jira.jboss.org/jira/browse/JBPAPP-2818\">JBPAPP-2818</ulink>: ç¾å¨ <filename>main/src/bin/run.sh</filename> ã¯ã <filename>$JBOSS_HOME/bin/run.conf</filename> ããããã¡ã¤ã«åºæã® <filename>$JBOSS_HOME/server/$PROFILE/run.conf</filename> ã§ä¸æ¸ããããã¨ã許å¯ãã¾ããã"
#. Tag: para
#, no-c-format
More information about the jboss-cvs-commits
mailing list