You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Raymond Feng <en...@gmail.com> on 2007/09/21 09:22:42 UTC
TUSCANY-1750
Hi,
I spent a few hours debugging this problem. And it turned out a big surprise
to me. The issue has nothing to do with the code. Believe or not, the
culprit is the trailing space in the value for the location attribute of the
<pathelement> in the build.xml.
<pathelement
location="../binding-echo-extension/target/sample-binding-echo-extension.jar
"/>
As a result, the jar is not added to the classpath by ant on Linux (but it
works on Windows). Then the tuscany code doesn't handle the <binding.echo>
and there is no effective endpoint for ComponentB.echoReference.
Removing the trailing space fixes the problem! What can I say :-(? I have to
claim those whoever wrote this build.xml owes a case of beer :-).
Thanks,
Raymond
----- Original Message -----
From: <rf...@apache.org>
To: <tu...@ws.apache.org>
Sent: Friday, September 21, 2007 12:13 AM
Subject: svn commit: r578002 -
/incubator/tuscany/java/sca/samples/databinding-echo/build.xml
> Author: rfeng
> Date: Fri Sep 21 00:13:13 2007
> New Revision: 578002
>
> URL: http://svn.apache.org/viewvc?rev=578002&view=rev
> Log:
> Fix for TUSCANY-1750
>
> Modified:
> incubator/tuscany/java/sca/samples/databinding-echo/build.xml
>
> Modified: incubator/tuscany/java/sca/samples/databinding-echo/build.xml
> URL:
> http://svn.apache.org/viewvc/incubator/tuscany/java/sca/samples/databinding-echo/build.xml?rev=578002&r1=578001&r2=578002&view=diff
> ==============================================================================
> --- incubator/tuscany/java/sca/samples/databinding-echo/build.xml
> (original)
> +++ incubator/tuscany/java/sca/samples/databinding-echo/build.xml Fri Sep
> 21 00:13:13 2007
> @@ -62,7 +62,7 @@
> <classpath>
> <pathelement path="target/${test.jar}"/>
> <pathelement
> location="../../lib/tuscany-sca-manifest.jar"/>
> - <pathelement
> location="../binding-echo-extension/target/sample-binding-echo-extension.jar
> "/>
> + <pathelement
> location="../binding-echo-extension/target/sample-binding-echo-extension.jar"/>
> </classpath>
> </java>
> </target>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-commits-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-commits-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: Writing a Mojo to generate build.xml for Tuscany application
modules, was: TUSCANY-1750
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> The "mvn ant:ant" can generate a reasonable build.xml. Are you looking
> for a Mojo that generates the ant script against our binary distro
> structure?
>
> Thanks,
> Raymond
Yes, have you looked at what's generated by ant:ant? I wouldn't call
this "a reasonable build.xml" :) compared to the current handcrafted
build.xml.
>
> ----- Original Message ----- From: "Jean-Sebastien Delfino"
> <js...@apache.org>
> To: <tu...@ws.apache.org>
> Sent: Sunday, September 23, 2007 7:53 PM
> Subject: Writing a Mojo to generate build.xml for Tuscany application
> modules, was: TUSCANY-1750
>
>
>> Raymond Feng wrote:
>>> Hi,
>>>
>>> I spent a few hours debugging this problem. And it turned out a big
>>> surprise to me. The issue has nothing to do with the code. Believe
>>> or not, the culprit is the trailing space in the value for the
>>> location attribute of the <pathelement> in the build.xml.
>>>
>>> <pathelement
>>> location="../binding-echo-extension/target/sample-binding-echo-extension.jar
>>> "/>
>>>
>>> As a result, the jar is not added to the classpath by ant on Linux
>>> (but it works on Windows). Then the tuscany code doesn't handle the
>>> <binding.echo> and there is no effective endpoint for
>>> ComponentB.echoReference.
>>>
>>> Removing the trailing space fixes the problem! What can I say :-(? I
>>> have to claim those whoever wrote this build.xml owes a case of beer
>>> :-).
>>>
>>> Thanks,
>>> Raymond
>>>
>>
>> We've spent so much time testing these handwritten build.xml files...
>> How about writing a generator that will generate a correct build.xml
>> from the Maven pom?
>>
>> It looks like the only variables are:
>> - the name of the module
>> - if it's a JAR or a WAR
>> - the dependency JARs
>> - for a JAR the name of the main class
>> ... so generate a build.xml shouldn't be too hard.
>>
>> Anybody interested in writing a Mojo for that?
>>
>> --
>> Jean-Sebastien
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Writing a Mojo to generate build.xml for Tuscany application modules, was: TUSCANY-1750
Posted by Raymond Feng <en...@gmail.com>.
Hi,
The "mvn ant:ant" can generate a reasonable build.xml. Are you looking for a
Mojo that generates the ant script against our binary distro structure?
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <js...@apache.org>
To: <tu...@ws.apache.org>
Sent: Sunday, September 23, 2007 7:53 PM
Subject: Writing a Mojo to generate build.xml for Tuscany application
modules, was: TUSCANY-1750
> Raymond Feng wrote:
>> Hi,
>>
>> I spent a few hours debugging this problem. And it turned out a big
>> surprise to me. The issue has nothing to do with the code. Believe or
>> not, the culprit is the trailing space in the value for the location
>> attribute of the <pathelement> in the build.xml.
>>
>> <pathelement
>> location="../binding-echo-extension/target/sample-binding-echo-extension.jar
>> "/>
>>
>> As a result, the jar is not added to the classpath by ant on Linux (but
>> it works on Windows). Then the tuscany code doesn't handle the
>> <binding.echo> and there is no effective endpoint for
>> ComponentB.echoReference.
>>
>> Removing the trailing space fixes the problem! What can I say :-(? I have
>> to claim those whoever wrote this build.xml owes a case of beer :-).
>>
>> Thanks,
>> Raymond
>>
>
> We've spent so much time testing these handwritten build.xml files... How
> about writing a generator that will generate a correct build.xml from the
> Maven pom?
>
> It looks like the only variables are:
> - the name of the module
> - if it's a JAR or a WAR
> - the dependency JARs
> - for a JAR the name of the main class
> ... so generate a build.xml shouldn't be too hard.
>
> Anybody interested in writing a Mojo for that?
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> 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: Writing a Mojo to generate build.xml for Tuscany application modules, was: TUSCANY-1750
Posted by shaoguang geng <ge...@yahoo.com>.
Any way,I think Raymond has done a great thing,problem itself is nothing more than problem, but works that dig them out are always greate to flatten the road for us to keep going on?
Jean-Sebastien Delfino <js...@apache.org> wrote: Raymond Feng wrote:
> Hi,
>
> I spent a few hours debugging this problem. And it turned out a big
> surprise to me. The issue has nothing to do with the code. Believe or
> not, the culprit is the trailing space in the value for the location
> attribute of the
in the build.xml.
>
>
> location="../binding-echo-extension/target/sample-binding-echo-extension.jar
> "/>
>
> As a result, the jar is not added to the classpath by ant on Linux
> (but it works on Windows). Then the tuscany code doesn't handle the
> and there is no effective endpoint for
> ComponentB.echoReference.
>
> Removing the trailing space fixes the problem! What can I say :-(? I
> have to claim those whoever wrote this build.xml owes a case of beer :-).
>
> Thanks,
> Raymond
>
We've spent so much time testing these handwritten build.xml files...
How about writing a generator that will generate a correct build.xml
from the Maven pom?
It looks like the only variables are:
- the name of the module
- if it's a JAR or a WAR
- the dependency JARs
- for a JAR the name of the main class
.... so generate a build.xml shouldn't be too hard.
Anybody interested in writing a Mojo for that?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
---------------------------------
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
Writing a Mojo to generate build.xml for Tuscany application modules,
was: TUSCANY-1750
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> I spent a few hours debugging this problem. And it turned out a big
> surprise to me. The issue has nothing to do with the code. Believe or
> not, the culprit is the trailing space in the value for the location
> attribute of the <pathelement> in the build.xml.
>
> <pathelement
> location="../binding-echo-extension/target/sample-binding-echo-extension.jar
> "/>
>
> As a result, the jar is not added to the classpath by ant on Linux
> (but it works on Windows). Then the tuscany code doesn't handle the
> <binding.echo> and there is no effective endpoint for
> ComponentB.echoReference.
>
> Removing the trailing space fixes the problem! What can I say :-(? I
> have to claim those whoever wrote this build.xml owes a case of beer :-).
>
> Thanks,
> Raymond
>
We've spent so much time testing these handwritten build.xml files...
How about writing a generator that will generate a correct build.xml
from the Maven pom?
It looks like the only variables are:
- the name of the module
- if it's a JAR or a WAR
- the dependency JARs
- for a JAR the name of the main class
... so generate a build.xml shouldn't be too hard.
Anybody interested in writing a Mojo for that?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org