Re: [wtp-dev] Eclipse Wild Web Developer got debug support over DAP, and JSDT.

[Lars Vogel]

Hi Mickael,

Great news IMHO. Thanks for the work. Our vogella team members working with
JS are looking forward to the LSP based JavaScript support.

We also plan to demo it on Fosdem in February.

Best regards, Lars




Am Do., 20. Dez. 2018, 16:56 hat Mickael Istria 
geschrieben:

> Hi all,
>
> I'd like to share with you -who probably have interest in plain Web
> (non-Java EE) development- that Eclipse Wild Web Developer
> https://github.com/eclipse/wildwebdeveloper recently reached major
> milestones:
> * Update to newer Language Server which brings better quality for
> JavaScript and TypeScript development
> * Addition of a debugger that uses (embeds) the VSCode Node Debugger and
> connects with it using the Debug Adapter Protocol. The Debug Adapter
> Protocol already has decent support in LSP4E.
> The quality is now good enough for most real-world use-cases. Some users
> report some satisfaction, package has a good popularity on marketplace with
> constantly growing #installs for the last 6 month now reaching ~2000
> monthly install, some interesting bugs are reported. All the community
> indicators are green.
>
> For JS at least, this stack is much cheaper to maintain and brings a
> higher quality than current (and foreseeable future) JSDT. Separating IDE
> and Language Server/Debug Adapter/TextMate grammars... also allows to put
> the work in places that guarantee a bigger opportunity for reuse.
> It just seems like 1 hour of time spent on improving Wild Web Developer
> and its stack is now more productive than a week of work on JSDT.
>
> So, as stakeholder of this domain, unless you plan to keep relying on
> WebTools for a reason or another, what would be interesting would be that
> you start adopting Eclipse Wild Web Developer, use it, and contribute bug
> reports and patches to it to ensure the quality matches the community
> expectation.
>
> On a political part (I'm not very good at it, some maybe my bosses will
> hate me for being so direct ;), on behalf of Red Hat developers involved in
> those parts of WebTools, we'd like to clarify that we will probably soon
> but progressively stop providing any form of support for JSDT (and maybe
> HTML, CSS and JSON from WebTools) and will move our own portfolio and our
> community effort only to Wild Web Developer when it comes to Web
> development. We'll also try to move the "Eclipse IDE for JavaScript and Web
> developers" package (~1 monthly downloads) to Wild Web Developer
> instead of JSDT very soon, for 2019-03.
>
> Cheers, and let's keep in touch on Eclipse Wild Web Developer issue
> tracker ;)
> --
> Mickael Istria
> Eclipse IDE 
> developer, for Red Hat Developers 
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Broken SSE builds due to compilation error, but only in Hudson (can't reproduce locally)

[Lars Vogel]

FYI -IIRC last time I updated the BREE the classpath was not updated
automatically.



Am 19.12.2017 16:03 schrieb "Nick Boldt" <nbo...@redhat.com>:

Thanks, Lars.

IIRC, Eclipse fixes that automatically if you adjust the BREE in the
manifest editor... but not if you sed everything commandline. ;)



On Tue, Dec 19, 2017 at 3:17 AM, Lars Vogel <lars.vo...@vogella.com> wrote:

