The module some.package.path is not a friend of some-path\some.jar

So what is friend dependency anyways. Friend Dependency is caused by a Module that have an API which its author is not yet comfortable exposing to just anyone, because it might not be fully stabilized yet. In this case, the module with the API can declare some public packages, but also stipulate that only a predefined list of “friend modules” are permitted to use them. The friend modules just declare a regular specification version dependency, but unknown modules are not permitted to use any packages from the API module.

So in order to declare a dependency to that module, you need to use an implementation dependency. Please read the following Netbeans Wiki Dev FAQ on how to declare this implementation dependency and to enable friend dependency.

note: please also understand that implementation dependencies cause special problems for Auto Update. It is explained on the Netbeans Wiki Dev FAQ as well

Because there is already review of this book by Alex Ruiz who focused on pro and cons, so in this review I will focus on the book’s content itself.

Swing Extreme Testing book is come with 311 pages. The chapters structure is nice and follow the logical step and easy to follow. This books use real life application as the example rather than using imaginative sample. The content is very interesting it start with the methodology (Extreme Testing) as the author called. What needs to be tested, who is to write the tests, when they are to be written, so on. Then go to management of test class and test data. And the testing of User Interface itself. This books also describe the technique to test JavaHelp, ResourceBundle Testing, Server and User Interface Testing, and Multiple JVM testings.

In this books, the author present Cyborg, a higher-level wrapper for java.awt.Robot class. This is the tool for user interface testing. The books also discuss some very important techniques for testing Swing applications. These techniques are: how to set up user interfaces in a thread-safe manner, how to find the objects representing particular components on the screen and how to interrogate a component for its state.

The book is closed with flaky test, tests that occasionally fail or do not terminate. As the authors says

“The problem with having flaky tests is that they remove the element of reproducibility from our testing process. If our tests pass, we don’t know whether all the bugs we’re testing against have actually been fixed, or whether they just happened not to manifest themselves in that testing run. If our tests fail, this could be due to either production errors or testing errors, or both. If we can’t be sure of our test results, we can’t be sure of our software.”

Finally, all the tests presented are automated test. This books also contains many tips and trick using real life application (what worked for them and what didn’t). Those tips and tricks itself worth the book.

Some note: I really surprised when book also describe the ResourceBundle and JavaHelp tests.

If you are wondering how do we track Java version, please visit this step by step guide on how to track java version using google analytics at
http://cowwoc.blogspot.com/2008/11/tracking-java-versions-using-google.html

Here is our Java visitor stats, it is fresh from Google Analytics data 05 December 2008 - 05 January 2009

and the corresponding Operating System (OS) stats

Based on the above, Java 1.6_xx seems to have very nice grounds, and the Java 1.5 (9.36%) seems come from Mac OSX (12.90%), not set is probably from visitor who disable javascript (noscript).

The only things that puzzle me is the Java 1.8.0 (6.59%). Where does it come from or is there really a Java 1.8.0 ? If you know where this 1.8.0 come from, please do not hesitate to drop me a note.

Because of the above requirement I need to find a ways to reference or create instance of something from other module in the branding module, so nbres:// protocols was come to rescue.

In the example below, the settings and wstcref file of the TopComponent is located at other module (Core Module) and the layer.xml below is in the Branding module.

<folder name="Windows2">
    <folder name="Components">
        <file name="BookshelfTopComponent.settings" url="nbres:/kiyut/alkitab/windows/BookshelfTopComponent.settings"/>
        <file name="BookNavigatorTopComponent.settings" url="nbres:/kiyut/alkitab/windows/BookNavigatorTopComponent.settings"/>
        <file name="DefinitionsTopComponent.settings" url="nbres:/kiyut/alkitab/windows/DefinitionsTopComponent.settings"/>
        <file name="DailyDevotionsTopComponent.settings" url="nbres:/kiyut/alkitab/windows/DailyDevotionsTopComponent.settings"/>
    </folder> 
    <folder name="Modes">
        <folder name="explorer">
            <file name="BookshelfTopComponent.wstcref" url="nbres:/kiyut/alkitab/windows/BookshelfTopComponent.wstcref">
                <attr name="position" intvalue="100"/>
            </file>
            <file name="BookNavigatorTopComponent.wstcref" url="nbres:/kiyut/alkitab/windows/BookNavigatorTopComponent.wstcref">
                <attr name="position" intvalue="110"/>
            </file>
        </folder>
        ...
    </folder>
</folder>

For the complete example, you can download the complete source code of Alkitab Bible Study (Public Domain) at http://www.kiyut.com/products/alkitab/developer/index.html under source code section.

So now you can track your visitors who have java installed. The nice things regarding this tips and tricks is that this tips also capture the java version eg: Java 1.5, 1.6, etc. So no more wondering or guessing regarding Java installed base.

