tuscany-sca-all jar is empty

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

In the distribution that I just build from a complete checkout
earlier today, the tuscany-sca-all-1.0-incubating-SNAPSHOT.jar
is empty apart from pom.xml, pom.properties, and Manifest.mf.
I can't immediately spot the error in the pom.  If someone else
can see the problem, please reply here, otherwise I'll look into
it a bit later on.

   Simon



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

Re: tuscany-sca-all jar is empty

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

Done http://issues.apache.org/jira/browse/TUSCANY-1265. I'll take a look at
it a little later.

Simon

Re: tuscany-sca-all jar is empty

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

On 5/10/07, Simon Laws <si...@googlemail.com> wrote:
>
> Simon
>
> I get the same effect here. It's because the shaded bundle jar can't be
> copied over the original jar. The shader plugin that is used here is alpha
> and has zero docs so I really can't tell what it's doing or why it's going
> worng without diving into the code. I took a quick look but I couldn't see
> anything obvious. I'm assuming it runs OK for ant as he has been producing
> distributions so must be something about my (our)  environment. My
> temporary
> solution to get round it is to
>
> 1/ build the bundle and copy the shaded jar over the jar that is
> automatically put in the .m2 maven repository by the bundle build
> 2/ comment out the bundle module in the distribution build and run the
> distribution build.
>
> Simon
>

Ideally the distro's should be recreatable by anyone and in the future from
our published src distro, so this doesn't seem very good. Probably we should
have a jira for this and could either of you do a bit more debugging? Does
anyone else see this? Has anyone other than me successfully built the binary
distro?

   ...ant

Re: tuscany-sca-all jar is empty

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

Simon

I get the same effect here. It's because the shaded bundle jar can't be
copied over the original jar. The shader plugin that is used here is alpha
and has zero docs so I really can't tell what it's doing or why it's going
worng without diving into the code. I took a quick look but I couldn't see
anything obvious. I'm assuming it runs OK for ant as he has been producing
distributions so must be something about my (our)  environment. My temporary
solution to get round it is to

1/ build the bundle and copy the shaded jar over the jar that is
automatically put in the .m2 maven repository by the bundle build
2/ comment out the bundle module in the distribution build and run the
distribution build.

Simon