Hi Mike I believe we will have it once we have our automatic build running and once it would be able to download the wink distribution zip from the Wink site.
Once we have it set, all a developer would need to do in order to use Wink would be to download and unzip the wink-0.1.zip. Then he will have all the wink jars, examples code and ant or maven scripts to build these examples. >From that point he can modify the examples, add his own code and rebuilt them using an already exist ant or maven scripts. He can even deploy and run the examples automatically using the maven jetty plug-in. I'm not sure if everyone is familiar with the wink distribution package and how to build it. To build the distribution package fallow the "distribution package" section in the "howToBuild.txt" file located in the trunk root folder (very simple 4 cmd commands). Let me know what do you think Eli -----Original Message----- From: Michael Rheinheimer [mailto:[email protected]] Sent: Tuesday, June 30, 2009 9:44 PM To: [email protected] Subject: ease of WINK adoption Team, To simplify building up a WINK-based JAX-RS application, I wanted to float some ideas. Currently, if I'm a JAX-RS app developer and want to use WINK, I have to pull the SVN repo, build from trunk, then build samples, then go break open a sample .war and see what it looks like. To simplify this process for app developers wanting to use WINK, here are a few ideas: 1) provide a template area where app developers can drop their app source code, and an ANT script that will build everything up, including the final .war file the user will need. Pros: simple! Developers don't have to crack open any .war files, learn any new IDEs, etc. Could become part of a future tools suite, allowing developers (or IDE tool) to pick and choose what libraries to include in the .war, and build up the proper data in the deployment metadata. Cons: requires developers to have ANT installed. Probably requires developers to pull WINK source (depending on how this type of solution might be provided) 2) build a template war file, where app developers can drop in their already-built app Pros: also simple. Smaller amount of work for the WINK team to develop this solution, I think. Does not require pulling WINK source from SVN, no need for ANT or an IDE. Cons: WAR file may have much more than the app developer actually needs, thus a heavy disk footprint, but developer could simply remove libs or components that are not needed. Personally, I like (2). This isn't intended to open a big tools discussion, I just wanted to propose an idea about making life easy for app developers wanting to prototype their JAX-RS apps with WINK. What other ideas are there? What kind of tools does Symphony provide? Thanks. mike
