CodeGear™ JBuilder® 2008 Release Notes

By: CodeGear

Abstract: JBuilder 2008 Release Notes

CodeGear™ JBuilder® 2008

    Release Notes

v 1.2.0

    Introduction

This document contains a subset of known problems, workarounds and tips for JBuilder 2008.

Check the JBuilder Technical Resource page at http://jbuilder.codegear.com/ for any additional JBuilder Release Notes items that may have occurred subsequent to this document.

For more product information, refer to the JBuilder 2008 Help online and the various links on the Welcome to CodeGear JBuilder 2008 menu item on the product Help menu. These resources describe the new features of JBuilder 2008. You can also find other plug-in specific help through the Eclipse Online Help links.


    System Requirements

The system requirements for CodeGear JBuilder (all editions) are listed below:

        PC (Windows® and Linux):

    • 1 GB RAM minimum (1.5 GB RAM recommended)
    • 700 MB to 1.2 GB hard disk space minimum, plus additional space during installation
    • Intel® Pentium®4/2.4 GHz or higher (or compatible)
    • High-resolution monitor
    • Mouse or other pointing device


    Windows™ Operating System:

    • Microsoft® Windows™ XP Professional (SP2)
    • Microsoft® Windows™ Vista 32-bit


      NOTE: ProjectAssist™ has a separate installer. ProjectAssist can only be installed on Microsoft® Windows® XP Professional (SP2) and Microsoft® Windows™ 2003 Server.

    Red Hat Enterprise Linux (IDE or Assimilated TeamInsight Components)

    • Red Hat Linux 4.0

        Macintosh® (IDE or Assimilated TeamInsight Components)

    • Intel Processor
    • 1 GB RAM minimum (1.5 GB RAM recommended)
    • Mac OS X Tiger (10.4)


        Updating Your Product License

    License updates include new or modified license attributes. There are three ways to update the JBuilder License:

    • Manual license updates
    • Scheduled license updates
    • Software update

    To manually update your license:

    1. Open Help | JBuilder Licensing | License Updates.
      The CodeGear license update selection window opens.
    2. From the CodeGear License update selection window, select the license(s) you wish to update.
    3. Click OK.

    If an update is available, a message is returned describing the new license. Click OK to update. There is also a message returned when there is no update available.

    To schedule license updates:

    1. Open Window | Preferences | CodeGear Licensing.
    2. Check Enable automatic license update.
    3. Select a schedule option in the Automatic License Update Schedule box.

    The final way to update your license happens when you update the software. At this time you are automatically asked if you would like to update your license.


        Blackfish SQL

    Below is new information regarding Blackfish SQL.

        Blackfish SQL Deployment on Different Machine

    In order to deploy Blackfish SQL for Java on a machine other than the one with the licensed copy of JBuilder 2008, click on the following link:

    If the previous JBuilder registration record was not found, the following error message is displayed: The serial number entered is an upgrade only version of the product, and requires a prior version of the product to be registered. That registration entry was NOT found, registration failed. (17)

    NOTE: For networked license users: if your instance of JBuilder is connected to the local license server (BLS or FLEXnet), copy [JBuilder2008RootDirectory]/jbuilder/eclipse/license/concurrent_xxx.slip (or named_xxx.slip) to your user home directory on the machine where Blackfish SQL is deployed. Check Blackfish SQL documentation for detailed instructions.

        Running Blackfish SQL for Java as a Service on Microsoft® Windows™ Vista and XP Professional

    When running Blackfish SQL for Java as a service, Blackfish SQL may not be registered by default. This is because JBuilder 2008 is licensed for a specific user; and Windows services by default do not run as that user. There are two options:

    • Run the Blackfish service as the same user that is licensed to run JBuilder. For example, if jbblogs is the registered JBuilder user, then open Start | Control Panel and double-click Administrative Tools. Next, double-click Services. Right-click Blackfish SQL, select Properties, and click the Log On tab. From here select the "This account" radio button, specify jbblogs as the user, and then enter jbblogs' password in the Password and Confirm password fields. If the service is running you need to restart it.
    • When you attempt to connect to a Blackfish SQL server running as a service and you receive an error, you see a message listing the directories where Blackfish SQL is looking for license files. Make note of those directories. Then, depending on your license, do one of the following:
      • Users who have already registered JBuilder 2008 Enterprise: https://reg.codegear.com/srs6/verify_email.jsp?serial=A2CB-SPASNA-GDA4QE-8EKC+1+2275 (or go to http://reg.codegear.com and enter Blackfish SQL JBuilder Enterprise Edition serial number: A2CB-SPASNA-GDA4QE-8EKC and Registration Code: 2275).Save the activation file in one of the directories Blackfish SQL is looking for licenses.
      • Users who have already registered JBuilder 2008 Professional: https://reg.codegear.com/srs6/verify_email.jsp?serial=F2QB-DTAKSD-AMBMBD-NELC+1+3212 (or go to http://reg.codegear.com and enter Blackfish SQL JBuilder Professional Edition serial number: F2QB-DTAKSD-AMBMBD-NELC and Registration Code: 3212). Save the activation file in one of the directories Blackfish SQL is looking for licenses.
      • If you are a networked license user and your instance of JBuilder is connected to the local license server (BLS or FLEXnet), copy [JBuilder2008RootDirectory]/jbuilder/eclipse/license/concurrent_xxx.slip (or named_xxx.slip) to one of the directories Blackfish SQL is looking for licenses.

        [5615] How to Make a Blackfish SQL Database Transactional

    The Mac and Microsoft® Windows™ Vista installer for Blackfish SQL 8 does not make the sample databases transactional. This prevents the databases from being accessed from JDBC or SQL unless the database is opened in read-only mode. Use the following steps to make sample databases transactional:

    1. Launch JdsExplorer from [BFSQL-INSTALL-DIR]/bin/JdsExplorer.
    2. Use File | Open to open a database.
      Sample databases can be found in the [BFSQL-INSTALL-DIR]/samples/JDataStore/datastores.
    3. Select a database to open.
    4. Enter sysdba for user and masterkey for the password.
    5. Use the TxManager|Install menu to make the database transactional.
    6. Press OK on the Tx Manager properties dialog.
    7. Close the JdsExplorer.


        Borland® Optimizeit™

    Updated Application Server Support - Optimizeit for JBuilder 2008 has been validated to work with application servers:

    • BEA WebLogic 8.1.4, 9.2 or 10.0
    • IBM WebSphere 6.0 or 6.1 with EJB 3 feature pack
    • Oracle Application Server 10.1
    • Apache Tomcat 5.0, 5.5 or 6.0.14
    • Apache Geronimo 1.1 or 2.1
    • JBoss 3.2.6, 4.0.5, 4.2.1 or 5.0
    • GlassFish v1.1 or v2

    Apple Mac OS Support - Optimizeit for JBuilder 2008 is validated to run in Eclipse within Mac OS X v10.4 Tiger.
    [4961] Optimizeit is supported only on Intel-based Macintosh.

    About the Optimizeit Agent and Platform Support on Disparate Systems - For profiling application results from a remotely running application or application server, you must have the Optimizeit Agent installed. There are unique versions of the agent for each operating system.

    You may install the remote agent from your original JBuilder DVD since it has versions for all supported operating systems. If you purchased JBuilder via electronic download however and do not have a DVD, you may download JBuilder versions specific to each operating system from the registered user download site, and install the independent Optimizeit agent from downloaded file.

    The following platform configurations are supported:

    JBuilder Platform OS Remote Platforms OS
    Windows XP Windows XP
    Windows XP RedHat Linux
    Windows XP Windows XP
    RedHat Linux Windows XP
    RedHat Linux RedHat Linux
    Mac OS 10.4 Tiger Mac OS 10.4 Tiger


        Using the Maven Repository

    The Maven repository snapshot zip file is located on the partner DVD for your convenience. A Maven repository is required for building JBuilder 2008 application factories data-aware sample modules. The modules will try to download the repository from the Maven central repository. If you have network issues, or run into problems with the download, you can unzip the provided maven repository zip file into your [user home]\.m2 directory. This ensures the data-aware sample modules work properly. Alternatively, you can prevent the modules from trying to download the repository across the network by setting the preference for Maven to "offline":

    1. Select Windows | Preferences.
    2. From the Preferences dialog, select Maven.
    3. Turn on the Offline checkbox.


        Reading Application Modules from an RSS Feed

    Application modules can be configured to be read from an RSS feed by selecting Window | Preferences | Applicaton Factory | Module Search/Export Directories. The ability to read the RSS feed modules is controlled by a menu item in the Application Factory Explorer. By default this setting is turned OFF. By turning this setting to ON, there is a possibility the startup of JBuilder will slow down if the Application Factory Explorer view is open and the network connection to the location of the external modules is slow.

    To turn the setting ON, open the Application Factory Explorer toolbar dropdown menu and select the "Include external module sources" menu item.


        Known Issues


    These issues are organized by product area.

        General

    Install, Startup, and Licensing

  • [4550 and 4698] Install fails to complete and JBuilder fails to launch with a JVM error,
    Cannot reserve more then 1136mb of memory for JBuilder on certain machine configurations.
    Workaround: This is a 2-step workaround.
    1. Edit the file JBuilder.ini in the root of the JBuilder install directory and add the parameter:
      -vm jre\jre\bin\javaw.exe
    2. Run JBuilder_Home/reset_Jbuilder.bat

    Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=188968.

  • Clean option on startup with new plugins: If you use a workspace that was created by an earlier version of JBuilder or Eclipse, the IDE should be launched with the -clean option on the command line:

    jbuilder.exe -clean

    This procedure is recommended whenever there are new plugin versions being executed. Using the clean option on the command line during startup removes caches and preferences in the workspace that might cause problems for the newer plugins.
  • [5425] Headless features require JBuilder to be licensed using full GUI - in order to run any command line tools or other headless features of JBuilder, JBuilder must first be licensed using the full GUI mode.


  • [5427] - Some data-aware frameworks are missing when upgrading an Enterprise License. For example: If you upgrade your license from JBuilder Professional to JBuilder Enterprise, you should run JBuilder with the -clean switch after you have entered the new license.
    1. If running JBuilder, exit the program.
    2. Go to a command prompt/terminal window.
    3. Navigate to the directory where JBuilder is installed, typically c:\JBuilder2008 on Windows, [userhomedirectory]/JBuilder2008 on Linux, or /Applications/JBuilder2008/JBuilder.app/Contents/MacOS/JBuilder on Mac.
    4. Launch JBuilder with -clean, jbuilder.exe -clean on Windows, ./JBuilder.bin -clean on Linux, and ./JBuilder -clean on Mac.

    You only need to do this once, after you upgrade your license. After that, you can and should launch JBuilder the way you usually do.


    Application Factory

  • [4423] A Problem reporting window opens stating that Could not restore workbench layout when opening JBuilder 2007 workspaces in JBuilder 2008.
    Workaround: For each perspective being used, reset the perspective to the default view by selecting Window | Reset Perspective


  • [4299] Adobe Acrobat Reader should be installed before attempting to open the PDF-format report for data-aware applications from within the IDE .


  • [3954] When trying to invoke Code Insight (the context sensitive popup windows in the JavaScript Editor) while editing Application Factory scripts displays the following error The compilation unit is not in build path of a JavaScript project
    Workaround: To disable this message, select Window | Preferences | JavaScript | Editor | Content Assist | Advanced and uncheck Other JavaScript Proposals and Type Proposals.


  • [4569] When pressing the Export Module button to create a new application module from the module editor, manual changes to readme.html and cheatsheets.xml need to be saved File | Save prior to doing an Application Module export in order for them to get included in the built module.


  • [5618] The tagx file doesn't get updated after linking a note to a tag.
    Workaround:
    1. Create a new application factory project.
    2. Create a new note and tag.
    3. Link the note to the tag and view the tagx file.
    //exp: The tagx file is updated to show that the note is linked with the tag.
    //act: The tag entry isn't updated with the note id.

    If you update the tagx file (by adding another tag, note, etc.), the file updates.


    Application Generator

  • [2732] Data-aware applications require that the project Java runtime "JRE System Library" be a full JDK in order to build the project successfully.


  • [4770] When you generate CRUD artifacts for one entity, generation of CRUD artifacts for related entities is NOT performed automatically. After CRUD generation Web-page for selected entity will be up-to-date and correct, but the links from this page to pages for related entities will not always work as expected until you explicitly invoke CRUD generation for related entities. Typical cases when broken link can occur:
    • You have entities A and B with 1:M or M:N relation link. You generate CRUD for entity A. Web page with list of entity A has link to page for entity B, but this link will not work until you generate CRUD for entity B also.
    • You have entities A and B without relation link. You generate CRUD for both of them. Then you add relation link between them you need to regenerate CRUD for both entities, otherwise Web link between pages will not work as expected.
    • Same applies for Tag cloud generation. After generation of tag cloud you will have correct tag cloud and tag list page, but the links from tag list page to entity page will not work correct until you regenerate CRUD for entity.


  • [5349] Compass search works incorrectly - Lucene supports escaping special characters that are part of the query syntax. Below are the current list special characters:
    &nbsp&nbsp&nbsp + - && || ! ( ) { } [ ] ^ " ~ * ? : \
    To escape these character use the \ before the character. For example to search for (1+1):2 use the query:
    &nbsp&nbsp&nbsp \(1\+1\)\:2
    For more information about search query syntax see http://lucene.apache.org/java/2_0_0/queryparsersyntax.html


  • [5342] Starting/deploying data-aware applications can sometimes timeout after 45 seconds. Although the server will usually start after several tries, the timeout can be changed through Window | Preferences | Server, Server timeout delay = Unlimited.


  • [4686] Compass: For a ParseException when trying to find by date field: Date format is defined in the compass-for-entityName.cmp.xml file of web application. By default java.util.Date type use MM/dd/yyyy format, java.sql.Timestamp - yyyy-MM-dd-HH-mm-ss.


  • [3771] For Data-Aware Application JBuilder 2008 supports only Tomcat 6.0.14 with MySQL 5.0.x.


  • [5589] After running Integration tests against a test database, to return back to the original database go to Project | Properties | Data-Aware Web Application Settings | Database settings, reselect correct database connection and click OK.


    Project Migration

  • [621] Legacy Java EE JBuilder project imports copy over generated sources for web services projects resulting in compilation errors in JBuilder 2008. Workaround: Remove the generated sources that were copied from the legacy project manually. Rebuild the project in JBuilder 2008.

  • [2202] Legacy Java EE project import fails if the machine does not have an active internet connection. Workaround: Ensure that the computer has an active internet network connection before performing a legacy JBuilder Java EE project import.

    Web Services

  • [2411] Geronimo Web Services: User cannot access web project using default context name when deploying a standalone web project Workaround: Package the web project into an Enterprise Application project and deploy the Enterprise Application Archive (EAR).


    Enterprise JavaBeans (EJB)

  • Creating a standalone Java test client for EJBs: JBuilder 2008 provides code templates for the initial context code required to lookup EJBs from a standalone Java client. Code templates are prefixed by gic. JBuilder 2008 provides code templates for all supported servers. To use the template:
    1. Type gic, followed by Ctrl+Space to invoke the code template listing.
    2. Select the appropriate code template according to the server being tested.
  • [785] EJB diagram: Double clicking on bean in model navigator does not open the diagram for a newly converted project.
    Workaround: User can open diagram by double clicking on the diagram package and then selecting the bean by double clicking on the bean (in model tree).
  • [1384] EJB 3.0: Oracle 10.3.1.1 standalone server is looped on password inquiry if the server is not initialized previously.
    Workaround: To use the Oracle OC4J 10.1.3.x application server, the user must perform a first time initialization manually, according to readme provided with Oracle server.
    After initial manual start and stop, OC4J can be used from JBuilder 2008.


  • [1555] EJB 2.x: Failure to generate home interfaces when bean has home method that does not start with ejbHome prefix, such as ejbHomename. Workaround: Make sure all home methods have the ejbHome prefix appended to the name.


  • [1639] XDoclet code generation fails if default JRE for workspace is set to JDK 1.4. Workaround: Ensure that the default JRE for the workspace is set to JDK 5.0.


  • [2320] Legacy Java EE project import fails to generate XDoclet annotations for business methods in session beans. Workaround: Delete the imported project and re-import the project in the same workspace.


  • [4969] Work around for performance issue with EJB Modeling - Use the option
    Windows | Preferences | EJB Modeling Prioperties | Source Synchronization to "Delay, ms" to tune based on the size of your application for better performance.


  • [4941] As a general rule, use CodeGear plugins if one exists for the Server/Version you are working with instead of the generic plugins for the same Server/Version since they have bug fixes and are tested to work correctly


  • [5087] In some conditions a problem marker Target bean is not defined for ejb relationship can appear even if there are no errors in the source code and an entity relationship is correctly defined.
    Workaround: Open target and source bean class in java editor, make some changes and save them. Run clean and build.


    Borland® Optimizeit™

  • [5348] On Linux platform, Optimizeit cannot compare Request Analyzer snapshots if the LD_LIBRARY_PATH is not set to include [optimizeit-install-path]/eclipse/optimizeit-agent/lib and [optimizeit-install-path]/eclipse/optimizeit-agent/ext/strace/lib directories


  • [4470] On Linux platform, Optimizeit does not display any data when ACServer has been started before JBuilder is launched. To work around this problem, stop the current profiling session, open a terminal window, run ACStop.sh to stop the ACServer, and relaunch the profiling session.


  • [5603] For instructions on how to use stand-alone optimizeit agent, open Help | Borland Optimizeit | Procedures | Using Optimizeit Agent.


    Third Party

  • [5443] Subclipse - on Linux and Macintosh, selecting Windows | Preferences | Team | SVN may cause an error dialog to appear. To stop the error from appearing, dismiss the error dialog , select the "SVNKit (Pure Java)" radio button on that preferences page, and apply your changes.

    This is due to Subclipse not bundling JavaHL for all platforms. See Subclipse bug http://subclipse.tigris.org/issues/show_bug.cgi?id=714. If you are interested in using JavaHL on your platform, see the following for details for how to do so, http://subclipse.tigris.org/faq.html#get-javahl.


  • [5372] ClearCase - users have reported issues with the ClearCase plugin that ships with JBuilder. IBM offers an improved version of the ClearCase plugin. If you use ClearCase with JBuilder we recommend that you download it from http://www.ibm.com/developerworks/rational/library/content/03July/2500/2834/ClearCase/clearcase_plugins.html.


  • [2870] In some cases when a JPA modeling project is under subversion VCS, modification of entities brings up a Subversion lock dialog.
    To avoid it edit \.metadata\.plugins\org.eclipse.core.runtime\.settings\com.tssap.selena.model.platform.eclipse.prefs file and add a line UseHookForTeamOperations=false.


  • [5322] JBoss Tools HTML Editor - On Linux systems, opening an HTML file for the first time in a workspace with the JBoss Tools HTML Editor may not work. If it fails, try restarting JBuilder. Select File | Switch Workspace | Other, and click OK to restart in the same workspace. If it still fails, follow the steps at http://labs.jboss.com/wiki/JBosstoolsVisualEditorFAQ to make sure you have the correct libstcd version installed on your machine.


  • [5652] The Java Script editor opens a dialog when code completion is invoked. This happens when typing a javascript varaibale followed by a '.'
    Workaround: Turn off all completion proposals in Windows | Preferences | Java Script | Editor | Content Assist | Advanced.


    Team Development with ProjectAssist and TeamInsight

