On Wed, Jun 25, 2008 at 6:14 PM, Fabio Mancinelli < [EMAIL PROTECTED]> wrote:
> Dear all, > > the new version of XEclipse is almost ready and I am planning to > release it in a week. > In order to publish it through Eclipse's standard update mechanism I > need to put an "update site"[1] somewhere (see also > http://jira.xwiki.org/jira/browse/XECLIPSE-51) > . > > I thought about different scenarios: > > 1) Put the update site directly in the SVN (like > http://code.google.com/p/q4e/wiki/Installation) > 2) Put the update site on http://maven.xwiki.org/ > 3) Put the update site elsewhere. > What about somewhere on xwiki.org itself ? .... :) - Asiri > > I don't think 1) is a good idea because we would put the plugin jars > under version control, but it is nevertheless interesting because > "publishing" a new version will consist in doing a simple commit, > making the process more automatic and traceable[2] > > 2) is not a good idea because an update site has nothing to do with > maven. > > 3) is ok but I don't know where "elsewhere" could be. > > So the idea is to have two update sites, one for > "releases" (http://.../xeclipse/update) and one for snapshots > (http://.../xeclipse/update/dev) where to put in a XEclipse builds. I > know that this overlaps with the maven infrastructure, but this is > what Eclipse-oriented people expect (see > http://jira.xwiki.org/jira/browse/XECLIPSE-90) > > And probably 1) is a good solution. > > WDYT? > > -Fabio > > [1] An update site is simply a directory with a site.xml and all the > plugin jars, published on the web. > > [2] Side-note about update sites. As far as I know there is no way for > building them in an automatic way (unless a hackish, tricky, ant-based > way). The Maven PDE plugin doesn't support it, and the artifacts > generated by the maven build cannot be assembled together in an update > site (at least not without a lot of tricky steps I am not fully aware > of). So basically the safest way to generate an update site is to do > it in the IDE and "scp -r" the result to the target location. By > putting the update site in the SVN things would be easier, because > once the update site is generated, a commit would publish it directly. > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
