[
http://jira.codehaus.org/browse/MOJO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93554
]
Barrie Treloar commented on MOJO-739:
-------------------------------------
I don't have a lifecycle for fragments yet, not update sites. They hopefully
can reuse an existing lifecycle, or they can be extended later.
I was intending to turn feature into a jar.
My reasoning was I was hoping to also extend maven-eclipse-plugin to install
features as well into the maven repository.
I haven't done enough investigation to see whether I need to do anything more
than change the feature artifact from zip to jar.
(I think all it did was look for META_INF/MANIFEST.MF and look for an entry)
Is there a reason why zip is preferred for features?
I will ensure that there are integration tests (and tutorials) for a
multi-module build that tests all this.
> Create a new lifecycle instead of binding ontop of zip.
> -------------------------------------------------------
>
> Key: MOJO-739
> URL: http://jira.codehaus.org/browse/MOJO-739
> Project: Mojo
> Issue Type: Bug
> Components: pde
> Reporter: Barrie Treloar
>
> The pde plugin should probably bind to a new lifecylcle instead of re-using
> the zip one.
> Something like "pde".
> With MOJO-738 changing the artifact type to "jar" instead of "zip" for plugin
> builds, it makes sense to move away from the zip lifecycle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
