Hi Damien,

thx for this hint. i already tried ${settings.localRepository} but since i
use the default (and no ${settings.localRepository} is specified in my
settings.xml) maven can't resolve the property.


and the second reason why i didn't investigate more time to get rid of the
${env.WTK_HOME} variable, is that one needs to specify the WTK_HOME for the
j2me-maven-plugin anyway.

        <plugin>
                <groupId>com.pyx4me</groupId>
                <artifactId>j2me-maven-plugin</artifactId>
                <version>2.0.1</version>
                <executions>
                        <execution>
                                <goals>
                                        <goal>package</goal>
                                </goals>
                        </execution>
                </executions>
                <configuration>
                                <j2meConfiguration>CLDC-1.1</j2meConfiguration>
                                <j2meProfile>MIDP-2.0</j2meProfile>
                                <useWtkLibs>true</useWtkLibs>
                                <wtkHome>${env.WTK_HOME}</wtkHome>              
            <!--
environment variable needed here -->
                                <proguardInclude>proguard.conf</proguardInclude>
                                <proguard>true</proguard>
                                <obfuscate>true</obfuscate>
                                <jadAttributes>
                                                ...
                                </jadAttributes>
                                <midlets>
                                                <MIDlet>
                                                                ...
                                                </MIDlet>
                                </midlets>
                </configuration>
        </plugin>

is it possible to pass some libs, instead of the WTK_HOME?

AFAIK the plugin also needs an executable for the preverification.

regards
R.C.


Damien Lecan-2 wrote:
> 
>>
>>                 <compilerArguments>
>>
>> <bootclasspath>${env.WTK_HOME}/lib/cldcapi11.jar;${env.WTK_HOME
>> }/lib/midpapi20.jar</bootclasspath>
>>                 </compilerArguments>
>>
> 
> Glad to see that working.
> 
> At least, if you have an internal maven repository, you might have a more
> portable build system.
> You could deploy cldcapi11.jar and midpapi20.jar into your internal
> repository, and then use combination of
> ${settings.localRepository}/path/to/dependency
> and dependency declaration.
> 
> This is how we do where I'm working. Nothing more than Maven has be
> installed to develop J2ME applications (no more wtk installation)
> 
> 
> Damien
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-M2--j2me-maven-plugin%3A-preverification-error-tf3975257s177.html#a11339623
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to