The Early Draft Review for JSR 294 – Improved Modularity Support in the JavaTM Programming Language is now available for Review

The intention is to deliver this JSR as a component of Java SE 7.

JSR 294 plan to extend the Java programming language with new constructs called “superpackages” that allow hierarchical modular organizatio.

Each superpackage is a collection of one or more packages or superpackages, which helps to organize large programs consisting of many packages. Related packages that are grouped into a superpackage can access each others’ public
types, while unrelated packages outside the superpackage cannot access those types, unless the types are exported

Example declaration

superpackage A {
member package P;
member superpackage B;
}
superpackage B member A {
member superpackage C;
export superpackage C;
}
superpackage C member B {
member package Q;
export Q.X;
}

Find out more about JSR 294 Here and Here


JSR 308 proposes an extension to Java’s annotation system that permits annotations to appear on any use of a type. (By contrast, Java SE 6 permits annotations to appear only on class/method/field/variable declarations; JSR 308 is backward-compatible and continues to permit those annotations.) Such a generalization removes arbitrary limitations of Java’s annotation system, and it enables new uses of annotations. This proposal also notes a few other possible extensions to annotations

Example

@NonNullDefault
class DAG {
Set<Edge> edges;
List<Vertex> getNeighbors(@Interned @Readonly Vertex v) @Readonly {
List<Vertex> neighbors = new LinkedList<Vertex>();
for (Edge e : edges)
if (e.from() == v)
neighbors.add(e.to());
return neighbors;
}
}

Find out more about JSR 308 here


Managing multiple eclipse plugins can become difficult, specially when you need to update or remove a particular plugin.
Heres the easy way to manage multiple eclipse plugins.

1) create a folder ‘links’ under eclipse home folder.
2) create a file plugins.link under this folder.
This file can have any name as far as extension is .link, you can create multiple link file for different plugins.
3) edit the link file and put the path of custom plugins folder
example path=D:/customplugins ( use forward slash only).
This custom plugin folder should reflect eclipse plugins directory structure.
create a ecliplse folder within customplugin folder.
create two folders features, and plugins under eclipse folder.

Now you are ready to install plugins in that custom location.
You can repeat this steps to install different plugins in different folders. it will help you when you want to remove/reinstall a particular plugin.


JSR 283 Content Repository for Java Technology API version 2.0 has been approved.

The aim is to produce a content repository API that provides an implementation independent way to access content bi-directionally on a granular level.

A content repository is a high-level information management system that is a superset of traditional data repositories. A content repository implements  content services such as: author based versioning, full textual searching, fine grained access control, content categorization and content event monitoring. It is these  content services that differentiate a content repository from a data repository. Many of today?s (web) applications interact with content repositories in various ways. This API proposes that content repositories have a dedicated, standard way of interaction with applications that deal with content. This API will focus on transactional read/write access, binary content (stream operations), textual content, full-text searching, filtering, observation, versioning, handling of hard and soft structured content.

Original Specification can be downloaded from
here


Summary Of Proposed JSRs for Java SE 7 Platform
JSR 277: Java Module System

JSR 294: Improved modularity support in the Java programming language

JSR 295: Beans binding

JSR 303: Bean validation

JSR 292: Supporting Dynamically Typed Languages

JSR 296: Swing application framework

JSR 203: More new I/ O APIs for the Java Platform (NIO.2)

JSR 220: Enterprise JavaBeans™ 3.0

JSR 255: JMX specification, version 2.0

JSR 262: Web services connector for JMX agents

JSR 260: Javadoc™ Tag Technology Update

JSR(s) TBD Java Language changes

JSR 308: Annotations on Java Types

JSR 310: Date and Time API

Fore more detaild information of above JSRs visit JCP