from:"Victor V. Rubezhny"

[wtp-dev] Rework of WebTools SourceEditing and WebServies features

2020-05-07 Thread Victor V. Rubezhny


Hello,

I'd like to ask Committers to review the following PRs made to 
webtools.sourceediting and webtools.webservices repositories:


 * https://git.eclipse.org/r/#/c/161813/ -***Bug 562631
   
*
 
   - Rework webtools.sourceediting features in order to make more
   flexible WTP installation
 * https://git.eclipse.org/r/#/c/162564/
   

   - *Bug 562684
   
*
 
   - Rework webtools.webservices features in order to make more
   flexible WTP installation
 * https://git.eclipse.org/r/#/c/161781/
   

   - *Bug 562634
   
*
 
   - Web UI directly references an action class defined in JSDTI'd like
   to ask Committers to re

These changes allow more flexible and selective installation of 
sourceediting and JSDT-related features during te installation of WTP 
and post installation configuration, allowing to install and uninstall 
JSDT-elated features separately from the source editing tools.


The projets that require WTP source editing features now are allowed to 
use alternative ways of authoring JavaSctipt/TypeSctipt by not having a 
requirement to have JSDT features installed, thus avoiding a similar 
JavaSctipr-related UI elements/actons/tools to be duplicated on the IDE.


Thanks in advance,

Victor Rubezhny

___
wtp-dev mailing list
wtp-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Reminder: development status call tomorrow the 26th

2018-07-25 Thread Victor V. Rubezhny


Hi!

I might not appear tomorrow as I have to go to our Barcelona office 
after noon, so I don't know if I'll be back in time for the meeting.


Regards,
Victor

On 07/25/2018 04:29 PM, Nitin Dahyabhai wrote:

Hi folks,
Just a reminder that our periodic status call takes place tomorrow. 
The agenda has been posted to https://wiki.eclipse.org/WTP_2018-07-26 .


---
Regards,
Nitin Dahyabhai
Eclipse Web Tools Platform
___
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] Project Lead approval needed for WTP 3.10 release review document

2018-06-13 Thread Victor V. Rubezhny


Nitin,

just one note on the release document:

Page 3, Chapter "PMC Organization":
"Victor Rubezhny, Exadel" should read as "Victor Rubezhny, Red Hat" 
(should look exactly as several lines above on the same page).


Other that that, my vote is +1, as JSDT Lead.

Kind Regards,
Victor Rubezhny, Red Hat, Inc.


On 06/13/2018 09:49 PM, Nitin Dahyabhai wrote:

Fellow WTP Project Leads,

Please vote your approval for the draft of our release document that was
just published at
https://www.eclipse.org/webtools/releaseReviews/201806/WebTools3.10.pdf .
Combined with our IP Log, it's an essential part of getting WTP 3.10
out the door. The bug for tracking the Release Review is
https://bugs.eclipse.org/535372 .

My vote is +1, as Source Editing's lead.

---
Nitin Dahyabhai
Eclipse Web Tools Platform
___
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] WTP Development Status meeting reminder

2017-12-07 Thread Victor V. Rubezhny

I'm sorry, but due to lack of normal internet connection I wouldn't 
appear on the meeting today.


I hope I'll back to the normal work in one-two weeks (this week looks 
like a lost one due to two holidays here in Catalonia)


Victor Rubezhny,
JSDT

On 12/07/2017 05:13 PM, Carl Anderson wrote:


Folks,

Just a reminder that there will be a Web Tools Platform Development 
Status Meeting Thursday (12/7)- the agenda has already been posted at 
https://wiki.eclipse.org/WTP_2017-12-07- feel free to add more.


Sincerely,

- Carl Anderson
WTP PMC 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



___
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] WTP Development Status meeting reminder

2017-08-17 Thread Victor V. Rubezhny




On 08/17/2017 09:16 PM, Nitin Dahyabhai wrote:


On Aug 17, 2017, at 2:04 PM, Victor V. Rubezhny <vrube...@redhat.com 
<mailto:vrube...@redhat.com>> wrote:


Hello,

Are the phone numbers / access codes changed?

It doesn't accept old 32557235# on +18884266840

/Victor



I made a point to add a clickable tel: link into the updated calendar 
notice with those numbers, except for the leading ‘1’, and just now 
used it to connect to the meeting. I’ve had problems connecting to 
AT Conference lines from pure VOIP solutions in the past, was one 
involved with yours?


I'm trying to call by Skype-beta (as I always used to call in the past 
with Skype-alfa) to +18884266840 - the mechanical woman is answering me 
and asks for an access code, but after I enter the conference access 
code it tells me that it cannot recognize my code. Unfortunately, Skype 
cannot be started on my phone tonight...


When I'm trying to check the telephone numbers and clicking at 
https://www.teleconference.att.com/servlet/glbAccess?process=1=6460142=2158616239 
link at https://wiki.eclipse.org/WTP_Development_Status_Meetings it just 
shows the following error message:


"www.teleconference.att.com says:

Dial-In Number and Access Code not found. Please re-enter your Dial-In 
Number and Access Code."


So, once I'm not in US, I even couldn't get the right phone number to 
call from Spain.


/Victor



___
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] WTP Development Status meeting reminder

2017-08-17 Thread Victor V. Rubezhny


Hello,

Are the phone numbers / access codes changed?

It doesn't accept old 32557235# on +18884266840

/Victor

On 08/17/2017 01:57 AM, Carl Anderson wrote:


Folks,

Just a reminder that there will be a Web Tools Platform Development 
Status Meeting Thursday (8/17)- the agenda has already been posted at 
https://wiki.eclipse.org/WTP_2017-08-17- feel free to add more.


Sincerely,

- Carl Anderson
WTP PMC 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



___
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] Successful CI requires breaking deps and reorgs, discussion required

2017-07-14 Thread Victor V. Rubezhny


On 07/11/2017 11:09 PM, Robert Stryker wrote:

Hey everyone:



Hello Rob!


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.




I believe we can make these changes to be released in Photon. (I'm 
curious: why it's not named after Pluto?) And I don't think we need to 
rush with those in Oxygen+X releases.




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 ;)


Right now, I'm like "-1" for such a merge. These are two "too-different" 
projects. We just had in HTML Editor the content assist/validation from 
JSDT for embeded JavaScript tags as well as we made SSE validation to 
work on JSDT projects (and provided the according validator) - that's 
why these two projects became to depend on each other...


I'd just prefer to make it one-way dependency... Like to make SSE NOT to 
depend on JSDT.





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?



I hope yes, we can make that dependency to be at least 'one way'

Thanks all

- Rob Stryker


Thanks in advance,
Victor




___
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] Approval of WTP Oxygen release document

2017-06-14 Thread Victor V. Rubezhny


+1

Victor

On 06/14/2017 09:51 PM, Keith Chong wrote:


+1 for Web Services.

Regards,
Keith Chong
WTP Web Services


Inactive hide details for Neil Hauge ---2017/06/14 03:43:16 PM---+1 
NeilNeil Hauge ---2017/06/14 03:43:16 PM---+1 Neil


From: Neil Hauge 
To: "General discussion of project-wide or architectural issues." 


Date: 2017/06/14 03:43 PM
Subject: Re: [wtp-dev] Approval of WTP Oxygen release document
Sent by: wtp-dev-boun...@eclipse.org





+1

Neil

On Jun 14, 2017, at 3:41 PM, Raghunathan Srinivasan
<_raghunathan.srinivasan@oracle.com_
> wrote:

+1 for JSF Tools

*From:*Elson Yuen [_mailto:ey...@ca.ibm.com_] *
Sent:*Wednesday, June 14, 2017 12:32 PM*
To:*General discussion of project-wide or architectural issues.*
Subject:*Re: [wtp-dev] Approval of WTP Oxygen release document

+1 for server tools

Regards,
Elson

-
Elson Yuen, P.Eng.
WebSphere Server Tools and Bluemix Tools Architect
IBM Toronto Lab
Tel: (905) 413-2689, T/L: 313-2689


"Carl Anderson" ---2017/06/14 02:50:14 PM---WTP
project leaders, Please vote your approval for the final draft
of our release document that

From: "Carl Anderson" <_...@us.ibm.com_ >
To: "Web Tools Platform Development" <_wtp-dev@eclipse.org_
>
Date: 2017/06/14 02:50 PM
Subject: [wtp-dev] Approval of WTP Oxygen release document
Sent by: _wtp-dev-bounces@eclipse.org_







WTP project leaders,

Please vote your approval for the final draft of our release
document that was just published_
__

__https://www.eclipse.org/webtools/releaseReviews/201706/WebTools3.9.pdf_



My vote is +1

FWIW,

- Carl Anderson
WTP Releng project lead, WTP Common 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_



___
wtp-dev mailing list_
__wtp-dev@eclipse.org_ 
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit_

__https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_wtp-2Ddev=DwICAg=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=MPRQjQCoeXGM4keF0e3irRoBATxR7RIqYXMHG_Uv7bE=ajpSr6zWxo0Rwk2U_NDAObtPdI2WitY_kqcNSk_R5uU=Vz6W2ZDKuP10pLWnVAQWtB1sx0k_xHqWCfj8yTB9BMo=_

___
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] Fw: [cross-project-issues-dev] jdeps Results on M7 Repo

2017-05-25 Thread Victor V. Rubezhny


Hi Carl,

For Neon we use nashorn in order to run Esprima parser, however it's 
poorly exports its classes meanwhile we still need to use some of them 
even if they're internal:


   ## Start of Java internal API usage report for 
org.eclipse.wst.jsdt.core_2.0.0.v201608251059.jar

   org.eclipse.wst.jsdt.core_2.0.0.v201608251059.jar -> 
/opt/public/common/jdk1.8.0_121.x64/jre/lib/ext/nashorn.jar
   org.eclipse.wst.jsdt.internal.esprima.EsprimaParser 
(org.eclipse.wst.jsdt.core_2.0.0.v201608251059.jar)
  -> jdk.nashorn.internal.runtime.ECMAException JDK internal 
API (nashorn.jar)

   Warning: JDK internal APIs are unsupported and private to JDK implementation 
that are
   subject to be removed or changed incompatibly and could break your 
application.
   Please modify your code to eliminate dependency on any JDK internal APIs.
   For the most recent update on JDK internal API replacements, please check:
   https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool

   ## End of Java internal API usage report for 
org.eclipse.wst.jsdt.core_2.0.0.v201608251059.jar

Not sure if we can fix this...

Also, isn't it a bit too late running such the tests? Or Neon stream 
isn't closed yet?


We're not using nashorn in Oxygen, so I believe this problem should not 
appear in 3.9.x.


Thanks in advance,
Victor


On 05/24/2017 05:15 PM, Carl Anderson wrote:


Victor and Keith,

As the project leads for JSDT (org.eclipse.wst.jsdt.core) and Web 
Services (org.eclipse.wst.wsi), can you look into these issues? (I 
would assume that bugs will be opened shortly, if they haven't already 
been opened.)


FWIW,

