Ant, sure, I wasn't planning to do it right now, but the fact that the JIRA components changed caused me to post the note as a heads up. I did mention in the JIRA that we wouldn't necessarily see the build breaking immediately, and the effect would be more subtle, but I forgot that aspect of the scenario when posting just now.
Kelvin. On 19/07/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
Ant, sure, I wasn't planning to do it right now, but the fact that the JIRA components changed caused me to post the note as a heads up. I did mention in the JIRA that we wouldn't necessarily see the build breaking immediately, and the effect would be more subtle, but I forgot that aspect of the scenario when posting just now. Kelvin. On 19/07/07, ant elder <[EMAIL PROTECTED]> wrote: > > > > On 7/19/07, kelvin goodson < [EMAIL PROTECTED]> wrote: > > > > I opened https://issues.apache.org/jira/browse/TUSCANY-1437 a few days > > back > > with multiple components, touching DAS and SCA as well as SDO in order > > that > > it was understood that there were impacts on all these components. > > > > The groupId for the API artifact needs to change to > > org.apache.tuscany.sdoand the artifact-id to > > tuscany-sdo-api-r2.1 . This change arose from feedback on the release > > candidate. > > > > The branch for the SDO 1.0 release already has this renaming in place, > > but > > we need a coordinated effort in making this change in the trunk. A > > knock on > > effect of the change is that the api jar name has an additional > > "tuscany-" > > prefix on it, so scripts that set up classpaths might need to be > > changed. > > > > The components on this JIRA have just been reset to SDO-Implem, so > > it's > > clear that I didn't communicate the cross component nature of the > > issue very > > well through that JIRA. In the body of the JIRA I asked people > > working in > > the affected component areas to identify the places where this change > > occurs. > > > > Please feed back either in the JIRA or on this thread, the places > > which are > > likely to break if we don't coordinate this change, and better still > > provide a patch for that area so that i can apply all the changes > > synchronously. > > > It may not be so bad - if the artifacts with the old name remain in the > maven repository then while that old api is compatible with the impl then > things should still keep on working, shouldn't they? So that would give us a > bit of leeway. Searching the SCA code base there's quite a lot of places > needing change, I can help do that but would be good if it could be left > till at least next week. > > ...ant > > >