> Hi Nick,
>
> I think you also need to adjust the classpath setting for the jre of each
> project.
>
> Best regards, Lars
>
> Am 18.12.2017 18:44 schrieb "Nick Boldt" <nbo...@redhat.com>:
>
>> John,
>>
>> Glad you're on board with updating to 1.8.
>>
>> Here's what *I* would do, because I tend to prefer commandline tools over
>> GUI ones.
>>
>> 1. I would start with piping all the manifest files through sed...
>>
>>for m in $(find . -name MANIFEST.MF); do sed -i -e
>> "s#J2SE-1\..#JavaSE-1.8#" -e "s#JavaSE-1\..#JavaSE-1.8#" ${m}; done
>>
>> 2. Run a build to see what breaks with the updated manifests from 1.4,
>> 1.5, 1.6 -> 1.8.
>>
>> (If you don't like sed, there's prolly a way to do the whole thing in
>> Eclipse, but that'll likely have to be done one plugin at a time.)
>>
>> 3. Then fix all the compilation complaints in Eclipse.
>>
>> 4. You'll probably also want to bump all your plugins/features from x.y.z
>> to x.(y+1).z to avoid breaking old consumers.
>>
>> The easiest way for that is to run this:
>>
>> mvn -Dtycho.mode=maven 
>> org.eclipse.tycho:tycho-versions-plugin:1.0.0:set-version
>> -DnewVersion=5.6.7-SNAPSHOT
>>
>> But bear in mind that it expects ALL plugins/features to be the same
>> version, and if your project doesn't roll that way, it won't bump
>> everything in the reactor in one fell swoop, so you'll have to run it in
>> each and every plugin folder. Or just edit your MANIFEST.MF and pom.xml
>> files by hand.
>>
>> Nick
>>
>>
>>
>> On Mon, Dec 18, 2017 at 12:50 PM, John J Collier <john.j.coll...@ibm.com>
>> wrote:
>>
>>> I agree that we should try and bump the BREE wherever possible. JEE
>>> Tools for example seems to still be on a BREE of J2SE-1.5, if we could get
>>> that up to 1.8, that would be great.
>>>
>>> Nick, what would have to be done to bump up JEE Tools to 1.8?
>>>
>>>
>>> Regards,
>>>
>>> John Collier
>>> Software Developer, WDT/IBM Cloud
>>> Email: john.j.coll...@ibm.com
>>> Phone: (905)-413-3389 <(905)%20413-3389>
>>>
>>>
>>>
>>> From:Nick Boldt <nbo...@redhat.com>
>>> To:Nitin Dahyabhai <nitin.dahyab...@gmail.com>
>>> Cc:Keith Chong <kch...@ca.ibm.com>, Victor Rubezhny <
>>> vrube...@redhat.com>, "General discussion of project-wide or
>>> architectural issues." <wtp-dev@eclipse.org>
>>> Date:2017/12/18 10:57 AM
>>> Subject:Re: [wtp-dev] Broken SSE builds due to compilation
>>> error, but only in Hudson (can't reproduce locally)
>>> Sent by:wtp-dev-boun...@eclipse.org
>>> --
>>>
>>>
>>>
>>> *wild cheering for dropping support for BREE = J2SE-1.4*
>>>
>>> *waves Team Nitin flag*
>>>
>>> If you're keen to break some more eggs, please have a look at
>>> *https://bugs.eclipse.org/bugs/show_bug.cgi?id=528800*
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.eclipse.org_bugs_show-5Fbug.cgi-3Fid-3D528800=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=6q9DBEiC7mYUpxGNnkdhHBpN_7m_NuKsWnDlkmpsTd4=yleicvggdbs8IhYGQg0-YbWEXXoA1kzbeg042TBSZhU=I07gjkLnprJfwDAw_Zuz09qr-lCmNNFbki6PG8U3_mY=>re:
>>> updating toolchains.xml to the latest JDKs, and maybe removing support for
>>> obsolete BREEs like JDK 1.4 - 1.7.
>>>
>>> Just a thought!
>>>
>>> Nick
>>>
>>>
>>>
>>> On Mon, Dec 18, 2017 at 10:45 AM, Nitin Dahyabhai <
>>> *nitin.dahyab...@gmail.com* <nitin.dahyab...@gmail.com>> wrote:
>>> I intend to bump up the BREE of both SSE core and UI to 1.8 in the
>>> master branch to get us past this once and for all. With the platform
>>> dependencies already there, as long as I can keep the code compliance
>>> itself where it is (it's more a pragmatic choice than a dogmatic one) I
>>> don't see much cause not to.
>>>
>>> -Nitin
>>>
>>> On Dec 18, 201

Re: [wtp-dev] Broken SSE builds due to compilation error, but only in Hudson (can't reproduce locally)

[Lars Vogel]

Hi Nick,

I think you also need to adjust the classpath setting for the jre of each
project.

Best regards, Lars

Am 18.12.2017 18:44 schrieb "Nick Boldt" :

> John,
>
> Glad you're on board with updating to 1.8.
>
> Here's what *I* would do, because I tend to prefer commandline tools over
> GUI ones.
>
> 1. I would start with piping all the manifest files through sed...
>
>for m in $(find . -name MANIFEST.MF); do sed -i -e
> "s#J2SE-1\..#JavaSE-1.8#" -e "s#JavaSE-1\..#JavaSE-1.8#" ${m}; done
>
> 2. Run a build to see what breaks with the updated manifests from 1.4,
> 1.5, 1.6 -> 1.8.
>
> (If you don't like sed, there's prolly a way to do the whole thing in
> Eclipse, but that'll likely have to be done one plugin at a time.)
>
> 3. Then fix all the compilation complaints in Eclipse.
>
> 4. You'll probably also want to bump all your plugins/features from x.y.z
> to x.(y+1).z to avoid breaking old consumers.
>
> The easiest way for that is to run this:
>
> mvn -Dtycho.mode=maven 
> org.eclipse.tycho:tycho-versions-plugin:1.0.0:set-version
> -DnewVersion=5.6.7-SNAPSHOT
>
> But bear in mind that it expects ALL plugins/features to be the same
> version, and if your project doesn't roll that way, it won't bump
> everything in the reactor in one fell swoop, so you'll have to run it in
> each and every plugin folder. Or just edit your MANIFEST.MF and pom.xml
> files by hand.
>
> Nick
>
>
>
> On Mon, Dec 18, 2017 at 12:50 PM, John J Collier 
> wrote:
>
>> I agree that we should try and bump the BREE wherever possible. JEE Tools
>> for example seems to still be on a BREE of J2SE-1.5, if we could get that
>> up to 1.8, that would be great.
>>
>> Nick, what would have to be done to bump up JEE Tools to 1.8?
>>
>>
>> Regards,
>>
>> John Collier
>> Software Developer, WDT/IBM Cloud
>> Email: john.j.coll...@ibm.com
>> Phone: (905)-413-3389 <(905)%20413-3389>
>>
>>
>>
>> From:Nick Boldt 
>> To:Nitin Dahyabhai 
>> Cc:Keith Chong , Victor Rubezhny <
>> vrube...@redhat.com>, "General discussion of project-wide or
>> architectural issues." 
>> Date:2017/12/18 10:57 AM
>> Subject:Re: [wtp-dev] Broken SSE builds due to compilation
>> error, but only in Hudson (can't reproduce locally)
>> Sent by:wtp-dev-boun...@eclipse.org
>> --
>>
>>
>>
>> *wild cheering for dropping support for BREE = J2SE-1.4*
>>
>> *waves Team Nitin flag*
>>
>> If you're keen to break some more eggs, please have a look at
>> *https://bugs.eclipse.org/bugs/show_bug.cgi?id=528800*
>> re:
>> updating toolchains.xml to the latest JDKs, and maybe removing support for
>> obsolete BREEs like JDK 1.4 - 1.7.
>>
>> Just a thought!
>>
>> Nick
>>
>>
>>
>> On Mon, Dec 18, 2017 at 10:45 AM, Nitin Dahyabhai <
>> *nitin.dahyab...@gmail.com* > wrote:
>> I intend to bump up the BREE of both SSE core and UI to 1.8 in the master
>> branch to get us past this once and for all. With the platform dependencies
>> already there, as long as I can keep the code compliance itself where it is
>> (it's more a pragmatic choice than a dogmatic one) I don't see much cause
>> not to.
>>
>> -Nitin
>>
>> On Dec 18, 2017, at 10:37 AM, Nick Boldt <*nbo...@redhat.com*
>> > wrote:
>>
>> I've been seeing this for about a week now:
>>
>> [ERROR] Failed to execute goal 
>> org.eclipse.tycho:tycho-compiler-plugin:1.0.0:compile
>> (default-compile) on project org.eclipse.wst.sse.ui: Compilation failure:
>> Compilation failure:
>> [ERROR] /jobs/genie.webtools/webtools-sourceediting_R3_10/workspace/
>> core/bundles/org.eclipse.wst.sse.ui/src/org/eclipse/wst/sse/
>> ui/internal/StructuredTextAnnotationHover.java:[43]
>> [ERROR] HTMLPrinter.addPageProlog(buffer);
>> [ERROR] ^
>> [ERROR] The type java.lang.StringBuilder cannot be resolved. It is
>> indirectly referenced from required .class files
>>
>> Affected jobs:
>> *
>> *https://hudson.eclipse.org/webtools/view/webtools_R3_10/job/webtools-sourceediting_R3_10/*
>> 
>> *
>> *https://hudson.eclipse.org/webtools/view/webtools_R3_10/job/WTP-R3_10_Integration/*
>> 

Re: [wtp-dev] Successful CI requires breaking deps and reorgs, discussion required

[Lars Vogel]

Sounds like a great initiative. We in Eclipse Platform are also
simplifying our project structure at the moment (combining multiple
sub-projects). Great to see that WTP plans to go a similar route.

Best regards, Lars

On Tue, Jul 11, 2017 at 11:09 PM, Robert Stryker <stry...@redhat.com> wrote:
> Hey everyone:
>
> So I've been working on getting that dependency graph stuff going, and I
> haven't been very successful because of the cycles ;) I have some raw data,
> which is excluding (for the most part) test plugins, but a few test plugins
> snuck their way into the report because they're in weird folders like
> "development" instead of "tests". So just gloss over those where possible.
>
> The purpose of this missive is to try to:
>  1)  get a properly ordered project with CI with Jenkins, fewer jobs, fewer
> repos, etc, wherever possible;
>  2) To identify what exact coding changes (other than repo merges) will be
> necessary;
>  3) To get +1's by current component leads to do the above, ie, express a
> willingness to get things done. Without a willingness to make some changes,
> we might be stuck with an old and convoluted structure and alienate the new
> releng guy ;)  (ie Nick Boldt)
>
> Full gist with raw data is here:
> https://gist.github.com/robstryker/b584195b5067b0909dc2b57cbcc9ef8f
>
> But, I can provide a summary.
>
> WTP can be thought of as basically 5 tiers:
>   1) Common/server at the bottom
>   2) jsdt / source-editing
>   3) javaee stuff  (javaee, ejb, webservices)
>   3a/3b) webservices.axis2, webservices.jaxws, and jsf
>   4) Dali at the top
>
> Tier 1:
>
> Common/Server is a bit messy at the moment. Common depends on server
> currently because it exposes an extension point that uses wst.server's
> IRuntime. JavaEE uses that extension point.  If we refactor that extension
> point, it could use the facet IRuntime instead and break the circular
> dependency.
>
> QUESTION 1)
> IS SUCH A CHANGE APPROPRIATE AT THIS TIME? If it's not appropriate, or
> cannot be approved, then we might have real issues in breaking these
> circular dependencies between repos until the next major release.
>
> Once that's broken (there are gerrit pushes for that change), there's still
> one more issue: org.eclipse.jst.common.ui  (in common) depends on
> org.eclipse.jst.common.frameworks (in javaee).
>
> One of these plugins needs to move, either up or down. Luckily the only
> things between javaee and common are jsdt/sourceediting and server. The data
> doesn't show either would be affected by either a move up or a move down.
>
> QUESTION 2: CAN ONE OF THESE PLUGINS BE MOVED AT THIS TIME?
>
> Servertools would look much nicer if it was 1 repository.
>
> QUESTION 3: Will the servertools lead consent to a merge of their repos?
>
> Tier 2:  jsdt / source-editing.  These two have circular dependencies among
> themselves. It'd be great if these 2 projects could figure out a proper
> heirarchy, or, alternately, if they'd agree to be merged into one repo ;)
>
> QUESTION 4: Are the jsdt / source-editing repos able to break their circular
> dependencies? If no, are they willing to be merged into one repo?
>
>
> Tier 3+:  JavaEE / EJB / Webservices:   These guys need a bit more
> investigation. We could theoretically merge ALL of it into one repo, which
> would be very convenient but I'm not sure it's 100% appropriate.
> Alternately, we could deep-dive to see if or how the dependencies could be
> broken. I haven't had time to deep-dive on a plugin-by-plugin level yet.
>
> Tier 4: Dali:  Dali is fine. Probably doesn't need any changes.
>
>
> All of the above is regarding primarily the plugins themselves, NOT any test
> bundles. Nick and I have been working at a pom structure that would allow
> builds of your plugins (ie mvn clean install)  to occur against only your
> required dependencies (and fail if you depend on something that is not on
> your tier or lower), and a different profile to use for integration tests.
>
> This is required because,  surprisingly, almost all unit tests are actually
> integration tests with code much further up or further down the stack as
> compared to where the tests live.
>
> So basically, the 4 questions are, when can we begin making changes (even to
> API if necessary or moving plugins between repos) to Tier 1, is servertools
> willing to merge their repos, and are jsdt/sourceediting capable of breaking
> deps or do they consent to a repo merge?
>
> Thanks all
>
> - Rob Stryker
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit

Re: [wtp-dev] Alternative to WTP editors with TM4E and LSP4E

[Lars Vogel]

Thanks Mickael, looks great. I personally would love to see the old
WTP editors replaced with this approach.

Best regards, Lars

On Tue, Apr 25, 2017 at 6:01 PM, Mickael Istria <mist...@redhat.com> wrote:
> Hi all,
>
> I'd like to share with you some progress about the TM4E and LSP4E projects.
> Both projects are actually targeting to allow easy implementation of rich
> editors reusing external resources and to reduce and factorize maintenance
> effort.
> As WTP editors have been in a bad shape (out-of-date, not comfortable,
> reviews pending for a while) for several years now, we've started to
> look at how TM4E and LSP4E, with the right language servers, can allow to
> have a better web development story in Eclipse IDE than what WTP is
> currently offering.
> Here is the result:
> *
> https://marketplace.eclipse.org/content/bluesky-web-development-eclipse-ide-experimental
> * https://github.com/mickaelistria/eclipse-bluesky
> * http://www.screencast.com/t/BaC9DxHIqD
>
> It's relying on VSCode language servers for HTML, CSS, SCSS, SASS, LESS,
> JSON and on https://github.com/sourcegraph/javascript-typescript-langserver
> for JS and TS.
> It took me about a couple of weeks to bind those with LSP4E and to work on
> the packaging part (which is actually the only necessary part when dealing
> with Language Servers). All the features are provided by the language
> servers and are presented in Eclipse IDE thanks to LSP4E.
>
> Please have a look, give it a try and provide feedback. Contributions (bug
> reports, code, whatever) are entirely welcome at every layer of that work:
> on Platform UI, in LSP4E, in BlueSky integration, in language servers
> directly.
>
> Now, let's just face *the* question: wouldn't it make more sense for our
> community, "products" and users, to start dropping the unmaintained-like WTP
> editors and to consider this alternative as an official replacement and to
> adopt the language server/generic editor approach which happens to work
> well?
>
> Cheers,
> --
> Mickael Istria
> Eclipse developer for Red Hat Developers
> My blog - My Tweets
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Development Status meeting reminder