Since 1998, NetBeans has grown from a student project into an award winning Open Source project, IDE and application platform. With millions of downloads a year worldwide, the NetBeans community boasts an active and diverse following of software developers, students, instructors and partner companies.

For our 10th birthday bash we plan to highlight some of the key initiatives and individuals whose contributions and dedication have kept the NetBeans momentum going strong. There will be unique content—video greetings, community profiles and more—available during the week-long retrospective.

We’ve also come up with a fun way for the community to celebrate with us—the NetBeans Decathlon! Ten interactive activities that let NetBeans users show and share what the NetBeans project means to them.

Participants will be entered to win a cool limited edition NetBeans T-shirt. Stay tuned for details of the Decathlon and the official birthday kickoff!

Visit Netbeans 10th Birthday Celebration Site.

Note: this is tested on Netbeans 6.1, and use Alkitab Bible Study as example.

Architecture

As you probably aware, netbeans divide the platform into clusters, each cluster have their own directory and your Application (Platform Based) is given a cluster of its own eg:

- bin
- etc
- ide9 (IDE cluster)
- platform (Platform cluster)
- alkitab (your application cluster)
  * modules
    - locale (note this is important)
- ...

As far as I understand, the netbeans store the locale into the folder [cluster]/modules/locale. So somehow you need to put your jar (contain only locale) into that folder. Another important point that the jar name must be the same name as the module you want to localize eg:

- for com-your-modules.jar, the locale jar name should be com-your-modules[_country_lang].jar
- for org-netbeans-core.jar, the locale jar name should be org-netbeans-core[_country_lang].jar
- etc

The country code and lang is optional for the jar name. It only use if you really want to separate the jar for each locale. To keep thing simple we do not append the country code/language and all the supported locale will be under single jar.

Step 1: Create new module

The first step is to create new module project that will contain the localization (in this case for all languages). Inside the new module, create package (folder structure) which matching the things you want to localize and create the appropriate properties file localized (append country code and language)
eg: kiyut.alkitab.actions.Bundle_in_ID.properties

For the platform/ide cluster you need to find out where the text is localized and the jar name eg:
org.netbeans.core.actions.Bundle
with key Exit=E&xit
jar name = org-netbeans-core.jar
And create the same structure in the above new module project.

Step 2: Modify the build.xml

The next step is to modify the build.xml to produce the jar in appropriate location (note: the locale folder). The output will something like this

your-module-name-localization.nbm (this is the new project nbm as step 1)
- info
- META-INF
- netbeans
  - config
    - Modules
      - your-module-name-localization.xml
- modules
  - locale
    - your-jar-contain-localization-properties.jar (optionally can use country code)
    - org-netbeans-core.jar (netbeans part that you localize)
    - org-netbeans-core-windows.jar
    - etc
  - your-module-name-localization.jar

Here is the sample build.xml, note it overrides the target: jar and nbm.

