Manfred and Michael
rom what ive read gmaven has a hidden dependency on GROOVY being fully
operational before gmaven-plugin will run so you're going to need to setup env
vars
GROOVY_HOME
if "%GROOVY_HOME%" == "" set GROOVY_HOME=%DIRNAME%.
PROGNAME
PROGNAME=`basename "$0"`
GROOVY_OPTS
set GROOVY_OPTS="-Xmx128m"
set GROOVY_OPTS=%GROOVY_OPTS% -Dprogram.name="%PROGNAME%"
set GROOVY_OPTS=%GROOVY_OPTS% -Dgroovy.home="%GROOVY_HOME%"
STARTER_MAIN_CLASS
set STARTER_MAIN_CLASS=org.codehaus.groovy.tools.GroovyStarter
STARTER_CONF
set STARTER_CONF=%GROOVY_HOME%\conf\groovy-starter.conf
TOOLS_JAR
if exist "%JAVA_HOME%\lib\tools.jar" set TOOLS_JAR=%JAVA_HOME%\lib\tools.jar
Here is my groovy-starter.conf you can use to get you going
# load required libraries
load !{groovy.home}/lib/*.jar
# load user specific libraries
load !{user.home}/.groovy/lib/*.jar
# tools.jar for ant tasks
load ${tools.jar}
STARTER_CLASSPATH
set STARTER_CLASSPATH=%GROOVY_HOME%\lib\@GROOVYJAR@
you will also want to take a look at .\gradle\assemble.gradle to determine
if you will build for an OSGI container
how to construct MANIFEST.MF
location of jars
location of starter classes
gradle has its own build environment so you're going to want to transfer all of
the assemble.gradle properties and attributes over to your pom
also since groovy has to compile .groovy files to java you're going to want to
ensure your groovy-compiler groovyc is operational run this Q&D script
%GROOVY_HOME%\src\bin\startGroovy.bat -classpath -classpath
%GROOVY_HOME%\target\classes;%CLASSPATH%
%GROOVY_HOME%\org.codehaus.groovy.tools.FileSystemCompiler
.\src\main\java\org\codehaus\groovy\util\StringUtil.groovy
and verify StringUtil.class is produced
Have Fun
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Fri, 24 Aug 2012 22:15:19 -0700
> Subject: Re: access password in settings.xml
> From: [email protected]
> To: [email protected]
> CC: [email protected]
>
> On Fri, August 24, 2012 2:36 am, Michael Hüttermann wrote:
> > Hello,
> >
> > how can I (e.g. programmatically, in an own Maven plugin) access the
> > "server">"password" element of settings.xml, to re-use the value. Is there
> > any chance to do so?
>
> Btw. you can also access collections from settings or pom programmatically
> with the gmaven plugin e.g. like this
>
> <plugin>
> <groupId>org.codehaus.gmaven</groupId>
> <artifactId>gmaven-plugin</artifactId>
> <executions>
> <execution>
> <phase>verify</phase>
> <goals>
> <goal>execute</goal>
> </goals>
> <configuration>
> <source>
> println "I am in ${project.name} version ${project.version}
> project.dependencies.each {
> println "Group: $it.groupId; Artifact: $it.artifactId; Version:
> $it.version"
> }
> </source>
> </configuration>
> </plugin>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
