openArchitectureWare.org

oAW has moved to Eclipse.

At this site you will find information about the outdated version openArchitectureWare 4, only.
Please read our letter of intent for further information.

 

CVS Archive

CVS

The openArchitectureWare source code development is hosted at SourceForge.

Hint: The download link at this page refers to the older Version 3 only.
Use the actual downloads page at this web site instead.

CVS content

The CVS directories growed for a long time. Therefore most of the subdirectories are deprecated and will not be supported any longer.

You can find the actual code in the oaw_v4 subdirectory.

Since the actual oAW code becomes more and more integrated in Eclipse, it's the obvious thing to use the Eclipse IDE also for our own development. So you will find many projects that can be directly imported into Eclipse there.

The several sub-projects are stored in a cascaded structure there. But it is a common agreement between the deveolpers that all of the projects should be stored locally in a flat structure. Some dependencies between project will only work, if you have your local copy also organised that way. That means that all imported projects have to be flat in one base workspace directory.

Components

The development of oAW is an ongoing process. That's why we only want to describe here the overall structure of the CVS:

The base projects that build the oAW framework are

  • core: The general code that builds the oAW framework (Eclipse independent, although they are structured as plugins)
  • core.plugin: The Eclipse plugins that integrate the several core projects into Eclipse (requires the core projects)
  • classic: The migrated oAW version 3 stuff. It still contains actually also all UML tool handling. So you'll need these projects, if you work with external UML tools.
    Some of the code is not further developed. But there is also new development there like the new MappingInstantiator.
  • documentation: The actual documentation sources and PDF files.
  • samples: All actual samples. This is again sub structured for the different examples.
You will find more new topics there that will also grow in the future.

There are several ways to access the CVS.

Anonymous CVS

  • Protocol: pserver
  • Host: architecturware.cvs.sourceforge.net
  • Repository: /cvsroot/architecturware
  • Login: anonymous
  • Password: no password required.

  • cvs -d:pserver:anonymous@architecturware.cvs.sourceforge.net:/cvsroot/architecturware login

    cvs -z3 -d:pserver:anonymous@architecturware.cvs.sourceforge.net:/cvsroot/architecturware co -P

SF oAW-developer account

  • Protocol: ssh/extssh
  • Host: architecturware.cvs.sourceforge.net
  • Repository: /cvsroot/architecturware
  • Login: your user name
  • Password: your password

  • cvs -z3 -d:ext:developername@architecturware.cvs.sourceforge.net:/cvsroot/architecturware co -P modulename

Importing the Team Project Set

A very convenient way to get all projects from CVS using Eclipse is importing a Team Project Set. To do so just follow these instructions:
  1. Open a new workspace (recommended)
  2. Download this Team Project Set file*) and save it to disk, filename: oaw4-all-usr.psf
  3. Choose File / Import / Team / Team Project Set
  4. Get a cup of coffee ;-)

*) get this version for the oAW 4.2 branch

new CVS location due to SourceForge restructuring

SourceForge improved its CVS service architecture, which became effective 2006-05-12
They promise greater performance and stability of the CVS and elimination of several single points of failure.

If you accessed the CVS before, you have to redirect your repository location to the new host.

old
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/architecturware login

new
cvs -d:pserver:anonymous@architecturware.cvs.sourceforge.net:/cvsroot/architecturware login

You may reload all stuff again from the new loacation or try to edit all ROOT files in all CVS directories with a suitable tool.

CVS webclient

General Notes about the current CVS state

The developers try to keep the sources in the CVS repository in a working state. However, this may not always be the case (e.g. as a result of ongoing major changes). Also, it is not recommended to mix files from CVS with previously released versions unless you know exactly what you're doing. Often dependencies exist that rely on using a specific version.

Until February 2006 we used another Open Discussion Forum at SourceForge that is still available.

This forum is no longer active but is still a good information repository for general discussions that had already been in the past.


Last Updated Wednesday, October 01 2008 @ 03:28 PM CEST; 11.820 Hits