<project name="kiyut.alkitab.modules.localization" default="netbeans" basedir=".">
    <description>Builds, tests, and runs the project kiyut.alkitab.modules.localization.</description>
    <import file="nbproject/build-impl.xml"/>
    <target name="build-init" depends="harness.build-init">
        <property name="update-source.basedir" value="../alkitab-suite/alkitab-core"/>
        <property name="locale.dir" value="${basedir}/build/cluster/modules/locale/"/>
    </target>
 
    <!-- Update the source for localization, it is only for Alkitab -->
    <!-- Netbeans properties file need to be update/copied manually -->
    <target name="update-source" description="Update locale source" depends="init">
        <copy todir="." preservelastmodified="false" verbose="true" overwrite="true">
            <fileset dir="${update-source.basedir}">
                <include name="src/**/*.properties"/>
                <include name="src/**/*.htm*"/>
                <exclude name="src/kiyut/alkitab/*.properties" />
                <!-- <include name="javahelp/**/*.properties"/>
                <include name="javahelp/**/*.htm*"/>
                <include name="javahelp/**/*toc.xml"/>
                -->
            </fileset>
        </copy>
    </target>
 
    <target name="jar" depends="projectized-common.jar">
        <!-- step 1: create jar for each module which only contains locale and place it under locale folder -->
 
        <mkdir dir="${locale.dir}"/>
        <jar jarfile="${locale.dir}/kiyut-alkitab.jar" compress="${build.package.compress}">
            <fileset dir="build/classes">
                <include name="**/kiyut/alkitab/**/*_*.properties"/>
                <exclude name="**/kiyut/alkitab/modules/**" />
            </fileset>
        </jar>
 
        <jar jarfile="${locale.dir}/org-netbeans-core.jar" compress="${build.package.compress}">
            <fileset dir="build/classes">
                <include name="**/org/netbeans/core/**/*_*.properties"/>
                <exclude name="**/org/netbeans/core/windows/**" />
            </fileset>
        </jar>
 
        <jar jarfile="${locale.dir}/org-netbeans-core-windows.jar" compress="${build.package.compress}">
            <fileset dir="build/classes">
                <include name="**/org/netbeans/core/windows/**/*_*.properties"/>
            </fileset>
        </jar>
 
        <jar jarfile="${locale.dir}/org-netbeans-modules-options-api.jar" compress="${build.package.compress}">
            <fileset dir="build/classes">
                <include name="**/org/netbeans/modules/options/**/*_*.properties"/>
            </fileset>
        </jar>
 
        <!-- step 2: update the module jar by removing the uneeded locale files for this module -->
 
        <property name="module.jar-temp" value="${module.jar}-temp"/>
        <jar jarfile="${cluster}/${module.jar-temp}" compress="${build.package.compress}" index="${build.package.index}" filesetmanifest="merge">
            <zipfileset src="${cluster}/${module.jar}">
                <include name="**/modules/localization/**"/>
                <include name="META-INF/**"/>
            </zipfileset>
        </jar>
        <move file="${cluster}/${module.jar-temp}" tofile="${cluster}/${module.jar}"/>
 
    </target>
 
    <target name="nbm" depends="projectized-common.nbm">
        <property name="nbm-expand" value="nbm-expand"/>
 
        <!-- step 1: unjar the created nbm file -->
        <unjar src="build/${nbm}" dest="build/${nbm-expand}">
            <patternset>
                <exclude name="META-INF/**"/>
            </patternset>
        </unjar>
 
        <!-- step 2: put the locale into the appropriate folder -->
        <copy todir="build/${nbm-expand}/netbeans/modules/locale/" >
            <fileset dir="${cluster}/modules/locale/" />
        </copy>
 
        <!-- step 3: re jar the result -->
        <jar jarfile="build/${nbm}" compress="true">
            <fileset dir="build/${nbm-expand}" />
        </jar>
 
        <!-- step 4 [optional: sign the nbm result -->
        <antcall target="sign-nbm" />
    </target>
 
    <target name="sign-nbm" if="keystore">
        <signjar jar="build/${nbm}" keystore="${keystore}" storepass="${storepass}" alias="${nbm_alias}" />
    </target>
 
</project>

Step 3: Finish and Testing

It is finished, you only need to test it. Note in your application Menu-Tools-Plugins, it should list the new localization plugins which can be updated by Update Center

You can download the whole source code at Alkitab Bible Study Developer section.

Update
Additional comment by Josh is available here (in German)

What’s new:

• Add Sword AugmentPath and DownloadDir
• Add Strongs and Morphology User Preferences or Options
• Add Source Viewer
• Various UI Improvement
• Various Bug Fixes
• [Installer] add options to install some books:
  KJV, StrongsHebrew, StrongsGreek, Robinson Morph

This release improve the stability a lot, it fixes many bugs. The next release will be 1.0 final, so if you find any bugs, questions, etc please do not hesitate to drop me a note, it help me a lot to stop the bugs before 1.0 final.

Due to the size issues (13.6 MB) the included [optional] books are: KJV, StrongsHebrew, StrongsGreek, and Robinson Morph. If you would like to distribute other books eg: ESV, ISV, TSK, the source code (2.9 MB) is available at http://www.kiyut.com/producs/alkitab/developer/index.html.

The ant build script is included with the source code, so minimal programming or technical skill is required:

• just copy the books you like into certain folder (make sure you understand the book copyright)
• modify the installer to add reference to your redist books.
• and run the build in script.
• then you are done.

Alkitab Bible Study is released as public domain, so feel free to modify/enhance, distribute, etc.

If you build a “standalone” module for your Netbeans RCP based application, during development you will notice that it will display the original Netbeans IDE/RCP splash screen rather than your branded application splash screen.

To enable your own branded splash during development you can add the following on the module project properties

# replace the token with your own branding token
branding.token=alkitab
branding.dir=none

Note: it is tested on Netbeans 6.1

• Many Photo Filter and Photo Effects.
• Easy, simple, and fun to create impressive photo effects.
• But suprisingly powerful.

What’s new:

• Add Crop Tool
• Add Selection Resize Tool
• Add Zoom (ctrl-key) and Pan (shift-key) with MouseWheel support
• Add Handle Size Options Preferences
• Add Menu - File - Revert
• Add Menu - File - Save As
• Improved Rotate Tool (shift-key)
• Improved Canvas
• Other bug fixes and enhancements

Citra FX Photo Effects Information

Product Page
http://www.kiyut.com/products/citra/index.html

Features Page
http://www.kiyut.com/products/citra/features.html

Screenshots Page
http://www.kiyut.com/products/citra/screenshots.html