Hi Sebb,
sebb wrote:
> On 9 March 2011 02:46, Gary Gregory wrote:
[snip]
>> Ug, I cannot change the groupId because I cannot change the package.
>> Codec 1.5 fixes some long standing bugs introduced in 1.4.
>>
>> If I change the groupId... Are we talking end of the Maven world or
>> wasted mem
Thank you, I understand now. I will go the Nexus route first...
Gary
On Tue, Mar 8, 2011 at 10:55 PM, sebb wrote:
> On 9 March 2011 02:46, Gary Gregory wrote:
> >
> >
> > On Tue, Mar 8, 2011 at 9:34 PM, sebb wrote:
> >>
> >> On 9 March 2011 02:31, Gary Gregory wrote:
> >> > Does having the o
On 9 March 2011 02:46, Gary Gregory wrote:
>
>
> On Tue, Mar 8, 2011 at 9:34 PM, sebb wrote:
>>
>> On 9 March 2011 02:31, Gary Gregory wrote:
>> > Does having the old style of groupId mean that deploying will not work,
>> > per
>> > http://wiki.apache.org/commons/UsingNexus#top
>> >
>> > "All Co
On Tue, Mar 8, 2011 at 9:34 PM, sebb wrote:
> On 9 March 2011 02:31, Gary Gregory wrote:
> > Does having the old style of groupId mean that deploying will not work,
> per
> > http://wiki.apache.org/commons/UsingNexus#top
> >
> > "All Commons components that use the org.apache.commons groupId are
On Tue, Mar 8, 2011 at 9:34 PM, sebb wrote:
> On 9 March 2011 02:31, Gary Gregory wrote:
> > Does having the old style of groupId mean that deploying will not work,
> per
> > http://wiki.apache.org/commons/UsingNexus#top
> >
> > "All Commons components that use the org.apache.commons groupId are
On 9 March 2011 02:31, Gary Gregory wrote:
> Does having the old style of groupId mean that deploying will not work, per
> http://wiki.apache.org/commons/UsingNexus#top
>
> "All Commons components that use the org.apache.commons groupId are already
> set up to use Nexus."
>
> And if not... what ha
Does having the old style of groupId mean that deploying will not work, per
http://wiki.apache.org/commons/UsingNexus#top
"All Commons components that use the *org.apache.commons* groupId are
already set up to use Nexus."
And if not... what happens?
Gary
On Tue, Mar 8, 2011 at 9:28 PM, Gary Gre
Does having the old style of groupId mean that deploying will not work, per
http://wiki.apache.org/commons/UsingNexus#top
"All Commons components that use the *org.apache.commons* groupId are
already set up to use Nexus."
And if not... what happens?
Gary
On Tue, Mar 8, 2011 at 8:00 PM, sebb w
Reverting and will do for 2.0.
Gary
On Tue, Mar 8, 2011 at 8:00 PM, sebb wrote:
> On 9 March 2011 00:02, wrote:
> > Author: ggregory
> > Date: Wed Mar 9 00:02:12 2011
> > New Revision: 1079608
> >
> > URL: http://svn.apache.org/viewvc?rev=1079608&view=rev
> > Log:
> > Use org.apache.commons
On 9 March 2011 00:02, wrote:
> Author: ggregory
> Date: Wed Mar 9 00:02:12 2011
> New Revision: 1079608
>
> URL: http://svn.apache.org/viewvc?rev=1079608&view=rev
> Log:
> Use org.apache.commons groupId
If you change the groupId you'll probably need to change the package
name as well ..
Other
sebb wrote:
> On 8 March 2011 20:17, Luc Maisonobe wrote:
>> Le 07/03/2011 11:37, er...@apache.org a écrit :
>>> Author: erans
>>> Date: Mon Mar 7 10:37:52 2011
>>> New Revision: 1078734
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1078734&view=rev
>>> Log:
>>> MATH-542
>>> "MathRuntimeExceptio
I also added a TM to the commons-skin's [commons] logo. In SVN.
Gary
On Tue, Mar 8, 2011 at 4:16 PM, sebb wrote:
> I did this because of the branding requirements:
>
> http://www.apache.org/foundation/marks/pmcs#graphics
>
>
> On 8 March 2011 21:06, Gary Gregory wrote:
> > My preference is to
Ironic that the page does not follow its own graphics branding requirement.
G
On Tue, Mar 8, 2011 at 4:16 PM, sebb wrote:
> I did this because of the branding requirements:
>
> http://www.apache.org/foundation/marks/pmcs#graphics
>
>
> On 8 March 2011 21:06, Gary Gregory wrote:
> > My preferen
I see. Here is what I am talking about for codec:
https://svn.apache.org/repos/asf/commons/proper/codec/trunk/src/site/resources/images/logo.png
Where is the commons logo? In commons-skin?
Gary
On Tue, Mar 8, 2011 at 4:16 PM, sebb wrote:
> I did this because of the branding requirements:
>
>
Hello.
> > Modified:
> > commons/proper/math/trunk/src/test/java/org/apache/commons/math/ode/sampling/DummyStepInterpolatorTest.java
> > URL:
> > http://svn.apache.org/viewvc/commons/proper/math/trunk/src/test/java/org/apache/commons/math/ode/sampling/DummyStepInterpolatorTest.java?rev=1078734&r
I did this because of the branding requirements:
http://www.apache.org/foundation/marks/pmcs#graphics
On 8 March 2011 21:06, Gary Gregory wrote:
> My preference is to remove the two TMs I see near the logos.
>
> You do not see TMs, Rs, and SMs all over the place on http://www.apple.com/
> for e
My preference is to remove the two TMs I see near the logos.
You do not see TMs, Rs, and SMs all over the place on
http://www.apple.com/for example.
It's not appleaing visually either IMO.
If we were truly worried about it, someone should stick TMs in the logos.
Gary
On Tue, Mar 8, 2011 at 3:5
On 8 March 2011 20:17, Luc Maisonobe wrote:
> Le 07/03/2011 11:37, er...@apache.org a écrit :
>> Author: erans
>> Date: Mon Mar 7 10:37:52 2011
>> New Revision: 1078734
>>
>> URL: http://svn.apache.org/viewvc?rev=1078734&view=rev
>> Log:
>> MATH-542
>> "MathRuntimeException" provides two ways for
On 8 March 2011 19:55, Gary Gregory wrote:
> The TM on the Commons URL is in the wrong place:
> http://yfrog.com/f/h20qjd3j/
So where should it be?
It can be placed anywhere, by suitable choice of top/bottom/left/right.
> IMO, the TM should be in the graphics themselves. Much more reusable that
Le 07/03/2011 11:37, er...@apache.org a écrit :
> Author: erans
> Date: Mon Mar 7 10:37:52 2011
> New Revision: 1078734
>
> URL: http://svn.apache.org/viewvc?rev=1078734&view=rev
> Log:
> MATH-542
> "MathRuntimeException" provides two ways for enhancing the information
> content:
> one for local
The TM on the Commons URL is in the wrong place:
http://yfrog.com/f/h20qjd3j/
IMO, the TM should be in the graphics themselves. Much more reusable that
way.
Gary
On Mon, Mar 7, 2011 at 3:47 PM, sebb wrote:
> I think the time has come to formally vote on the updates to Commons
> Skin and Common
+1
Simone Tripodi wrote:
> Hi all PMCs,
> I prepared the OGNL[1] proposal to be submitted to the ASF incubator,
> I already discussed with involved people and the original author and
> we all agreed Commons should be the best place for OGNL where living.
> Some of them are Struts PMC members, the
Le 08/03/2011 12:58, Simone Tripodi a écrit :
> Hi all PMCs,
> I prepared the OGNL[1] proposal to be submitted to the ASF incubator,
> I already discussed with involved people and the original author and
> we all agreed Commons should be the best place for OGNL where living.
> Some of them are Stru
+1, works with [codec] in SVN.
Gary
On Tue, Mar 8, 2011 at 12:21 PM, sebb wrote:
> Note: to test this you need to change the POM to reference commons-parent
> 19.
>
> As this is not yet in an official repo, you will need to add the
> following repository definition to your settings.xml:
>
>
A posting on the user list points out that the commons daemon 1.0.3
POM has a groupId of org.apache.commons, but is somehow included in
the directory:
http://repo1.maven.org/maven2/commons-daemon/commons-daemon/
i.e. it should have the groupId commons-daemon.
I assume this happened before Nexus,
Note: to test this you need to change the POM to reference commons-parent 19.
As this is not yet in an official repo, you will need to add the
following repository definition to your settings.xml:
Nexus
true
Nexus
https://repo
+1
Phil
On Mar 8, 2011, at 4:58 AM, Simone Tripodi wrote:
> Hi all PMCs,
> I prepared the OGNL[1] proposal to be submitted to the ASF incubator,
> I already discussed with involved people and the original author and
> we all agreed Commons should be the best place for OGNL where living.
> Some
+1
forgot to cast my vote! doh! :P
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Mar 8, 2011 at 5:31 PM, Henri Yandell wrote:
> +1.
>
> On Tue, Mar 8, 2011 at 5:17 AM, Jochen Wiedmann
> wrote:
>> +1
>>
>> If the project is indeed used by Struts and Tapestry (as cla
+1.
On Tue, Mar 8, 2011 at 5:17 AM, Jochen Wiedmann
wrote:
> +1
>
> If the project is indeed used by Struts and Tapestry (as claimed in
> the proposal), then I see no reason for objecting.
>
>
> On Tue, Mar 8, 2011 at 12:58 PM, Simone Tripodi
> wrote:
>> Hi all PMCs,
>> I prepared the OGNL[1] pr
On 8 March 2011 06:17, Henri Yandell wrote:
> Should we be claiming trademark on 'Commons'?
I wondered about that.
This is trivial to change, and only affects Commons Parent.
(and if a component wants to override it, they can add their own
version of the section to their site.xml)
I'll leave t
+1
If the project is indeed used by Struts and Tapestry (as claimed in
the proposal), then I see no reason for objecting.
On Tue, Mar 8, 2011 at 12:58 PM, Simone Tripodi
wrote:
> Hi all PMCs,
> I prepared the OGNL[1] proposal to be submitted to the ASF incubator,
> I already discussed with invo
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 gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
Hi all PMCs,
I prepared the OGNL[1] proposal to be submitted to the ASF incubator,
I already discussed with involved people and the original author and
we all agreed Commons should be the best place for OGNL where living.
Some of them are Struts PMC members, they also asked on their private
MLs and
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 gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
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 gene...@gump.apache.org.
Project commons-vfs2 has an issue affecting its community integration.
This issue
35 matches
Mail list logo
