Thanks Raymond
I'm seeing missing import-package headers too. The issue is far deeper than
just the split packages. It creates quite a few dependencies to the
internal implementation classes. We need to find better ways to handle
such things.
+1
I fixed the obvious ones under r810317 and
I note that the domain-node module defines the package...
org.apache.tuscany.sca.node
Which is also defined in node-api. Is this necessary? How about
org.apache.tuscany.sca.domain.node
I can't get my Eclipse PDE workspace to settle down with the latest
2.x code (I do get a clean maven build)
On Tue, Sep 1, 2009 at 2:41 PM, Simon Lawssimonsl...@googlemail.com wrote:
How about
org.apache.tuscany.sca.domain.node
That seems fine for now so go for it. We can rationalize all the
domainy modules and packages later on.
...ant
I'm also getting lots of manifest problems in the domain-node and
endpoint-wrapper area. Are the manifests in svn intended to be
correct?
Simon
simonsl...@googlemail.com
Sent: Tuesday, September 01, 2009 7:01 AM
To: dev@tuscany.apache.org; antel...@apache.org
Subject: Re: [2.x] split package in domain node
I'm also getting lots of manifest problems in the domain-node and
endpoint-wrapper area. Are the manifests in svn intended
