Hi Simone, I tend to agree with Raymond on this one.
On Jul 6, 2012, at 8:39 PM, Simone Tripodi wrote: > Hi Raymond > > thanks for your feedbacks! I wouldn't create an assembly for each > module we have - maybe the common shared libs could be contained in > the "end user" libs... > > Does anyone has an idea which are most valuable end-user modules? those module IMHO would be at least (for the moment) oauth2-client oauth2-resourceserver oauth2-common oauth2-authzserver Regards Antonio > > Best and thanks, > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > On Thu, Jul 5, 2012 at 7:46 PM, Raymond Feng <[email protected]> wrote: >> Hi, >> >> For Amber, it will be probably used as a library of jars at this point since >> we don't have a fully-fledged oAuth 2.0 server application yet. I suggest >> that we create a simple binary dist that contains all the jars that Amber >> produces and depends. Of course, we'll publish the amber jars into maven >> repo :-). >> >> Thanks, >> Raymond >> >> On Jul 4, 2012, at 1:29 AM, Simone Tripodi wrote: >> >>> Hi all guys, >>> >>> while it is clear that here at ASF we release *sources* and that it is >>> a good practice to redistribute precompiled packages, I would like to >>> understand - hopefully some of you could help me - which are the >>> modules/packages we intend to redistribute to users. >>> >>> I mean, just to take a sample, at Any23 we redistribute a CLI tool - >>> which contains dependencies - that is the any23 "product" that users >>> download-extract-launch... do we have something similar at Amber? Or >>> having Amber in form of Maven-artifacts only already satisfies the >>> users needs? >>> >>> Many thanks in advance, all the best! >>> -Simo >>> >>> http://people.apache.org/~simonetripodi/ >>> http://simonetripodi.livejournal.com/ >>> http://twitter.com/simonetripodi >>> http://www.99soft.org/ >>