[Lars Vogel]

> We discuss it each status meeting.

Thanks Carl.

> the project lead for Common has been tied up with other responsibilities

Maybe time to nominate another co-project lead? We did this recently for
several sub-projects in Platform and I also become co-lead in WindowBuilder
to help them with their release process.

Best regards, Lars

On Fri, Sep 30, 2016 at 3:26 PM, Carl Anderson <c...@us.ibm.com> wrote:

> Lars,
>
> If you look at our agendas, you will see that it has been the top item for
> a long time. We discuss it each status meeting. (Along with Dali, which is
> also not Gerrit-enabled.)
> The main issue is that, for historical reasons, Common was broken up into
> 4 different parts- common, snippets, faceted projects, and tests. These
> should all be combined into one Git repository, which should then be
> Gerrit-enabled. (The groups that used to actively work on the broken out
> parts- snippets and fproj- no longer do much with WTP.) However, the
> project lead for Common has been tied up with other responsibilities, and
> needs to get his act together and get this done.
>
> FWIW,
>
> - Carl Anderson
> WTP Common Project lead
>
> [image: Inactive hide details for Lars Vogel ---09/30/2016 08:34:47
> AM---Sorry, Typos: s/can you put enable Gerrit for WTP commons?/can]Lars
> Vogel ---09/30/2016 08:34:47 AM---Sorry, Typos: s/can you put enable Gerrit
> for WTP commons?/can you put the Gerrit
>
> From: Lars Vogel <lars.vo...@vogella.com>
> To: "General discussion of project-wide or architectural issues." <
> wtp-dev@eclipse.org>
> Date: 09/30/2016 08:34 AM
> Subject: Re: [wtp-dev] Development Status meeting reminder
> Sent by: wtp-dev-boun...@eclipse.org
> --
>
>
>
> Sorry, Typos:
>
> s/can you put enable Gerrit for WTP commons?/can you put the Gerrit
> enablement of WTP commons on the agenda?
>
>
>
> On Fri, Sep 30, 2016 at 2:33 PM, Lars Vogel <lars.vo...@vogella.com>
> wrote:
> > Carl, can you put enable Gerrit for WTP commons? See
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=480383
> >
> > I reply to the "status" email, because maybe that is something the WTP
> > team wants to discuss.
> >
> > Best regards, Lars
> >
> > On Thu, Sep 29, 2016 at 4:51 PM, Carl Anderson <c...@us.ibm.com> wrote:
> >> Folks,
> >>
> >> Just a reminder that there will be a Web Tools Platform Development
> Status
> >> Meeting today (9/29)- the agenda has already been posted at
> >> https://wiki.eclipse.org/WTP_2016-09-29 - feel free to add more.
> >>
> >> Sincerely,
> >>
> >> - Carl Anderson
> >> WTP Releng Project lead
> >>
> >>
> >> ___
> >> wtp-dev mailing list
> >> wtp-dev@eclipse.org
> >> To change your delivery options, retrieve your password, or unsubscribe
> from
> >> this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/wtp-dev
> >
> >
> >
> > --
> > Eclipse Platform UI and e4 project co-lead
> > CEO vogella GmbH
> >
> > Haindaalwisch 17a, 22395 Hamburg
> > Amtsgericht Hamburg: HRB 127058
> > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> > USt-IdNr.: DE284122352
> > Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
> http://www.vogella.com
>
>
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
> http://www.vogella.com
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Development Status meeting reminder

