There is no change in any of the individual terms; this is merely a
rearrangement.
This change undoes what I was trying to do back in 2004 of breaking up
each individual test into a grep, for readability. The performance of
the script has continued to suffer as new greps were added over time,
to the point where this is now a bad tradeoff.
provides the ability to define model objects following the Active Record
design pattern, and using a DSL syntax similar to that of the Ruby on Rails
ActiveRecord system.
Elixir does not intend to replace SQLAlchemy's core features, but instead
focuses on providing a simpler syntax for defining model objects when you do
not need the full expressiveness of SQLAlchemy's manual mapper definitions.
Elixir is intended to replace the ActiveMapper SQLAlchemy extension, and the
TurboEntity project.
WWW: http://elixir.ematia.de
- Add ADDONS and PgSQL as OPTION.
- Docs are not updated on tar balls anymore, Docuwiki is now integrated in the groupware.
- Pass maintainership to submitter.
PR: ports/109133
Submitted by: Patrick Tracanelli <eksffa@freebsdbrasil.com.br>
files will be forgotten in the future, change the way the manual is
installed
- Install a desktop entry
- While here, move to LOCALBASE
PR: ports/108437
Submitted by: jylefort
Approved by: maintainer timeout (17 days)
applications that can configure, and perform operations on, a server applica
-tion. In general, each manageable component of the server application is re
-presented by a Management Bean (or MBean, for short). JMX defines three types
of MBeans, of which Model MBeans are the most flexible. Model MBeans provide a
way to define MBeans for many different components, without having to write a
specific MBean implementation class for each one.
However, this power comes at a price. It is necessary to set up a substantial
amount of metadata about each MBean, including the attributes it should expose
(similar to JavaBeans properties), the operations it should make available (si
-milar to calling methods of a Java object via reflection), and other related
information. The Modeler component is designed to make this process fairly pain
-less -- the required metadata is configured from an XML description of each
Model MBean to be supported. In addition, Modeler provides a factory mechanism
to create the actual Model MBean instances themselves.
The Modeler component of the Jakarta Commons subproject offers convenient
support for configuring and instantiating Model MBeans (management beans),
as described in the JMX Specification.
Homepage: http://jakarta.apache.org/commons/modeler/
Submitted by: Nemo LIU <nemoliu at gmail dot com>
PR: ports/109074
and the best supported such module of the several listed at
http://tcl.apache.org/
Works with both Apache-1.3.x and 2.x and has an interesting development
paradigm.