- Carl Anderson
WTP PMC lead
- Forwarded by Carl Anderson/Raleigh/IBMon 05/24/2017 11:10 AM-

From: "Daniel Megert" 
To: "Cross Project" 
Cc: Wayne Beaton 
Date: 05/24/2017 10:59 AM
Subject: [cross-project-issues-dev] jdeps Results on M7 Repo
Sent by: cross-project-issues-dev-boun...@eclipse.org





Here is a list of Eclipse projects that violate internal access rules 
regarding jdeps:


org.eclipse.actf.visualization.engines.lowvision
org.eclipse.fx.ui.controls
org.eclipse.fx.ui.panes
org.eclipse.jubula.rc.javafx
org.eclipse.wst.jsdt.core
org.eclipse.wst.wsi

There are also violations in third party plug-ins. You can see the 
full report here: 
_https://hudson.eclipse.org/releng/job/Generate_jdeps_report/8/artifact/jepsReport.txt_


HTH
Dani___
cross-project-issues-dev mailing list
cross-project-issues-...@eclipse.org
To change your delivery options, retrieve your password, or 
unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-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

[wtp-dev] Fix for Bug 501140 - ConcurrentModificationException in J2EEElementChangedListener.getResourceMappings

2017-03-07 Thread Victor V. Rubezhny


Chuck,

could you please review the fix for *Bug 501140* 
 
-ConcurrentModificationException in 
J2EEElementChangedListener.getResourceMappings [1] provided in Gerrit [2]?


The fix looks pretty simple and safe.

Is it still possible to push it into Neon.x?


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=501140 - Bug 501140 - 
ConcurrentModificationException in 
J2EEElementChangedListener.getResourceMappings


[2] https://git.eclipse.org/r/#/c/80793/ - Patch set in Gerrit


Thanks in advance,

Victor

___
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] JSDT 3.8.x maintenance branch is created

2017-02-17 Thread Victor V. Rubezhny



Hello,

I've created R3_8_maintenance branch for Webtools.jsdt project. Please 
use this branch for 3.8.x (Neon.X) builds:


webtools.jsdt: R3_8_maintenance


Thanks in advance,

Victor

___
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] Branching JSDT for Neon maintenance

2017-02-17 Thread Victor V. Rubezhny


Hello,

I've branched JSDT for 3.8.x maintenance, please use the following 
branch for 3.8.x (Neon):


webtools: R3_8_maintenance


Thanks in advance,

Victor Rubezhny

___
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] Status and future outlook of the JSDT debugger

2017-01-23 Thread Victor V. Rubezhny


Angelo,

sorry, unfortunately I found that your answers were moved to junk folder.

I'll try your contribution with typescript.java 
https://github.com/angelozerr/typescript.java/wiki/Installation-Update-Site. 
 



Thanks,
Victor


On 01/22/2017 05:28 PM, Angelo zerr wrote:



2017-01-22 17:04 GMT+01:00 Gorkem Ercan >:





On Sat, Jan 21, 2017 at 9:00 AM, Angelo zerr
> wrote:

Hi Ivan,

I'm very glad that you post this question because in my case I
need to debug TypeScript (in other mean debugging with source
map).

So I have created a patch for JSDT Chrome debugger at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=487465
 and
sourcemap code is based on your sdbg work. See my comment at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=487465#c7


My patch is not perfect but I hope JSDT Team will accept it
and hope guys like you will improve it.


I believe Victor tried to use your patch for minified JS cases and
could not get it to work.
Are you in touch with him?


Victor contacted me about that, I gave him some informattion, but I 
think he is very busy with other topics.



Regard's Angelo

2017-01-21 10:06 GMT+01:00 Ivan Markov >:

Dear all,

Being the maintainer of sdbg.github.io
, the recent (2015-2016) rebirth of
the JSDT tooling is of course something I'm interested it.
(... and unfortunately something I've slept through).

Regarding the JSDT debugging story, as far as I understand
there are two codebases in use:
1) The original JSDT Debug plugins, which support only Rhino
2) A fork of the old Chromedevtools-Java tooling from
Google (last when I looked at it - still in the Google
Code times, it was a completely independent set of Eclipse
plugins, is this still the case?)

The following question to follow (obviously):
Have you considered using the SDBG codebase, and if not,
why not? Technical or legal issues?

Cheers,
Ivan




___
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





___
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] Help needed for jeetools, common and webtools issues

2017-01-19 Thread Victor V. Rubezhny


Carl, Chuck,

Could you please help to review and push the fixes for the following 
issues into the according repositories?


For webtools.javaee:

- ConcurrentModificationException in 
J2EEElementChangedListener.getResourceMappings

https://bugs.eclipse.org/bugs/show_bug.cgi?id=501140
https://git.eclipse.org/r/#/c/80793/

For webtools.common:

- ArrayIndexOutOfBoundsException in ResourceIsLoadingAdapter.getAdapter

https://bugs.eclipse.org/bugs/show_bug.cgi?id=501145
(the repository doesn't look like a gerrit enabled one, so please 
look the patch attached to the Bugzilla)


For webtools:

- Fix JSDT Web Site

https://bugs.eclipse.org/bugs/show_bug.cgi?id=510207
https://git.eclipse.org/r/#/c/88396/1

The jeetools's and common's patches were made a while ago, so they need 
to be rebased over the master branch and we'd like to see these issues 
fixed for 3.8.2 as well.


Thanks in advance,
Victor





___
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] Is Validation dead?

2016-09-21 Thread Victor V. Rubezhny

Oh, no. This preference is only about JavaScript - we had a lot of 
complains on old JavaScript parser that was giving too many false 
positives in its validation while it actually was not able to parse most 
of those scripts (like the minified ones), so we decided to add this 
'exclude from parsing/validation' option for JSDT projects.
For the rest of validators you can only choose to disable validation on 
a project at all using Project Properties->Validation (requires to 
enable the project specific settings) or on whole workspace using 
Window->Preferences->Validation, as well as to play with different 
validators preferences like Window->Preferences->Web->HTML 
Files->Validation (or ...JSON->JSON Files->Validation and so on).


I believe that someone may open a feature request to make it possible to 
exclude some files/folders in a project from any kind of validation in 
Eclipse WTP, and personally me finds such a feature request reasonable 
and really useful for some cases.


Regards,
Victor



On 09/21/2016 09:49 PM, Adam Hardy wrote:

Hi Victor
is the default exclusions pattern meant to apply to all validation 
types, or just to Javascript and Client-side Javascript validation? I 
see validation errors in node_modules and bower_components from HTML 
Syntax validation, JSON validation and from Web Resources validation 
as well in my current project.


Regards
Adam

 Original Message  
Subject: Re: [wtp-dev] Is Validation dead?
From: Victor V. Rubezhny <vrubez...@redhat.com>
To: wtp-dev@eclipse.org
Date: Wed Sep 21 2016 16:59:59 GMT+0100 (GMT Standard Time)


Hello Adam,

why not to use Windows->Preferences->JavaScript->Include 
Path->Default exclusion

patterns ?