[Lars Vogel]

Sorry, Typos:

s/can you put enable Gerrit for WTP commons?/can you put the Gerrit
enablement of WTP commons on the agenda?



On Fri, Sep 30, 2016 at 2:33 PM, Lars Vogel <lars.vo...@vogella.com> wrote:
> Carl, can you put enable Gerrit for WTP commons? See
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=480383
>
> I reply to the "status" email, because maybe that is something the WTP
> team wants to discuss.
>
> Best regards, Lars
>
> On Thu, Sep 29, 2016 at 4:51 PM, Carl Anderson <c...@us.ibm.com> wrote:
>> Folks,
>>
>> Just a reminder that there will be a Web Tools Platform Development Status
>> Meeting today (9/29)- the agenda has already been posted at
>> https://wiki.eclipse.org/WTP_2016-09-29 - feel free to add more.
>>
>> Sincerely,
>>
>> - Carl Anderson
>> WTP Releng Project lead
>>
>>
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe from
>> this list, visit
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: 
> http://www.vogella.com



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Development Status meeting reminder

[Lars Vogel]

Carl, can you put enable Gerrit for WTP commons? See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=480383

I reply to the "status" email, because maybe that is something the WTP
team wants to discuss.

Best regards, Lars

On Thu, Sep 29, 2016 at 4:51 PM, Carl Anderson <c...@us.ibm.com> wrote:
> Folks,
>
> Just a reminder that there will be a Web Tools Platform Development Status
> Meeting today (9/29)- the agenda has already been posted at
> https://wiki.eclipse.org/WTP_2016-09-29 - feel free to add more.
>
> Sincerely,
>
> - Carl Anderson
> WTP Releng Project lead
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Simplify WTP sub-project setup?

[Lars Vogel]

Hi Daniel,

you are bringing up several points which are not closely related to my
suggestion for combining the sub-projects of WTP. This is mainly an
organisational suggestion, not a technical one.

For the code changes you suggesting, I suggest you open bugs and
attach patches to them.

Best regards, Lars

On Mon, Sep 26, 2016 at 8:48 PM, Daniel Kasmeroglu
<daniel.kasmero...@kasisoft.net> wrote:
> Hi Lars,
>
> I agree with your suggestion to combine several projects but I am not aware
> of any plans of this sort (I'm just starting to dive into the wtp project).
> Therefore I can't tell what others on this list do think about it.
>
> Speaking for myself: I don't know the plans of the other participants but I
> hope to make some contributions (although only starting with November when I
> got some time off). I personally believe that we should follow this outline
> in order to get WTP into a modern state (at least that's my personal goal
> for the next Eclipse release):
>
> * Make all projects maven-only: I don't like the idea that we're using
> eclipse configuration files and maven project descriptions together. Maybe
> others have different opinions on that but I think developers nowadays are
> used to check something out and just run "maven clean install". Feedback is
> obviously welcome.
>
> * Fix all basic issues: Loading the code base into Eclipse shows a lot of
> issues such as unnecessary imports, casts, null checks etc. Since these are
> trivial kinds of issues they should be fixed right away.
>
> * Combine projects that make sense to be combined (the sourceediting
> repository is such a candidate).  I'm aware that other developers might have
> different feelings about it.
>
> * Use Java 8. That's my primary goal but I think the other stuff should come
> first. I really like Java 8 ;-)
>
>
> @Others
>
> What is the exact procedure for reviews? I've just took a quick look at
> https://git.eclipse.org/r/#/c/81399/ which had been assigned to Dimitar
> Giormov. I personally would reject this commit purely on the basis that the
> Server.java modification adds multiple duplications. However it could be
> argued that the reviewer could refactor the code afterwards to get rid of
> these duplications. What would be the right mindset in the context of WTP?
>
> Apart from that: Is there any list which shows who's responsible for which
> project?
>
>
> Bye
>
>
> Am 26.09.2016 um 12:07 schrieb Lars Vogel:
>>
>> Hi,
>>
>> https://projects.eclipse.org/projects/webtools seems to have a lot of
>> subprojects, but lots of them seem not very active.
>>
>> Are there plans to combine sub-projects to simplify the committer setup?
>>
>> We have done this in the Eclipse platform project with several
>> projects which had only a very small number of committers, e.g. ua,
>> runtime and text were merged into platform.ui and I think this helped
>> a lot.
>>
>> This might help with issues like Robert having problems to get his
>> patches accepted
>> (http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10071.html).
>>
>> Best regards, Lars
>>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] Simplify WTP sub-project setup?

