You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jeremy Boynes <jb...@apache.org> on 2006/12/05 18:44:09 UTC
Re: Are we ready to release M2?
I think resolves the last issue - does anyone have anything else to
bring up? If not, I will start to package another release candidate.
--
Jeremy
On Dec 5, 2006, at 8:50 AM, ant elder wrote:
> Yes! Jeremy, as release manager what do you say, would you make us
> another
> release candidate to review and vote on?
>
> ...ant
>
> On 12/5/06, Raymond Feng <en...@gmail.com> wrote:
>>
>> Hi,
>>
>> Considering the axiom SNAPSHOT dependency puzzle has been figured
>> out,
>> should we go ahead to push M2 release out?
>>
>> Thanks,
>> Raymond
>>
>> ----- Original Message -----
>> From: "Raymond Feng" <en...@gmail.com>
>> To: <tu...@ws.apache.org>
>> Sent: Monday, December 04, 2006 12:10 PM
>> Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options
>> for
>> Tuscany SCA Java M2 release)
>>
>>
>> > Hi,
>> >
>> > I did some further investigations with Ant and here are some
>> observations:
>> >
>> > 1) maven2 build will pull in axis2 artifacts from maven1 or
>> maven2 repo
>> > randomly. I even see a mixture that the pom is downloaded from a
>> m1 repo
>> > while the jar from a m2 repo.
>> >
>> > 2) axis2-kernel 1.1 pom from maven2 repo is invalid. It has a
>> dependency
>> > on "org.apache.ws.commons.neethi:neethi"
>> > <dependency>
>> > <groupId>org.apache.ws.commons.neethi</groupId>
>> > <artifactId>neethi</artifactId>
>> > </dependency>
>> >
>> > But the axis2-parent pom has "org.apache.neethi:neethi" instead.
>> >
>> > <dependency>
>> > <groupId>org.apache.neethi</groupId>
>> > <artifactId>neethi</artifactId>
>> > <version>2.0</version>
>> > </dependency>
>> >
>> > As a result, the pom fails to pass the validation and it's
>> treated as an
>> > invalid pom. Transative dependency is not activated at all for
>> > axis2-kernel 1.1.
>> >
>> > To conclude, no matter axis2 1.1 is downloaded from m1 or m2
>> repo, the
>> pom
>> > is invalid and transative dependency is not activated at all for
>> > axis2-kernel. The bug becomes good news to us: the SNAPSHOT
>> version of
>> > axiom-api will NOT be used by Tuscany runtime.
>> >
>> > Do we feel safe to release our M2 now without waiting for further
>> releases
>> > from axis2?
>> >
>> > Thanks,
>> > Raymond
>> >
>> > ----- Original Message -----
>> > From: "ant elder" <an...@gmail.com>
>> > To: <tu...@ws.apache.org>
>> > Sent: Monday, December 04, 2006 12:31 AM
>> > Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and
>> options for
>> > Tuscany SCA Java M2 release)
>> >
>> >
>> >> I'm starting to wonder if the subject line is even more apt
>> than we
>> >> realize
>> >> and we're just assuming this is a significant problem without
>> >> investigating.
>> >>
>> >>
>> >> AFAICT the only thing thats happening is what I originally
>> reported -
>> you
>> >> see log messages about the AXIOM API SNAPSHOT when using the WS
>> >> samples...but it doesn't look like that SNAPSHOT jar is actually
>> getting
>> >> used by anything.
>> >>
>> >> - If you delete if from your repository the samples run fine.
>> You can
>> run
>> >> the samples in offline mode and not have that SNAPSHOT jar in your
>> >> repository and the samples still run fine.
>> >>
>> >> - If you build the sample webapps with
>> loadExtensionDependencies set to
>> >> true
>> >> then the SNAPSHOT jar is *not* included in the WAR repository
>> and the
>> >> samples still run fine even in offline mode.
>> >>
>> >> - If you make incompatible changes to classes in the SNAPSHOT
>> jar in
>> your
>> >> local repository, eg change the OMElement interface to have no
>> methods,
>> >> the
>> >> samples still run fine.
>> >>
>> >> Additionally debugging in the MavenHelper class you can see the
>> SNAPSHOT
>> >> messages are coming from the
>> artifactResolver.resolveTransitively call
>> on
>> >> line 264 but the ArtifactResolutionResult thats returned from
>> the call
>> >> *does
>> >> not* include the axiom-api SNAPSHOT artifact.
>> >>
>> >> Based on that it doesn't look like the SNAPSHOT jar is even
>> added to
>> the
>> >> classpath used by the samples. Could anyone else confirm these
>> >> observations?
>> >> If this is true the I think we could safely cut the M2 release
>> as-is,
>> >> maybe
>> >> just add a comment to the release notes about the SNAPSHOT
>> messages.
>> >>
>> >> ...ant
>> >>
>> >
>>
>>
>> ---------------------------------------------------------------------
>> 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: Are we ready to release M2?
Posted by Simon Nash <na...@hursley.ibm.com>.
I have now run all the samples successfully, using only the jars that
are deployed to maven when using the -Prelease flag.
The only other issue I had with the previous release candidate was the
packaging and formal release voting for the spec APIs that we need from
org.osoa and commonj. These need to be available as binaries, source,
and javadoc.
Simon
Simon Nash wrote:
> On further investigation, this is caused by a mismatch betweeen the
> sample instructions in readme.html and the artifacts built by the sample.
>
> The instructions give the following command to run:
> java -jar target/distribution/bin/launcher.jar
> target/sample-helloworldwsclient-async-1.0-incubator-M2.jar
>
> However, the name of the jar file as currently built is
> target/sample-helloworldwsclient-async-1.0-incubator-M2-SNAPSHOT.jar
>
> Looking into this a bit more, I noticed that some samples (like this one)
> build executable jars with the suffix
> 1.0-incubator-M2-SNAPSHOT
> whereas others (like greeterwsclient-oneway) build jars with the suffix
> 1.0-incubator-M2
> and others (like calculator) have no suffix at all.
>
> This is not a showstopper for releasing M2, but we should agree on and use
> a consistent naming convention for these artifacts.
>
> Simon
>
> Simon Nash wrote:
>
>> I checked out the M2 branch, cleaned out my local Maven .m2 repo,
>> built the runtime using -Prelease, built the samples, and ran all
>> the samples. The main purpose of doing this was to ensure that
>> the -Prelease flag had not removed any artifacts that were needed
>> to successfully build and run the samples.
>>
>> All was going well until I got the following error from the
>> helloworldwsclient-async sample:
>>
>> Exception in thread "main" java.lang.NullPointerException
>> at
>> org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistryImpl.java:102)
>>
>> at
>> org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.loadFromSidefile(CompositeComponentTypeLoader.java:65)
>>
>> at
>> org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load(CompositeComponentTypeLoader.java:57)
>>
>> at
>> org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load(CompositeComponentTypeLoader.java:39)
>>
>> at
>> org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(LoaderRegistryImpl.java:159)
>>
>> at
>> org.apache.tuscany.core.deployer.DeployerImpl.load(DeployerImpl.java:101)
>> at
>> org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.java:76)
>>
>> at
>> org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl(AbstractRuntime.java:136)
>>
>> at
>> org.apache.tuscany.runtime.standalone.host.StandaloneRuntimeImpl.initialize(StandaloneRuntimeImpl.java:87)
>>
>> at
>> org.apache.tuscany.launcher.MainLauncherBooter.main(MainLauncherBooter.java:83)
>>
>>
>> Can anyone else confirm this problem? I will continue looking at
>> my setup to see if I can find out more about what is going on.
>>
>> 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: Are we ready to release M2?
Posted by Simon Nash <na...@hursley.ibm.com>.
On further investigation, this is caused by a mismatch betweeen the
sample instructions in readme.html and the artifacts built by the sample.
The instructions give the following command to run:
java -jar target/distribution/bin/launcher.jar target/sample-helloworldwsclient-async-1.0-incubator-M2.jar
However, the name of the jar file as currently built is
target/sample-helloworldwsclient-async-1.0-incubator-M2-SNAPSHOT.jar
Looking into this a bit more, I noticed that some samples (like this one)
build executable jars with the suffix
1.0-incubator-M2-SNAPSHOT
whereas others (like greeterwsclient-oneway) build jars with the suffix
1.0-incubator-M2
and others (like calculator) have no suffix at all.
This is not a showstopper for releasing M2, but we should agree on and use
a consistent naming convention for these artifacts.
Simon
Simon Nash wrote:
> I checked out the M2 branch, cleaned out my local Maven .m2 repo,
> built the runtime using -Prelease, built the samples, and ran all
> the samples. The main purpose of doing this was to ensure that
> the -Prelease flag had not removed any artifacts that were needed
> to successfully build and run the samples.
>
> All was going well until I got the following error from the
> helloworldwsclient-async sample:
>
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistryImpl.java:102)
>
> at
> org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.loadFromSidefile(CompositeComponentTypeLoader.java:65)
>
> at
> org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load(CompositeComponentTypeLoader.java:57)
>
> at
> org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load(CompositeComponentTypeLoader.java:39)
>
> at
> org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(LoaderRegistryImpl.java:159)
>
> at
> org.apache.tuscany.core.deployer.DeployerImpl.load(DeployerImpl.java:101)
> at
> org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.java:76)
> at
> org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl(AbstractRuntime.java:136)
>
> at
> org.apache.tuscany.runtime.standalone.host.StandaloneRuntimeImpl.initialize(StandaloneRuntimeImpl.java:87)
>
> at
> org.apache.tuscany.launcher.MainLauncherBooter.main(MainLauncherBooter.java:83)
>
>
> Can anyone else confirm this problem? I will continue looking at
> my setup to see if I can find out more about what is going on.
>
> Simon
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Are we ready to release M2?
Posted by Simon Nash <na...@hursley.ibm.com>.
I checked out the M2 branch, cleaned out my local Maven .m2 repo,
built the runtime using -Prelease, built the samples, and ran all
the samples. The main purpose of doing this was to ensure that
the -Prelease flag had not removed any artifacts that were needed
to successfully build and run the samples.
All was going well until I got the following error from the
helloworldwsclient-async sample:
Exception in thread "main" java.lang.NullPointerException
at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistryImpl.java:102)
at org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.loadFromSidefile(CompositeComponentTypeLoader.java:65)
at org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load(CompositeComponentTypeLoader.java:57)
at org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load(CompositeComponentTypeLoader.java:39)
at org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(LoaderRegistryImpl.java:159)
at org.apache.tuscany.core.deployer.DeployerImpl.load(DeployerImpl.java:101)
at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.java:76)
at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl(AbstractRuntime.java:136)
at org.apache.tuscany.runtime.standalone.host.StandaloneRuntimeImpl.initialize(StandaloneRuntimeImpl.java:87)
at org.apache.tuscany.launcher.MainLauncherBooter.main(MainLauncherBooter.java:83)
Can anyone else confirm this problem? I will continue looking at
my setup to see if I can find out more about what is going on.
Simon
Jeremy Boynes wrote:
> I think resolves the last issue - does anyone have anything else to
> bring up? If not, I will start to package another release candidate.
> --
> Jeremy
>
> On Dec 5, 2006, at 8:50 AM, ant elder wrote:
>
>> Yes! Jeremy, as release manager what do you say, would you make us
>> another
>> release candidate to review and vote on?
>>
>> ...ant
>>
>> On 12/5/06, Raymond Feng <en...@gmail.com> wrote:
>>
>>>
>>> Hi,
>>>
>>> Considering the axiom SNAPSHOT dependency puzzle has been figured out,
>>> should we go ahead to push M2 release out?
>>>
>>> Thanks,
>>> Raymond
>>>
>>> ----- Original Message -----
>>> From: "Raymond Feng" <en...@gmail.com>
>>> To: <tu...@ws.apache.org>
>>> Sent: Monday, December 04, 2006 12:10 PM
>>> Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options for
>>> Tuscany SCA Java M2 release)
>>>
>>>
>>> > Hi,
>>> >
>>> > I did some further investigations with Ant and here are some
>>> observations:
>>> >
>>> > 1) maven2 build will pull in axis2 artifacts from maven1 or maven2
>>> repo
>>> > randomly. I even see a mixture that the pom is downloaded from a
>>> m1 repo
>>> > while the jar from a m2 repo.
>>> >
>>> > 2) axis2-kernel 1.1 pom from maven2 repo is invalid. It has a
>>> dependency
>>> > on "org.apache.ws.commons.neethi:neethi"
>>> > <dependency>
>>> > <groupId>org.apache.ws.commons.neethi</groupId>
>>> > <artifactId>neethi</artifactId>
>>> > </dependency>
>>> >
>>> > But the axis2-parent pom has "org.apache.neethi:neethi" instead.
>>> >
>>> > <dependency>
>>> > <groupId>org.apache.neethi</groupId>
>>> > <artifactId>neethi</artifactId>
>>> > <version>2.0</version>
>>> > </dependency>
>>> >
>>> > As a result, the pom fails to pass the validation and it's treated
>>> as an
>>> > invalid pom. Transative dependency is not activated at all for
>>> > axis2-kernel 1.1.
>>> >
>>> > To conclude, no matter axis2 1.1 is downloaded from m1 or m2 repo,
>>> the
>>> pom
>>> > is invalid and transative dependency is not activated at all for
>>> > axis2-kernel. The bug becomes good news to us: the SNAPSHOT
>>> version of
>>> > axiom-api will NOT be used by Tuscany runtime.
>>> >
>>> > Do we feel safe to release our M2 now without waiting for further
>>> releases
>>> > from axis2?
>>> >
>>> > Thanks,
>>> > Raymond
>>> >
>>> > ----- Original Message -----
>>> > From: "ant elder" <an...@gmail.com>
>>> > To: <tu...@ws.apache.org>
>>> > Sent: Monday, December 04, 2006 12:31 AM
>>> > Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options
>>> for
>>> > Tuscany SCA Java M2 release)
>>> >
>>> >
>>> >> I'm starting to wonder if the subject line is even more apt than we
>>> >> realize
>>> >> and we're just assuming this is a significant problem without
>>> >> investigating.
>>> >>
>>> >>
>>> >> AFAICT the only thing thats happening is what I originally
>>> reported -
>>> you
>>> >> see log messages about the AXIOM API SNAPSHOT when using the WS
>>> >> samples...but it doesn't look like that SNAPSHOT jar is actually
>>> getting
>>> >> used by anything.
>>> >>
>>> >> - If you delete if from your repository the samples run fine. You
>>> can
>>> run
>>> >> the samples in offline mode and not have that SNAPSHOT jar in your
>>> >> repository and the samples still run fine.
>>> >>
>>> >> - If you build the sample webapps with loadExtensionDependencies
>>> set to
>>> >> true
>>> >> then the SNAPSHOT jar is *not* included in the WAR repository and
>>> the
>>> >> samples still run fine even in offline mode.
>>> >>
>>> >> - If you make incompatible changes to classes in the SNAPSHOT jar in
>>> your
>>> >> local repository, eg change the OMElement interface to have no
>>> methods,
>>> >> the
>>> >> samples still run fine.
>>> >>
>>> >> Additionally debugging in the MavenHelper class you can see the
>>> SNAPSHOT
>>> >> messages are coming from the artifactResolver.resolveTransitively
>>> call
>>> on
>>> >> line 264 but the ArtifactResolutionResult thats returned from the
>>> call
>>> >> *does
>>> >> not* include the axiom-api SNAPSHOT artifact.
>>> >>
>>> >> Based on that it doesn't look like the SNAPSHOT jar is even added to
>>> the
>>> >> classpath used by the samples. Could anyone else confirm these
>>> >> observations?
>>> >> If this is true the I think we could safely cut the M2 release
>>> as-is,
>>> >> maybe
>>> >> just add a comment to the release notes about the SNAPSHOT messages.
>>> >>
>>> >> ...ant
>>> >>
>>> >
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
>
>
--
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