Hi Kolja, Hi Guys,
> Exactly. Maybe the first button on the SourceForge.net download page
> should be a link to the files for JabRef 2.2 advertised as 'latest
> stable version'
> followed by a link to the files for JabRef 2.3 beta 2 advertised as
> 'current beta version'. Can we do this?
My
On 11/09/2007, Kolja Brix <[EMAIL PROTECTED]> wrote:
> Dear Morten!
>
> > The current version of JabRef is 2.2, and it requires Java 1.4.2. The
> > current beta version requires version 1.5, but I would rather
> > recommend 1.6.
> Yes, ok. Why exactly do we need version 1.5 or higher in the beta ve
On 10/09/2007, Christopher Oezbek <[EMAIL PROTECTED]> wrote:
> > We should include this check already in the 2.3
> > version, since it requires Java 1.5.
>
> Sure! You only need the class JabRefMain from net.sf.jabref and the
> modified compile target in the build.xml.
> Running from the Jar should
2007/9/11, Morten Omholt Alver <[EMAIL PROTECTED]>:
> > > Our biggest problem is perhaps that users download 2.3 beta without
> > > realizing that it is a beta version.
> > Exactly. Maybe the first button on the SourceForge.net download page should
> > be
> > a link to the files for JabRef 2.2 adv
Dear Jabref developers,
> Perhaps we should do as Christopher suggests, and add prominent
> "Download stable version" and "Download beta version" links on the top
> of the main page.
a few moments ago, I added two download buttons to the main webpage. I hope
you like the design.
--
Bye,
Kolj