[Lars Vogel]

Hi,

https://projects.eclipse.org/projects/webtools seems to have a lot of
subprojects, but lots of them seem not very active.

Are there plans to combine sub-projects to simplify the committer setup?

We have done this in the Eclipse platform project with several
projects which had only a very small number of committers, e.g. ua,
runtime and text were merged into platform.ui and I think this helped
a lot.

This might help with issues like Robert having problems to get his
patches accepted
(http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10071.html).

Best regards, Lars

-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] CSS editor as separate feature?

[Lars Vogel]

Hi,

In Neon it still appears as if the WTP CSS editor does not exists. See
screenshot.

Similar for the JSON editor, but at least the JSON editor is visible
if I remove the "Group items by category" flag.

Best regards, Lars

On Thu, Feb 25, 2016 at 8:46 PM, Lars Vogel <lars.vo...@vogella.com> wrote:
> Thanks. Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=488493
> for this request.
>
> Best regards, Lars
>
> On Wed, Feb 24, 2016 at 8:03 PM, Gorkem Ercan <gorkem.er...@gmail.com> wrote:
>> Hi Lars,
>>
>> As a general rule WTP should provide individual features of all its editors.
>> In the case of CSS, CSS does not live on the HTML/browser world only
>> anymore.
>> I can see Qt or E4 making use of the CSS editor.
>> —
>> Gorkem
>>
>>
>>
>> On 24 Feb 2016, at 11:04, Lars Vogel wrote:
>>
>>> Hi Gorkem,
>>>
>>> thanks. Sounds like you think a separate CSS feature makes sense. Is
>>> that correct?
>>>
>>> Best regards, Lars
>>>
>>> On Wed, Feb 24, 2016 at 4:11 PM, Gorkem Ercan <gorkem.er...@gmail.com>
>>> wrote:
>>>>
>>>>
>>>> I guess this has been one of the issues with WTP always reconnized as the
>>>> one complete package for JavaEE development
>>>> while it was actually much more.
>>>> —
>>>> Gorkem
>>>>
>>>>
>>>> On 24 Feb 2016, at 8:25, Lars Vogel wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I'm the Eclipse Platform UI and e4 Co-lead in the Eclipse top-level
>>>>> project. I learned via a Tweet from Kaloyan Raev that WTP offers a CSS
>>>>> editor. Given that I consider myself as experience Eclipse user that
>>>>> is not a good sign.
>>>>>
>>>>> AFAIK WTP does not offer the CSS editor as separate feature. Would it
>>>>> be possible to offer the CSS editor similar to the XML editor as
>>>>> separate installable feature so that it is also ever to discover for
>>>>> Eclipse users?
>>>>>
>>>>> I'm happy to provide a Gerrit review for that, in case you find that
>>>>> useful.
>>>>>
>>>>> Best regards, Lars
>>>>>
>>>>> --
>>>>> Eclipse Platform UI and e4 project co-lead
>>>>> CEO vogella GmbH
>>>>>
>>>>> Haindaalwisch 17a, 22395 Hamburg
>>>>> Amtsgericht Hamburg: HRB 127058
>>>>> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>>>>> USt-IdNr.: DE284122352
>>>>> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
>>>>> http://www.vogella.com
>>>>> ___
>>>>> wtp-dev mailing list
>>>>> wtp-dev@eclipse.org
>>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>>> from this list, visit
>>>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>>>
>>>>
>>>> ___
>>>> wtp-dev mailing list
>>>> wtp-dev@eclipse.org
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from
>>>> this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>>
>>>
>>>
>>>
>>> --
>>> Eclipse Platform UI and e4 project co-lead
>>> CEO vogella GmbH
>>>
>>> Haindaalwisch 17a, 22395 Hamburg
>>> Amtsgericht Hamburg: HRB 127058
>>> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>>> USt-IdNr.: DE284122352
>>> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
>>> http://www.vogella.com
>>> ___
>>> wtp-dev mailing list
>>> wtp-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe from
>> this list, visit
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: 
> http://www.vogella.com



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] SWTBot and/or RCPTT for WTP testing

[Lars Vogel]

Hi Carl,

I have a question with your move to CBI. Are you planning to move all WTP
at once or single repositories?

Best regards, Lars
Am 14.04.2016 8:31 nachm. schrieb "Carl Anderson" :

