On Jul 11, 2006, at 11:18 AM, Raymond Feng wrote:
Hi,
Now I can build all the projects except "runtime/standalone" (same
problem as I reported before).
Unfortunately, it worked for me with a clean repo (rm ~/.m2/repository).
Can you remove either the whole repo or the maven-assembly-plugin
directory and try again.
The databinding-sdo project already has everthing from sdo project
so the sdo folder can be safely removed. With the databinding-sdo
referencing the incubating-M1 version of SDO, I can build it
successfully as well (as expected, I need to have the SDO jars in
local maven repo).
Now it seems that we fetch SDO projects (except the spec one) into
the sandbox, but they are not in the main build. What's the
intension here?
My problem with sdo was that I didn't have a copy locally so it
downloaded the M1 version from the repo. That didn't have the recent
changes in it.
When we release something, we need to modify the version in the trunk
to be a SNAPSHOT of the /next/ version so that locally built stuff
does not conflict with what is in the online repo. We now have
TUSCANY-537 to make that change in the sdo trunk.
I have added an external reference to it from the sandbox code so
when you update sandbox/jboynes you will get a live copy of the sdo
tree. Once we've fixed the version numbers we can include that in the
sandbox build just like it is included in trunk. At that point we can
re-enable the databinding code.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
