Hi all,
We have been convinced that contributing under a foreign project's namespace is
not a good idea; on the other hand, the deprecated legacy
org.eclipse.tm.terminal.view feature has already been removed from the simrel,
so if there's any existing adopter of that one he will be broken in M6 since we
cannot proceed with the move before the move review is complete.
Find attached what I have proposed to the EPP packages (pull in the existing
org.eclipse.tcf.te.terminals.feature for M6 such that we get wide exposure and
feedback).
https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
Please discuss any comments, concerns or questions on the Move Review bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=462230
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: [email protected]
[mailto:[email protected]] On Behalf Of Oberhuber,
Martin
Sent: Monday, March 16, 2015 6:42 PM
To: Cross project issues ([email protected])
Subject: [cross-project-issues-dev] Heads Up: TCF Terminals Moving to TM
Hi all,
You might be aware that based on the original TM Terminal view, the TCF Project
has come up with a much enhanced terminal:
https://marketplace.eclipse.org/content/tcf-terminals
In order to simplify code adoption and contributions, we want to restructure
the codebase and re-unite it with the original TM codebase.
The result will be called "TM Terminal 4.0" but will contain the related TM
_and_ TCF code in a single, small git repository.
Here is the respective restructuring review:
https://projects.eclipse.org/projects/tools.cdt.tcf/reviews/move-tcf-terminals-code-tm-project
Now unfortunately the review is scheduled to complete by April 1 which is after
M6, but we would like to give adopters
a preview of the new Terminal with M6 in order to get more feedback. Thus
here's what we are planning:
- The TM project will no longer contribute its
org.eclipse.tm.terminal.* to the simrel
- Instead, the TCF project will contribute
org.eclpse.tm.terminal.*_4.0 to the simrel (already using the *new* namespace).
If you do not take any action, you will simply see the new "4.0" version of
those features from TCF, giving you the new tabbed terminal view.
Downstream consumers would only be affected if they consume
org.eclipse.tm.terminal.(ssh|telnet|view) directly from the TM repo rather than
simrel repo.
As far as I can tell, this shouldn't affect anyone, but wanted to make sure
everyone is aware.
The original Terminal widget (org.eclipse.tm.terminal) is not affected by the
restructuring, only the view and the connectors.
For now this is just a heads up; more details are on the epp-dev mailinglist,
https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03447.html
We are planning to add the new "TM Namespace" features to the TCF simrel
contribution over the course of the week.
I will send another notification once the new features are available.
Please let us know here on the list of any concerns or questions !
Or comment directly on the Move Review if you want.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
--- Begin Message ---
Hi Package Maintainers,
We have been convinced that contributing from TCF under a foreign namespace is
not a good idea.
On the other hand, the deprecated legacy terminal view has already been removed
from the simrel:
http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=d677d5a6ae094bb2d1a7136be9d5b1d84c62740d
This means there is now some action strongly suggested, or packages might fail
to build or build against outdated (M5) terminal contributions:
- jee : Remove legacy terminal.view , optionally add the new
tcf.terminals.view - Bug
462087<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462087>
- reporting : Remove legacy terminal.view , optionally add the new
tcf.terminals.view - Bug
462089<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462089>
- parallel : Optionally add org.eclipse.tcf.te.terminals.feature AND
org.eclipse.tcf.te.terminals.rse.feature
- cpp : Optionally add org.eclipse.tcf.te.terminals.feature AND
org.eclipse.tcf.te.terminals.rse.feature
For the must-have changes in jee and reporting, we have created bugs and Gerrit
changesets.
Since I am an epp committer, I think I could apply these for you, but I would
like the package maintainer’s OK before I do that.
I would strongly recommend also applying the optional changes (adding the TCF
Terminals View) such that users can see the new view and provide feedback.
Without doing this, the Terminal view would be GONE in the respective packages
in M6 and only reappear in M7 once the move has been completed.
I can also apply these changes for you if I get your OK.
Please let me know how you want to proceed, and if there’s any
questions/concerns !
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: [email protected] [mailto:[email protected]] On
Behalf Of Oberhuber, Martin
Sent: Monday, March 16, 2015 6:17 PM
To: EPP Developer Mailing List ([email protected])
Subject: [epp-dev] Heads Up and some action requested : TCF Terminals Moving to
TM
Hi Package Maintainers,
You might be aware that based on the original TM Terminal view, the TCF Project
has come up with a much enhanced terminal:
https://marketplace.eclipse.org/content/tcf-terminals
In order to simplify code adoption and contributions, we want to restructure
the codebase and re-unite it with the original TM codebase.
The result will be called “TM Terminal 4.0” but will contain the related TM
_and_ TCF code in a single, small git repository.
Here is the respective restructuring review:
https://projects.eclipse.org/projects/tools.cdt.tcf/reviews/move-tcf-terminals-code-tm-project
Now unfortunately the review is scheduled to complete by April 1 which is after
M6, but we would like to give adopters
a preview of the new Terminal with M6 in order to get more feedback. Thus
here’s what we are planning:
- The TM project will no longer contribute its
org.eclipse.tm.terminal.* to the simrel
- Instead, the TCF project will contribute
org.eclpse.tm.terminal.*_4.0 to the simrel (already using the *new* namespace).
This affects the “jee” and “reporting” packages which currently directly use
those features:
org.eclipse.epp.packages/packages>grep org.eclipse.tm.terminal */feature.xml
org.eclipse.epp.package.jee.feature/feature.xml: <import
feature="org.eclipse.tm.terminal"/>
org.eclipse.epp.package.jee.feature/feature.xml: <import
feature="org.eclipse.tm.terminal.ssh"/>
org.eclipse.epp.package.jee.feature/feature.xml: <import
feature="org.eclipse.tm.terminal.telnet"/>
org.eclipse.epp.package.jee.feature/feature.xml: <import
feature="org.eclipse.tm.terminal.view"/>
org.eclipse.epp.package.reporting.feature/feature.xml: <import
feature="org.eclipse.tm.terminal"/>
org.eclipse.epp.package.reporting.feature/feature.xml: <import
feature="org.eclipse.tm.terminal.ssh"/>
org.eclipse.epp.package.reporting.feature/feature.xml: <import
feature="org.eclipse.tm.terminal.telnet"/>
org.eclipse.epp.package.reporting.feature/feature.xml: <import
feature="org.eclipse.tm.terminal.view"/>
If you do not take any action, you will simply see the new “4.0” version of
those features from TCF, giving you the new tabbed terminal view.
If you want, you can take the following two actions as soon as TCF starts
contributing the new namespace:
- You may REMOVE “org.eclipse.tm.terminal” since that feature is
auto-required by “org.eclipse.tm.terminal.view” ; that would allow updating the
widget without updating the view in the future.
- You may ADD “org.eclipse.tm.terminal.local” since that feature gives
you the new local terminal (console) prompt
- You may want to set the minimum version range to 4.0 to ensure you
get the new features
- You may want to review the terminal whether it fits your needs and
provide feedback.
Of course other packages are more than welcome to also consume the new Terminal
– all relevant docs are in the marketplace entry cited above.
For now this is just a heads up;
We are planning to add the new “TM Namespace” features to the TCF simrel
contribution over the course of the week.
I will send another notification once the new features are available.
Please let me know of any concerns or questions !
Or comment directly on the Move Review if you want.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
_______________________________________________
epp-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
--- End Message ---
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
