yes but it's UNdeprecated in jdk 5.0 :) On 11/19/05, Edwin Punzalan (JIRA) <[EMAIL PROTECTED]> wrote: > [ http://jira.codehaus.org/browse/MNG-1525?page=comments#action_51395 ] > > Edwin Punzalan commented on MNG-1525: > ------------------------------------- > > You see, Maven's minimum JDK requirement is 1.4. And getEnv() in 1.4 is > already deprecated. > > Right now, I'm adding a method to retrieve the environment variables defined > in a machine by executing "cmd /C set" for windows, or (since "set" is not > working in your OS) "/usr/bin/printenv" for *NIX machines. > > We're still open for suggesstions on how to do this, btw. ^_^ > > > Allow environment variables to be referenced in pom.xml, settings.xml, etc. > > --------------------------------------------------------------------------- > > > > Key: MNG-1525 > > URL: http://jira.codehaus.org/browse/MNG-1525 > > Project: Maven 2 > > Type: New Feature > > Versions: 2.0 > > Environment: Red Hat Linux, Java 5, Maven 2 > > Reporter: Richard Allen > > Assignee: Edwin Punzalan > > Fix For: 2.0.1 > > > > > > > Maven should allow environment variables to be referenced; similar to Java > > System properties. Ant allows this to be done using the following syntax: > > <property environment="env"/> > > ${env.CATALINA_BASE} > > where CATALINA_BASE has been defined like: > > export CATALINA_BASE=$HOME/tomcat > > In Maven, an example use for signing jars might be: > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-jar-plugin</artifactId> > > <executions> > > <execution> > > <goals> > > <goal>sign</goal> > > </goals> > > </execution> > > </executions> > > <configuration> > > <keystore>${env.KEYSTORE_FILE}</keystore> > > <storepass>${env.KEYSTORE_PASS}</storepass> > > <alias>${env.KEYSTORE_ALIAS}</alias> > > > > <jarPath>${project.build.directory}/${project.build.finalName}.jar</jarPath> > > </configuration> > > </plugin> > > where KEYSTORE_FILE, KEYSTORE_PASS, and KEYSTORE_ALIAS are environment > > variables. > > It would also be very useful to have environment variables available when > > defining filter properties files. For instance: > > # application.properties > > deploy.dir=${env.CATALINA_BASE}/webapps > > Environment variables can be referenced in Java like: > > Map<String, String> environmentVariables = java.lang.System.getenv(); > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://jira.codehaus.org/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]