Repository Organization

From Filtered Push Wiki
Jump to: navigation, search


FilteredPush SVN Repository

Organization of FilteredPush Subversion repository on Sourceforge.

Multiple reorganizations since project incept, see variously: Discussion of reorganization of repository from prototype 2010Feb19. See also: Discussion of subsequent reorganization of repository 2011Nov08. See also: Subsequent reorganization of repository for better Maven integration 2013Jan16, discussion memorialized on Discussion page..

Current Organization

Implication of below should be documented on: Production_Coding_Standards#Repository_commits

See: http://sourceforge.net/p/filteredpush/svn/HEAD/tree/trunk/ and http://sourceforge.net/p/filteredpush/svn/HEAD/tree/

Top level FP-Design, trunk, tags, branches. Trunk contains projects and a top level pom:

Expanded View
  • FP-API-Library
  • FP-Akka
  • FP-Configuration - Contains the rules and ruleset configs for the AnnotationParser, the corresponding xml model descriptors for the AnnotationGenerator, and work flow xml files for Kepler. This is distinct from the network deployment configurations which can be found in FP-Applications.
  • FP-Drivers - Driver implementations for use by the AnnotationProcessor
  • FP-HTTP - Contains all deployable support projects that are not service oriented but can be wrapped by the SOA modules.
  • FP-JavaSOA - Contains FilteredPush SOA Applications and modules that are supported using one or many of the following frameworks/libraries: JavaEE/EJB, Spring, JAX-WS (SOAP), JAX-RS (REST).
  • FP-Applications - Contains applications of the SOA Modules in the form of EAR projects.
  • FP-Modules - Contains FilteredPush service modules (FP-Knowledge, FP-Analysis, FP-Messaging) and presentation layer components (FP-Web). Can be deployed as part of an application EAR or individually. Spring/EJB support and configuration for Tomcat or JavaEE server deployment.
  • FP-Testing - Contains any tests and testing utilities that aren't dedicated to unit testing specific components but are test clients designed to invoke the network in a deployment environment (i.e. testing the AccessPoint).
  • FP-Tools - ClientHelper tools.
  • FP-SemanticWeb - Semantic web related libraries for parsing/generating annotation rdf/xml.
  • FP-Examples - Contains example source code (i.e. FP-HelloEJB)
  • FP-IPT - FilteredPush IPT
  • FP-GG - FilteredPush Golden Gate



Reorganization to here was driven by use of Maven as a build system. Top level FP-Design, trunk, tags, branches, with projects within each branch.

See: http://sourceforge.net/p/filteredpush/svn/1919/tree/ and with parent pom in trunk and subprojects below: http://sourceforge.net/p/filteredpush/svn/1993/tree/trunk/

Subsequent Production Re-Organization

Reorganization in 2012

Repository reorganization.png
  • FP-Configuration - Contains the rules and ruleset configs for the AnnotationParser, the corresponding xml model descriptors for the AnnotationGenerator, and work flow xml files for Kepler. This is distinct from the network deployment configurations which can be found in FP-Applications.
  • FP-Drivers - Driver implementations for use by the AnnotationProcessor
  • FP-Examples - Contains example source code (i.e. FP-HelloEJB)
  • FP-IPT - FilteredPush IPT
  • FP-GG - FilteredPush Golden Gate
  • FP-HTTP - Contains all deployable support projects that are not service oriented but can be wrapped by the SOA modules.
  • FP-JavaSOA - Contains FilteredPush SOA Applications and modules that are supported using one or many of the following frameworks/libraries: JavaEE/EJB, Spring, JAX-WS (SOAP), JAX-RS (REST).
  • FP-Applications - Contains applications of the SOA Modules in the form of EAR projects.
  • FP-Modules - Contains FilteredPush service modules (FP-Knowledge, FP-Analysis, FP-Messaging) and presentation layer components (FP-Web). Can be deployed as part of an application EAR or individually. Spring/EJB support and configuration for Tomcat or JavaEE server deployment.
  • FP-SemanticWeb - Semantic web related libraries for parsing/generating annotation rdf/xml.
  • FP-Testing - Contains any tests and testing utilities that aren't dedicated to unit testing specific components but are test clients designed to invoke the network in a deployment environment (i.e. testing the AccessPoint).
  • FP-Tools - ClientHelper tools.


Retained overall structure of projects containing trunk/tags/branches, reorganized which code was in which projects.

See: http://sourceforge.net/p/filteredpush/svn/1093/tree/ to http://sourceforge.net/p/filteredpush/svn/1919/tree/

Initial Production Organization

2011 FP-Design

Separated FP-Design elements out of FP-Networking in 2011 See: http://sourceforge.net/p/filteredpush/svn/770/tree/

Reorganization in 2010

Moved repository from UMB to SourceForge. Retained project with contained trunk/branches/tags, added more projects for additional proposed products/clients.

See: http://sourceforge.net/p/filteredpush/svn/3/tree/ to http://sourceforge.net/p/filteredpush/svn/1085/tree/

As in Prototype, several top level projects, each containing trunk/tags/branches (FP-Web, FP-Network, FP-IPT, etc).

See: http://sourceforge.net/p/filteredpush/svn/3/tree/ to http://sourceforge.net/p/filteredpush/svn/1085/tree/

Prototype Repository Organization

Several top level projects, each containing trunk/tags/branches (FP-Web, FP-Network, FP-IPT).