[
https://issues.apache.org/jira/browse/SLING-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-10429:
--------------------------------
Description: With the switch to using {{bnd.bnd}} in 4.2.18, the
sling.event bundle no longer contained the sling.event.api bundle. Downstream
javadoc generation failed to locate source files for the embedded
sling.event.api classes however. One way to fix, that I'm aware of, this is to
include the sling.event.api bundle in the jar again. (Another variant might be
to embed source files of the event-api.jar in event.jar..) (was: With the
switch to using {{bnd.bnd}} in 4.2.18, the sling.event bundle no longer
contained the sling.event.api bundle. Downstream javadoc generation failed to
locate source files for the embedded sling.event.api classes however. One way
to fix, that I'm aware of, this is to include the sling.event.api bundle in the
jar again.)
> Include api jar in sling.event for correct javadoc generation
> -------------------------------------------------------------
>
> Key: SLING-10429
> URL: https://issues.apache.org/jira/browse/SLING-10429
> Project: Sling
> Issue Type: Task
> Components: Event
> Affects Versions: Event 4.2.18
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Major
> Fix For: Event 4.2.20
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the switch to using {{bnd.bnd}} in 4.2.18, the sling.event bundle no
> longer contained the sling.event.api bundle. Downstream javadoc generation
> failed to locate source files for the embedded sling.event.api classes
> however. One way to fix, that I'm aware of, this is to include the
> sling.event.api bundle in the jar again. (Another variant might be to embed
> source files of the event-api.jar in event.jar..)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
