Based on the discussions we had before, the workspace/workspace-impl should
be used to deal with a collection of contributions including resolving the
cross-contribution import/export. It will be very strange to have
contribution processing depend on code in node-api/node-impl.
I'm still in favor of leaving the functions in workspace/workspace-impl and
have node-api/node-impl reference workspace.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Tuesday, June 09, 2009 3:33 AM
To: <[email protected]>
Subject: Re: Node usage of the workspace and implementation-node modules
But what is the function needed that we the old workspace modules
would be used for? All the code that was there has been added to
various other modules now like the contribution ones or the node-api
and node-impl. What is left in workspace or workspace-impl that we
need to bring back?
...ant
On Mon, Jun 8, 2009 at 5:22 PM, Raymond Feng<[email protected]> wrote:
I'm responding to Ram's question on how to resolve the artifacts within
the
SCA domain following import/export directives. I don't think it has
anything
to do with the endpoints.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Monday, June 08, 2009 8:50 AM
To: <[email protected]>
Subject: Re: Node usage of the workspace and implementation-node modules
On Mon, Jun 8, 2009 at 4:42 PM, Raymond Feng<[email protected]> wrote:
The 2.x workspace and workspace-impl modules are in the contrib folder.
I
suggest you re-activate them for your work.
Why? What is the use case that they would be handling thats not going
to be supported by the new endpoint resolution that is working now?
...ant
