Bug 5774 - [KEPLER] console output should be cleaned when creating a new recipe
Summary: [KEPLER] console output should be cleaned when creating a new recipe
Status: RESOLVED WONTFIX
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Low minor
Target Milestone: Future
Assignee: Jose Lamego
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-01-30 13:24 UTC by Alexandru Georgescu
Modified: 2016-09-15 15:09 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
console output (18.89 KB, text/plain)
2014-01-30 13:24 UTC, Alexandru Georgescu 		no flags Details
prntscrn (239.39 KB, image/png)
2014-01-30 13:25 UTC, Alexandru Georgescu 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Georgescu 2014-01-30 13:24:06 UTC 
Created attachment 1751 [details]
console output

HOST: Fedora20 64bit
eclipse-poky-kepler:c73c6e4510c42601854f3c542ca6e14b4510380c


STEPS TO REPRODUCE:
1. Create a new recipe by specifying a source file as described in TC780 (https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=780)

2. Check the console output in the Eclipse window

RESULTS:

2. The "Yocto Project Console" displays all the steps that happen in the back when parsing and creating the custom recipe. (see printscreen and attached log)
Comment 1 Alexandru Georgescu 2014-01-30 13:25:06 UTC 
Created attachment 1752 [details]
prntscrn
Comment 2 Tim Orling 2016-09-15 15:09:32 UTC 
Kepler is quite old at this point and is no longer supported. Many changes have happened in Eclipse since this bug was filed. Also, this test case is specifically for Bitbake Commander which was deprecated in 2.1, is no longer supported, and is being dropped from the build [YOCTO #100032]. If someone in the community would like to submit patches to fix this, please re-open the bug.