On Jul 28, 2009, at 8:24 PM, Baram, Eliezer wrote:
The thought behind this format of release was to support both Maven
users and ant users. Maven users can use the examples' poms, and for
Ant users we bring build.xmls and all the third parties.
I think its fine to provide Ant build scripts for samples, though IMO
that is just extra work to maintain them. I'm also fine with just
asking users to fetch mvn and use it. It is actually a smaller user
dowload ;-)
The wink-server and the wink-client are located under the dist/
components folder while a collaborate jar of all the components is
located under dist.
It might be that the collaborate jar and the fact that the server,
client, etc jars are a little hidden is confusing. I think we can
omit the collaborate jar and move all the component one level up.
Will this make the release more understandable?
Yes, I would like to just see each artifact which is produced. Leave
uberjaring to advanced folks that need that.
--jason
--Eli
-----Original Message-----
From: Jason Dillon [mailto:[email protected]] On Behalf Of
Jason Dillon
Sent: Tuesday, July 28, 2009 3:29 PM
To: [email protected]
Subject: Re: [discuss] Wink 0.1 updated proposal
The release outputs for Wink currently boggle my mind, coming from a
Maven standpoint I don't really understand what is intended to be in
the release and what is not. The ant-based release muck confuses me
even more as I don't see things like wink-client or wink-server jars.
Is this really how we want to release wink?
--jason
On Jul 21, 2009, at 12:48 PM, Nicholas L Gallardo wrote:
In the interest of getting a Wink 0.1 out as soon as possible,
here's an
updated proposal for the release.
None of the issues currently marked for 0.1 are show stoppers.
Let's move
those issues to 0.2 and cut a 0.1 release with what we have today
(with one
exception, addressed below).
If my proposal for a 6-week release interval is accepted, then we
can just
wrap all of the remaining issues in the next few weeks and they'd be
available soon in the Wink-0.2 release.
It looks like we have agreement on disabling x-http-method-override
by
default in WINK-76 (https://issues.apache.org/jira/browse/WINK-76).
We
should just flip that switch and close it out for Wink 0.1 so that
we're
consistent across all releases.
Thoughts?
-Nick
Nicholas Gallardo
WebSphere - REST & WebServices Development
[email protected]
Phone: 512-286-6258
Building: 903 / 5G-016