The following are known problems in the various components installed during the ProjectAssist server installation. These can affect the use of these components by the TeamInsight clients.

ProjectAssist Administration

  • [2561] Navigating back and forth in ProjectAssist File Wizard during a .pacx file install may cause inconsistent results in subsequent relists of already scanned components.
    Workaround: Cancel and re-scan.


  • [2652] The caret and percent sign (^ and %) cannot be used in ProjectAssist project names. The use of these characters causes problems in Subversion.


  • [2836] Dates selected via the date picker UI in Xplanner are not formatted correctly. Workaround: users will need to enter the date manually in the date fields using the format yyyy-mm-dd instead of using the UI to select the dates.


Liferay

  • [1545] If first Pre-Installation Scan in the ProjectAssist Stack file install is skipped, the user cannot assimilate a running install of Liferay until the user enters non-conflicting values.
    Workaround: If you want to assimilate an existing Liferay installation, do not skip the first Pre-Installation Scan during the ProjectAssist stack file installation. Perform at least the Minimal Scan during the first Pre-Installation Scan.


  • [1943] When opening Bugzilla portlet through Liferay, the X-axis (Time)on the Trends tab starts with an old date.(1970-01-01)


  • [2619] On some systems, the StarTeam portlets in the Liferay portal may not work immediately after an install.
    Workaround: If the StarTeam portlets do not work, reboot the computer which has the Liferay server installed on it.


