[
http://issues.apache.org/jira/browse/AXIS-1835?page=comments#action_60887 ]
Jeff Liu commented on AXIS-1835:
--------------------------------
I assembled the update site using Eclipse, so it was not an automated process.
I've also posted this question to the Eclipse update/install team... There's an
automated (but unsupported) way of creating an update site from
features/plugins. However, AFAIK, there's no automated way of creating a
feature/plugin from a set of jars (ex. axis-1_1.zip). So, just to throw in a
picture here, here's what (I think) the Axis update site is going to look like:
Axis update site
|_ Axis 1.1 feature
|_ Axis 1.1 plugin
|_ Axis 1.2 feature
|_ Axis 1.2 plugin
...
As long as you have the features/plugins, you can automate the creation of the
update site, but that requires you to have the features/plugins to begin with.
And there's no automated process for creating that, mainly because the
descriptor files (plugin.xml) for Axis 1.1, 1.2, etc are likely going to be
different.
Personally, I think this is ok because features/plugins to me are like source
code. We check them into the CVS system, and they will be different from
version to version. So when Axis cuts a new version of Axis, we'll create a new
feature/plugin for it. Oh, btw, you'll probably ask why a new feature/plugin
for each version of Axis. The plans that we have in the Eclipse Web Tools
Platform project is to provide tooling for Axis 1.1, 1.2... That's why we need
to put them into seperate plugins.
Comments/Suggestions?
> Create an Eclipse update manager site for Axis
> ----------------------------------------------
>
> Key: AXIS-1835
> URL: http://issues.apache.org/jira/browse/AXIS-1835
> Project: Axis
> Type: New Feature
> Reporter: Jeff Liu
> Priority: Minor
>
> I work on the Eclipse Web Tools Platform Project (WTP). One of the features
> included in WTP is the ability to generate a Web service that targets Axis.
> Obviously, in order to do that, a user would need to "install" Axis into WTP.
> The install steps are not easy, in fact, they are quite painful... What would
> be nice is if we can host an Eclipse update manager site on the Axis Web
> site, so that users can just point to the URL and Axis will be installed
> automatically. I'll be interested in contributing this piece of the work. Any
> comments/suggestions?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
