Forwarding FYI. I'm pretty sure this is an area that interests a lot of you. For those interested please feel free to come and discuss it on the cargo lists.
For a quick summary of what this is about, check: http://tinyurl.com/le5mq Thanks -Vincent -----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: jeudi 30 mars 2006 13:31 To: [EMAIL PROTECTED] Subject: [cargo-dev] RE: [Idea] Customization Hi Cargo devs, Juri has started working on this. I've committed his work in the contrib/customizer/ area (https://svn.codehaus.org/cargo/cargo/trunk/contrib/customizer/). The idea is for all of you to provide input. I didn't get much feedback on the proposal below... :-) I believe this is going to be big as there's real need for packaging J2EE archives depending on an environment. There's currently no neat solution for any build tool (ant, maven1, maven2) that I know of. The idea is to offer this feature in Cargo. So if you're using maven1 or maven2 for example you'll be able to have your normal build that builds your modules independently of any environment and then have an environment module which will repackage your artifacts and modify their contents depending on your environments. There are still a lot of work to be done and we need all possible inputs and help. Thanks -Vincent > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: lundi 13 mars 2006 14:47 > To: '[EMAIL PROTECTED]' > Subject: [Idea] Customization > > Hi, > > I've sent 2 proposals recently: > > * one about supporting configuration customization through the use of > regexp. See http://tinyurl.com/77aa9 > > * another about generating J2EE archives for different environments and > more generally a proposal to support modifying any type of zip file using > regexps. See http://tinyurl.com/le5mq > > I've just had the idea of merging the two proposals in one. Imagine the > following: > > * Ability to take a dir or a zip file as input > * Generate a new zip/dir or the same zip/dir but updated > * Customizations brought on files/input streams. > > This would allow all sort of use cases and would solve our issue of custom > configurations + the issue of customizing J2EE archives for any > environment. > > Technical ideas: > > * Define a Customization interface > - takes an input stream source > - generate an output stream destination > - apply a set of transformations to the input stream > * Several Customization implementations possible > - AntTokenCustomization > - RegexpCustomization > * A CustomizationPack to regroup several Customization together and to > work on zips or directories. Several implementations: > - ZipCustomizationPack > - DirectoryCustomizationPack > * Modify the LocalConfiguration interface to add a new API: > - LocalConfiguration.addCustomizationPack(...) > * Refactor current Ant token filters in configuration code to use the > AntTokenCustomization class and define a default pack for each container's > configuration. Users customization packs could be added after the default > pack. > > WDYT? > > Thanks > -Vincent ___________________________________________________________________________ Nouveau : tiliphonez moins cher avec Yahoo! Messenger ! Dicouvez les tarifs exceptionnels pour appeler la France et l'international. Tilichargez sur http://fr.messenger.yahoo.com ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
