Sorry if you misunderstood my opinion on this matter. i only stand an
opinion that both methods may coexist peacefully on the same level.
you can eater build with ant or with maven. the only thing to take in
account is that with maven you don't need to worry with the libraries
which are kept in a
eal blocks are out before suggesting moving everything and
asking people to move with us.
- - Original Message -
From: "Nuno Santos" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 26, 2004 07:42
Subject: Re: [VOTE] - Move Cocoon to Maven
> I do beli
I do believe that both current build system and maven build system
with only a minor changes.
Is a fact that maven requires a standard directory ( which is not too
diferent from the one adopted for cocoon build system) but with a minor
change it can be done!
Don't forget that the maven build sys
Nicola Ken Barozzi wrote:
>
> Carsten Ziegeler wrote:
> ...
> > 3. The biggest advantage imho (and again this is my
> personal opinion -
> > others might differ of course) are the different reports
> you get for
> > free
>
> Sorry Carsten, but this is a bit ridiculous, given all the
> lines
Carsten Ziegeler wrote:
...
3. The biggest advantage imho (and again this is my personal opinion -
others
might differ of course) are the different reports you get for free
Sorry Carsten, but this is a bit ridiculous, given all the lines of code
you pour into Cocoon. You know how many lines of cod
Stefano Mazzocchi wrote:
>
> Carsten Ziegeler wrote:
>
> > Although the vote is over, just my 2 cents:
> >
> > Maven is a really useful tool *if* you know how to use it! I think
> > most projects that tried to use Maven and failed did not
> use it in the
> > right way. Just look at the mess A
Carsten Ziegeler wrote:
Although the vote is over, just my 2 cents:
Maven is a really useful tool *if* you know how to use it! I think
most projects that tried to use Maven and failed did not use it in
the right way. Just look at the mess Avalon tried to do with Maven.
If you want to use Maven, you
Antonio Gallardo wrote:
I propose to move Cocoon to Maven. Please VOTE:
-1
I'm with Howard [1] and Hani [2] on this matter. Again, "Less is more"
and we certainly don't need the (mostly) useless drivel that passes for
"Project reports" in maven-generated sites. Trimming the fat by having
the bui
Antonio Gallardo wrote:
OK. I will not continue the drama. I revoke the VOTE. It was just a RT.
Sorry for the loud.
To close this issue. Here is also another gig -1 to forbid it. ;-)
Antonio, I understand you being disappointed, but don't take it badly.
Changing the build system is an important
Carsten Ziegeler wrote:
Although the vote is over, just my 2 cents:
Maven is a really useful tool *if* you know how to use it! I think
most projects that tried to use Maven and failed did not use it in
the right way. Just look at the mess Avalon tried to do with Maven.
If you want to use Maven, you
...I propose to move Cocoon to Maven. Please VOTE:
I know the vote is canceled, but maybe we can talk about the problems
before looking at a solution?
IMHO these are the problems of the current build system:
1) Monolithic repository makes it impossible to include libraries
having non-ASF compati
Gallardo [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 25, 2004 1:14 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [VOTE] - Move Cocoon to Maven
>
>
> OK. I will not continue the drama. I revoke the VOTE. It was
> just a RT.
> Sorry for the loud.
>
> To close this i
OK. I will not continue the drama. I revoke the VOTE. It was just a RT.
Sorry for the loud.
To close this issue. Here is also another gig -1 to forbid it. ;-)
Best Regards,
Antonio Gallardo
Leszek Gawron wrote:
What about real blocks? Will maven still be useful?
no
--
Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
On 24.05.2004 23:18, Antonio Gallardo wrote:
2-Automatically generation of statistics and status of the project.
4-We can still use forrest for doco generation.
AFAIK they are contrary, see OJB project for example. They abstain from
statistics for forrest-generated docu.
I propose to move Cocoon
Antonio Gallardo wrote:
Hi:
I saw many projects that benefit from maven in:
1-shared repository of jars. It will help to cut most of the fat of cocoon.
2-Automatically generation of statistics and status of the project.
Improves the overview of the project. Manually managing release notes
allow rel
Leszek Gawron wrote:
2-Automatically generation of statistics and status of the project.
I think that anyone outside cocoon-dev does not care really for the
status of the project as long as they are using a released version.
My english is sometimes to poor to express what I meant. I mean that
the
Antonio Gallardo wrote:
Hi:
I saw many projects that benefit from maven in:
1-shared repository of jars. It will help to cut most of the fat of cocoon.
2-Automatically generation of statistics and status of the project.
Improves the overview of the project. Manually managing release notes
allow rel
I propose to move Cocoon to Maven. Please VOTE:
I have a personal problem with maven. Everyone has his own limits, and
I have to recognize that I just seem not to be able to cope with
football, contemporary music, statistics and Maven.
I don't recall being able to actually build a maven projec
Antonio Gallardo wrote:
I cannot vote so just comments:
I saw many projects that benefit from maven in:
Porting to maven means breaking all users' build systems (see
YourCocoonBasedProject on wiki)
1-shared repository of jars. It will help to cut most of the fat of cocoon.
The jars have to end up
Hi:
I saw many projects that benefit from maven in:
1-shared repository of jars. It will help to cut most of the fat of cocoon.
2-Automatically generation of statistics and status of the project.
Improves the overview of the project. Manually managing release notes
allow releases without a full
21 matches
Mail list logo