Great!!. Do you also plan to have maven profiles for these three? You can see the usage of checking out source and only building client or xbaya and so on?
Suresh On Dec 5, 2012, at 11:54 AM, Lahiru Gunathilake <[email protected]> wrote: > Since Amila is busy with integration tests, I can work on having multiple > build distribtuions. My plan is to have three separate directories in > distribution and build these above three packs on them. > > Those would be airavata-server, xbaya-gui, airavata-client .. inside > distribution folder. > > > Thanks > Lahiru > On Fri, Nov 30, 2012 at 11:54 PM, Suresh Marru <[email protected]> wrote: > >> A big + 1, this was long overdue. Thanks Saminda and Amila for initiating >> and jumping onto this. >> >> We may also want to consider creating the JNLP as part of the default >> build. For instance, we can have a associated JNLP bundled with the server. >> That way we can have users directly click on JNLP and launch XBaya which is >> pointed to the server. >> >> Cheers, >> Suresh >> >> On Nov 29, 2012, at 12:22 PM, Saminda Wijeratne <[email protected]> >> wrote: >> >>> Hi Devs, >>> >>> Currently we have both XBaya & the Airavata services bundled together >> when >>> we create the final distribution. This can arise confusion to the users & >>> unnecessary overhead of retrieving/understanding/configuring for >> different >>> stakeholders. Shall we have different distributions as follows? >>> >>> >>> 1. Airavata server binary distribution - everything related to hosting >>> an Airavata Server >>> 2. XBaya binary distribution - everything needed for XBaya >>> to run independently >>> 3. Airavata client binary distribution - all the libraries required >>> for a 3rd party client to use the Airavata API >>> >>> >>> (This would mean that we'll have 3 binary packs for an Airavata release) >>> >>> Regards, >>> Saminda >> >> > > > -- > System Analyst Programmer > PTI Lab > Indiana University
