James Carman a écrit :
Well, I'd like to see commons have some consistency to it. I would
rather every component within commons follow the same naming
conventions w.r.t. packages and I guess now artifactIds (I didn't
realize that was an issue within maven until I did my little test
tonight). Ma
On Sun, 2008-02-17 at 10:34 +0100, Emmanuel Bourg wrote:
> James Carman a écrit :
> > Well, I'd like to see commons have some consistency to it. I would
> > rather every component within commons follow the same naming
> > conventions w.r.t. packages and I guess now artifactIds (I didn't
> > reali
On 17/02/2008, Phil Steitz <[EMAIL PROTECTED]> wrote:
> Thanks, all for the feedback on RC1. Here is another RC incorporating
> suggestions for documentation improvements, (compatible) API changes
> and sources and javadoc jars in the binary distribution.
>
> The zips / tars are here:
> http://peo
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme has an issue affecting its community
integration.
This
On 2/17/08, simon <[EMAIL PROTECTED]> wrote:
>
> On Sun, 2008-02-17 at 10:34 +0100, Emmanuel Bourg wrote:
> > James Carman a écrit :
> > > Well, I'd like to see commons have some consistency to it. I would
> > > rather every component within commons follow the same naming
> > > conventions w.r.t.
Hi,
I'd like to open the discussion on the changes we'll implement on the
2.x branch. Here is a list of the things I have in mind :
Cleanup
- Remove ConfigurationFactory, its use is deprecated since the
introduction of ConfigurationBuilder. This removal will allow us to drop
the dependency
simon a écrit :
There is a slow process of migrating commons libraries from the old
style of groupId to a proper groupId of org.apache.commons. This
migration is also happening for projects where no incompatible changes
are being made, ie is just a "namespace cleanup".
I understand that the gr
On Feb 17, 2008 6:45 AM, sebb <[EMAIL PROTECTED]> wrote:
> On 17/02/2008, Phil Steitz <[EMAIL PROTECTED]> wrote:
> > Thanks, all for the feedback on RC1. Here is another RC incorporating
> > suggestions for documentation improvements, (compatible) API changes
> > and sources and javadoc jars in th
maven --version gives:
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1
Is this earlier or later than 1.02?
java -version
java version "1.4.2_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
Java Hot
On Feb 17, 2008 8:37 AM, sebb <[EMAIL PROTECTED]> wrote:
> maven --version gives:
>
> __ __
> | \/ |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.1
>
> Is this earlier or later than 1.02?
That is later and it does not work for commons
On Feb 17, 2008 8:45 AM, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On Feb 17, 2008 8:37 AM, sebb <[EMAIL PROTECTED]> wrote:
> > maven --version gives:
> >
> > __ __
> > | \/ |__ _Apache__ ___
> > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> > |_| |_\__,_|\_/\___|_||_| v. 1.1
> >
> > I
Sorry, last response got away from me.
Regarding the m1 build, I can't reproduce the error you are seeing.
Are you using 1.0.2? What jdk and platform?
Phil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
On 17/02/2008, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On Feb 17, 2008 8:45 AM, Phil Steitz <[EMAIL PROTECTED]> wrote:
> > On Feb 17, 2008 8:37 AM, sebb <[EMAIL PROTECTED]> wrote:
> > > maven --version gives:
> > >
> > > __ __
> > > | \/ |__ _Apache__ ___
> > > | |\/| / _` \ V / -_) ' \ ~ int
sebb a écrit :
On 17/02/2008, Phil Steitz <[EMAIL PROTECTED]> wrote:
On Feb 17, 2008 8:45 AM, Phil Steitz <[EMAIL PROTECTED]> wrote:
On Feb 17, 2008 8:37 AM, sebb <[EMAIL PROTECTED]> wrote:
maven --version gives:
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projec
On Feb 17, 2008 9:38 AM, Luc Maisonobe <[EMAIL PROTECTED]> wrote:
> sebb a écrit :
> > On 17/02/2008, Phil Steitz <[EMAIL PROTECTED]> wrote:
> >> On Feb 17, 2008 8:45 AM, Phil Steitz <[EMAIL PROTECTED]> wrote:
> >>> On Feb 17, 2008 8:37 AM, sebb <[EMAIL PROTECTED]> wrote:
> maven --version giv
In most points I agree. Some comments below:
Emmanuel Bourg schrieb:
Hi,
I'd like to open the discussion on the changes we'll implement on the
2.x branch. Here is a list of the things I have in mind :
Cleanup
- Remove ConfigurationFactory, its use is deprecated since the
introduction of C
On Feb 17, 2008 3:09 PM, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On Feb 17, 2008 6:45 AM, sebb <[EMAIL PROTECTED]> wrote:
> > On 17/02/2008, Phil Steitz <[EMAIL PROTECTED]> wrote:
> > > Thanks, all for the feedback on RC1. Here is another RC incorporating
> > > suggestions for documentation impro
I ran the builds on the source distro using m1 and m2 - all looks good to me.
Niall
On Feb 17, 2008 6:47 AM, Phil Steitz <[EMAIL PROTECTED]> wrote:
> Thanks, all for the feedback on RC1. Here is another RC incorporating
> suggestions for documentation improvements, (compatible) API changes
> and
If I remove the optional tags, and now Maven 1.1 seems to work OK -
however it reports:
DEPRECATED: the default goal should be specified in the
section of project.xml instead of maven.xml
On 17/02/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> I ran the builds on the source distro using m1
This commit contains a lot of noise related to formatting changes. This
makes it very difficult to find out what you actually changed.
Can you please try to minimize reformatting as much as possible?
Thanks
Oliver
[EMAIL PROTECTED] schrieb:
Author: ebourg
Date: Sat Feb 16 16:20:15 2008
New Re
Oliver Heger a écrit :
This commit contains a lot of noise related to formatting changes. This
makes it very difficult to find out what you actually changed.
Can you please try to minimize reformatting as much as possible?
Thanks
Oliver
Do you mind if we set the column limit to 120 character
Emmanuel Bourg schrieb:
sebb a écrit :
The static DateFormat is not private, so the synchronization is not
guaranteed.
I'll make it private. I added a comment mentioning that it must be
synchronized.
Likewise the instance DateFormat.
Indeed that is worse, since the format is temporarily
sebb schrieb:
On 17/02/2008, Emmanuel Bourg <[EMAIL PROTECTED]> wrote:
Oliver Heger a écrit :
This commit contains a lot of noise related to formatting changes. This
makes it very difficult to find out what you actually changed.
Can you please try to minimize reformatting as much as possible?
On 17/02/2008, Emmanuel Bourg <[EMAIL PROTECTED]> wrote:
> Oliver Heger a écrit :
> > This commit contains a lot of noise related to formatting changes. This
> > makes it very difficult to find out what you actually changed.
> >
> > Can you please try to minimize reformatting as much as possible?
>
sebb a écrit :
Whether wrapped code is difficult to read depends on where the code is
wrapped ...
The kind of wrapping that I find difficult to read is a wrapping on a
method invocation, for example:
foo
.bar()
or wrapping just after a parenthesis :
Foo foo = new Foo(
Emmanuel Bourg skrev den 17-02-2008 23:36:
it's less annoying after a comma :
foo.doSomething(param1,
param2,
param2);
I have found it convenient to introduce explanatory variables, named
according to the parameter they are to be assigned (which sho
This is a vote to release Commons Math 1.2.
The zips / tars are here:
http://people.apache.org/~psteitz/math-1.2-RC3/
The site included in the binary distro is here:
http://people.apache.org/~psteitz/math-1.2-RC3/docs/
Release notes:
http://people.apache.org/~psteitz/math-1.2-RC3/RELEASE-NOTES.t
Selon [EMAIL PROTECTED]:
> Modified: commons/proper/math/tags/MATH_1_2_RC3/src/site/xdoc/changes.xml
[snip]
> - +
28 matches
Mail list logo