Why do I need to specify the maven-ipojo-plugin in my pom files? #276

Closed
evrignaud opened this Issue Jul 15, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@evrignaud

I'm using Wisdom and the wisdom-maven-plugin and I don't get clearly why I should explicitly specify that I want to use the maven-ipojo-plugin.
I understand that technically iPojo is behind and his a corner stone.
But why the iPojo bundle manipulation can't be done when activating the wisdom-maven-plugin, because using Wisdom implies necessarily using iPojo.
Sure we still need in some case to be able to specify some iPojo specific configuration, but the defaults should allow to only use the wisdom-maven-plugin.

@cescoffier

This comment has been minimized.

Show comment
Hide comment
@cescoffier

cescoffier Jul 16, 2014

Member

Are you using the wisdom packaging ?

On 15 juil. 2014, at 22:50, evrignaud notifications@github.com wrote:

I'm using Wisdom and the wisdom-maven-plugin and I don't get clearly why I
should explicitly specify that I want to use the maven-ipojo-plugin.
I understand that technically iPojo is behind and his a corner stone.
But why the iPojo bundle manipulation can't be done when activating the
wisdom-maven-plugin, because using Wisdom implies necessarily using iPojo.
Sure we still need in some case to be able to specify some iPojo specific
configuration, but the defaults should allow to only use the
wisdom-maven-plugin.


Reply to this email directly or view it on GitHub
#276.

Member

cescoffier commented Jul 16, 2014

Are you using the wisdom packaging ?

On 15 juil. 2014, at 22:50, evrignaud notifications@github.com wrote:

I'm using Wisdom and the wisdom-maven-plugin and I don't get clearly why I
should explicitly specify that I want to use the maven-ipojo-plugin.
I understand that technically iPojo is behind and his a corner stone.
But why the iPojo bundle manipulation can't be done when activating the
wisdom-maven-plugin, because using Wisdom implies necessarily using iPojo.
Sure we still need in some case to be able to specify some iPojo specific
configuration, but the defaults should allow to only use the
wisdom-maven-plugin.


Reply to this email directly or view it on GitHub
#276.

@cescoffier

This comment has been minimized.

Show comment
Hide comment
@cescoffier

cescoffier Jul 16, 2014

Member

So, just to detail a bit my last reply (because on the iPHONE it's not really great to comment on issues).

If you are using the wisdom packaging, you don't need to declare the maven-ipojo-plugin:

<packaging>wisdom</packaging>

This requires to have the wisdom-maven-plugin configured in your pom file with <extensions>true</extensions>.

In that case you don't need the iPOJO plugin because the iPOJO manipulator is automatically executed on the output bundle (the manipulator is used directly, not the maven plugin).

Member

cescoffier commented Jul 16, 2014

So, just to detail a bit my last reply (because on the iPHONE it's not really great to comment on issues).

If you are using the wisdom packaging, you don't need to declare the maven-ipojo-plugin:

<packaging>wisdom</packaging>

This requires to have the wisdom-maven-plugin configured in your pom file with <extensions>true</extensions>.

In that case you don't need the iPOJO plugin because the iPOJO manipulator is automatically executed on the output bundle (the manipulator is used directly, not the maven plugin).

@cescoffier cescoffier added the question label Jul 16, 2014

@evrignaud

This comment has been minimized.

Show comment
Hide comment
@evrignaud

evrignaud Jul 17, 2014

Hi,

Thanks for the clarification. In fact I use my own packaging that's using my own "component" system.
But I have noticed that in fact with the wisdom packaging only the wisdom plugin is required.
Good to see that Wisdom comes by default with a very good behavior.

Hi,

Thanks for the clarification. In fact I use my own packaging that's using my own "component" system.
But I have noticed that in fact with the wisdom packaging only the wisdom plugin is required.
Good to see that Wisdom comes by default with a very good behavior.

@evrignaud evrignaud closed this Jul 17, 2014

@cescoffier cescoffier added this to the 0.6.2 milestone Jul 25, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment