This guide is intended to orient GlassFish users to the new features and procedures which are provided by the Kenai suit of project hosting tools.
- 1 Where's my project?
- 2 How to log in
- 3 E-Mail
- 4 Where is my repository?
- 5 Manage your project
- 6 Project Roles
- 7 Project Bug Reports
- 8 What about external links?
- 9 Converting Themes
- 10 Wikis
- 11 Forums
- 12 Blogs
- 13 Training?
- 14 What to do if there's a problem with your project
When migrated, projects will move from <project>.dev.java.net to <project>.java.net (no more .dev, no more https!). For example, https://jersey.dev.java.net will move to http://jersey.java.net.
Each project is given a default home page and, each project can create a custom web-page. The default page is also found as
By default, this page has the common look & feel for Kenai.
We have re-written the GlassFish theme, for use with Kenai. For the first set of migrated projects, we have provided instructions, and we hope to manually migrate each project to this theme, as part of the migration effort. Further instructions and details are given below.
Your Collab user ID is migrated to the new Kenai infrastructure. All java.net users should have received their Welcome to java.net notification (from "firstname.lastname@example.org"). If you did not receive this notice, check your SPAM or filter folders. If that fails, you can user the "lost password?" link: enter your user id and you can reset your password via the e-mail link.
Note: Java.net uses Kenai tool suite and is very similar in look & feel. However, the systems are separate. This includes your log-in ID and all credentials. If you want your credentials (password, public-key, Etc.) to be the same, you must migrate them to java.net yourself.
Your e-mail user ID will become your-user-ID@java.net (During the transition, email@example.com will route through the Collab e-mail system and you'll continue to get notifications for Collab based updates and changes.)
Mail content will be migrated and is included in each projects documentation.
Project links are of the form:
More details about e-mail can be found here:
Note About SPAM Filters
If you use a SPAM filter, you may need to adjust your e-mail settings to prevent these messages from being identified as SPAM.
You can find the new repository URL by browsing to
The check-out URLs to your repositories will be listed in that table. For example, in the Mimepull project, the SVN repository is located at
Note for projects using CVS
Kenai only offers limited support for CVS. We have attempted to convert as many projects which formerly used CVS, to SVN. You can tell if your project has been converted by the repository name. For example, the MQ repository is converted as part of this migration. The new repository is named: Migrated CVS, but it is a subversion repository (you can tell from the repository URL). The repository location would be:
For projects which will remain in CVS after the migration, these projects are called CVS Repository, for example:
You must be logged in, to view the CVS access URL. (Your project can elect to migrate your repository to SVN manually)
Note: CVS is not an option for new projects. CVS is only supported for migrated, legacy project use.
CVS requires an SSH Key. You add this to your profile http://java.net/mypage, Click Edit My Profile, select SSH Keys tab. You can find details about creating and working with SSH keys at this help page. You can find more details about using CVS in this Issue/Article. Here is a writeup about configuring SSH and TortoiseCVS: TortoiseCVS Setup for Kenai. The authentication tools will only validate against a java.net user profile. You cannot use a kenai.com profile key. Note also: CVS does not currently generate commit notices. This enhancement is being added.
SSH support to Kenai does not require HTTP proxy integration. You can directly interact with Kenai SSH ports.
If you find you are behind a different proxy, the following may be useful (though it's not required inside Oracle WAN)
- If your new repository is migrated from CVS to SVN, you are in luck. SVN supports being proxied. There are a number of fine blog articles that outline the steps you will need to take to ci/co through a proxy with svn.
- The info on working with CVS through a proxy is a bit harder to find. This document gives you some generic info about access a CVS repo through a proxy. Read this document for more specific info on the content of the ~/.ssh/config file for systems inside the Oracle firewall.
SVN users may be able to avoid creating a new working copy of their project's source tree. See the documentation about the svn switch command and --relocate option.
Before you try that or create a new working copy from a checkout of the new repo, make a copy of your current diffs. Go ahead... I will wait.
If the repository has changed from a CVS repo to an SVN repo, you will need to create a new working directory.
Kenai project features are enabled in the "features" page. You can browse to that page via:
(You must have proper permissions to view and change these settings)
We recommend you read the documentation about the features available at Kenai:
Roles will be mapped during the migration process, as follows:
- Unauthenticated (aka Anonymous or Guest)
- Authenticated (anyone who has java.net/kenai.com account and logged in)
- Observer (anyone who wishes to watch a public project on java.net/kenai.com)
- Collab.observer -> Kenai.observer
- Content Developer
- collab.content-developer -> kenai.content-developer
- Tester (Not existing in java.net. If not applicable, don't use the role)
- Software Developer
- collab.developer -> kenai.developer
- Project Admin
- Collab.admin -> Kenai.admin
- Project Owner (1 per project, This is administratively assigned at conversion. Each project will need to designate the new owner, after conversion is completed.)
- First collab.admin -> kenai.owner, fix manually after migration
Migrated users will see one entry for each role they formerly held. You may elect to keep these, or remove the roles of lesser privilege. You will find more information about roles and permissions associated with each at these links:
All existing bug reports for all GlassFish projects will be migrated to Jira. This was chosen for several reasons, the primary one being that we needed to preserve the bug-ids from IssueTracker.
Mapping via IDs between IssueTracker to Jira will be possible (though we'll need to work through many of the sub-details).
For example, Issue 11921 is available at:
In IssueTracker: https://glassfish.dev.java.net/issues/show_bug.cgi?id=11921
In Jira: http://java.net/jira/browse/GLASSFISH-11921 (In the Sandbox, TestJava http://testjava.net/jira/browse/GLA-11921)
The query syntax is completely different. We'll need to recreate our bug queries.
If you haven't used Jira, have a look at the Jira User Guide:
We are using version 4.0
Each project has a "dashboard" which is useful as the general issue tracking home page. Two examples of this are:
Jira offers many opportunities for customizations. We are evaluating what customizations are available, and how we can best tailor Jira for our use. Here are a couple of other useful documents, to read about using Jira
Issue Tracker used Priority 1 (Highest) through 5 (lowest). Jira maps these values into words:
| Priority|| IssueTracker|| Jira|
| Highest|| P1|| Blocker|
| || P2|| Critical|
| || P3 || Major |
| || P4|| Minor |
| Lowest|| P5|| Trivial|
The Kenai team will do the best they can, to use DNS and Request forwarding, to ensure that external links yield something, if not exactly what might be expected, something close. Here are some examples of links that should be automatically forwarded.
At the top level, the project URL will automatically forward:
If using the default web-site:https://<project>.dev.java.net ==> http://java.net/projects/<project>If using the custom web-sitehttp://<project>.dev.java.net ==> <project>.java.net (your custom site)
Bugs: Issue Tracker will forward to Jira
https://<project>.dev.java.net/issues ==> http://java.net/jira/browse/<project>.
https://<project>.dev.java.net/servlets/ProjectMailingListList ==> http://java.net/projects/<project>/lists
https://<project>.dev.java.net/servlets/ProjectDocumentList ==> http://java.net/downloads/<project>
Source code: (not an exact match, but from Kenai URL below, you can see a list of repositories and you can select the repository you wish to browse)
https://<project>.dev.java.net/source/browse/<project> ==> http://java.net/projects/<project>/sources
A new theme has been written that conforms to the Kenai infrastructure. We have tried to map this theme to the current (old), GlassFish theme. There are some changes. The details of this conversion are described in this document:
We will try to automate this as much as possible, however, it is likely that project owners will need to customize this when the project is first migrated.
No Changes. All GlassFish projects were migrated to wikis.sun.com. A wiki service is available through Kenai. We encourage projects to continue to use wikis.sun.com at this time.
No Changes. GlassFish Forums are not migrated as part of this project. For example, the GlassFish forum remains at http://forums.java.net/jive/forum.jspa?forumID=56&start=0
Forums still hosted at Java.net will be migrated at the end of October as well. The e-mail bridge between this and the GlassFish (and other) e-mail lists will be preserved. There will be some downtime for this, but that is independent from the development project migration effort.
Blog migration is also a separate effort that has been underway for several months now too. The first step is migrating to the Drupal CMS. The plan is for all blogs to be moved to Oracle hosted servers by mid December. There will be some down-time, but it should be minimal.
First training session is rescheduled for Tuesday, Nov. 16, 9 AM PST. Further details to be posted. Allow about 90 minutes for this session -- 1 Hr for general overview followed by 30 minutes for site owners and managers.
First off, look for the help pages at java.net. Much of what we'll need to learn is, how does the Kenai infrastructure work. If that fails, you can contact the Kenai development team. There is a link at the bottom of default java.net pages, is a "contact us" link. You can use that for general Kenai related questions. Finally, if you have a problem specific to the migration, send an e-mail to: firstname.lastname@example.org.
You can also find information in the Kenai forums. These are at http://kenai.com/forums
I'm sure this won't answer all questions, but it's a start.