Trunk is now 6.1.0-SNAPSHOT and development can continue as normal towards the 6.1.0 release. The 6.0.x branch was created off of trunk revision 622 and will be used to actually cut the 6.0.0 release (which was delayed by a variety of minor set backs) tomorrow.
The 6.0.0 release has been pushed to Monday.
The delay was due to config changes that break the Designer import process. Ramesh has addressed that and the other remaining concerns with Designer compatibility, so we will proceed with calling our current code 6.0.0 - consider the trunk effectively frozen.
Any patches that may be needed by Designer for their initial release will be managed by the Designer project if and until there are sufficient issues to warrant a 6.0.1 Teiid release.
We have reached a milestone of sorts. Even after importing several years of backlogged defects, we now have more issues worked than open. From here we will continue to sharpen our focus and work down outstanding issues - especially after the 6.1.0 release. Congratulations to all.
Now on to the 6.0.0 release. Everything still looks good for next Friday. Early in the week we will synch up with the Designer to ensure there are no blockers due to integration. Note that much of the community documentation effort is now being put off to 6.1.0 or beyond.
Check to see the dependencies you are looking are in
If you see them there, then you can use them in your project, if not you
can add it to the above repository. This maven2 repo is nothing but a
SVN repo, so, you can add your library at
however, make sure you adding them at correct place, and you do not have
to download whole repo to just add one project, you can just download
which ever folder level, you are adding the library using the command
line svn client. Once you add them you can use that library in your
module. If possible always add source code for the library you are
Now to the tests, if anything making external connections, either
internal systems are external systems CAN NOT be in the project's tests.
if you can mock them you can include in your project, if it involves
multiple modules, you can include them in the "teiid-test-integrations"
project, still with no external connectivity. The idea here is that any
developer who is working on the code is not mandated to have a network
If you need to connect to external source, please write that test in the
On Thu, 2009-03-12 at 09:03 -0400, John Doyle wrote:
> hey guys,
> I need to add a couple of new dependencies for the xml connector to support the streaming rewrite. What's the process for getting these into the repos for hudson? Is there some doc you can point me to?
> Also, I want to add a couple of simple ConnectorHost based tests for the XML-HTTP connector. I don't see a lightweight http server like Jetty in our dependencies that I can use. Is there one that I just missed or would I have to add one?