>>
>> IMHO it's not worth writing much stuff for mavenizing 2.1.x, this is
>> coming in 2.2, very close to being ready IIUC.
>>
It has already worked when ant and maven coexisted. Now it's in a kind of
stale state (priority is on the core, and blocks are no more constructed).
My app work with 2.2
Bertrand Delacretaz napisał(a):
Le 5 déc. 05, à 18:39, BURGHARD Éric a écrit :
...Because you already wrote all the patching stuff and because i
wrote a
groovyc plugin for maven that make the conversion of ant based build
process to maven plugins pretty easy, we could quickly have something
rea
g[R]eK napisał(a):
Can you wikify your experience somewhere, please? Fulfillment of my
dreams would be complete tutorial explaining how to play nice with
C2.1.8, Eclipse 3.1 and Maven2 assuming reader's experience with Maven2
is near zero :-)
However, any snatch of information also would be appre
Le 5 déc. 05, à 18:13, Jorg Heymans a écrit :
...Does bricks-cms run on 2.2 core ?
Haven't had time to try yet, but if it needs changes they should be
minimal, as there's little Cocoon-specific code in the app.
-Bertrand
smime.p7s
Description: S/MIME cryptographic signature
Bertrand Delacretaz wrote:
I think we must keep the existing bricks-cms as is as an example of
ant-based builds for 2.1.x, and create a separate Mavenized version - it
will be clearer than mixing up both things, and the application-specific
code is very small anyway, so duplication won't be
Le 5 déc. 05, à 18:39, BURGHARD Éric a écrit :
...Because you already wrote all the patching stuff and because i
wrote a
groovyc plugin for maven that make the conversion of ant based build
process to maven plugins pretty easy, we could quickly have something
really user-friendly without redesig
>
> It's not *one* jar, an important feature of the bricks-cms build is
> picking up required blocks, and compiling only those. Later, the build
> applies the required *.x* patch files to the Cocoon configs, as is
> currently required in 2.1.x. An alternate build must handle all of
> this, in addi
Le 5 déc. 05, à 15:41, BURGHARD Éric a écrit :
...Now to put the cocoon2.1.x jar into the apache m2 repository, there
is no
need of mavenize the whole process of cocoon...
It's not *one* jar, an important feature of the bricks-cms build is
picking up required blocks, and compiling only those
Bertrand Delacretaz wrote:
> I think we must keep the existing bricks-cms as is as an example of
> ant-based builds for 2.1.x, and create a separate Mavenized version -
> it will be clearer than mixing up both things, and the
> application-specific code is very small anyway, so duplication won't b
Le 5 déc. 05, à 13:27, g[[R]]eK a écrit :
...Fulfillment of my
dreams would be complete tutorial explaining how to play nice with
C2.1.8, Eclipse 3.1 and Maven2 assuming reader's experience with Maven2
is near zero :-)...
FWIW, I'd like to "port" the bricks-cms example app [1] to the Maven2
bu
BURGHARD Éric napisał(a):
Since a few week i'm just about to see the end of the tunnel thanks to maven
2 and its archetypes, and i'm full of hope again because it's simple and
clear. My application is now constructed by maven, all the jar, ant, jelly,
tools disappear from my repository. It just
11 matches
Mail list logo
