[VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

Please review and vote on the 0.90 release artifacts of Tuscany SCA for
Java.

The artifacts are available for review at:
http://people.apache.org/~antelder/tuscany/0.90-rc1/

This includes the binary and source distributions, the RAT reports, and the
Maven staging repository.

The SVN tag for the release is:
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/

Looks ok to me so here's my +1.

Thanks in advance,

   ...ant

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Nash <na...@hursley.ibm.com>]

Jean-Sebastien Delfino wrote:
 > (cut)
 >
> 3) In docs/, wer'e missing Javadoc for a number of SPI packages listed 
> in CHANGES, and more importantly, Javadoc for the SCA Java APIs .
> 
The javadoc for org.osoa.sca.* is there but these packages aren't being
included in the top-level index.

 > (cut)
> 
> 8) I'd suggest to rename the binding-echo-appl and 
> implementation-crud-client to something else, as most of these samples 
> are appls as well, and implementation-crud is not a client, but I don't 
> have a good name proposal. I had proposed to rename echo-binding to 
> echo-binding-extension but it doesn't fit either as none of our other 
> extension modules are named *-extension. These two samples look too 
> complicated to me now, but I'm not sure if we can do anything about it 
> for this release.
> 
I don't see a problem with naming these samples *-extension to
differentiate them from the other non-extension samples.  As you said
in an earlier post, this makes it easy for users to find the sample
extensions.  These are only sample "toy" extensions and I don't think
this would cause users to put -extension on the end of the names of
real extensions that they build.

I think we should leave the structure of these two samples as is for this
elease (modulo possible renaming), and discuss other alternatives later.

   Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Laws <si...@googlemail.com>]

I fixed the sample problems when we mentioned them before (that's 5 and 6
from Sebatien's list). I can look at other things first thing as it sounds
like we are going to respin. Too tired now to get it right.

I still don't think we wait for a fix for my build problem. It's the first
time it's come up, it's only on the combination of software I have and there
is a (manual) work around.

Simon

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Jean-Sebastien Delfino <js...@apache.org>]

ant elder wrote:
> On 5/23/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>>
>> ant elder wrote:
>> > Please review and vote on the 0.90 release artifacts of Tuscany SCA 
>> for
>> > Java.
>> >
>> > The artifacts are available for review at:
>> > http://people.apache.org/~antelder/tuscany/0.90-rc1/
>> >
>> > This includes the binary and source distributions, the RAT reports,
>> > and the
>> > Maven staging repository.
>> >
>> > The SVN tag for the release is:
>> >
>> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ 
>>
>> >
>> >
>> > Looks ok to me so here's my +1.
>> >
>> > Thanks in advance,
>> >
>> >   ...ant
>> >
>>
>> I've reviewed the binary release on Linux. It looks pretty good to me
>> but I have a few comments, some minor, some more important:
>>
>> 1) CHANGES file, I'd suggest to move the API / user items to the top and
>> move the SPI related section to the bottom, and change Host extensions
>> to Host integrations or Host environments.
>>
>> 2) RELEASE_NOTES, I'd suggest to change "The Tuscany all and manifest
>> jars..." to "The tuscany-sca-all and tuscany-sca-manifest jars..."
>>
>> 3) In docs/, wer'e missing Javadoc for a number of SPI packages listed
>> in CHANGES, and more importantly, Javadoc for the SCA Java APIs .
>>
>> 4) I couldn't find text explaining that tuscany-sca-all contains all the
>> other Tuscany JARs and that you don't need them as well if you're using
>> it.
>>
>> 5) The RMI READMEs seem out of sync. Also I found having the
>> build_client and build_server in both the rmi-reference and rmi-service
>> samples confusing, how about just having a single build.xml like the
>> other samples do (e.g. helloworld-ws-reference and
>> helloworld-ws-service). Build.xml would start the server in rmi-service
>> and the client in rmi-reference.
>>
>> 6) The implementation-crud-client does not work (I'm probably
>> responsible for breaking this one...)
>>
>> 7) Like Ant said in another email, it would be good to rename
>> calculator-web to calculator-webapp
>>
>> 8) I'd suggest to rename the binding-echo-appl and
>> implementation-crud-client to something else, as most of these samples
>> are appls as well, and implementation-crud is not a client, but I don't
>> have a good name proposal. I had proposed to rename echo-binding to
>> echo-binding-extension but it doesn't fit either as none of our other
>> extension modules are named *-extension. These two samples look too
>> complicated to me now, but I'm not sure if we can do anything about it
>> for this release.
>>
>> 8) In the helloworld-jsonrpc sample, clicking the
>> services/HelloWorldService link at the top of the page shows an
>> exception, this probably normal as the server expects a JSON request,
>> but confusing. I'd suggest to remove that link.
>>
>> 9) I could not find text in a README describing how I would use the
>> binary distro, load one of the samples in Eclipse or IDEA and run it
>> from there. As a developer that's one of the things I'd like to do first
>> to browse the sample code and experiment with it. The steps described in
>> the samples README only apply to the source distro and require Maven
>> expertise, we should document simpler steps for somebody using the
>> binary distro without Maven.
>>
>> 10) The samples/README says that you can build with mvn from both the
>> source and binary distros, but the steps seem to apply to only the
>> source distro.
>>
>> 11) None of the samples shows the use of META-INF/sca-deployables. I'd
>> suggest to have one of the Webapp samples use that instead of
>> sca-contribution.xml.
>>
>> I think it would be good to respin another release candidate with fixes
>> for (1), (3), (4), (5), (6), (9) and (11) at least...
>
>
> Which things MUST be fixed to avoid -1s on the next rc?  Is 11 on this 
> list
> a blocker? Is the linux compile problem a blocker? Also which things are
> people volunteering to fix? The javadoc one (3) seems a difficult one 
> to fix
> to me which could easily end up just making things worse if we rush 
> it. The
> 0.90 branch is open to everyone for updating so ideally I'd like to 
> just get
> up tomorrow morning to find all the blockers fixed so I can cut anther 
> rc,
> but so far its not clear what are the blockers or what the correct fix 
> is,
> so its going to be difficult to know if things are in a state where I can
> cut another rc or not. We could spend weeks polishing this point 
> release, is
> that what we want to be doing?
>
>   ..ant
>

None of them, that's why I didn't -1 the RC1. If you end up respinning 
an RC for other reasons then I'd say that the more important ones for me 
are (3), (5), (6) and (9) and it looks like Simon Laws has already fixed 
(5) and (6). If there's no other good reason for respinning an RC then 
you get my +1 for RC1 as long as we have JIRAs for these issues, and 
more importantly an Errata document clearly posted on our download page, 
documenting them and how to get around them.

-- 
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

On 5/23/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> ant elder wrote:
> > Please review and vote on the 0.90 release artifacts of Tuscany SCA for
> > Java.
> >
> > The artifacts are available for review at:
> > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> >
> > This includes the binary and source distributions, the RAT reports,
> > and the
> > Maven staging repository.
> >
> > The SVN tag for the release is:
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> >
> >
> > Looks ok to me so here's my +1.
> >
> > Thanks in advance,
> >
> >   ...ant
> >
>
> I've reviewed the binary release on Linux. It looks pretty good to me
> but I have a few comments, some minor, some more important:
>
> 1) CHANGES file, I'd suggest to move the API / user items to the top and
> move the SPI related section to the bottom, and change Host extensions
> to Host integrations or Host environments.
>
> 2) RELEASE_NOTES, I'd suggest to change "The Tuscany all and manifest
> jars..." to "The tuscany-sca-all and tuscany-sca-manifest jars..."
>
> 3) In docs/, wer'e missing Javadoc for a number of SPI packages listed
> in CHANGES, and more importantly, Javadoc for the SCA Java APIs .
>
> 4) I couldn't find text explaining that tuscany-sca-all contains all the
> other Tuscany JARs and that you don't need them as well if you're using
> it.
>
> 5) The RMI READMEs seem out of sync. Also I found having the
> build_client and build_server in both the rmi-reference and rmi-service
> samples confusing, how about just having a single build.xml like the
> other samples do (e.g. helloworld-ws-reference and
> helloworld-ws-service). Build.xml would start the server in rmi-service
> and the client in rmi-reference.
>
> 6) The implementation-crud-client does not work (I'm probably
> responsible for breaking this one...)
>
> 7) Like Ant said in another email, it would be good to rename
> calculator-web to calculator-webapp
>
> 8) I'd suggest to rename the binding-echo-appl and
> implementation-crud-client to something else, as most of these samples
> are appls as well, and implementation-crud is not a client, but I don't
> have a good name proposal. I had proposed to rename echo-binding to
> echo-binding-extension but it doesn't fit either as none of our other
> extension modules are named *-extension. These two samples look too
> complicated to me now, but I'm not sure if we can do anything about it
> for this release.
>
> 8) In the helloworld-jsonrpc sample, clicking the
> services/HelloWorldService link at the top of the page shows an
> exception, this probably normal as the server expects a JSON request,
> but confusing. I'd suggest to remove that link.
>
> 9) I could not find text in a README describing how I would use the
> binary distro, load one of the samples in Eclipse or IDEA and run it
> from there. As a developer that's one of the things I'd like to do first
> to browse the sample code and experiment with it. The steps described in
> the samples README only apply to the source distro and require Maven
> expertise, we should document simpler steps for somebody using the
> binary distro without Maven.
>
> 10) The samples/README says that you can build with mvn from both the
> source and binary distros, but the steps seem to apply to only the
> source distro.
>
> 11) None of the samples shows the use of META-INF/sca-deployables. I'd
> suggest to have one of the Webapp samples use that instead of
> sca-contribution.xml.
>
> I think it would be good to respin another release candidate with fixes
> for (1), (3), (4), (5), (6), (9) and (11) at least...


Which things MUST be fixed to avoid -1s on the next rc?  Is 11 on this list
a blocker? Is the linux compile problem a blocker? Also which things are
people volunteering to fix? The javadoc one (3) seems a difficult one to fix
to me which could easily end up just making things worse if we rush it. The
0.90 branch is open to everyone for updating so ideally I'd like to just get
up tomorrow morning to find all the blockers fixed so I can cut anther rc,
but so far its not clear what are the blockers or what the correct fix is,
so its going to be difficult to know if things are in a state where I can
cut another rc or not. We could spend weeks polishing this point release, is
that what we want to be doing?

   ..ant

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Jean-Sebastien Delfino <js...@apache.org>]

ant elder wrote:
> Please review and vote on the 0.90 release artifacts of Tuscany SCA for
> Java.
>
> The artifacts are available for review at:
> http://people.apache.org/~antelder/tuscany/0.90-rc1/
>
> This includes the binary and source distributions, the RAT reports, 
> and the
> Maven staging repository.
>
> The SVN tag for the release is:
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ 
>
>
> Looks ok to me so here's my +1.
>
> Thanks in advance,
>
>   ...ant
>

I've reviewed the binary release on Linux. It looks pretty good to me 
but I have a few comments, some minor, some more important:

1) CHANGES file, I'd suggest to move the API / user items to the top and 
move the SPI related section to the bottom, and change Host extensions 
to Host integrations or Host environments.

2) RELEASE_NOTES, I'd suggest to change "The Tuscany all and manifest 
jars..." to "The tuscany-sca-all and tuscany-sca-manifest jars..."

3) In docs/, wer'e missing Javadoc for a number of SPI packages listed 
in CHANGES, and more importantly, Javadoc for the SCA Java APIs .

4) I couldn't find text explaining that tuscany-sca-all contains all the 
other Tuscany JARs and that you don't need them as well if you're using it.

5) The RMI READMEs seem out of sync. Also I found having the 
build_client and build_server in both the rmi-reference and rmi-service 
samples confusing, how about just having a single build.xml like the 
other samples do (e.g. helloworld-ws-reference and 
helloworld-ws-service). Build.xml would start the server in rmi-service 
and the client in rmi-reference.

6) The implementation-crud-client does not work (I'm probably 
responsible for breaking this one...)

7) Like Ant said in another email, it would be good to rename 
calculator-web to calculator-webapp

8) I'd suggest to rename the binding-echo-appl and 
implementation-crud-client to something else, as most of these samples 
are appls as well, and implementation-crud is not a client, but I don't 
have a good name proposal. I had proposed to rename echo-binding to 
echo-binding-extension but it doesn't fit either as none of our other 
extension modules are named *-extension. These two samples look too 
complicated to me now, but I'm not sure if we can do anything about it 
for this release.

8) In the helloworld-jsonrpc sample, clicking the 
services/HelloWorldService link at the top of the page shows an 
exception, this probably normal as the server expects a JSON request, 
but confusing. I'd suggest to remove that link.

9) I could not find text in a README describing how I would use the 
binary distro, load one of the samples in Eclipse or IDEA and run it 
from there. As a developer that's one of the things I'd like to do first 
to browse the sample code and experiment with it. The steps described in 
the samples README only apply to the source distro and require Maven 
expertise, we should document simpler steps for somebody using the 
binary distro without Maven.

10) The samples/README says that you can build with mvn from both the 
source and binary distros, but the steps seem to apply to only the 
source distro.

11) None of the samples shows the use of META-INF/sca-deployables. I'd 
suggest to have one of the Webapp samples use that instead of 
sca-contribution.xml.

I think it would be good to respin another release candidate with fixes 
for (1), (3), (4), (5), (6), (9) and (11) at least...

Thanks.

-- 
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Laws <si...@googlemail.com>]

I didn't. I looked at both versions of maven-jaxb-plugin at
https://maven-repository.dev.java.net/repository/com.sun.tools.xjc.maven2/poms/and
both have the odd characters in. There seem to be other
implementations
of the maven-jaxb-plugin around and I tried the ones I could find but got
NPEs in maven. Not sure whether this is the version of the plugin, the
version of jaxb or a real problem. I'm not that faimiliar with JAXB and what
version works with what so I don't have a quick fix. Also tried upgrading my
JDK but that didn't work either.  Am already on Maven 2.0.6.

Happy to try any other ideas people have.

What I have to do is work backwards through this and work out what version
of what will actually work for us (I find trying to work this out for maven
plugins very difficult) and see if I can get a combination that doesn't have
the author name with the non-UTF8 character or where this particular fault
has been fixed. Failing this we will have to get on whatever mail list deals
with it and ask for a fix.

As it stands we can offer a manual fix for anyone who has Linux/IBM JDK, i.e.
run the build until it fails and then remove the problematic characters
manually from the offending pom in the local repo.

I can't say how long this will take but I think we need to get on with the
release and address is next time.

Simon

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Raymond Feng <en...@gmail.com>]

Hi, Simon.

Do you have any luck to fix the problem? If not, we probably have to 
document the limitation and let the release out.

Thanks,
Raymond

----- Original Message ----- 
From: "Simon Laws" <si...@googlemail.com>
To: <tu...@ws.apache.org>
Sent: Tuesday, May 22, 2007 10:35 AM
Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating


> OK, so I can't get the compile to work on my linux box with a simple 
> change
> to the version/location of the maven-jaxb-plugin that the build uses. I'm
> going to upgrade my JDK and see if that has a positive effect but of 
> course
> that has no bearing on the SCA release. As this problem is restricted to a
> particular JDK on a particular platform then we can post a note about how 
> to
> get round the problem manually. I would really like to fix the readmes but
> if that's the only thing then I can live with a note on the web page for
> that.
>
> Simon
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Laws <si...@googlemail.com>]

OK, so I can't get the compile to work on my linux box with a simple change
to the version/location of the maven-jaxb-plugin that the build uses. I'm
going to upgrade my JDK and see if that has a positive effect but of course
that has no bearing on the SCA release. As this problem is restricted to a
particular JDK on a particular platform then we can post a note about how to
get round the problem manually. I would really like to fix the readmes but
if that's the only thing then I can live with a note on the web page for
that.

Simon

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Venkata Krishnan <fo...@gmail.com>]

Hi,

I've give the distros a shot on windows xp.

- The src disb. builds clean
- The tried all the samples from the binary dist just following the
READMEs.  Like the others I do find the README for the rmi samples out of
sync and also the  crud-client app does not run.  But all the other samples
run cleanly.

With the rmi samples I am quite surprised because during the code chill time
period I think I fixed the samples to run as per the README.  The RMI Server
sample used a RMI Client ( an not a SCA Reference) and similarly the RMI
Reference sample used a RMI Server (not a SCA Service) and each was pretty
compact in itself.  I am not sure about where it changed after that.

