Re: [ANN] Maven b3 released!

[Peter Donald]

Please don't cross post announcements to the general list. Announcements 
should go to the announcements list as thats what it is meant for.

On Thu, 11 Apr 2002 23:14, Jason van Zyl wrote:
> The Maven team is pleased to announce the Beta 3 release!
>
> http://jakarta.apache.org/turbine/maven/
>
> Maven is a Java project management and project comprehension tool. Maven is
> based on the concept of a project object model (POM) in that all the
> artifacts produced by Maven are a result of consulting a well defined model
> for your project. Builds, documentation, source metrics, and source
> cross-references are all controlled by your POM.
>
> Maven has many goals, but in a nutshell Maven aims to make the developer's
> life easier by providing a well defined project structure, well defined
> development processes to follow, and a coherent body of documentation that
> keeps your developers and clients apprised of what's happening with your
> project. Maven alleviates a lot of what most developers consider drudgery
> and lets them get on with the task at hand. This is essential in OSS
> projects where there aren't many people dedicated to the task of
> documenting and propagating the critical information about your project
> which is necessary in order to attract potential new developers and
> clients.
>
> Changes in this version include:
>
> o Integration of Checkstyle
>
> o Maven installation update mechanism that allows you to easily
>   update your Maven installation.
>
> o POM update mechanism that will move your Maven projects forward easily
>   as Maven improves. The updater will transform your project descriptor,
>   properties files and the project structure itself if required.
>
> o Testing has been simplified and made safer.
>
> o An XML Schema and validation mechanism have been added.
>
> o Documentation changes include fully documented Maven properties, the
>   start of an FAQ, and several modifications to help unify the
>   documentation so its more coherent for new users.

-- 
Cheers,

Pete


Why does everyone always overgeneralize?


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: commons digest...

[Andrew C. Oliver]

On Thu, 2002-04-11 at 22:18, Pier Fumagalli wrote:
> Andrew C. Oliver <[EMAIL PROTECTED]> wrote:
> 
> > Commons digest messages always look like this (below) rather than having
> > the nice summaries (it works on other lists like cocoon for instance).
> > I can't handle the traffic to get mails individually, but whats worse is
> > I can read a summary to see what is interesting.  I know it sounds like
> > a whine...but can we fix this?
> 
> Sure, I was supposed to do it today, but I ended up with some real work to
> do...
> 

Thanks!  

> > Anything I can do to help?
> 
> Not if you don't know how ezmlm-make works! :) :) :)
> 

All the more reason to offer to help ;-)

-Andy

> Pier
> 
> > On Thu, 2002-04-11 at 14:08, [EMAIL PROTECTED]
> > wrote:
> >> 
> >> commons-dev Digest 11 Apr 2002 18:08:24 - Issue 399
> >> 
> >> Topics (messages 6547 through 6556):
> >> 
> >> <- subject index not available for message(s) ->
> >> 6547 by: 
> >> 6548 by: 
> >> 6549 by: 
> >> 6550 by: 
> >> 6551 by: 
> >> 6552 by: 
> >> 6553 by: 
> >> 6554 by: 
> >> 6555 by: 
> >> 6556 by: 
> >> 
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org/poi - port of Excel/Word/OLE 2 Compound
Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: commons digest...

[Pier Fumagalli]

Andrew C. Oliver <[EMAIL PROTECTED]> wrote:

> Commons digest messages always look like this (below) rather than having
> the nice summaries (it works on other lists like cocoon for instance).
> I can't handle the traffic to get mails individually, but whats worse is
> I can read a summary to see what is interesting.  I know it sounds like
> a whine...but can we fix this?

Sure, I was supposed to do it today, but I ended up with some real work to
do...

> Anything I can do to help?

Not if you don't know how ezmlm-make works! :) :) :)

Pier

> On Thu, 2002-04-11 at 14:08, [EMAIL PROTECTED]
> wrote:
>> 
>> commons-dev Digest 11 Apr 2002 18:08:24 - Issue 399
>> 
>> Topics (messages 6547 through 6556):
>> 
>> <- subject index not available for message(s) ->
>> 6547 by: 
>> 6548 by: 
>> 6549 by: 
>> 6550 by: 
>> 6551 by: 
>> 6552 by: 
>> 6553 by: 
>> 6554 by: 
>> 6555 by: 
>> 6556 by: 
>> 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

commons digest...

[Andrew C. Oliver]

Commons digest messages always look like this (below) rather than having
the nice summaries (it works on other lists like cocoon for instance). 
I can't handle the traffic to get mails individually, but whats worse is
I can read a summary to see what is interesting.  I know it sounds like
a whine...but can we fix this?  Anything I can do to help?

