This package contains the Bridje Java Applications Framework. A project that provides a set of Java APIs to be use in Java projects. Bridje can be compared to Spring but it´s more simplistic and lightweight. The project brings you a way of doing things that is not compromised by any JSR. The goals for this project are:
All of these goals are really ambitious, and at many times one or more of them need to be sacrificed in favor of the others, but we think that is a matter of balance and priorities. So the framework will orbit around these principles.
See Changelog See The Framework´s Wiki
The project is licensed under the Apache License:
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Bridje libraries are available on the Maven Central Repository
<properties>
....
<bridje.version>0.4.2</bridje.version>
</properties>
<dependencies>
....
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-ioc</artifactId>
<version>${bridje.version}</version>
</dependency>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-vfs</artifactId>
<version>${bridje.version}</version>
</dependency>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-http</artifactId>
<version>${bridje.version}</version>
</dependency>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-web</artifactId>
<version>${bridje.version}</version>
</dependency>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-el</artifactId>
<version>${bridje.version}</version>
</dependency>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-jdbc</artifactId>
<version>${bridje.version}</version>
</dependency>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-orm</artifactId>
<version>${bridje.version}</version>
</dependency>
....
</dependencies>
<build>
<plugins>
....
<plugin>
<groupId>org.bridje</groupId>
<artifactId>bridje-maven-plugin</artifactId>
<version>${bridje.version}</version>
<executions>
<execution>
<id>generate-bridje-sources</id>
<goals>
<goal>generate-sources</goal>
</goals>
<phase>generate-sources</phase>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-web-srcgen</artifactId>
<version>${bridje.version}</version>
</dependency>
<dependency>
<groupId>org.bridje</groupId>
<artifactId>bridje-orm-srcgen</artifactId>
<version>${bridje.version}</version>
</dependency>
</dependencies>
<plugin>
....
<plugins>
</build>
Your application will include the framework's librarys as well as this dependencies at runtime
Your application does not need to depend on this libraries unless you specifically include then
The libraries that the framework uses in the build process.