Anyways, looking at it overall I'd like to give a '+1' based on the
following: -
- Though I agree that this is not the most perfect of packages I still feel
none of the glitches are paralysing.  For example, even if the rmi samples
did not work as per the README they contain all that is required to run them
and then there are a whole bunch of other samples that work cleanly
demonstrating SCA and the extensions we offer to date.
- Its been a while since we released and this one has fundamental changes to
how things were a few months ago.  Getting this release out asap is good for
us and to users so that there is enough time for trying out and giving
feedback that can be picked up for our next release which I guess is going
to be in another few weeks from now.
- Finally this is just about 0.90 and I am ok to have the sort of issues
that have been identified with it.  I am happy to know what we need to watch
for in our next release.

Thanks

- Venkat



On 5/21/07, ant elder <an...@gmail.com> wrote:
>
> Please review and vote on the 0.90 release artifacts of Tuscany SCA for
> Java.
>
> The artifacts are available for review at:
> http://people.apache.org/~antelder/tuscany/0.90-rc1/
>
> This includes the binary and source distributions, the RAT reports, and
> the
> Maven staging repository.
>
> The SVN tag for the release is:
>
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
>
> Looks ok to me so here's my +1.
>
> Thanks in advance,
>
>    ...ant
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

On 5/24/07, Simon Laws <si...@googlemail.com> wrote:
>
> OK, below is an errata based on the points that people have highlighted as
> important in this thread. Anything else need to be added? Anyone have any
> better words for installing samples from the binary distro in Eclipse or
> any
> words at all for IDEA. Now we have most people's comments in, this is
> quite
> a long list!
>
> Simon
>
> Samples
> =======
> * Some sample READMEs don't match the code as it stands
>   calculator-rmi-reference
>     The README describes how to start client and server processes from
> this
> project. This is now not
>     the case. This project now only supports the client process. Use the
> calculator-rmi-service sample
>     to start the server using "ant-f build-server.xml run" first and then
> run the client here.
>
>   calculator-rmi-service
>     The README describes how to start client and server processes from
> this
> project. This is now not
>     the case. This project now only supports the server process. Run the
> server here first and then
>     use the calculator-rmi-reference sample to start the client using "ant
> -f build-client.xml run".
>
> * The implementation-crud-client sample has the wrong package name for the
> test client
>   In both README and build.xml "crud.CRUDClient" should read "
> crud.client.CRUDClient"
>
> * The calculator-web and helloworld-jsonrpc build.xml produces a war that
> is
> not deployable. To fix the build.xml file. Move the line
>
>   <include name="sca-api-0.90-incubating-SNAPSHOT.jar"/>
>
>   From the <lib> section to the <zipfileset> section.
>
> * At the top of the web page provided by the helloworld-jsonrpc sample
> there
> is the text.
>   "... to make JSON-RPC requests to the service located at
> services/HelloWorldService"
>   Selecting the link "service/HelloWorldService" causes and error.
>
> * There is no sample for how to use the META_INF/sca-deployables feature
> in
> this release.
>
> Build
> =====
>
> * There is a problem building the source distribution on linux with the
> IBM
> JDK 1.5.0. The problem manifests itself
>   with a problem building the databinding-jaxb module. Maven reports that
> it
> is unable to process the
>   maven-jaxb-plugin pom. This occurs because this pom has non-UTF8
> characters. The manual fix is to remove the
>   offending characters manually from the pom in your local repo and
> restart
> the build:
>
>   .m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-
> jaxb-plugin-1.1.pom
>
>   remove the non-UTF8 characters from this block.
>
>     <developer>
>       <id>MÆlfweald</id>
>       <name>Malachi de Ælfweald</name>
>       <email>malachid@gmail.com</email>
>       <roles>
>         <role>Developer</role>
>       </roles>
>     </developer>
>
> Documentation
> =============
>
> * Java doc for some of the SPI packages listed in the the CHANGES file are
> missing from the docs directory
> * Java doc for org.osoa.sca.* packages is provided but not included on the
> index page
> * Java doc to the Tuscany Java SCA APIs is not provided with this release
> * Instructions for loading the binary distribution samples into an IDE
> without using maven to generate suitable project
>   files are missing.
>
>   For Eclipse - in a new or existing workspace
>     Create a new java project to represent the sample you want to work on,
> e.g.
>         calculator
>     Import all of the sample code and resources into this project, e.g.
>         File, Import and then select
> tuscany-sca-0.90-incubating\samples\calculator from the filesystem
>     Configure the source path to include
>         src/main/java
>         src/main/resources
>     Configure the output folder to be
>         calculator/target
>     Configure the build path to include all of the jars provided in
>         lib
>         modules
>      If you select calculator.CalculatorClient.java and run as "Java
> Application" you should see
>         3 + 2=5.0
>         3 - 2=1.0
>         3 * 2=6.0
>         3 / 2=1.5
>
> Other
> =====
>
> * Some non-working modules have been included in the distribution and
> should
> be ignored
>   modules/binding-jms
>   modules/discovery-jms
>   modules/implementation-spring
>   modules/jmx
>

Listing all these issues like this makes RC1 sound a bit too imperfect IMHO
so I'm now -1 on releasing it.

I've cut a new RC2 which includes all the fixes that have been made in the
0.90 branch, many thanks to all those who've been fixing things there as the
problems have been discovered. It doesn't fix the Javadoc problem, there's a
note in the CHANGES file saying thats incomplete, and it doesn't fix the
Linux build issue, there's a note in the BUILDING file about that, and
there's a couple of other's not fixed as they seemed either to small or
difficult to be worth the risk of the change. Fingers crossed the respin
hasn't introduced any new problems...

I'll start a new vote thread for RC2.

   ...ant

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Luciano Resende <lu...@gmail.com>]

I was looking for the javadoc issue, and the issue is that
maven-dependency-plugin:unpack-javadoc just copy and unpack each
module javadoc files, overriding files with same name from previous
modules javadoc, this is why we only see the index.html from the last
module processed, instead of having a "aggregated" index.html.

I have tried various options to aggregate these javadocs from multiple
modules, without any success.

Does anybody know about some maven hacks to accomplish this ?


On 5/24/07, Simon Laws <si...@googlemail.com> wrote:
> OK, below is an errata based on the points that people have highlighted as
> important in this thread. Anything else need to be added? Anyone have any
> better words for installing samples from the binary distro in Eclipse or any
> words at all for IDEA. Now we have most people's comments in, this is quite
> a long list!
>
> Simon
>
> Samples
> =======
> * Some sample READMEs don't match the code as it stands
>   calculator-rmi-reference
>     The README describes how to start client and server processes from this
> project. This is now not
>     the case. This project now only supports the client process. Use the
> calculator-rmi-service sample
>     to start the server using "ant-f build-server.xml run" first and then
> run the client here.
>
>   calculator-rmi-service
>     The README describes how to start client and server processes from this
> project. This is now not
>     the case. This project now only supports the server process. Run the
> server here first and then
>     use the calculator-rmi-reference sample to start the client using "ant
> -f build-client.xml run".
>
> * The implementation-crud-client sample has the wrong package name for the
> test client
>   In both README and build.xml "crud.CRUDClient" should read "
> crud.client.CRUDClient"
>
> * The calculator-web and helloworld-jsonrpc build.xml produces a war that is
> not deployable. To fix the build.xml file. Move the line
>
>   <include name="sca-api-0.90-incubating-SNAPSHOT.jar"/>
>
>   From the <lib> section to the <zipfileset> section.
>
> * At the top of the web page provided by the helloworld-jsonrpc sample there
> is the text.
>   "... to make JSON-RPC requests to the service located at
> services/HelloWorldService"
>   Selecting the link "service/HelloWorldService" causes and error.
>
> * There is no sample for how to use the META_INF/sca-deployables feature in
> this release.
>
> Build
> =====
>
> * There is a problem building the source distribution on linux with the IBM
> JDK 1.5.0. The problem manifests itself
>   with a problem building the databinding-jaxb module. Maven reports that it
> is unable to process the
>   maven-jaxb-plugin pom. This occurs because this pom has non-UTF8
> characters. The manual fix is to remove the
>   offending characters manually from the pom in your local repo and restart
> the build:
>
>   .m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-
> jaxb-plugin-1.1.pom
>
>   remove the non-UTF8 characters from this block.
>
>     <developer>
>       <id>MÆlfweald</id>
>       <name>Malachi de Ælfweald</name>
>       <email>malachid@gmail.com</email>
>       <roles>
>         <role>Developer</role>
>       </roles>
>     </developer>
>
> Documentation
> =============
>
> * Java doc for some of the SPI packages listed in the the CHANGES file are
> missing from the docs directory
> * Java doc for org.osoa.sca.* packages is provided but not included on the
> index page
> * Java doc to the Tuscany Java SCA APIs is not provided with this release
> * Instructions for loading the binary distribution samples into an IDE
> without using maven to generate suitable project
>   files are missing.
>
>   For Eclipse - in a new or existing workspace
>     Create a new java project to represent the sample you want to work on,
> e.g.
>         calculator
>     Import all of the sample code and resources into this project, e.g.
>         File, Import and then select
> tuscany-sca-0.90-incubating\samples\calculator from the filesystem
>     Configure the source path to include
>         src/main/java
>         src/main/resources
>     Configure the output folder to be
>         calculator/target
>     Configure the build path to include all of the jars provided in
>         lib
>         modules
>      If you select calculator.CalculatorClient.java and run as "Java
> Application" you should see
>         3 + 2=5.0
>         3 - 2=1.0
>         3 * 2=6.0
>         3 / 2=1.5
>
> Other
> =====
>
> * Some non-working modules have been included in the distribution and should
> be ignored
>   modules/binding-jms
>   modules/discovery-jms
>   modules/implementation-spring
>   modules/jmx
>


-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Laws <si...@googlemail.com>]

OK, below is an errata based on the points that people have highlighted as
important in this thread. Anything else need to be added? Anyone have any
better words for installing samples from the binary distro in Eclipse or any
words at all for IDEA. Now we have most people's comments in, this is quite
a long list!

Simon

Samples
=======
* Some sample READMEs don't match the code as it stands
  calculator-rmi-reference
    The README describes how to start client and server processes from this
project. This is now not
    the case. This project now only supports the client process. Use the
calculator-rmi-service sample
    to start the server using "ant-f build-server.xml run" first and then
run the client here.

  calculator-rmi-service
    The README describes how to start client and server processes from this
project. This is now not
    the case. This project now only supports the server process. Run the
server here first and then
    use the calculator-rmi-reference sample to start the client using "ant
-f build-client.xml run".

* The implementation-crud-client sample has the wrong package name for the
test client
  In both README and build.xml "crud.CRUDClient" should read "
crud.client.CRUDClient"

* The calculator-web and helloworld-jsonrpc build.xml produces a war that is
not deployable. To fix the build.xml file. Move the line

  <include name="sca-api-0.90-incubating-SNAPSHOT.jar"/>

  From the <lib> section to the <zipfileset> section.

* At the top of the web page provided by the helloworld-jsonrpc sample there
is the text.
  "... to make JSON-RPC requests to the service located at
services/HelloWorldService"
  Selecting the link "service/HelloWorldService" causes and error.

* There is no sample for how to use the META_INF/sca-deployables feature in
this release.

Build
=====

* There is a problem building the source distribution on linux with the IBM
JDK 1.5.0. The problem manifests itself
  with a problem building the databinding-jaxb module. Maven reports that it
is unable to process the
  maven-jaxb-plugin pom. This occurs because this pom has non-UTF8
characters. The manual fix is to remove the
  offending characters manually from the pom in your local repo and restart
the build:

  .m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-
jaxb-plugin-1.1.pom

  remove the non-UTF8 characters from this block.

    <developer>
      <id>MÆlfweald</id>
      <name>Malachi de Ælfweald</name>
      <email>malachid@gmail.com</email>
      <roles>
        <role>Developer</role>
      </roles>
    </developer>

Documentation
=============

* Java doc for some of the SPI packages listed in the the CHANGES file are
missing from the docs directory
* Java doc for org.osoa.sca.* packages is provided but not included on the
index page
* Java doc to the Tuscany Java SCA APIs is not provided with this release
* Instructions for loading the binary distribution samples into an IDE
without using maven to generate suitable project
  files are missing.

  For Eclipse - in a new or existing workspace
    Create a new java project to represent the sample you want to work on,
e.g.
        calculator
    Import all of the sample code and resources into this project, e.g.
        File, Import and then select
tuscany-sca-0.90-incubating\samples\calculator from the filesystem
    Configure the source path to include
        src/main/java
        src/main/resources
    Configure the output folder to be
        calculator/target
    Configure the build path to include all of the jars provided in
        lib
        modules
     If you select calculator.CalculatorClient.java and run as "Java
Application" you should see
        3 + 2=5.0
        3 - 2=1.0
        3 * 2=6.0
        3 / 2=1.5

Other
=====

* Some non-working modules have been included in the distribution and should
be ignored
  modules/binding-jms
  modules/discovery-jms
  modules/implementation-spring
  modules/jmx

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Luciano Resende <lu...@gmail.com>]

Thanks for the patch Simon, I have applied it on the 0.90 branch and
in trunk as well and have resolved the JIRA.

On 5/23/07, Simon Nash <na...@hursley.ibm.com> wrote:
> I found a serious problem in the calculator-web sample in the 0.90
> release candidate.  The ant script for this sample builds a war that
> is not deployable because of two missing files.  The pre-built war file
> that is shipped as part of the binary distro is fine.  I discovered
> this as a last-minute glitch with my demo for the Tuscany presentation
> that I gave today at the IBM Impact conference.
>
> I'll write a JIRA for this now and post a patch asap (later today EDT).
>
>    Simon
>
> Simon Nash wrote:
> > I think the "shop window factor" is an important consideration.
> > The cumulative effect of the issues that people have reported seems
> > to be significant enough from this perspective that a respin is
> > desirable.  In particular, the build and sample README problems
> > could be quite off-putting to a novice user.
> >
> >   Simon
> >
> > Simon Laws wrote:
> >
> >> I've given the src and binary distros a spin on linux. My
> >> configuration is
> >>
> >> Fedora Core5
> >> IBM JDK 1.5.0
> >> Maven 2.0.6
> >>
> >> Binary:
> >>
> >> I concur with Luciano that the READMEs for
> >>
> >> calculator-rmi-reference
> >> calculator-rmi-service
> >> implementation-crud
> >>
> >> now don't match the way that the samples are currently organized. I'm
> >> reluctant to agree to go with this release when our shop window isn't
> >> fully
> >> functional. I have checked fixes in for the calculator sample to the
> >> 0.9branch and head. Luciano's fix for implementation-crud looks good
> >> to me.
> >>
> >> Source:
> >>
> >> This fails to build under maven in my environment. The culprit is the
> >> maven-jaxb-plugin. The pom provided with the version that we refer in our
> >> poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the
> >> author
> >> names which causes the maven build to fail with the IBM JDK 1.5.0 on
> >> Linux.
> >> I can confirm that this does not cause a problem with the same JDK (same
> >> version and build at least) on Windows XP. I tried using different
> >> maven-jaxb-plugins from a variety of repositories. All failed for other
> >> reasons. There is a manual work around to the problem, i.e. remove the
> >> non-UTF8 characters, so I don't think that this, on its own is a blocker.
> >>
> >> I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.
> >>
> >> Simon
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
> >
>
> --
> Simon C Nash   IBM Distinguished Engineer
> Hursley Park, Winchester, UK   nash@hursley.ibm.com
> Tel. +44-1962-815156   Fax +44-1962-818999
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>


-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Nash <na...@hursley.ibm.com>]

I found a serious problem in the calculator-web sample in the 0.90
release candidate.  The ant script for this sample builds a war that
is not deployable because of two missing files.  The pre-built war file
that is shipped as part of the binary distro is fine.  I discovered
this as a last-minute glitch with my demo for the Tuscany presentation
that I gave today at the IBM Impact conference.

I'll write a JIRA for this now and post a patch asap (later today EDT).

   Simon

Simon Nash wrote:
> I think the "shop window factor" is an important consideration.
> The cumulative effect of the issues that people have reported seems
> to be significant enough from this perspective that a respin is
> desirable.  In particular, the build and sample README problems
> could be quite off-putting to a novice user.
> 
>   Simon
> 
> Simon Laws wrote:
> 
>> I've given the src and binary distros a spin on linux. My 
>> configuration is
>>
>> Fedora Core5
>> IBM JDK 1.5.0
>> Maven 2.0.6
>>
>> Binary:
>>
>> I concur with Luciano that the READMEs for
>>
>> calculator-rmi-reference
>> calculator-rmi-service
>> implementation-crud
>>
>> now don't match the way that the samples are currently organized. I'm
>> reluctant to agree to go with this release when our shop window isn't 
>> fully
>> functional. I have checked fixes in for the calculator sample to the
>> 0.9branch and head. Luciano's fix for implementation-crud looks good
>> to me.
>>
>> Source:
>>
>> This fails to build under maven in my environment. The culprit is the
>> maven-jaxb-plugin. The pom provided with the version that we refer in our
>> poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the 
>> author
>> names which causes the maven build to fail with the IBM JDK 1.5.0 on 
>> Linux.
>> I can confirm that this does not cause a problem with the same JDK (same
>> version and build at least) on Windows XP. I tried using different
>> maven-jaxb-plugins from a variety of repositories. All failed for other
>> reasons. There is a manual work around to the problem, i.e. remove the
>> non-UTF8 characters, so I don't think that this, on its own is a blocker.
>>
>> I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.
>>
>> Simon
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> 
> 
> 

