Hi Lenya Devs,
following the discussion about maven and ant I think that everybody
agrees that maven shouldn't be a feature of the next release.
So I would suggest the following for the 2.1 release.
1) No java 1.4 support.. java 1.5 or 1.6 is required. (I tried 1.7
but it didn't work).
2) Bug fixing.
3) if required: replacement of the binaries (iibs), but I think this
will take time.
4) All other feature should be done later.
WDYT ?
Does anybody know if 3) is necessary ?
Best
Rudolf
Am 02.02.2013 um 22:56 schrieb Gerd Schrick:
Dear Lenya Devs,
sorry for the maybe 'stupid' question, but why not stay with Ant?
(The following is just MY opinion based on MY experiences with Ant.
I've no serious experiences with other build environements, so it's
not meant to be a comparison.)
As you know, we're heavily working with Lenya since years and Ant is
doing a really great job.
We had a project where we tried to integrate/create the build
process in Maven, what was an unsuccessfull PITA ;-)
IMO Ant is very complex, powerfull and flexible(!) but still easy to
understand if someone tries to get into it.
First use was the Lenya build but meanwhile we use it for additional
tasks:
A)
complex xml content-cleanup and preprocessing/preparing for import
in Lenya (many 100 files in one bunch and it's really fast)
B)
with very little changes in the Lenya build/run scripts it's
possible to create (really easy!) different builds (pubs and
modules) from one codebase. These independant builds reside in
different directories and with the run script I can quickly select
what build to start (using the builtin Jetty). This is extremely
helpfull as I'm developing for different customers.
C)
last but not least a "distribute" script/build. Based on a given
build the necessary files are collected and some adjustments are
made so that this copy of the build fits for the destination
environment.
Our usecase:
1 Build and testing is done on our testserver with all pubs in it
and no proxy nor mail server.
2 the 3 production servers should use the same build but with a
different set of pubs each and
3 the proxy settings (within the publication) are partly different
as well as the notification (mail) and database (datasource) settings
First we used shell scripts for it. But job 3 was really hard. With
Ant it's easy (and fast).
Kind regards,
Gerd
Richard Frovarp <rfrov...@apache.org> hat am 28. Januar 2013 um
20:20 geschrieben:
> On 01/28/2013 04:00 AM, Andreas Hartmann wrote:
> > Am 27.01.13 14:15, schrieb Rudolf Korhummel:
> >> Hi Lenya Devs,
> >>
> >> Does it mean that we have to remove all binary libraries before
we can
> >> do the new release ?
> >> If yes: Would it be good to use maven instead of ant ?
> >
> > This shouldn't be necessary, we could as well use Ivy (which can
access
> > Maven repositories) for dependency management.
> >
> > Having worked with Maven for a couple of years now, I'm not a
particular
> > fan of it. The syntax is overly verbose, some concepts are very
complex
> > (e.g. profiles) and the build process is very restrictive.
> >
> > I don't think it is necessary or particularly beneficial to move
away
> > from Ant for the existing codebase. If we decide to do this,
though, we
> > might want to take a look at Gradle and maybe Buildr (Gradle
seems to be
> > more stable, Buildr otoh is an Apache project).
> >
> > -- Andreas
> >
>
> Ivy certainly could do it. Gradle can integrate the ant tasks
right in,
> which is what would make it an attractive option.
>
> I am a fan of Maven, but I'm only using it for simple builds. The
more
> complex the build, the less appealing it becomes.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org
> For additional commands, e-mail: dev-h...@lenya.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org
For additional commands, e-mail: dev-h...@lenya.apache.org
