In various other caliper posts, it would seem that Caliper was approaching a 1.0 release sometime in October (i.e,. in August the answers were along the line "wait two months"), but there hasn't been any activity in the git repo since June 18th. Any update?
I hope to have it out very early next year.
According to this answer to my question, it's "coming very, very soon".
Related
About 5 yrs ago I bought 'Practical Dojo Projects' and 'The Concise Guide to Dojo' (Wrox.) But these 2008 & 2009 books don't even mention which version they are written for. I now have a project I want to do in Dojo. Are these books of any use today or will they just confuse me because of the major changes in Dojo ? Should I just wait (maybe 2 years or more ???) for Dojo 2.0 to be released ?
What is written in these books is still valid but outdated.
Thanks to a very good backward compatibility from Dojo, almost all what you will read in the books can still be used.
However, Dojo syntax has changed and even if the legacy syntax (the one in the books) is still valid, they now encourage you to use the AMD syntax.
this page will help you "converting" the syntax in the book into the more modern syntax. Appart the syntax change, almost all what you learn in the books is still valid.
Most programming books are outdated especially if they were writing ~8 years ago. Your best bet is to read their docs, recent tutorials, or any articles about the framework. Also make sure the community around the tool is still active and that you can get support if you get stock anywhere in the middle of dev your new app.
Recently, our team has starting using http://swagger.io/, which after tweaking a bit how we'd need to work has worked very well for us. The Swagger UI with the prebuilt documentation is quite helpful.
Part of the other reason we started using Swagger was to try and take advantage of Swagger Code Generation, which is the hope of easily generated SDKs. It takes a bit to figure out, but once it is configured it seems to be doing a decent job.
Ultimately, my question is does anyone have experience with Swagger Code Gen, and can speak to their experience with it? We've felt it is a bit of a immature tool (at this stage), and are trying to balance how much is worth either tweaking Swagger Code Gen to get it working or even compromise aspects of our API to get it there.
Thanks
Dan
There's been a lot of improvements to Swagger Codegen since your question in March 2015. More than 300 PRs have been merged. The latest version 2.1.4 was released 2 weeks ago.
There are many examples that developers using it in production. Here is one recent example.
Please give it another try and report here if you've any feedback for the Swagger Codegen community.
I recently (as of monday just gone) started a new job where the system they use is based upon ardor3d.
I require a full API list / Any user documentation available as the company have none and from what I can tell the main author of the technology has decided to shut the project down
Any docs or help you gave provide would be fantastic
Thanks
Please read those articles:
Ardor3D on Wikipedia
JogAmp's Ardor3D Continuation Overview
To sum up, your link points out to an obsolete unmaintained version of Ardor3D. I'll publish a huge tutorial about JogAmp's Ardor3D Continuation before the end of September with the detailed procedure to install it, build it and use it with Ant, Maven, Gradle, Eclipse, Netbeans and in command line.
JogAmp's Ardor3D Continuation is alive, I can publish the Java documentation Monday or Tuesday if you really need it.
If you prefer using an obsolete version of Ardor3D, I won't be able to help you and you will miss tons of enhancements, more than 60 commits. Feel free to contact the JogAmp community on our official forum.
N.B: The brand new JogAmp's Ardor3D Continuation user's guide is here, it contains about 95 simple examples, good luck.
N.B: The API documentation is here.
It would appear that for all my searching I've found something.
Given how long it took to find and how obscure it was to actually find I'm going to leave the link for it here:
http://grepcode.com/project/repo1.maven.org/maven2/com.ardor3d/ardor3d-core/
In the hopes that if someone else is ever in the same position this'll help them
I am an NHibernate newbie so I apologize if there is an obvious answer to this that I'm missing.
I see some questions on SO and some blog posts referring to NHibernate 3. But when I go to nhforge.org, it looks like the current downloads are for 2.1.2. Is 3 still a work in progress? Are there betas available somewhere? Documentation? Is there an established timeframe / roadmap for 3.X?
Update:
NH 3 has been released :)
http://sourceforge.net/projects/nhibernate/files/
You can download the latest NHibernate 3.0 Alpha from Sourceforge and view the roadmap / change log for the project on the NHibernate Issue Tracker.
If you click on the "Download Now NH 2.1.2" link on the NHForge home page, that will bring you to the download location for NH 3.0 Alpha 2 source and binaries.
http://nhibernate.info/
For release notes, see this thread from the NH user's group (basically, release notes are available in the download):
http://groups.google.com/group/nhusers/browse_thread/thread/e0cc47b01207b5ae/ef89fb5218e46fd7?lnk=raot&fwc=1&pli=1
Here is an NHibernate features page. Some, but not all, of the 3.0 features are called out here:
http://nhibernate.info/doc/nhibernate-features.html
The NHibernate documentation is here:
http://nhibernate.info/doc/nh/en/index.html
But the documentation doesn't appear to have been updated for NHibernate 3.0 yet. Most of the 3.0 features have documentation available on various blog posts that you can find through Google searches. I'm sure the project would love to have a volunteer pull all the documentation together in one place.
The timeframe / roadmap for NHibernate 3.0 to be officially released is whenever the important bugs have all been fixed. You can watch the progress on bug fixes on the NHibernate JIRA:
https://nhibernate.jira.com/browse/NH
Like most software, NHibernate 3.0 will be released when "it's ready". Here's a quote from Fabio, the project lead for NHibernate:
Roadmap: we hope to fix all of the
actual existing open issues but
because we know that it will be
impossible we can only say you that we
will release NH3 before the end of
this year.
(Source: http://groups.google.com/group/nhusers/msg/40769ab8b95750fc)
From the NHUsers mailing list, it sounds like quite a few people are running NH 3.0 in production.
You can find some information about NH3 from this podcast
http://www.hanselman.com/blog/HanselminutesPodcast225LearningAboutNHibernate3WithJasonDentler.aspx
You can also find the source for the project on source Forge
http://sourceforge.net/projects/nhibernate/files/
It hasn't been released yet. I believe it's still in the alpha stage, as per the wiki
And actually, after listening to Hanselminutes Podcast 225 - Learning about NHibernate 3 with Jason Dentler, http://nhibernate.info/ is a great place to get all the information you're looking for.
Check their website.
You can download binaries there: http://sourceforge.net/projects/nhibernate/files/NHibernate/
I'm getting ready to deploy the first release of our software, version 1.0. Once it's out to our customer, inevitably, some bugs will be found. When I fix those bugs though, I'm not sure what "best practice" is for versioning it. When I release the fixes, would that be an entirely new version (in maven), such as 1.01 (or whatever the increment is, 1.1 for example)? Or would it still be 1.0 with some sort of classifier (maybe a date tag)?
Thanks,
Jeff
Wikipedia has a surprisingly thorough discussion of software versioning. It covers all the major points and discusses most of the approaches I've seen.
(In your specific case I'd go with 1.0.1 which would generally be regarded as "an update to 1.0 with no significant feature additions")
You have to change the number in order for maven clients to recognize a newer version in the repository. The change is up to you. I'm sure there's a best practice document somewhere but my company dictates the numbers we use so I've never looked for one.