By default it should be set to the following pattern:
**/*.min.js,**/node_modules/*,**/bower_components/* which means like 
'not to
validate any files those names ends with min.js (minified javascript 
files) or

is placed inside any node_modules or bower_components folders.

Please check if you have such exclusion patterns set in your 
workspace (for some
reasons, like using an old workspace or saving improper values for 
the exclusion
patterns setting they (the exclusion patterns) might not to work, but 
if you're
creating a new workspace all should work properly (and the patterns I 
specified

above are used to be the default value).

In case you see that exclusion patterns are properly specified, but 
files in
bower_components and/or node_modules folder are still being validated 
then

please file a bug to bugzilla here:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JSDT
and add description on how workspace was created, which kinds of 
projects it
consists of, what is your test project configuration and what values 
are used
for the exclusion patterns. Feel free to attach any log files if you 
see some

error messages that are related to the issue by your opinion.

Thanks in advance,
Victor Rubezhny,
JSDT


On 09/21/2016 05:21 PM, Adam Hardy wrote:
With the default settings, Eclipse will validate everything in 
node_modules

and bower_components and any other directories I create.

This took ages and produced a ton of errors, so I turned off 
validation.


If I want to use validation without seeing tons of these 3rd party 
errors, I
have to add an 'exclude' group in each type of validation (approx 
25) and add

in each directory manually.

This is a lot of work, and then I have to decide if I apply it in the
workspace settings, which will be lost when I upgrade Eclipse next, 
or for

each project.

Is validation functionally dead because of this, or is there a 
work-around, or
is there a solution in the pipeline, like allowing global 
include/exclude groups?


Thanks
Adam


___
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] Is Validation dead?

2016-09-21 Thread Victor V. Rubezhny


Hello Adam,

why not to use Windows->Preferences->JavaScript->Include Path->Default 
exclusion patterns ?


By default it should be set to the following pattern: 
**/*.min.js,**/node_modules/*,**/bower_components/* which means like 
'not to validate any files those names ends with min.js (minified 
javascript files) or is placed inside any node_modules or 
bower_components folders.


Please check if you have such exclusion patterns set in your workspace 
(for some reasons, like using an old workspace or saving improper values 
for the exclusion patterns setting they (the exclusion patterns) might 
not to work, but if you're creating a new workspace all should work 
properly (and the patterns I specified above are used to be the default 
value).


In case you see that exclusion patterns are properly specified, but 
files in bower_components and/or node_modules folder are still being 
validated then please file a bug to bugzilla here: 
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JSDT
and add description on how workspace was created, which kinds of 
projects it consists of, what is your test project configuration and 
what values are used for the exclusion patterns. Feel free to attach any 
log files if you see some error messages that are related to the issue 
by your opinion.


Thanks in advance,
Victor Rubezhny,
JSDT


On 09/21/2016 05:21 PM, Adam Hardy wrote:
With the default settings, Eclipse will validate everything in 
node_modules and bower_components and any other directories I create.


This took ages and produced a ton of errors, so I turned off validation.

If I want to use validation without seeing tons of these 3rd party 
errors, I have to add an 'exclude' group in each type of validation 
(approx 25) and add in each directory manually.


This is a lot of work, and then I have to decide if I apply it in the 
workspace settings, which will be lost when I upgrade Eclipse next, or 
for each project.


Is validation functionally dead because of this, or is there a 
work-around, or is there a solution in the pipeline, like allowing 
global include/exclude groups?


Thanks
Adam


___
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] WTP 3.8.0 tagging (release review underway)

2016-06-15 Thread Victor V. Rubezhny


Thanks Carl!

And thanks to all the contributors!

Webtools.JSDT master branch is now tagged as R3_8_0

Best Regards,
Victor Rubezhny,
JSDT

On 06/15/2016 06:05 PM, Carl Anderson wrote:


Folks,

It is with great pleasure (and many thanks to all of those who helped) 
that I announce that all of the paperwork has been approved, and the 
WTP 3.8.0 release review is underway- that was our last hurdle to be 
part of the Eclipse Neon simultaneous release. Congratulations to all 
on another successful release!
Now, in preparation for Neon.1 and Oxygen builds, I need the project 
leads to tag your repositories with an appropriate tag for WTP 3.8.0- 
I have tagged the Common, Java EE Tools (which includes EJB Tools), 
and Releng repositories with R3_8_0. This is our final step (and a 
critical one, should we ever need to either rebuild WTP 3.8.0 or 
create patches for WTP 3.8.0).
Once again, congratulations and many thanks to all of those who helped 
make the WTP 3.8.0 release a success. We'll be taking a break from our 
meetings- they will start up again in August, in preparation for Neon.1.


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




--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] Approval of WTP Neon Release document

2016-06-09 Thread Victor V. Rubezhny


+1 (JSDT)

Regards,
Victor Rubezhny

On 06/09/2016 06:22 PM, Carl Anderson wrote:


Resending this note, since the original never showed up:

WTP project leaders,

Please vote your approval for the final draft of our release document 
that was published.


https://www.eclipse.org/webtools/releaseReviews/201606/WebTools3.8.pdf

My vote is +1

(It was brought to my attention that project leads, not just the PMC 
members, should give +1)


FWIW,

- Carl Anderson
WTP Releng project lead, WTP Common 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




--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] Fwd: [epp-dev] Neon RC2 packages

2016-05-27 Thread Victor V. Rubezhny


On 05/27/2016 02:26 PM, Mickael Istria wrote:

On 05/27/2016 12:52 PM, Victor V. Rubezhny wrote:
Perhaps we have to file a bug against these messages to bugzilla - 
removing/hiding these messages will not solve the main problem - but 
if reported we could have a reminder of what we have to improve in 
Neon+1.

Ok, thanks for the info.
Let's just not waste resources in avoiding this message, and focus on 
having those navigation features working instead. Do you think it 
would be achievable for Neon.1?
All these features require the creation of a model and type inference. 
So, it's still a question if we can use TypeScript services or something 
other for that.


/Victor




Cheers.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>



___
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




--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] Fwd: [epp-dev] Neon RC2 packages

2016-05-27 Thread Victor V. Rubezhny


On 05/27/2016 01:36 PM, Mickael Istria wrote:

On 05/27/2016 12:33 PM, Ilya Buziuk wrote:

Mickael, thanks for reporting. I will take a look

Thank you.
Another question: are navigation commands such as F3/Go to Declaration 
supposed to work? Whenever I try F3, I get a message in the status bar 
"Current text selection does not resolve to JavaScript element". I'm 
not sure if this is a bug, or just a missing feature to expect for 
next versions.
There is no JavaScript elements produced in Neon because of its core 
changes. The message itself isn't something critical, but reminds us on 
the need of continue the development.


Perhaps we have to file a bug against these messages to bugzilla - 
removing/hiding these messages will not solve the main problem - but if 
reported we could have a reminder of what we have to improve in Neon+1.


/Victor

--
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




--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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?

2016-05-25 Thread Victor V. Rubezhny


Hi,

what build are you talking about?

/Victor

On 05/25/2016 09:58 PM, Lars Vogel wrote:

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  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  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 
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




--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] Some XML Patches

2016-04-22 Thread Victor V. Rubezhny


Nitin, Nick!

Could you look at the fix for 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=491313 that is provided 
through Gerrit: https://git.eclipse.org/r/70427


We'd like to deliver the fix to M7 if there is no any objections.

Thanks in advance,
Victor Rubezhny



On 04/12/2016 05:26 PM, Rob Stryker wrote:

Hi all:

I've got some xml patches which haven't received any love lately. 
Thought I'd ping you all to at least take a look at them.


https://bugs.eclipse.org/bugs/show_bug.cgi?id=491313
https://bugs.eclipse.org/bugs/show_bug.cgi?id=459013

The first adds an option to xml validation preference page to ignore 
or mark as warning / error the specific xml situation where the error 
is in a referenced xml file, not the one currently being validated. A 
lot of times, upstream (ie on the web) xsd files contain errors or 
inconsistancies, and neither users nor our team has any ability to fix 
it.   By adding a preference, our tools users can set it as they wish, 
and our product can set the value directly.


The second is an NPE only replicatable in our test case.

Both need a quick look-through if we'd like them in neon.  The first 
seems to have failed it's gerrit build, but if you look at the logs, 
the failure seems completely unrelated to the patch:


org.apache.maven.InternalErrorException: Internal error: 
java.lang.RuntimeException: No solution found because the problem is 
unsatisfiable.: [Unable to satisfy dependency from 
org.eclipse.wst.jsdt.web.core 1.0.800.qualifier to bundle 
org.eclipse.wst.jsdt.core [1.1.0,2.0.0).; No solution found because 
the problem is unsatisfiable.]



- Rob Stryker


___
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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 parser@master

2016-03-19 Thread Victor V. Rubezhny


That's great! Thank you, Mickael!

/Victor

On 03/18/2016 12:36 PM, Mickael Istria wrote:

On 03/18/2016 10:22 AM, Victor V. Rubezhny wrote:
Sure, yes we'd like to keep JUnit tests running in order to always 
know their status, but currently it seems like site is not produced 
because of thise failures.
Ok, I've changed the job config to have tests running and reporting 
issue, but not blocking build. That introduced the Yellow Ball on 
Hudson: https://hudson.eclipse.org/webtools/job/jsdt-snapshots/ .

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>



___
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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 parser@master

2016-03-19 Thread Victor V. Rubezhny


Mickael,

All should be built fine at the moment, JUnit tests are failing.
I'd suggest to disable JUnit tests until they are fixed.

/Victor

On 03/18/2016 11:05 AM, Mickael Istria wrote:
There seems to be a lot of test failures recently: 
https://hudson.eclipse.org/webtools/job/jsdt-snapshots/

Does your parser change requests some possible build changes?

--
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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/?

2016-03-07 Thread Victor V. Rubezhny


On 03/07/2016 05:33 PM, Gorkem Ercan wrote:



On 7 Mar 2016, at 7:59, Mickael Istria 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?


I believe, Victor is trying to coordinate.


Unfortunately, all I can do is to inform Carl on this (and I believe I 
told about the build problem on last WTP Development Status meeting).


Also we have yet another problem with webtools.jsf project with must be 
fixed after I've bumped *.wst.html.core plug-in version to 1.2 that can 
be fixed by applying this patch: https://git.eclipse.org/r/67849 - I 
believe I have informed Raghunathan on this problem, but if any other 
webtools.jsf committer reads this - feel free to help.


Thanks in advance,
Victor





--
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

___
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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] Build is broken because of change in webtools.sourceediting

2016-03-04 Thread Victor V. Rubezhny


Raghunathan,

(and webtools.jsf committers)

I've pushed a fix for Bug #443097 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=443097) into 
webtools.sourceediting repo which required me to change  html.core 
plug-in's version to 1.2.


As such, the build is currently broken because org.eclipse.wst.jsf.core 
plug-in's manifest contains the following dependency version range:


org.eclipse.wst.html.core;bundle-version="[1.1.0,1.2.0)"

In order to fix this issue, I've created the fix: 
https://git.eclipse.org/r/67849


Please apply it as soon as possible in order to fix the build.
Please modify the features version yourself if it's required for jsf 
project.


Thanks in advance,
Victor Rubezhny,
JSDT

--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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

2016-01-28 Thread Victor V. Rubezhny


The link points to the last week's agenda for some reason.

The correct one - https://wiki.eclipse.org/WTP_2016-01-28

Regards,
Victor

On 01/28/2016 07:12 PM, Carl Anderson wrote:


Folks,

Just a reminder that there will be a Web Tools Platform Development 
Status Meeting today (1/28)- the agenda has already been posted at 
https://wiki.eclipse.org/WTP_2016-01-28 
 - 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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] Updating WTP help docs for Mars.2

2016-01-28 Thread Victor V. Rubezhny


Thank you Chuck!

I've added JSDT's 3.7.2 documentation jar to the list 
(org.eclipse.wst.jsdt.doc_1.4.101.v201507140011.jar).


Kind Regards,
Victor


On 01/28/2016 10:27 PM, Chuck Bridgham wrote:

Hi Victor,

The bug open tracking help changes for Mars.2 is listed below:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=477616

I usually send an update for all projects in the June release, but 
leave it to each subproject for interim updates.


Add a comment with the list of updated help plugins..

For example, this was our entry for Mars: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=469456#c31



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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] JSDT Sync call minutes [20160112]

2016-01-13 Thread Victor V. Rubezhny

+1 from me too, but...

Yes, I've asked not to include any JUnit tests into the contribution.
Otherwise I have had to open a number of additional CQs for those tests,
while we are limited in time.

Any JUnit Tests which aren't bringing a licensing problems are welcomed
and can be added at any time after the contribution is done.

There is a couple of little licensing problems regarding these tests:
1) any json file (like bower.json, for example) is to be written by a
committer or a contributor (we must respect authors) - I think it's the
smallest problem.
2) bower.json and package.json files specify dependencies for a project,
but we have no our own projects in bower/npm repositories published
under Eclipse Public License, so it's very problematic for us to
reference any products (in these files) in our tests. At least I don't
know a single existing javascript library published under EPL in npm.
The same problem is for Bower/NPM tools contributed by Ilya.

So, we CAN write some common JUnit tests for testing some functionality,
like creating some json file, finding content assist proposals according
to its JSON Schema, validating it against the schema, but we CANNOT use
a json file to download any dependency into a test project or, for
example, to show proposals of possible versions of some javascript
library (because it requires us to download it from outside of Eclipse's
repositories) and/or request any info from bower or npm repositories.

As far as I understood, we have to open a CQ every time we need to use
something "from outside" in case we're not sure that it's license allows
us to do it from Eclipse.

Ilya has some JUnit tests for bower/npm tools - but those tests don't
download anything afaik. So, if we have some tests which aren't using a
content not authored by a contributor (Angelo or the other ones) or a
committer - we CAN push such tests into Source Editing repo. Otherwise
we have to open a CQ for every file or a library to be used and/or
downloaded by JUnit test during its work.

In most cases there are no problems to open a CQ... It just takes to
long to resolve sometimes.

Regards,
Victor

On 01/13/2016 11:29 AM, Mickael Istria wrote:

On 01/13/2016 09:23 AM, Angelo zerr wrote:
I think it should be very good to integrate JUnit tests
https://github.com/angelozerr/eclipse-wtp-json/tree/master/core/org.eclipse.wst.json.core.tests
that I have not included in the gerrit patch (Victor told me to
remove it).

+1.
Unless there are complex legal issues with those, can you please turn
them as a patch to webtools.sourceediting and push it onto Gerrit?

--
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

CONFIDENTIALITY NOTICE: This email and files attached to it are
confidential. If you are not the intended recipient you are hereby notified
that using, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited. If you have received
this email in error please notify the sender and delete this email.
___
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] Question about the planned JavaScript Debugger.

2016-01-11 Thread Victor V. Rubezhny

Hi Angelo,

The Chome Dev Tools contribution is ready to go, so please give us a 
couple of days to push ChDT contribution into JSDT, tune the build 
config for it and push the required changes to its protocols.
After that all we'll need to wait is the declaration of build for WTP 
3.8. Once the build is declared ChDT will be available for downloads.

Regards,
Victor

On 01/11/2016 01:41 PM, Angelo zerr wrote:

> It's everybody's debugger ;)

Yes sure:) When I said "your debugger", I meant your work.

>this is why I recommended when we talked last about this to use the 
jsdt debugger APIs instead of any webclipse or Nodeclipse  specific code.

I don't use Webclipse/Nodeclipse debugger (I have none dependencies to 
their API) but I create a well launch according the debugger.

I tell me if it should be possible to provide an update site for jsdt 
debugger and if we wait for the release of Neon to benefit with jsdt 
debugger?

Regard's Angelo

2016-01-10 15:28 GMT+01:00 Max Rydahl Andersen >:

Angelo,

Myeclipse use the same tech behind the scenes. Nodeclipse does the
same. Just that we collaborated with Google to get the code over
to eclipse so everyone gets it as opposed to make it something
requiring a special install.

If you make it work for the eclipse jsdt debugger I'm pretty sure
the same or similar is what myeclipse or Nodeclipse can do for
theirs.

this is why I recommended when we talked last about this to use
the jsdt debugger APIs instead of any webclipse or Nodeclipse
 specific code.

Whatever you do - I hope it works :)

/max
http://about.me/maxandersen

On 08 Jan 2016, at 19:12, Angelo zerr > wrote:

Hi Gorkem,

Many thanks for your answer! I will try to test your work.

My main goal is to support Run/Debug protractor inside AngularJS
Eclipse.

I think I will start with Webclipse (MyEclipse debugger) and
after I will implement it with your debugger.

Thank's again!

Regard's Angelo

2016-01-08 19:03 GMT+01:00 Gorkem Ercan >:

On 8 Jan 2016, at 12:19, Angelo zerr wrote:

Hi all,

I have several questions about your JavaScript Debugger:

* can we play with it? where can we find it?

Gerrit contribution is ongoing in
https://git.eclipse.org/r/#/c/63817/

* is it able to debug node application?

Yes it is..

I'm very interested with this JavaScript Debugger (if it
can support debug
of node application) to :

* add a tern debugger to debug tern plugin inside
tern.java. Today it's
possible to debug tern plugins with MyEclipse JavaScript
Debugger &
Nodeclipse JavaSCript Debugger. I would liek to support
your debugger too.

I think those are also based on the Google's chromedevtools
plugin, so it will probably
not going to be a big effort for you.

* try to debug AngularJS Protractor tests with your
debugger (I have more
and more people who wish run/debug protractor tests). I
have played with
MyEclipse JavaScript Debugger and I can debug protractor
but conf is a
little complex. I would like to give you ideas to easy
the conf of
protractor.

The initial contribution comes with a generic launch
configuration but we
do plan to add more specific (and easier) launch different JS
applications
so your input is welcome.

Many thanks for your answer.

Have a nice WE

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

___
wtp-dev mailing list
wtp-dev@eclipse.org 
To change your

Re: [wtp-dev] Questions about JSDT development

2015-12-25 Thread Victor V. Rubezhny


Philip,

That's great! Thank you for your fix proposals!

Have good holidays!

Kind Regards,
Victor Rubezhny,
JSDT

On 12/25/2015 07:13 PM, Philip Lowman wrote:

Mickael,

Thanks for the pointers, compiling with Java 8 solved the problem.

I'll signup for an Eclipse account and push my patches via Gerrit 
soon.  One is for bug 363580 
 to prevent the 
debugger from resuming all threads when Context.enter() & exit is 
called without starting a script thread (a very common use case for 
us).  The other is a bug having to do with collisions in generated 
filenames in the External Javascript Source folder (which prevents 
opening the correct source file when it happens).



On Wed, Dec 23, 2015 at 4:55 AM, Mickael Istria > wrote:


On 12/23/2015 04:40 AM, Philip Lowman wrote:

Hi,

Hi,

I've developed a couple of fixes for the javascript debugger

Great!
Thanks and welcome!


1. If I need to be concerned with the following build error for
the org.eclipse.wst.jsdt.doc plugin[1] which I get after
following the directions at the URL below.  The error message
sounds like I should be compiling with the Java EE SDK.  Should I
be compiling with the Java EE SDK or is it acceptable to just
disable this plugin and develop with the Java SE SDK?
https://wiki.eclipse.org/JSDT/Development#Building_and_testing_JSDT_locally

osgi.ee  means "OSGi Execution Environment", which
is configured per bundle in the
Bundle-RequiredExecutionEnvironment directlve in the MANIFEST.MF.
It's not related to Java EE.
Those errors seem to highlight that you're using Java 7, whereas
most recent Eclipse bundles require Java 8. So I believe you
should simply install Java 8 and make sure you have it well
configured for the build to use it. "mvn --help" can be used to
tell you which version of Java your build is using.


2. Directions on how to contribute fixes.  What is the preferred
process for JSDT?  Is it to sign the agreement referenced on this
page and just attach patches to Bugzilla (filing bugs when
necessary)?
https://eclipse.org/contribute/

The most efficient and recommended workflow is to push your
patches via Gerrit:
https://wiki.eclipse.org/JSDT/Development#Pushing_a_new_patch_for_review

HTH
-- 
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




--
Philip Lowman


___
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] Proposal: Ignore undefined HTML attributes, elements validation with extension point

2015-12-21 Thread Victor V. Rubezhny


Hi Angelo and WTP HTML Adopters,

For Bug #443097 (Ignore undefined HTML attributes, elements validation 
with extension point) we'd like to propose a change to HTML Validation 
in order to allow Adopters to introduce their own validators for the 
custom tags like the ionic and angular ones that cannot be validated 
through the DTDs or XML Schemas.


The change provides extension point that allows adopters to inject their 
own custom validator, interface which is to be implemented by such a 
validator and abstract class that already implements the required 
interface for the validator and can be derived by a custom validator and 
contain some useful utility methods. Custom validators might either just 
prevent WTP HTML Validator to report errors for custom/dynamic tags and 
attributes or even report their own validation errors.


JUnit test case for HTML Validator is updated with a test case in order 
to test the custom validator.


We'd like to know if this change will be useful for the Adopters and 
does its work.


Please discuss the enhancement at 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=443097

Please review the code for the proposal at https://git.eclipse.org/r/63093

Thanks in advance,
Victor Rubezhny,
JSDT





--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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] Minutes from 2015-12-15 JSDT meeting

2015-12-15 Thread Victor V. Rubezhny


The meeting minutes are now available on wiki.

https://wiki.eclipse.org/JSDT/Confcalls/Minutes_20151215

Thanks everyone for attending.

Victor

--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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] Minutes from 20151208 JSDT meeting

2015-12-08 Thread Victor V. Rubezhny


The meeting minutes are now available on wiki.

https://wiki.eclipse.org/JSDT/Confcalls/Minutes_20151208

Thanks everyone for attending.

Victor


--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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] JSON Editor contribution is approved

2015-11-25 Thread Victor V. Rubezhny


Hi, Mickael!

Yes, that's exactly what we going to do.

Regards,
Victor Rubezhny

On 11/25/2015 10:00 AM, Mickael Istria wrote:

Good news.
Here are my 2 cents.

On 11/25/2015 12:31 AM, Victor V. Rubezhny wrote:
During few discussions that took place during last few weeks we're 
all agreed to put this contribution into WTP SSE repository (correct 
me if I'm wrong), so given the fact of moving the repository into 
Gerrit and merging the webtools.sourceediting.tests repository into 
it, I have the following questions:


- Should we wait for the finish of Gerrit adoption process or we can 
attach the final patch for the issue (bug #471820) before we proceed 
with actual code pushing? And how the adoption goes for 
webtools.sourceediting? (IMHO, it's better to propose a change in 
Gerrit instead of just a text patch attachment for the contribution...)
- Should we wait for the webtools.sourceediting.tests to be finally 
merged into webtools.sourceediting repository? (As far as I 
understood, not only the tests are to be merged, but the overall 
maven project is to be fixed during the merge, so we have to use the 
latest projects configuration for the contribution.)
I would say that we already waited too much. There are already 2 
things we're waiting on for this repository (Gerrit, merge), let's 
avoid adding one more.
If you want a review mechanism, you can consider turning the 
contribution into a commit on a branch at GitHub and review/amed the 
commit there until it's ready to get merged.


--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>



___
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] JSON Editor contribution is approved

2015-11-24 Thread Victor V. Rubezhny


Hi All!

We've finally got the JSON Editor contribution approved, see:

BugZilla for the contribution:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=471820 - [contribution] 
Eclipse WTP JSON Editor


CQs for the contribution and supplementary libraries & JSON schemas:
- http://dev.eclipse.org/ipzilla/show_bug.cgi?id=9924 - JSON Editor
- http://dev.eclipse.org/ipzilla/show_bug.cgi?id=10061 - minimal-json 
Version: 0.9.4
- https://dev.eclipse.org/ipzilla/show_bug.cgi?id=10236 - 
Use/redistribute JSON Schemas originally published at schemastore.org


We still have few minor issues to fix, but it wouldn't take too long to 
get the final commit ready:


- we have to fix the icons (we'll put en empty ones in order not to have 
licensing issues and open the new issue in order to contribute the icons);
- we have to remove some extra file (an old license file that is not 
valid anymore);

- we have to move into org.eclipse.wst.* namespace
- we have to setup a maven project configs for plug-ins and new features

During few discussions that took place during last few weeks we're all 
agreed to put this contribution into WTP SSE repository (correct me if 
I'm wrong), so given the fact of moving the repository into Gerrit and 
merging the webtools.sourceediting.tests repository into it, I have the 
following questions:


- Should we wait for the finish of Gerrit adoption process or we can 
attach the final patch for the issue (bug #471820) before we proceed 
with actual code pushing? And how the adoption goes for 
webtools.sourceediting? (IMHO, it's better to propose a change in Gerrit 
instead of just a text patch attachment for the contribution...)
- Should we wait for the webtools.sourceediting.tests to be finally 
merged into webtools.sourceediting repository? (As far as I understood, 
not only the tests are to be merged, but the overall maven project is to 
be fixed during the merge, so we have to use the latest projects 
configuration for the contribution.)
- Are we able to put JSON Editor plug-ins into 
webtools.sourceediting/bundles (without creating any extra folders)?
- Is it OK to use org.eclipse.wst.json.* namespace for JSON Editor 
plug-ins and features?


We still targeting the contribution for Neon Release.

Thanks in advance,
Victor Rubezhny,
JSDT


--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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] On merging webtools.sourceediting and webtools.sourceediting.tests repositories

2015-11-05 Thread Victor V. Rubezhny


Hi All,

On the work on merging webtools.sourceediting and 
webtools.sourceediting.tests repositories...


I've got the working configuration for build and JUnit testing on test 
merged repository provided by Alina. It required me to cherry pick few 
fixes (thanks to Nitin) from the latest master branches in order to make 
it into some buildable/testable state, but now you I can build 
webtools.sourceediting plug-ins and features as well as site and run 
JUnit tests (which pass successfully) from the merged repository.


You may find this work in merge.tests branch of 
https://github.com/vrubezhny/merged.webtools.sourceediting repository on 
GitHub.com:


https://github.com/vrubezhny/merged.webtools.sourceediting/tree/merge.tests

(Please don't forget to switch into 'merge.tests' branch)

Please, note that this repository branch cannot be used (just pushed 
into) the master branch of sourceediting, because it's done a month ago 
for training and testing purposes, so it doesn't contain some of the 
latest changes from webtools.sourceediting/webtools.sourceediting.tests 
master branches. But we can reproduce the same steps (we've used to make 
it) in order to perform the merging and maven projects setup on real 
working webtools.sourceediting repository.


Also I have a question to the sourceediting tests committers and CBI 
Build team: For most of sourceediting tests projects there is jar 
production is defined in build.property files which produces the 
following jars in tests repo:


tests/org.eclipse.jst.jsp.core.tests/jspcoretests.jar
tests/org.eclipse.jst.jsp.tests.encoding/jspencodingtests.jar
tests/org.eclipse.jst.jsp.ui.tests/jspuitests.jar
tests/org.eclipse.wst.css.core.tests/csscoretests.jar
tests/org.eclipse.wst.css.tests.encoding/cssencodingtests.jar
tests/org.eclipse.wst.css.ui.tests/cssuitests.jar
tests/org.eclipse.wst.dtd.core.tests/dtdcoretests.jar
tests/org.eclipse.wst.dtd.ui.tests/dtduitests.jar
tests/org.eclipse.wst.html.core.tests/htmlcoretests.jar
tests/org.eclipse.wst.html.tests.encoding/htmlencodingtests.jar
tests/org.eclipse.wst.html.ui.tests/htmluitests.jar
tests/org.eclipse.wst.sse.core.tests/ssemodeltests.jar
tests/org.eclipse.wst.sse.ui.tests/sseeditortests.jar
tests/org.eclipse.wst.xml.catalog.tests/catalogtests.jar
tests/org.eclipse.wst.xml.core.tests/ssemodelxmltests.jar
tests/org.eclipse.wst.xml.tests.encoding/tests.jar
tests/org.eclipse.wst.xml.ui.tests/xmluitests.jar
tests/org.eclipse.wst.xml.validation.tests/validatexmltests.jar
tests/org.eclipse.wst.xsd.core.tests/xsdcoretests.jar
tests/org.eclipse.wst.xsd.ui.tests/xsduitests.jar
tests/org.eclipse.wst.xsd.validation.tests/testresources/generatedResults/
tests/org.eclipse.wst.xsd.validation.tests/validatexsdtests.jar

as well as some other test result files and folders.
So, the question is: do we really need these jars or I can remove their 
production from build.properties files?


Thanks in advance,
Victor Rubezhny,
JSDT



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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 couple of questions on WTP SourceEditing repository...

2015-10-26 Thread Victor V. Rubezhny


On 10/27/2015 01:34 AM, Nitin Dahyabhai wrote:


I haven't been the Lead for a little over two and a half years now. 
Both branches *are* open, though some of the version numbers may not 
have been updated for Mars and Mars.1 since not everything had a 
change. I’ve been looking into correcting those and tightening up the 
lower bounds of required plug-ins where internals are referenced, but 
don’t be shy about getting to them before me.



Oops, sorry about that. Off course, Nick is the lead...


As for the merging, Alina has been working on it and ran into some 
build-related issues that we’re still sorting out. Have you been able 
to get a clean build when the histories and working directories are 
merged in a local clone? Either way, please don’t push those kinds of 
changes just yet.


OK, I'll wait for the merge to happen first. And I'll try to build the 
merged repo on my environment.


Regards,
Victor Rubezhny,
JSDT


Regards,
---
Nitin Dahyabhai
IBM Emerging Technology

- Original message -
From: "Victor V. Rubezhny" <vrubez...@exadel.com>
Sent by: wtp-dev-boun...@eclipse.org
To: "General discussion of project-wide or architectural issues."
<wtp-dev@eclipse.org>, Nitin Dahyabhai/Raleigh/IBM@IBMUS
Cc:
Subject: [wtp-dev] A couple of questions on WTP SourceEditing
repository...
Date: Tue, Oct 20, 2015 8:13 PM
Hi,

The questions are probably to Nitin (as he's a project lead for
SourceEditing)...

Am I correct in that if I want to deliver a couple of fixes into
SourceEditing for 3.7.2 I have to push into both -
R3_7_maintenance and
master - branches?
If so, are both branches open for push and is it a good time to push
regarding the following merge of *.tests repository into
webtools.sourceediting repo?

This is regarding the following JSDT/Web issues that have patches
attached:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=480264 - JavaScript
files
that are the children of a 'derived' folder are excluded from the
build/parsing/validation/indexing
https://bugs.eclipse.org/bugs/show_bug.cgi?id=473521 -
NullPointerException in AutoEditStrategyForJs.getJavaProject (67)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472816 -
NullPointerException in FormattingStrategyJSDT.getTranslation (288)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472730 -
NullPointerException in JSDTHoverProcessor.getHoverInfo (58)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472230 -
JavaScriptModelException in JavaModelOperation.runOperation (798)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=470181 -
IndexOutOfBoundsException in JsValidator.performValidation (201)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=467323 -
NullPointerException in NodeImpl.getStructuredDocument (477)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466596 -
NullPointerException in JFaceNodeAdapterForJs.filter (142)

Thanks in Advance,
Victor Rubezhny,
JSDT

--


CONFIDENTIALITY NOTICE: This email and files attached to it are
confidential. If you are not the intended recipient you are hereby
notified
that using, copying, distributing or taking any action in reliance
on the
contents of this information is strictly prohibited. If you have
received
this email in error please notify the sender and delete this email.
___
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] A couple of questions on WTP SourceEditing repository...

2015-10-20 Thread Victor V. Rubezhny


Hi,

The questions are probably to Nitin (as he's a project lead for 
SourceEditing)...


Am I correct in that if I want to deliver a couple of fixes into 
SourceEditing for 3.7.2 I have to push into both - R3_7_maintenance and 
master - branches?
If so, are both branches open for push and is it a good time to push 
regarding the following merge of *.tests repository into 
webtools.sourceediting repo?


This is regarding the following JSDT/Web issues that have patches attached:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=480264 - JavaScript files 
that are the children of a 'derived' folder are excluded from the 
build/parsing/validation/indexing
https://bugs.eclipse.org/bugs/show_bug.cgi?id=473521 - 
NullPointerException in AutoEditStrategyForJs.getJavaProject (67)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472816 - 
NullPointerException in FormattingStrategyJSDT.getTranslation (288)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472730 - 
NullPointerException in JSDTHoverProcessor.getHoverInfo (58)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472230 - 
JavaScriptModelException in JavaModelOperation.runOperation (798)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=470181 - 
IndexOutOfBoundsException in JsValidator.performValidation (201)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=467323 - 
NullPointerException in NodeImpl.getStructuredDocument (477)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466596 - 
NullPointerException in JFaceNodeAdapterForJs.filter (142)


Thanks in Advance,
Victor Rubezhny,
JSDT

--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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] Draft JSDT plan is now on Wiki

2015-10-12 Thread Victor V. Rubezhny

Hi Doug,

On using Node.js we have: 
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9479 - Use of node.js 
installation on user environment Version: v0.12.2 and later

The CQ is resolved, so JSDT can use the user's existing Node.js 
installation (we aren't able to redistribute it).

Regards,
Victor Rubezhny

On 10/12/2015 11:38 AM, Doug Schaefer wrote:
From: > on behalf of Angelo zerr 
>

Cool. I was hoping that but. Ian’s done some great work with
J2V8 and we should make sure we can use it from Eclipse
projects. If there are performance issues, we should try and
fix them. At the end of it, it’s the same engine that node uses.

I think in my side (tern.java) we could improve something too.

Yes, it would be a shame, but it’s the reality we face at
Eclipse. We really need modern web development tooling to be
one of the core pieces of the Eclipse IDE. And being able to
add support for new frameworks quickly is very important.
Angular 2 and React are critical there IMHO, Angular 1 and
Ember are probably in the mix there too. And as we all know
there’s a new one every day :).

We need to do what we need to do, though. Hopefully we can
work this out with tern. If it doesn’t, we need to consider
alternatives.

Please not ethat Orion uses now tern, so for license term, tern
should be OK to be adopted by Eclipse IDE, no?

Tern isn’t the issue. I see we do have CQ’s that approve Tern and 
Acorn for use with Orion. The issue is with the run times. We could 
start with Nashorn. J2V8 would need to be IP approved before we could 
use it.

I know Max has dealt with the legal issues with these components. Be 
good to hear from him on where things are :).

Doug.

Regard's Angelo

Regard's Angelo

2015-10-11 0:02 GMT+02:00 Dawid Pakuła >:

Hi,

currently it’s not possible to do many things in JSDT
by design (JDT history). JSDT build thirth semi model
(something between AST and language model) during it’s
inference process. This model have a lot of
limitations like:
1. Unable to change return type based on arguments
2. Unable to register method/field without AST
3. Unable to drop fields wrongly detected by default
inferencer

So a lot of context based completions and semantic
analysis aren’t possible without second index and
additional (external) processing.

Via bug 466589 [1] I requested porting DLTK inference
engine as fully pluggable, simple and fast alternative
to current.

[1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=466589
-- 
Dawid Pakuła

+48 795 996 064 

On 10 October 2015 at 23:12:37, Doug Schaefer
(dschae...@qnx.com ) wrote:

Thanks Gorkem, that's what I suspected.

I guess the other side of that question, why couldn't
we do the same as what tern does in JSDT? For QML we
have been working on an ANTLR 4 grammars for
JavaScript and still need to make sure it's correct
and then do the hard part, the semantic analysis. But
it could be a path to success as well.

Sent from my BlackBerry 10 smartphone on the Rogers
network.
Original Message
From: Gorkem Ercan
Sent: Saturday, October 10, 2015 12:06 PM
To: General discussion of project-wide or
architectural issues.
Reply To: General discussion of project-wide or
architectural issues.
Subject: Re: [wtp-dev] Draft JSDT plan is now on Wiki

On 9 Oct 2015, at 21:43, Doug Schaefer wrote:

> Quick question on the tern.java integration. If I¹m
correct, it looks
> like
> it¹s optional depending on whether tern.java is
installed on the
> user¹s
> system. What are the arguments against making a
tighter integration if
> tern is so much better than JSDT could ever do.
>
It is legal. tern.java uses tern.js which uses
node.js. Our current CQs
for node.js, and npm are
for prerequisite exempt only and it is not enough for

Re: [wtp-dev] JSDT Weekly sync meetings

2015-10-05 Thread Victor V. Rubezhny

Time is OK for me... We have Californication call two hours and a half 
later, so JSDT Conf. Call at 12pm EST is not too late for me :)


Thanks for the wiki page.

/Victor

On 10/05/2015 06:15 PM, Gorkem Ercan wrote:


I have actually discussed with some of the regular contributors 
including Victor

(who is located in Moscow) before making the arrangements.

Thanks for the wiki page Mickael, it was on my list.
--
Gorkem

On 5 Oct 2015, at 4:49, Mickael Istria wrote:


Hi Gorkem,
I've put that in a wiki page: https://wiki.eclipse.org/JSDT/Confcalls

Note that 12pm EST seems a bit late for european attendees (and even 
later for Russian ones). Given the amount of recent contributors to 
JSDT that are on the other side of the Atlantic, I suggest we try to 
agree on a more convenient schedule.


--
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

___
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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.

___
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] Please tag streams for Mars.1

2015-09-24 Thread Victor V. Rubezhny


JavaScript Development Tools has been tagged with R3_7_1.

Best Regards,
Victor Rubezhny,
JSDT

On 09/23/2015 10:52 PM, Vaninder K Rajput wrote:


Hello Teams,

Please tag streams for Mars.1 before committing any changes. We 
already have our Mars.1 GA driver and no more changes are expected.




*Thanks,*

*Vaninder Rajput*
Websphere Developer Tools
D3-231/8200 Warden/Toronto
email: _vanin...@ca.ibm.com_ 

*IBM Canada*| 8200 Warden Ave Markham ON | _http://w3.canlab.ibm.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



--


CONFIDENTIALITY NOTICE: This email and files attached to it are 
confidential. If you are not the intended recipient you are hereby notified 
that using, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have received 
this email in error please notify the sender and delete this email.
___
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] Is there a status cal on September 10th?

2015-09-09 Thread Victor V. Rubezhny


Hi, Rob!

Calendar at https://wiki.eclipse.org/WTP_2015-09-03 says that there 
should be a meeting but I'm not sure if it's correct (we have bi-weekly 
meetings last few weeks and the last one was on September 3rd).


/Victor

On 09/09/2015 08:13 PM, Rob Stryker wrote:

Hi All:

Just wondering if there's a status call on September 10th or not. 
Thanks in advance.


- Rob
___
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] Where is Victor Rubezhny (JSDT)

2015-07-29 Thread Victor V. Rubezhny


Hi Chris and ALL!

I'm going to three week vacation starting from tonight (GMT +03:00), so 
I probably (because of lack of full-size internet in roaming) can't 
participate in following Smoke Tests and WTP Status Meetings. I'll be 
back at August, 20.


I hope it won't break the release cycle for JSDT and WTP 3.7 Service 
Release 1 - there are not too many changes where done since the last 
Smoke Test requests.


But if it's still required [to do Smoke Testing for JSDT] I'd like to 
ask Chris [if he is able] or any other JSDT comitter to do the required 
testing for the period of my vacation.


Thanks,
Victor Rubezhny,
JSDT.




___
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] Please tag streams for Mars

2015-06-17 Thread Victor V. Rubezhny


Hi All,

I've tagged webtools.jsdt repository with R3_7_0

Best Regards,
Victor Rubezhny


On 06/11/2015 12:16 AM, Carl Anderson wrote:


Folks,

I tagged the following repositories with R3_7_0 :

webtools.common
webtools.common.fproj
webtools.common.snippets
webtools.common.tests
webtools.ejb
webtools.javaee
webtools.releng.aggregator

FWIW,

- Carl Anderson
WTP Build guy

Inactive hide details for Vaninder K Rajput ---06/10/2015 01:42:55 
PM---Hello Teams, Please take some time to tag the streams fVaninder K 
Rajput ---06/10/2015 01:42:55 PM---Hello Teams, Please take some time 
to tag the streams for Mars. Although Mars is not


From: Vaninder K Rajput vanin...@ca.ibm.com
To: wtp-dev@eclipse.org
Date: 06/10/2015 01:42 PM
Subject: [wtp-dev] Please tag streams for Mars
Sent by: wtp-dev-boun...@eclipse.org





Hello Teams,

Please take some time to tag the streams for Mars. Although Mars is 
not done yet, we have our RC4 driver and no more changes to the stream 
are anticipated. So before you start committing changes for 3.8.0, 
please don't forget to tag it.




*
Thanks,*
*
Vaninder Rajput*
Websphere Developer Tools
D3-231/8200 Warden/Toronto
email: _vanin...@ca.ibm.com_ mailto:vanin...@ca.ibm.com
*
IBM Canada*|  8200 Warden Ave Markham ON | _http://w3.canlab.ibm.com_ 
http://w3.canlab.ibm.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


___
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] JSDT has a snapshot site

2015-06-08 Thread Victor V. Rubezhny


That's great news!

Thanks Michael for pushing and Samuel for your support!

Regards,
Victor

On 06/08/2015 08:01 PM, Mickael Istria wrote:

Hi all,

Since JSDT contains some incubating bundles that are not yet 
contributed to WTP main site, I've set up an alternative p2 repo which 
contains the output of latest build of JSDT from master branch, so one 
can use it in order to try the incubating part of JSDT.
The repository is located at 
http://download.eclipse.org/webtools/jsdt/snapshots/ and is populated 
by https://hudson.eclipse.org/webtools/job/jsdt-snapshots/ .


Thanks Samuel Wu for your support.
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
My blog http://mickaelistria.wordpress.com - My Tweets 
http://twitter.com/mickaelistria



___
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] WTP Project leads - Release review

2015-06-03 Thread Victor V. Rubezhny


JSDT is fine.

Regards,
Victor

On 06/02/2015 10:57 PM, Chuck Bridgham wrote:

Hi,

The current Mars release draft document is here:

http://www.eclipse.org/webtools/releaseReviews/201506/WebTools3.7.pdf

Please send me your comments before Thursday at noon EST.

Thanks - Chuck

Senior Architect, WebSphere Developer Tools, Eclipse WTP PMC Lead
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


___
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] OOME and performance issues in JSDT - questions for those who use...

2015-05-26 Thread Victor V. Rubezhny


On 05/26/2015 11:16 PM, Max Rydahl Andersen wrote:


Looks great! Hope this can get into SR1.

Regarding the performance issues listed, I strongly see one  
candidate to cut out from JSDT: It's override indicators that are 
doubling the performance glitches and adds almost nothing useful for 
users (imho). Should we cut it out?


So this is the markers for wether a function or property overrides 
something in the scope known to the parser ?


I reckon this is not even possible to know reliably in javascript thus 
I would be inclined to not keep it enabled if it is a huge

performance stealer!

Yes, that's it. I really don't see this feature anyhow useful in 
JavaScript while this feature eats processor cycles and memory (which is 
really a big problem in JSDT). And that's why I'd suggest to have it 
disabled by default at least.


/Victor


/max
http://about.me/maxandersen
___
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] IPTeam awaiting response from Committer

2015-05-19 Thread Victor V. Rubezhny


Chuck,

IPTeam awaiting response from Committer for CQ #9487 
(http://dev.eclipse.org/ipzilla/show_bug.cgi?id=9487) 'cause they 
require the URL where PMC discussed and voted on the matter.


Do we have such an URL?

I suppose that the similar questions may appear for CQs #9479 
(http://dev.eclipse.org/ipzilla/show_bug.cgi?id=9479) and #9488 
(http://dev.eclipse.org/ipzilla/show_bug.cgi?id=9488) as well.


Thanks in advance,
Victor Rubezhny,
JSDT
___
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] OOME and performance issues in JSDT - questions for those who use...

2015-05-19 Thread Victor V. Rubezhny


Hi All,

I'd like to ask several questions regarding  OOME while parsing/infer 
types issues and the overall performance...


There are pretty many related issues in bugzilla like the following:
*Bug 317249* https://bugs.eclipse.org/bugs/show_bug.cgi?id=317249 
-[performance] Eclipse frequently hangs with high CPU when editing 
JavaScript with lots of local declarations
*Bug 323283* https://bugs.eclipse.org/bugs/show_bug.cgi?id=323283 
-[performance] Opening env.rhino.1.2.js hangs Eclipse
*Bug 324299* https://bugs.eclipse.org/bugs/show_bug.cgi?id=324299 
-[performance] Javascript editor crashes or destabilizes Eclipse

and many others...

These issues aren't easy to fix and mostly require to have some 
compromise between the performance and functionality.


As such, I'd like to ask: do we need a mode/option for JSDT when there 
is no JavaScript parsing/validation is applied? Using such a mode users 
will get:

- No warnings/error markers and/or annotations
- No outline/type hierarchy/override indicators.
- No validation/content assist/refactoring allowed in JavaScript Editor.
But:
- JavaScript editor will be as fast as just a text editor and will still 
be syntax-highlighted.

- No more OOME errors
- (in future) Custom validators/content assist providers allowed.

This could really help with performance on big projects especially when 
JSDT doesn't plays the main role in project development.


Users may test such an option by replacing they JSDT from WTP M7 by the 
version built from my playground here:

https://github.com/vrubezhny/webtools.jsdt/tree/no-build-no-validation-mode-enabled

Use the following command to build:
cd YourProjects/webtools.jsdt
mvn clean install -DskipTests=true -Pbuild-individual-bundles

Then install from local site 
YourProjects/webtools.jsdt/site/target/repository/ directory 
(available after successful build).


What do you need to make it fast - is just to set ECMAScript compliance 
level preference value to  External Builder/Validator on 
JavaScript-Validator preference page.


BTW, having such option could be really useful if you're using a product 
like tern.java and angularjs-eclipse - they're provide ECMA5 
compatibility and work a really faster this way.


And as no parsing/validation/content assist and so on is available when 
External Builder/Validator option is selected, I'd like to ask users 
what features they are really need and use in JSDT?


Regarding the performance issues listed, I strongly see one candidate to 
cut out from JSDT: It's override indicators that are doubling the 
performance glitches and adds almost nothing useful for users (imho). 
Should we cut it out?


What do you think?

Thanks in advance,
Victor Rubezhny,
JSDT

___
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] IPTeam awaiting response from Committer

2015-05-19 Thread Victor V. Rubezhny


Chuck,

yes, https://github.com/npm/npm/archive/master.zip is the correct link 
for the latest NPM version sources.


But I didn't feel like they're asking for an URL to source code, I 
rather feel it as they're asking for a PMC discussion log/message 
thread/message.


Thanks in advance,
Victor Rubezhny,
JSDT

On 05/19/2015 06:34 PM, Chuck Bridgham wrote:

Hi Victor,

We were referring to the source attachment when we voted.  Could you 
please find the original url download locations of these source files 
from the respective project sites - and add a comment for each?
For example: https://github.com/npm/npm/archive/master.zipcould be 
what they are looking for? Please confirm.



Thanks - Chuck

Senior Architect, WebSphere Developer Tools, Eclipse WTP PMC Lead
IBM Software Lab - Research Triangle Park, NC



From: Victor V. Rubezhny vrubez...@exadel.com
To: Chuck Bridgham/Raleigh/IBM@IBMUS, General discussion of 
project-wide or architectural issues. wtp-dev@eclipse.org

Date: 05/19/2015 10:42 AM
Subject: [wtp-dev] IPTeam awaiting response from Committer
Sent by: wtp-dev-boun...@eclipse.org




Chuck,

IPTeam awaiting response from Committer for CQ #9487
(http://dev.eclipse.org/ipzilla/show_bug.cgi?id=9487) 'cause they
require the URL where PMC discussed and voted on the matter.

Do we have such an URL?

I suppose that the similar questions may appear for CQs #9479
(http://dev.eclipse.org/ipzilla/show_bug.cgi?id=9479) and #9488
(http://dev.eclipse.org/ipzilla/show_bug.cgi?id=9488) as well.

Thanks in advance,
Victor Rubezhny,
JSDT
___
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 learning about JSDT

2015-05-06 Thread Victor V. Rubezhny


Welcome Gloria!

As Mickael already suggested, https://wiki.eclipse.org/JSDT/Development 
is the first read for JSDT.
Source code can be obtained from git by cloning from 
git://git.eclipse.org/gitroot/jsdt/webtools.jsdt, but I'd suggest you to 
clone the whole WTP project recursively by running:


git clone --recursive 
http://git.eclipse.org/gitroot/webtools/webtools.releng.aggregator.git


webtools.jsdt project will be inside the project structure.

The main source for the bugs/issues is Bugzilla: 
https://bugs.eclipse.org/bugs/describecomponents.cgi?product=JSDT
If you want to fix an issue that is not reported in BugZilla feel free 
to open a new one.


And, also as Mickael said, a good point to start improving the JSDT 
project is Sonar issues: 
https://dev.eclipse.org/sonar/drilldown/issues/org.eclipse.webtools.jsdt:jsdt-parent?severity=CRITICAL


You may propose your fixed either by attaching a patch to the BugZilla 
issue or by pushing your fix into Gerrit (You should register and 
achieve ssh key to use it): 
https://git.eclipse.org/r/#/q/project:jsdt/webtools.jsdt .


Feel free to ask your questions on wtp-dev mailing list: 
https://dev.eclipse.org/mailman/listinfo/wtp-dev (it looks like you're 
already subscribed here)


Best Regards,
Victor Rubezhny,
JSDT


On 05/06/2015 04:48 PM, Gloria Yadira Torrealba Melendez/Mexico/IBM wrote:


Hello, my name is Gloria Torrealba, currently a developer working at 
IBM on web tooling for a product that extends WTP.


My specific interest is in JSDT and I look forward to working with the 
wtp dev community in helping out with the JSDT project.


I am starting to learn more about this project and would welcome any 
pointer/guidance to get me up to speed.


Thanks!


Regards


*Gloria Yadira Torrealba Melendez*   2200 Camino A El Castillo  
Rational Application Developer   El Salto, 45680
Phone:  +52-33-3669-7000 x5576   Mexico
e-mail: glor...@mx1.ibm.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

Re: [wtp-dev] Is PMC approval required for non-UI bugs to merge after M6 is released?

2015-03-26 Thread Victor V. Rubezhny


Thanks Neil!

Looks like document I've been searched for... and haven't found.

/Victor

On 03/27/2015 12:22 AM, Neil Hauge wrote:

Victor,

You might find last years Ramp Down plan helpful as well.  The same 
general plan will be in place for Mars release, but it covers the 
basics that Carl described.


https://wiki.eclipse.org/WTP_3.6_Ramp_down_Plan_for_Luna

Neil

On 3/26/2015 5:19 PM, Victor V. Rubezhny wrote:

Carl,

Thanks for explanation and historical references :)
I'd rather save your answer handy.

/Victor

On 03/26/2015 09:29 PM, Carl Anderson wrote:


Victor,

The info you are looking for is on 
https://wiki.eclipse.org/WTP_PMC_Defect_Review . The main issue is 
that any bug that has impact outside of WTP needs PMC approval after 
M6.  That includes new features, API changes (not internal... public 
API), and any UI changes that effect the translatable files.  Those 
changes need to be approved first by the project lead (or his 
delegate), and then by the PMC, adding in whatever verbiage is 
necessary for the PMC to understand what they are approving.  (Way 
back when, after RC1, some foolish WTP developer asked for PMC 
approval on a behavior change.  The PMC thought it was just a bug 
fix and approved.  Things got ugly when it affected an adopter of 
WTP.  So our process was changed to make it clear that the PMC 
approval is for a specific reason in those cases.  And that foolish 
developer?  Well, he went on to become the WTP Releng project lead, 
and a member of the WTP PMC!)
If all you are doing is fixing bugs that do not have an external 
effect, then PMC approval is not needed until RC1 is declared.


FWIW,

- Carl Anderson
WTP Releng project lead, and a member of the WTP PMC

Inactive hide details for Victor V. Rubezhny ---03/26/2015 
01:44:23 PM---Hi, I have a number of bug fixes to merge into JSDT 
Victor V. Rubezhny ---03/26/2015 01:44:23 PM---Hi, I have a number 
of bug fixes to merge into JSDT master for Mars stream,


From: Victor V. Rubezhny vrubez...@exadel.com
To: General discussion of project-wide or architectural issues. 
wtp-dev@eclipse.org

Date: 03/26/2015 01:44 PM
Subject: [wtp-dev] Is PMC approval required for non-UI bugs to merge 
after M6 is released?

Sent by: wtp-dev-boun...@eclipse.org





Hi,

I have a number of bug fixes to merge into JSDT master for Mars stream,
but I'm a bit lost in translations...

Once upon a time I read a doc (probably on wiki) that regulate the
possibility of pushing the code into master depending on the stage of a
project (When a PMC Approval is required for UI/Non-UI issues and so
on). It looks like I've lost the URL to that document and cannot 
find it

for some reason. Could anybody please send a link to such a document if
it really exists?

Am I correct in that I don't need a PMC Approval for non-UI fixes and I
can deliver these fixes even after M6 is declared (but before the
declaration of M7?)?

The fixes I'd like to include into JSDT Mars stream are:

- https://bugs.eclipse.org/bugs/show_bug.cgi?id=387850 - Update to 
Rhino

1.7R4
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=453700 - Incorrect
parentheses clean up in JS files
- probably few fixes provided by Gerrit contributions (I'm reviewing
some fixes for Sonar FindBug issues at the moment)

All these fixes make no harm for UI, so they don't require to change
translations, docs and so on.

And a minor question on Bug# 453700: This bug is included into the
Great Fixes for Mars competition, but suddenly I've fixed it by
myself... So, what should I do with it: wait for a possible fix from
competitors until the competition is finished (May 6, 2015) or push my
fix and cancel the issue from a competition (probably to replace it 
with

another issue)?

Thanks in advance,
Victor Rubezhny,
JSDT
___
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




___
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

Re: [wtp-dev] Is PMC approval required for non-UI bugs to merge after M6 is released?

2015-03-26 Thread Victor V. Rubezhny


Carl,

Thanks for explanation and historical references :)
I'd rather save your answer handy.

/Victor

On 03/26/2015 09:29 PM, Carl Anderson wrote:


Victor,

The info you are looking for is on 
https://wiki.eclipse.org/WTP_PMC_Defect_Review . The main issue is 
that any bug that has impact outside of WTP needs PMC approval after 
M6.  That includes new features, API changes (not internal... public 
API), and any UI changes that effect the translatable files.  Those 
changes need to be approved first by the project lead (or his 
delegate), and then by the PMC, adding in whatever verbiage is 
necessary for the PMC to understand what they are approving.  (Way 
back when, after RC1, some foolish WTP developer asked for PMC 
approval on a behavior change.  The PMC thought it was just a bug fix 
and approved.  Things got ugly when it affected an adopter of WTP.  So 
our process was changed to make it clear that the PMC approval is for 
a specific reason in those cases.  And that foolish developer?  Well, 
he went on to become the WTP Releng project lead, and a member of the 
WTP PMC!)
If all you are doing is fixing bugs that do not have an external 
effect, then PMC approval is not needed until RC1 is declared.


FWIW,

- Carl Anderson
WTP Releng project lead, and a member of the WTP PMC

Inactive hide details for Victor V. Rubezhny ---03/26/2015 01:44:23 
PM---Hi, I have a number of bug fixes to merge into JSDT Victor V. 
Rubezhny ---03/26/2015 01:44:23 PM---Hi, I have a number of bug fixes 
to merge into JSDT master for Mars stream,


From: Victor V. Rubezhny vrubez...@exadel.com
To: General discussion of project-wide or architectural issues. 
wtp-dev@eclipse.org

Date: 03/26/2015 01:44 PM
Subject: [wtp-dev] Is PMC approval required for non-UI bugs to merge 
after M6 is released?

Sent by: wtp-dev-boun...@eclipse.org





Hi,

I have a number of bug fixes to merge into JSDT master for Mars stream,
but I'm a bit lost in translations...

Once upon a time I read a doc (probably on wiki) that regulate the
possibility of pushing the code into master depending on the stage of a
project (When a PMC Approval is required for UI/Non-UI issues and so
on). It looks like I've lost the URL to that document and cannot find it
for some reason. Could anybody please send a link to such a document if
it really exists?

Am I correct in that I don't need a PMC Approval for non-UI fixes and I
can deliver these fixes even after M6 is declared (but before the
declaration of M7?)?

The fixes I'd like to include into JSDT Mars stream are:

- https://bugs.eclipse.org/bugs/show_bug.cgi?id=387850 - Update to Rhino
1.7R4
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=453700 - Incorrect
parentheses clean up in JS files
- probably few fixes provided by Gerrit contributions (I'm reviewing
some fixes for Sonar FindBug issues at the moment)

All these fixes make no harm for UI, so they don't require to change
translations, docs and so on.

And a minor question on Bug# 453700: This bug is included into the
Great Fixes for Mars competition, but suddenly I've fixed it by
myself... So, what should I do with it: wait for a possible fix from
competitors until the competition is finished (May 6, 2015) or push my
fix and cancel the issue from a competition (probably to replace it with
another issue)?

Thanks in advance,
Victor Rubezhny,
JSDT
___
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] The Bower IDE contribution

2015-03-25 Thread Victor V. Rubezhny


On 03/25/2015 05:41 PM, Mickael Istria wrote:

On 03/25/2015 03:34 PM, Konstantin Komissarchik wrote:
1. The “incubating” term has special meaning per EDP. A mature 
project cannot have incubating code in its source repository. That 
doesn’t mean that you couldn’t use a different term… alpha, beta, etc.
You're right, in that case, we should talk about Experimental 
plugins (Bower) for a mature project (JSDT)

Correct


2. If this code is merged into JSDT source repo, it and all of its 
dependencies must be able to pass the IP review before JSDT 3.7 can 
release. The IP review covers the entire source repo, even if a 
certain piece isn’t being released.


I assumed there were already IP approval for Bower, maybe I'm wrong. 
If not, then I understand that it's currently a blocker for merging in 
JSDT, and opening CQs should be top-priority.
All the dependencies are existing Eclipse project (JGit is the main 
one). The code itself (initial one) has passed the IP approval: 
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9173
But as we're still modifying it, it looks like we have to get another 
approval on it before merging it into a release stream.


3. Only a project can have releases. There is no formal notion of a 
component and you cannot have informal components making releases, so 
no Bower IDE 0.1 release, for instance. That doesn’t mean that you 
couldn’t exclude some functionality that’s in the source repo from a 
JSDT release or deliver different pieces of a JSDT release in 
different p2 repositories.


As far as I know, there is no plan to release Bower integration 
separately from JSDT. @Victor: is there?

I don't have such plans.

/Victor


--
Mickael Istria
Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
My blog http://mickaelistria.wordpress.com - My Tweets 
http://twitter.com/mickaelistria



___
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] The Bower IDE contribution

2015-03-24 Thread Victor V. Rubezhny


On 03/23/2015 02:34 PM, Mickael Istria wrote:

TL;DR: Being in master != being in delivery for Mars.

On 03/23/2015 12:21 PM, Victor V. Rubezhny wrote:
I didn't merged the code in master, since we still have few issues 
that blocks us from doing it in Mars (I don't think we can get them 
fixed in time for Mars, so it looks like we're missing Mars stream 
with this contribution).
That's not a problem: we can have code in master without shipping it 
on Mars, that's what I strongly believe is the best approach for 
easier collaboration, and to avoid risk of diverging branches.
IMHO, It's better to write your suggestions here (in mailing list) 
first, because I'm going to push another patch set into Gerrit ( 
https://git.eclipse.org/r/#/c/41693/ ), so if you have some code 
comments to do then your comments could be 'forgotten'. But still 
free to add comments to the change.
Suggestion is that for a 1st integration in master, just include the 
bundles, not the pom files, do not update other pom files, feature.xml 
nor category.xml. So the code is there, people can work on it, but not 
altering the build and delivery.
But this will not enable neither the building of Bower plug-ins, nor 
running its JUnit tests then.


Then next iteration would be to see if we can build it easily, include 
in the category.xml file as a separete entry, without modifying the 
regular JSDT feature so it wouldn't get in Mars. That would allow 
people who want to try it to get it from a p2 repository.
I can create a category for Bower IDE, but again: what will go into this 
category in case we aren't adding the Bower plug-ins into the build? It 
looks for me that we have to add the bower-related plug-ins to 
pom.xml-s, to create a separated feature for bower and then include that 
feature into site/pom.xml and category.xml, but not to 
jsdt.feature/jsdt_sdk.feature. But I'm not sure if bower plug-ins will 
not became 'installable by default' in such case.


IMHO, contributing it into master will not make any harm (visually it 
will add few actions to context menus) for WTP and JSDT, all the 
'issues' are only on how Bower IDE works. But it looks unfinished at 
the moment and still have few important issues to be fixed before 
that possible merge to master. M6 is going to be declared today or in 
few days, so it looks like it's too late to merge. I'm sure we can 
finish it for the Mars+1 stream.


But I'd still like to hear/read on your suggestions.
Being in master and being in Mars are totally separated topics, both 
technically and organisationally. The most efficient and easier 
approach would be to have code in master right now, but not ship it in 
Mars. The fact that M6 is approaching doesn't forbid merging unrelated 
changes. It's actually something we could even add on the day before 
Mars if we wanted ;)

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
My blog http://mickaelistria.wordpress.com - My Tweets 
http://twitter.com/mickaelistria



___
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] The Bower IDE contribution

2015-03-23 Thread Victor V. Rubezhny


Mickael,

I didn't merged the code in master, since we still have few issues that 
blocks us from doing it in Mars (I don't think we can get them fixed in 
time for Mars, so it looks like we're missing Mars stream with this 
contribution).


IMHO, It's better to write your suggestions here (in mailing list) 
first, because I'm going to push another patch set into Gerrit ( 
https://git.eclipse.org/r/#/c/41693/ ), so if you have some code 
comments to do then your comments could be 'forgotten'. But still free 
to add comments to the change.


IMHO, contributing it into master will not make any harm (visually it 
will add few actions to context menus) for WTP and JSDT, all the 
'issues' are only on how Bower IDE works. But it looks unfinished at the 
moment and still have few important issues to be fixed before that 
possible merge to master. M6 is going to be declared today or in few 
days, so it looks like it's too late to merge. I'm sure we can finish it 
for the Mars+1 stream.


But I'd still like to hear/read on your suggestions.

Regards,
Victor Rubezhny


On 03/23/2015 01:38 PM, Mickael Istria wrote:

On 03/17/2015 07:37 AM, Mickael Istria wrote:

On 03/16/2015 02:44 PM, Victor V. Rubezhny wrote:
I think it's a good proposal to merge the current Bower IDE into 
master, but I don't get how I can make it go into the build and not 
include it into JSDT/JSDT_SDK features at the same time: If I'm not 
including the plug-ins, will they be built still and added into the 
update site?
The idea is to add it to the pom.xml so it gets built and to add it 
as a separate entry in the category.xml (under an Experimental or 
Incubation category of JSDT). Then, if necessary/useful, we may also 
tweak the global WTP category.xml to include it there as well.
@Victor: so did you merge the code in master? Is it still worth 
commenting on the Gerrit review ( https://git.eclipse.org/r/#/c/41693/ 
)? I could put comments there to explain how to integrate it into the 
JSDT build without altering what's delievered to WTP and Simrel in a 
1st time.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
My blog http://mickaelistria.wordpress.com - My Tweets 
http://twitter.com/mickaelistria



___
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] The Bower IDE contribution

2015-03-17 Thread Victor V. Rubezhny


Carl,

Yes, Max is correct.

There is no any impact on any WTP feature, it's only about using the 
Bower's IDE features and its commands.


Regards,
Victor


On 03/17/2015 01:39 PM, Max Rydahl Andersen wrote:

The performance is only if you actually use the bower functionality.

And its just caused by jgit only supporting full clones, not shallow 
clones
thus the bower support here is much slower than native bower which can 
do the

must faster shallow clone.

/max



Victor,

I believe that the Bower contribution should be pushed to master 
when
you believe that it is ready.  We can treat it like we have treated 
the JPA
Diagram Editor.  If there are sufficient-enough issues for us to not 
have

this enabled by default, we can also add in a default to disable it, and
allow a way for users that want/need it enabled to enable it.
The main question I would have about the slowness would be for
non-JSDT users that use WTP.  Will there be an overall performance 
impact
from these plugins?  Or is it limited to just people that use JSDT?  
From
what I read below, it seems to be limited to those that use JSDT.  If 
this
truly degrades the performance of WTP for all users, it should be 
disabled

by default.  But we can discuss that and other options as necessary.
Please let me know if you have any questions/comments/concerns.

FWIW,

- Carl Anderson
WTP Build guy



From:Victor V. Rubezhny vrubez...@exadel.com
To:Max Rydahl Andersen max.ander...@redhat.com, Mickael Istria
 mist...@redhat.com
Cc:gorkem.er...@gmail.com, external-exadel-l...@redhat.com
 external-exadel-l...@redhat.com, General discussion of
 project-wide or architectural issues. wtp-dev@eclipse.org
Date:03/16/2015 09:44 AM
Subject:Re: [wtp-dev] The Bower IDE contribution
Sent by:wtp-dev-boun...@eclipse.org



Max, Mickael,

actually we have all the required dependencies since the following
issues were fixed:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=457483 - Move JGit and
EGit to offset+1 on release train
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=458521 - Add JGit/EGit
as a dependency of WTP

I think it's a good proposal to merge the current Bower IDE into master,
but I don't get how I can make it go into the build and not include it
into JSDT/JSDT_SDK features at the same time: If I'm not including the
plug-ins, will they be built still and added into the update site?

Today I'm testing the fixes provided by Stephane for the following 
issues:

- https://bugs.eclipse.org/bugs/show_bug.cgi?id=462110 - [bower]
Install/Update commands don't follow the NPM Node SemVer rules
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=462108 - [bower]
Install/Update command block the UI, no way to cancel the operation
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=462117 - [bower]
JsonSyntaxException exception occurs in Bower IDE while installing
angular dependency

If we've got these issues fixed, we could get something like a preview
for the contribution:

- anyway, we cannot get 'slow install' in time (it hardly depends on
upstream JGit issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=301628
-BasePackFetchConnection: implement shallow support)

- Probably we can get at least a partial fix for 'registry' property in
.bowerrc file (https://bugs.eclipse.org/bugs/show_bug.cgi?id=462112 -
[bower] The Bower Preference page is to be replaced by the support of
.bowerrc file)

- Also, for sure we can hide the Bower-Update command (which currently
does just Clean + Install, so in conjunction with the slowness of
Install operation has no sense to keep it at the moment.

As such, we're getting a preview-version with two big issue
(Install/update slowness + JSDT (including 3rd party products that
depends on it, like Tern.java and VJET) starts to get slow when too many
files are installed' according to bower.json configuration. See:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=462115 - [bower] Do we
need to exclude dependencies installed by bower from the JSDT Include 
Path?

- https://issues.jboss.org/browse/JBIDE-19448 - (JBIDE-19448)
Performance problems with angular-phonecat project

Any thoughts?

Thanks in advance,
Victor

On 03/16/2015 04:11 PM, Max Rydahl Andersen wrote:

On 16 Mar 2015, at 9:30, Mickael Istria wrote:


Hi Victor, hi all,

I  don't get how this contribution can have blockers that make it
worth being on a separate branch. Indeed, the bower integration may
not yet be ready to be delivered as part of a release, but since it's
a set of separate plugins, I would find it more convenient to put
this directly on master, to build it together with the regular JSDT,
but to mark it as Incubating, with version 0.0.1. However, it should
remain out of the main feature (the one we ship to Release Train)
until to becomes more stable.
I believe this approach would bring more additional testers and
contributors on this Bower integration and would help a lot to reach
high quality faster.

WDYT

Re: [wtp-dev] WTP 3.6.3 not yet published on the downloads page...

2015-03-03 Thread Victor V. Rubezhny


Carl,

regarding of Bug# 461160... What should I do to initiate the procedure 
of creating such a patch?


Thanks in Advance,
Victor

On 03/02/2015 11:30 PM, Carl Anderson wrote:


Konstantin,

Oops- I sent out the e-mail with the link, but forgot to unhide it. 
 It is shown now.  The direct link is 
http://download.eclipse.org/webtools/downloads/drops/R3.6.3/R-3.6.3-20150216091848/ . 
 (And note that 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160 may cause a 
public patch to be made.)


FWIW,

- Carl Anderson
WTP Build guy

Inactive hide details for Konstantin Komissarchik ---03/02/2015 
02:27:31 
PM---http://download.eclipse.org/webtools/downloads/Konstantin 
Komissarchik ---03/02/2015 02:27:31 
PM---http://download.eclipse.org/webtools/downloads/


From: Konstantin Komissarchik konstantin.komissarc...@oracle.com
To: 'General discussion of project-wide or architectural issues.' 
wtp-dev@eclipse.org

Date: 03/02/2015 02:27 PM
Subject: [wtp-dev] WTP 3.6.3 not yet published on the downloads page...
Sent by: wtp-dev-boun...@eclipse.org





_http://download.eclipse.org/webtools/downloads/_
___
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

59 matches

Mail list logo