|
|
| Changed: |
<
< |
- NOTE: the plugin assumes that source code and .iml file are kept in or under the same directory as the .ipr and .iws files.
| >
> |
- NOTE: the plugin assumes that source code and .iml file are kept in or under the same directory as the .ipr and .iws files (on Windoze the "Documents and Settings" directory causes problems with Ant because of spaces in the name; so use junction.exe from www.sysinternals.com to create a parallel link like Settings to bypass the problem).
|
|
|
| Added: |
>
> |
Added workspace directory note.
-- PaulBaclace - 20 Nov 2004
|
| Added: |
>
> |
- NOTE: the plugin assumes that source code and .iml file are kept in or under the same directory as the .ipr and .iws files.
|
|
|
| Changed: |
<
< |
-
- Do step 1 for IDEA version 3.x then
- Copy over $IDEA_HOME/plugins/j2mesupport/lib/j2mesupport.jar which was copied into the plugins directory during the ant run, replace it with j2mesupport_041009.zip (or later version, if any).
| >
> |
-
- DO NOT perform step 1 for IDEA 3.0!
- Copy j2mesupport.jar from distribution to $IDEA_HOME/plugins/j2mesupport/lib/j2mesupport.jar.
|
| Changed: |
<
< |
After a successful installation of J2MESupport (for IDEA 3.0 and 3.5 - check $IDEA_HOME/plugins directory for presesnce of j2mesupport.jar. Alterantively for IDEA 4.0 and 4.5 check IDEA_HOME/plugins/lib/j2mesupport).
If plugin's jar is there, you can proceed like that:
| >
> |
After a successful installation of J2MESupport (for IDEA 3.0 and 3.5 - check $IDEA_HOME/plugins directory for presesnce of j2mesupport.jar. Alterantively for IDEA 4.0 and 4.5 check IDEA_HOME/plugins/j2mesupport/lib/j2mesupport).
If plugin's jar is there, you can proceed: |
|
|
| Added: |
>
> |
Updated for IDEA versions 4.0 and 4.5
-- PaulBaclace - 11 Nov 2004
|
| Changed: |
<
< |
Plese see #CurrentFeatures section for detailed description of all features.
| >
> |
Please see #CurrentFeatures section for detailed description of all features.
|
| Changed: |
<
< |
-
- Download the binary j2mesuport_xxxxxx.ZIP file (see below)
- Unzip
j2mesupor_xxxxxx.zip in your %TEMP% directory.
| >
> |
-
- Download the binary j2mesuport_xxxxxx.ZIP file (j2mesupport_030220.zip see below)
- Unzip
j2mesuport_xxxxxx.zip in your %TEMP% directory.
|
| Added: |
>
> |
-
- Do step 1 for IDEA version 3.x then
- Copy over $IDEA_HOME/plugins/j2mesupport/lib/j2mesupport.jar which was copied into the plugins directory during the ant run, replace it with j2mesupport_041009.zip (or later version, if any).
- Copy http://www.intellij.org/twiki/pub/Main/JtoMESupport/FileSize.zip to $IDEA_HOME/lib/ant/lib
|
|
|
| Changed: |
<
< |
-
- make sure ant can be started from command line by typing - ant
* You can download version of this isntallation with prepacked ant
| >
> |
-
- make sure ant can be started from command line by typing - ant. You can download version of this isntallation with prepacked ant
|
| Changed: |
<
< |
After a successful installation of J2MESupport (check IDEA plugin directory for presesnce of j2mesupport.jar for IDEA 3.0 and 3.5.
Alterantivelly for IDEA_HOME/plugins/lib/j2mesupport) for IDEA 4.0 and 4.5, you can proceed like that:
| >
> |
After a successful installation of J2MESupport (for IDEA 3.0 and 3.5 - check $IDEA_HOME/plugins directory for presesnce of j2mesupport.jar. Alterantively for IDEA 4.0 and 4.5 check IDEA_HOME/plugins/lib/j2mesupport).
If plugin's jar is there, you can proceed like that:
|
| Changed: |
<
< |
- click "J2ME project" checkbox to enable J2ME support
| >
> |
- click "J2ME project" checkbox to enable J2ME support for your project
|
| Changed: |
<
< |
-
- run midlet in phone emulator
- debug - dissabled, because when debugged in IDEA, emulator hangs up after jump to breakpoint.
| >
> |
-
- run multiple instances of your midlet suite in phone emulator
- debug midlets - You could experience emulator hanging up in debug mode. As far as I know it is because of WTK jpda implementation (my source of information is a SUN emploee). If anyone knows something more about this issue, I'd be glad to discuss it and find work around.
|
|
|
| Changed: |
<
< |
%META:FILEATTACHMENT{name="j2mesupport_041009.zip" attr="" comment="Version 1.1 for IDEA 4.5 (rename to jar)" date="1097328746" path="j2mesupport_041009.zip" size="517147" user="PavlinZahariev" version="1.1"}%
| >
> |
%META:FILEATTACHMENT{name="j2mesupport_041009.zip" attr="" comment="Ant task for J2MESupport 1.1 (instructions above)" date="1098456021" path="C:\Downloads\j2mesupport_041009.zip" size="507621" user="PavlinZahariev" version="1.2"}% |
|
|
| Changed: |
<
< |
| >
> |
|
| Deleted: |
<
< |
|
| Added: |
>
> |
|
| Added: |
>
> |
This plugin was created with a single idea - to allow for midlets development in IntelliJ IDEA.
|
| Deleted: |
<
< |
This plugin provides IDEA support for J2ME.
|
| Added: |
>
> |
J2MESupport plugin integerates SUN Microsystem's WTK functionality into IDEA. It provides round trip development cycle.
The user can create and manage J2ME aware project; can create, edit, refactor, build, deploy, run and test midlets.
Plese see #CurrentFeatures section for detailed description of all features.
|
| Changed: |
<
< |
Manage your midlet development from within IDEA.
| >
> |
- 1. IDEA versions 3.0 and 3.5
- Download the binary j2mesuport_xxxxxx.ZIP file (see below)
- Unzip
j2mesupor_xxxxxx.zip in your %TEMP% directory.
- cd to created j2mesupport folder
- edit install.properties file
- make sure ant can be started from command line by typing - ant
* You can download version of this isntallation with prepacked ant
* Plese note, that ant integrated with IDEA can not be used for this purpose, because ant.jar need to be changed during installation and obviouslly if it is in use, then it can not be rewritten.
- run install.bat
- See also "Jar Dependencies" section in Plugin Info
- Run Intellij IDEA
- 2. IDEA versions 4.0 and 4.5
- Distributions - J2MESupport is distributed in two forms, depending on the version being published.
- Bugfix versions and minor changes versions will be (whenever possible) distributed as single JAR (or ZIP) file containing the new version of the plugin.
- Major releases come in file named j2mesupport_bin_yymmdd.zip with the following structure.
- /bin:
- any binary and command files needed by this plugin or during instalation procedure
- /conf:
- configuration files needed by this plugin or during instalation procedure
- /doc:
- build.txt - current plugin version and IDEA versions it will run with
- changes.txt - changes between versions
- install.txt - how to install current version of the plugin
- licence.txt - obviously a licence for using this plugin
- readme.txt - general info about this plugin
- todo.txt - mostly short term development plans
- /lib
- j2mesupport.jar
- any other libraries needed by this plugin or during instalation procedure
- /res
- any non-binary files needed by this plugin or during instalation procedure
- Note
- The structure and the contents of the plugiin distributions are subject to change, in which case changes will be described here and in the distribution readme.txt.
|
| Changed: |
<
< |
After a successful installation of J2MESupport (check IDEA plugin directory for presesnce of j2mesupport.jar), you can proceed like that:
| >
> |
After a successful installation of J2MESupport (check IDEA plugin directory for presesnce of j2mesupport.jar for IDEA 3.0 and 3.5.
|
| Changed: |
<
< |
Start IDEA
| >
> |
Alterantivelly for IDEA_HOME/plugins/lib/j2mesupport) for IDEA 4.0 and 4.5, you can proceed like that:
|
| Changed: |
<
< |
- create new empty project - use any target JDK, add midpapi.zip to project classpath
| >
> |
Start IDEA
|
| Changed: |
<
< |
- click checkbox to enable J2ME support
| >
> |
- click "J2ME project" checkbox to enable J2ME support
|
| Changed: |
<
< |
- use J2ME support tool window which appears on the right side (by default) to
Operate your J2ME project:
| >
> |
- use J2ME support tool window which appears on the right side (by default) to operate your J2ME project:
|
| Changed: |
<
< |
| >
> |
|
| Deleted: |
<
< |
|
| Changed: |
<
< |
If you want to share your experience with this plugin or request a feature/bugfix, please see topic JtoMESupportDev
Ofcourse any feedback is pretty welcome 
| >
> |
For reference to on going development and bug fixing , please reffer to JtoMESupportDev
|
| Changed: |
<
< |
- Download the binary j2mesuport_xxxxxx.ZIP file (see below)
- Unzip
j2mesupor_xxxxxx.zip in your %TEMP% directory.
- cd to created j2mesupport folder
- edit install.properties file
- make sure ant can be started from command line by typing - ant
You can download version of this isntallation with prepacked ant
Plese note, that ant integrated with IDEA can not be used for this purpose, because ant.jar need to be changed during installation and obviouslly if it is in use, then it can not be rewritten.
- run install.bat
- See also "Jar Dependencies" section in Plugin Info
- Run IntelliJ
| >
> |
If you want to share your experience with this plugin or request a feature/bugfix, please see topic JtoMeSupportDiscusson
|
| Changed: |
<
< |
| Plugin Version: | 14 Dec 2002 (V1.000) |
| >
> |
| Plugin Version: | 09 Oct 2004 (V1.500) |
|
| Added: |
>
> |
| 09 Oct 2004 (V1.500): | Minor release for IDEA 4.5 Midlet refactoring fixes |
| 18 Mar 2003 (V1.100): | Minor release for IDEA 3.5 |
|
| Changed: |
<
< |
| Jar Dependencies: | J2MESupport uses Sun Microsystems WTK 1.04 phone emulator to test midlets. Current version uses hacked version of kenv.zip. PLease use supplied install.bat script to set up WTK properly. An other hack is made to ant.jar - adding a custom task. Next version will do that in separate jar file |
| >
> |
| Jar Dependencies: | J2MESupport uses Sun Microsystems WTK 1.04 to 2.1.
|
| Changed: |
<
< |
-- PavlinZahariev - 14 Dec 2002
| >
> |
-- PavlinZahariev
|
| Changed: |
<
< |
%META:FILEATTACHMENT{name="j2mesupport_041009.txt" attr="" comment="Version 1.1 for IDEA 4.5" date="1097328670" path="j2mesupport_041009.txt" size="517147" user="PavlinZahariev" version="1.1"}%
| >
> |
%META:FILEATTACHMENT{name="j2mesupport_041009.txt" attr="h" comment="Version 1.1 for IDEA 4.5" date="1097328670" path="j2mesupport_041009.txt" size="517147" user="PavlinZahariev" version="1.1"}% |
|
|
| Added: |
>
> |
Currently I'm working on this page. Please come back later or take the risk ro read inconsistent information or download wrong files!
Pavlin
|
| Changed: |
<
< |
%META:FILEATTACHMENT{name="j2mesupport_021214.zip" attr="" comment="" date="1039872721" path="C:\temp\j2mesupport_021214.zip" size="1661000" user="PavlinZahariev" version="1.1"}%
| >
> |
%META:FILEATTACHMENT{name="j2mesupport_021214.zip" attr="h" comment="" date="1039872721" path="C:\temp\j2mesupport_021214.zip" size="1661000" user="PavlinZahariev" version="1.1"}% |
|
|
| Added: |
>
> |
If you want to share your experience with this plugin or request a feature/bugfix, please see topic JtoMESupportDev
|
| Changed: |
<
< |
Please see topic JtoMESupportDev, any feedback is pretty welcome
| >
> |
Ofcourse any feedback is pretty welcome
|
| Deleted: |
<
< |
Installation Experiences (by UweGeuder - 07 Feb 2003)
In the install.properties file I did not really understand how install.path should be set. I used "." (dot) and it think it worked.
I did not succeed to use the prepacked ant. Firstly, it doesn't seem to contain anything that can be run from the command line. After adding my own wrapper I got an error about missing SAX classes. A completely separate Ant download and installation did it without further (obvious) problems.
After the installation the plugin looks nice and functional. However I haven't been able to use it because of the JDK problem described in JavaTwoMicroEdition.
Hi, install.path is the path to folder, where installation archive was unpacked. Its probably redundand and you are right that "." should work. I'll change this in next release.
Prepacked ANT is actually not an ANT installation. Please see my note above about ant setup. Directory /${install.path}/ant contains a task for calculating file size (handy aftet jar generation) and an optional component for FTP task, which I use to deploy to remote servers.
Please see my note about target JDK in JavaTwoMicroEdition.
Cerainly there are plenty of bugs in the plugin itself. Some were already fixed and others are still waiting to be discovered :).
I'm sorry to react, that late on this note. I was watching plugin forum for reactions. Please post your notes primarily there.
-- PavlinZahariev - 20 Feb 2003
This is great work! I had some trouble, though, getting the run targets in the autogenerated ant build.xml file to work. In particular, I had to add a line to the run target for the midlet name and also change 'deploy' to the 'deploy.local.path' property. These changes were required:
<target name="runner" depends="checkdist">
<exec executable="${toolkit.home.dir}/bin/emulator">
<arg line="-Xdevice:${device.type}"/>
<arg line="-Xverbose:class,classverbose"/>
<arg line="-Xdescriptor:${project.dir}>${deploy.local.path}/${project.name}.jad"/>
<arg line="${midlet0.name}"/>
</exec>
</target>
Also, it would be nice to have separate targets for each of the useable device types. I added the following to obtain this:
<target name="run-defaultGray">
<antcall target="runner">
<param name="device.type" value="DefaultGrayPhone"/>
</antcall>
</target>
<target name="run-defaultColor">
<antcall target="runner">
<param name="device.type" value="DefaultColorPhone"/>
</antcall>
</target>
<target name="run-motorola_i85s">
<antcall target="runner">
<param name="device.type" value="Motorola_i85s"/>
</antcall>
</target>
<target name="run-blackberry">
<antcall target="runner">
<param name="device.type" value="RIMJavaHandheld"/>
</antcall>
</target>
<target name="run-palm">
<antcall target="runner">
<param name="device.type" value="PalmOS_Device"/>
</antcall>
</target>
<target name="runner" depends="checkdist">
<exec executable="${toolkit.home.dir}/bin/emulator">
<arg line="-Xdevice:${device.type}"/>
<arg line="-Xverbose:class,classverbose"/>
<arg line="-Xdescriptor:${project.dir}/${deploy.local.path}/${project.name}.jad"/>
<arg line="${midlet0.name}"/>
</exec>
</target>
-- Lee Crawford?
Lee, thank you for your opinion!
I think, that putting all these targets (and any other new phone emulator option) into ant script could be very usefull if want to automate the process of running emulators. In current version of the plugin, you can simply use the combo next to "Run" toolbar button to select different phone, then press "Run" or "Debug".
I fixed some bugs in last version. The new build is posted bellow.
Also I gonna release the sources, which by far are not as good as I'd wish too, but I think there is a usefull framework how to manip with options which can be stored in project.iws and also edited in dialog.
Please, let's discuss this plugin in forums, otherwise this page becomes huge and messy.
-- PavlinZahariev - 18 Mar 2003
|
| Added: |
>
> |
%META:FILEATTACHMENT{name="j2mesupport_041009.txt" attr="" comment="Version 1.1 for IDEA 4.5" date="1097328670" path="j2mesupport_041009.txt" size="517147" user="PavlinZahariev" version="1.1"}%
%META:FILEATTACHMENT{name="j2mesupport_041009.zip" attr="" comment="Version 1.1 for IDEA 4.5 (rename to jar)" date="1097328746" path="j2mesupport_041009.zip" size="517147" user="PavlinZahariev" version="1.1"}%
%META:FILEATTACHMENT{name="FileSize.zip" attr="" comment="Ant task for J2MESupport 1.1 (instructions above)" date="1097329205" path="FileSize.zip" size="1709" user="PavlinZahariev" version="1.1"}% |
|
|
| Changed: |
<
< |
%META:FIELD{name="IntelliJPluginName" title="IntelliJPluginName" value=""}%
%META:FIELD{name="IntelliJPluginVersion" title="IntelliJPluginVersion" value=""}%
%META:FIELD{name="IntelliJPluginVendor" title="IntelliJPluginVendor" value=""}%
%META:FIELD{name="IntelliJPluginBinary" title="IntelliJPluginBinary" value=""}%
| >
> |
%META:FIELD{name="IntelliJPluginName" title="IntelliJPluginName" value="J2MESupport"}%
%META:FIELD{name="IntelliJPluginVersion" title="IntelliJPluginVersion" value="1.10"}%
%META:FIELD{name="IntelliJPluginVendor" title="IntelliJPluginVendor" value="Applego"}%
%META:FIELD{name="IntelliJPluginBinary" title="IntelliJPluginBinary" value="http://prz.wz.cz/j2me/j2mesupport.jar"}%
|
| Changed: |
<
< |
%META:FIELD{name="IntelliJPluginClassification" title="IntelliJPluginClassification" value=""}%
| >
> |
%META:FIELD{name="IntelliJPluginClassification" title="IntelliJPluginClassification" value="IntegrationPlugin, Other"}%
|
| Changed: |
<
< |
%META:FIELD{name="ShouldRunOnOS" title="ShouldRunOnOS" value=""}%
| >
> |
%META:FIELD{name="ShouldRunOnOS" title="ShouldRunOnOS" value="OsWin2K, OsWinXP"}%
|
| Changed: |
<
< |
%META:FILEATTACHMENT{name="j2mesupport_030318__src.zip" attr="" comment="Source code and IDEA project for this plugin" date="1048037858" path="C:\pinwork\backup\j2mesupport_030318__src.zip" size="136655" user="PavlinZahariev" version="1.1"}%
| >
> |
%META:FILEATTACHMENT{name="j2mesupport_030318__src.zip" attr="" comment="Source code for v1.0 - Ariadna version" date="1048037858" path="C:\pinwork\backup\j2mesupport_030318__src.zip" size="136655" user="PavlinZahariev" version="1.1"}% |
|
|
| Changed: |
<
< |
%META:FORM{name="WebForm"}%
| >
> |
%META:FORM{name="IntelliJPluginWebForm"}%
%META:FIELD{name="IntelliJPluginName" title="IntelliJPluginName" value=""}%
%META:FIELD{name="IntelliJPluginVersion" title="IntelliJPluginVersion" value=""}%
%META:FIELD{name="IntelliJPluginVendor" title="IntelliJPluginVendor" value=""}%
%META:FIELD{name="IntelliJPluginBinary" title="IntelliJPluginBinary" value=""}%
%META:FIELD{name="IntelliJPluginSource" title="IntelliJPluginSource" value=""}%
%META:FIELD{name="IntelliJPluginClassification" title="IntelliJPluginClassification" value=""}% |
|
|
| Changed: |
<
< |
Please see topic JtoMESupportDev, any feedback are welcome
| >
> |
Please see topic JtoMESupportDev, any feedback is pretty welcome
|
| Added: |
>
> |
|
| Added: |
>
> |
|
| Deleted: |
<
< |
%META:FILEATTACHMENT{name="j2mesupport_030220.zip" attr="" comment="" date="1045706618" path="G:\pinwork\projects\plugin\plugin\j2mesupport\install\j2mesupport_030220.zip" size="411774" user="PavlinZahariev" version="1.1"}%
|
| Added: |
>
> |
%META:FILEATTACHMENT{name="j2mesupport_030318.zip" attr="" comment="Version 1.0 build 007 (ant not included)" date="1048037540" path="C:\pinwork\backup\j2mesupport_030318.zip" size="441894" user="PavlinZahariev" version="1.1"}%
%META:FILEATTACHMENT{name="j2mesupport_030318__src.zip" attr="" comment="Source code and IDEA project for this plugin" date="1048037858" path="C:\pinwork\backup\j2mesupport_030318__src.zip" size="136655" user="PavlinZahariev" version="1.1"}% |
|
|
| Added: |
>
> |
Lee, thank you for your opinion!
I think, that putting all these targets (and any other new phone emulator option) into ant script could be very usefull if want to automate the process of running emulators. In current version of the plugin, you can simply use the combo next to "Run" toolbar button to select different phone, then press "Run" or "Debug".
I fixed some bugs in last version. The new build is posted bellow.
Also I gonna release the sources, which by far are not as good as I'd wish too, but I think there is a usefull framework how to manip with options which can be stored in project.iws and also edited in dialog.
Please, let's discuss this plugin in forums, otherwise this page becomes huge and messy.
-- PavlinZahariev - 18 Mar 2003 |
|
|
| Added: |
>
> |
This is great work! I had some trouble, though, getting the run targets in the autogenerated ant build.xml file to work. In particular, I had to add a line to the run target for the midlet name and also change 'deploy' to the 'deploy.local.path' property. These changes were required:
<target name="runner" depends="checkdist">
<exec executable="${toolkit.home.dir}/bin/emulator">
<arg line="-Xdevice:${device.type}"/>
<arg line="-Xverbose:class,classverbose"/>
<arg line="-Xdescriptor:${project.dir}>${deploy.local.path}/${project.name}.jad"/>
<arg line="${midlet0.name}"/>
</exec>
</target>
Also, it would be nice to have separate targets for each of the useable device types. I added the following to obtain this:
<target name="run-defaultGray">
<antcall target="runner">
<param name="device.type" value="DefaultGrayPhone"/>
</antcall>
</target>
<target name="run-defaultColor">
<antcall target="runner">
<param name="device.type" value="DefaultColorPhone"/>
</antcall>
</target>
<target name="run-motorola_i85s">
<antcall target="runner">
<param name="device.type" value="Motorola_i85s"/>
</antcall>
</target>
<target name="run-blackberry">
<antcall target="runner">
<param name="device.type" value="RIMJavaHandheld"/>
</antcall>
</target>
<target name="run-palm">
<antcall target="runner">
<param name="device.type" value="PalmOS_Device"/>
</antcall>
</target>
<target name="runner" depends="checkdist">
<exec executable="${toolkit.home.dir}/bin/emulator">
<arg line="-Xdevice:${device.type}"/>
<arg line="-Xverbose:class,classverbose"/>
<arg line="-Xdescriptor:${project.dir}/${deploy.local.path}/${project.name}.jad"/>
<arg line="${midlet0.name}"/>
</exec>
</target>
-- Lee Crawford?
|
|
|
| Added: |
>
> |
|
| Added: |
>
> |
%META:FILEATTACHMENT{name="j2mesupport_030309.zip" attr="" comment="Version 1.0" date="1047254201" path="G:\pinwork\projects\plugin\j2mesupport\deploy\j2mesupport_030309.zip" size="439480" user="PavlinZahariev" version="1.1"}% |
|
|
| Changed: |
<
< |
Use wizard to set up midlet project. Set midlet options from dialog window. Build/Run/Debug midlets directly from IDEA. Deploy locally or via FTP. Test in Sun Microsystems WTK phone emulator. Run emulator in debug mode and attach IDEA debugger using remote method.
| >
> |
After a successful installation of J2MESupport (check IDEA plugin directory for presesnce of j2mesupport.jar), you can proceed like that:
Start IDEA
- create new empty project - use any target JDK, add midpapi.zip to project classpath
- open project properties and find J2MESupport properties tab.
- click checkbox to enable J2ME support
- wizard dialog will start and guide you through j2me project setup.
- use J2ME support tool window which appears on the right side (by default) to
Operate your J2ME project:
- edit options
- build project
- deploy midlet
- run midlet in phone emulator
- debug - dissabled, because when debugged in IDEA, emulator hangs up after jump to breakpoint.
|
| Added: |
>
> |
Hi, install.path is the path to folder, where installation archive was unpacked. Its probably redundand and you are right that "." should work. I'll change this in next release.
Prepacked ANT is actually not an ANT installation. Please see my note above about ant setup. Directory /${install.path}/ant contains a task for calculating file size (handy aftet jar generation) and an optional component for FTP task, which I use to deploy to remote servers.
Please see my note about target JDK in JavaTwoMicroEdition.
Cerainly there are plenty of bugs in the plugin itself. Some were already fixed and others are still waiting to be discovered :).
I'm sorry to react, that late on this note. I was watching plugin forum for reactions. Please post your notes primarily there.
-- PavlinZahariev - 20 Feb 2003
|
| Added: |
>
> |
%META:FILEATTACHMENT{name="j2mesupport_030220.zip" attr="" comment="" date="1045706618" path="G:\pinwork\projects\plugin\plugin\j2mesupport\install\j2mesupport_030220.zip" size="411774" user="PavlinZahariev" version="1.1"}%
%META:FILEATTACHMENT{name="j2mesupport_ant_030220.zip" attr="" comment="includes ant (FileSize? task and net.jar component)" date="1045707895" path="G:\pinwork\projects\plugin\plugin\j2mesupport\j2mesupport_ant_030220.zip" size="1669196" user="PavlinZahariev" version="1.1"}% |
|
|
| Added: |
>
> |
Installation Experiences (by UweGeuder - 07 Feb 2003)
In the install.properties file I did not really understand how install.path should be set. I used "." (dot) and it think it worked.
I did not succeed to use the prepacked ant. Firstly, it doesn't seem to contain anything that can be run from the command line. After adding my own wrapper I got an error about missing SAX classes. A completely separate Ant download and installation did it without further (obvious) problems.
After the installation the plugin looks nice and functional. However I haven't been able to use it because of the JDK problem described in JavaTwoMicroEdition. |
|
|
| Added: |
>
> |
|
| Changed: |
<
< |
%META:FIELD{name="TopicShortDescription" title="TopicShortDescription" value="JavaTwoMicroEdition support"}%
%META:FIELD{name="TestedOnOS" title="TestedOnOS" value=""}%
%META:FIELD{name="ShouldRunOnOS" title="ShouldRunOnOS" value="AnyWin"}%
| >
> |
%META:FIELD{name="TopicShortDescription" title="TopicShortDescription" value="IDEA support for JavaTwoMicroEdition (J2ME) "}%
%META:FIELD{name="TestedOnOS" title="TestedOnOS" value="OsWin2K"}%
%META:FIELD{name="ShouldRunOnOS" title="ShouldRunOnOS" value=""}%
%META:FILEATTACHMENT{name="j2mesupport_021214.zip" attr="" comment="" date="1039872721" path="C:\temp\j2mesupport_021214.zip" size="1661000" user="PavlinZahariev" version="1.1"}% |
|
|
| Added: |
>
> |
%META:TOPICINFO{author="PavlinZahariev" date="1039866621" format="1.0" version="1.1"}%
This plugin provides IDEA support for J2ME.
Manage your midlet development from within IDEA.
Use wizard to set up midlet project. Set midlet options from dialog window. Build/Run/Debug midlets directly from IDEA. Deploy locally or via FTP. Test in Sun Microsystems WTK phone emulator. Run emulator in debug mode and attach IDEA debugger using remote method.
Here put detailed information about features of your plugin
Please see topic JtoMESupportDev, any feedback are welcome
- Download the binary j2mesuport_xxxxxx.ZIP file (see below)
- Unzip
j2mesupor_xxxxxx.zip in your %TEMP% directory.
- cd to created j2mesupport folder
- edit install.properties file
- make sure ant can be started from command line by typing - ant
You can download version of this isntallation with prepacked ant
Plese note, that ant integrated with IDEA can not be used for this purpose, because ant.jar need to be changed during installation and obviouslly if it is in use, then it can not be rewritten.
- run install.bat
- See also "Jar Dependencies" section in Plugin Info
- Run IntelliJ
Related Topics: PluginDocumentation, ProjectPluginTemplate, OpenAPI, IntellijPluginDocumentation,
IntellijPluginDocumentation, PluginDeployment, IdeasForPlugins
-- PavlinZahariev - 14 Dec 2002
%META:FORM{name="WebForm"}%
%META:FIELD{name="TopicClassification" title="TopicClassification" value="IntelliJPluginPackage"}%
%META:FIELD{name="TopicShortDescription" title="TopicShortDescription" value="JavaTwoMicroEdition support"}%
%META:FIELD{name="TestedOnOS" title="TestedOnOS" value=""}%
%META:FIELD{name="ShouldRunOnOS" title="ShouldRunOnOS" value="AnyWin"}% |
View
| Diffs | r1.19 | > | r1.18 | > | r1.17
| More
|
|