Eclipse integration/Known issues beta2 - Revision history

imported_>amigadave: wikify slightly

2010-05-12T08:16:23Z

wikify slightly

← Older revision		Revision as of 08:16, 12 May 2010
Line 6:		Line 6:
	== Product baselines ==		== Product baselines ==

	* Fremantle SDK is supported as separate installation e.g. not delivered as default environment with Desktop image, for example.		* [[Open development/Maemo roadmap/Fremantle\|Fremantle]] SDK is supported as separate installation e.g. not delivered as default environment with Desktop image, for example.
	* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle extras-devel repository		* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle [[extras-devel]] repository
	* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html		* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html
	Notice that updating process from Eclipse Update Site (update from beta 1 to beta 2) may not work for some plug-ins		Notice that updating process from Eclipse Update Site (update from beta 1 to beta 2) may not work for some plug-ins
Line 20:		Line 20:

	* While debugging Python application automatic termination of debugged program does not work when debugging session ends		* While debugging Python application automatic termination of debugged program does not work when debugging session ends
	* Automatic installation of OProfiling support to the Maemo device may cause Eclipse to crash if Eclipse cannot find OProfile packages from configured repositories. Add repository		* Automatic installation of OProfiling support to the Maemo device may cause Eclipse to crash if Eclipse cannot find OProfile packages from configured repositories. Add repository <pre>deb http://repository.maemo.org/ diablo/tools free</pre> to the Maemo device and run "sudo apt-get update" manually as workaround.
	deb http://repository.maemo.org/ diablo/tools free
	to the Maemo device and run "sudo apt-get update" manually as workaround.

	== Maemo ESBox plugin for Eclipse ==		== Maemo ESBox plugin for Eclipse ==
Line 30:		Line 28:
	== Maemo Pluthon plugin for Eclipse ==		== Maemo Pluthon plugin for Eclipse ==

	* <none>		* none

	== Maemo PC Connectivity ==		== Maemo PC Connectivity ==
Line 40:		Line 38:
	== Maemo SDK Virtual Image ==		== Maemo SDK Virtual Image ==

	* NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems		* NetworkManager is being started after Scratchbox, so the <code>resolv.conf</code> file used by Scratchbox may be invalid which causes network problems

	== Maemo Flasher-3.5 Tool ==		== Maemo Flasher-3.5 Tool ==
Line 49:		Line 47:

	* Some publically available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published		* Some publically available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published

	* Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products		* Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products

imported_>dneary: Eclipse integration/KnownIssues beta2 moved to Eclipse integration/Known issues beta2

2010-04-26T09:15:48Z

Eclipse integration/KnownIssues beta2 moved to Eclipse integration/Known issues beta2

← Older revision	Revision as of 09:15, 26 April 2010
(No difference)

imported_>guaka: Category:Eclipse

2009-10-26T09:43:01Z

Category:Eclipse

← Older revision		Revision as of 09:43, 26 October 2009
Line 54:		Line 54:
	----		----
	Feedback can be sent to eclipse-integration@maemo.org		Feedback can be sent to eclipse-integration@maemo.org

			[[Category:Eclipse]]

imported_>jatikka: /* Product baselines */

2009-07-03T13:11:40Z

Product baselines

← Older revision		Revision as of 13:11, 3 July 2009
Line 9:		Line 9:
	* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle extras-devel repository		* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle extras-devel repository
	* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html		* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html
			Notice that updating process from Eclipse Update Site (update from beta 1 to beta 2) may not work for some plug-ins

	== Product configuration ==		== Product configuration ==

imported_>jatikka: /* Maemo Mica plugin framework for Eclipse */

2009-07-03T13:00:26Z

Maemo Mica plugin framework for Eclipse

← Older revision		Revision as of 13:00, 3 July 2009
Line 22:		Line 22:
	deb http://repository.maemo.org/ diablo/tools free		deb http://repository.maemo.org/ diablo/tools free
	to the Maemo device and run "sudo apt-get update" manually as workaround.		to the Maemo device and run "sudo apt-get update" manually as workaround.
	* Scanning all project source packages to gather indexer information for project sometimes fails to index all source files on Windows host PC
	* Automatic project import from Debian repository sometimes sets erroneously also source repository for binary only Debian repository causing following error "Failed to find source package. Probably this package has no source."

	== Maemo ESBox plugin for Eclipse ==		== Maemo ESBox plugin for Eclipse ==