-- 
Simon C Nash   IBM Distinguished Engineer
Hursley Park, Winchester, UK   nash@hursley.ibm.com
Tel. +44-1962-815156   Fax +44-1962-818999


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Nash <na...@hursley.ibm.com>]

I think the "shop window factor" is an important consideration.
The cumulative effect of the issues that people have reported seems
to be significant enough from this perspective that a respin is
desirable.  In particular, the build and sample README problems
could be quite off-putting to a novice user.

   Simon

Simon Laws wrote:

> I've given the src and binary distros a spin on linux. My configuration is
> 
> Fedora Core5
> IBM JDK 1.5.0
> Maven 2.0.6
> 
> Binary:
> 
> I concur with Luciano that the READMEs for
> 
> calculator-rmi-reference
> calculator-rmi-service
> implementation-crud
> 
> now don't match the way that the samples are currently organized. I'm
> reluctant to agree to go with this release when our shop window isn't fully
> functional. I have checked fixes in for the calculator sample to the
> 0.9branch and head. Luciano's fix for implementation-crud looks good
> to me.
> 
> Source:
> 
> This fails to build under maven in my environment. The culprit is the
> maven-jaxb-plugin. The pom provided with the version that we refer in our
> poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author
> names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux.
> I can confirm that this does not cause a problem with the same JDK (same
> version and build at least) on Windows XP. I tried using different
> maven-jaxb-plugins from a variety of repositories. All failed for other
> reasons. There is a manual work around to the problem, i.e. remove the
> non-UTF8 characters, so I don't think that this, on its own is a blocker.
> 
> I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.
> 
> Simon
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

Ok, go ahead.

You also mentioned a JavaDoc issue before, would you like to fix that as
well or can that be left to be fixed on the next release?

   ...ant

On 5/22/07, Luciano Resende <lu...@gmail.com> wrote:
>
> If we are going to resping the RC, I'd like to remove the modules that are
> not being part of the build from the source distribution.
>
> On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
> >
> > Hi,
> >
> > Sorry for the confusion.
> >
> > Simon found the build break and he didn't take it as a show-stopper. I
> > then
> > said the build failure is serious enough to be a show stopper.
> >
> > Simon found the fix by moving the plugin to the latest version (I just
> > realized that he only said that in the JIRA) but he was concerned that
> how
> > the fix would impact the quality of the release. I then tried to assure
> > him
> > that the usage of the plugin is fairly isolated and the risk should be
> > minor.
> >
> > Thanks,
> > Raymond
> >
> > ----- Original Message -----
> > From: "ant elder" <an...@gmail.com>
> > To: <tu...@ws.apache.org>
> > Sent: Tuesday, May 22, 2007 9:01 AM
> > Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
> >
> >
> > > I'm not clear what you're saying - "Build failure seems to be a
> > > show-stopper
> > > to me" and "So if we fix it..." - surely we must fix it if its a
> > > showstopper
> > > and we want to have a release?
> > >
> > > What is the fix, from the earlier post it didn't sound like there was
> a
> > > good
> > > known fix?
> > >
> > >   ...ant
> > >
> > > On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
> > >>
> > >> Hi,
> > >>
> > >> Build failure seems to be a show-stopper to me :-). Thank you for
> > >> catching
> > >> it.
> > >>
> > >> The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB
> > classes
> > >> for
> > >> the unit tests. So if we fix it, the scope of testing shouldn't be a
> > big
> > >> deal. All we have to do is to run the maven build on the environments
> > we
> > >> have tested so far.
> > >>
> > >> Thanks,
> > >> Raymond
> > >>
> > >> ----- Original Message -----
> > >> From: "Simon Laws" < simonslaws@googlemail.com>
> > >> To: <tu...@ws.apache.org>
> > >> Sent: Tuesday, May 22, 2007 3:37 AM
> > >> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
> > >>
> > >>
> > >> > I've given the src and binary distros a spin on linux. My
> > configuration
> > >> is
> > >> >
> > >> > Fedora Core5
> > >> > IBM JDK 1.5.0
> > >> > Maven 2.0.6
> > >> >
> > >> > Binary:
> > >> >
> > >> > I concur with Luciano that the READMEs for
> > >> >
> > >> > calculator-rmi-reference
> > >> > calculator-rmi-service
> > >> > implementation-crud
> > >> >
> > >> > now don't match the way that the samples are currently organized.
> I'm
> > >> > reluctant to agree to go with this release when our shop window
> isn't
> > >> > fully
> > >> > functional. I have checked fixes in for the calculator sample to
> the
> > >> > 0.9branch and head. Luciano's fix for implementation-crud looks
> good
> > >> > to me.
> > >> >
> > >> > Source:
> > >> >
> > >> > This fails to build under maven in my environment. The culprit is
> the
> > >> > maven-jaxb-plugin. The pom provided with the version that we refer
> in
> > >> our
> > >> > poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the
> > >> author
> > >> > names which causes the maven build to fail with the IBM JDK 1.5.0on
> > >> > Linux.
> > >> > I can confirm that this does not cause a problem with the same JDK
> > >> > (same
> > >> > version and build at least) on Windows XP. I tried using different
> > >> > maven-jaxb-plugins from a variety of repositories. All failed for
> > other
> > >> > reasons. There is a manual work around to the problem, i.e. remove
> > the
> > >> > non-UTF8 characters, so I don't think that this, on its own is a
> > >> blocker.
> > >> >
> > >> > I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for
> > this.
> > >> >
> > >> > Simon
> > >> >
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Luciano Resende <lu...@gmail.com>]

Ok, so I'll remove the following modules, that are not part of the build,
from the 0.9 branch : binding-jms, discovery-jms, implementation-spring and
jmx.

As for the javadoc, I'm flexible with that, and I think it can be fixed in a
new release.

On 5/22/07, ant elder <an...@gmail.com> wrote:
>
> Ok :) I hadn't read the JIRA.
>
> Simon, as you're the one that can recreate this would you be able to
> commit
> that and test it works for you?
>
>    ...ant
>
> On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
> >
> > Hi,
> >
> > Sorry for the confusion.
> >
> > Simon found the build break and he didn't take it as a show-stopper. I
> > then
> > said the build failure is serious enough to be a show stopper.
> >
> > Simon found the fix by moving the plugin to the latest version (I just
> > realized that he only said that in the JIRA) but he was concerned that
> how
> > the fix would impact the quality of the release. I then tried to assure
> > him
> > that the usage of the plugin is fairly isolated and the risk should be
> > minor.
> >
> > Thanks,
> > Raymond
> >
> > ----- Original Message -----
> > From: "ant elder" <an...@gmail.com>
> > To: <tu...@ws.apache.org>
> > Sent: Tuesday, May 22, 2007 9:01 AM
> > Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
> >
> >
> > > I'm not clear what you're saying - "Build failure seems to be a
> > > show-stopper
> > > to me" and "So if we fix it..." - surely we must fix it if its a
> > > showstopper
> > > and we want to have a release?
> > >
> > > What is the fix, from the earlier post it didn't sound like there was
> a
> > > good
> > > known fix?
> > >
> > >   ...ant
> > >
> > > On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
> > >>
> > >> Hi,
> > >>
> > >> Build failure seems to be a show-stopper to me :-). Thank you for
> > >> catching
> > >> it.
> > >>
> > >> The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB
> > classes
> > >> for
> > >> the unit tests. So if we fix it, the scope of testing shouldn't be a
> > big
> > >> deal. All we have to do is to run the maven build on the environments
> > we
> > >> have tested so far.
> > >>
> > >> Thanks,
> > >> Raymond
> > >>
> > >> ----- Original Message -----
> > >> From: "Simon Laws" < simonslaws@googlemail.com>
> > >> To: <tu...@ws.apache.org>
> > >> Sent: Tuesday, May 22, 2007 3:37 AM
> > >> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
> > >>
> > >>
> > >> > I've given the src and binary distros a spin on linux. My
> > configuration
> > >> is
> > >> >
> > >> > Fedora Core5
> > >> > IBM JDK 1.5.0
> > >> > Maven 2.0.6
> > >> >
> > >> > Binary:
> > >> >
> > >> > I concur with Luciano that the READMEs for
> > >> >
> > >> > calculator-rmi-reference
> > >> > calculator-rmi-service
> > >> > implementation-crud
> > >> >
> > >> > now don't match the way that the samples are currently organized.
> I'm
> > >> > reluctant to agree to go with this release when our shop window
> isn't
> > >> > fully
> > >> > functional. I have checked fixes in for the calculator sample to
> the
> > >> > 0.9branch and head. Luciano's fix for implementation-crud looks
> good
> > >> > to me.
> > >> >
> > >> > Source:
> > >> >
> > >> > This fails to build under maven in my environment. The culprit is
> the
> > >> > maven-jaxb-plugin. The pom provided with the version that we refer
> in
> > >> our
> > >> > poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the
> > >> author
> > >> > names which causes the maven build to fail with the IBM JDK 1.5.0on
> > >> > Linux.
> > >> > I can confirm that this does not cause a problem with the same JDK
> > >> > (same
> > >> > version and build at least) on Windows XP. I tried using different
> > >> > maven-jaxb-plugins from a variety of repositories. All failed for
> > other
> > >> > reasons. There is a manual work around to the problem, i.e. remove
> > the
> > >> > non-UTF8 characters, so I don't think that this, on its own is a
> > >> blocker.
> > >> >
> > >> > I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for
> > this.
> > >> >
> > >> > Simon
> > >> >
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>



-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Luciano Resende <lu...@gmail.com>]

If we are going to resping the RC, I'd like to remove the modules that are
not being part of the build from the source distribution.

On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
>
> Hi,
>
> Sorry for the confusion.
>
> Simon found the build break and he didn't take it as a show-stopper. I
> then
> said the build failure is serious enough to be a show stopper.
>
> Simon found the fix by moving the plugin to the latest version (I just
> realized that he only said that in the JIRA) but he was concerned that how
> the fix would impact the quality of the release. I then tried to assure
> him
> that the usage of the plugin is fairly isolated and the risk should be
> minor.
>
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "ant elder" <an...@gmail.com>
> To: <tu...@ws.apache.org>
> Sent: Tuesday, May 22, 2007 9:01 AM
> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
>
>
> > I'm not clear what you're saying - "Build failure seems to be a
> > show-stopper
> > to me" and "So if we fix it..." - surely we must fix it if its a
> > showstopper
> > and we want to have a release?
> >
> > What is the fix, from the earlier post it didn't sound like there was a
> > good
> > known fix?
> >
> >   ...ant
> >
> > On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> Build failure seems to be a show-stopper to me :-). Thank you for
> >> catching
> >> it.
> >>
> >> The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB
> classes
> >> for
> >> the unit tests. So if we fix it, the scope of testing shouldn't be a
> big
> >> deal. All we have to do is to run the maven build on the environments
> we
> >> have tested so far.
> >>
> >> Thanks,
> >> Raymond
> >>
> >> ----- Original Message -----
> >> From: "Simon Laws" < simonslaws@googlemail.com>
> >> To: <tu...@ws.apache.org>
> >> Sent: Tuesday, May 22, 2007 3:37 AM
> >> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
> >>
> >>
> >> > I've given the src and binary distros a spin on linux. My
> configuration
> >> is
> >> >
> >> > Fedora Core5
> >> > IBM JDK 1.5.0
> >> > Maven 2.0.6
> >> >
> >> > Binary:
> >> >
> >> > I concur with Luciano that the READMEs for
> >> >
> >> > calculator-rmi-reference
> >> > calculator-rmi-service
> >> > implementation-crud
> >> >
> >> > now don't match the way that the samples are currently organized. I'm
> >> > reluctant to agree to go with this release when our shop window isn't
> >> > fully
> >> > functional. I have checked fixes in for the calculator sample to the
> >> > 0.9branch and head. Luciano's fix for implementation-crud looks good
> >> > to me.
> >> >
> >> > Source:
> >> >
> >> > This fails to build under maven in my environment. The culprit is the
> >> > maven-jaxb-plugin. The pom provided with the version that we refer in
> >> our
> >> > poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the
> >> author
> >> > names which causes the maven build to fail with the IBM JDK 1.5.0 on
> >> > Linux.
> >> > I can confirm that this does not cause a problem with the same JDK
> >> > (same
> >> > version and build at least) on Windows XP. I tried using different
> >> > maven-jaxb-plugins from a variety of repositories. All failed for
> other
> >> > reasons. There is a manual work around to the problem, i.e. remove
> the
> >> > non-UTF8 characters, so I don't think that this, on its own is a
> >> blocker.
> >> >
> >> > I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for
> this.
> >> >
> >> > Simon
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>


-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

Ok :) I hadn't read the JIRA.

Simon, as you're the one that can recreate this would you be able to commit
that and test it works for you?

   ...ant

On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
>
> Hi,
>
> Sorry for the confusion.
>
> Simon found the build break and he didn't take it as a show-stopper. I
> then
> said the build failure is serious enough to be a show stopper.
>
> Simon found the fix by moving the plugin to the latest version (I just
> realized that he only said that in the JIRA) but he was concerned that how
> the fix would impact the quality of the release. I then tried to assure
> him
> that the usage of the plugin is fairly isolated and the risk should be
> minor.
>
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "ant elder" <an...@gmail.com>
> To: <tu...@ws.apache.org>
> Sent: Tuesday, May 22, 2007 9:01 AM
> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
>
>
> > I'm not clear what you're saying - "Build failure seems to be a
> > show-stopper
> > to me" and "So if we fix it..." - surely we must fix it if its a
> > showstopper
> > and we want to have a release?
> >
> > What is the fix, from the earlier post it didn't sound like there was a
> > good
> > known fix?
> >
> >   ...ant
> >
> > On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> Build failure seems to be a show-stopper to me :-). Thank you for
> >> catching
> >> it.
> >>
> >> The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB
> classes
> >> for
> >> the unit tests. So if we fix it, the scope of testing shouldn't be a
> big
> >> deal. All we have to do is to run the maven build on the environments
> we
> >> have tested so far.
> >>
> >> Thanks,
> >> Raymond
> >>
> >> ----- Original Message -----
> >> From: "Simon Laws" < simonslaws@googlemail.com>
> >> To: <tu...@ws.apache.org>
> >> Sent: Tuesday, May 22, 2007 3:37 AM
> >> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
> >>
> >>
> >> > I've given the src and binary distros a spin on linux. My
> configuration
> >> is
> >> >
> >> > Fedora Core5
> >> > IBM JDK 1.5.0
> >> > Maven 2.0.6
> >> >
> >> > Binary:
> >> >
> >> > I concur with Luciano that the READMEs for
> >> >
> >> > calculator-rmi-reference
> >> > calculator-rmi-service
> >> > implementation-crud
> >> >
> >> > now don't match the way that the samples are currently organized. I'm
> >> > reluctant to agree to go with this release when our shop window isn't
> >> > fully
> >> > functional. I have checked fixes in for the calculator sample to the
> >> > 0.9branch and head. Luciano's fix for implementation-crud looks good
> >> > to me.
> >> >
> >> > Source:
> >> >
> >> > This fails to build under maven in my environment. The culprit is the
> >> > maven-jaxb-plugin. The pom provided with the version that we refer in
> >> our
> >> > poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the
> >> author
> >> > names which causes the maven build to fail with the IBM JDK 1.5.0 on
> >> > Linux.
> >> > I can confirm that this does not cause a problem with the same JDK
> >> > (same
> >> > version and build at least) on Windows XP. I tried using different
> >> > maven-jaxb-plugins from a variety of repositories. All failed for
> other
> >> > reasons. There is a manual work around to the problem, i.e. remove
> the
> >> > non-UTF8 characters, so I don't think that this, on its own is a
> >> blocker.
> >> >
> >> > I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for
> this.
> >> >
> >> > Simon
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Raymond Feng <en...@gmail.com>]

Hi,

Sorry for the confusion.

Simon found the build break and he didn't take it as a show-stopper. I then 
said the build failure is serious enough to be a show stopper.

