continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Venisse <emman...@venisse.net>
Subject Re: Continuum Profiles
Date Mon, 11 Jun 2007 08:18:41 GMT
I think we can let users choose anv var they want

Emmanuel

LAMY Olivier a écrit :
> Hi,
> Yes sure, you're right.
> Will we use only this predefined list of env var ?
> If yes, I think ANT_OPTS is needed too ?
> 
> --
> Olivier  
> 
> -----Message d'origine-----
> De : Emmanuel Venisse [mailto:emmanuel@venisse.net] 
> Envoyé : samedi 9 juin 2007 10:37
> À : continuum-dev@maven.apache.org
> Objet : Re: Continuum Profiles
> 
> I understand what you mean BUT Continuum never call java directly but always use maven,
mvn, and or a shell script, so it don't have to use directly an env var like -Djava.awt.headless=true
> If you need this env var for maven, you must set it with MAVEN_OPTS and if it's for plugins,
in plugin configuration if it's possible.
> 
> JDK, Maven 2, Maven 1 and ANT installations are only to set the root directory of tools,
maybe we need only env var lile JAVA_HOME, M2_HOME, MAVEN_HOME and ANT_HOME
> 
> Emmanuel
> 
> LAMY Olivier a écrit :
>> Hi,
>>
>> This means adding a type (jdk, builder, envs) field in Installation in the model
?  
>>
>> If I look [1], how can I say :
>> - use MAVEN_OPTS (-Xms512m -Xmx512m) with maven builder 
>> - use env variable (-Djava.awt.headless=true) with jdk 
>>
>> Why not adding a field envargument in Installation and add this field in [2]
>>
>> I know it changes the model :-)
>>
>> --
>> Olivier
>>
>> [1] http://people.apache.org/~evenisse/design/continuum/continuum_profiles/profile.htm.
>> [2] http://people.apache.org/~evenisse/design/continuum/continuum_profiles/installation_read.htm
>>
>> -----Message d'origine-----
>> De : Emmanuel Venisse [mailto:emmanuel@venisse.net] 
>> Envoyé : samedi 9 juin 2007 09:34
>> À : continuum-dev@maven.apache.org
>> Objet : Re: Continuum Profiles
>>
>> I updated pages with the installation types and environment variables.
>>
>> Emmanuel
>>
>> Emmanuel Venisse a écrit :
>>> Yes, I'll change installations screens to define the installation type.
>>> environment variables will be added too.
>>>
>>> Emmanuel
>>>
>>> LAMY Olivier a écrit :
>>>> Hi,
>>>>
>>>> Very nice idea. Just some remarks concerning the actual continuum model.
>>>>
>>>> Builder and Jdk have the same type (Installation), I think this must 
>>>> be splitted in two types in order to prevent user to add a Builder as 
>>>> a Jdk (screen [1]) when they build a profile.
>>>>
>>>> Then it could be nice to can add some environnement variable for 
>>>> builder/jdk (as MAVEN_OPTS or some stuff like 
>>>> -Djava.awt.headless=true for a jdk) (as say [2]).
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier
>>>>
>>>>
>>>> [1]
>>>> http://people.apache.org/~evenisse/design/continuum/continuum_profile
>>>> s/profile.htm
>>>>
>>>> [2]
>>>> http://people.apache.org/~evenisse/design/continuum/continuum_profile
>>>> s/installations.htm
>>>>
>>>>
>>>> -----Message d'origine-----
>>>> De : Emmanuel Venisse [mailto:emmanuel@venisse.net] Envoyé : vendredi
>>>> 8 juin 2007 20:16
>>>> À : continuum-dev@maven.apache.org
>>>> Objet : Continuum Profiles
>>>>
>>>> Hi,
>>>>
>>>> I wrote a little doc
>>>> (http://docs.codehaus.org/display/CONTINUUM/CI+profiles) about what I 
>>>> think we need to implement to add profiles in Continum.
>>>>
>>>> I don't think we can implement all features in 1.1 because it's a big 
>>>> work.
>>>>
>>>> The work can be split like that:
>>>> 1.1: add installation screens, basic profile screens (set of
>>>> installations) and the possibility to add a profile to a build 
>>>> definition
>>>> 1.2: advanced profiles (Remove build definitions and move schedule, 
>>>> build file, scm policy to the profile) with combined profiles.
>>>>
>>>> Screens attached to CONTINUUM-44 don't integrate advanced profiles, I 
>>>> think they will be available next week.
>>>>
>>>> Any comments are welcome.
>>>> Thanks.
>>>>
>>>> Emmanuel
>>>>
>>>>
>>>> This e-mail, any attachments and the information contained therein 
>>>> ("this message") are confidential and intended solely for the use of 
>>>> the addressee(s). If you have received this message in error please 
>>>> send it back to the sender and delete it. Unauthorized publication, 
>>>> use, dissemination or disclosure of this message, either in whole or 
>>>> in part is strictly prohibited.
>>>> *********************************************************************
>>>> * Ce message électronique et tous les fichiers joints ainsi que  les 
>>>> informations contenues dans ce message ( ci après "le message" ), 
>>>> sont confidentiels et destinés exclusivement à l'usage de la  
>>>> personne à laquelle ils sont adressés. Si vous avez reçu ce message 
>>>> par erreur, merci  de le renvoyer à son émetteur et de le détruire. 
>>>> Toutes diffusion, publication, totale ou partielle ou divulgation 
>>>> sous quelque forme que se soit non expressément autorisées de ce 
>>>> message, sont interdites.
>>>> *********************************************************************
>>>> *
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
> 
> 
> 


Mime
View raw message