Continuum/Maven

  • [1344] The following error can occur while running Maven:

    Error: "The plugin 'com.borland.maven.mojo:qalab' does not exist or no valid version could be found"

    Error: "The plugin 'com.codegear.maven:optimizeit-test-coverage-plugin' does not exist or no valid version could be found"

    Error: "The plugin 'com.codegear.maven:together-reports-plugin' does not exist or no valid version could be found"

    The sample Maven 2 project generated by ProjectAssist can use one or more Maven 2 plugins created by CodeGear. When ProjectAssist installs the Continuum component, it copies the above plugins to the local Maven 2 repository.

    Continuum runs as a service and where it looks for the local Maven repository varies based on the particular configuration of Windows. On some machines, the CodeGear plugins are copied to the wrong location.

    It might look for the Maven repository in any of these locations:

    1. c:\.m2\repository
    2. windowsdrive:\Documents and Settings\LocalService\.m2\repository
    3. windowsdrive:\windows\system32\config\systemprofile\.m2\repository

    Workaround:

    1. The CodeGear plugins, along with cached copies of other plugins used by ProjectAssist, are in [ProjectAssist install dir]\projectassist\eclipse\plugins\com.borland.dsib.project[version number]\components\SampleProject\.m2.zip. Unzip that file into the .m2 directory that Continuum is using as its Maven repository. If prompted to overwrite any existing files when unzipping, you should do so.
    2. If individual developers want to run Maven against a ProjectAssist generated Maven 2 SampleProject, they need to install the directory and descendants on their local machine.
    3. For users not running as a service, the location of the Maven 2 repository is always userhome\.m2\repository. For example, if you are logged on with username JDOE, and assuming your Documents and Settings directory is on drive C:, your Maven repository is located at c:\Documents and Settings\JDOE\.m2\repository.


  • [1422] On initial startup, the Maven Archetype Wizard may take a long time to open. This is an issue with the m2 plugin indexing both the remote repository and the local .m2 directory. The first time the m2 plugin is loaded in a new workspace, it builds these indexes and require more time to open.


  • [1599]The Continuum build output page cannot display multibyte characters correctly.
    Workaround: Click on Download as text to view the result in plain text format.


  • [2329]In assimilation cases where Continuum is not installed on the same machine as Liferay, the project upload fails. Continuum requires access to the POM file. If there is a firewall between Continuum and Liferay, the project addition fails.
    Workaround:Open the Liferay port (8080) so that Continuum can access the project file.


  • [2629]By default, "Site goal" does not work since a dependent extensions section does not get added to the .pom file.
    Workaround: Add the following in your build section to run "site" goal from Continuum on JBuilder generated projects:
    <build> 
    	    <extensions>
    	      <extension>
    	        <groupId>org.apache.maven.wagon</groupId>
    	          <artifactId>wagon-webdav</artifactId>
    	          <version>1.0-beta-1</version>
    	        </extension>
    	      </extensions>
    	    </build>