Simon found the fix by moving the plugin to the latest version (I just 
realized that he only said that in the JIRA) but he was concerned that how 
the fix would impact the quality of the release. I then tried to assure him 
that the usage of the plugin is fairly isolated and the risk should be 
minor.

Thanks,
Raymond

----- Original Message ----- 
From: "ant elder" <an...@gmail.com>
To: <tu...@ws.apache.org>
Sent: Tuesday, May 22, 2007 9:01 AM
Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating


> I'm not clear what you're saying - "Build failure seems to be a 
> show-stopper
> to me" and "So if we fix it..." - surely we must fix it if its a 
> showstopper
> and we want to have a release?
>
> What is the fix, from the earlier post it didn't sound like there was a 
> good
> known fix?
>
>   ...ant
>
> On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
>>
>> Hi,
>>
>> Build failure seems to be a show-stopper to me :-). Thank you for 
>> catching
>> it.
>>
>> The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes
>> for
>> the unit tests. So if we fix it, the scope of testing shouldn't be a big
>> deal. All we have to do is to run the maven build on the environments we
>> have tested so far.
>>
>> Thanks,
>> Raymond
>>
>> ----- Original Message -----
>> From: "Simon Laws" < simonslaws@googlemail.com>
>> To: <tu...@ws.apache.org>
>> Sent: Tuesday, May 22, 2007 3:37 AM
>> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
>>
>>
>> > I've given the src and binary distros a spin on linux. My configuration
>> is
>> >
>> > Fedora Core5
>> > IBM JDK 1.5.0
>> > Maven 2.0.6
>> >
>> > Binary:
>> >
>> > I concur with Luciano that the READMEs for
>> >
>> > calculator-rmi-reference
>> > calculator-rmi-service
>> > implementation-crud
>> >
>> > now don't match the way that the samples are currently organized. I'm
>> > reluctant to agree to go with this release when our shop window isn't
>> > fully
>> > functional. I have checked fixes in for the calculator sample to the
>> > 0.9branch and head. Luciano's fix for implementation-crud looks good
>> > to me.
>> >
>> > Source:
>> >
>> > This fails to build under maven in my environment. The culprit is the
>> > maven-jaxb-plugin. The pom provided with the version that we refer in
>> our
>> > poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the
>> author
>> > names which causes the maven build to fail with the IBM JDK 1.5.0 on
>> > Linux.
>> > I can confirm that this does not cause a problem with the same JDK 
>> > (same
>> > version and build at least) on Windows XP. I tried using different
>> > maven-jaxb-plugins from a variety of repositories. All failed for other
>> > reasons. There is a manual work around to the problem, i.e. remove the
>> > non-UTF8 characters, so I don't think that this, on its own is a
>> blocker.
>> >
>> > I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.
>> >
>> > Simon
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

I'm not clear what you're saying - "Build failure seems to be a show-stopper
to me" and "So if we fix it..." - surely we must fix it if its a showstopper
and we want to have a release?

What is the fix, from the earlier post it didn't sound like there was a good
known fix?

   ...ant

On 5/22/07, Raymond Feng <en...@gmail.com> wrote:
>
> Hi,
>
> Build failure seems to be a show-stopper to me :-). Thank you for catching
> it.
>
> The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes
> for
> the unit tests. So if we fix it, the scope of testing shouldn't be a big
> deal. All we have to do is to run the maven build on the environments we
> have tested so far.
>
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "Simon Laws" < simonslaws@googlemail.com>
> To: <tu...@ws.apache.org>
> Sent: Tuesday, May 22, 2007 3:37 AM
> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
>
>
> > I've given the src and binary distros a spin on linux. My configuration
> is
> >
> > Fedora Core5
> > IBM JDK 1.5.0
> > Maven 2.0.6
> >
> > Binary:
> >
> > I concur with Luciano that the READMEs for
> >
> > calculator-rmi-reference
> > calculator-rmi-service
> > implementation-crud
> >
> > now don't match the way that the samples are currently organized. I'm
> > reluctant to agree to go with this release when our shop window isn't
> > fully
> > functional. I have checked fixes in for the calculator sample to the
> > 0.9branch and head. Luciano's fix for implementation-crud looks good
> > to me.
> >
> > Source:
> >
> > This fails to build under maven in my environment. The culprit is the
> > maven-jaxb-plugin. The pom provided with the version that we refer in
> our
> > poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the
> author
> > names which causes the maven build to fail with the IBM JDK 1.5.0 on
> > Linux.
> > I can confirm that this does not cause a problem with the same JDK (same
> > version and build at least) on Windows XP. I tried using different
> > maven-jaxb-plugins from a variety of repositories. All failed for other
> > reasons. There is a manual work around to the problem, i.e. remove the
> > non-UTF8 characters, so I don't think that this, on its own is a
> blocker.
> >
> > I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.
> >
> > Simon
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Raymond Feng <en...@gmail.com>]

Hi,

Build failure seems to be a show-stopper to me :-). Thank you for catching 
it.

The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes for 
the unit tests. So if we fix it, the scope of testing shouldn't be a big 
deal. All we have to do is to run the maven build on the environments we 
have tested so far.

Thanks,
Raymond

----- Original Message ----- 
From: "Simon Laws" <si...@googlemail.com>
To: <tu...@ws.apache.org>
Sent: Tuesday, May 22, 2007 3:37 AM
Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating


> I've given the src and binary distros a spin on linux. My configuration is
>
> Fedora Core5
> IBM JDK 1.5.0
> Maven 2.0.6
>
> Binary:
>
> I concur with Luciano that the READMEs for
>
> calculator-rmi-reference
> calculator-rmi-service
> implementation-crud
>
> now don't match the way that the samples are currently organized. I'm
> reluctant to agree to go with this release when our shop window isn't 
> fully
> functional. I have checked fixes in for the calculator sample to the
> 0.9branch and head. Luciano's fix for implementation-crud looks good
> to me.
>
> Source:
>
> This fails to build under maven in my environment. The culprit is the
> maven-jaxb-plugin. The pom provided with the version that we refer in our
> poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author
> names which causes the maven build to fail with the IBM JDK 1.5.0 on 
> Linux.
> I can confirm that this does not cause a problem with the same JDK (same
> version and build at least) on Windows XP. I tried using different
> maven-jaxb-plugins from a variety of repositories. All failed for other
> reasons. There is a manual work around to the problem, i.e. remove the
> non-UTF8 characters, so I don't think that this, on its own is a blocker.
>
> I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.
>
> Simon
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Laws <si...@googlemail.com>]

I've given the src and binary distros a spin on linux. My configuration is

Fedora Core5
IBM JDK 1.5.0
Maven 2.0.6

Binary:

I concur with Luciano that the READMEs for

calculator-rmi-reference
calculator-rmi-service
implementation-crud

now don't match the way that the samples are currently organized. I'm
reluctant to agree to go with this release when our shop window isn't fully
functional. I have checked fixes in for the calculator sample to the
0.9branch and head. Luciano's fix for implementation-crud looks good
to me.

Source:

This fails to build under maven in my environment. The culprit is the
maven-jaxb-plugin. The pom provided with the version that we refer in our
poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author
names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux.
I can confirm that this does not cause a problem with the same JDK (same
version and build at least) on Windows XP. I tried using different
maven-jaxb-plugins from a variety of repositories. All failed for other
reasons. There is a manual work around to the problem, i.e. remove the
non-UTF8 characters, so I don't think that this, on its own is a blocker.

I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this.

Simon

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Kevin Williams <kj...@gmail.com>]

I checked out the source from the 0.90 tag and it builds fine from an empty
mvn repository on Mac OS X and the reactor summary is clean.  I also
randomly chose several of the samples from the distribution binaries
(calculator-script, supplychain, simple-bigbank, implementation-composite)
and they work as advertised.

+1 from me

On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
>
> I have done necessary updates to STATUS page [1], and the Incubator
> Tuscany
> page [2]. Note that the changes on the incubator page takes a little while
> to get reflect on the live website.
>
> [1] https://svn.apache.org/repos/asf/incubator/tuscany/STATUS
> [2] http://incubator.apache.org/projects/tuscany.html
>
>
> On 5/21/07, ant elder < ant.elder@gmail.com> wrote:
> >
> > I don't think that document says we MUST include the STATUS document. It
> > says "Check status document" meaning check that the STATUS doc doesn't
> say
> > there are outstanding legal issues that may prevent a release. Even if
> > that
> > releasemanagement doc did say we must, the doc is still under
> development
> > and in draft state so I'm not sure its binding policy. Given other
> recent
> > incubator releases didn't include the STATUS doc and an IPMCer recently
> > said
> > it could be removed from a distro i think this is not a blocking issue.
> >
> >    ...ant
> >
> > On 5/21/07, Luciano Resende < luckbr1975@gmail.com> wrote:
> > >
> > > Regarding the STATUS document, I think the policy say we must include
> > > them,
> > > check [1] on the "Release Documentation" and "STATUS document"
> sessions.
> > > Also our STATUS file is not up to date, and I can take care of helping
> > > updating that after I finish reviewing the rest of the release
> > candidate.
> > >
> > > [1] - http://incubator.apache.org/guides/releasemanagement.html
> > >
> > > On 5/21/07, ant elder <an...@gmail.com> wrote:
> > > >
> > > > Hey many thanks for the prompt and detailed review.
> > > >
> > > > I can't remember exactly about the STATUS file, i think it may be an
> > old
> > > > requirement that is no longer necessary. I can find this
> > > incubator-general
> > > > email [1] about the recent CXF release which included and old and
> > > > incorrect
> > > > status file, and the guidance from an IPMC member was its ok to just
> > > > remove
> > > > it from the distro, so i think its fine we don't include this.
> > > >
> > > > All these other comments seem like good things we should do in
> future,
> > > if
> > > > we
> > > > do have to respin the 0.90 distro's for some other reason I'll try
> to
> > > > incorporate some of them.
> > > >
> > > > Thanks,
> > > >
> > > >    ...ant
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
> > > >
> > > > On 5/21/07, kelvin goodson < kelvingoodson@gmail.com> wrote:
> > > > >
> > > > > Ant,
> > > > >   I've had a good poke around and built the source distro and run
> > the
> > > > > tests
> > > > > successfully. The only potential blocking issue I have found is
> that
> > > > > absence
> > > > > of a STATUS file,  which it was my understanding should be copied
> in
> > > > from
> > > > > the project's STATUS file into every distribution,  but I haven't
> > been
> > > > > able
> > > > > to re-find that guidance in the apache site. Can anyone help
> clarify
> > > > this
> > > > > please?
> > > > >
> > > > > The rest of these comments are all minor observations that
> wouldn't
> > > stop
> > > > > me
> > > > > +1-ing the release.  Indeed, some of them may result in
> > clarification
> > > > that
> > > > > what you have done is corrent and that will help SDO in future
> > > releases?
> > > > >
> > > > > I've had comments in the past that Apache like it if the names of
> > the
> > > > > release file names include the "apache-" prefix
> > > > >
> > > > > I think the copyright in the NOTICES file at the top level of the
> > > source
> > > > > distro should include 2005
> > > > >
> > > > > I thought that the intention of the BUILDING file was to guide a
> > > person
> > > > > who
> > > > > has downloaded the source distribution to be able to recreate the
> > > > > distribution files,  not just to compile and test?  I can't
> re-find
> > > the
> > > > > guidance on that having searched that apache site.
> > > > >
> > > > > The LICENSE file in binary distro contains CPL 1.0 twice,  once
> for
> > > > wsdl4j
> > > > > and then at the bottom for Jruby.
> > > > >
> > > > > It would be really helpful to include a package.html file for each
> > > > package
> > > > > so that the javadoc gives an overview of what each package does.
> > > > >
> > > > > Cheers, Kelvin.
> > > > >
> > > > >
> > > > > On 20/05/07, ant elder < ant.elder@gmail.com> wrote:
> > > > > >
> > > > > > Please review and vote on the 0.90 release artifacts of Tuscany
> > SCA
> > > > for
> > > > > > Java.
> > > > > >
> > > > > > The artifacts are available for review at:
> > > > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/<http://people.apache.org/%7Eantelder/tuscany/0.90-rc1/>
> > > > > >
> > > > > > This includes the binary and source distributions, the RAT
> > reports,
> > > > and
> > > > > > the
> > > > > > Maven staging repository.
> > > > > >
> > > > > > The SVN tag for the release is:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> > > > > >
> > > > > > Looks ok to me so here's my +1.
> > > > > >
> > > > > > Thanks in advance,
> > > > > >
> > > > > >    ...ant
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > Apache Tuscany Committer
> > > http://people.apache.org/~lresende<http://people.apache.org/%7Elresende>
> > > http://lresende.blogspot.com/
> > >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[kelvin goodson <ke...@gmail.com>]

On 21/05/07, Luciano Resende <lu...@gmail.com> wrote:
>
> I have done necessary updates to STATUS page [1], and the Incubator
> Tuscany
> page [2]. Note that the changes on the incubator page takes a little while
> to get reflect on the live website.
>
> [1] https://svn.apache.org/repos/asf/incubator/tuscany/STATUS
> [2] http://incubator.apache.org/projects/tuscany.html


I just did another update to [1] to add the news about Andy Grove becoming a
committer,  but I don't know where the source for [2] is.  Can someone give
me a pointer please?

<snip/>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Luciano Resende <lu...@gmail.com>]

I have done necessary updates to STATUS page [1], and the Incubator Tuscany
page [2]. Note that the changes on the incubator page takes a little while
to get reflect on the live website.

[1] https://svn.apache.org/repos/asf/incubator/tuscany/STATUS
[2] http://incubator.apache.org/projects/tuscany.html


On 5/21/07, ant elder <an...@gmail.com> wrote:
>
> I don't think that document says we MUST include the STATUS document. It
> says "Check status document" meaning check that the STATUS doc doesn't say
> there are outstanding legal issues that may prevent a release. Even if
> that
> releasemanagement doc did say we must, the doc is still under development
> and in draft state so I'm not sure its binding policy. Given other recent
> incubator releases didn't include the STATUS doc and an IPMCer recently
> said
> it could be removed from a distro i think this is not a blocking issue.
>
>    ...ant
>
> On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
> >
> > Regarding the STATUS document, I think the policy say we must include
> > them,
> > check [1] on the "Release Documentation" and "STATUS document" sessions.
> > Also our STATUS file is not up to date, and I can take care of helping
> > updating that after I finish reviewing the rest of the release
> candidate.
> >
> > [1] - http://incubator.apache.org/guides/releasemanagement.html
> >
> > On 5/21/07, ant elder <an...@gmail.com> wrote:
> > >
> > > Hey many thanks for the prompt and detailed review.
> > >
> > > I can't remember exactly about the STATUS file, i think it may be an
> old
> > > requirement that is no longer necessary. I can find this
> > incubator-general
> > > email [1] about the recent CXF release which included and old and
> > > incorrect
> > > status file, and the guidance from an IPMC member was its ok to just
> > > remove
> > > it from the distro, so i think its fine we don't include this.
> > >
> > > All these other comments seem like good things we should do in future,
> > if
> > > we
> > > do have to respin the 0.90 distro's for some other reason I'll try to
> > > incorporate some of them.
> > >
> > > Thanks,
> > >
> > >    ...ant
> > >
> > > [1]
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
> > >
> > > On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
> > > >
> > > > Ant,
> > > >   I've had a good poke around and built the source distro and run
> the
> > > > tests
> > > > successfully. The only potential blocking issue I have found is that
> > > > absence
> > > > of a STATUS file,  which it was my understanding should be copied in
> > > from
> > > > the project's STATUS file into every distribution,  but I haven't
> been
> > > > able
> > > > to re-find that guidance in the apache site. Can anyone help clarify
> > > this
> > > > please?
> > > >
> > > > The rest of these comments are all minor observations that wouldn't
> > stop
> > > > me
> > > > +1-ing the release.  Indeed, some of them may result in
> clarification
> > > that
> > > > what you have done is corrent and that will help SDO in future
> > releases?
> > > >
> > > > I've had comments in the past that Apache like it if the names of
> the
> > > > release file names include the "apache-" prefix
> > > >
> > > > I think the copyright in the NOTICES file at the top level of the
> > source
> > > > distro should include 2005
> > > >
> > > > I thought that the intention of the BUILDING file was to guide a
> > person
> > > > who
> > > > has downloaded the source distribution to be able to recreate the
> > > > distribution files,  not just to compile and test?  I can't re-find
> > the
> > > > guidance on that having searched that apache site.
> > > >
> > > > The LICENSE file in binary distro contains CPL 1.0 twice,  once for
> > > wsdl4j
> > > > and then at the bottom for Jruby.
> > > >
> > > > It would be really helpful to include a package.html file for each
> > > package
> > > > so that the javadoc gives an overview of what each package does.
> > > >
> > > > Cheers, Kelvin.
> > > >
> > > >
> > > > On 20/05/07, ant elder <an...@gmail.com> wrote:
> > > > >
> > > > > Please review and vote on the 0.90 release artifacts of Tuscany
> SCA
> > > for
> > > > > Java.
> > > > >
> > > > > The artifacts are available for review at:
> > > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> > > > >
> > > > > This includes the binary and source distributions, the RAT
> reports,
> > > and
> > > > > the
> > > > > Maven staging repository.
> > > > >
> > > > > The SVN tag for the release is:
> > > > >
> > > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> > > > >
> > > > > Looks ok to me so here's my +1.
> > > > >
> > > > > Thanks in advance,
> > > > >
> > > > >    ...ant
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany Committer
> > http://people.apache.org/~lresende
> > http://lresende.blogspot.com/
> >
>