imported_>jatikka: /* Product baselines */

2009-07-03T08:29:50Z

Product baselines

← Older revision		Revision as of 08:29, 3 July 2009
Line 8:		Line 8:
	* Fremantle SDK is supported as separate installation e.g. not delivered as default environment with Desktop image, for example.		* Fremantle SDK is supported as separate installation e.g. not delivered as default environment with Desktop image, for example.
	* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle extras-devel repository		* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle extras-devel repository
	* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/~~beta1~~/update_maemo_vm.html		* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html

	== Product configuration ==		== Product configuration ==

imported_>jatikka: /* Known Issues for Maemo Eclipse Integration Edition 2 Beta 1 release */

2009-07-03T08:20:39Z

Known Issues for Maemo Eclipse Integration Edition 2 Beta 1 release

← Older revision		Revision as of 08:20, 3 July 2009
Line 42:		Line 42:

	* NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems		* NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems

			== Maemo Flasher-3.5 Tool ==

			* Flasher-3.5 beta tool may have problems in some Windows host PC configurations to flash eMMC images properly. Workaround is to retry with another USB port in host PC or use Linux/Mac for eMMC flashing

	== Integration testing ==		== Integration testing ==

imported_>jatikka: /* Maemo Mica plugin framework for Eclipse */

2009-07-03T08:04:13Z

Maemo Mica plugin framework for Eclipse

← Older revision		Revision as of 08:04, 3 July 2009
Line 22:		Line 22:
	deb http://repository.maemo.org/ diablo/tools free		deb http://repository.maemo.org/ diablo/tools free
	to the Maemo device and run "sudo apt-get update" manually as workaround.		to the Maemo device and run "sudo apt-get update" manually as workaround.
	* Scanning all project source packages to gather indexer information for project sometimes fails on Windows host PC		* Scanning all project source packages to gather indexer information for project sometimes fails to index all source files on Windows host PC
	* Automatic project import from Debian repository sometimes sets erroneously also source repository for binary only Debian repository causing following error "Failed to find source package. Probably this package has no source."		* Automatic project import from Debian repository sometimes sets erroneously also source repository for binary only Debian repository causing following error "Failed to find source package. Probably this package has no source."

imported_>jatikka: /* Maemo Mica plugin framework for Eclipse */

2009-07-03T08:01:25Z

Maemo Mica plugin framework for Eclipse

← Older revision		Revision as of 08:01, 3 July 2009
Line 23:		Line 23:
	to the Maemo device and run "sudo apt-get update" manually as workaround.		to the Maemo device and run "sudo apt-get update" manually as workaround.
	* Scanning all project source packages to gather indexer information for project sometimes fails on Windows host PC		* Scanning all project source packages to gather indexer information for project sometimes fails on Windows host PC
	* Automatic import from Debian repository sometimes sets erroneously also ~~src~~ repository for binary only Debian repository causing following error "Failed to find source package. Probably this package has no source."		* Automatic project import from Debian repository sometimes sets erroneously also source repository for binary only Debian repository causing following error "Failed to find source package. Probably this package has no source."

	== Maemo ESBox plugin for Eclipse ==		== Maemo ESBox plugin for Eclipse ==

imported_>jatikka: /* Maemo PC Connectivity */

2009-07-03T07:59:04Z

Maemo PC Connectivity

← Older revision		Revision as of 07:59, 3 July 2009
Line 37:		Line 37:
	* Mac OS X support is still initial for Beta 2 release on functionality and quality point of view. Especially testing on Mac environment has been somewhat limited.		* Mac OS X support is still initial for Beta 2 release on functionality and quality point of view. Especially testing on Mac environment has been somewhat limited.
	* Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems		* Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems
			* When creating a project and setting sbrsh as download method quite often errors like "sbrsh server: fuse: bad mount point " and "sbrsh server: Can't mount to point:" happens. As a workaround you need to restart sbrshd (on Maemo device side) and restart Esbox (on host PC side)

	== Maemo SDK Virtual Image ==		== Maemo SDK Virtual Image ==