From jbosstools-commits at lists.jboss.org Thu Mar 4 08:12:09 2010 Content-Type: multipart/mixed; boundary="===============8229485372035162621==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r20654 - branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en-US. Date: Thu, 04 Mar 2010 08:12:09 -0500 Message-ID: <201003041312.o24DC9jm021991@svn01.web.mwc.hst.phx2.redhat.com> --===============8229485372035162621== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ochikvina Date: 2010-03-04 08:12:09 -0500 (Thu, 04 Mar 2010) New Revision: 20654 Modified: branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en= -US/Article_Info.xml branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en= -US/Fixed_Issues.xml branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en= -US/Release_Notes.xml branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/en= -US/master.xml Log:

https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files = here with the ones for JBDS 3.0.0 GA release.

Modified: branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_N= otes/en-US/Article_Info.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 --- branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/Article_Info.xml 2010-03-04 13:08:09 UTC (rev 20653) +++ branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/Article_Info.xml 2010-03-04 13:12:09 UTC (rev 20654) @@ -1,3 +1,3 @@ = -Release NotesInformation about the c= hanges made to this JBoss Developer Studio release.= JBoss Developer Studio3.000These release note= s contain important information related to the JBoss Developer Studio. New = features, known problems, resources, and other current issues are addressed= here.= +Release NotesInformation about the c= hanges made for this release of the JBoss Developer Studio.JBoss Developer Studio3.000These rele= ase notes contain important information related to the JBoss Developer Stud= io. New features, resources, and other current issue= s are addressed here. Modified: branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_N= otes/en-US/Fixed_Issues.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 --- branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/Fixed_Issues.xml 2010-03-04 13:08:09 UTC (rev 20653) +++ branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/Fixed_Issues.xml 2010-03-04 13:12:09 UTC (rev 20654) @@ -18,7 +18,7 @@ - JBIDE-5= 355: A Contexts and Dependency Injection Project Facet has been add= ed to JBoss Developer Studio. + JBIDE-5= 355: A Contexts and Dependency Injection Project Facet has been add= ed to JBoss Developer Studio. This makes it poss= ible to enable CDI support for a faceted project via the New Dyna= mic Web Project wizard or the Project Facets setting page available at Project<= guimenuitem>PropertiesProject Facets. @@ -35,13 +35,13 @@ - JBIDE-5= 653: The ESB Content Based Router dialog box = has been modified so that the CBR Alias field is now m= ondatory, allowing the value of it to determine what other fields are avail= able. The Rule Set field is now not required when a CBR Alias of Regex or XPath is provided, since with thes= e alias the rules can be specified inline and the Rule Language field is now set to apply only when the CBR Alias is Drools. The Rules Reload field will only appl= y when a Rule Set has been specified. + JBIDE-5= 653: The ESB Content Based Router dialog box = has been modified so that the CBR Alias field is now m= andatory, allowing the value of it to determine what other fields are avail= able. The Rule Set field is now not required when a CBR Alias of Regex or XPath is provided, since with thes= e alias the rules can be specified in-line and the Rule Language<= /guilabel> field is now set to apply only when the CBR Alias is Drools. The Rules Reload field will only app= ly when a Rule Set has been specified. The table Route List found in the JB= oss ESB Editor now lists the expression sin= ce this is a common undertaking by users. - In the Add Route To dialog box, the Service Category field has been made mandatory. Other changes t= o this dialog box include the Desitination name only b= eing required if the previous CBR action contained a Rule Set and if the CBR action did not contain a Rule Set, an Expression field is included. + In the Add Route To dialog box, the Service Category field has been made mandatory. Other changes t= o this dialog box include the Destination name only be= ing required if the previous CBR action contained a Rule Set and if the CBR action did not contain a Rule Set, an Expression field is included. @@ -71,12 +71,12 @@ - JBIDE-5= 427: In the ESB Editor, the items that displayed when right clickin= g and going to Provider= New were presented in a different order to those= of the ListnerNew list. To ensure consistency the Provide= r list of items has been reordered to match the = Listner menu. + JBIDE-5= 427: In the ESB Editor, the items that displayed when right clickin= g and going to Provider= New were presented in a different order to those= of the ListenerNew list. To ensure consistency the Provid= er list of items has been reordered to match the Listener menu. - JBIDE-5= 229: ESB 4.7 that is contained within JBoss SOA Platfo= rm 5.0 is now offically supported in this version of the JBoss Developer Studio. + JBIDE-5= 229: ESB 4.7 that is contained within JBoss SOA Platfo= rm 5.0 is now officially supported in this version of the JBoss Developer Studio. @@ -86,9 +86,34 @@ - JBIDE-5= 108: The JBoss Runtime Manager was setup to search for ESB Runtime = files from a specified location reguardless of how it was installed. This c= aused issue when the ESB Runtime was installed as a user defined runtime. T= he issue has been rectified by adding a Configuration = field to the Preference page. If the user sets the Configuration field to the home location of the JBoss Enterprise Application Platform or JB= oss SOA Platform, there configuration combination will list a= ll available configurations. If the user selects a standalone ESB Runtime l= ocation, the configuration combination will be empty and the user should ig= nore the field. The ESB runtime classpath container now gathers configurati= on information from the selected server runtime and then selects JARs accor= dingly or the s! tandalone ESB Runtime. + JBIDE-5= 108: The JBoss Runtime Manager was setup to search for ESB Runtime = files from a specified location regardless of how it was installed. This ca= used issue when the ESB Runtime was installed as a user defined runtime. Th= e issue has been rectified by adding a Configuration f= ield to the Preference page. If the user sets the Configuration field to the home location of the JBoss Enterprise Application Platform or JBo= ss SOA Platform, there configuration combination will list al= l available configurations. If the user selects a standalone ESB Runtime lo= cation, the configuration combination will be empty and the user should ign= ore the field. The ESB runtime classpath container now gathers configuratio= n information from the selected server runtime and then selects JARs accord= ingly or the st! andalone ESB Runtime. + + + JBIDE-4= 730: The ESB project creation wizard receives a new logo following = this update. Instead of using the generic JBoss Developer Stud= io logo within the ESB project wizard, a new ESB wizard logo = is displayed. + + + + + JBIDE-4= 320: ESB projects are now Web Tools Platform (WTP) modules. This en= sures that it is possible to use an ESB module inside a WAR or EAR archive = within WTP. ESB project deployment has not been limited though and they can= still be deployed as an individual module. + + + + + JBIDE-4= 168: The ability to select a directory using a browser window has b= een added for the FS Message Filter and the FTP Message filter attributes o= f directory, post-directory and <= property>error-directory. This added feature ensures that a user= does not need to manually type the entire path to a directory but instead = they just select the path from a browser. + + + + + JBIDE-2= 024: The Process field f the Action<= /guilabel> tab in the ESB now includes a Browse butt= on that allows a user to select which method of the Action class should be used for the process. The list in the dialog will sh= ow all public methods that has a Message parameter. Mu= ltiple methods can be selected if necessary. + + + + + JBIDE-2= 023: The Class field of the Action tab now includes a Browse button that disp= lays the possible classes that extend from the AbstractActionLif= ecycle class. + + @@ -108,7 +133,7 @@ - JBIDE-5= 641: When specifying the persistence property: <proper= ty name=3D"hibernate.ejb.cfgfile" value=3D"hibernate.cfg.xml"/>, an error could display saying that the hibernate.cfg.xml file could not be found. This occured because the validator only con= sidered full paths and not relative path naming. This has since been correc= ted through the modification of the HibernatePersistenceUnit class. = + JBIDE-5= 641: When specifying the persistence property: <proper= ty name=3D"hibernate.ejb.cfgfile" value=3D"hibernate.cfg.xml"/>, an error could display saying that the hibernate.cfg.xml file could not be found. This occurred because the validator only co= nsidered full paths and not relative path naming. This has since been corre= cted through the modification of the HibernatePersistenceUnit class. = @@ -145,7 +170,7 @@ - JBIDE-5= 222: A new feature as been added that allows for support of filter configurations in closed porjects for console configur= ation. This option is available through Preference= sRun/DebugLaunchingLaunch Configurations. + JBIDE-5= 222: A new feature as been added that allows for support of filter configurations in closed projects for console configur= ation. This option is available through Preference= sRun/DebugLaunchingLaunch Configurations. @@ -173,6 +198,41 @@ JBIDE-4= 899: The Hibernate Configurations view was not= updated after a hibernate console enabled project with console configurati= on was deleted from the workspace. This meant that the console configuratio= n was not removed along with the project. This bug is rectified with this u= pdate. + + + JBIDE-4= 780: The Options tab now allows you to browse = and set the NamingStrategy and EntityResolve= r. The console configuration option has also been updated to rea= ct when one of the packages of a referenced class changes. + + + + + JBIDE-4= 733: A new feature has been added that allows a user to select whea= ther JPA-Generate DDL should be executed in the database. Before this updat= e this feature was automatic, always executing JPA-Generate in the database. + + + + + JBIDE-4= 715: A toggle button has been added to the Hibernate Mapping diagra= m to allow the outline view to be ordered either alphabetically or by the s= tructure outlined in the file. The toggle button interface ensures the expe= rience remains consistent across all tools included within the JBoss Developer Studio. + + + + + JBIDE-4= 662: Annotations support has been added to Hibernate Tools. The add= ition of annotations support allows for interaction with the Eclipse Dali J= ava Persistence Tools Project plug-in. + + + + + JBIDE-4= 451: The option is now given to the user to enable the HQ= L Editor and Hibernate Criteria Editor to b= e dynamically updated when opening a new query instead of opening an instan= ce of each editor for each query. This can be achieved by clicking the butt= on of a tack to the right of the Max results: drop-wo= n box in the editor. + + + + + JBIDE-4= 450: The Properties view has been updated with= a new property called Tab name. The addition of this = property allows for a user to individually name each query tab, allowing fo= r improved tab management. + + + + + JBIDE-4= 227: The Open Mapping File option now su= pports all possible configuration files. In the past only files called orm.xml have been supported and this update now provides i= ncreased user functionality. + + @@ -240,6 +300,46 @@ JBIDE-4= 970: KBbuilder now loads composite compo= nents from the JSF resource folders and adds them to the KB module. This al= lows for the components to be available for code assistance. + + + JBIDE-4= 771: The Find Usages function has been improve= d to provide information about methods when inside an EL expression. = + + + + + JBIDE-2= 806: The Eclipse OpenOn feature that allows a user to click any ref= erence to a template as if it was a hyperlink did not work if the template = path was set using an EL variable. This limitation has now been corrected s= o that OpenOn works with all paths, including those set using the EL variab= le. This is a great advantage to users as the Expression Language variable = is a frequently used feature. + + + + + JBIDE-81= 6: A bug existed within the JSF component of the JBos= s Developer Studio where if a resource bundle is defined in a= template page code completion for the bundle would not be available within= the file that includes the template with the loadbundles. The workaround f= or this was to also define the resource bundle in this template client file= , however that meant the same component was defined twice in the component = tree. = + + + The bug has since been fixed by adding a schema for included page c= ontexts. This schema enables the creation of contexts for all the pages inc= luded in the source and for the gathering of information on bundles declare= d in the included pages. The information collected is as follows: + + + + + Namespaces that are declared + + + + + Tag libraries that are used + + + + + Resource bundles that are declared + + + + + + + JBIDE-51= 2: The drop-down box for context variable code completion has been = upgraded for enhanced usability. The source of the variable is now outlined= during code completion and the code is highlighted in a different colour f= or improved reading and overall understanding of each file. + + @@ -271,7 +371,7 @@ - JBIDE-5= 221: The JBoss Server View has now been replac= ed with the Server View in the Seam perspective. This = has occured out of the JBoss Server View being deprica= ted. + JBIDE-5= 221: The JBoss Server View has now been replac= ed with the Server View in the Seam perspective. This = has occurred out of the JBoss Server View being deprec= ated. @@ -308,14 +408,49 @@ - JBIDE-4= 987: = + JBIDE-4= 987: Seam and JPA Connection Profiles have been synchronized for th= is release. The jpa-connection profile is used in the= launch configuration instead of hibernate.properties = if the JPA facet is installed. + JBIDE-4= 985: Seam projects now create a Hibernate configuration that uses t= he selected connection profile directly (without copying its settings into = the hibernate.properties file). + + + + JBIDE-4= 944: The Seam wizards Action, Entity= and Conversation had the ability to overwr= ite resources when they generated code. The wizards would warn the user tha= t some resources already existed and yet overwrite them. This has been corr= ected through the modification of the SeamBaseOperation.java file. + + + JBIDE-4= 856: Seam component methods and properties used in the Expression L= anguage (EL) have been refactored. This has caused the internal structure o= f the components to be modified so that the Query Participant works with the JDT Java Search to find usages and append them to = search results. The Rename Participant has also been= modified to work with the JDT Java Refactor to rename usages and apply cha= nges to the Java Refactor, allowing for a user to rename a setter= or getter method and have the R= ename Participant warn the user of the consequences of renaming= a paired method. + + + + + JBIDE-4= 136: Classloading issues were being faced by users of Seam Tools be= cause the JBoss Developer Studio used the MANIFEST.MF file for creating an artifact classpath instead = of using the EAR lib/ directory that is recommended by= Seam. Until now the JBoss Developer Studio has = not been able to use the EAR lib/ directory because th= is functionality has not been supported by Eclipse. With the introduction o= f Eclipse 3.5 in this release the use of the EAR lib/ = directory is now supported and the process of creating an artifact classpat= h has been updated. + + + + + JBIDE-2= 807: An option is now provided when creating a New Seam P= roject, to not create a test project. This has become an option = since the Seam model does not require the test project to exist and so allo= ws the user to decide if it is of importance. Selecting to create or not cr= eate a test project is achieved through the ticking of a Create T= est Project check box within the New Seam Project wizard. + + + + + JBIDE-1= 452: Support has been added for the Seam PDF Facelet tag library. T= his Facelet library allows for PDF creation from within Seam. + + + + + JBIDE-1= 451: Support has been added for the Seam Mail Facelet tag library. = This Facelet library allows for email forms to be created from within Seam.= All components of the Facelet have been included except mail:mes= sage and mail:body as these components are = rendered as divisions (using the <div> tag). + + + + + JBIDE-1= 176: The Seam Web Project now supports the JPA facet. Addition of t= he Java Persistence API allows for the management of relational data within= applications. + + @@ -421,7 +556,7 @@ - The createPartControl() method in the MozillaEditor and MozillaPreview classes create XullRunnerEditor as an inner class.= The issue was that the XullRunnerEditor class retai= ned a reference to MozillaEditor(MozillaPreview) tha= t caused it not to be released and instead retain references to WST and EMF= classes. This has now been corrected so that MozillaEditor(Mozi= llaPreview) is now released after use and referecnes are not re= tained. + The createPartControl() method in the MozillaEditor and MozillaPreview classes create XullRunnerEditor as an inner class.= The issue was that the XullRunnerEditor class retai= ned a reference to MozillaEditor(MozillaPreview) tha= t caused it not to be released and instead retain references to WST and EMF= classes. This has now been corrected so that MozillaEditor(Mozi= llaPreview) is now released after use and references are not re= tained. @@ -448,7 +583,7 @@ - JBIDE-4= 934: Facelets tag librarys support has been added to the = Palette for the Visual Page Editor. + JBIDE-4= 934: Facelets tag library support has been added to the P= alette for the Visual Page Editor. @@ -456,6 +591,98 @@ JBIDE-4= 914: The Visual Page Editor has been redesigned so that all drop-do= wn menu items are placed in the toolbar as buttons. + + + JBIDE-4= 323: Zoom actions have been added to the visual context menu so tha= t a user can now resize the content of the Visual Page Editor to make it ea= sier to read and manage. + + + + + JBIDE-2= 820: Support for new JSF 2.0 elements has been added to the Visual = Page Editor. The tags that are newly supported are: + + + + + h:head + + + + + h:body + + + + + h:outputscript + + + + + h:outputstyle + + + + + h:button = + + + + + h:link = + + + + + f:ajax = + + + + + f:event = + + + + + f:validateBean + + + + + f:validateRequired = + + + + + f:viewParam = + + + + + f:metadata = + + + + + + + JBIDE-2= 571: Selection of the <h:selectOneMenu> = did not function correctly. Instead of being selected with one mouse click,= two clicks were necessary. A bug was also present that made the nested com= ponents <f:selectItem> and <f:selec= tItems> unable to be selected from within the Visual Page Edi= tor. Correction of the two clicks necessary to select the <h:s= electOneMenu> component has been completed by removing the ch= eck within VpeController.java that ensures the node is= of type text. The issue that did not allow for the selection of the <f:selectItem> and <f:selectItems> components was found to be a bug in XULRunner. To correct this the = XULRunner component has been updated to version 1.9, which corrects this er= ror and provides! numerous other small bug fixes (JBIDE-2248. + + + + + JBIDE-2= 248: The XULRunner component has been upgraded to version 1.9. This= new version of XULRunner adds support for the newest HTML and CSS features= to the Visual Page Editor. Included in this is support for CSS3. + + + + + JBIDE-1= 592: A new feature has been added that allows for Facelets tag libr= aries from file.jar/META-INF/*.tablib.xml or those tha= t are registered within web.xml by the facel= ets.LIBRARIES context parameter to now be used within content as= sist for source editing in the Visual Page Editor. + + + + + JBIDE-52= 7: A bug existed within the Visual Page Editor that inhibited the <= guibutton>Previous and Next buttons for = detected occurrences of searched annotations to not function correctly. The= action of these buttons has now been corrected so that a user can navigate= their way through all found occurrences of a searched annotation. This fun= ctionality works in the Visual Page Editor as it would work in a text edito= r. + + @@ -499,16 +726,26 @@ + JBIDE-5= 734: The shortcut keys for full publishing a project to the server = and building a full archive have been combined under then shortcut key menu= accessed with AltShift= Y. From this menu press F to full publ= ish the project or B to build the full archive. + + + + JBIDE-5= 690: The Full-Publish hotkey would only acce= pt the first module and re-deploy it to the first server the module is depl= oyed on. For the user this meant that if the module was already deployed on= several servers, using Full-Publish would only re-d= eploy it to the first server returned in the list. To solve this issue a us= er interface has been added for the Full-Publish hot= key that allows for the selection of the server to re-deploy to. During the= implementation of this fix, the package has been renamed to XPL. - JBIDE-5= 267: The JBoss Enterprise Application Platform server would start correctly, however the JBoss Develop= er Studio would not acknowledge that it had started. To count= eract this the JMXPoller.java timeout behaviour has be= en modified to always return that the server succeeded in starting instead = of ignoring the timeout. This fix ensures that a user is not informed that = the server did not start correctly when it did. + JBIDE-5= 383: Expression Language Code Assistance has been added for the @Name beans. This allows for users to begin typing code a= nd for suggestions of automatic completion to be suggested, improving user = efficiency. + JBIDE-5= 267: The JBoss Enterprise Application Platform server would start correctly, however the JBoss Develop= er Studio would not acknowledge that it had started. To count= eract this the JMXPoller.java timeout behavior has bee= n modified to always return that the server succeeded in starting instead o= f ignoring the timeout. This fix ensures that a user is not informed that t= he server did not start correctly when it did. + + + + JBIDE-5= 153: A JavaMain tab has been added to the tab = group to allow for customization of the main class of the server. The chang= es to the main class are verified to persist by server startup checks. @@ -551,7 +788,7 @@ - JBIDE-5= 005: A new export wizard has been added to the JBoss D= eveloper Studio. The new wizard allows the export operation t= o utilize IModule objects. This added feature reduces redundancy and incons= istancy for the export operation. + JBIDE-5= 005: A new export wizard has been added to the JBoss D= eveloper Studio. The new wizard allows the export operation t= o utilize IModule objects. This added feature reduces redundancy and incons= istency for the export operation. @@ -559,7 +796,7 @@ JBIDE-4= 976: The JBoss Tools Palette has been intergra= ted into the standard Eclipse GEF Palette view. The st= andard Palette view, accessible at WindowShow View= OthersGeneralPalette<= /guimenuitem> is now shown in the right top part of the Web Development and Seam perspectives. = The JBoss Tools Palette remains at WindowShow View= OthersJBoss Tools Web= JBoss Tools Palette. - The differences in behaviour between the paletts are: + The differences in behavior between the palettes are: @@ -574,7 +811,7 @@ - Though the behaviour of the new palette is standard for Eclipse, f= or customers used to the globally set state of tabs and perfer to customize= the palette before opening the Visual Page Editor, th= e old palette will remain accessible. + Though the behavior of the new palette is standard for Eclipse, fo= r customers used to the globally set state of tabs and perfer to customize = the palette before opening the Visual Page Editor, the= old palette will remain accessible. @@ -589,7 +826,7 @@ - JBIDE-4= 888: The porlet facets configuration utility has been added for m2e= clipse. This configuration utility allows for the following: + JBIDE-4= 888: The portlet facets configuration utility has been added for m2= eclipse. This configuration utility allows for the following: @@ -614,6 +851,124 @@ JBIDE-4= 877: Tag completion has been upgraded so that partial matches are d= isplayed and selectable following direct tag matches. + + + JBIDE-4= 850: A new feature has been added to the CSS Views with this releas= e that allows a user to edit styles inside HTML and xhtm. + + + + + JBIDE-4= 690: The Maven Portlet library provider has been added to the JBoss Developer Studio with this release. + + + + + JBIDE-4= 689: The portlet libraries engine has been updated to use the WTP 3= .1 Library Framework. This framework is implemented in the Portlet Core and= JSF Portlet installation page. The following library providers are now ava= ilable to the user: + + + + + Library provider: + + + + = + + User Library + + + = + + Library provided by Target Runtime + + + = + + Disable Library Configuration + + + + + + Portlet Core Facet library providers: + + + + = + + Portlet Target Runtime Provider + + + = + + Maven Portlet 1.0 and 2.0 Libraries + + + + + + JSF Portlet Facet library providers: + + + = + + JSF Portletbridge Runtime provider + + + = + + JSF Portlet Target Runtime Provider + + + = + + Maven Portletbridge 2.0.0 ALPHA Libraries + + + = + + Maven Portletbridge 2.0.0 ALPHA Libraries with dependencies + + + + + + + + + JBIDE-3= 563: Code assist has been added for classes that are defined in lin= ked CSS. The schema for included page contexts has been added. This has occ= urred as it is needed to create the contexts for all the pages included in = the source. It allows for the gathering of information on bundles declared = in included pages. + + + The included page contexts are created and the following informatio= n is collected within the included contexts: + + + + + Namespaces are declared within the included pages + + + + + Tag libraries are used in the included pages + + + + + Resource bundles are declared within the included pages = + + + + + + + JBIDE-3= 125: Exadel OpenOn support has been added to the code editors. This= new functionality allows for a user to open a file that is being reference= d within the code, in a new editor window. Related CDI Beans will also appe= ar from a search of references to an object within the code, allowing for a= user to quickly see where else an object is referenced. + + + + + JBIDE-2= 541: A new feature has been added to this release that allows for t= he JavaDoc documentation to be available for the EL proposals as it is for = Java methods. The JavaDoc comments are also available if they originated fr= om a projects source folders. + + Modified: branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_N= otes/en-US/Release_Notes.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 --- branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/Release_Notes.xml 2010-03-04 13:08:09 UTC (rev 20653) +++ branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/Release_Notes.xml 2010-03-04 13:12:09 UTC (rev 20654) @@ -3,9 +3,9 @@
- + - +
Modified: branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_N= otes/en-US/master.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 --- branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/master.xml 2010-03-04 13:08:09 UTC (rev 20653) +++ branches/jbosstools-3.1.x/documentation/guides/JBDS_3.0_Release_Notes/e= n-US/master.xml 2010-03-04 13:12:09 UTC (rev 20654) @@ -34,7 +34,7 @@ JBoss by Red Hat - Version: 1.0 + Version: 3.0.0.GA