fixed path to jar files so that build.cmd all works
#10
Conversation
rather then writing Version: ${waffle.version}, write "Implementaion
Version"
This lets us use:
getPackage().getImplementationVersion()
to read the version information
this avoids compiler warnings when running from java 1.6 or 1.7
Add the ability to run samples direclty from eclipse. Just run: StartEmbeddedJetty.java
Adding a utility to collect all system information into an XML document Adds a servlet to return this information (sorry, the web.xml was added in the previous commit)
|
I'm still learning how to use git/github, so forgive me if I have made things complicated (and let me know how to make things easier) I added a utility class to help debug the environments I am still struggling to get working. Long term it would be great to have a simple servlet that can check all the standard things and report back. This is a first step in that direction. This uses the builtin javax.xml package to build an XML document. This avoids the need for another dependency, but has a really ugly API |
|
First, thanks for the pull. There's a lot of other stuff here that's nothing to do with fixing paths. There's a Jetty server? At this point master is finished, we're working on the 1.5 branch that has a ton of changes. We should have made master the next release and tagged the previous one, but this is the way it is for now :) Please check that branch, the build.cmd should be all good. Plus the documentation is now in markdown and there's a section on contributing that talks about setting up a development environment. Looking forward to your PRs into 1.5 and beyond. Thanks. |
|
Sorry, this was really two requests (and one trivial one) and not yet understanding github
I'll start over off the 1.5 branch and try to make two pull requests |
No description provided.