Contribute lsp4xml to the Eclipse foundation

[mickaelistria]

Is this intended to become an Eclipse.org project? I see recent change from @fbricon seem to move away from eclipse namespace, does it mean anything on that matter?
Having it an Eclipse project would allow other bricks at Eclipse.org (Eclipse IDE, Eclipse Theia, Eclipse Che...) to just include the project without any IP review/approval.

[angelozerr]

+1 for that @mickaelistria

@fbricon @NikolasKomonen what do you think to move lsp4xml to Eclipse?

Is there some guys who could do that?

[fbricon]

Yes, that's the plan. Should happen before the summer. Right now I need to own the groupid to be able to publish to bintray

[mickaelistria]

Ok, thanks for the confirmation. Do you want me to close the ticket or do you want to keep it for the future ?

[mickaelistria]

By the way, the current state is not too annoying: since all files have proper EPL headers, code automatically passes the Type A CQ validation at Eclipse, and it's a matter of hours between the request and the approval.

[angelozerr]

@mickaelistria I'm working on the proposal https://docs.google.com/document/d/1iihjjULgOd4Wel5QRuPoeJ1eVTppKfVLTo5skLm3gQU/edit?usp=sharing

As some files are copy/paste of TypeScript code from https://github.com/microsoft/vscode-html-languageservice I need to update header file with this information

[fbricon]

@martinlippert ok to reference Pivotal as an interested party in the above proposal?
@dhuebner same question concerning Typefox

[martinlippert]

@fbricon sure

[angelozerr]

@fbricon could we change the millestone please for the next sprint?

[mickaelistria]

could we change the millestone please for the next spring?

I hope you mean sprint, it'd be a pity to wait 9 months ;)

[angelozerr]

I hope you mean sprint, it'd be a pity to wait 9 months ;)

Oooops, thanks @mickaelistria to fix my error. Our spring will finish in one week. I will do that after

[mickaelistria]

What's the status here? We'd like to more easily consume latest LSP4XML release in Wild Web Developer, and doing it costs us extra effort as long a project is not at Eclipse.org.

[angelozerr]

We will take care of this issue as soon as @fbricon will be available (he should be available next week). But if you wish to support LSP4XML inside Wil Web Developer we should take care of:

• supporting settings for LSP4XML. For instance 0.8.0 provides CodeLens which is disable by default
• fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=548610 because Codelens is called before didOpen and it is disabled after that in LSP4e

[fbricon]

@Seiphon can we list Liferay to the interested parties in https://docs.google.com/document/d/1iihjjULgOd4Wel5QRuPoeJ1eVTppKfVLTo5skLm3gQU/edit?usp=sharing?

It's about time we move forward with the contribution to the EF, if @nitind is still ok to mentor the process.

cc @waynebeaton

[angelozerr]

@gamerson I think you could be interested with this issue (see below comments)

[gamerson]

We are indeed interested! Happy to see this process moving forward.

…

On Fri, Oct 25, 2019 at 5:28 AM Angelo ***@***.***> wrote: @gamerson <https://github.com/gamerson> I think you could be interested with this issue (see below comments) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#283>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAERKFNAJRBZYDFOHTTBZ23QQLC45ANCNFSM4GQ66JIA> .

-- Greg Amerson Liferay Developer Tools Liferay, Inc. www.liferay.com

[jtydhr88]

hey @fbricon @angelozerr @gamerson
@Seiphon already added Liferay into the interested parties.

[fbricon]

Contribution is done https://projects.eclipse.org/projects/technology.lemminx
Github repo was transferred to https://github.com/eclipse/lemminx/
CI: http://download.eclipse.org/lemminx

Until we complete setting up proper Maven repo publishing, snapshots are pushed to https://download.eclipse.org/lemminx/snapshots/

[mickaelistria]

Congrats and thanks!