Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [Dltk-dev] JavaScript module


On Wed, Apr 26, 2017 at 12:10 PM, Kaloyan Raev <kaloyan.r@xxxxxxxx> wrote:
It does not need to be like this. We can have different builds for Photon milestones (DLTK 6.0) and Oxygen updates (DLTK 5.7.x, 5.8.x, etc.)

Somehow, I didn't consider this as an option with the current manpower at all.
 

However, I agree that if you want to have DLTK 6.0 now for Oxygen, it is still possible. It would be best if the narrow time window left is used for other clean up activities.

I believe we should hear from the project lead on that one. And if we go for 6.0 - stop buidling the python module too (it can always can be added back if/when it becomes usable). By stopping to build these two we can drop the dependency of the very old antlr these two depend on and have a build with single Orbit repo we depend on , after seeing Neon.3 issues I believe every project has to be more proactive on this.

Another idea that flows in my head - if we do 6.0 what about making it require Oxygen as min version directly? That allow easily experimenting/using lsp4e, generic editor and other goodies. Just a thought. ;)
 


On 04/26/2017 11:55 AM, akurtakov wrote:


On Wed, Apr 26, 2017 at 11:50 AM, Kaloyan Raev <kaloyan.r@xxxxxxxx> wrote:
I don't understand your last statement.

The Oxygen development is open since July 2016. So far there haven't been any significant changes done that required having separate Oxygen and Neon.X branches.

I suggest that we plan a DLTK 6.0 release for Photon. We can use this opportunity for other cleanup activities.

I mean if we do 6.0 for Photon it would be April(late March?) next year when we will have cut the last 5.x release  giving us exactly the same amount of time for such changes.
 



On 04/26/2017 11:42 AM, akurtakov wrote:


On Wed, Apr 26, 2017 at 11:40 AM, akurtakov <akurtakov@xxxxxxxxx> wrote:


On Wed, Apr 26, 2017 at 11:31 AM, Kaloyan Raev <kaloyan.r@xxxxxxxx> wrote:
Yes, you are right - they are not on the release train. But they are still on the project's update site. And there might be adopters consuming them from there.

Any reason to push this change in a hurry for Oxygen?
Other than stop shipping not really functional modules - no.

Thinking more about - we have just opened development for Oxygen and next few releases will still support Neon so any potential 6.0 change would be next year and being done in a hurry for Photon? Or I'm missing some other change?
 
 



On 04/26/2017 11:01 AM, akurtakov wrote:


On Wed, Apr 26, 2017 at 10:52 AM, Kaloyan Raev <kaloyan.r@xxxxxxxx> wrote:
I am also not sure if there are any adopters of the DLTK _javascript_ and Python modules. Which does not mean there aren't any.

Note that these are not published to the release train [1]. So I would say chances are very very low, esp. considering how useful are they nowadays.
 

Removing them is a backward incompatible change, which should happen in a new major version - DLTK 6.0. I suggest that we plan this for the Photon release (June 2018).

If there is agreement for that it's not too late for Oxygen.

[1] http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/dltk.aggrcon
 

Kaloyan


On 04/26/2017 10:50 AM, Dawid Pakuła wrote:
+1

Personally, I think that in future dltk could be extension for LSP4E, as a provider of ast, indexing and other advanced stuff. But, for this have to support multiple language toolkits in same project.

-- 
Dawid Pakuła

On 26 April 2017 at 09:37:12, akurtakov (akurtakov@xxxxxxxxx) wrote:

Hi everyone,
_javascript_ ecosystem is moving quite fast, which can't be said for DLTK one. Even the WTP one is considered badly outdated now [1] and looking for new path. Should we just give up on _javascript_ module in DLTK and disable it from the build? I don't think anyone will join working on it especially with the current push about language servers and friends. WDYT?

P.S. I have similar thoughts about Python but this one could probably be reformed as language server based one, while the JS have definetely taken another path.
Regards,
Alex
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev


_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev
_______________________________________________ dltk-dev mailing list dltk-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dltk-dev 
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev
_______________________________________________ dltk-dev mailing list dltk-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dltk-dev 
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev
_______________________________________________ dltk-dev mailing list dltk-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dltk-dev 
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev

Back to the top