Thanks,

-Andy



On Thu, 2002-04-11 at 14:08, [EMAIL PROTECTED]
wrote:
> 
> commons-dev Digest 11 Apr 2002 18:08:24 - Issue 399
> 
> Topics (messages 6547 through 6556):
> 
> <- subject index not available for message(s) ->
>   6547 by: 
>   6548 by: 
>   6549 by: 
>   6550 by: 
>   6551 by: 
>   6552 by: 
>   6553 by: 
>   6554 by: 
>   6555 by: 
>   6556 by: 
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org/poi - port of Excel/Word/OLE 2 Compound
Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Mailman for Jakarta/Apache?

[Pier Fumagalli]

"Andrew C. Oliver" <[EMAIL PROTECTED]> wrote:

> On Tue, 2002-04-09 at 04:00, Peter Donald wrote:
>> Hi,
>> 
>> Is there any desire to get a mailman interface to the Apache mailing lists?
>> (For those of you who don't know it is the same interface used at sourceforge
>> - but their archives suck so we can use our own for that.)
> 
> We can use our own to suck?  ;-)  (sorry couldn't resist)

:-)

>> The reason being that I have received a bunch of admin emails over last few
>> days from people who could have handled it them selves if a mailman
>> styleinterface was available.
>> 
>> Thoughts on this?
> 
> My only question starts with a P.  With the amount of volume Jakarta a/o
> Apache gets, can Mailman hold up?  (I've no idea, I'm asking)...  If so,
> then god yes... I'm too stupid to remember the syntax of those commands
> and have to email the thing to send me the help page all the time...

Currently we're using EZMLM/QMAIL which are a good solution, but not the
optimal one (IMO). Over time I'm noticing how postfix is somehow better than
Qmail, the only problem is that EZMLM is just so friggin' cute...

With the amount of messages we generate (only for Jakarta.apache.org we're
around 600.000 deliveries per day) switching infrastructure is a _big_
problem, but since I'm paid by my employer to do something similar
(newsletter generator), something good might come out of it...

Maybe in 6 months from now we'd be able to switch to something better, but
for now, let's not touch it too much... And if someone wants to come along
and do a web-interface for ezmlm (not those crap ones available), I'm all
ears...

Pier

--
I think that it's extremely foolish to name a server after the current U.S.
President. B.W. Fitzpatrick



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Mailman for Jakarta/Apache?

[Andrew C. Oliver]

Cool...thats kinda what I thought.  

On Wed, 2002-04-10 at 23:32, James Duncan Davidson wrote:
> 
> On Tuesday, April 9, 2002, at 05:00 , Andrew C. Oliver wrote:
> 
> > My only question starts with a P.  With the amount of volume Jakarta a/o
> > Apache gets, can Mailman hold up?  (I've no idea, I'm asking)...  If so,
> > then god yes... I'm too stupid to remember the syntax of those commands
> > and have to email the thing to send me the help page all the time...
> 
> Brian has tried several things to use for lists. This is how we've 
> settled on qmail/ezmlm. Most anything else isn't going to handle the 
> kind of load that goes through the server. Hell, Jakarta is running its 
> lists on nagoya partially because of load reasons.
> 
> The right place for this kind of discussion is infrastructure@ -- but 
> lots of effort has already gone into how to run these lists
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org/poi - port of Excel/Word/OLE 2 Compound
Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Large code donation?

[Ceki Gülcü]

Your explanation is crystal clear. I'll organize a vote on the
donation just to make sure that we really want the code. Thanks again, Ceki

At 23:58 11.04.2002 +0200, [EMAIL PROTECTED] wrote:

>On Thu, 11 Apr 2002, Ceki [iso-8859-1] Gülcü wrote:
>
> > A commercial company, after changing its business orientation, recently
> > proposed to donate a rather large chuck of code, essentially a log4j
> > extension, to the log4j project. Do we need to have them sign any
> > paperwork? Assuming they post the source code (under the Apache Software
> > License)  to the log4j-dev list, can we then consider that the
> > contribution is "just" a large patch?
> >
> > Any clarification on this matter would be greatly appreciated.
>
>There are several reasons why this needs a contributors license (assuming
>people want the code)
>
>-   Whoever post the patch cannot claim he has written
> it himself
>-   And since it is clearly associated with a commercial
> company - that person cannot easily claim he or she
> owns it 100%
>-   Nor do we have a clear relation (committer, member)
> with that person.
>
>So each of those is an indiactor that you propably want to go through the
>contributor license hassle. The PMC or board can help you.
>
>Feel free to ask for a hand.
>
>But of course you do want to make sure that the log4j community
>actually wants that code !
>
>Dw
>
>
>--
>To unsubscribe, e-mail:   
>For additional commands, e-mail: 