-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Simon Nash <na...@hursley.ibm.com>]

This seems quite scary: "Release then Test".

Can't we use a staging maven respository to perform a pre-release
test?  Would this require extensive changes to POMs?

I'm at a conference this week and unfortunately I haven't been able
to give the release candidate a thorough review and workout.  I have
looked through the contents and tried a few samples.  I noticed a
minor problem with the javadoc, which isn't a showstopper for this
release.  The top-level docs/javadoc/index.html file only lists
the org.apache.tuscany.* packages.  It should also list the
org.osoa.sca.* packages.

   Simon

ant elder wrote:

> I think building the samples with mvn from an empty local mvn repo isn't
> going to work until we've actually released the 0.90 artifacts into the
> Incubator repository. The samples do define the Incubatory repository in
> their pom.xml's so it should work once released, but we can't easily 
> test it
> until then
> 
>   ...ant
> 
> On 5/23/07, Raymond Feng <en...@gmail.com> wrote:
> 
>>
>> Hi,
>>
>> I downloaded the 0.90 binary distro and unzipped it locally. I also
>> deleted
>> my local maven repo. Then when I follow the README in
>> tuscany-sca-0.90-incubating\samples\calculator to run "mvn" to build the
>> samples, I get the following error as appended later.
>>
>> Am I not supposed to build the sample this way since it's a binary 
>> distro?
>> I
>> can see the jar is pre-built.
>>
>> Other than that, the ant script works well to run the pre-built 
>> samples. I
>> think it is very nice for users to see the samples actually run in this
>> simple way.
>>
>> Thanks,
>> Raymond
>>
>> C:\Apache\tuscany-sca-0.90-incubating\samples\calculator>mvn
>> [INFO] Scanning for projects...
>> Downloading:
>> http://people.apache.org/repo/m2-incubating-repository/org/apache/t
>> uscany/sca/tuscany-sca/0.90-incubating/tuscany-sca-0.90-incubating.pom
>> Downloading:
>> http://repo1.maven.org/maven2/org/apache/tuscany/sca/tuscany-sca/0.
>> 90-incubating/tuscany-sca-0.90-incubating.pom
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error building POM (may not be this project's POM).
>>
>>
>> Project ID: null:sample-calculator:jar:null
>>
>> Reason: Cannot find parent: org.apache.tuscany.sca:tuscany-sca for
>> project:
>> null
>> :sample-calculator:jar:null
>>
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
>> org.apache
>> .tuscany.sca:tuscany-sca for project: null:sample-calculator:jar:null
>>         at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java
>> :378)
>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
>>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> java:64)
>>         at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> sorImpl.java:43)
>>         at java.lang.reflect.Method.invoke(Method.java:615)
>>         at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>         at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>
>>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
>> parent
>> : org.apache.tuscany.sca:tuscany-sca for project:
>> null:sample-calculator:jar:nul
>> l
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
>> efaultMavenProjectBuilder.java:1264)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def
>> aultMavenProjectBuilder.java:749)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
>> leInternal(DefaultMavenProjectBuilder.java:479)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
>> nProjectBuilder.java:200)
>>         at 
>> org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537)
>>         at
>> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
>>         at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java
>> :364)
>>         ... 11 more
>> Caused by: org.apache.maven.project.ProjectBuildingException: POM
>> 'org.apache.tu
>> scany.sca:tuscany-sca' not found in repository: Unable to download the
>> artifact
>> from any repository
>>
>>   org.apache.tuscany.sca:tuscany-sca:pom:0.90-incubating
>>
>> from the specified remote repositories:
>>   central (http://repo1.maven.org/maven2),
>>   apache.incubator 
>> (http://people.apache.org/repo/m2-incubating-repository
>> )
>>
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
>> sitory(DefaultMavenProjectBuilder.java:573)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
>> efaultMavenProjectBuilder.java:1260)
>>         ... 17 more
>> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
>> Unable
>> to download the artifact from any repository
>>
>>   org.apache.tuscany.sca:tuscany-sca:pom:0.90-incubating
>>
>> from the specified remote repositories:
>>   central (http://repo1.maven.org/maven2),
>>   apache.incubator 
>> (http://people.apache.org/repo/m2-incubating-repository
>> )
>>
>>         at
>> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
>> faultArtifactResolver.java:197)
>>         at
>> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
>> faultArtifactResolver.java:73)
>>         at
>> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
>> sitory(DefaultMavenProjectBuilder.java:526)
>>         ... 18 more
>> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: 
>> Unable to
>> downl
>> oad the artifact from any repository
>>         at
>> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
>> aultWagonManager.java:324)
>>         at
>> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
>> faultArtifactResolver.java:185)
>>         ... 20 more
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 3 seconds
>> [INFO] Finished at: Tue May 22 17:03:52 PDT 2007
>> [INFO] Final Memory: 2M/5M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> ----- Original Message -----
>> From: "ant elder" <an...@gmail.com>
>> To: <tu...@ws.apache.org>
>> Sent: Monday, May 21, 2007 1:13 PM
>> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
>>
>>
>> > Another very detailed review, thank you! Comments in line, but to
>> > summarise
>> > - there's an unclear sample readme, a broken sample readme, and some
>> > missing
>> > Javadoc. This isn't perfect, but are any of those blockers requiring 
>> the
>> > delay of another RC? I think not and its better to get this release out
>> > sooner than to delay and respin another RC, so my vote is still +1 on
>> > going
>> > with this RC, and we can fix those issues in the next release.
>> Completely
>> > open to other's opinions though so please say what you think.
>> >
>> >   ...ant
>> >
>> > On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
>> >>
>> >> Here are my findings around the 0.9 Release Candidate, my main concern
>> is
>> >> with the issues I mentioned in the modules directory of the source.
>> >>
>> >> Samples:
>> >> I have tried the standalone samples and the web samples (in jetty and
>> >> tomcat).
>> >> All samples look OK, with the exceptions of the ones mentioned below :
>> >>
>> >> calculator-rmi-reference - WARNING
>> >>
>> >> The README is confusing, by reading it, I was under the impression 
>> that
>> >> the
>> >> server and client were on the same project, and it also have the 
>> client
>> >> and
>> >> server ant xml files there. But in order to properly run the sample,
>> you
>> >> need to go to calculator-rmi-service and actually start the server
>> there,
>> >> then come to the reference (client)
>> >>
>> >> D:\temp\0.9 Release\tuscany-
>> >> sca-0.90-incubating\samples\calculator-rmi-reference>ant -f
>> >> build-server.xmlrun
>> >> Buildfile: build-server.xml
>> >>
>> >> run:
>> >>      [java] java.lang.NoClassDefFoundError: 
>> calculator/CalculatorServer
>> >>      [java] Exception in thread "main"
>> >>      [java] Java Result: 1
>> >
>> >
>> > Looks like a cutNpaste problem between the service and client readme's,
>> i
>> > agree this makes it confusing.
>> >
>> > implementation-crud-client - ERROR
>> >>
>> >> Looks like the ant.xml property has the wrong package, I have fixed
>> this
>> >> in
>> >> the branch and trunk
>> >> after adding the right package, it works
>> >>     <property name="test.class" value="crud.client.CRUDClient" />
>> >>
>> >> D:\temp\0.9 Release\tuscany-
>> >> sca-0.90-incubating\samples\implementation-crud-client>ant run
>> >> Buildfile: build.xml
>> >>
>> >> run:
>> >>      [java] java.lang.NoClassDefFoundError: crud/CRUDClient
>> >>      [java] Exception in thread "main"
>> >>      [java] Java Result: 1
>> >
>> >
>> > Yep, this one is broken. I guess after all the last minute changes to
>> the
>> > way the extension samples were like.
>> >
>> > Source Modules
>> >>
>> >> itest\interop-soap-client -> pom version has SNAPSHOT
>> >> itest\interop-soap-round2-client -> pom version has SNAPSHOT
>> >> itest\interop-soap-service -> pom version has SNAPSHOT
>> >>    -> reference axion snapshot
>> >>    -> reference axion-impl snapshot
>> >> itest\interop-xsq-client -> pom version has SNAPSHOT
>> >>    -> still has varios scdl files
>> >>
>> >> modules\binding-jms --> are we shipping that ? still have SCDL files
>> with
>> >> references to snapshot, wsdl also reference snapshot
>> >> modules\discovery-jms --> are we shipping that ? If so, it has 
>> SNAPSHOT
>> >> version on it
>> >>
>> >> modules\binding-ws-xml -> test1.wsdl references snapshot
>> >> (<wsdlsoap:address
>> >> location="
>> >>
>> >>
>> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService 
>>
>> >> "
>> >> />)
>> >>
>> >> modules\contribution-impl -> namespace defined as NS = "
>> >> http://tuscany.apache.org/xmlns/1.0-SNAPSHOT";
>> >>
>> >> modules\interface-wsdl-xml -> test1.wsdl andpoing  references snapshot
>> >> (<wsdlsoap:address location="
>> >>
>> >>
>> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService 
>>
>> >> "
>> >> />)
>> >
>> >
>> > None of those are significant IMHO as either they're not included in 
>> the
>> > build or the reference to snapshot is not actually used at runtime.
>> >
>> > Javadoc
>> >>
>> >> Just a subset of packages javadoc was generated, I don't see
>> contribution
>> >> javadoc available... Is this ok ?
>> >
>> >
>> > Another flaw, ideally we'd have Javadoc for every package we said 
>> was an
>> > API
>> > or SPI.
>> >
>> > Binaries
>> >>
>> >> We have a dependency on JRuby release candidate
>> >> (jruby-complete-1.0RC2.jar
>> >> )
>> >> ? Is that ok ?
>> >
>> >
>> > Thats fine, its just SNAPSHOT build we shouldn't release with.
>> >
>> > On 5/21/07, ant elder <an...@gmail.com> wrote:
>> >> >
>> >> > I don't think that document says we MUST include the STATUS 
>> document.
>> >> > It
>> >> > says "Check status document" meaning check that the STATUS doc
>> doesn't
>> >> say
>> >> > there are outstanding legal issues that may prevent a release. Even
>> if
>> >> > that
>> >> > releasemanagement doc did say we must, the doc is still under
>> >> development
>> >> > and in draft state so I'm not sure its binding policy. Given other
>> >> recent
>> >> > incubator releases didn't include the STATUS doc and an IPMCer
>> recently
>> >> > said
>> >> > it could be removed from a distro i think this is not a blocking
>> issue.
>> >> >
>> >> >    ...ant
>> >> >
>> >> > On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
>> >> > >
>> >> > > Regarding the STATUS document, I think the policy say we must
>> include
>> >> > > them,
>> >> > > check [1] on the "Release Documentation" and "STATUS document"
>> >> sessions.
>> >> > > Also our STATUS file is not up to date, and I can take care of
>> >> > > helping
>> >> > > updating that after I finish reviewing the rest of the release
>> >> > candidate.
>> >> > >
>> >> > > [1] - http://incubator.apache.org/guides/releasemanagement.html
>> >> > >
>> >> > > On 5/21/07, ant elder <an...@gmail.com> wrote:
>> >> > > >
>> >> > > > Hey many thanks for the prompt and detailed review.
>> >> > > >
>> >> > > > I can't remember exactly about the STATUS file, i think it 
>> may be
>> >> > > > an
>> >> > old
>> >> > > > requirement that is no longer necessary. I can find this
>> >> > > incubator-general
>> >> > > > email [1] about the recent CXF release which included and old 
>> and
>> >> > > > incorrect
>> >> > > > status file, and the guidance from an IPMC member was its ok to
>> >> > > > just
>> >> > > > remove
>> >> > > > it from the distro, so i think its fine we don't include this.
>> >> > > >
>> >> > > > All these other comments seem like good things we should do in
>> >> future,
>> >> > > if
>> >> > > > we
>> >> > > > do have to respin the 0.90 distro's for some other reason I'll
>> try
>> >> to
>> >> > > > incorporate some of them.
>> >> > > >
>> >> > > > Thanks,
>> >> > > >
>> >> > > >    ...ant
>> >> > > >
>> >> > > > [1]
>> >> > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e 
>>
>> >> > > >
>> >> > > > On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
>> >> > > > >
>> >> > > > > Ant,
>> >> > > > >   I've had a good poke around and built the source distro and
>> run
>> >> > the
>> >> > > > > tests
>> >> > > > > successfully. The only potential blocking issue I have 
>> found is
>> >> that
>> >> > > > > absence
>> >> > > > > of a STATUS file,  which it was my understanding should be
>> copied
>> >> in
>> >> > > > from
>> >> > > > > the project's STATUS file into every distribution,  but I
>> haven't
>> >> > been
>> >> > > > > able
>> >> > > > > to re-find that guidance in the apache site. Can anyone help
>> >> clarify
>> >> > > > this
>> >> > > > > please?
>> >> > > > >
>> >> > > > > The rest of these comments are all minor observations that
>> >> wouldn't
>> >> > > stop
>> >> > > > > me
>> >> > > > > +1-ing the release.  Indeed, some of them may result in
>> >> > clarification
>> >> > > > that
>> >> > > > > what you have done is corrent and that will help SDO in future
>> >> > > releases?
>> >> > > > >
>> >> > > > > I've had comments in the past that Apache like it if the names
>> of
>> >> > the
>> >> > > > > release file names include the "apache-" prefix
>> >> > > > >
>> >> > > > > I think the copyright in the NOTICES file at the top level of
>> the
>> >> > > source
>> >> > > > > distro should include 2005
>> >> > > > >
>> >> > > > > I thought that the intention of the BUILDING file was to guide
>> a
>> >> > > person
>> >> > > > > who
>> >> > > > > has downloaded the source distribution to be able to recreate
>> the
>> >> > > > > distribution files,  not just to compile and test?  I can't
>> >> re-find
>> >> > > the
>> >> > > > > guidance on that having searched that apache site.
>> >> > > > >
>> >> > > > > The LICENSE file in binary distro contains CPL 1.0 twice,  
>> once
>> >> for
>> >> > > > wsdl4j
>> >> > > > > and then at the bottom for Jruby.
>> >> > > > >
>> >> > > > > It would be really helpful to include a package.html file for
>> >> > > > > each
>> >> > > > package
>> >> > > > > so that the javadoc gives an overview of what each package
>> does.
>> >> > > > >
>> >> > > > > Cheers, Kelvin.
>> >> > > > >
>> >> > > > >
>> >> > > > > On 20/05/07, ant elder <an...@gmail.com> wrote:
>> >> > > > > >
>> >> > > > > > Please review and vote on the 0.90 release artifacts of
>> Tuscany
>> >> > SCA
>> >> > > > for
>> >> > > > > > Java.
>> >> > > > > >
>> >> > > > > > The artifacts are available for review at:
>> >> > > > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
>> >> > > > > >
>> >> > > > > > This includes the binary and source distributions, the RAT
>> >> > reports,
>> >> > > > and
>> >> > > > > > the
>> >> > > > > > Maven staging repository.
>> >> > > > > >
>> >> > > > > > The SVN tag for the release is:
>> >> > > > > >
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ 
>>
>> >> > > > > >
>> >> > > > > > Looks ok to me so here's my +1.
>> >> > > > > >
>> >> > > > > > Thanks in advance,
>> >> > > > > >
>> >> > > > > >    ...ant
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Luciano Resende
>> >> > > Apache Tuscany Committer
>> >> > > http://people.apache.org/~lresende
>> >> > > http://lresende.blogspot.com/
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Luciano Resende
>> >> Apache Tuscany Committer
>> >> http://people.apache.org/~lresende
>> >> http://lresende.blogspot.com/
>> >>
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
> 

-- 
Simon C Nash   IBM Distinguished Engineer
Hursley Park, Winchester, UK   nash@hursley.ibm.com
Tel. +44-1962-815156   Fax +44-1962-818999


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

I think building the samples with mvn from an empty local mvn repo isn't
going to work until we've actually released the 0.90 artifacts into the
Incubator repository. The samples do define the Incubatory repository in
their pom.xml's so it should work once released, but we can't easily test it
until then

   ...ant

On 5/23/07, Raymond Feng <en...@gmail.com> wrote:
>
> Hi,
>
> I downloaded the 0.90 binary distro and unzipped it locally. I also
> deleted
> my local maven repo. Then when I follow the README in
> tuscany-sca-0.90-incubating\samples\calculator to run "mvn" to build the
> samples, I get the following error as appended later.
>
> Am I not supposed to build the sample this way since it's a binary distro?
> I
> can see the jar is pre-built.
>
> Other than that, the ant script works well to run the pre-built samples. I
> think it is very nice for users to see the samples actually run in this
> simple way.
>
> Thanks,
> Raymond
>
> C:\Apache\tuscany-sca-0.90-incubating\samples\calculator>mvn
> [INFO] Scanning for projects...
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/t
> uscany/sca/tuscany-sca/0.90-incubating/tuscany-sca-0.90-incubating.pom
> Downloading:
> http://repo1.maven.org/maven2/org/apache/tuscany/sca/tuscany-sca/0.
> 90-incubating/tuscany-sca-0.90-incubating.pom
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: null:sample-calculator:jar:null
>
> Reason: Cannot find parent: org.apache.tuscany.sca:tuscany-sca for
> project:
> null
> :sample-calculator:jar:null
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> org.apache
> .tuscany.sca:tuscany-sca for project: null:sample-calculator:jar:null
>         at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java
> :378)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:615)
>         at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
> parent
> : org.apache.tuscany.sca:tuscany-sca for project:
> null:sample-calculator:jar:nul
> l
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
> efaultMavenProjectBuilder.java:1264)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def
> aultMavenProjectBuilder.java:749)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
> leInternal(DefaultMavenProjectBuilder.java:479)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
> nProjectBuilder.java:200)
>         at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537)
>         at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
>         at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java
> :364)
>         ... 11 more
> Caused by: org.apache.maven.project.ProjectBuildingException: POM
> 'org.apache.tu
> scany.sca:tuscany-sca' not found in repository: Unable to download the
> artifact
> from any repository
>
>   org.apache.tuscany.sca:tuscany-sca:pom:0.90-incubating
>
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   apache.incubator (http://people.apache.org/repo/m2-incubating-repository
> )
>
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
> sitory(DefaultMavenProjectBuilder.java:573)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
> efaultMavenProjectBuilder.java:1260)
>         ... 17 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> Unable
> to download the artifact from any repository
>
>   org.apache.tuscany.sca:tuscany-sca:pom:0.90-incubating
>
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   apache.incubator (http://people.apache.org/repo/m2-incubating-repository
> )
>
>         at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
> faultArtifactResolver.java:197)
>         at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
> faultArtifactResolver.java:73)
>         at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
> sitory(DefaultMavenProjectBuilder.java:526)
>         ... 18 more
> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
> downl
> oad the artifact from any repository
>         at
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
> aultWagonManager.java:324)
>         at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
> faultArtifactResolver.java:185)
>         ... 20 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Tue May 22 17:03:52 PDT 2007
> [INFO] Final Memory: 2M/5M
> [INFO]
> ------------------------------------------------------------------------
>
> ----- Original Message -----
> From: "ant elder" <an...@gmail.com>
> To: <tu...@ws.apache.org>
> Sent: Monday, May 21, 2007 1:13 PM
> Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
>
>
> > Another very detailed review, thank you! Comments in line, but to
> > summarise
> > - there's an unclear sample readme, a broken sample readme, and some
> > missing
> > Javadoc. This isn't perfect, but are any of those blockers requiring the
> > delay of another RC? I think not and its better to get this release out
> > sooner than to delay and respin another RC, so my vote is still +1 on
> > going
> > with this RC, and we can fix those issues in the next release.
> Completely
> > open to other's opinions though so please say what you think.
> >
> >   ...ant
> >
> > On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
> >>
> >> Here are my findings around the 0.9 Release Candidate, my main concern
> is
> >> with the issues I mentioned in the modules directory of the source.
> >>
> >> Samples:
> >> I have tried the standalone samples and the web samples (in jetty and
> >> tomcat).
> >> All samples look OK, with the exceptions of the ones mentioned below :
> >>
> >> calculator-rmi-reference - WARNING
> >>
> >> The README is confusing, by reading it, I was under the impression that
> >> the
> >> server and client were on the same project, and it also have the client
> >> and
> >> server ant xml files there. But in order to properly run the sample,
> you
> >> need to go to calculator-rmi-service and actually start the server
> there,
> >> then come to the reference (client)
> >>
> >> D:\temp\0.9 Release\tuscany-
> >> sca-0.90-incubating\samples\calculator-rmi-reference>ant -f
> >> build-server.xmlrun
> >> Buildfile: build-server.xml
> >>
> >> run:
> >>      [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer
> >>      [java] Exception in thread "main"
> >>      [java] Java Result: 1
> >
> >
> > Looks like a cutNpaste problem between the service and client readme's,
> i
> > agree this makes it confusing.
> >
> > implementation-crud-client - ERROR
> >>
> >> Looks like the ant.xml property has the wrong package, I have fixed
> this
> >> in
> >> the branch and trunk
> >> after adding the right package, it works
> >>     <property name="test.class" value="crud.client.CRUDClient" />
> >>
> >> D:\temp\0.9 Release\tuscany-
> >> sca-0.90-incubating\samples\implementation-crud-client>ant run
> >> Buildfile: build.xml
> >>
> >> run:
> >>      [java] java.lang.NoClassDefFoundError: crud/CRUDClient
> >>      [java] Exception in thread "main"
> >>      [java] Java Result: 1
> >
> >
> > Yep, this one is broken. I guess after all the last minute changes to
> the
> > way the extension samples were like.
> >
> > Source Modules
> >>
> >> itest\interop-soap-client -> pom version has SNAPSHOT
> >> itest\interop-soap-round2-client -> pom version has SNAPSHOT
> >> itest\interop-soap-service -> pom version has SNAPSHOT
> >>    -> reference axion snapshot
> >>    -> reference axion-impl snapshot
> >> itest\interop-xsq-client -> pom version has SNAPSHOT
> >>    -> still has varios scdl files
> >>
> >> modules\binding-jms --> are we shipping that ? still have SCDL files
> with
> >> references to snapshot, wsdl also reference snapshot
> >> modules\discovery-jms --> are we shipping that ? If so, it has SNAPSHOT
> >> version on it
> >>
> >> modules\binding-ws-xml -> test1.wsdl references snapshot
> >> (<wsdlsoap:address
> >> location="
> >>
> >>
> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService
> >> "
> >> />)
> >>
> >> modules\contribution-impl -> namespace defined as NS = "
> >> http://tuscany.apache.org/xmlns/1.0-SNAPSHOT";
> >>
> >> modules\interface-wsdl-xml -> test1.wsdl andpoing  references snapshot
> >> (<wsdlsoap:address location="
> >>
> >>
> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService
> >> "
> >> />)
> >
> >
> > None of those are significant IMHO as either they're not included in the
> > build or the reference to snapshot is not actually used at runtime.
> >
> > Javadoc
> >>
> >> Just a subset of packages javadoc was generated, I don't see
> contribution
> >> javadoc available... Is this ok ?
> >
> >
> > Another flaw, ideally we'd have Javadoc for every package we said was an
> > API
> > or SPI.
> >
> > Binaries
> >>
> >> We have a dependency on JRuby release candidate
> >> (jruby-complete-1.0RC2.jar
> >> )
> >> ? Is that ok ?
> >
> >
> > Thats fine, its just SNAPSHOT build we shouldn't release with.
> >
> > On 5/21/07, ant elder <an...@gmail.com> wrote:
> >> >
> >> > I don't think that document says we MUST include the STATUS document.
> >> > It
> >> > says "Check status document" meaning check that the STATUS doc
> doesn't
> >> say
> >> > there are outstanding legal issues that may prevent a release. Even
> if
> >> > that
> >> > releasemanagement doc did say we must, the doc is still under
> >> development
> >> > and in draft state so I'm not sure its binding policy. Given other
> >> recent
> >> > incubator releases didn't include the STATUS doc and an IPMCer
> recently
> >> > said
> >> > it could be removed from a distro i think this is not a blocking
> issue.
> >> >
> >> >    ...ant
> >> >
> >> > On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
> >> > >
> >> > > Regarding the STATUS document, I think the policy say we must
> include
> >> > > them,
> >> > > check [1] on the "Release Documentation" and "STATUS document"
> >> sessions.
> >> > > Also our STATUS file is not up to date, and I can take care of
> >> > > helping
> >> > > updating that after I finish reviewing the rest of the release
> >> > candidate.
> >> > >
> >> > > [1] - http://incubator.apache.org/guides/releasemanagement.html
> >> > >
> >> > > On 5/21/07, ant elder <an...@gmail.com> wrote:
> >> > > >
> >> > > > Hey many thanks for the prompt and detailed review.
> >> > > >
> >> > > > I can't remember exactly about the STATUS file, i think it may be
> >> > > > an
> >> > old
> >> > > > requirement that is no longer necessary. I can find this
> >> > > incubator-general
> >> > > > email [1] about the recent CXF release which included and old and
> >> > > > incorrect
> >> > > > status file, and the guidance from an IPMC member was its ok to
> >> > > > just
> >> > > > remove
> >> > > > it from the distro, so i think its fine we don't include this.
> >> > > >
> >> > > > All these other comments seem like good things we should do in
> >> future,
> >> > > if
> >> > > > we
> >> > > > do have to respin the 0.90 distro's for some other reason I'll
> try
> >> to
> >> > > > incorporate some of them.
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > >    ...ant
> >> > > >
> >> > > > [1]
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
> >> > > >
> >> > > > On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
> >> > > > >
> >> > > > > Ant,
> >> > > > >   I've had a good poke around and built the source distro and
> run
> >> > the
> >> > > > > tests
> >> > > > > successfully. The only potential blocking issue I have found is
> >> that
> >> > > > > absence
> >> > > > > of a STATUS file,  which it was my understanding should be
> copied
> >> in
> >> > > > from
> >> > > > > the project's STATUS file into every distribution,  but I
> haven't
> >> > been
> >> > > > > able
> >> > > > > to re-find that guidance in the apache site. Can anyone help
> >> clarify
> >> > > > this
> >> > > > > please?
> >> > > > >
> >> > > > > The rest of these comments are all minor observations that
> >> wouldn't
> >> > > stop
> >> > > > > me
> >> > > > > +1-ing the release.  Indeed, some of them may result in
> >> > clarification
> >> > > > that
> >> > > > > what you have done is corrent and that will help SDO in future
> >> > > releases?
> >> > > > >
> >> > > > > I've had comments in the past that Apache like it if the names
> of
> >> > the
> >> > > > > release file names include the "apache-" prefix
> >> > > > >
> >> > > > > I think the copyright in the NOTICES file at the top level of
> the
> >> > > source
> >> > > > > distro should include 2005
> >> > > > >
> >> > > > > I thought that the intention of the BUILDING file was to guide
> a
> >> > > person
> >> > > > > who
> >> > > > > has downloaded the source distribution to be able to recreate
> the
> >> > > > > distribution files,  not just to compile and test?  I can't
> >> re-find
> >> > > the
> >> > > > > guidance on that having searched that apache site.
> >> > > > >
> >> > > > > The LICENSE file in binary distro contains CPL 1.0 twice,  once
> >> for
> >> > > > wsdl4j
> >> > > > > and then at the bottom for Jruby.
> >> > > > >
> >> > > > > It would be really helpful to include a package.html file for
> >> > > > > each
> >> > > > package
> >> > > > > so that the javadoc gives an overview of what each package
> does.
> >> > > > >
> >> > > > > Cheers, Kelvin.
> >> > > > >
> >> > > > >
> >> > > > > On 20/05/07, ant elder <an...@gmail.com> wrote:
> >> > > > > >
> >> > > > > > Please review and vote on the 0.90 release artifacts of
> Tuscany
> >> > SCA
> >> > > > for
> >> > > > > > Java.
> >> > > > > >
> >> > > > > > The artifacts are available for review at:
> >> > > > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> >> > > > > >
> >> > > > > > This includes the binary and source distributions, the RAT
> >> > reports,
> >> > > > and
> >> > > > > > the
> >> > > > > > Maven staging repository.
> >> > > > > >
> >> > > > > > The SVN tag for the release is:
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> >> > > > > >
> >> > > > > > Looks ok to me so here's my +1.
> >> > > > > >
> >> > > > > > Thanks in advance,
> >> > > > > >
> >> > > > > >    ...ant
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Luciano Resende
> >> > > Apache Tuscany Committer
> >> > > http://people.apache.org/~lresende
> >> > > http://lresende.blogspot.com/
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Luciano Resende
> >> Apache Tuscany Committer
> >> http://people.apache.org/~lresende
> >> http://lresende.blogspot.com/
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Raymond Feng <en...@gmail.com>]

Hi,

I downloaded the 0.90 binary distro and unzipped it locally. I also deleted 
my local maven repo. Then when I follow the README in 
tuscany-sca-0.90-incubating\samples\calculator to run "mvn" to build the 
samples, I get the following error as appended later.

Am I not supposed to build the sample this way since it's a binary distro? I 
can see the jar is pre-built.

Other than that, the ant script works well to run the pre-built samples. I 
think it is very nice for users to see the samples actually run in this 
simple way.

Thanks,
Raymond

C:\Apache\tuscany-sca-0.90-incubating\samples\calculator>mvn
[INFO] Scanning for projects...
Downloading: 
http://people.apache.org/repo/m2-incubating-repository/org/apache/t
uscany/sca/tuscany-sca/0.90-incubating/tuscany-sca-0.90-incubating.pom
Downloading: 
http://repo1.maven.org/maven2/org/apache/tuscany/sca/tuscany-sca/0.
90-incubating/tuscany-sca-0.90-incubating.pom
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: null:sample-calculator:jar:null

Reason: Cannot find parent: org.apache.tuscany.sca:tuscany-sca for project: 
null
:sample-calculator:jar:null


[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: 
org.apache
.tuscany.sca:tuscany-sca for project: null:sample-calculator:jar:null
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:615)
        at 
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at 
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent
: org.apache.tuscany.sca:tuscany-sca for project: 
null:sample-calculator:jar:nul
l
        at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
efaultMavenProjectBuilder.java:1264)
        at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def
aultMavenProjectBuilder.java:749)
        at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
leInternal(DefaultMavenProjectBuilder.java:479)
        at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
nProjectBuilder.java:200)
        at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537)
        at 
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364)
        ... 11 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.tu
scany.sca:tuscany-sca' not found in repository: Unable to download the 
artifact
from any repository

  org.apache.tuscany.sca:tuscany-sca:pom:0.90-incubating

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.incubator (http://people.apache.org/repo/m2-incubating-repository)

        at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
sitory(DefaultMavenProjectBuilder.java:573)
        at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
efaultMavenProjectBuilder.java:1260)
        ... 17 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: 
Unable
to download the artifact from any repository

  org.apache.tuscany.sca:tuscany-sca:pom:0.90-incubating

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.incubator (http://people.apache.org/repo/m2-incubating-repository)

        at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:197)
        at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:73)
        at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
sitory(DefaultMavenProjectBuilder.java:526)
        ... 18 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
downl
oad the artifact from any repository
        at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
aultWagonManager.java:324)
        at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:185)
        ... 20 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Tue May 22 17:03:52 PDT 2007
[INFO] Final Memory: 2M/5M
[INFO] ------------------------------------------------------------------------

----- Original Message ----- 
From: "ant elder" <an...@gmail.com>
To: <tu...@ws.apache.org>
Sent: Monday, May 21, 2007 1:13 PM
Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating


