Question on data virtualization runtimes and where downloadRuntime support belongs
by Rob Stryker
Hey all:
So, astools has historically housed almost all the download-runtime code
for various jboss runtimes. This changed a bit, however, when karaf /
fuse / serviceworks came on the scene. The FuseIDE code now provides a
home for their server bean loaders (things that accurately identify
local installs), their runtime detectors (to work with turning those
installs into IRuntime objects in eclipse), and their download runtimes
(to know where to fetch them / download them / install them).
Where does Data Virtualization / teiid fit in for this? I'm not very
familiar with what teiid adds on to our server types. It seems they
don't add their own server types, so that would suggest I should put
their runtime detection code in with astools. However, if they require
any special / teiid-only property keys to be set when creating the
server, that would indicate they should handle the import and not me,
since I won't have access to their custom keys. This is important for
runtime detection, as I don't want to return a half-complete runtime /
server with missing flags that's unusable for teiid.
So the question is: where should the code for recognizing local DV
installs, downloading DV runtimes, etc, live? ASTools, or Teiid?
- Rob Stryker
11 years
JBoss Tools 4.3.0.Alpha2 code freeze this Thursday 16th April
by Max Rydahl Andersen
Heya,
Just a friendly reminder that Alpha2 code freeze is coming up on this
Thursday the 16th [1]
if you are on Red Hat VPN you can access the ical for it at [2]. Planned
release of this is for 27th April.
This Alpha2 is "Special" in the sense it is targeting Eclipse Mars M6
which includes a lot of updates and fixes
to the platform including:
* OS X p2 layout has changed = OS X users cannot update from Mars M1-M5
to M6, need to install.
* Jetty 8 to Jetty 9 (major api change)
* egit 3.x to 4.0
* GTK3 bug fixes (Snjezana Go Go!)
* ...and probably a lot more ;)
Big things hoping to show up in Alpha2 if you are not aware are:
* easyimport
* OpenShift v3 tooling (it did not make it to Alpha1)
* First working and pretty version of Central on HTML5
* <fill in your thing here for N&N >
[1]
https://issues.jboss.org/browse/JBIDE/?selectedTab=com.atlassian.jira.jir...
[2]
https://pp.engineering.redhat.com/pp-admin/api/v1/releases/524/schedule-t...
Good luck and don't be afraid to ask if you find issues in M6.
There are still time to fix it upstream! :)
p.s. I'm not available this Friday - but Fred Bricon promised to fill in
for me if any questions/concerns
around code freeze and readiness.
Thanks,
/max
http://about.me/maxandersen
11 years
Fwd: [epp-dev] Heads Up and some action requested : TCF Terminals Moving to TM
by Max Rydahl Andersen
Hey,
I believe this will end up affecting us too.
Opened jira for this: https://issues.jboss.org/browse/JBDS-3384
For most this is just a repackaging that don't affect code, but for Fuse
Tooling
which currently rely on org.eclipse.tm.internal.terminal this will
require changes.
/max
http://about.me/maxandersen
Forwarded message:
> From: Oberhuber, Martin <Martin.Oberhuber(a)windriver.com>
> To: Eclipse Packaging Project <epp-dev(a)eclipse.org>
> Subject: Re: [epp-dev] Heads Up and some action requested : TCF
> Terminals Moving to TM
> Date: Thu, 19 Mar 2015 15:54:07 +0000
>
> 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=d...
>
> 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: epp-dev-bounces(a)eclipse.org [mailto:epp-dev-bounces@eclipse.org]
> On Behalf Of Oberhuber, Martin
> Sent: Monday, March 16, 2015 6:17 PM
> To: EPP Developer Mailing List (epp-dev(a)eclipse.org)
> 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-term...
>
> 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
> epp-dev(a)eclipse.org
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/epp-dev
11 years
Re: [jbosstools-dev] VersionWatch repo
by Max Rydahl Andersen
Did not notice this was not on mailing list.
Jiri - what is the status of this ?
Which repo has the latest content and which one is used in build ?
> where are we with this ?
>
> I see no conclusion and now wondering which repo is the master ?
>
> /max
>
>> Hi Nick,
>>
>> some time ago there was a request to put VersionWatch outside QE
>> repo. So I've created a new repo under my account with it:
>>
>> https://github.com/jpeterka/jbosstools-vwatch
>>
>> If you find it desirable feel free to clone it among other jbosstools
>> repositories.
>>
>> Thanks,
>>
>> Jirka
>>
>> --
>> Jiri Peterka
>> JBoss Developer Studio QE
>> Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic
>> IRC: jpeterka #jboss-qa, #devstudio-qa
>> email: jpeterka(a)redhat.com
>
>
> /max
> http://about.me/maxandersen
/max
http://about.me/maxandersen
11 years
jbosside-dev销售主管2天强化训练
by ngsqdh
尊敬的jbosside-dev，您好！
『销售主管2天强化训练』报名咨询请联系叶·霞1·3·6·9·1·4·7·2·8·1·6；微·信&Q·Q：1·3·2·1·2·5·9·1·2·4。
11 years