--
Ceki


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Large code donation?

[dirkx]

On Thu, 11 Apr 2002, Ceki [iso-8859-1] Gülcü wrote:

> A commercial company, after changing its business orientation, recently
> proposed to donate a rather large chuck of code, essentially a log4j
> extension, to the log4j project. Do we need to have them sign any
> paperwork? Assuming they post the source code (under the Apache Software
> License)  to the log4j-dev list, can we then consider that the
> contribution is "just" a large patch?
>
> Any clarification on this matter would be greatly appreciated.

There are several reasons why this needs a contributors license (assuming
people want the code)

-   Whoever post the patch cannot claim he has written
it himself
-   And since it is clearly associated with a commercial
company - that person cannot easily claim he or she
owns it 100%
-   Nor do we have a clear relation (committer, member)
with that person.

So each of those is an indiactor that you propably want to go through the
contributor license hassle. The PMC or board can help you.

Feel free to ask for a hand.

But of course you do want to make sure that the log4j community
actually wants that code !

Dw


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Large code donation?

[Ceki Gülcü]

Hi all,

A commercial company, after changing its business orientation, recently 
proposed to
donate a rather large chuck of code, essentially a log4j extension, to the 
log4j project.
Do we need to have them sign  any paperwork? Assuming they post the source 
code
(under the Apache Software License)  to the log4j-dev list, can we then 
consider that
the contribution is "just" a large patch?

Any clarification on this matter would be greatly appreciated.

--
Ceki


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [PATCH] http://jakarta.apache.org/site/mail2.html broken url

[Santiago Gala]

Daniel F. Savarese wrote:

>In message <[EMAIL PROTECTED]>, Santiago Gala writes:
>
>>Santiago Gala wrote:
>>I have enough karma for xml/html committing, but not for ssh to the web 
>>machine. So, could anybody with enough karma update the site?
>>
>
>I just did a cvs update mail2.html, but it doesn't look like there was
>any change committed.  I tried doing an update and rebuild of my
>jakarta-site2 checkout, but there ws no difference in mail2.html.
>
Funny, because I patched mail2.xml:

[sgala@patusan jakarta-site2]$ cvs log xdocs/site/mail2.xml

RCS file: /home/cvs/jakarta-site2/xdocs/site/mail2.xml,v
Working file: xdocs/site/mail2.xml
head: 1.43
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 43;selected revisions: 43
description:

revision 1.43
date: 2002/04/07 22:05:50;  author: sgala;  state: Exp;  lines: +1 -1
Patch sent by [EMAIL PROTECTED] Thanks.
...

>
>I don't have the email with the original patch, so I'll pass the buck
>to someone else.
>

I had committed just changes in mail2.xml, thinking that the build was 
done elsewhere. Now I have committed also mail2.html.

Sorry for the half cooked thing.





--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

[ANN] Maven b3 released!

[Jason van Zyl]

The Maven team is pleased to announce the Beta 3 release!

http://jakarta.apache.org/turbine/maven/

Maven is a Java project management and project comprehension tool. Maven is
based on the concept of a project object model (POM) in that all the
artifacts produced by Maven are a result of consulting a well defined model
for your project. Builds, documentation, source metrics, and source
cross-references are all controlled by your POM. 

Maven has many goals, but in a nutshell Maven aims to make the developer's
life easier by providing a well defined project structure, well defined
development processes to follow, and a coherent body of documentation that
keeps your developers and clients apprised of what's happening with your
project. Maven alleviates a lot of what most developers consider drudgery
and lets them get on with the task at hand. This is essential in OSS
projects where there aren't many people dedicated to the task of documenting
and propagating the critical information about your project which is
necessary in order to attract potential new developers and clients.

Changes in this version include:

o Integration of Checkstyle

o Maven installation update mechanism that allows you to easily
  update your Maven installation.

o POM update mechanism that will move your Maven projects forward easily
  as Maven improves. The updater will transform your project descriptor,
  properties files and the project structure itself if required.

o Testing has been simplified and made safer.

o An XML Schema and validation mechanism have been added.

o Documentation changes include fully documented Maven properties, the
  start of an FAQ, and several modifications to help unify the
  documentation so its more coherent for new users.

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]

http://tambora.zenplex.org


--
To unsubscribe, e-mail:   
For additional commands, e-mail: