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
On 13 November 2010 05:56, Ralph Goers wrote:
> I've changed the package name from org.commons.vfs to org.commons.vfs2.
> However, it isn't necessary to change the artifact id from commons-vfs to
> commons-vfs2 since we are changing the groupId already. The only reason to
> do it is to have i
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-jelly-tags-quartz has an issue affecting its community
integratio
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
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MavenGroupIDChange" page has been changed by sebbapache.
The comment on this change is: Add classpath notes.
http://wiki.apache.org/commons/MavenGroupIDChange?action=diff&rev1=1&re
Change it to be consistent. We've had this discussion before.
On Sat, Nov 13, 2010 at 12:56 AM, Ralph Goers
wrote:
> I've changed the package name from org.commons.vfs to org.commons.vfs2.
> However, it isn't necessary to change the artifact id from commons-vfs to
> commons-vfs2 since we are
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MavenGroupIDChange" page has been changed by James Carman.
The comment on this change is: Added a comment to the package name change
section..
http://wiki.apache.org/commons/Maven
I don't know why this showed up with so many diffs. All I did was
fire up the GUI version of the editor and add the comment in
parentheses. Sorry for the noise.
-- Forwarded message --
From: Apache Wiki
Date: Sat, Nov 13, 2010 at 9:07 AM
Subject: [Commons Wiki] Update of "Maven
On 13 November 2010 14:12, James Carman wrote:
> I don't know why this showed up with so many diffs. All I did was
> fire up the GUI version of the editor and add the comment in
> parentheses. Sorry for the noise.
Must be a bug in the GUI editor.
It looks like it has joined all the lines toget
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MavenGroupIDChange" page has been changed by sebbapache.
http://wiki.apache.org/commons/MavenGroupIDChange?action=diff&rev1=3&rev2=4
--
On 2010-11-13 15:00, James Carman wrote:
> Change it to be consistent. We've had this discussion before.
+1
Consistence is a good thing.
>
> On Sat, Nov 13, 2010 at 12:56 AM, Ralph Goers
> wrote:
>> I've changed the package name from org.commons.vfs to org.commons.vfs2.
>> However, it isn't
This is a great post. Personally, I think the need to do this is completely
caused by Maven and I've been discussing this with them for years. I will be
writing up a proposal on the Maven wiki which would eliminate the need to keep
renaming packages and artifacts. Instead, artifacts would con
This stuff isn't just all about Maven. The artifactId change is, but
the package name change is useful (and even required) in non-maven
environments, too.
On Sat, Nov 13, 2010 at 10:09 AM, Ralph Goers
wrote:
> This is a great post. Personally, I think the need to do this is completely
> caused
Le 13/11/2010 16:09, Ralph Goers a écrit :
> This is a great post. Personally, I think the need to do this is completely
> caused by Maven and I've been discussing this with them for years. I will be
> writing up a proposal on the Maven wiki which would eliminate the need to
> keep renaming pa
Not really. If you can insure that only a single version of the artifact is on
the classpath then there is no need for package renaming. The concept here is
very similar to how packages in RedHat or Debian versions of Linux work. I
will admit that without a tool like Maven it would be much mor
Sometimes you *can't* ensure that! We've already discussed the whole
idea of "jar hell" (two different libraries on the classpath require
two different, binary incompatible versions of the same library) and
this isn't something you can resolve with the classes in the same
package.
On Sat, Nov 13,
On Nov 13, 2010, at 7:28 AM, Luc Maisonobe wrote:
> Le 13/11/2010 16:09, Ralph Goers a écrit :
>> This is a great post. Personally, I think the need to do this is completely
>> caused by Maven and I've been discussing this with them for years. I will
>> be writing up a proposal on the Maven w
Can't we adopt some Commons-wide guidelines (or rules) for stuff like this and
put in on the wiki?
Gary Gregory
Senior Software Engineer
Rocket Software
3340 Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA
Tel: +1.404.760.1560
Email: ggreg...@seagullsoftware.com
Web: seagull.rocketsoftware.co
We're working on it. Notice the wiki update notices that have been
going out today. Sebb and I have been commenting back and forth.
Feel free to chime in on the wiki. Let's get all of our
ideas/concerns in one place and then work on forming a good set of
guidelines, which you can break as long a
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=1581&projectId=95
Build statistics:
State: Failed
Previous State: Ok
Started at: Sat 13 Nov 2010 18:22:16 +
Finished at: Sat 13 Nov 2010 18:25:08 +
Total time: 2m 51s
Build Trigger: Schedule
Build
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=1588&projectId=72
Build statistics:
State: Failed
Previous State: Ok
Started at: Sun 14 Nov 2010 00:34:02 +
Finished at: Sun 14 Nov 2010 00:35:06 +
Total time: 1m 4s
Build Trigger: Schedule
Build
21 matches
Mail list logo
