From dleangen at canada.com Mon Oct 17 01:40:43 2005
From: dleangen at canada.com (David Leangen)
Date: Mon, 17 Oct 2005 14:40:43 +0900
Subject: Installation of Depot/Metro
Message-ID: <4353395B.3050303@canada.com>
Steve,
I'm finally starting to set this stuff up again.
Actually, I have no idea how to do this. IIUC, I first need to setup
Depot before I can do anything. It seems that Depot requires a graphical
environment. However, I am running text-only Linux. What do I need to do?
By the way, I think that it is customary, when creating a TAR archive,
to create the archive as a compressed directory of files. Since this
seems to be the usual practice, when I untarred the file, I ended up
with all the files mixed up in a place where I didn't want them to be.
That creates a bit of an inconvenient mess...
Cheers,
Dave
From mcconnell at dpml.net Mon Oct 17 10:11:35 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 17 Oct 2005 23:41:35 +0930
Subject: Installation of Depot/Metro
In-Reply-To: <4353395B.3050303@canada.com>
Message-ID: <20051017141146.SGTB21196.omta02sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of David Leangen
> Sent: Monday, 17 October 2005 3:11 PM
> To: DPML Development
> Subject: Installation of Depot/Metro
>
>
> Steve,
>
> I'm finally starting to set this stuff up again.
>
> Actually, I have no idea how to do this. IIUC, I first need
> to setup Depot before I can do anything. It seems that Depot
> requires a graphical environment. However, I am running
> text-only Linux. What do I need to do?
The depot application is itself a text-only application. It provides the
core support for loading up other plugins depending on commandline
parameters.
Here's a summary (based on HEAD):
console the core command line handler that includes support
for plugin deployment
setup a plugin that handles the setup and/or upgrading of the
depot installation
station a background process manager that handles the management
of a set of jvms based on installed application
definitions
exec an internal plugin used by the station to handle coordination
of new process creation and the handling of callbacks between
the station and the new process
There are also a couple of Swing-based plugins. These include plugins
handling system preferences and a Desktop plugin that provides support for
dynamic process control - however - these are both works-in-progress.
Support for the setup and configuration of applications does not require
Swing, however, for the moment you may need to write a little setup code to
do the initial installation.
>From memory your using Transit-based plugins - in which case you should be
able to simply launch your plugin using the depot console.
>
> By the way, I think that it is customary, when creating a TAR
> archive, to create the archive as a compressed directory of
> files. Since this seems to be the usual practice, when I
> untarred the file, I ended up with all the files mixed up in
> a place where I didn't want them to be.
> That creates a bit of an inconvenient mess...
Are we talking about the depot installation archive? Unpacking the archive
should result in the creation of three directories (prefs, data and shared).
If the archive was constructed so that there is a single root - would that
solve the problem?
Cheers, Steve.
>
> Cheers,
> Dave
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
From mhaavald at online.no Mon Oct 31 03:58:34 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Mon, 31 Oct 2005 09:58:34 +0100 (CET)
Subject: Status...
Message-ID: <6849692.1130749113631.JavaMail.adm-moff@moffice9.nsc.no>
Hi,
what is the status for DPML at present.
It has been very silent as far as I can see.
Is the september release stable and ready for use?
I am thinking of getting started with some server development.
I have tried some releases.
Now I would like to set up my dev environment and get started.
What I am looking for is howto's on setup of dev env, how to set up the build files etc...
If there is a "blueprint" server out there I could perhaps download it and have a go.
/Morten
From mcconnell at dpml.net Mon Oct 31 07:07:21 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 31 Oct 2005 22:37:21 +1030
Subject: Status...
In-Reply-To: <6849692.1130749113631.JavaMail.adm-moff@moffice9.nsc.no>
Message-ID: <20051031120733.IBKU15112.omta03ps.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Sent: Monday, 31 October 2005 7:29 PM
> To: dev-dpml at lists.ibiblio.org
> Subject: Status...
>
> Hi,
Hi Morten!
> what is the status for DPML at present.
Changes between HEAD and release 20050809.
Transit:
--------
Added a registry protocol handler enabling publication of references to an
RMI registry in the form registry://[host]:[port]/[path] or the shortform
registry:/[path]. Updates to the standard log message formatter to include
the JVM process identifier. Updates to the ContentModel implementation to
include the declaration of constructed types used as plugin parameters
(which makes for more reliability in plugin handling). Improvement to the
plugin loader preventing the assignment of an argument to more than one
constructor parameter value. Addition of support for primitive arguments
in plugin constructors (such as int, boolean, etc.). Upgrade of plugin model
to include support for system level jar files (e.g. protocol handlers or L&F
implementations that need to exist in the system classloader). Also added
Enum and ValuedEnum to Transit's util package.
Magic:
------
The entire module/resource model has been rewritten to be independent of
Ant. The implementation now builds a project model without any reference to
the underlying build strategy. A separate plugin is provided that
implements Ant-based builds. The build system itself now runs as a plugin
under Depot which introduces a suite of advantages such as: (1) build
configuration auditing, (b) building a named project, (c) building all
consumers of a project, etc. These updates also include over one hundred
tests and a much cleaner core system build (although I should mention that
the creation of a new release is pending some more work on the generation
of the overall installation - that's probably a few days off).
Depot
-----
Incorporated the Janel exe running into the distribution (mainly of
Interest to Windows users). Updates to DPML Station with support for
multi-JVM deployment and teardown. Added a remote logging services that
handles message aggregation from multiple JVMs to the central station and
support for JVM process identity within the default log message formatter.
Major cleanup of the APIs and the implementation dealing with application
profiles. Also improvements to Depot Preferences when running on JRE 5.0
under Windows. A rather deep but important update is support for plugins
that need to add jar files to the system classloader. This has been
integrated into the basic plugin model, plugin loader, and Depot
Application deployment services.
Metro
-----
General enhancements to the Part contract model including improvements
in the way top-level versus composite parts and handled. Separation of
state related aspects into a new package 'net.dpml.state' supported by a
cleaner implementation. Introduced support for long-term storage of
descriptors and directives compliant with JSR-57. Added definition and
implementation of a remote component model and context model suitable
for deployment independently of a component runtime (i.e. management
occurs on machine 'a' and deployment occurs on machine 'b'). Moved all
enumerations to formally typed enumerations (e.g. CollectionPolicy,
LifestylePolicy, etc.). At the moment there is still some work going on
inside Metro concerning the internal strategy for management of internal
parts versus management of the enclosing component. This is mainly an
issue of getting the APIs down just right.
> It has been very silent as far as I can see.
Sure has!
> Is the september release stable and ready for use?
It's ok ... but if you have the chose I'd wait for next release simply
because the build system and general module management is vastly
improved.
> I am thinking of getting started with some server development.
>
> I have tried some releases.
> Now I would like to set up my dev environment and get started.
> What I am looking for is howto's on setup of dev env, how to
> set up the build files etc...
> If there is a "blueprint" server out there I could perhaps
> download it and have a go.
By the end of the week the trunk/planet/http package will be back in
operation and this will provide a good example of setting up the build,
test and deployment environment. I'm also planning on using the http
package as an example of remote management of a server application.
Cheers, Steve.
> /Morten
>
From mcconnell at dpml.net Mon Oct 31 11:00:46 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Tue, 1 Nov 2005 02:30:46 +1030
Subject: Status...
In-Reply-To: <20051031120733.IBKU15112.omta03ps.mx.bigpond.com@julia>
Message-ID: <20051031160101.JHKW16720.omta01sl.mx.bigpond.com@julia>
> > Is the september release stable and ready for use?
>
> It's ok ... but if you have the chose I'd wait for next
> release simply because the build system and general module
> management is vastly improved.
Or even better ..
If you have some cycles available it would be great to get some validation
in place on the build process. The scenario under windows is looking good
but getting some external validation would be great.
The current build procedure for windows is:
a) build the bootstrap resources (bootstrap.bat)
b) build the main DPML system (build.exe)
c) build the DPML installation (pending)
(a) Bootstrap build
-------------------
Create a directory to hold the svn codebase (e.g. c:\dev\dpml), checkout the
sources, cd to the main directory and invoke the bootstrap build procedure.
$ cd dev\dpml
$ svn checkout svn://svn.berlios.de/dpml/trunk/main main
$ cd main
$ bootstrap
(b) System Build
----------------
The bootstrap build establishes the resources necessary for deployment of
Depot
running the core build system. Assuming that the %DPML_HOME%/Shared/bin
Directory is in the system path you should be able to build all of the DPML
platform using the following command:
$ build
The above command is basically a plugin that gets the current directory and
requests selection of all projects that are descendants of that directory,
and
builds each project. The lat project in the sequence in the DPML module
which
is where there the installation packaging occurs. Currently the tangible
results will be the complete javadoc, junit report, and a directory
containing
the installation bundle.
(c) Installation Build
----------------------
I'm currently working on this. The build procedure for the dpml module
handles
the creation of the DPML platform install bundle. The procedure does not
yet
create a zip or installer but this is the next item on the agenda.
Cheers, Steve.
From mcconnell at dpml.net Fri Nov 4 06:16:45 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Fri, 4 Nov 2005 21:46:45 +1030
Subject: Current TODO list
Message-ID: <20051104111652.QTLE19070.omta01ps.mx.bigpond.com@julia>
Here is a short-list of my TODO items:
1. application profile storage needs some reworking so that
the definition is available as a standalone XML file
2. the current module export implementation could be improved
with links to imported modules
3. scripts for 'station' and 'build' are needed for *nix
4. dpml module project needs to be completed with the creation
of the zip and tar installation archives
5. exported modules do not currently include module properties
6. need to add an external form of transit preferences
7. metro implementation needs to be synchronized with active
management model
8. online dos need to be updated to reflect changes in build
procedures and tools
9. there is a bug in Transit concerning dynamic system
classloader entries
The dpml/planet/http module is now synchronized with the updates to the
build system and this will serve as the foundation for getting in place
examples of application profiles. With that in place things will start to
fall into place with respect to examples of 'build', 'test', 'deploy', and
'management'.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mhaavald at online.no Mon Nov 28 13:58:30 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Mon, 28 Nov 2005 19:58:30 +0100 (CET)
Subject: SV: Status...
In-Reply-To: <20051031160101.JHKW16720.omta01sl.mx.bigpond.com@julia>
References: <20051031120733.IBKU15112.omta03ps.mx.bigpond.com@julia>
<20051031160101.JHKW16720.omta01sl.mx.bigpond.com@julia>
Message-ID: <1120129.1133204310571.JavaMail.adm-moff@moffice8.nsc.no>
Hi,
should I download head and build or await a new milestone release?
Ref. mail concerning som stuff you said you wanted to do.
/Morten
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-10-31 17:00:46 CET
> To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> Subject: RE: Status...
>
>
> > > Is the september release stable and ready for use?
> >
> > It's ok ... but if you have the chose I'd wait for next
> > release simply because the build system and general module
> > management is vastly improved.
>
> Or even better ..
>
> If you have some cycles available it would be great to get some validation
> in place on the build process. The scenario under windows is looking good
> but getting some external validation would be great.
>
> The current build procedure for windows is:
>
> a) build the bootstrap resources (bootstrap.bat)
> b) build the main DPML system (build.exe)
> c) build the DPML installation (pending)
>
> (a) Bootstrap build
> -------------------
>
> Create a directory to hold the svn codebase (e.g. c:\dev\dpml), checkout the
>
> sources, cd to the main directory and invoke the bootstrap build procedure.
>
> $ cd dev\dpml
> $ svn checkout svn://svn.berlios.de/dpml/trunk/main main
> $ cd main
> $ bootstrap
>
> (b) System Build
> ----------------
>
> The bootstrap build establishes the resources necessary for deployment of
> Depot
> running the core build system. Assuming that the %DPML_HOME%/Shared/bin
> Directory is in the system path you should be able to build all of the DPML
> platform using the following command:
>
> $ build
>
> The above command is basically a plugin that gets the current directory and
> requests selection of all projects that are descendants of that directory,
> and
> builds each project. The lat project in the sequence in the DPML module
> which
> is where there the installation packaging occurs. Currently the tangible
> results will be the complete javadoc, junit report, and a directory
> containing
> the installation bundle.
>
> (c) Installation Build
> ----------------------
>
> I'm currently working on this. The build procedure for the dpml module
> handles
> the creation of the DPML platform install bundle. The procedure does not
> yet
> create a zip or installer but this is the next item on the agenda.
>
> Cheers, Steve.
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
>
From mcconnell at dpml.net Tue Nov 29 04:02:32 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Tue, 29 Nov 2005 19:32:32 +1030
Subject: Status...
In-Reply-To: <1120129.1133204310571.JavaMail.adm-moff@moffice8.nsc.no>
Message-ID: <20051129090451.XSAR19070.omta01ps.mx.bigpond.com@julia>
> -----Original Message-----
> From: Morten Haavaldsen [mailto:mhaavald at online.no]
> Sent: Tuesday, 29 November 2005 5:29 AM
> To: Stephen McConnell; 'DPML Development'
> Subject: SV: Status...
>
>
> Hi,
>
> should I download head and build or await a new milestone release?
I recommend building from HEAD.
The trunk/main/README.TXT file has the build procedure info.
Cheers, Steve.
From mhaavald at online.no Tue Nov 29 08:34:01 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Tue, 29 Nov 2005 14:34:01 +0100 (CET)
Subject: SV: Status...
In-Reply-To: <20051129090451.XSAR19070.omta01ps.mx.bigpond.com@julia>
References: <1120129.1133204310571.JavaMail.adm-moff@moffice8.nsc.no>
<20051129090451.XSAR19070.omta01ps.mx.bigpond.com@julia>
Message-ID: <11699638.1133271241063.JavaMail.adm-moff@moffice11.nsc.no>
Hi,
thanks.
I'll have a go.
Do you use the eclipse plugin or do you have another dev env setup?
I.e. what do you recommend with respect to setting up a productive dev env.
/Morten
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-11-29 10:02:32 CET
> To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> Cc: 'Morten Haavaldsen' [mhaavald at online.no]
> Subject: RE: Status...
>
>
>
> > -----Original Message-----
> > From: Morten Haavaldsen [mailto:mhaavald at online.no]
> > Sent: Tuesday, 29 November 2005 5:29 AM
> > To: Stephen McConnell; 'DPML Development'
> > Subject: SV: Status...
> >
> >
> > Hi,
> >
> > should I download head and build or await a new milestone release?
>
> I recommend building from HEAD.
> The trunk/main/README.TXT file has the build procedure info.
>
> Cheers, Steve.
>
From mcconnell at dpml.net Tue Nov 29 09:22:30 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Wed, 30 Nov 2005 00:52:30 +1030
Subject: Status...
In-Reply-To: <11699638.1133271241063.JavaMail.adm-moff@moffice11.nsc.no>
Message-ID: <20051129142232.JXBX18661.omta02sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: Morten Haavaldsen [mailto:mhaavald at online.no]
> Sent: Wednesday, 30 November 2005 12:04 AM
> To: Stephen McConnell; 'DPML Development'
> Cc: 'Morten Haavaldsen'
> Subject: SV: Status...
>
> Hi,
> thanks.
> I'll have a go.
>
>
> Do you use the eclipse plugin or do you have another dev env setup?
No eclipse plugin at the moment (however - now would be the time to work on
this as Magic has been totally rewritten with a complete separation of
dependency logic from build strategy).
> I.e. what do you recommend with respect to setting up a
> productive dev env.
To build from scratch you will need Ant 1.6.5 installed on you machine and
an SVN client. I have the environment variable DPML_HOME defined on my
system - you may want to set this to something like C:\system\dpml (although
I should not that this is not absolutely required but its useful if your
developing).
After that:
$ cd dev\dpml\main
$ svn checkout svn://svn.berlios.de/dpml/trunk/main
$ bootstrap
$ build
You may want to checkout and build the http package.
$ cd dev\dpml\planet
$ svn checkout svn://svn.berlios.de/dpml/trunk/planet
$ build
In theory this should all work without problem (at least its working fine on
my machine). Let me know if you hit any bumps.
Cheers, Steve.
From mcconnell at dpml.net Wed Nov 30 11:35:06 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Thu, 1 Dec 2005 03:05:06 +1030
Subject: Woops - build is broken
Message-ID: <20051130163509.ZXNA24868.omta05sl.mx.bigpond.com@julia>
In the process of doing some enhancement to the build and site generation
I've managed to break the build. Hopefully I should have things sorted
shortly.
/Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Wed Nov 30 12:49:09 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Thu, 1 Dec 2005 04:19:09 +1030
Subject: Woops - build is broken [RESOLVED]
In-Reply-To: <20051130163509.ZXNA24868.omta05sl.mx.bigpond.com@julia>
Message-ID: <20051130174912.WMGK15112.omta03ps.mx.bigpond.com@julia>
.... and fixed.
Planet content is now included under the trunk/main svn directory and site
content production now reflects everything.
/Steve.
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Stephen McConnell
> Sent: Thursday, 1 December 2005 3:05 AM
> To: 'DPML Development'
> Subject: Woops - build is broken
>
>
>
> In the process of doing some enhancement to the build and
> site generation I've managed to break the build. Hopefully I
> should have things sorted shortly.
>
> /Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
From mcconnell at dpml.net Fri Dec 2 09:38:52 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Sat, 3 Dec 2005 01:08:52 +1030
Subject: Imminent updates
Message-ID: <20051202143858.SZHK19070.omta01ps.mx.bigpond.com@julia>
I'll be posting some significant updates to the DPML site this weekend.
Unlike earlier updates the new information will relate to the SVN HEAD.
Significant changes will include:
Transit:
A complete overall of the configuration mechanisms and the
the introduction of a transit command line tools supporting total
configuration management (for both local and remote Transit systems)
Magic replaced by the Depot Library and Build System:
Magic has been completely rewritten following the separation of
the core index from the build implementation. The index has morphed
info a common project library with an API that is completely
independent of the build strategy. A Depot Build System plugin
replaces Magic with an embedded Ant builder and a powerful
command line tool.
Metro enters finalization:
A new metro command line tools provides support for the deployment
of components with command line customization down to individual
context entries. The Metro Station is up and operational with
support for multiple JVM management, remote start-up, shutdown,
restart, interrogation, etc.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Sun Dec 4 19:35:43 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 5 Dec 2005 11:05:43 +1030
Subject: [SITE] info about updates to the site
Message-ID: <20051205003554.SAOI1358.omta03sl.mx.bigpond.com@julia>
Morning all!
The DPML site has been updated to reflect the current SVH HEAD
Development status. A new section has been added to the Home
group containing generated reports including JUnit reports,
complete javadoc, a full checkstyle report, and a generated
component catalog.
http://www.dpml.net/about/reports
Transit docs have been updated to include the new Transit
configuration management tools.
http://www.dpml.net/transit/cli/index.html
The Depot pages have been updated to include information about
the common project library apis and plug-selectable build system
(replacing the previous Magic documentation) and the build tool.
http://www.dpml.net/depot/library/index.html
http://www.dpml.net/depot/cli/index.html
Metro pages now include coverage of the general concepts although
details are lacking form the moment concerning related build tools
and documentation about the runtime. Documentation is available
concerning the metro application launcher and the station server
management system.
http://www.dpml.net/metro/runtime/cli/index.html
http://www.dpml.net/metro/station/cli/index.html
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mhaavald at online.no Wed Dec 7 19:12:59 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Thu, 8 Dec 2005 01:12:59 +0100 (CET)
Subject: SV: [SITE] info about updates to the site
In-Reply-To: <20051205003554.SAOI1358.omta03sl.mx.bigpond.com@julia>
Message-ID: <21937141.1134000778924.JavaMail.adm-moff@moffice5.nsc.no>
Hi,
I tried to build HEAD but encountered problems.
I checket out the code as, did bootstrap then ant (says build in instructions???), but ant gave the following(see below).
Hope this is easy to figure out.
/Morten
C:\development\dpml\main>ant
ant
Buildfile: build.xml
init:
standard.prepare:
prepare:
standard.build:
build:
[transit:import] failed to download link:plugin:dpml/metro/dpml-metro-tools
[transit:import] failed to download artifact:jar:dpml/util/dpml-util-cli#SNAPSHOT
BUILD FAILED
java.lang.RuntimeException: Unexpected error while constructing path instance for the scope: RUNTIME
at net.dpml.tools.impl.DefaultContext.createPath(DefaultContext.java:471)
at net.dpml.tools.impl.DefaultContext.init(DefaultContext.java:123)
at net.dpml.tools.impl.DefaultContext.getPath(DefaultContext.java:191)
at net.dpml.tools.tasks.ModuleTask.init(ModuleTask.java:54)
at net.dpml.tools.process.ModuleProcess.targetFinished(ModuleProcess.java:53)
at org.apache.tools.ant.Project.fireTargetFinished(Project.java:1922)
at org.apache.tools.ant.Target.performTasks(Target.java:374)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by: Unable to resolve artifact [artifact:jar:dpml/util/dpml-util-cli#SNAPSHOT].
at net.dpml.tools.impl.DefaultContext.resolveArtifact(DefaultContext.java:544)
at net.dpml.tools.impl.DefaultContext.addToPath(DefaultContext.java:527)
at net.dpml.tools.impl.DefaultContext.createPath(DefaultContext.java:504)
at net.dpml.tools.impl.DefaultContext.createPath(DefaultContext.java:465)
... 14 more
Caused by: net.dpml.transit.artifact.ArtifactNotFoundException: Unresolvable artifact: [artifact:jar:dpml/util/dpml-util-cli#SNAPSHOT]. (c:\projects\dpml_system\Data\cache\dpml\util\jars\dpml-util-cli-SNAPSHOT.jar)
at net.dpml.transit.DefaultCacheHandler.getResource(DefaultCacheHandler.java:396)
at net.dpml.transit.artifact.ArtifactURLConnection.getInputStream(ArtifactURLConnection.java:140)
at java.net.URL.openStream(URL.java:913)
at net.dpml.tools.impl.DefaultContext.resolveArtifact(DefaultContext.java:536)
... 17 more
Total time: 14 seconds
java.lang.RuntimeException: Unexpected error while constructing path instance for the scope: RUNTIME
at net.dpml.tools.impl.DefaultContext.createPath(DefaultContext.java:471)
at net.dpml.tools.impl.DefaultContext.init(DefaultContext.java:123)
at net.dpml.tools.impl.DefaultContext.getPath(DefaultContext.java:191)
at net.dpml.tools.tasks.ModuleTask.init(ModuleTask.java:54)
at net.dpml.tools.process.ModuleProcess.targetFinished(ModuleProcess.java:53)
at org.apache.tools.ant.Project.fireTargetFinished(Project.java:1922)
at org.apache.tools.ant.Target.performTasks(Target.java:374)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by: Unable to resolve artifact [artifact:jar:dpml/util/dpml-util-cli#SNAPSHOT].
at net.dpml.tools.impl.DefaultContext.resolveArtifact(DefaultContext.java:544)
at net.dpml.tools.impl.DefaultContext.addToPath(DefaultContext.java:527)
at net.dpml.tools.impl.DefaultContext.createPath(DefaultContext.java:504)
at net.dpml.tools.impl.DefaultContext.createPath(DefaultContext.java:465)
... 14 more
Caused by: net.dpml.transit.artifact.ArtifactNotFoundException: Unresolvable artifact: [artifact:jar:dpml/util/dpml-util-cli#SNAPSHOT]. (c:\projects\dpml_system\Data\cache\dpml\util\jars\dpml-util-cli-SNAPSHOT.jar)
at net.dpml.transit.DefaultCacheHandler.getResource(DefaultCacheHandler.java:396)
at net.dpml.transit.artifact.ArtifactURLConnection.getInputStream(ArtifactURLConnection.java:140)
at java.net.URL.openStream(URL.java:913)
at net.dpml.tools.impl.DefaultContext.resolveArtifact(DefaultContext.java:536)
... 17 more
Unexpected error while constructing path instance for the scope: RUNTIME
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-12-05 01:35:43 CET
> To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> Cc: 'DPML Support' [support-dpml at lists.ibiblio.org]
> Subject: [SITE] info about updates to the site
>
>
> Morning all!
>
> The DPML site has been updated to reflect the current SVH HEAD
> Development status. A new section has been added to the Home
> group containing generated reports including JUnit reports,
> complete javadoc, a full checkstyle report, and a generated
> component catalog.
>
> http://www.dpml.net/about/reports
>
>
> Transit docs have been updated to include the new Transit
> configuration management tools.
>
> http://www.dpml.net/transit/cli/index.html
>
>
> The Depot pages have been updated to include information about
> the common project library apis and plug-selectable build system
> (replacing the previous Magic documentation) and the build tool.
>
> http://www.dpml.net/depot/library/index.html
> http://www.dpml.net/depot/cli/index.html
>
>
> Metro pages now include coverage of the general concepts although
> details are lacking form the moment concerning related build tools
> and documentation about the runtime. Documentation is available
> concerning the metro application launcher and the station server
> management system.
>
> http://www.dpml.net/metro/runtime/cli/index.html
> http://www.dpml.net/metro/station/cli/index.html
>
>
> Cheers, Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
>
From mcconnell at dpml.net Wed Dec 7 20:23:20 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Thu, 8 Dec 2005 11:53:20 +1030
Subject: [SITE] info about updates to the site
In-Reply-To: <21937141.1134000778924.JavaMail.adm-moff@moffice5.nsc.no>
Message-ID: <20051208012323.LFAQ18661.omta02sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Sent: Thursday, 8 December 2005 10:43 AM
> To: Stephen McConnell; 'DPML Development'
> Cc: 'DPML Support'
> Subject: SV: [SITE] info about updates to the site
>
> Hi,
>
> I tried to build HEAD but encountered problems.
> I checket out the code as, did bootstrap then ant (says build
> in instructions???),
The bootstrap procedure creates the following:
1. transit core and tools
2. depot build tools and library
3. some external modules
4. the cli package
5. the build tool
6. the depot tool
If everything goes according to plan you should be able to enter the
following command to continue the build process:
$ build
However - keep in mind that the bootstrap script has no error handling
(which is not a problem if everything goes fine but it does mean that you
need to look at the info logged during the build for any BUILD-FAILED
messages).
Can you confirm that %DPML_HOME%/Shared/bin/build.exe exists?
> [transit:import] failed to download
> artifact:jar:dpml/util/dpml-util-cli#SNAPSHOT
The above error worrys me a bit because the dpml-util-cli artifact should
have been created in the bootstrap process.
Cheers, Steve.
P.s. I'm available on ICQ 19990444.
From mcconnell at dpml.net Wed Dec 7 22:26:07 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Thu, 8 Dec 2005 13:56:07 +1030
Subject: bootstrap.bat update
Message-ID: <20051208032611.LIXI19070.omta01ps.mx.bigpond.com@julia>
The bootstrap.bat file has been updated (SVN rev 727) to include error
checking. If an error occurs during bootstrap the build will fail with the
message:
BOOTSTRAP FAILED
Normal successful bootstrapping will end with the message:
BOOTSTRAP SUCCESSFUL
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Wed Dec 7 22:35:02 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Thu, 8 Dec 2005 14:05:02 +1030
Subject: [SITE] info about updates to the site
In-Reply-To: <20051208012323.LFAQ18661.omta02sl.mx.bigpond.com@julia>
Message-ID: <20051208033505.LSFR19070.omta01ps.mx.bigpond.com@julia>
> If everything goes according to plan you should be able to
> enter the following command to continue the build process:
>
> $ build
This assumes that the %DPML_HOME%\Shared\bin directory is declared in you
PATH environment variable (I've just added a note to that effect in the
README.TXT file).
Cheers, Steve.
From mcconnell at dpml.net Sun Dec 11 12:58:59 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 12 Dec 2005 04:28:59 +1030
Subject: [STATION] some issues being addressed
Message-ID: <20051211175909.UFZL17345.omta04ps.mx.bigpond.com@julia>
The DPML Station is an application that handles the deployment of
multiple component-based applications. A command line tool provides
support for the starting/stopping/restarting of applications isolated
within their own JVMs (and a bunch of stuff related to remote
application and profile management).
A number of utilities have been added recently to the SVN supporting
the deployment of the Station as an NT service. The existing
utilities are based on SRVANY.EXE however tests are showing that
there is an issues with JVM processes launched by the station
not being properly terminated when the termination is invoked by
the NT service.
Am currently looking into alternatives.
More news soon.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mhaavald at online.no Sun Dec 11 17:43:17 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Sun, 11 Dec 2005 23:43:17 +0100 (CET)
Subject: DateValidatorTest....
In-Reply-To: <20051211175909.UFZL17345.omta04ps.mx.bigpond.com@julia>
Message-ID: <29951711.1134340997373.JavaMail.adm-moff@moffice9.nsc.no>
Hi,
here is the result from bootstsrap and the DateValidatorTest.
[junit] Running net.dpml.cli.validation.DateValidatorTest
[junit] Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 0,091 sec
[junit] Test net.dpml.cli.validation.DateValidatorTest FAILED
I enclose the file.
/Morten
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-12-11 18:58:59 CET
> To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> Subject: [STATION] some issues being addressed
>
>
> The DPML Station is an application that handles the deployment of
> multiple component-based applications. A command line tool provides
> support for the starting/stopping/restarting of applications isolated
> within their own JVMs (and a bunch of stuff related to remote
> application and profile management).
>
> A number of utilities have been added recently to the SVN supporting
> the deployment of the Station as an NT service. The existing
> utilities are based on SRVANY.EXE however tests are showing that
> there is an issues with JVM processes launched by the station
> not being properly terminated when the termination is invoked by
> the NT service.
>
> Am currently looking into alternatives.
> More news soon.
>
> Cheers, Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
>
-------------- next part --------------
Testsuite: net.dpml.cli.validation.DateValidatorTest
Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 0,21 sec
Testcase: testSingleFormatValidate took 0,04 sec
Testcase: testDefaultDateFormatValidate took 0 sec
Testcase: testDefaultTimeFormatValidate took 0 sec
Testcase: testDefaultDateTimeFormatValidate took 0 sec
Testcase: testDefaultValidator took 0,01 sec
Caused an ERROR
23/01/03 18:00
net.dpml.cli.validation.InvalidArgumentException: 23/01/03 18:00
at net.dpml.cli.validation.DateValidator.validate(DateValidator.java:189)
at net.dpml.cli.validation.DateValidatorTest.testDefaultValidator(DateValidatorTest.java:116)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestDecorator.run(TestDecorator.java:28)
at net.dpml.cli.validation.TimeZoneTestSuite.run(TimeZoneTestSuite.java:40)
Testcase: testValidate took 0 sec
Testcase: testMinimumBounds took 0 sec
Testcase: testFormats took 0 sec
Testcase: testMaximumBounds took 0 sec
From mcconnell at dpml.net Mon Dec 12 04:50:36 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 12 Dec 2005 20:20:36 +1030
Subject: DateValidatorTest....
In-Reply-To: <29951711.1134340997373.JavaMail.adm-moff@moffice9.nsc.no>
Message-ID: <20051212095051.JOVX1358.omta03sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Hi,
>
> here is the result from bootstsrap and the DateValidatorTest.
>
> [junit] Running net.dpml.cli.validation.DateValidatorTest
> [junit] Tests run: 9, Failures: 0, Errors: 1, Time
> elapsed: 0,091 sec
> [junit] Test net.dpml.cli.validation.DateValidatorTest FAILED
>
> I enclose the file.
Thanks!
I've hit some issues before with the DateValidator - ended up debugging
stuff related to tests that pass when executed with default locale settings
but fail with different locale settings. Just for reference what timezone
and locale is your system set to?
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mhaavald at online.no Mon Dec 12 08:41:26 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Mon, 12 Dec 2005 14:41:26 +0100 (CET)
Subject: SV: DateValidatorTest....
In-Reply-To: <20051212095051.JOVX1358.omta03sl.mx.bigpond.com@julia>
References: <29951711.1134340997373.JavaMail.adm-moff@moffice9.nsc.no>
<20051212095051.JOVX1358.omta03sl.mx.bigpond.com@julia>
Message-ID: <18257644.1134394886495.JavaMail.adm-moff@moffice6.nsc.no>
Hi,
my timezone is GMT+1.00 (Oslo).
/Morten
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-12-12 10:50:36 CET
> To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> Subject: RE: DateValidatorTest....
>
>
>
> > -----Original Message-----
> > From: dev-dpml-bounces at lists.ibiblio.org
> > [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> > Morten Haavaldsen
>
> > Hi,
> >
> > here is the result from bootstsrap and the DateValidatorTest.
> >
> > [junit] Running net.dpml.cli.validation.DateValidatorTest
> > [junit] Tests run: 9, Failures: 0, Errors: 1, Time
> > elapsed: 0,091 sec
> > [junit] Test net.dpml.cli.validation.DateValidatorTest FAILED
> >
> > I enclose the file.
>
> Thanks!
>
> I've hit some issues before with the DateValidator - ended up debugging
> stuff related to tests that pass when executed with default locale settings
> but fail with different locale settings. Just for reference what timezone
> and locale is your system set to?
>
> Cheers, Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
>
From mhaavald at online.no Mon Dec 12 08:48:12 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Mon, 12 Dec 2005 14:48:12 +0100 (CET)
Subject: Developing components..
In-Reply-To: <18257644.1134394886495.JavaMail.adm-moff@moffice6.nsc.no>
References: <29951711.1134340997373.JavaMail.adm-moff@moffice9.nsc.no>
<20051212095051.JOVX1358.omta03sl.mx.bigpond.com@julia>
<18257644.1134394886495.JavaMail.adm-moff@moffice6.nsc.no>
Message-ID: <15509820.1134395292188.JavaMail.adm-moff@moffice6.nsc.no>
Hi,
which dpml libraries do I need to set up for basic development on DPML and where do they reside?
I am using JBuilder mostly but occasionally also eclispe which is better for multiproject development.
Perhaps eclipse is best:
One project each for API, SPI and IMPL.
I just want to set up a test server basically with some components providing services to other components.
One of them is to listen to a socket and receive incoming requests.
One nice thing to add to the component catalog would be Webservices(like from Axis 1.2, or Axis2) and have POJO's easily exposed....
Anyway, I start with a simple server config.
/Morten
From mcconnell at dpml.net Tue Dec 13 01:13:15 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Tue, 13 Dec 2005 16:43:15 +1030
Subject: Developing components..
In-Reply-To: <15509820.1134395292188.JavaMail.adm-moff@moffice6.nsc.no>
Message-ID: <20051213061327.QSWQ18661.omta02sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Sent: Tuesday, 13 December 2005 12:18 AM
> To: Morten Haavaldsen; Stephen McConnell; 'DPML Development'
> Subject: Developing components..
>
> Hi,
>
>
> which dpml libraries do I need to set up for basic
> development on DPML and where do they reside?
There are a number of different topics here:
a) tooling dependencies
b) component runtime dependencies
- helpful utilities
- service dependencies
c) test dependencies
d) deployment dependencies
Tooling Dependencies
--------------------
The current implementation provides a project library that is build system
independent. This is defined by the dpml/depot/dpml-library-common and
dpml/depot/dpml-library-console packages (the library is API to project
definitions and the console is the command line tool to list project info
and invokes project builders).
The default build system is based on Ant and is defined under the
dpml/depot/dpml-tools-builder package. Separation of library from build
implementation specifically addresses the earlier issues we encountered when
attempting automation in other build systems like Eclipse, etc. Based on
earlier activity in this area I'm confident that plugins could be created to
read in project definitions which would automatically populate an IDEs
internal project definitions.
Component Runtime Dependencies
------------------------------
Components do not require any runtime dependencies on DPML content - i.e.
there are no 'framework' structural dependencies. Instead the component
uses the Context inner class to declare operational criteria. The
operations declared within the component Context may imply introduce service
dependencies on other APIs. Beyond this there are some practical utilities
such as a Logger class that simply make like easier. The utilities are
included in the dpml/util/* packages and are all self-contained in that they
do not have external dependencies.
Utility package list:
dpml/util/dpml-util-i18n I18N support.
dpml/util/dpml-util-cli CommandLine support package.
dpml/util/dpml-configuration-api Immutable XML configuration data.
dpml/util/dpml-parameters-api Immutable named/value pairs.
dpml/util/dpml-activity-api Convenient lifestyle interfaces.
dpml/util/dpml-logging-api Simplified access to JDK Logger.
Test Dependencies
-----------------
The dpml/metro/dpml-metro-parts package contains a set of container APIs
that can are used to handle component deployment. These provide a
convenient mechanisms to load and deploy components without concern for the
container implementation. The package dependencies include
dpml/metro/dpml-state-api and dpml/transit/dpml-transit-main.
An example of the usage of the parts API is shown in the following page:
http://www.dpml.net/metro/runtime/controller/index.html
In a testcase you would typically replace the uri with something like:
final File dir = new File( System.getProperty( "project.test.dir" ) );
URI uri = new File( test, "test.part" ).toURI();
Package Location
----------------
Prior to a binary release you should reference packages from
DPML_HOME/Shared/local directory. This is basically a local repository
containing everything used and produced in the build of the dpml tools,
runtime and components. Please note that this repository uses the 'classic'
layout (i.e. [group]/[type]s/[name].[type]) and I just want to mention that
this may be changed to the 'modern' layout before release.
> I am using JBuilder mostly but occasionally also eclispe
> which is better for multiproject development.
>
> Perhaps eclipse is best:
>
> One project each for API, SPI and IMPL.
Try and think of these in terms of PUBLIC, PROTECTED and PRIVATE. The only
reason for separation is when you want to share or expose a part of a
implementation such as an API - as such an API is typically classified as
PUBLIC. You may want to expose additional APIs to internal components or
management applications in which case these would be viewed as PROTECTED -
and the rest is PRIVATE.
When a separation is required it is best to define the codebase in a
separate project because this creates an identifiable jar file which in-turn
can be referenced when declaring a component part (an potentially tagged in
terms of their PUBIC, PROTECTED or PRIVATE role).
On the other-hand, starting off with a single project for everything makes
life easy. After all, it's easy to breakout things into multiple projects
later on.
>
> I just want to set up a test server basically with some
> components providing services to other components.
>
> One of them is to listen to a socket and receive incoming requests.
As a starting point take a look at the classes in the main/metro/test
package. In particular - src/main/net/dpml/test/app which contains a Server
and Listener interface, a DefaultServer and DefaultListener implementation,
a Demo component and testcase in
src/test/net/dpml/runtime/test/AppTestCase.java.
All of the above gets tied together with the following instructions (from
metro/test/build.xml):
Cheers, Steve.
>
> One nice thing to add to the component catalog would be
> Webservices(like from Axis 1.2, or Axis2) and have POJO's
> easily exposed....
>
>
> Anyway, I start with a simple server config.
>
>
>
> /Morten
>
>
>
>
>
>
From mcconnell at dpml.net Tue Dec 13 01:52:52 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Tue, 13 Dec 2005 17:22:52 +1030
Subject: DateValidatorTest....
In-Reply-To: <18257644.1134394886495.JavaMail.adm-moff@moffice6.nsc.no>
Message-ID: <20051213065304.QVNU10380.omta04sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Sent: den 13 december 2005 00:11
> To: Stephen McConnell; 'DPML Development'
> Subject: SV: DateValidatorTest....
>
> Hi,
>
> my timezone is GMT+1.00 (Oslo).
Thanks - I just changed the 'Regional and language Option' on my system to
Sweeden and ran the util/cli build - and guess what? The test failed.
Testcase: testDefaultValidator took 0 sec
Caused an ERROR
23/01/03 18:00
net.dpml.cli.validation.InvalidArgumentException: 23/01/03 18:00
at net.dpml.cli.validation.DateValidator.validate(DateValidator.java:189)
at net.dpml.cli.validation.DateValidatorTest.testDefaultValidator(
DateValidatorTest.java:116)
Now that things are repeatable I should be able to figure out what is
happening.
/Steve.
>
> /Morten
>
>
>
>
>
> > From: Stephen McConnell [mcconnell at dpml.net]
> > Sent: 2005-12-12 10:50:36 CET
> > To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> > Subject: RE: DateValidatorTest....
> >
> >
> >
> > > -----Original Message-----
> > > From: dev-dpml-bounces at lists.ibiblio.org
> > > [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of Morten
> > > Haavaldsen
> >
> > > Hi,
> > >
> > > here is the result from bootstsrap and the DateValidatorTest.
> > >
> > > [junit] Running net.dpml.cli.validation.DateValidatorTest
> > > [junit] Tests run: 9, Failures: 0, Errors: 1, Time
> > > elapsed: 0,091 sec
> > > [junit] Test net.dpml.cli.validation.DateValidatorTest FAILED
> > >
> > > I enclose the file.
> >
> > Thanks!
> >
> > I've hit some issues before with the DateValidator - ended up
> > debugging stuff related to tests that pass when executed
> with default
> > locale settings but fail with different locale settings. Just for
> > reference what timezone and locale is your system set to?
> >
> > Cheers, Steve.
> >
> > --------------------------
> > Stephen McConnell
> > mailto:mcconnell at dpml.net
> > http://www.dpml.net
> >
> >
> > _______________________________________________
> > dev-dpml mailing list
> > dev-dpml at lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/dev-dpml
> >
>
From mhaavald at online.no Sun Dec 18 15:36:11 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Sun, 18 Dec 2005 21:36:11 +0100 (CET)
Subject: Building 782 fails with metr/state test...
In-Reply-To: <20051215153503.XOML10380.omta04sl.mx.bigpond.com@julia>
References: <2491943.1134600099978.JavaMail.adm-moff@moffice11.nsc.no>
<20051215153503.XOML10380.omta04sl.mx.bigpond.com@julia>
Message-ID: <3750085.1134938171629.JavaMail.adm-moff@moffice3.nsc.no>
Hi,
Build fails inside metro/state.
Hope the log below is helpful.
/Morten
[junit] Running net.dpml.metro.state.test.DefaultStateMachineTestCase
[x:reactor] net.dpml.metro.state.StateBuilderRuntimeException: Internal error while attempting to build state graph.
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:82)
[x:reactor] at net.dpml.metro.state.test.DefaultStateMachineTestCase.setUp(DefaultStateMachineTestCase.java:52)
[x:reactor] at junit.framework.TestCase.runBare(TestCase.java:125)
[x:reactor] at junit.framework.TestResult$1.protect(TestResult.java:106)
[x:reactor] at junit.framework.TestResult.runProtected(TestResult.java:124)
[x:reactor] at junit.framework.TestResult.run(TestResult.java:109)
[x:reactor] at junit.framework.TestCase.run(TestCase.java:118)
[x:reactor] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[x:reactor] at junit.framework.TestSuite.run(TestSuite.java:203)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:632)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.executeUnitTests(JUnitTestTask.java:336)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.execute(JUnitTestTask.java:203)
[x:reactor] at net.dpml.tools.process.JarProcess.targetStarted(JarProcess.java:124)
[x:reactor] at org.apache.tools.ant.Project.fireTargetStarted(Project.java:1902)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:367)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.executeTarget(ReactorTask.java:127)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.execute(ReactorTask.java:84)
[x:reactor] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[x:reactor] at org.apache.tools.ant.Task.perform(Task.java:364)
[x:reactor] at org.apache.tools.ant.Target.execute(Target.java:341)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[x:reactor] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[x:reactor] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[x:reactor] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[x:reactor] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[x:reactor] Caused by: net.dpml.configuration.ConfigurationException: No attribute named "uri" is associated with the configuration element "operation" at null:10:44
[x:reactor] at net.dpml.configuration.impl.DefaultConfiguration.getAttribute(DefaultConfiguration.java:344)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildOperation(DefaultStateMachine.java:989)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:894)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:899)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:76)
[x:reactor] ... 36 more
[x:reactor] net.dpml.metro.state.StateBuilderRuntimeException: Internal error while attempting to build state graph.
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:82)
[x:reactor] at net.dpml.metro.state.test.DefaultStateMachineTestCase.setUp(DefaultStateMachineTestCase.java:52)
[x:reactor] at junit.framework.TestCase.runBare(TestCase.java:125)
[x:reactor] at junit.framework.TestResult$1.protect(TestResult.java:106)
[x:reactor] at junit.framework.TestResult.runProtected(TestResult.java:124)
[x:reactor] at junit.framework.TestResult.run(TestResult.java:109)
[x:reactor] at junit.framework.TestCase.run(TestCase.java:118)
[x:reactor] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[x:reactor] at junit.framework.TestSuite.run(TestSuite.java:203)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:632)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.executeUnitTests(JUnitTestTask.java:336)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.execute(JUnitTestTask.java:203)
[x:reactor] at net.dpml.tools.process.JarProcess.targetStarted(JarProcess.java:124)
[x:reactor] at org.apache.tools.ant.Project.fireTargetStarted(Project.java:1902)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:367)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.executeTarget(ReactorTask.java:127)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.execute(ReactorTask.java:84)
[x:reactor] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[x:reactor] at org.apache.tools.ant.Task.perform(Task.java:364)
[x:reactor] at org.apache.tools.ant.Target.execute(Target.java:341)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[x:reactor] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[x:reactor] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[x:reactor] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[x:reactor] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[x:reactor] Caused by: net.dpml.configuration.ConfigurationException: No attribute named "uri" is associated with the configuration element "operation" at null:10:44
[x:reactor] at net.dpml.configuration.impl.DefaultConfiguration.getAttribute(DefaultConfiguration.java:344)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildOperation(DefaultStateMachine.java:989)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:894)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:899)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:76)
[x:reactor] ... 36 more
[x:reactor] net.dpml.metro.state.StateBuilderRuntimeException: Internal error while attempting to build state graph.
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:82)
[x:reactor] at net.dpml.metro.state.test.DefaultStateMachineTestCase.setUp(DefaultStateMachineTestCase.java:52)
[x:reactor] at junit.framework.TestCase.runBare(TestCase.java:125)
[x:reactor] at junit.framework.TestResult$1.protect(TestResult.java:106)
[x:reactor] at junit.framework.TestResult.runProtected(TestResult.java:124)
[x:reactor] at junit.framework.TestResult.run(TestResult.java:109)
[x:reactor] at junit.framework.TestCase.run(TestCase.java:118)
[x:reactor] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[x:reactor] at junit.framework.TestSuite.run(TestSuite.java:203)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:632)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.executeUnitTests(JUnitTestTask.java:336)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.execute(JUnitTestTask.java:203)
[x:reactor] at net.dpml.tools.process.JarProcess.targetStarted(JarProcess.java:124)
[x:reactor] at org.apache.tools.ant.Project.fireTargetStarted(Project.java:1902)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:367)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.executeTarget(ReactorTask.java:127)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.execute(ReactorTask.java:84)
[x:reactor] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[x:reactor] at org.apache.tools.ant.Task.perform(Task.java:364)
[x:reactor] at org.apache.tools.ant.Target.execute(Target.java:341)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[x:reactor] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[x:reactor] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[x:reactor] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[x:reactor] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[x:reactor] Caused by: net.dpml.configuration.ConfigurationException: No attribute named "uri" is associated with the configuration element "operation" at null:10:44
[x:reactor] at net.dpml.configuration.impl.DefaultConfiguration.getAttribute(DefaultConfiguration.java:344)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildOperation(DefaultStateMachine.java:989)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:894)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:899)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:76)
[x:reactor] ... 36 more
[x:reactor] net.dpml.metro.state.StateBuilderRuntimeException: Internal error while attempting to build state graph.
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:82)
[x:reactor] at net.dpml.metro.state.test.DefaultStateMachineTestCase.setUp(DefaultStateMachineTestCase.java:52)
[x:reactor] at junit.framework.TestCase.runBare(TestCase.java:125)
[x:reactor] at junit.framework.TestResult$1.protect(TestResult.java:106)
[x:reactor] at junit.framework.TestResult.runProtected(TestResult.java:124)
[x:reactor] at junit.framework.TestResult.run(TestResult.java:109)
[x:reactor] at junit.framework.TestCase.run(TestCase.java:118)
[x:reactor] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[x:reactor] at junit.framework.TestSuite.run(TestSuite.java:203)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:632)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.executeUnitTests(JUnitTestTask.java:336)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.execute(JUnitTestTask.java:203)
[x:reactor] at net.dpml.tools.process.JarProcess.targetStarted(JarProcess.java:124)
[x:reactor] at org.apache.tools.ant.Project.fireTargetStarted(Project.java:1902)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:367)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.executeTarget(ReactorTask.java:127)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.execute(ReactorTask.java:84)
[x:reactor] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[x:reactor] at org.apache.tools.ant.Task.perform(Task.java:364)
[x:reactor] at org.apache.tools.ant.Target.execute(Target.java:341)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[x:reactor] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[x:reactor] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[x:reactor] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[x:reactor] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[x:reactor] Caused by: net.dpml.configuration.ConfigurationException: No attribute named "uri" is associated with the configuration element "operation" at null:10:44
[x:reactor] at net.dpml.configuration.impl.DefaultConfiguration.getAttribute(DefaultConfiguration.java:344)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildOperation(DefaultStateMachine.java:989)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:894)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:899)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:76)
[x:reactor] ... 36 more
[x:reactor] net.dpml.metro.state.StateBuilderRuntimeException: Internal error while attempting to build state graph.
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:82)
[x:reactor] at net.dpml.metro.state.test.DefaultStateMachineTestCase.setUp(DefaultStateMachineTestCase.java:52)
[x:reactor] at junit.framework.TestCase.runBare(TestCase.java:125)
[x:reactor] at junit.framework.TestResult$1.protect(TestResult.java:106)
[x:reactor] at junit.framework.TestResult.runProtected(TestResult.java:124)
[x:reactor] at junit.framework.TestResult.run(TestResult.java:109)
[x:reactor] at junit.framework.TestCase.run(TestCase.java:118)
[x:reactor] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[x:reactor] at junit.framework.TestSuite.run(TestSuite.java:203)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:632)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.executeUnitTests(JUnitTestTask.java:336)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.execute(JUnitTestTask.java:203)
[x:reactor] at net.dpml.tools.process.JarProcess.targetStarted(JarProcess.java:124)
[x:reactor] at org.apache.tools.ant.Project.fireTargetStarted(Project.java:1902)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:367)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.executeTarget(ReactorTask.java:127)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.execute(ReactorTask.java:84)
[x:reactor] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[x:reactor] at org.apache.tools.ant.Task.perform(Task.java:364)
[x:reactor] at org.apache.tools.ant.Target.execute(Target.java:341)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[x:reactor] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[x:reactor] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[x:reactor] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[x:reactor] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[x:reactor] Caused by: net.dpml.configuration.ConfigurationException: No attribute named "uri" is associated with the configuration element "operation" at null:10:44
[x:reactor] at net.dpml.configuration.impl.DefaultConfiguration.getAttribute(DefaultConfiguration.java:344)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildOperation(DefaultStateMachine.java:989)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:894)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:899)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:76)
[x:reactor] ... 36 more
[x:reactor] net.dpml.metro.state.StateBuilderRuntimeException: Internal error while attempting to build state graph.
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:82)
[x:reactor] at net.dpml.metro.state.test.DefaultStateMachineTestCase.setUp(DefaultStateMachineTestCase.java:52)
[x:reactor] at junit.framework.TestCase.runBare(TestCase.java:125)
[x:reactor] at junit.framework.TestResult$1.protect(TestResult.java:106)
[x:reactor] at junit.framework.TestResult.runProtected(TestResult.java:124)
[x:reactor] at junit.framework.TestResult.run(TestResult.java:109)
[x:reactor] at junit.framework.TestCase.run(TestCase.java:118)
[x:reactor] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[x:reactor] at junit.framework.TestSuite.run(TestSuite.java:203)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434)
[x:reactor] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:632)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.executeUnitTests(JUnitTestTask.java:336)
[x:reactor] at net.dpml.tools.tasks.JUnitTestTask.execute(JUnitTestTask.java:203)
[x:reactor] at net.dpml.tools.process.JarProcess.targetStarted(JarProcess.java:124)
[x:reactor] at org.apache.tools.ant.Project.fireTargetStarted(Project.java:1902)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:367)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.executeTarget(ReactorTask.java:127)
[x:reactor] at net.dpml.tools.tasks.ReactorTask.execute(ReactorTask.java:84)
[x:reactor] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[x:reactor] at org.apache.tools.ant.Task.perform(Task.java:364)
[x:reactor] at org.apache.tools.ant.Target.execute(Target.java:341)
[x:reactor] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[x:reactor] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[x:reactor] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[x:reactor] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[x:reactor] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[x:reactor] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[x:reactor] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[x:reactor] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[x:reactor] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[x:reactor] Caused by: net.dpml.configuration.ConfigurationException: No attribute named "uri" is associated with the configuration element "operation" at null:10:44
[x:reactor] at net.dpml.configuration.impl.DefaultConfiguration.getAttribute(DefaultConfiguration.java:344)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildOperation(DefaultStateMachine.java:989)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:894)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.buildState(DefaultStateMachine.java:899)
[x:reactor] at net.dpml.metro.state.impl.DefaultStateMachine.load(DefaultStateMachine.java:76)
[x:reactor] ... 36 more
[junit] Tests run: 6, Failures: 6, Errors: 0, Time elapsed: 1,252 sec
[junit] Test net.dpml.metro.state.test.DefaultStateMachineTestCase FAILED
[junit] Running net.dpml.metro.state.test.DefaultStateTestCase
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0,05 sec
[junit] Running net.dpml.metro.state.test.DefaultTransitionTestCase
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0,03 sec
[junit] Running net.dpml.metro.state.test.DefaultTriggerTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,05 sec
[junit] Running net.dpml.state.test.DefaultOperationTestCase
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,03 sec
[junit] Running net.dpml.state.test.DefaultStateMachineTestCase
[x:reactor] # -------------------
[x:reactor] # state: []
[x:reactor] # trigger (1): [trigger:initialization]
[x:reactor] # -------------------
[x:reactor] # state: [available]
[x:reactor] # trigger (1): [trigger:termination]
[x:reactor] # operation (1): [audit]
[x:reactor] # -------------------
[x:reactor] # state: [started]
[x:reactor] # trigger (1): [trigger:termination]
[x:reactor] # transition (1): [stop] --> [../stopped]
[x:reactor] # -------------------
[x:reactor] # state: [stopped]
[x:reactor] # transition (1): [start] --> [../started]
[x:reactor] # -------------------
[x:reactor] # state: [terminated]
[x:reactor] # -------------------
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0,19 sec
[junit] Running net.dpml.state.test.DefaultStateTestCase
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0,061 sec
[junit] Running net.dpml.state.test.DefaultTransitionTestCase
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0,16 sec
[junit] Running net.dpml.state.test.DefaultTriggerTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,04 sec
BUILD FAILED
C:\development\dpml\Preferences\dpml\tools\templates\reactor.template:32: The following error occurred while executing this line:
One or more unit test failures occured.
Total time: 8 seconds
C:\development\dpml\main\metro\state>
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-12-15 16:34:58 CET
> To: 'Morten Haavaldsen' [mhaavald at online.no]
> Subject: RE: Developing components..
>
>
>
> > -----Original Message-----
> > From: Morten Haavaldsen [mailto:mhaavald at online.no]
> > Sent: Thursday, 15 December 2005 9:12 AM
> > To: Stephen McConnell
> > Subject: SV: Developing components..
> >
> > Hi,
> >
> > what are your thoughts about Spring in metro?
>
> It should be feasible to do. One would need to write a controller for
> Spring components (i.e. an implementation of
> net.dpml.metro.part.Controller). Add to this something to generate a part
> with Spring deployment information inside it and you have everything you
> need to incorporate a Spring component into another component or run a
> Spring component at top-level.
>
> > Spring really does not have any runtime platform, it is meant
> > to be embedded into servlets and containers and runtime environments.
> >
> > The thought about Spring, transit, metro/station is really appealing!
> > But, it may be that metro and Spring overlaps too much?
> >
> > WDYT?
>
> I figure controllers for Avalon 4.2 and Spring would be worth putting in
> place. The Avalon cace is interesting because it should be reasonably
> simple to do and would enable a higher level of validation of the internal
> logic in Metro concerning composition of mixed components.
>
> Thoughts?
>
> /Steve.
>
>
> > /Morten
> >
> >
> >
> >
> >
> > > From: Stephen McConnell [mcconnell at dpml.net]
> > > Sent: 2005-12-13 07:13:15 CET
> > > To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> > > Subject: RE: Developing components..
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: dev-dpml-bounces at lists.ibiblio.org
> > > > [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of Morten
> > > > Haavaldsen
> > > > Sent: Tuesday, 13 December 2005 12:18 AM
> > > > To: Morten Haavaldsen; Stephen McConnell; 'DPML Development'
> > > > Subject: Developing components..
> > > >
> > > > Hi,
> > > >
> > > >
> > > > which dpml libraries do I need to set up for basic development on
> > > > DPML and where do they reside?
> > >
> > > There are a number of different topics here:
> > >
> > > a) tooling dependencies
> > > b) component runtime dependencies
> > > - helpful utilities
> > > - service dependencies
> > > c) test dependencies
> > > d) deployment dependencies
> > >
> > > Tooling Dependencies
> > > --------------------
> > >
> > > The current implementation provides a project library that is build
> > > system independent. This is defined by the
> > > dpml/depot/dpml-library-common and dpml/depot/dpml-library-console
> > > packages (the library is API to project definitions and the
> > console is
> > > the command line tool to list project info and invokes
> > project builders).
> > >
> > > The default build system is based on Ant and is defined under the
> > > dpml/depot/dpml-tools-builder package. Separation of library from
> > > build implementation specifically addresses the earlier issues we
> > > encountered when attempting automation in other build systems like
> > > Eclipse, etc. Based on earlier activity in this area I'm confident
> > > that plugins could be created to read in project definitions which
> > > would automatically populate an IDEs internal project definitions.
> > >
> > > Component Runtime Dependencies
> > > ------------------------------
> > >
> > > Components do not require any runtime dependencies on DPML
> > content - i.e.
> > > there are no 'framework' structural dependencies. Instead the
> > > component uses the Context inner class to declare operational
> > > criteria. The operations declared within the component Context may
> > > imply introduce service dependencies on other APIs. Beyond
> > this there
> > > are some practical utilities such as a Logger class that
> > simply make
> > > like easier. The utilities are included in the dpml/util/* packages
> > > and are all self-contained in that they do not have
> > external dependencies.
> > >
> > > Utility package list:
> > >
> > > dpml/util/dpml-util-i18n I18N support.
> > > dpml/util/dpml-util-cli CommandLine support package.
> > > dpml/util/dpml-configuration-api Immutable XML
> > configuration data.
> > > dpml/util/dpml-parameters-api Immutable named/value pairs.
> > > dpml/util/dpml-activity-api Convenient lifestyle
> > interfaces.
> > > dpml/util/dpml-logging-api Simplified access to
> > JDK Logger.
> > >
> > >
> > > Test Dependencies
> > > -----------------
> > >
> > > The dpml/metro/dpml-metro-parts package contains a set of container
> > > APIs that can are used to handle component deployment.
> > These provide
> > > a convenient mechanisms to load and deploy components
> > without concern
> > > for the container implementation. The package dependencies include
> > > dpml/metro/dpml-state-api and dpml/transit/dpml-transit-main.
> > >
> > > An example of the usage of the parts API is shown in the
> > following page:
> > >
> > > http://www.dpml.net/metro/runtime/controller/index.html
> > >
> > > In a testcase you would typically replace the uri with
> > something like:
> > >
> > > final File dir = new File( System.getProperty(
> > "project.test.dir" ) );
> > > URI uri = new File( test, "test.part" ).toURI();
> > >
> > > Package Location
> > > ----------------
> > >
> > > Prior to a binary release you should reference packages from
> > > DPML_HOME/Shared/local directory. This is basically a local
> > > repository containing everything used and produced in the
> > build of the
> > > dpml tools, runtime and components. Please note that this
> > repository uses the 'classic'
> > > layout (i.e. [group]/[type]s/[name].[type]) and I just want
> > to mention
> > > that this may be changed to the 'modern' layout before release.
> > >
> > >
> > > > I am using JBuilder mostly but occasionally also eclispe which is
> > > > better for multiproject development.
> > > >
> > > > Perhaps eclipse is best:
> > > >
> > > > One project each for API, SPI and IMPL.
> > >
> > > Try and think of these in terms of PUBLIC, PROTECTED and
> > PRIVATE. The
> > > only reason for separation is when you want to share or
> > expose a part
> > > of a implementation such as an API - as such an API is typically
> > > classified as PUBLIC. You may want to expose additional APIs to
> > > internal components or management applications in which case these
> > > would be viewed as PROTECTED - and the rest is PRIVATE.
> > >
> > > When a separation is required it is best to define the
> > codebase in a
> > > separate project because this creates an identifiable jar
> > file which
> > > in-turn can be referenced when declaring a component part (an
> > > potentially tagged in terms of their PUBIC, PROTECTED or
> > PRIVATE role).
> > >
> > > On the other-hand, starting off with a single project for
> > everything
> > > makes life easy. After all, it's easy to breakout things into
> > > multiple projects later on.
> > >
> > > >
> > > > I just want to set up a test server basically with some
> > components
> > > > providing services to other components.
> > > >
> > > > One of them is to listen to a socket and receive incoming
> > requests.
> > >
> > > As a starting point take a look at the classes in the
> > main/metro/test
> > > package. In particular - src/main/net/dpml/test/app which
> > contains a
> > > Server and Listener interface, a DefaultServer and DefaultListener
> > > implementation, a Demo component and testcase in
> > > src/test/net/dpml/runtime/test/AppTestCase.java.
> > >
> > > All of the above gets tied together with the following instructions
> > > (from
> > > metro/test/build.xml):
> > >
> > >
> > > > > class="net.dpml.test.app.DefaultServer"
> > > lifestyle="singleton"/>
> > > > > class="net.dpml.test.app.DefaultListener"
> > > lifestyle="singleton"/>
> > > > > class="net.dpml.test.app.Demo"
> > > lifestyle="singleton">
> > >
> > > > > type="net.dpml.test.app.DefaultServer">
> > >
> > >
> > >
> > >
> > > > > type="net.dpml.test.app.DefaultListener">
> > >
> > > > uri="service:net.dpml.test.app.Server"/>
> > >
> > >
> > >
> > >
> > >
> > >
> > > > > dest="target/test/application.part" test="true"
> > > activation="true" collection="hard"/>
> > >
> > >
> > > Cheers, Steve.
> > >
> > >
> > > >
> > > > One nice thing to add to the component catalog would be
> > > > Webservices(like from Axis 1.2, or Axis2) and have POJO's easily
> > > > exposed....
> > > >
> > > >
> > > > Anyway, I start with a simple server config.
> > > >
> > > >
> > > >
> > > > /Morten
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > _______________________________________________
> > > dev-dpml mailing list
> > > dev-dpml at lists.ibiblio.org
> > > http://lists.ibiblio.org/mailman/listinfo/dev-dpml
> > >
> >
>
From mcconnell at dpml.net Sun Dec 18 15:53:19 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 19 Dec 2005 07:23:19 +1030
Subject: [NIX] scripts for nix available
Message-ID: <20051218205329.JTWO24868.omta05sl.mx.bigpond.com@julia>
Scripts for nix are now available - these include:
bootstrap -- Handles the bootstrap build of the
DPML system. Assumes that DPML_HOME
has been defined. On completion of
a successful bootstrap build the
general build can be executed using
the 'build' script. The bootstrap
scrip source can be found at
main/bootstrap
depot -- Core script that is invoked by the
build, metro, and station scripts.
Handles low-level concerns related to
setup of transit and the Depot console.
Script source is located in
main/depot/core/console/etc/bin
build -- Application handling the listing of
registered projects and ordered
building of projects (builds projects
by launching a builder plugin). The
build script source is located at
main/depot/library/console/etc/bin
metro -- Application that handles the deployment
of a Metro based application (normally
invoked by the Metro Station). The
script source can be found in
main/metro/exec/etc/bin
station -- Management centre that handles multiple
applications running under different
jvm. The script source can be found in
main/metro/station/console/etc/bin
Please note that while the W32 equivalent of the above is working nicely,
none of the above scripts have been tested on the *nix. In principal they
should work but if any problems occur please post a note to the list.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Sun Dec 18 15:59:37 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 19 Dec 2005 07:29:37 +1030
Subject: Building 782 fails with metr/state test...
In-Reply-To: <3750085.1134938171629.JavaMail.adm-moff@moffice3.nsc.no>
Message-ID: <20051218205946.NOMH18661.omta02sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Sent: Monday, 19 December 2005 7:06 AM
> To: Stephen McConnell; 'Morten Haavaldsen'; dev-dpml at lists.ibiblio.org
> Subject: Building 782 fails with metr/state test...
>
> Hi,
>
> Build fails inside metro/state.
> Hope the log below is helpful.
> [x:reactor] Caused by:
> net.dpml.configuration.ConfigurationException: No attribute
> named "uri" is associated with the configuration element
> "operation" at null:10:44
Try updating to 784, then:
$ bootstrap
$ build clean install
.. and I'll run a clean build here just to confirm.
/Steve.
From mcconnell at dpml.net Sun Dec 18 16:53:48 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 19 Dec 2005 08:23:48 +1030
Subject: Building 782 fails with metr/state test...
In-Reply-To: <20051218205946.NOMH18661.omta02sl.mx.bigpond.com@julia>
Message-ID: <20051218215358.GEIJ17345.omta04ps.mx.bigpond.com@julia>
> Try updating to 784, then:
>
> $ bootstrap
> $ build clean install
>
> .. and I'll run a clean build here just to confirm.
Just completed a clean build of HEAD without problem.
Based on the stack trace I suspect that all that is needed is a clean build
(descriptors related to component types were recently updated to include a
lifecycle state graph - which could be the underlying cause).
Cheers, Steve.
From mcconnell at dpml.net Sun Dec 18 21:00:58 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 19 Dec 2005 12:30:58 +1030
Subject: [STATION] Windows SCM Driver available
Message-ID: <20051219020107.SSWD3168.omta02ps.mx.bigpond.com@julia>
As of revision 788 and Windows SCM (Service Control Manager) for the Station
is available. The SCM is basically a Windows NT4 Service that establishes
the Station as a background process. Once installed and started
applications can be added, changed, started, stopped, etc. using the station
commandline tool.
Documentation concerning installation and service start-up are included
here:
http://www.dpml.net/metro/station/scm.html
The implementation is based a binary version of the Java Service Wrapper.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mhaavald at online.no Mon Dec 19 19:49:53 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Tue, 20 Dec 2005 01:49:53 +0100 (CET)
Subject: [STATION] demo still active after remove....
In-Reply-To: <20051219020107.SSWD3168.omta02ps.mx.bigpond.com@julia>
Message-ID: <2082210.1135039794121.JavaMail.adm-moff@moffice11.nsc.no>
Hi,
just tested station.
Added demo
Removed demo
But demo still works even after a remove.
Perhaps it is supposed to?
Is it so that the app is removed from station control but still active.
See log below:
C:\development\dpml\main\planet\http\demo>station remove demo
station remove demo
[2300 ] [INFO ] (depot.station): removed application [demo]
C:\development\dpml\main\planet\http\demo>station info
station info
Server is operational.
Port: 1099
Store: local:xml:dpml/station/registry
Basedir: C:\development\dpml\main\planet\http\demo
Codebase: artifact:jar:dpml/metro/dpml-station-server#SNAPSHOT
Profile count: 0
If will get right on to looking into the DefaultServer under test which you mentioned.
Question: Do you use eclipse or IntelliJ ?
I am about to configure the devenv, and perhaps best to try to have same as you/dpml developers in case of questions regaring libs etc?
Or doesn't it matter perhaps?
Last question: Say I have a local jar which my component relies on. How do I add it to the repository etc?
(I.e. the jar comes from an external e.g. utilities project.).
I will have a go at the test server...
PS!
Close to x-mas so I don't expect answers right away...
Regardless, I am impressed with what seems to be included in dpml now included the latest scm....
I hope to be able to contribute more than just asking questions!!!
I have some free time in just after x-mas eve...
Anyway, merry x-mas!!
DS!
/Morten
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-12-19 03:00:58 CET
> To: 'DPML Development' [dev-dpml at lists.ibiblio.org]
> Subject: [STATION] Windows SCM Driver available
>
>
>
> As of revision 788 and Windows SCM (Service Control Manager) for the Station
> is available. The SCM is basically a Windows NT4 Service that establishes
> the Station as a background process. Once installed and started
> applications can be added, changed, started, stopped, etc. using the station
> commandline tool.
>
> Documentation concerning installation and service start-up are included
> here:
>
> http://www.dpml.net/metro/station/scm.html
>
> The implementation is based a binary version of the Java Service Wrapper.
>
> Cheers, Steve.
>
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
>
From mcconnell at dpml.net Tue Dec 20 00:11:54 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Tue, 20 Dec 2005 15:41:54 +1030
Subject: [STATION] demo still active after remove....
In-Reply-To: <2082210.1135039794121.JavaMail.adm-moff@moffice11.nsc.no>
Message-ID: <20051220051205.RRPE10380.omta04sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Sent: Tuesday, 20 December 2005 11:20 AM
> To: Stephen McConnell; 'DPML Development'
> Subject: [STATION] demo still active after remove....
>
> Hi,
>
> just tested station.
>
> Added demo
> Removed demo
>
> But demo still works even after a remove.
> Perhaps it is supposed to?
No - the console code should be doing an auto-shutdown of the application.
This is fixed under rev 793.
>
> If will get right on to looking into the DefaultServer under
> test which you mentioned.
>
> Question: Do you use eclipse or IntelliJ ?
Neither.
Although that could change.
> I am about to configure the devenv, and perhaps best to try
> to have same as you/dpml developers in case of questions
> regaring libs etc?
>
> Or doesn't it matter perhaps?
If your building with ant its just automatic because the build.exe is
grabbing all of the info about the project dependencies from the common
library. If your building with an IDE then we should focus on a custom
plugin for the IDE that hooks into the library and auto-configures the IDE's
project model.
> Last question: Say I have a local jar which my component
> relies on. How do I add it to the repository etc?
> (I.e. the jar comes from an external e.g. utilities project.).
Easiest way is to create a local repository and add the jar to that
repository. The following command adds a new remote host to your Transit
configuration under the key 'demo' with a url
'file:${dpml.data}/repository/demo' (you could provide any url) and a
priority of 60.
$ transit add host demo -url file:${dpml.data}/repository/demo -priority 60
Setting the priority to 60 means that your local repository will be selected
before consulting remote repositories (which will keep things snappy). You
can see the result of adding the host using the transit list command:
$ transit info
More info about host addition is available here:
http://www.dpml.net/transit/cli/add/host.html
After that just add your files to the new repository using the convention
for the repository layout (the default layout is 'classic' which is what is
used in the cache and internal local repository) which is basically
[group]/[type]s/[name]-[version].[type].
More info of host layouts is available here:
http://www.dpml.net/transit/services/layouts.html
>
>
> I will have a go at the test server...
>
> PS!
> Close to x-mas so I don't expect answers right away...
> Regardless, I am impressed with what seems to be included in
> dpml now included the latest scm....
>
> I hope to be able to contribute more than just asking questions!!!
> I have some free time in just after x-mas eve...
>
> Anyway, merry x-mas!!
Merry Christmas to you too!
Cheers, Steve.
From mcconnell at dpml.net Thu Dec 22 17:24:18 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Fri, 23 Dec 2005 08:54:18 +1030
Subject: merging platform differences
Message-ID: <20051222222423.XFCC14751.omta05ps.mx.bigpond.com@julia>
I've been working on the creation of the binary distribution and I've
noticed that we have lots of places where the different file structures used
between the w32 install and a *nix install complicate things. This occurs
in the install documentation, setup examples, scripts to create binaries,
etc. Rather than duplicate logic for the different environments I'm going
to update Transit (and the related bootstrap builds) to use a single unified
approach.
This will significantly simply the creation of the binary distribution but
the SVN content may go though some non-buildable stages in the next 24 hours
(rev 811 is good).
I'll post a note as soon as I stabilize the build.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Fri Dec 23 23:07:22 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Sat, 24 Dec 2005 14:37:22 +1030
Subject: merging platform differences
In-Reply-To: <20051222222423.XFCC14751.omta05ps.mx.bigpond.com@julia>
Message-ID: <20051224040729.JDQL16720.omta01sl.mx.bigpond.com@julia>
All done.
Win32 users should note that future builds will place
executable resource into %DPML_HOME%\share\bin - as such you will
need to update you path environment variable. Also if you have
the Station installed as an NT service you will need to uninstall
and re-install the station (just double click on the respective bat
files).
/Steve.
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Stephen McConnell
> Sent: Friday, 23 December 2005 8:54 AM
> To: 'DPML Development'
> Subject: merging platform differences
>
>
>
> I've been working on the creation of the binary distribution
> and I've noticed that we have lots of places where the
> different file structures used between the w32 install and a
> *nix install complicate things. This occurs in the install
> documentation, setup examples, scripts to create binaries,
> etc. Rather than duplicate logic for the different
> environments I'm going to update Transit (and the related
> bootstrap builds) to use a single unified approach.
>
> This will significantly simply the creation of the binary
> distribution but the SVN content may go though some
> non-buildable stages in the next 24 hours (rev 811 is good).
>
> I'll post a note as soon as I stabilize the build.
>
> Cheers, Steve.
>
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
From mcconnell at dpml.net Sat Dec 24 03:11:11 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Sat, 24 Dec 2005 18:41:11 +1030
Subject: [METRO] binary distribution 20051224 available
Message-ID: <20051224081118.MPI15112.omta03ps.mx.bigpond.com@julia>
A binary distribution of Transit, Depot, and Metro has just been uploaded:
http://www.dpml.net/about/setup/index.html
Linux and Windows distributions are included.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Mon Dec 26 04:38:33 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 26 Dec 2005 20:08:33 +1030
Subject: [20051224] filter task is throwing an exception dure to unresolved
defaults
Message-ID: <20051226093844.YOEL24868.omta05sl.mx.bigpond.com@julia>
Found an issue while working with the 20051224 distribution concerning the
reoslution of a default value for the project publisher. The following
error occurs when buikld a project withough any prior properties:
init:
[x:init] project:acme/acme-client
[x:filter] Processing feature: project.publisher.name
BUILD FAILED
C:\osm\prefs\dpml\tools\templates\standard.template:31:
Unsupported feature [project.publisher.name].
/Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Mon Dec 26 04:54:28 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 26 Dec 2005 20:24:28 +1030
Subject: [20051224] filter task is throwing an exception dure to
unresolveddefaults
In-Reply-To: <20051226093844.YOEL24868.omta05sl.mx.bigpond.com@julia>
Message-ID: <20051226095438.BOAZ18661.omta02sl.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Stephen McConnell
> Sent: Monday, 26 December 2005 8:09 PM
> To: 'DPML Development'
> Subject: [20051224] filter task is throwing an exception dure
> to unresolveddefaults
>
>
> Found an issue while working with the 20051224 distribution
> concerning the reoslution of a default value for the project
> publisher. The following error occurs when buikld a project
> withough any prior properties:
>
> init:
> [x:init] project:acme/acme-client
> [x:filter] Processing feature: project.publisher.name
>
> BUILD FAILED
> C:\osm\prefs\dpml\tools\templates\standard.template:31:
> Unsupported feature [project.publisher.name].
>
> /Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
From mcconnell at dpml.net Mon Dec 26 04:55:46 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 26 Dec 2005 20:25:46 +1030
Subject: [20051224] filter task is throwing an exception dure to
unresolveddefaults
In-Reply-To: <20051226093844.YOEL24868.omta05sl.mx.bigpond.com@julia>
Message-ID: <20051226095555.YSCI24868.omta05sl.mx.bigpond.com@julia>
Resolved in rev 819.
/Steve.
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Stephen McConnell
> Sent: Monday, 26 December 2005 8:09 PM
> To: 'DPML Development'
> Subject: [20051224] filter task is throwing an exception dure
> to unresolveddefaults
>
>
> Found an issue while working with the 20051224 distribution
> concerning the reoslution of a default value for the project
> publisher. The following error occurs when buikld a project
> withough any prior properties:
>
> init:
> [x:init] project:acme/acme-client
> [x:filter] Processing feature: project.publisher.name
>
> BUILD FAILED
> C:\osm\prefs\dpml\tools\templates\standard.template:31:
> Unsupported feature [project.publisher.name].
>
> /Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
From mcconnell at dpml.net Mon Dec 26 05:46:01 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Mon, 26 Dec 2005 21:16:01 +1030
Subject: [METRO] added part content handler
Message-ID: <20051226104611.JSKW16720.omta01sl.mx.bigpond.com@julia>
During an intensive cleanup of the codebase during the past month
the functionaity dealing with a ContentHandler for the part datatype
was commented out. I've just added a new sub-project that provides
this (rev 820) as a descrite plugin. Tutorial docs will be updated
to reflect the same shortly.
/Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Tue Dec 27 14:17:25 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Wed, 28 Dec 2005 05:47:25 +1030
Subject: [METRO] binary update 20051228
Message-ID: <20051227191727.QKTJ24868.omta05sl.mx.bigpond.com@julia>
A updated binary has been posted to the DPML - build 20051228.
This is a minor update that includes resolution of the following issues:
1. resolution of the bug concerning a non-declared project publisher
2. elimination of all outstanding checkstyle format errors
3. addition of missing build reports to the binary distribution
4. addition of a content handler plugin for network resolvable parts
5. minor javadoc corrections
The download page includes links to the W32 and Unix distributions.
http://www.dpml.net/about/setup/index.html
Tutorials concerning Transit and Depot have been updated:
http://www.osm.net/training/index.html
Tutorial concerning Metro and the Station are in-progress.
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mhaavald at online.no Thu Dec 29 08:26:22 2005
From: mhaavald at online.no (Morten Haavaldsen)
Date: Thu, 29 Dec 2005 14:26:22 +0100 (CET)
Subject: SV: [METRO] binary distribution 20051224 available
In-Reply-To: <20051224081118.MPI15112.omta03ps.mx.bigpond.com@julia>
Message-ID: <11411701.1135862782348.JavaMail.adm-moff@moffice10.nsc.no>
Hi,
I managed to read through the web yesterday and "by accident" the tutorials surfaced under /training.
Regardless, I read the info on metro, transit , depot. It is very interesting! But, as it turns out, it may be that it is an uphill battle what you try to achiece. I.e. the documentation is very much "design doc". And on how the internals of transit, metro etc is made.
Documenting actual design is very hard to do in a few lines on the web. Usually you need more pages to accomplish showing static and dynamic views of object models.
Hence perhaps at a later stage some doc may be refactored into a "DPML developers area".
What I found helpful was to read through the planet/http area.
Especially enlightening how the Jetty is designed into metro.
Looked at the build file and saw how types had type and lastly Demo component got the defined type.
This tells me how to do a server up of components.
So, documentation may be more around the actual usage of metro, transit, and not on the internals.
The SPI, API and IMPL is as you say public ,protected and private for a component.
I will work through the training on the Widget example.
What I am looking for now is how a component uses the a service as offered by another component through the SPI. I.e. how is it "wired" together.
I am sure this is in the training pages which I will get to.
Looking at the http server I must say DPML is heading for something which is missing for the java community and that is a solid runtime framework.
When I read through the doc I read it from a developers viewpoint and I am eager to use it. An aspect is the management of a solution of servers. I.a. the Station API. It is perhaps possible to have servers hooked into a management solution.
I.e. a "blue print" architecture could be a set of servers constituting a solution. One of the servers is a Management Server. It is interesting what the Station and the Station API brings to the table ragarding monitoring, start, restart etc of servers.
The Demo has e.g.
How are thes operations called by other components or another program, e.g. hooked into the management server.
Also, the "blueprint" architecture has in my mind a "naming service".
I.e. not the ORB NS, but an "internal" naming service.
I.e. A component uses another service through a logical name.
A resolver resolves the address using a naming service.
What I have in mind is to have an dpml based server being a naming server.
Services register at the naming server.
Components using the service uses the logical name and the resolver resolves the actual network address.
This idea comes from my experience with Spring.
In Spring you wire beans together. This is neat, BUT, is ties components.
On the drawing board based on Spring is to make an Service exporter(like RMI exporter) which registeres the service in a Naming Service Server.
And also make a RMI Proxy which uses this naming service for resolving the location of the service.
Location transparency is important in distrubuted solutions.
Having this also enables "failover", "clustering", "load balancing" schemas.
I am not sure how to accomplish all this in Metro but I know it should be possible from what I have seen so far.
Perhaps I should make for Metro as exist for Spring an "exporter" and "resolver" which enables POJO's in separate servers to seamlessly call eachother.
The trend is more and more to have "non invasive" frameworks, or "POJO Frameworks"....to some extent one will always "see" the framework though...
Regardless, my journey with DPML should continue now working through the Widget example.
Also I will look into how to defined a new project using module, how to set up my own local library etc...
I, and others, should contribute to DPML with e.g. components like "HTTP Service" based on e.g. apache HTTP Client. Also components for publishing to JMS queues using connection pooling etc...
Perhaps also integrating ActiveMQ....
Many possibilities....
I guess what I am striving for is to separate the "dpml design internals" from the "dpml component" design guidelines *S*
Hope to get there and to be more useful than just to "review" what you are making!
BTW, I set up a project in JBuilder and had to add a lot of jars from metro. Also some "internal" jars.... Not quite clear which jars I should add.
I use the JBuilder to develop and magic/build to build it... But I need "code completion" etc to be able to be productive...
What does your development environment look like?
What IDE do you use and which libraries do you include developing components.
BR,
/Morten
> From: Stephen McConnell [mcconnell at dpml.net]
> Sent: 2005-12-24 09:11:11 CET
> To: 'DPML Development' [dev-dpml at lists.ibiblio.org], 'DPML Support' [support-dpml at lists.ibiblio.org]
> Subject: [METRO] binary distribution 20051224 available
>
>
>
> A binary distribution of Transit, Depot, and Metro has just been uploaded:
>
> http://www.dpml.net/about/setup/index.html
>
> Linux and Windows distributions are included.
>
> Cheers, Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
>
From mcconnell at dpml.net Thu Dec 29 14:58:40 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Fri, 30 Dec 2005 06:28:40 +1030
Subject: [METRO] binary distribution 20051224 available
In-Reply-To: <11411701.1135862782348.JavaMail.adm-moff@moffice10.nsc.no>
Message-ID: <20051229195844.SFAD3168.omta02ps.mx.bigpond.com@julia>
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Morten Haavaldsen
> Sent: Thursday, 29 December 2005 11:56 PM
> To: Stephen McConnell; 'DPML Development'; 'DPML Support'
> Subject: SV: [METRO] binary distribution 20051224 available
>
> Hi,
>
> I managed to read through the web yesterday and "by accident"
> the tutorials surfaced under /training.
I should mention that I have not been 'pushing' the tutorial content too
much just yet as the details concerning Transit and Depot have only just
been completed and the content concerning Metro (i.e. components) and
Station (application clusters) is only in the planning phase.
> Regardless, I read the info on metro, transit , depot. It is
> very interesting! But, as it turns out, it may be that it is
> an uphill battle what you try to achiece. I.e. the
> documentation is very much "design doc". And on how the
> internals of transit, metro etc is made.
The separation of documentation under DPML versus OSM is intentional. The
aim is to establish the developer information about the DPML Platform under
www.dpml.net whereas the usage and best practice material is aimed at
www.osm.net. The separation is to some extent a effort to make the
distinction between describing the mechanics of the implementation from
documentation dealing with the aims, principals, and vision (or as I like to
think of it 'the details versus the bigger picture').
> Documenting actual design is very hard to do in a few lines
> on the web. Usually you need more pages to accomplish showing
> static and dynamic views of object models.
> Hence perhaps at a later stage some doc may be refactored
> into a "DPML developers area".
As a general indication of intent:
www.dpml.net
- description of core products
- formal specification of tools (e.g. transit, build, depot,
metro and station cli handlers)
- formal description of sub-systems (Transit, Metro, Depot)
- developer documentation (with a priority on being technical
correct)
- ultimately providing the long-term legal and organizational
framework
www.osm.net
- looking at the broader picture of:
* the science of component-based-development
* the application of component-based-development
- guides to applying COP (and using the DPML SDK as an
example, and in doing so - critically evaluating the
platform)
- providing professional services backing the DPML
As to immediate content - well, there is still a lot to do and I believe
that there is a lot of room for improvement (even my mother-in-law has
complained about the complexity of some of the text on the DPML).
> What I found helpful was to read through the planet/http area.
> Especially enlightening how the Jetty is designed into metro.
> Looked at the build file and saw how types had type and
> lastly Demo component got the defined type.
> This tells me how to do a server up of components.
I think the Jetty example is good in respect to the demonstration of
adoption of a product into a declarative component model - however - I have
a couple of reservations. Firstly, the real meat of the HTTP package (the
planet/http/impl project) is largely oriented around the 'old-world' notion
of components - in effect 'flat-land'. By 'flat-land' I mean that none of
the components in the impl package leverage the notion of parts. In the demo
package we see the usage of part of component as the means to construction
of a new component - however, I think that some more 'thinking' is needed
concerning part structures within the impl package. One of the difficulties
here is dealing with the very notion of differentiating between 'service
dependencies' (declaring in a context object) and parts (declared
intrinsically within a component type).
It's a little like looking at a juggler juggling apples and recognizing that
we are dealing with (a) a person, (b) three apples, and in doing this,
recognizing that the brain, heart, liver, kidneys, and supporting systems
are a part of the juggler and not part of the picture of the juggler
juggling. While the net.dpml.part package is doing a good job of
identifying and separating these distinctions, I think the 'concepts' are
not sufficiently clear just yet. However, my own aim is to use the demo
package to explore this area further and hopefully tease out the final
details and establish clean conceptual separation of concerns.
> So, documentation may be more around the actual usage of
> metro, transit, and not on the internals.
This is the aim of the OSM content (also hosted by BelioOS and Ibiblio).
> The SPI, API and IMPL is as you say public ,protected and
> private for a component.
> I will work through the training on the Widget example.
I've been talking to a friends about putting up a sample application dealing
with a simple but real work pond application - an application that takes
information about a garden pond (hole in the ground of a specific volume),
the global environment (sunshine, temperature, etc.), the pond environment
(fish, etc.), and from this deals with the engineering view - pumps, flows,
filtering, maps to a commercial view (product selection and pricing), ties
in suppler views (product trends, inventory, ..) - and linking all of this
into the http impl package as a dynamically deployed and remotely manageable
application.
I figure this would be useful!
> What I am looking for now is how a component uses the a
> service as offered by another component through the SPI. I.e.
> how is it "wired" together.
Just a couple of comments:
1. a component receives access to a 'service' by declaring the dependency
within its Context definition
2. the separation of API versus SPI (or PUBLIC versus PROTECTED) is much
more related to the subject of a component implementation and the
selection of which classloader to use as a parent when creating a
subsystem - it really does not come into play when dealing with runtime
service access - but I know this statement is to some extent 'fuzzy'
so don't hesitate to post a separate message raising this subject
(perhaps
using the application example in the test project as a case study)
3. the wiring of a provider to a consumer is dealt with by the container.
The
container has available information about a consumer component's
dependencies and a provider component capabilities (service
production).
The container matches providers with consumers using directives
typically
something like a "service:org.acme.Widget" type of statement (which
tells
the container to hunt for a provider of the service in the immediate or
higher component and bind the provider to the consumer).
> I am sure this is in the training pages which I will get to.
Not really.
The training pages on the component topic are in the pipeline - much better
to look at the testcases in the main/metro/test project (in particular take
a look at the build file and the related component implementations).
> Looking at the http server I must say DPML is heading for
> something which is missing for the java community and that is
> a solid runtime framework.
>
> When I read through the doc I read it from a developers
> viewpoint and I am eager to use it. An aspect is the
> management of a solution of servers. I.a. the Station API. It
> is perhaps possible to have servers hooked into a management solution.
Yes.
The Station API is a part of a bigger picture.
In effect the Station represents a single point of management of a machine
(where machine means a physical cpu). The Station provides support for the
management of multiple machine level processes and the intention is to
provide a framework for the exporting of the station API to an external
manager (i.e. a manager of n stations). For example - a company managing
the deployment of 37,300 installations (remote machines), aggregating
information from all of these machines, managing these machines in whole or
individually.
> I.e. a "blue print" architecture could be a set of servers
> constituting a solution. One of the servers is a Management
> Server. It is interesting what the Station and the Station
> API brings to the table ragarding monitoring, start, restart
> etc of servers.
>
> The Demo has e.g.
>
>
>
>
> How are thes operations called by other components or another
> program, e.g. hooked into the management server.
After starting up the station and starting the demo application, take a look
at the control command:
http://www.dpml.net/metro/station/cli/control.html
> Also, the "blueprint" architecture has in my mind a "naming service".
> I.e. not the ORB NS, but an "internal" naming service.
> I.e. A component uses another service through a logical name.
> A resolver resolves the address using a naming service.
>
> What I have in mind is to have an dpml based server being a
> naming server. Services register at the naming server.
>
> Components using the service uses the logical name and the
> resolver resolves the actual network address.
If I understand correctly what you are describing is the distinction between
something that locates a service as opposed to something that identifies a
service. In some respects this parallels the Transit separation of resource
identity for resource locality. We have service locators such as
"registry:/demo/my-service" (which locates a RMI mounted remote service),
however, that's not the same as saying
"service:[some-service-oriented-naming-scheme]".
While working with the OMG Naming Service (and in the context of the work of
Brokerage with the OMG's EC Task Force), I came up with some principals
concerning what could be called a distributed naming service (but more
correctly a service referral framework). The following line includes
details about the overall model (validated in prototype form):
http://www.dpml.net/about/notepad/discovery/index.html
> This idea comes from my experience with Spring.
> In Spring you wire beans together. This is neat, BUT, is ties
> components.
> On the drawing board based on Spring is to make an Service
> exporter(like RMI exporter) which registeres the service in a
> Naming Service Server.
While thinking in this area - some thing to keep in mind or be aware of:
The registry protocol handler in Transit
http://www.dpml.net/transit/technical/registry.html
(which is basically nothing more that convenient RMI name lookup)
And secondly (bugger - no docs available on the site).
In effect there is a layer inside the component model that allows
the declaration of 'service:[interface-classname]' and this could
be a relevant hook into some of the things your thinking about.
(check into the ComponentController class for more details).
The is also the issue that we cannot presume that a component
implementation is remotable (but we can presume that its management
view is).
> And also make a RMI Proxy which uses this naming service for
> resolving the location of the service.
> Location transparency is important in distrubuted solutions.
> Having this also enables "failover", "clustering", "load
> balancing" schemas.
>
> I am not sure how to accomplish all this in Metro but I know
> it should be possible from what I have seen so far.
>
> Perhaps I should make for Metro as exist for Spring an
> "exporter" and "resolver" which enables POJO's in separate
> servers to seamlessly call eachother.
>
> The trend is more and more to have "non invasive" frameworks,
> or "POJO Frameworks"....to some extent one will always "see"
> the framework though...
I'm of the opinion that a POJO is the IT equivalent of a body without a
soul. It's an object devoid of semantics and IMO a backlash from the strict
framework models. The thing is that happing a soul does not necessarily
mean depending on a particular API - but this is a question of degree. If I
write a component that leverages the Part API I'm gaining substantial value
with respect to long-term fine-grain management but I've left the agnostic
world of POJO. In my mind there is a lot you can do with frameless
components in flatland - and flatland does not come close to addressing
multi-dimensional problems.
I.e. POJOs are like nuts and bolts - useful - but your not going to build a
city with just nuts and bolts.
>
> Regardless, my journey with DPML should continue now working
> through the Widget example.
> Also I will look into how to defined a new project using
> module, how to set up my own local library etc...
> I, and others, should contribute to DPML with e.g. components
> like "HTTP Service" based on e.g. apache HTTP Client. Also
> components for publishing to JMS queues using connection
> pooling etc...
> Perhaps also integrating ActiveMQ....
>
> Many possibilities....
>
> I guess what I am striving for is to separate the "dpml
> design internals" from the "dpml component" design guidelines *S*
Guideline --> OSM
Internals --> DPML
>
> Hope to get there and to be more useful than just to "review"
> what you are making!
:-)
> BTW, I set up a project in JBuilder and had to add a lot of
> jars from metro. Also some "internal" jars.... Not quite
> clear which jars I should add.
If you want to get info about the dependencies of the class you using, just
list the project in question. For example if you want to use the part api
and your wondering what the dependencies are:
$ build -l -s dpml/metro/dpml-part-api
The above command will produce the following (-l) listing of the (-s)
select[ion].
Listing project: dpml/metro/dpml-part-api
project:dpml/metro/dpml-part-api
version: SNAPSHOT
basedir: C:\dev\dpml\main\metro\part\api
types: (1)
jar
runtime providers: (2)
project:dpml/metro/dpml-state-api
resource:dpml/transit/dpml-transit-main
test providers: (6)
resource:ant/ant-launcher
resource:ant/ant-trax
resource:ant/ant-xslp
resource:ant/ant
resource:junit/junit
resource:ant/ant-junit
You can see from the above command that the dpml-part-api project has two
runtime dependencies (dpml-state-api and dpml-transit-main). Whenever you
list a project you will see the fully expanded dependencies implied by the
project.
> I use the JBuilder to develop and magic/build to build it...
> But I need "code completion" etc to be able to be productive...
>
> What does your development environment look like?
> What IDE do you use and which libraries do you include
> developing components.
Your going to be very disappointed - I don't use an IDE.
My development environment consists of build.exe and Notepad2 version
1.0.12.
However - I figure that the usual problem of setting up a project (within an
IDE) can be handled via a plugin that reads information from the common
project library. Everything is there to fully populate a project definition
- it's no different to the way that the Depot builder is doing the setup of
a Ant project and the related context object.
Cheers Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
>
> BR,
> /Morten
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> > From: Stephen McConnell [mcconnell at dpml.net]
> > Sent: 2005-12-24 09:11:11 CET
> > To: 'DPML Development' [dev-dpml at lists.ibiblio.org], 'DPML Support'
> > [support-dpml at lists.ibiblio.org]
> > Subject: [METRO] binary distribution 20051224 available
> >
> >
> >
> > A binary distribution of Transit, Depot, and Metro has just
> been uploaded:
> >
> > http://www.dpml.net/about/setup/index.html
> >
> > Linux and Windows distributions are included.
> >
> > Cheers, Steve.
> >
> > --------------------------
> > Stephen McConnell
> > mailto:mcconnell at dpml.net
> > http://www.dpml.net
> >
> > _______________________________________________
> > dev-dpml mailing list
> > dev-dpml at lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/dev-dpml
> >
>
From mcconnell at dpml.net Fri Dec 30 22:17:39 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Sat, 31 Dec 2005 13:47:39 +1030
Subject: [METRO] milestone 20051231
Message-ID: <20051231031747.MXXI3168.omta02ps.mx.bigpond.com@julia>
The milestone build 20051231 is available online. It includes
resolution of checkstyle plugin loading and rule selection along
with earlier issues reporting following the 20051224 build.
http://www.dpml.net/about/setup/index.html
/Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net
From mcconnell at dpml.net Sat Dec 31 00:31:54 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Sat, 31 Dec 2005 16:01:54 +1030
Subject: [METRO] milestone 20051231
In-Reply-To: <20051231031747.MXXI3168.omta02ps.mx.bigpond.com@julia>
Message-ID: <20051231053203.RENA15112.omta03ps.mx.bigpond.com@julia>
While running up an installation on a virgin machine I've encountered a
couple of problems.
1. lib directory is not included in the binary distribution
2. links are not included in the local repository packaged with the binary
The lib directory issue is already resolved in svn but the links issue will
take a bit more work. Basically I'm going to update the replicate task an
in the process add support for the declaration of the target layout.
/Steve.
> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org] On Behalf Of
> Stephen McConnell
> Sent: Saturday, 31 December 2005 1:48 PM
> To: 'DPML Support'; 'DPML Development'
> Subject: [METRO] milestone 20051231
>
>
> The milestone build 20051231 is available online. It
> includes resolution of checkstyle plugin loading and rule
> selection along with earlier issues reporting following the
> 20051224 build.
>
> http://www.dpml.net/about/setup/index.html
>
> /Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml
From mcconnell at dpml.net Sat Dec 31 22:54:11 2005
From: mcconnell at dpml.net (Stephen McConnell)
Date: Sun, 1 Jan 2006 14:24:11 +1030
Subject: Replicate Task, the Modern Layout and the local system repository.
Message-ID: <20060101035420.MQVD18661.omta02sl.mx.bigpond.com@julia>
Updates to the replicate task have been completed resulting in a much
improved process of binary creation. In effect the replicate task now fully
supports the replication of link artifacts and more importantly, the task
takes a layout name as one of the possible argument. This means that you
can use to construct repository data for any of the standard
layouts ('classic', 'modern' or 'eclipse').
With this in-place I've updated Transit to default to the 'modern' layout
within the local system repository and everything is working nicely.
Docs on the replicate task are also available here:
http://www.dpml.net/depot/tasks/replicate.html
Cheers, Steve.
--------------------------
Stephen McConnell
mailto:mcconnell at dpml.net
http://www.dpml.net