Category Archive for: ‘Java’
I have updated my Eclipse RCP demo application using Eclipse 3.3. I ran into problems with the update mechanism, getting errors with regards to the feature org.eclipse.rcp. I already filed a bug (204075).
Steps To Reproduce:
1. Create an RCP-based application with update functionality
2. Include the feature org.eclipse.rcp in your own feature
3. Deploy your application to the local file system
4. Create a new version of your feature
5. Update your update site
6. Try to update your previously deployed application
You cannot update it, because you get an error with regards to org.eclipse.rcp 3.3.0 v>xxxx>.jar: [Invalid signature file digest for Manifest main attributes]
Workaround (only tested on Windows):
1. Browse your Eclipse 3.3 distribution’s feature directory
2. Jar the org.eclipse.rcp feature again (to zip it and then rename it to .jar works just fine)
3. Copy the new feature to your update site (override the original org.eclipse.rcp feature)
Then your update works fine again.
It took me a while to figure out how I can make NetBeans work with my self signed ssl certificate that I use for my subversion server:
- Perform any svn operation with the locally installed command line client (addressing the server with the untrusted certificate)
- When the client responds with messages about an untrusted certificate, accept it
- Under Windows, copy your
C:Documents and SettingsApplication DataSubversionauthsvn.ssl.server to
C:Documents and Settings.netbeansconfigsvnconfigauthsvn.ssl.server
Then, svn command work well under NetBeans
I just updated the help system for one of my tutorial RCP applications to Eclipse 3.3. I wanted to use the Jetty stack instead of Tomcat, like the Eclipse 3.3 SDK does. Since the help on “RCP help” is still a bit outdated, it took me a while to collect all necessary plug-ins. Here is the list of plug-ins you need to deploy with your Eclipse 3.3 RCP based application if you want to use the Jetty stack (in alphabetical order):
Recently I implemented a customer-specific project wizard. Since I didn’t want to reinvent the wheel, I took a look at the existing Eclipse project wizards. When comparing them I noticed a few (little) inconsistencies. As an example compare the screen shots of the Java project wizard and the Plug-in project wizard. First, the plug-in project wizard:
Then the Java project wizard:
The plug-in project wizard is actually reusing the general new project wizard while the Java project wizard does not reuse it. I personally like the UI design of the plug-in wizard better because it is smaller, makes better use of space and has a more intuitive semantics. Consider the following situation: An Eclipse newbie wants to create a NEW Java project but not create the project in the workspace. How would he do that? As an experienced Eclipse user he would know that he just selects “Create project from existing source” and then browse to an empty or even non-existing directory. But that is not what the radio button’s text suggests.
Personally I found it very curious that I use Eclipse for years now and never noticed that :). This example is of course not a big deal, but wouldn’t it be a good time now to take a look at the existing Eclipse UI from a new user’s point of view and improve the usability and the consistency a bit?
If you agree, vote for bug 199147.
Recently I was invited to give a talk at TheServerSide Java Symposium in Barcelona, where I met Heinz Kabutz. Heinz is a nice guy and a real Java expert. He is also the author of a great Java newsletter. Take a look at http://www.javaspecialists.eu/, there you find more information about his newsletter.