I have updated the DAS distributions to work as proposed under revision
#539815, this should be aligned with the SCA and SDO proposed distributions,
the only difference being that, the samples on the binary distribution have
source code attached to the binary distributions, instead of having the
a
Well, I thought more about this subject, and I think I'm OK with the
following distributions :
source : all sources for implementation and samples
binary : implementation binaries and dependencies + javadoc + samples
binaries
\lib -> api implementation and dependency
\doc -> javadocs
\samp
Comments in-line
On 5/18/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
Switching this to tuscany-users to solicit user community input.
I think I need some clarification of what it means to ship the samples
with the binary distribution. One of the key things a user is going to
want to do is to
On 5/18/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
Perhaps the binary distributions should include
- the sample source
- binary samples ready to run
- a generic description of how to build the samples
- a maven pom file that rebuilds the samples, along with instruction
son how to get maven go
Switching this to tuscany-users to solicit user community input.
I think I need some clarification of what it means to ship the samples
with the binary distribution. One of the key things a user is going to
want to do is to modify and rebuild the samples, so how do we make
that easy for them? It
In this week DAS release IRC chat [1], Ant had a proposal to change the DAS
distributed artifacts.
We currently have the following distributions :
- Source : have das source implementation (M2)
- BInary : have DAS binaries and all necessary dependencies (M2)
- Sample : sample application
