[
https://issues.apache.org/jira/browse/AXIS2-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088165#comment-13088165
]
Andreas Veithen commented on AXIS2-4937:
----------------------------------------
I think that this approach would introduce a bunch of new difficulties, but
there is another more fundamental question. IIRC the primary goal is not to
redesign the build of these plugins: the existing Felix based build works well
and once deployed, the plugins work well in Eclipse (at least there are no
issues caused by the way the plugins are built). The issue is with the
deployment in Eclipse and the original goal was to produce an Eclipse feature
and download site to make this easier. Now the question is: if we succeed in
creating an Eclipse feature and a download site that includes this "dependency
bundle" built with Felix, then one would expect that it should also be possible
to create these artifacts for the existing Felix built plugins, i.e. why would
one need Tycho at all to build the plugins?
> Creating Eclipse Features and a p2 Repository for Axis2 Eclipse IDE plugins
> ---------------------------------------------------------------------------
>
> Key: AXIS2-4937
> URL: https://issues.apache.org/jira/browse/AXIS2-4937
> Project: Axis2
> Issue Type: New Feature
> Components: ide plugins
> Affects Versions: 1.5.4
> Reporter: Harshana Eranga Martin
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: Axis2_4937_Eclipse_plugins.patch
>
>
> This jira will be used to track the progress of creating Eclipse Features and
> a p2 repository for Axis2 Eclipse IDE plugins.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
