See responses inline.
Simon
Raymond Feng wrote:
Hi,
I was building against the tagged svn source tree. Please see my
comments inline.
This should work and produce the same output as building from the
distribution.
Thanks,
Raymond
/________________________________________________________________
Raymond Feng
[email protected] <mailto:[email protected]>
/Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
/
________________________________________________________________/
On May 23, 2010, at 7:38 AM, Simon Nash wrote:
I've started a new thread for this problem so as not to pollute the
vote thread.
Were you by any chance running "mvn clean install" from the
binaries/bundle
directory? This would produce the results you are describing. There's no
reason to do this, as the "binaries" module and all its submodules are
built
automatically when you build the top-level travelsample directory.
All output
from the "binaries" module and its submodules goes into the
binaries/target
directory, not into the target directories on the submodules.
Yes, I did. Nothing except an empty archive-tmp folder was produced from
the command.
>
This is because the output from binaries/bundle goes into the
binaries/target directory, not the binaries/bundle/target directory.
Do you see any output there?
I suspect that the copy stage failed because MacOS doesn't
like the target as "target/.".
Where is this reference to "target/."?
I'm still not sure why you're running a separate build for binaries/bundle.
When you build the top-level travel sample directory, the binaries and
binaries/bundle directories are built as part of this and they produce
output in binaries/target as described in the README.
To clarify, there is no binary distribution of the travel sample. There
is a single distribution which can be built from the "distribution"
module.
Building the "binaries" module produces an executable binary package for
the travel sample as a subtree within binaries/target (not a zip or gz).
The "binaries" module and its submodules are built automatically when
running
a top-level build, but the "distribution" module isn't.
Are the distros you posted on the p.a.o site from the building of
"distribution" folder?
Yes. This is what we do for Tuscany SCA Java, and I thought it made
sense to do the same for the travel sample.
Simon
I suspect you intended to build the "distribution" module but built the
binaries/bundle module instead. The procedure for building the
distribution
is described in the BUILDING file. Is there any change we could make to
the BUILDING file to clarify this?
Simon
-------- Original Message --------
Subject: Re: [VOTE] Release Tuscany SCA Travel Sample 1.0
Date: Sat, 22 May 2010 12:57:05 -0700
From: Raymond Feng <[email protected] <mailto:[email protected]>>
Reply-To: [email protected] <mailto:[email protected]>
To: [email protected]
References: <[email protected]>
Hi,
I just had a quick run on Mac OSX. The build was successful. But there
is an issue with the binary distros:
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Tuscany SCA Tours Binaries Bundle
[INFO] task-segment: [clean, install]
[INFO]
------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [assembly:single {execution: distribution-package}]
[INFO] Reading assembly descriptor: ../src/main/assembly/bin.xml
[INFO] Processing DependencySet (output=util)
[INFO] Processing DependencySet (output=contributions)
[INFO] Processing DependencySet
(output=contributions/scatours-contribution-payment-bpel-process)
[INFO] Processing DependencySet (output=launchers)
[INFO] Processing DependencySet (output=services)
[INFO] Processing DependencySet (output=clients)
[INFO] Processing DependencySet (output=webapps)
[INFO] Processing DependencySet (output=domainconfig)
[INFO] Copying files to
/Users/rfeng/Projects/tuscany/sca-java-1.x/tags/travelsample-1.0-RC1/binaries/target/.
[WARNING] Assembly file:
/Users/rfeng/Projects/tuscany/sca-java-1.x/tags/travelsample-1.0-RC1/binaries/target/.
is not a regular file (it may be a directory). It cannot be attached to
the project build for installation or deployment.
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/Users/rfeng/Projects/tuscany/sca-java-1.x/tags/travelsample-1.0-RC1/binaries/bundle/pom.xml
to
/Users/rfeng/.m2/repository/org/apache/tuscany/sca/scatours-binaries-bundle/1.0/scatours-binaries-bundle-1.0.pom
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[delete] Deleting directory
/Users/rfeng/Projects/tuscany/sca-java-1.x/tags/travelsample-1.0-RC1/binaries/target/domainconfig/META-INF
[INFO] Executed tasks
No files are copied into binaries/target. No zip/gz files are produced.
Thanks,
Raymond
/________________________________________________________________
Raymond Feng
[email protected] <mailto:[email protected]>
/Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
/
________________________________________________________________/
On May 21, 2010, at 4:03 PM, Simon Nash wrote:
Please review and vote on RC1 of the SCA Travel Sample 1.0 release.
The distribution artifacts and RAT report are available for review at:
http://people.apache.org/~nash/tuscany/travelsample-1.0-RC1/
The release tag is at:
https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/tags/travelsample-1.0-RC1/
There are no maven artifacts included in this release.
As this has been posted on a weekend, I'll wait 72 hours from start of
business Monday (US Pacific Time) before closing the vote.
Simon