CVS

  • [2610] Corrupt characters may appear in the comment areas of the CVS Liferay portlet. This may be caused by the default encoding of the server machine (used by Liferay) being different from the encoding used when checking in the comment. Workaround: A field exists on the CVS portlet Setup tab to specify type of encoding for comments.


Subversion

  • [1599] The Subversion viewer Show file field cannot display international characters.
    The Subversion viewer Diff to previous can display international characters only when the server character set and the source file character set are identical.


Bugzilla

  • [1299] When Bugzilla is installed as a ProjectAssist component, it exists in the root url context (for example, http://myserver:8070, as opposed to http://myserver:8070/bugzilla).


  • [1418] At least one component name is required in the Components field on the Projects tab of ProjectAssist Designer to be able to enter bugs for a Bugzilla project.
    Workaround: In the Components field for Bugzilla enter a single component name, or a comma-separated list of component names. Spaces are allowed in component names. If you use quotes around a component name, the quotes are part of the component name in Bugzilla.


  • [1608] Bugzilla webdotbase parameter is not set to use the installed WebDot, but instead points to the default value set by the installation of http://www.research.att.com/~north/cgi-bin/webdot.cgi/%urlbase%
    Workaround: This is actually designed behavior -- the default value works to display local and remote graphs. ProjectAssist installs a version of WebDot (graphviz 2.8) so that you can optionally use this version for generating dependency graphs locally. To generate dependency graphs locally:
    1. Select the Parameters link on the bottom of any Bugzilla page.
    2. Select Dependency Graphs in the list of setting groups on the left of the page.
    3. Follow the instruction for setting the webdotbase parameter. You must specify the full path to dot.exe in your installed WebDot.


  • [1943] When opening Bugzilla portlet through Liferay, the X-axis (Time)on the Trends tab starts with an old date.(1970-01-01)


  • [2559 and 2649] When installing a Bugzilla project through ProjectAssist, you cannot specify a default component or project name with a hyphen ('-') in it. Any such component does not get added to Bugzilla.
    Workaround: Use the Bugzilla web interface to add the component and version for the new project. The component is added in this case.


Mylyn

  • [8]When working with Mylyn and repositories that have already been configured, a user name and password credentials sometimes disappears -- this happens for all Mylyn repository types.
    Workaround: Open the repository properties and re-add the credentials.


StarTeam

  • [2032]It is possible that extended characters may appear corrupted if the encoding for the characters displayed in the �Connections Parameters� dialog does not match the default encoding used by the operating system. Open this dialog by selecting Window | Show Views | Other | Star Team | Server Explorer, right-click on the server in the server view and select Properties ) Workaround: Change the encoding in the "Connection Parameters" dialog to an appropriate value for the locale on which the user is running.


  • [2619] On some systems, the StarTeam portlets in the Liferay portal may not work immediately after an install.
    Workaround: If the StarTeam portlets do not work, reboot the computer which has the Liferay server installed on it.


MySQL

  • [769] Note: It is normal for Developers to have a No Access role for MySQL. Although Developers have no direct access to databases, ProjectAssist services that rely on those databases will work for TeamInsight members. Assigning the Developer role for MySQL has no effect; only users assigned an Administrator role have access privileges.


    Samples

The JBuilder 2008 welcome screen provides links to samples on the web. Go to:

  1. Help | Welcome to CodeGear JBuilder 2008
  2. Scroll down and click Samples and Wizards


    Videos

The JBuilder 2008 welcome screen provides links to samples on the web. Go to:

  1. Help | Welcome to CodeGear JBuilder 2008
  2. Scroll down and click Videos


    Documentation and Getting Help

Comments to the JBuilder 2008 help documentation are welcomed. Send documentation comments to: JBuilder 2008 Documentation Comments.

For the JBuilder FAQ, Videos, and all the other latest JBuilder 2008 information, please visit http://jbuilder.codegear.com/


    Installation Instructions

For installation instructions, see install.html in your [JBuilder2008Directory].


v200804151426

Server Response from: ETNASC02