On 8/1/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto:
<snip> > >> In fact it does not build anything from source: it only has to take the > >> original SAR, replace the config.xml and add some library. > >> > >> Maybe the tool (another ant script) would also be useful to people > >> downloading the binary distribution (well, in fact it is only a zip > >> file, but I saw some user has problems working with it). > > > > i agree that a SAR manipulation tool would be useful for the binary > > distribution. IIRC pheonix ships an ant task for this. would need to > > think about whether documentation on customisation would be better > > than an actual script. > > > > - robert > > Maybe it's time to split the sar generation from the phoenix-deployment. > This way we could have a module building the sar and another module that > takes the sar and place it in the phoenix distribution to create a > binary build. The ant script used for this last action could be almost > the same used by the binary distribution to create custom sar. > I don't know if the api-library-function-deployment layers are enough to > do that. i suppose the bigger question is how to approach binary distributions once JAMES supports multiple containers: do we issue an distribution per container or one distribution containing multiple artifacts? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
