Re: [wtp-dev] Initial development setup - p3

[Daniel Kasmeroglu]

Thanks for the hint. The inclusion of the SDK did the job.


Am 22.09.2016 um 09:25 schrieb Piotr Tomiak:

Daniel,

W dniu 22.09.2016 o 00:25, Daniel Kasmeroglu pisze:


1. The XML type 'enablement' is missing for the following XSDs:

* 
webtools.javaee/plugins/org.eclipse.jst.j2ee/schema/ClasspathDependencyExtension.exsd 



* 
webtools.javaee/plugins/org.eclipse.jst.j2ee/schema/archiveExportParticipants.exsd


This element is included in 'expressionLanguage.exsd' which is part 
of org.eclipse.core.expressions. However this plugin is declared as a 
dependency within the project org.eclipse.jst.j2ee, so I'm wondering 
whether any one has idea why Neon RCP is complaining here?


I think you need to ensure that in your target platform "Eclipse SDK" 
feature is present. Usually, when we have this problem, the SDK 
feature is missing.


Best regards,
Piotr Tomiak
___
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] Initial development setup - p3

[Piotr Tomiak]

Daniel,

W dniu 22.09.2016 o 00:25, Daniel Kasmeroglu pisze:


1. The XML type 'enablement' is missing for the following XSDs:

* 
webtools.javaee/plugins/org.eclipse.jst.j2ee/schema/ClasspathDependencyExtension.exsd 



* 
webtools.javaee/plugins/org.eclipse.jst.j2ee/schema/archiveExportParticipants.exsd


This element is included in 'expressionLanguage.exsd' which is part of 
org.eclipse.core.expressions. However this plugin is declared as a 
dependency within the project org.eclipse.jst.j2ee, so I'm wondering 
whether any one has idea why Neon RCP is complaining here?


I think you need to ensure that in your target platform "Eclipse SDK" 
feature is present. Usually, when we have this problem, the SDK feature 
is missing.


Best regards,
Piotr Tomiak
___
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] Initial development setup - p3

[Mickael Istria]

On 09/22/2016 12:25 AM, Daniel Kasmeroglu wrote:

2. Compiler Errors/Warnings

After the import of the projects there were plenty of errors. For 
instance: The plugin 'org.eclipse.jst.common.frameworks' has several 
unused imports which are currently configured as compiler errors (f.e. 
IJavaProjectLite). Why aren't these imports removed? I mean all those 
things that Eclipse detects automatically could be fixed very easily.
Is there any rationale behind this? And if not are there any 
objections when I would make the changes accordingly (of course only 
these automatically detected issues).

I imagine that this can be legacy code that no-one took time to clean up.
3. Are there any plans to switch to a completely maven based build, so 
we could drop these eclipse configuration files?

Which Eclipse configuration files? There are many of them!
What would be the value of dropping the Eclipse configuration files?
The build is already fully maven-based, it's using Tycho. If you want to 
be more Maven-centric, it's doable, but make sure you have the 
m2eclipse-tycho connector installed.
4.  Are there any plans to make an upgrade to Java 8? Where are 
potential obstacles if there are known ones?

As far as I know, no plan, no obstacle.
The only reason would be that this task doesn't get high priority and 
that the amount of contributors to WTP is a too low to consider doing 
"gardening" on the code. But feel free to contribute PRs for that, I 
believe they'd be welcome.


Cheers,
--
Mickael Istria
Eclipse developer for Red Hat Developers 
My blog  - My Tweets 

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

[wtp-dev] Initial development setup - p3

[Daniel Kasmeroglu]

It's me again ;-)

I'm using the 'master' branch now and imported the projects using the 
Eclipse way (didn't even occure to me 8-).


Still got the following questions:


1. The XML type 'enablement' is missing for the following XSDs:

* 
webtools.javaee/plugins/org.eclipse.jst.j2ee/schema/ClasspathDependencyExtension.exsd 



* 
webtools.javaee/plugins/org.eclipse.jst.j2ee/schema/archiveExportParticipants.exsd


This element is included in 'expressionLanguage.exsd' which is part of 
org.eclipse.core.expressions. However this plugin is declared as a 
dependency within the project org.eclipse.jst.j2ee, so I'm wondering 
whether any one has idea why Neon RCP is complaining here?



2. Compiler Errors/Warnings

After the import of the projects there were plenty of errors. For 
instance: The plugin 'org.eclipse.jst.common.frameworks' has several 
unused imports which are currently configured as compiler errors (f.e. 
IJavaProjectLite). Why aren't these imports removed? I mean all those 
things that Eclipse detects automatically could be fixed very easily.


Is there any rationale behind this? And if not are there any objections 
when I would make the changes accordingly (of course only these 
automatically detected issues).



3. Are there any plans to switch to a completely maven based build, so 
we could drop these eclipse configuration files?



4.  Are there any plans to make an upgrade to Java 8? Where are 
potential obstacles if there are known ones?



Best regards

Daniel Kasmeroglu



2.

___
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