> Another very detailed review, thank you! Comments in line, but to 
> summarise
> - there's an unclear sample readme, a broken sample readme, and some 
> missing
> Javadoc. This isn't perfect, but are any of those blockers requiring the
> delay of another RC? I think not and its better to get this release out
> sooner than to delay and respin another RC, so my vote is still +1 on 
> going
> with this RC, and we can fix those issues in the next release. Completely
> open to other's opinions though so please say what you think.
>
>   ...ant
>
> On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
>>
>> Here are my findings around the 0.9 Release Candidate, my main concern is
>> with the issues I mentioned in the modules directory of the source.
>>
>> Samples:
>> I have tried the standalone samples and the web samples (in jetty and
>> tomcat).
>> All samples look OK, with the exceptions of the ones mentioned below :
>>
>> calculator-rmi-reference - WARNING
>>
>> The README is confusing, by reading it, I was under the impression that
>> the
>> server and client were on the same project, and it also have the client
>> and
>> server ant xml files there. But in order to properly run the sample, you
>> need to go to calculator-rmi-service and actually start the server there,
>> then come to the reference (client)
>>
>> D:\temp\0.9 Release\tuscany-
>> sca-0.90-incubating\samples\calculator-rmi-reference>ant -f
>> build-server.xmlrun
>> Buildfile: build-server.xml
>>
>> run:
>>      [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer
>>      [java] Exception in thread "main"
>>      [java] Java Result: 1
>
>
> Looks like a cutNpaste problem between the service and client readme's, i
> agree this makes it confusing.
>
> implementation-crud-client - ERROR
>>
>> Looks like the ant.xml property has the wrong package, I have fixed this
>> in
>> the branch and trunk
>> after adding the right package, it works
>>     <property name="test.class" value="crud.client.CRUDClient" />
>>
>> D:\temp\0.9 Release\tuscany-
>> sca-0.90-incubating\samples\implementation-crud-client>ant run
>> Buildfile: build.xml
>>
>> run:
>>      [java] java.lang.NoClassDefFoundError: crud/CRUDClient
>>      [java] Exception in thread "main"
>>      [java] Java Result: 1
>
>
> Yep, this one is broken. I guess after all the last minute changes to the
> way the extension samples were like.
>
> Source Modules
>>
>> itest\interop-soap-client -> pom version has SNAPSHOT
>> itest\interop-soap-round2-client -> pom version has SNAPSHOT
>> itest\interop-soap-service -> pom version has SNAPSHOT
>>    -> reference axion snapshot
>>    -> reference axion-impl snapshot
>> itest\interop-xsq-client -> pom version has SNAPSHOT
>>    -> still has varios scdl files
>>
>> modules\binding-jms --> are we shipping that ? still have SCDL files with
>> references to snapshot, wsdl also reference snapshot
>> modules\discovery-jms --> are we shipping that ? If so, it has SNAPSHOT
>> version on it
>>
>> modules\binding-ws-xml -> test1.wsdl references snapshot
>> (<wsdlsoap:address
>> location="
>>
>> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService
>> "
>> />)
>>
>> modules\contribution-impl -> namespace defined as NS = "
>> http://tuscany.apache.org/xmlns/1.0-SNAPSHOT";
>>
>> modules\interface-wsdl-xml -> test1.wsdl andpoing  references snapshot
>> (<wsdlsoap:address location="
>>
>> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService
>> "
>> />)
>
>
> None of those are significant IMHO as either they're not included in the
> build or the reference to snapshot is not actually used at runtime.
>
> Javadoc
>>
>> Just a subset of packages javadoc was generated, I don't see contribution
>> javadoc available... Is this ok ?
>
>
> Another flaw, ideally we'd have Javadoc for every package we said was an 
> API
> or SPI.
>
> Binaries
>>
>> We have a dependency on JRuby release candidate 
>> (jruby-complete-1.0RC2.jar
>> )
>> ? Is that ok ?
>
>
> Thats fine, its just SNAPSHOT build we shouldn't release with.
>
> On 5/21/07, ant elder <an...@gmail.com> wrote:
>> >
>> > I don't think that document says we MUST include the STATUS document. 
>> > It
>> > says "Check status document" meaning check that the STATUS doc doesn't
>> say
>> > there are outstanding legal issues that may prevent a release. Even if
>> > that
>> > releasemanagement doc did say we must, the doc is still under
>> development
>> > and in draft state so I'm not sure its binding policy. Given other
>> recent
>> > incubator releases didn't include the STATUS doc and an IPMCer recently
>> > said
>> > it could be removed from a distro i think this is not a blocking issue.
>> >
>> >    ...ant
>> >
>> > On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
>> > >
>> > > Regarding the STATUS document, I think the policy say we must include
>> > > them,
>> > > check [1] on the "Release Documentation" and "STATUS document"
>> sessions.
>> > > Also our STATUS file is not up to date, and I can take care of 
>> > > helping
>> > > updating that after I finish reviewing the rest of the release
>> > candidate.
>> > >
>> > > [1] - http://incubator.apache.org/guides/releasemanagement.html
>> > >
>> > > On 5/21/07, ant elder <an...@gmail.com> wrote:
>> > > >
>> > > > Hey many thanks for the prompt and detailed review.
>> > > >
>> > > > I can't remember exactly about the STATUS file, i think it may be 
>> > > > an
>> > old
>> > > > requirement that is no longer necessary. I can find this
>> > > incubator-general
>> > > > email [1] about the recent CXF release which included and old and
>> > > > incorrect
>> > > > status file, and the guidance from an IPMC member was its ok to 
>> > > > just
>> > > > remove
>> > > > it from the distro, so i think its fine we don't include this.
>> > > >
>> > > > All these other comments seem like good things we should do in
>> future,
>> > > if
>> > > > we
>> > > > do have to respin the 0.90 distro's for some other reason I'll try
>> to
>> > > > incorporate some of them.
>> > > >
>> > > > Thanks,
>> > > >
>> > > >    ...ant
>> > > >
>> > > > [1]
>> > > >
>> > > >
>> > >
>> >
>> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
>> > > >
>> > > > On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
>> > > > >
>> > > > > Ant,
>> > > > >   I've had a good poke around and built the source distro and run
>> > the
>> > > > > tests
>> > > > > successfully. The only potential blocking issue I have found is
>> that
>> > > > > absence
>> > > > > of a STATUS file,  which it was my understanding should be copied
>> in
>> > > > from
>> > > > > the project's STATUS file into every distribution,  but I haven't
>> > been
>> > > > > able
>> > > > > to re-find that guidance in the apache site. Can anyone help
>> clarify
>> > > > this
>> > > > > please?
>> > > > >
>> > > > > The rest of these comments are all minor observations that
>> wouldn't
>> > > stop
>> > > > > me
>> > > > > +1-ing the release.  Indeed, some of them may result in
>> > clarification
>> > > > that
>> > > > > what you have done is corrent and that will help SDO in future
>> > > releases?
>> > > > >
>> > > > > I've had comments in the past that Apache like it if the names of
>> > the
>> > > > > release file names include the "apache-" prefix
>> > > > >
>> > > > > I think the copyright in the NOTICES file at the top level of the
>> > > source
>> > > > > distro should include 2005
>> > > > >
>> > > > > I thought that the intention of the BUILDING file was to guide a
>> > > person
>> > > > > who
>> > > > > has downloaded the source distribution to be able to recreate the
>> > > > > distribution files,  not just to compile and test?  I can't
>> re-find
>> > > the
>> > > > > guidance on that having searched that apache site.
>> > > > >
>> > > > > The LICENSE file in binary distro contains CPL 1.0 twice,  once
>> for
>> > > > wsdl4j
>> > > > > and then at the bottom for Jruby.
>> > > > >
>> > > > > It would be really helpful to include a package.html file for 
>> > > > > each
>> > > > package
>> > > > > so that the javadoc gives an overview of what each package does.
>> > > > >
>> > > > > Cheers, Kelvin.
>> > > > >
>> > > > >
>> > > > > On 20/05/07, ant elder <an...@gmail.com> wrote:
>> > > > > >
>> > > > > > Please review and vote on the 0.90 release artifacts of Tuscany
>> > SCA
>> > > > for
>> > > > > > Java.
>> > > > > >
>> > > > > > The artifacts are available for review at:
>> > > > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
>> > > > > >
>> > > > > > This includes the binary and source distributions, the RAT
>> > reports,
>> > > > and
>> > > > > > the
>> > > > > > Maven staging repository.
>> > > > > >
>> > > > > > The SVN tag for the release is:
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
>> > > > > >
>> > > > > > Looks ok to me so here's my +1.
>> > > > > >
>> > > > > > Thanks in advance,
>> > > > > >
>> > > > > >    ...ant
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Luciano Resende
>> > > Apache Tuscany Committer
>> > > http://people.apache.org/~lresende
>> > > http://lresende.blogspot.com/
>> > >
>> >
>>
>>
>>
>> --
>> Luciano Resende
>> Apache Tuscany Committer
>> http://people.apache.org/~lresende
>> http://lresende.blogspot.com/
>>
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

Another very detailed review, thank you! Comments in line, but to summarise
- there's an unclear sample readme, a broken sample readme, and some missing
Javadoc. This isn't perfect, but are any of those blockers requiring the
delay of another RC? I think not and its better to get this release out
sooner than to delay and respin another RC, so my vote is still +1 on going
with this RC, and we can fix those issues in the next release. Completely
open to other's opinions though so please say what you think.

   ...ant

On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
>
> Here are my findings around the 0.9 Release Candidate, my main concern is
> with the issues I mentioned in the modules directory of the source.
>
> Samples:
> I have tried the standalone samples and the web samples (in jetty and
> tomcat).
> All samples look OK, with the exceptions of the ones mentioned below :
>
> calculator-rmi-reference - WARNING
>
> The README is confusing, by reading it, I was under the impression that
> the
> server and client were on the same project, and it also have the client
> and
> server ant xml files there. But in order to properly run the sample, you
> need to go to calculator-rmi-service and actually start the server there,
> then come to the reference (client)
>
> D:\temp\0.9 Release\tuscany-
> sca-0.90-incubating\samples\calculator-rmi-reference>ant -f
> build-server.xmlrun
> Buildfile: build-server.xml
>
> run:
>      [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer
>      [java] Exception in thread "main"
>      [java] Java Result: 1


Looks like a cutNpaste problem between the service and client readme's, i
agree this makes it confusing.

implementation-crud-client - ERROR
>
> Looks like the ant.xml property has the wrong package, I have fixed this
> in
> the branch and trunk
> after adding the right package, it works
>     <property name="test.class" value="crud.client.CRUDClient" />
>
> D:\temp\0.9 Release\tuscany-
> sca-0.90-incubating\samples\implementation-crud-client>ant run
> Buildfile: build.xml
>
> run:
>      [java] java.lang.NoClassDefFoundError: crud/CRUDClient
>      [java] Exception in thread "main"
>      [java] Java Result: 1


Yep, this one is broken. I guess after all the last minute changes to the
way the extension samples were like.

Source Modules
>
> itest\interop-soap-client -> pom version has SNAPSHOT
> itest\interop-soap-round2-client -> pom version has SNAPSHOT
> itest\interop-soap-service -> pom version has SNAPSHOT
>    -> reference axion snapshot
>    -> reference axion-impl snapshot
> itest\interop-xsq-client -> pom version has SNAPSHOT
>    -> still has varios scdl files
>
> modules\binding-jms --> are we shipping that ? still have SCDL files with
> references to snapshot, wsdl also reference snapshot
> modules\discovery-jms --> are we shipping that ? If so, it has SNAPSHOT
> version on it
>
> modules\binding-ws-xml -> test1.wsdl references snapshot
> (<wsdlsoap:address
> location="
>
> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService
> "
> />)
>
> modules\contribution-impl -> namespace defined as NS = "
> http://tuscany.apache.org/xmlns/1.0-SNAPSHOT";
>
> modules\interface-wsdl-xml -> test1.wsdl andpoing  references snapshot
> (<wsdlsoap:address location="
>
> http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService
> "
> />)


None of those are significant IMHO as either they're not included in the
build or the reference to snapshot is not actually used at runtime.

Javadoc
>
> Just a subset of packages javadoc was generated, I don't see contribution
> javadoc available... Is this ok ?


Another flaw, ideally we'd have Javadoc for every package we said was an API
or SPI.

Binaries
>
> We have a dependency on JRuby release candidate (jruby-complete-1.0RC2.jar
> )
> ? Is that ok ?


Thats fine, its just SNAPSHOT build we shouldn't release with.

On 5/21/07, ant elder <an...@gmail.com> wrote:
> >
> > I don't think that document says we MUST include the STATUS document. It
> > says "Check status document" meaning check that the STATUS doc doesn't
> say
> > there are outstanding legal issues that may prevent a release. Even if
> > that
> > releasemanagement doc did say we must, the doc is still under
> development
> > and in draft state so I'm not sure its binding policy. Given other
> recent
> > incubator releases didn't include the STATUS doc and an IPMCer recently
> > said
> > it could be removed from a distro i think this is not a blocking issue.
> >
> >    ...ant
> >
> > On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
> > >
> > > Regarding the STATUS document, I think the policy say we must include
> > > them,
> > > check [1] on the "Release Documentation" and "STATUS document"
> sessions.
> > > Also our STATUS file is not up to date, and I can take care of helping
> > > updating that after I finish reviewing the rest of the release
> > candidate.
> > >
> > > [1] - http://incubator.apache.org/guides/releasemanagement.html
> > >
> > > On 5/21/07, ant elder <an...@gmail.com> wrote:
> > > >
> > > > Hey many thanks for the prompt and detailed review.
> > > >
> > > > I can't remember exactly about the STATUS file, i think it may be an
> > old
> > > > requirement that is no longer necessary. I can find this
> > > incubator-general
> > > > email [1] about the recent CXF release which included and old and
> > > > incorrect
> > > > status file, and the guidance from an IPMC member was its ok to just
> > > > remove
> > > > it from the distro, so i think its fine we don't include this.
> > > >
> > > > All these other comments seem like good things we should do in
> future,
> > > if
> > > > we
> > > > do have to respin the 0.90 distro's for some other reason I'll try
> to
> > > > incorporate some of them.
> > > >
> > > > Thanks,
> > > >
> > > >    ...ant
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
> > > >
> > > > On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
> > > > >
> > > > > Ant,
> > > > >   I've had a good poke around and built the source distro and run
> > the
> > > > > tests
> > > > > successfully. The only potential blocking issue I have found is
> that
> > > > > absence
> > > > > of a STATUS file,  which it was my understanding should be copied
> in
> > > > from
> > > > > the project's STATUS file into every distribution,  but I haven't
> > been
> > > > > able
> > > > > to re-find that guidance in the apache site. Can anyone help
> clarify
> > > > this
> > > > > please?
> > > > >
> > > > > The rest of these comments are all minor observations that
> wouldn't
> > > stop
> > > > > me
> > > > > +1-ing the release.  Indeed, some of them may result in
> > clarification
> > > > that
> > > > > what you have done is corrent and that will help SDO in future
> > > releases?
> > > > >
> > > > > I've had comments in the past that Apache like it if the names of
> > the
> > > > > release file names include the "apache-" prefix
> > > > >
> > > > > I think the copyright in the NOTICES file at the top level of the
> > > source
> > > > > distro should include 2005
> > > > >
> > > > > I thought that the intention of the BUILDING file was to guide a
> > > person
> > > > > who
> > > > > has downloaded the source distribution to be able to recreate the
> > > > > distribution files,  not just to compile and test?  I can't
> re-find
> > > the
> > > > > guidance on that having searched that apache site.
> > > > >
> > > > > The LICENSE file in binary distro contains CPL 1.0 twice,  once
> for
> > > > wsdl4j
> > > > > and then at the bottom for Jruby.
> > > > >
> > > > > It would be really helpful to include a package.html file for each
> > > > package
> > > > > so that the javadoc gives an overview of what each package does.
> > > > >
> > > > > Cheers, Kelvin.
> > > > >
> > > > >
> > > > > On 20/05/07, ant elder <an...@gmail.com> wrote:
> > > > > >
> > > > > > Please review and vote on the 0.90 release artifacts of Tuscany
> > SCA
> > > > for
> > > > > > Java.
> > > > > >
> > > > > > The artifacts are available for review at:
> > > > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> > > > > >
> > > > > > This includes the binary and source distributions, the RAT
> > reports,
> > > > and
> > > > > > the
> > > > > > Maven staging repository.
> > > > > >
> > > > > > The SVN tag for the release is:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> > > > > >
> > > > > > Looks ok to me so here's my +1.
> > > > > >
> > > > > > Thanks in advance,
> > > > > >
> > > > > >    ...ant
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > Apache Tuscany Committer
> > > http://people.apache.org/~lresende
> > > http://lresende.blogspot.com/
> > >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Luciano Resende <lu...@gmail.com>]

Here are my findings around the 0.9 Release Candidate, my main concern is
with the issues I mentioned in the modules directory of the source.

Samples:
I have tried the standalone samples and the web samples (in jetty and
tomcat).
All samples look OK, with the exceptions of the ones mentioned below :

calculator-rmi-reference - WARNING

The README is confusing, by reading it, I was under the impression that the
server and client were on the same project, and it also have the client and
server ant xml files there. But in order to properly run the sample, you
need to go to calculator-rmi-service and actually start the server there,
then come to the reference (client)

D:\temp\0.9 Release\tuscany-
sca-0.90-incubating\samples\calculator-rmi-reference>ant -f build-server.xmlrun
Buildfile: build-server.xml

run:
     [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer
     [java] Exception in thread "main"
     [java] Java Result: 1


implementation-crud-client - ERROR

Looks like the ant.xml property has the wrong package, I have fixed this in
the branch and trunk
after adding the right package, it works
    <property name="test.class" value="crud.client.CRUDClient" />

D:\temp\0.9 Release\tuscany-
sca-0.90-incubating\samples\implementation-crud-client>ant run
Buildfile: build.xml

run:
     [java] java.lang.NoClassDefFoundError: crud/CRUDClient
     [java] Exception in thread "main"
     [java] Java Result: 1



Source Modules

itest\interop-soap-client -> pom version has SNAPSHOT
itest\interop-soap-round2-client -> pom version has SNAPSHOT
itest\interop-soap-service -> pom version has SNAPSHOT
   -> reference axion snapshot
   -> reference axion-impl snapshot
itest\interop-xsq-client -> pom version has SNAPSHOT
   -> still has varios scdl files

modules\binding-jms --> are we shipping that ? still have SCDL files with
references to snapshot, wsdl also reference snapshot
modules\discovery-jms --> are we shipping that ? If so, it has SNAPSHOT
version on it

modules\binding-ws-xml -> test1.wsdl references snapshot (<wsdlsoap:address
location="
http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService"
/>)

modules\contribution-impl -> namespace defined as NS = "
http://tuscany.apache.org/xmlns/1.0-SNAPSHOT";

modules\interface-wsdl-xml -> test1.wsdl andpoing  references snapshot
(<wsdlsoap:address location="
http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService"
/>)

Javadoc

Just a subset of packages javadoc was generated, I don't see contribution
javadoc available... Is this ok ?

Binaries

We have a dependency on JRuby release candidate (jruby-complete-1.0RC2.jar)
? Is that ok ?




On 5/21/07, ant elder <an...@gmail.com> wrote:
>
> I don't think that document says we MUST include the STATUS document. It
> says "Check status document" meaning check that the STATUS doc doesn't say
> there are outstanding legal issues that may prevent a release. Even if
> that
> releasemanagement doc did say we must, the doc is still under development
> and in draft state so I'm not sure its binding policy. Given other recent
> incubator releases didn't include the STATUS doc and an IPMCer recently
> said
> it could be removed from a distro i think this is not a blocking issue.
>
>    ...ant
>
> On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
> >
> > Regarding the STATUS document, I think the policy say we must include
> > them,
> > check [1] on the "Release Documentation" and "STATUS document" sessions.
> > Also our STATUS file is not up to date, and I can take care of helping
> > updating that after I finish reviewing the rest of the release
> candidate.
> >
> > [1] - http://incubator.apache.org/guides/releasemanagement.html
> >
> > On 5/21/07, ant elder <an...@gmail.com> wrote:
> > >
> > > Hey many thanks for the prompt and detailed review.
> > >
> > > I can't remember exactly about the STATUS file, i think it may be an
> old
> > > requirement that is no longer necessary. I can find this
> > incubator-general
> > > email [1] about the recent CXF release which included and old and
> > > incorrect
> > > status file, and the guidance from an IPMC member was its ok to just
> > > remove
> > > it from the distro, so i think its fine we don't include this.
> > >
> > > All these other comments seem like good things we should do in future,
> > if
> > > we
> > > do have to respin the 0.90 distro's for some other reason I'll try to
> > > incorporate some of them.
> > >
> > > Thanks,
> > >
> > >    ...ant
> > >
> > > [1]
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
> > >
> > > On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
> > > >
> > > > Ant,
> > > >   I've had a good poke around and built the source distro and run
> the
> > > > tests
> > > > successfully. The only potential blocking issue I have found is that
> > > > absence
> > > > of a STATUS file,  which it was my understanding should be copied in
> > > from
> > > > the project's STATUS file into every distribution,  but I haven't
> been
> > > > able
> > > > to re-find that guidance in the apache site. Can anyone help clarify
> > > this
> > > > please?
> > > >
> > > > The rest of these comments are all minor observations that wouldn't
> > stop
> > > > me
> > > > +1-ing the release.  Indeed, some of them may result in
> clarification
> > > that
> > > > what you have done is corrent and that will help SDO in future
> > releases?
> > > >
> > > > I've had comments in the past that Apache like it if the names of
> the
> > > > release file names include the "apache-" prefix
> > > >
> > > > I think the copyright in the NOTICES file at the top level of the
> > source
> > > > distro should include 2005
> > > >
> > > > I thought that the intention of the BUILDING file was to guide a
> > person
> > > > who
> > > > has downloaded the source distribution to be able to recreate the
> > > > distribution files,  not just to compile and test?  I can't re-find
> > the
> > > > guidance on that having searched that apache site.
> > > >
> > > > The LICENSE file in binary distro contains CPL 1.0 twice,  once for
> > > wsdl4j
> > > > and then at the bottom for Jruby.
> > > >
> > > > It would be really helpful to include a package.html file for each
> > > package
> > > > so that the javadoc gives an overview of what each package does.
> > > >
> > > > Cheers, Kelvin.
> > > >
> > > >
> > > > On 20/05/07, ant elder <an...@gmail.com> wrote:
> > > > >
> > > > > Please review and vote on the 0.90 release artifacts of Tuscany
> SCA
> > > for
> > > > > Java.
> > > > >
> > > > > The artifacts are available for review at:
> > > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> > > > >
> > > > > This includes the binary and source distributions, the RAT
> reports,
> > > and
> > > > > the
> > > > > Maven staging repository.
> > > > >
> > > > > The SVN tag for the release is:
> > > > >
> > > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> > > > >
> > > > > Looks ok to me so here's my +1.
> > > > >
> > > > > Thanks in advance,
> > > > >
> > > > >    ...ant
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany Committer
> > http://people.apache.org/~lresende
> > http://lresende.blogspot.com/
> >
>



-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

I don't think that document says we MUST include the STATUS document. It
says "Check status document" meaning check that the STATUS doc doesn't say
there are outstanding legal issues that may prevent a release. Even if that
releasemanagement doc did say we must, the doc is still under development
and in draft state so I'm not sure its binding policy. Given other recent
incubator releases didn't include the STATUS doc and an IPMCer recently said
it could be removed from a distro i think this is not a blocking issue.

   ...ant

On 5/21/07, Luciano Resende <lu...@gmail.com> wrote:
>
> Regarding the STATUS document, I think the policy say we must include
> them,
> check [1] on the "Release Documentation" and "STATUS document" sessions.
> Also our STATUS file is not up to date, and I can take care of helping
> updating that after I finish reviewing the rest of the release candidate.
>
> [1] - http://incubator.apache.org/guides/releasemanagement.html
>
> On 5/21/07, ant elder <an...@gmail.com> wrote:
> >
> > Hey many thanks for the prompt and detailed review.
> >
> > I can't remember exactly about the STATUS file, i think it may be an old
> > requirement that is no longer necessary. I can find this
> incubator-general
> > email [1] about the recent CXF release which included and old and
> > incorrect
> > status file, and the guidance from an IPMC member was its ok to just
> > remove
> > it from the distro, so i think its fine we don't include this.
> >
> > All these other comments seem like good things we should do in future,
> if
> > we
> > do have to respin the 0.90 distro's for some other reason I'll try to
> > incorporate some of them.
> >
> > Thanks,
> >
> >    ...ant
> >
> > [1]
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
> >
> > On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
> > >
> > > Ant,
> > >   I've had a good poke around and built the source distro and run the
> > > tests
> > > successfully. The only potential blocking issue I have found is that
> > > absence
> > > of a STATUS file,  which it was my understanding should be copied in
> > from
> > > the project's STATUS file into every distribution,  but I haven't been
> > > able
> > > to re-find that guidance in the apache site. Can anyone help clarify
> > this
> > > please?
> > >
> > > The rest of these comments are all minor observations that wouldn't
> stop
> > > me
> > > +1-ing the release.  Indeed, some of them may result in clarification
> > that
> > > what you have done is corrent and that will help SDO in future
> releases?
> > >
> > > I've had comments in the past that Apache like it if the names of the
> > > release file names include the "apache-" prefix
> > >
> > > I think the copyright in the NOTICES file at the top level of the
> source
> > > distro should include 2005
> > >
> > > I thought that the intention of the BUILDING file was to guide a
> person
> > > who
> > > has downloaded the source distribution to be able to recreate the
> > > distribution files,  not just to compile and test?  I can't re-find
> the
> > > guidance on that having searched that apache site.
> > >
> > > The LICENSE file in binary distro contains CPL 1.0 twice,  once for
> > wsdl4j
> > > and then at the bottom for Jruby.
> > >
> > > It would be really helpful to include a package.html file for each
> > package
> > > so that the javadoc gives an overview of what each package does.
> > >
> > > Cheers, Kelvin.
> > >
> > >
> > > On 20/05/07, ant elder <an...@gmail.com> wrote:
> > > >
> > > > Please review and vote on the 0.90 release artifacts of Tuscany SCA
> > for
> > > > Java.
> > > >
> > > > The artifacts are available for review at:
> > > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> > > >
> > > > This includes the binary and source distributions, the RAT reports,
> > and
> > > > the
> > > > Maven staging repository.
> > > >
> > > > The SVN tag for the release is:
> > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> > > >
> > > > Looks ok to me so here's my +1.
> > > >
> > > > Thanks in advance,
> > > >
> > > >    ...ant
> > > >
> > >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[Luciano Resende <lu...@gmail.com>]

Regarding the STATUS document, I think the policy say we must include them,
check [1] on the "Release Documentation" and "STATUS document" sessions.
Also our STATUS file is not up to date, and I can take care of helping
updating that after I finish reviewing the rest of the release candidate.

[1] - http://incubator.apache.org/guides/releasemanagement.html

On 5/21/07, ant elder <an...@gmail.com> wrote:
>
> Hey many thanks for the prompt and detailed review.
>
> I can't remember exactly about the STATUS file, i think it may be an old
> requirement that is no longer necessary. I can find this incubator-general
> email [1] about the recent CXF release which included and old and
> incorrect
> status file, and the guidance from an IPMC member was its ok to just
> remove
> it from the distro, so i think its fine we don't include this.
>
> All these other comments seem like good things we should do in future, if
> we
> do have to respin the 0.90 distro's for some other reason I'll try to
> incorporate some of them.
>
> Thanks,
>
>    ...ant
>
> [1]
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e
>
> On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
> >
> > Ant,
> >   I've had a good poke around and built the source distro and run the
> > tests
> > successfully. The only potential blocking issue I have found is that
> > absence
> > of a STATUS file,  which it was my understanding should be copied in
> from
> > the project's STATUS file into every distribution,  but I haven't been
> > able
> > to re-find that guidance in the apache site. Can anyone help clarify
> this
> > please?
> >
> > The rest of these comments are all minor observations that wouldn't stop
> > me
> > +1-ing the release.  Indeed, some of them may result in clarification
> that
> > what you have done is corrent and that will help SDO in future releases?
> >
> > I've had comments in the past that Apache like it if the names of the
> > release file names include the "apache-" prefix
> >
> > I think the copyright in the NOTICES file at the top level of the source
> > distro should include 2005
> >
> > I thought that the intention of the BUILDING file was to guide a person
> > who
> > has downloaded the source distribution to be able to recreate the
> > distribution files,  not just to compile and test?  I can't re-find the
> > guidance on that having searched that apache site.
> >
> > The LICENSE file in binary distro contains CPL 1.0 twice,  once for
> wsdl4j
> > and then at the bottom for Jruby.
> >
> > It would be really helpful to include a package.html file for each
> package
> > so that the javadoc gives an overview of what each package does.
> >
> > Cheers, Kelvin.
> >
> >
> > On 20/05/07, ant elder <an...@gmail.com> wrote:
> > >
> > > Please review and vote on the 0.90 release artifacts of Tuscany SCA
> for
> > > Java.
> > >
> > > The artifacts are available for review at:
> > > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> > >
> > > This includes the binary and source distributions, the RAT reports,
> and
> > > the
> > > Maven staging repository.
> > >
> > > The SVN tag for the release is:
> > >
> > >
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> > >
> > > Looks ok to me so here's my +1.
> > >
> > > Thanks in advance,
> > >
> > >    ...ant
> > >
> >
>



-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[ant elder <an...@gmail.com>]

Hey many thanks for the prompt and detailed review.

I can't remember exactly about the STATUS file, i think it may be an old
requirement that is no longer necessary. I can find this incubator-general
email [1] about the recent CXF release which included and old and incorrect
status file, and the guidance from an IPMC member was its ok to just remove
it from the distro, so i think its fine we don't include this.

All these other comments seem like good things we should do in future, if we
do have to respin the 0.90 distro's for some other reason I'll try to
incorporate some of them.

Thanks,

   ...ant

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/%3cB6C98B95-409F-4630-B7A2-12CEC1DC537D@jaguNET.com%3e

On 5/21/07, kelvin goodson <ke...@gmail.com> wrote:
>
> Ant,
>   I've had a good poke around and built the source distro and run the
> tests
> successfully. The only potential blocking issue I have found is that
> absence
> of a STATUS file,  which it was my understanding should be copied in from
> the project's STATUS file into every distribution,  but I haven't been
> able
> to re-find that guidance in the apache site. Can anyone help clarify this
> please?
>
> The rest of these comments are all minor observations that wouldn't stop
> me
> +1-ing the release.  Indeed, some of them may result in clarification that
> what you have done is corrent and that will help SDO in future releases?
>
> I've had comments in the past that Apache like it if the names of the
> release file names include the "apache-" prefix
>
> I think the copyright in the NOTICES file at the top level of the source
> distro should include 2005
>
> I thought that the intention of the BUILDING file was to guide a person
> who
> has downloaded the source distribution to be able to recreate the
> distribution files,  not just to compile and test?  I can't re-find the
> guidance on that having searched that apache site.
>
> The LICENSE file in binary distro contains CPL 1.0 twice,  once for wsdl4j
> and then at the bottom for Jruby.
>
> It would be really helpful to include a package.html file for each package
> so that the javadoc gives an overview of what each package does.
>
> Cheers, Kelvin.
>
>
> On 20/05/07, ant elder <an...@gmail.com> wrote:
> >
> > Please review and vote on the 0.90 release artifacts of Tuscany SCA for
> > Java.
> >
> > The artifacts are available for review at:
> > http://people.apache.org/~antelder/tuscany/0.90-rc1/
> >
> > This includes the binary and source distributions, the RAT reports, and
> > the
> > Maven staging repository.
> >
> > The SVN tag for the release is:
> >
> >
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
> >
> > Looks ok to me so here's my +1.
> >
> > Thanks in advance,
> >
> >    ...ant
> >
>

Re: [VOTE] Release Tuscany Java SCA 0.90-incubating

[kelvin goodson <ke...@gmail.com>]

Ant,
  I've had a good poke around and built the source distro and run the tests
successfully. The only potential blocking issue I have found is that absence
of a STATUS file,  which it was my understanding should be copied in from
the project's STATUS file into every distribution,  but I haven't been able
to re-find that guidance in the apache site. Can anyone help clarify this
please?

The rest of these comments are all minor observations that wouldn't stop me
+1-ing the release.  Indeed, some of them may result in clarification that
what you have done is corrent and that will help SDO in future releases?

I've had comments in the past that Apache like it if the names of the
release file names include the "apache-" prefix

I think the copyright in the NOTICES file at the top level of the source
distro should include 2005

I thought that the intention of the BUILDING file was to guide a person who
has downloaded the source distribution to be able to recreate the
distribution files,  not just to compile and test?  I can't re-find the
guidance on that having searched that apache site.

The LICENSE file in binary distro contains CPL 1.0 twice,  once for wsdl4j
and then at the bottom for Jruby.

It would be really helpful to include a package.html file for each package
so that the javadoc gives an overview of what each package does.

Cheers, Kelvin.


On 20/05/07, ant elder <an...@gmail.com> wrote:
>
> Please review and vote on the 0.90 release artifacts of Tuscany SCA for
> Java.
>
> The artifacts are available for review at:
> http://people.apache.org/~antelder/tuscany/0.90-rc1/
>
> This includes the binary and source distributions, the RAT reports, and
> the
> Maven staging repository.
>
> The SVN tag for the release is:
>
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/
>
> Looks ok to me so here's my +1.
>
> Thanks in advance,
>
>    ...ant
>