Hi Milen
Can you share a minimal project to help us reproduce the issue ?
If you could zip it and attach it to a new JIRA, that would be great.
Thanks
--
Guillaume Sauthier (OW2)
Sent with Airmail
On 22 Sep 2014 at 08:27:12, Clement Escoffier (clement.escoff...@gmail.com)
wrote:
Hi,
I can but most likely not before next week.
Thanks
On Mon, Sep 29, 2014 at 1:00 AM, Guillaume Sauthier (OW2)
guillaume@gmail.com wrote:
Hi Milen
Can you share a minimal project to help us reproduce the issue ?
If you could zip it and attach it to a new JIRA, that would be great.
Hi,
Sorry for the late reply (should never change my email program).
So, it should not be the case. As soon as the stereotype is available in the
manipulator class path, it should be used. Obviously, if it’s in the bundle,
it’s necessarily in the class path. Could you open an issue, it’s
OK, my bad, I asked the question poorly.
It of course works with private-package as well (I just used the export in
my simple test).
What I intended to ask was, why the stereotype class needs to be included
in the bundle using it? In another words - isn't it enough that the bundle
imports the
OK, found the problem. It's due to how Export-Package of
the maven-bundle-plugin is configured.
Here is an example:
- I have stereotype maven project where I define a @Stereotype as
*test.ipojo.stereotype*.MyComponent
- The bundle maven project where I try to use the stereotype has its
classes
Hi,
Could you check that the stereotype class is actually included in the jar file
when not exported ? Maybe the ‘private-package’ instruction contains the error.
Cheers,
Clement
On 15 septembre 2014 at 15:05:17, Milen Dyankov (milendyan...@gmail.com) wrote:
OK, found the problem. It's due
Hi,
Stereotypes are analyzed at build time, not at runtime. So they are packaged in
regular jars. To work as expected, the stereotype need to be available from the
‘manipulator’ engine, in other words: be in the same class path.
So, if you are using Maven, you can do as follows:
plugin
Hi,
Is the usage of a @Stereotype annotated annotation from another bundle
supported? It doesn't seem to work even though the package is properly
exported and imported.
The docs only say:
If the stereotyped annotation is directly in the manipulated module, no
problems: any front-end will work
8 matches
Mail list logo