> Gorkem,
>
> I do not have any first-hand experience with SWTBot. Are there other teams
> at Eclipse that are already using SWTBot for testing?
> My biggest concern since we moved to CBI has been the fact that we have
> not yet got our JUnit tests running again as part of the main release
> build. I would consider getting those running again a much higher priority
> than getting SWTBot (or any new tests) into the main release build.
> However, I am more than willing to review patches and do whatever can be
> done to get the SWTBot tests running in any project's build, with the
> expectation that those will also run correctly in the main release build,
> once the JUnit issues are fixed.
> And, WTP Releng is always welcome to contributions from "future
> committers" - if anyone would like to work towards becoming a WTP Releng
> committer, we could certainly use the help.
>
> FWIW,
>
> - Carl Anderson
> WTP Releng project lead
>
> [image: Inactive hide details for "Gorkem Ercan" ---04/08/2016 10:26:29
> AM---Hi, I have been getting questions about using SWTBot and/o]"Gorkem
> Ercan" ---04/08/2016 10:26:29 AM---Hi, I have been getting questions about
> using SWTBot and/or RCPTT
>
> From: "Gorkem Ercan" 
> To: "General discussion of project-wide or architectural issues." <
> wtp-dev@eclipse.org>
> Date: 04/08/2016 10:26 AM
> Subject: [wtp-dev] SWTBot and/or RCPTT for WTP testing
> Sent by: wtp-dev-boun...@eclipse.org
> --
>
>
>
>
> Hi,
> I have been getting questions about using SWTBot and/or RCPTT
> for tests on WTP. I would like to open this to general discussion and
> especially
> get the opinions from WTP Release engineers.
>
> IMHO we should enable these tools to all WTP projects and allow
> contributors/committers to use
> it if they see it fit. My understanding is this is something WTP Releng
> can enable for all
> the project on WTP parent pom. Any cons to this approach or experiences
> with SWTBot/RCPTT?
> —
> Gorkem
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] New and Noteworthy content for WTP Neon M6

[Lars Vogel]

FYI - https://bugs.eclipse.org/bugs/show_bug.cgi?id=490396 has been
fixed and Gerrit is enabled for the N

On Tue, Mar 22, 2016 at 6:15 PM, Chuck Bridgham <cbrid...@us.ibm.com> wrote:
> JSDT and Source Editing projects have made significant progress in Neon M6,
> and will be using the following bugzilla to help track content.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=490207
>
> The wtp website repo isn't using Gerrit yet to submit patches, so please
> attach new contributions to the bug.
>
>
> Thanks - Chuck
>
> IBM Tools development, Eclipse WTP PMC
> IBM Software Lab - Research Triangle Park, NC
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] New and Noteworthy content for WTP Neon M6

[Lars Vogel]

Hi Chuck,

I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=490396 to
enable Gerrit for the WTP website. Please approach and afterwards add
webmaster to get this repo enabled for Gerrit.

Btw. your N landing page looks really outdated:
https://www.eclipse.org/webtools/development/news/main.php

Best regards, Lars

On Tue, Mar 22, 2016 at 6:15 PM, Chuck Bridgham <cbrid...@us.ibm.com> wrote:
> JSDT and Source Editing projects have made significant progress in Neon M6,
> and will be using the following bugzilla to help track content.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=490207
>
> The wtp website repo isn't using Gerrit yet to submit patches, so please
> attach new contributions to the bug.
>
>
> Thanks - Chuck
>
> IBM Tools development, Eclipse WTP PMC
> IBM Software Lab - Research Triangle Park, NC
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Broken Gerrit validation for webtools/job/sourceediting-gerrit/?

[Lars Vogel]

Thanks Mickael, I hope this gets fixed soon.

On Mon, Mar 7, 2016 at 1:59 PM, Mickael Istria <mist...@redhat.com> wrote:
> We need a new I-Build to complete in order to be able to reference new JSDT
> bundles. Last one is 4 days old, and is failing since then because some
> bundles seem to be missing:
> https://hudson.eclipse.org/webtools/job/WTP-R3_8_Integration/330/console
> Is someone taking care of it?
>
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] Broken Gerrit validation for webtools/job/sourceediting-gerrit/?

[Lars Vogel]

FYI - looks to me that the Gerrit build trigger is broken.
https://hudson.eclipse.org/webtools/job/sourceediting-gerrit/

Best regards, Lars
-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] A dedicated market place entry for JSon feature?

[Lars Vogel]

+1

Same for the CSS editor and XML editor (if they do not have a separate
entry yet in the marketplace, did not check).

On Fri, Mar 4, 2016 at 7:04 AM, Mickael Istria <mist...@redhat.com> wrote:
> Hi all,
>
> As I'm working on https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176 ,
> which is most likely to highly rely on marketplace, I have the feeling that
> the JSON feature should have a dedicated entry on marketplace.
> What do you think? If you agree can someone there create such entry? And as
> a bonus, can they add the 'fileExtension_json' tag to this entry so it can
> be discovered for JSon file?
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Angular2 syntax & HTML Editor limitation

[Lars Vogel]

> As I said, the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=449327 was  
> created in 2014.

Ups, sorry silly me.

Best regards, Lars

On Wed, Mar 2, 2016 at 3:07 PM, Angelo zerr <angelo.z...@gmail.com> wrote:
> Hi Lars,
>
>> do you also an Eclipe bug report for this missing feature in the HTML
>> Editor?
>

>
> Many thank's for your answer.
>
> Regard's Angelo
>
> 2016-03-02 14:57 GMT+01:00 Lars Vogel <lars.vo...@vogella.com>:
>>
>> Hi Angelo,
>>
>> do you also an Eclipe bug report for this missing feature in the HTML
>> Editor?
>>
>> Best regards, Lars
>>
>> Am 02.03.2016 8:38 vorm. schrieb "Angelo zerr" <angelo.z...@gmail.com>:
>>>
>>> Hi everybody,
>>>
>>> For your information, I have the intention to create Angular2 Eclipse
>>> https://github.com/angelozerr/angular2-eclipse which will be based on
>>> Eclipse TypeScript https://github.com/angelozerr/typescript.java
>>>
>>> My big problem today is that HTML Editor doesn't support [], (), * for
>>> attribute names (which is used by Angular2). The issue
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=449327 was created since 2014
>>> and I tell me if it could have any chance that it could be fixed in Neon?
>>>
>>> Many thank's for your help.
>>>
>>> Regard's Angelo
>>>
>>> ___
>>> wtp-dev mailing list
>>> wtp-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>
>>
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
> _______
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Angular2 syntax & HTML Editor limitation

