Skip to main content

Upgrading Java

Sun recently released Java 6.0. As a current user of Java 5.0 (Dadnab is written primarily in Java), I've looked into upgrading to the new version. So far, I haven't done so, because I don't know how.

Before, it was mostly a matter of including jar files in the class path when compiling or running the Java program. Now I don't even know if those jar files exist in the new version.

This situation is striking. I have studied Sun's Java site and forums. I have downloaded new Java software and read the documentation. Perhaps I've missed something, but I really have no idea how to make my currently operational Java programs use the new version.

Did anyone specify upgradability requirements for Java 6.0? Did anyone test against them, having a sample of representative Java 5.0 users (not Sun employees) sit down and attempt to upgrade to the new version? I doubt it. They've ended up with a product and associated set of documentation that is unusable for some experienced Java programmers because they can't upgrade to it.

Can anyone help me? Dadnab currently uses the Java SDK and Java EE. What do I download, and what do I install, to simply upgrade to the new versions (so I can take advantage of some of the new functionality, such as generics)?

Comments

Post a Comment

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos
32 comments
Read more

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware
8 comments
Read more

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio
15 comments
Read more