arittner
2012-09-12 12:34:11 UTC
Hi!
I've switched to NetBeans 7.2 IDE and I build (with maven) RELEASE71 platform projects.
I've currently a start up error with a NetBeans Platform Maven project. It's looks like this error: http://forums.netbeans.org/topic20022.html but only with my 64Bit starter. The 32Bit starter works for me.
But the nbm:run-platform runs only the 64Bit version.
The execution line is:
cmd.exe /X /C "C:\entw\Work\svn\4.2\apps\s3standard\target\s3\bin\s364.exe --console suppress --userdir C:\entw\Work\svn\4.2\apps\s3standard\target\userdir -J-Dnetbeans.logger.console=true -J-ea --branding s3 --jdkhome C:\entw\JDK\1.7.0_04"
I get the error message: Cannot find valid 'platform*' folder!
If I start the s364.exe from the explorer I get the same error.
If I start the s3.exe with the explorer, the application starts up. No problems.
A piece of my pom.xml:
Code:
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>nbm-maven-plugin</artifactId>
<configuration>
<brandingToken>${brandingToken}</brandingToken>
<distributionUrl>http://www.sepix.de/updates/4.2/</distributionUrl>
<etcConfFile>config/s3.conf</etcConfFile>
<installerOsLinux>false</installerOsLinux>
<installerOsMacosx>false</installerOsMacosx>
<installerOsSolaris>false</installerOsSolaris>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>deployment</id>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>nbm-maven-plugin</artifactId>
<executions>
<execution>
<id>updatesite</id>
<phase>package</phase>
<goals>
<goal>autoupdate</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<properties>
<netbeans.run.params.ide/>
<netbeans.run.params>${netbeans.run.params.ide}</netbeans.run.params>
</properties>
My s3.conf:
Code:
# ${HOME} will be replaced by user home directory according to platform
default_userdir="${HOME}/.${APPNAME}/dev"
default_mac_userdir="${HOME}/Library/Application Support/${APPNAME}/dev"
# options used by the launcher by default, can be overridden by explicit
# command line switches
default_options="--branding s3 -J-Xms24m -J-Xmx512m -J-Dsun.awt.disableMixing=true"
# for development purposes you may wish to append: -J-Dnetbeans.logger.console=true -J-ea
# default location of JDK/JRE, can be overridden by using --jdkhome <dir> switch
#jdkhome="/path/to/jdk"
# clusters' paths separated by path.separator (semicolon on Windows, colon on Unices)
#extra_clusters=
How can I change (for a workaround) to the 32Bit starter "s3.exe"? What is the problem with the 64Bit starter?
best regards,
josh.
I've switched to NetBeans 7.2 IDE and I build (with maven) RELEASE71 platform projects.
I've currently a start up error with a NetBeans Platform Maven project. It's looks like this error: http://forums.netbeans.org/topic20022.html but only with my 64Bit starter. The 32Bit starter works for me.
But the nbm:run-platform runs only the 64Bit version.
The execution line is:
cmd.exe /X /C "C:\entw\Work\svn\4.2\apps\s3standard\target\s3\bin\s364.exe --console suppress --userdir C:\entw\Work\svn\4.2\apps\s3standard\target\userdir -J-Dnetbeans.logger.console=true -J-ea --branding s3 --jdkhome C:\entw\JDK\1.7.0_04"
I get the error message: Cannot find valid 'platform*' folder!
If I start the s364.exe from the explorer I get the same error.
If I start the s3.exe with the explorer, the application starts up. No problems.
A piece of my pom.xml:
Code:
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>nbm-maven-plugin</artifactId>
<configuration>
<brandingToken>${brandingToken}</brandingToken>
<distributionUrl>http://www.sepix.de/updates/4.2/</distributionUrl>
<etcConfFile>config/s3.conf</etcConfFile>
<installerOsLinux>false</installerOsLinux>
<installerOsMacosx>false</installerOsMacosx>
<installerOsSolaris>false</installerOsSolaris>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>deployment</id>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>nbm-maven-plugin</artifactId>
<executions>
<execution>
<id>updatesite</id>
<phase>package</phase>
<goals>
<goal>autoupdate</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<properties>
<netbeans.run.params.ide/>
<netbeans.run.params>${netbeans.run.params.ide}</netbeans.run.params>
</properties>
My s3.conf:
Code:
# ${HOME} will be replaced by user home directory according to platform
default_userdir="${HOME}/.${APPNAME}/dev"
default_mac_userdir="${HOME}/Library/Application Support/${APPNAME}/dev"
# options used by the launcher by default, can be overridden by explicit
# command line switches
default_options="--branding s3 -J-Xms24m -J-Xmx512m -J-Dsun.awt.disableMixing=true"
# for development purposes you may wish to append: -J-Dnetbeans.logger.console=true -J-ea
# default location of JDK/JRE, can be overridden by using --jdkhome <dir> switch
#jdkhome="/path/to/jdk"
# clusters' paths separated by path.separator (semicolon on Windows, colon on Unices)
#extra_clusters=
How can I change (for a workaround) to the 32Bit starter "s3.exe"? What is the problem with the 64Bit starter?
best regards,
josh.