On 08.04.2020 15:58, Oliver Lietz wrote:
On Wednesday, April 8, 2020 1:42:17 PM CEST JCR wrote:
On 07.04.20 12:06, Bertrand Delacretaz wrote:
Hi,
Hi,
On Tue, Apr 7, 2020 at 11:37 AM JCR wrote:
...But what I
observe is, that MANIFEST.MF gets overriden on every change and even
On Wednesday, April 8, 2020 1:42:17 PM CEST JCR wrote:
> On 07.04.20 12:06, Bertrand Delacretaz wrote:
> > Hi,
Hi,
> > On Tue, Apr 7, 2020 at 11:37 AM JCR wrote:
> >> ...But what I
> >> observe is, that MANIFEST.MF gets overriden on every change and even
> >> package-info is present, the
Hi Juerg,
On Wed, Apr 8, 2020 at 1:42 PM JCR wrote:
> ...So this is the secret sauce that does the job. That needs to be added to
> the project's pom.xml...
Ok, glad you found out and sorry if our (lack of) examples made your
life harder than it should be!
-Bertrand
On 07.04.20 12:06, Bertrand Delacretaz wrote:
Hi,
On Tue, Apr 7, 2020 at 11:37 AM JCR wrote:
...But what I
observe is, that MANIFEST.MF gets overriden on every change and even
package-info is present, the package in there gets set back to to private...
It looks like your build setup is
Hi,
On Tue, Apr 7, 2020 at 11:37 AM JCR wrote:
> ...But what I
> observe is, that MANIFEST.MF gets overriden on every change and even
> package-info is present, the package in there gets set back to to private...
It looks like your build setup is causing trouble.
I recommend that you compare
On 30.03.20 16:18, JCR wrote:
On Sunday, March 29, 2020 5:14:48 PM CEST JCR wrote:
Am Sa., 28. März 2020 um 20:55 Uhr schrieb JCR :
Hello
Hi Juerg,
I wrote a very simple POJO, built it as OSGi bundle and deployed
it to
Sling11. Here's the source:
package rome.testly.testly1;
import
On Sunday, March 29, 2020 5:14:48 PM CEST JCR wrote:
Am Sa., 28. März 2020 um 20:55 Uhr schrieb JCR :
Hello
Hi Juerg,
I wrote a very simple POJO, built it as OSGi bundle and deployed it to
Sling11. Here's the source:
package rome.testly.testly1;
import
On Sunday, March 29, 2020 5:14:48 PM CEST JCR wrote:
> > Am Sa., 28. März 2020 um 20:55 Uhr schrieb JCR :
> >> Hello
Hi Juerg,
> >> I wrote a very simple POJO, built it as OSGi bundle and deployed it to
> >> Sling11. Here's the source:
> >>
> >> package rome.testly.testly1;
> >> import
Hi Jürg
Hi Jörg
>
> The class is declared as @Component (see above). Do I need any other
> declaration to make the export happen?
>
>
>
You need to have the package name appear in the "exported packages" section
of the bundle. The maven bundle plugin has some heuristics for reasonable
defaults.
Am Sa., 28. März 2020 um 20:55 Uhr schrieb JCR :
Hello
I wrote a very simple POJO, built it as OSGi bundle and deployed it to
Sling11. Here's the source:
package rome.testly.testly1;
import org.osgi.service.component.annotations.Component;
@Component(service=SlingFutil.class )
public
Hi Juerg,
Looks like your bundle does not export that class, so it's not available
outside of that bundle.
Jörg
Am Sa., 28. März 2020 um 20:55 Uhr schrieb JCR :
> Hello
>
> I wrote a very simple POJO, built it as OSGi bundle and deployed it to
> Sling11. Here's the source:
>
> package
Hello
I wrote a very simple POJO, built it as OSGi bundle and deployed it to
Sling11. Here's the source:
package rome.testly.testly1;
import org.osgi.service.component.annotations.Component;
@Component(service=SlingFutil.class )
public class SlingFutil {
public String nonsense() {
12 matches
Mail list logo
