From jbosstools-commits at lists.jboss.org Thu Feb 28 04:47:19 2008 Content-Type: multipart/mixed; boundary="===============8339197607899476234==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r6630 - trunk/as/docs/reference/en/modules. Date: Thu, 28 Feb 2008 04:43:18 -0500 Message-ID: --===============8339197607899476234== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ochikvina Date: 2008-02-28 04:43:18 -0500 (Thu, 28 Feb 2008) New Revision: 6630 Modified: trunk/as/docs/reference/en/modules/modules.xml Log: http://jira.jboss.com/jira/browse/JBDS-199 - adding the screenshot & some i= nfo about single file deployment = Modified: trunk/as/docs/reference/en/modules/modules.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/as/docs/reference/en/modules/modules.xml 2008-02-28 09:41:58 UTC = (rev 6629) +++ trunk/as/docs/reference/en/modules/modules.xml 2008-02-28 09:43:18 UTC = (rev 6630) @@ -35,7 +35,7 @@ Add or Remove Projects - + @@ -62,31 +62,45 @@
Deploying single files - In the context menu of files there is a Deploy To Serve= r - option that allows a single file deployment. To deploy these non-WTP f= iles/projects - right click on the file (-ds.xml, .ear, .jar etc.) and select - Deploy To server + + Sometimes it becomes necessary to deploy only one or two files to= a server. For + that in order not to do a full republish in the context menu of files = a Deploy To Server + option is provided that allows a single file deployment. To deploy the= se non-WTP files/projects + right click on the file ( + -ds.xml, + .ear, + .jar etc.) and select + Deploy To Server and it will be automatically deployed.
Deploy to Sever - +
The deployed files are listed side-by-side with other modules tha= t are deployed to - the server. + the server.
+ = +
+ Deployed files on the Server + + + + + +
=
=
Deploying with JBoss Server View - As it has been already mentioned = - JBoss Server View contains two parts: the top par= t that displays all defined servers and the - bottom part which provides categories with additional information. Thus= , in this section - we suggest two more ways to deploy resources onto the server. + As it has been already mentioned JBoss Server View contains two + parts: the top part that displays all defined servers and the bottom pa= rt which provides + categories with additional information. Thus, in this section we sugges= t two more ways + to deploy resources onto the server.
Top part of JBoss Server View In the top part of the JBoss Servers View li= ke in the Servers @@ -156,22 +170,20 @@ The only way to ensure an Incremental Build , such as changes to one - .jsp, - - .html, - or + .jsp, + + .html, or .class file, is to enable the builder for that project. This is do= ne by either changing the global preferences for the Archives View, or by enabling project-specific preferences and ensuring the builder is on.
= - The last chapter covers a variety of methods on how you can deploy = needed modules onto a server. + The last chapter covers a variety of methods on how you can deploy = needed modules onto a + server. = In summary, this reference supplies you with all necessary informat= ion on the - functionality that = - JBoss Server Manager - provides for work with JBoss - AS. + functionality that JBoss Server Manager provides fo= r work with JBoss AS. --===============8339197607899476234==--