[Lars Vogel]

Hi Angelo,

do you also an Eclipe bug report for this missing feature in the HTML
Editor?

Best regards, Lars
Am 02.03.2016 8:38 vorm. schrieb "Angelo zerr" :

> Hi everybody,
>
> For your information, I have the intention to create Angular2 Eclipse
> https://github.com/angelozerr/angular2-eclipse which will be based on
> Eclipse TypeScript https://github.com/angelozerr/typescript.java
>
> My big problem today is that HTML Editor doesn't support [], (), * for
> attribute names (which is used by Angular2). The issue
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=449327 was created since
> 2014 and I tell me if it could have any chance that it could be fixed in
> Neon?
>
> Many thank's for your help.
>
> Regard's Angelo
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] CSS editor as separate feature?

[Lars Vogel]

Thanks. Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=488493
for this request.

Best regards, Lars

On Wed, Feb 24, 2016 at 8:03 PM, Gorkem Ercan <gorkem.er...@gmail.com> wrote:
> Hi Lars,
>
> As a general rule WTP should provide individual features of all its editors.
> In the case of CSS, CSS does not live on the HTML/browser world only
> anymore.
> I can see Qt or E4 making use of the CSS editor.
> —
> Gorkem
>
>
>
> On 24 Feb 2016, at 11:04, Lars Vogel wrote:
>
>> Hi Gorkem,
>>
>> thanks. Sounds like you think a separate CSS feature makes sense. Is
>> that correct?
>>
>> Best regards, Lars
>>
>> On Wed, Feb 24, 2016 at 4:11 PM, Gorkem Ercan <gorkem.er...@gmail.com>
>> wrote:
>>>
>>>
>>> I guess this has been one of the issues with WTP always reconnized as the
>>> one complete package for JavaEE development
>>> while it was actually much more.
>>> —
>>> Gorkem
>>>
>>>
>>> On 24 Feb 2016, at 8:25, Lars Vogel wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm the Eclipse Platform UI and e4 Co-lead in the Eclipse top-level
>>>> project. I learned via a Tweet from Kaloyan Raev that WTP offers a CSS
>>>> editor. Given that I consider myself as experience Eclipse user that
>>>> is not a good sign.
>>>>
>>>> AFAIK WTP does not offer the CSS editor as separate feature. Would it
>>>> be possible to offer the CSS editor similar to the XML editor as
>>>> separate installable feature so that it is also ever to discover for
>>>> Eclipse users?
>>>>
>>>> I'm happy to provide a Gerrit review for that, in case you find that
>>>> useful.
>>>>
>>>> Best regards, Lars
>>>>
>>>> --
>>>> Eclipse Platform UI and e4 project co-lead
>>>> CEO vogella GmbH
>>>>
>>>> Haindaalwisch 17a, 22395 Hamburg
>>>> Amtsgericht Hamburg: HRB 127058
>>>> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>>>> USt-IdNr.: DE284122352
>>>> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
>>>> http://www.vogella.com
>>>> ___
>>>> wtp-dev mailing list
>>>> wtp-dev@eclipse.org
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>>
>>>
>>> ___
>>> wtp-dev mailing list
>>> wtp-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from
>>> this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>
>>
>>
>>
>> --
>> Eclipse Platform UI and e4 project co-lead
>> CEO vogella GmbH
>>
>> Haindaalwisch 17a, 22395 Hamburg
>> Amtsgericht Hamburg: HRB 127058
>> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>> USt-IdNr.: DE284122352
>> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
>> http://www.vogella.com
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] CSS editor as separate feature?

[Lars Vogel]

Hi Gorkem,

thanks. Sounds like you think a separate CSS feature makes sense. Is
that correct?

Best regards, Lars

On Wed, Feb 24, 2016 at 4:11 PM, Gorkem Ercan <gorkem.er...@gmail.com> wrote:
>
> I guess this has been one of the issues with WTP always reconnized as the
> one complete package for JavaEE development
> while it was actually much more.
> —
> Gorkem
>
>
> On 24 Feb 2016, at 8:25, Lars Vogel wrote:
>
>> Hi,
>>
>> I'm the Eclipse Platform UI and e4 Co-lead in the Eclipse top-level
>> project. I learned via a Tweet from Kaloyan Raev that WTP offers a CSS
>> editor. Given that I consider myself as experience Eclipse user that
>> is not a good sign.
>>
>> AFAIK WTP does not offer the CSS editor as separate feature. Would it
>> be possible to offer the CSS editor similar to the XML editor as
>> separate installable feature so that it is also ever to discover for
>> Eclipse users?
>>
>> I'm happy to provide a Gerrit review for that, in case you find that
>> useful.
>>
>> Best regards, Lars
>>
>> --
>> Eclipse Platform UI and e4 project co-lead
>> CEO vogella GmbH
>>
>> Haindaalwisch 17a, 22395 Hamburg
>> Amtsgericht Hamburg: HRB 127058
>> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>> USt-IdNr.: DE284122352
>> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
>> http://www.vogella.com
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev