You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Gilles Scokart <gs...@gmail.com> on 2008/05/27 10:03:14 UTC
Setting up Eclipse update site [Was Re: Releasing IvyDE]
Geronimo use the dist directory [1], UIMA use also their distribution
directory [2], Maven host it on codehaus [3], Harmony use their
web-site [4], and as Xavier said, Apache Directory also use their web
site [5].
If it is technically possible, I guess using the mirrored dist
directory is better. We should may be check that with infrastructure.
I tried to search the archives, but it seems that I don't have the
required karma (or that I didn't look at the right place).
[1] http://geronimo.apache.org/geronimo-eclipse-plugin-installation-instructions.html
[2] https://issues.apache.org/jira/browse/UIMA-659
[3] http://markmail.org/message/ipgrfz725czfzhkg
[4] http://markmail.org/message/ybqoy5emzdfjoxlr
[5] http://directory.apache.org/studio/update/1.x/
2008/5/26 Nicolas Lalevée <ni...@anyware-tech.com>:
> Le mardi 20 mai 2008, Gilles Scokart a écrit :
>> I didn't use IvyDE, but I'm +1 for an alpha or beta release seeing
>> that recent bug reports starts to be reported against "The latest
>> build (May 16 from www.hibnet.org)" [1] or from xoocode [2].
>>
>> [1] https://issues.apache.org/jira/browse/IVYDE-93
>> [2] https://issues.apache.org/jira/browse/IVYDE-90
>>
>> 2008/5/19 Maarten Coene <ma...@yahoo.com>:
>> > +1 for an IvyDE release.
>> > I'd prefer a beta release instead of an alpha release though...
>> >
>
> As there is no objection since last week, let's go for an IvyDE release !
>
> As suggested by Xavier, I vonlonteer to be the release manager.
>
> Marteen raised a question about the name of the release. For me, "alpha"
> means "release that developers know it to be unstable" and "beta" is
> for "developers think it has minor bugs but is stable, then let's the users
> test it".
> For me it is unstable, mainly due to IVYDE-82 and currently I saw that
> IVYDE-54 can freaks out Eclipse.
> So I vote for "alpha".
>
> Then about the release, in order to follow the Apache guidelines, some work
> need to be done about packaging the source of IvyDE. I will look about how
> the sources are usually packaged for the Eclipse plugins. We should probably
> have different kind of packaging: the source got from an updatesite, and the
> full sources which also contains the build system.
>
> We will also probably need an Apache Ivy updatsite. For the few tests I have
> done with my own one, it is not working properly, updates are not detected...
> Some investigation will be needed here too.
>
> About the documentation, I have finished migrating the IvyDE website, so now
> there is the "history" category, like the Ivy site. I think we should publish
> it as soon as we get an IvyDE release adopted. WDYT ?
>
> And the documentation in the binary distribution. Could a simple link to the
> website be enought ? Or should we push the html doc into the zip ?
>
> In the Apache doc, I can read:
>> If svn:externals is used, check carefully that a tag is referenced. This
> ensure that all the source for the release is fixed. If the target of a
> svn:externals changes then the release will no longer be complete
> reproducible.
> So shouldn't xooki be released somehow ?
>
> Does anybody see any other points that need to be addressed before starting to
> build a release ?
>
> Nicolas
>
>
>> >
>> > ----- Original Message ----
>> > From: Xavier Hanin <xa...@gmail.com>
>> > To: Ant Developers List <de...@ant.apache.org>
>> > Sent: Monday, May 19, 2008 6:19:40 PM
>> > Subject: Re: Releasing IvyDE
>> >
>> > On Mon, May 19, 2008 at 4:49 PM, Nicolas Lalevée
>> > <ni...@joost.com>
>> >
>> > wrote:
>> >> Hi,
>> >>
>> >> Recently there were some users complaining that there is no release of
>> >> IvyDE
>> >> compatible with Ivy 2. [1] [2]
>> >>
>> >> I know that IvyDE is not stable. See some major issues in Jira. For some
>> >> people it is even getting less stable: [3]
>> >>
>> >> But then I wonder if we could still do an alpha release, just to get
>> >> people less annoyed by the 1.2 version which has some terrible issues
>> >> [2], and probably more bug report, and hopefully more people interested
>> >> in contributing.
>> >>
>> >> WDYT ?
>> >
>> > I'm a strong +1 to get an alpha release of IvyDE out. I don't have much
>> > time currently though, but according to the high quality of the job
>> > you've done so far on IvyDE and its build system, I'm confident you are
>> > able to be the release manager for this version if you want.
>> >
>> > Xavier
>> >
>> >> Nicolas
>> >>
>> >> [1]
>> >>
>> >> http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200805.mbox/%3cB03
>> >>D774CEAF17944B6FEEAF04021E2354BE5C2E054@LNWEXMBX0104.msad.ms.com%3e [2]
>> >> https://issues.apache.org/jira/browse/IVYDE-65
>> >> [3]
>> >>
>> >> http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200805.mbox/%3cDA8
>> >>40B295A060446A405B65CCDBC0776E55CD9@ofgesrv20.int.ofac.ch%3e
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> >> For additional commands, e-mail: dev-help@ant.apache.org
>> >
>> > --
>> > Xavier Hanin - Independent Java Consultant
>> > http://xhab.blogspot.com/
>> > http://ant.apache.org/ivy/
>> > http://www.xoocode.org/
>> >
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> > For additional commands, e-mail: dev-help@ant.apache.org
>
>
>
> --
> Nicolas LALEVÉE
> ANYWARE TECHNOLOGIES
> Tel : +33 (0)5 61 00 52 90
> Fax : +33 (0)5 61 00 51 46
> http://www.anyware-tech.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Gilles Scokart
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
AW: Setting up Eclipse update site
Posted by Ja...@rzf.fin-nrw.de.
> > Geronimo use the dist directory [1], UIMA use also their
> > distribution directory [2], Maven host it on codehaus [3], Harmony
> > use their web-site [4], and as Xavier said, Apache Directory also
> > use their web site [5].
> >
> > If it is technically possible, I guess using the mirrored dist
> > directory is better.
>
> Please forgive this old Emacs user's ignorance, but I have no idea
> what an Eclipse update site is.
>
> If it holds files we'd want to distribute it should go into the dist
> directory, this is where our distributions live and it has the benefit
> of being automatically archived at archive.apache.org.
Eclipse has the feature to directly load "updates" and enhancements from
remote locations. So could
- download a "simple" Eclipse from eclipse.org
- start that
- add a new "update site" (IvyDE Update Site =
http://somewhere.apache.org/somewhere )
- select "new feature"
- Eclipse searches and finds IvyDE
- select IvyDE
- Eclipse downloads that and installs it
And after a restart of Eclipse you have it.
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Setting up Eclipse update site
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le jeudi 29 mai 2008, Stefan Bodewig a écrit :
> On Wed, 28 May 2008, Gilles Scokart <gs...@gmail.com> wrote:
> > There are a few thing to take into considerations :
> >
> > 1. An eclipse update site must provide a site map page [1] that has
> > to change when a new version come. 2. The site map give the
> > possibility to reference an other file that contains a list of
> > mirrors.
> >
> > So, we have to choose what we want to archive and mirror :
> > - The jars
> > - The site.xml
> > - The mirror file
> >
> > I guess that we should mirror the jars,
>
> absolutely.
>
> > but I'm not sure about the site.xml and the page that list the
> > mirrors.
>
> If we make the page that lists the mirrors a CGI on the site (just
> like the downloadpages) we might be fine.
>
> Will Eclipse use the mirrors of that list or is it a user choice? If
> it is a user choice then the main page should be a CGI as well and
> point to the mirrored jars so that Eclipse users would be forced to do
> something explicitly if they want to download the jars from
> apache.org.
I have found this interesting page:
http://incubator.apache.org/guides/releasing-eclipse-update-site.html
There even a link to a build.xml that create the files for the update site. I
didn't took time to look at it closely though.
By the way, I have found some other docs about releasing, licencing, mirroring
etc, in the "incubator" website. Does those docs are irrelevent for graduated
project ? Or I can rely on them (apart from the release vote process) ?
Nicolas, reading apache docs
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Setting up Eclipse update site
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 28 May 2008, Gilles Scokart <gs...@gmail.com> wrote:
> There are a few thing to take into considerations :
>
> 1. An eclipse update site must provide a site map page [1] that has
> to change when a new version come. 2. The site map give the
> possibility to reference an other file that contains a list of
> mirrors.
>
> So, we have to choose what we want to archive and mirror :
> - The jars
> - The site.xml
> - The mirror file
>
> I guess that we should mirror the jars,
absolutely.
> but I'm not sure about the site.xml and the page that list the
> mirrors.
If we make the page that lists the mirrors a CGI on the site (just
like the downloadpages) we might be fine.
Will Eclipse use the mirrors of that list or is it a user choice? If
it is a user choice then the main page should be a CGI as well and
point to the mirrored jars so that Eclipse users would be forced to do
something explicitly if they want to download the jars from
apache.org.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Setting up Eclipse update site
Posted by Gilles Scokart <gs...@gmail.com>.
There are a few thing to take into considerations :
1. An eclipse update site must provide a site map page [1] that has to
change when a new version come.
2. The site map give the possibility to reference an other file that
contains a list of mirrors.
So, we have to choose what we want to archive and mirror :
- The jars
- The site.xml
- The mirror file
I guess that we should mirror the jars, but I'm not sure about the
site.xml and the page that list the mirrors.
Note that in our case, there is an other 'page' to take into account :
the page on which we indicate where to find the update site. This
page must be on our web site, and could use a script similar to the
download page in order to point the user directly to one mirrored
update site (in that case, the site.xml would be mirrored as well)
Finally, we should maybe raise that question (probably again) about an
apache wide eclipse update site.
Do you have any preference /advice here before we bring the question
on the infrastructure list ?
[1] http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/update_sitemap.html
2008/5/28 Stefan Bodewig <bo...@apache.org>:
> On Tue, 27 May 2008, Gilles Scokart <gs...@gmail.com> wrote:
>
>> Geronimo use the dist directory [1], UIMA use also their
>> distribution directory [2], Maven host it on codehaus [3], Harmony
>> use their web-site [4], and as Xavier said, Apache Directory also
>> use their web site [5].
>>
>> If it is technically possible, I guess using the mirrored dist
>> directory is better.
>
> Please forgive this old Emacs user's ignorance, but I have no idea
> what an Eclipse update site is.
>
> If it holds files we'd want to distribute it should go into the dist
> directory, this is where our distributions live and it has the benefit
> of being automatically archived at archive.apache.org.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Gilles Scokart
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Setting up Eclipse update site
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 27 May 2008, Gilles Scokart <gs...@gmail.com> wrote:
> Geronimo use the dist directory [1], UIMA use also their
> distribution directory [2], Maven host it on codehaus [3], Harmony
> use their web-site [4], and as Xavier said, Apache Directory also
> use their web site [5].
>
> If it is technically possible, I guess using the mirrored dist
> directory is better.
Please forgive this old Emacs user's ignorance, but I have no idea
what an Eclipse update site is.
If it holds files we'd want to distribute it should go into the dist
directory, this is where our distributions live and it has the benefit
of being automatically archived at archive.apache.org.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org