[
https://issues.apache.org/jira/browse/SLING-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15625275#comment-15625275
]
Robert Munteanu commented on SLING-6208:
----------------------------------------
{quote}You can in fact restrict filter target files in Tycho (through a Maven
plugin configuration,
https://wiki.eclipse.org/Tycho/Target_Platform#Filtering). {quote}
That does not seem to help us here, as we need most of the target platform
identical, and then add:
- Eclipse Platform, for building
- Eclipse PDE, for dev
For the record, there is also option
4. Use the [Target Platform Definition DSL and
Generator|https://github.com/mbarbero/fr.obeo.releng.targetplatform], but it
seems overkill for our scenario ( see also SLING-3555 )
I've gone with 3. and created two target platform definitions, fixed in
[r1767485|https://svn.apache.org/r1767485]
> [dev] Extension point declaration for org.eclipse.ui.trace.traceComponents is
> marked as an error
> ------------------------------------------------------------------------------------------------
>
> Key: SLING-6208
> URL: https://issues.apache.org/jira/browse/SLING-6208
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Trivial
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> I am not sure when this started happening, but for me ( tried both Neon.1 and
> Mars.2 ) the extension point is marked as an error.
> The root cause seems to be that the extension point is provided by the
> {{org.eclipse.ui.trace}} bundle, which is not included in the target
> platform. In my local installation it's provided by the PDE feature, which
> means that we should include PDE in the target platform as well.
> I'd rather do this more fine-grained, but at the moment I don't see a simpler
> solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
