i've uploaded the tidied and regenerated site:
http://commons.apache.org/resources/
- robert
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On May 17, 2009, at 3:16 PM, Stephen Colebourne wrote:
Matt Benson wrote:
Or, to put it another way, the consensus seems to be
that the component + the major version # makes a project.
As I've said before, I won't try and stop this, I no longer have the
moral rights here. I do believe
Mohammady Mahdy wrote:
Guys I am glad to see this project coming back to life, the viewvc and
repository url on the site are broken though:
jakarta/commons/proper/resources/trunk: unknown location
Can you send the ones you are using ?
it takes a few hours for the site to sync: try again
The repository link still doesn't work:
ViewVCException: 404 Not Found: commons/proper/resources/trunk: unknown location
On Mon, May 18, 2009 at 9:28 AM, Robert Burrell Donkin
robertburrelldon...@blueyonder.co.uk wrote:
i've uploaded the tidied and regenerated site:
Planning to do so :) will jump the JIRA once I return today, let me know if
there is something specific I can help with.
On Mon, May 18, 2009 at 9:32 AM, Robert Burrell Donkin
robertburrelldon...@blueyonder.co.uk wrote:
Mohammady Mahdy wrote:
Guys I am glad to see this project coming back to
RAT reports a number of documents with missing headers
are we just going to assume that the provenance is fine but they were
forgotten, or do we need to do more digging?
- robert
-
To unsubscribe, e-mail:
the site has links into the wiki for a class diagram and a user guide.
is this enough of a bother to remove the links or create new documentation?
- robert
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On Sun, May 17, 2009 at 11:29 PM, Ralph Goers
ralph.go...@dslextreme.com wrote:
On May 17, 2009, at 3:16 PM, Stephen Colebourne wrote:
Matt Benson wrote:
Or, to put it another way, the consensus seems to be
that the component + the major version # makes a project.
As I've said before, I
So this is more noticeable. I'm starting to play with a rewritten
StringEscapeUtils system. escapeSql is going to get deleted, the
others will sit on top of a modular system. At least that's the
proposal - more in the ticket.
First pass at the code was educational - second pass should be
On May 17, 2009, at 11:39 PM, Henri Yandell wrote:
HttpClient is another example that is complained about by users :) The
only saving grace of v4 is that it is now named HttpComponents Core
(fitting Stephen's suggestion of a new name).
Of course that means users are also confused due to
Matt Benson wrote at Sonntag, 17. Mai 2009 22:31:
--- On Sun, 5/17/09, Matt Benson gudnabr...@yahoo.com wrote:
--- On Wed, 5/13/09, James Carman ja...@carmanconsulting.com
wrote:
[snip]
The point (at least mine) is that we don't *need* to
create
a new
project here. We have the
On May 18, 2009, at 12:19 AM, Jörg Schaible wrote:
I think we more or less all agree that such a new component should
play nice
with an older version in the classpath. However, while I am all for
evolving the current project with a new major release, we have to
consider
that it is not
Ralph Goers wrote at Montag, 18. Mai 2009 09:53:
On May 18, 2009, at 12:19 AM, Jörg Schaible wrote:
I think we more or less all agree that such a new component should
play nice
with an older version in the classpath. However, while I am all for
evolving the current project with a new
good point.
The correct groupId should be org.apache.commons
Sadly this is true for a few projects like commons.lang, but it's not true for
all projects, since a few commons projects already use the 'correct' groupId.
Also, this approach would not scale in the future.
LieGrue,
strub
-
Hi,
of which project are you talking about? VFS? Please put the components
name in your subject, like:
[vfs] Fix for race condition in forceMkdir
to be heard.
The issue is not attached to the mail. Please make sure you
additonally added it to a Jira issue. if there is none, please create
one :-)
On 2009-05-18, sebb seb...@gmail.com wrote:
On 15/05/2009, Oliver Heger oliver.he...@oliver-heger.de wrote:
I think md5 checksums are required for all artifacts. They are currently
missing.
Agreed.
Could perhaps add sha1 as well, but not essential
md5s and sha1s are now there and match.
On 16/05/2009, bay...@apache.org bay...@apache.org wrote:
Author: bayard
Date: Sat May 16 08:36:51 2009
New Revision: 775434
URL: http://svn.apache.org/viewvc?rev=775434view=rev
Log:
Letting PMD know we're on 1.5
Modified:
commons/proper/lang/trunk/pom.xml
Modified:
Excellent :-)
I think the consensus is to keep the sparse interfaces empty for now...
don't want to lock ourselves into anything without detailed discussion,
which there is no time for before 2.0.
Just drop a note into the Javadocs to the effect that methods may be added
in the next release. I
Mohammady Mahdy wrote:
The repository link still doesn't work:
ViewVCException: 404 Not Found: commons/proper/resources/trunk: unknown
location
it still looks fine to me :-/
i have Last Published: 17 May 2009. what do you have?
- robert
Mohammady Mahdy wrote:
Planning to do so :) will jump the JIRA once I return today, let me know if
there is something specific I can help with.
cool
i don't have any specific tasks (other than JIRA) ATM but if anyone
does, hopefully they'll jump in...
- robert
The link from: http://commons.apache.org/resources/source-repository.html is
working correctly.
The browse link on: http://commons.apache.org/resources/ is not though.
Thanks for updating.
On Mon, May 18, 2009 at 2:37 PM, Robert Burrell Donkin
robertburrelldon...@blueyonder.co.uk wrote:
The link from: http://commons.apache.org/resources/source-repository.html is
working correctly.
The browse link on: http://commons.apache.org/resources/ is not though.
This link points to proper instead of sandbox
Cheers
-
Thanks ^^
On Mon, May 18, 2009 at 3:06 PM, Christian Grobmeier grobme...@gmail.comwrote:
The link from:
http://commons.apache.org/resources/source-repository.html is
working correctly.
The browse link on: http://commons.apache.org/resources/ is not though.
This link points to proper
On May 18, 2009, at 2:39 AM, Henri Yandell wrote:
HttpClient is another example that is complained about by users :) The
only saving grace of v4 is that it is now named HttpComponents Core
(fitting Stephen's suggestion of a new name).
Well, this is kinda appropriate because I really have
Hello all,
I have created an empty Maven project with groupId commons-logging,
artifactId commons-logging and version 0.0.0-EMPTY. There is very
little content (around 500 bytes) in the whole project. This is to be
expected as the original aim was to produce an empty jar file.
For the actual
The POM should include SCM path, url to commons-logging site and licensing
metadata
Maybe you could also include the blog extract as description / comment. The
description explains the jar is empty but not why it is there
2009/5/18 Ceki Gulcu c...@qos.ch
Hello all,
I have created an empty
--- On Mon, 5/18/09, Jörg Schaible joerg.schai...@gmx.de wrote:
From: Jörg Schaible joerg.schai...@gmx.de
Subject: Re: [all] Rebooting commons projects
To: dev@commons.apache.org
Date: Monday, May 18, 2009, 2:19 AM
Matt Benson wrote at Sonntag, 17. Mai
2009 22:31:
--- On Sun,
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
Hello all,
I have created an empty Maven project with groupId commons-logging,
artifactId commons-logging and version 0.0.0-EMPTY. There is very
little content (around 500 bytes) in the whole project. This is to be
expected as the original aim
--- On Mon, 5/18/09, nicolas de loof nicolas.del...@gmail.com wrote:
From: nicolas de loof nicolas.del...@gmail.com
Subject: Re: commons-logging version 0.0.0-EMPTY
To: Commons Developers List dev@commons.apache.org
Date: Monday, May 18, 2009, 8:39 AM
The POM should include SCM path, url
If possible, I'd like karma for commons-sandbox. Also, I will
doing some work on cli and dbcp (to start) and if the PMC would
like to give me prelim-karma for that as well, that would be
appreciated :)
-
To unsubscribe, e-mail:
nicolas de loof wrote:
The POM should include SCM path, url to commons-logging site and licensing
metadata
Done. Note that I've used the url for for svn in commons/proper/trunk.
Maybe you could also include the blog extract as description / comment. The
description explains the jar is
Matt Benson wrote:
For the actual source code, see
https://svn.apache.org/viewvc/commons/sandbox/logging_empty/trunk/
Just to point out: the final location of this code should AIUI BE a branch under logging/branches... the current structure isn't harming anything at the moment, however.
sebb wrote:
It would be useful if the Manifest included the following details:
Implementation-Title: commons-logging
Implementation-Vendor: The Apache Software Foundation
Implementation-Vendor-Id: org.apache
Implementation-Version: 0.0.0-EMPTY
Specification-Title: commons-logging
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
sebb wrote:
It would be useful if the Manifest included the following details:
Implementation-Title: commons-logging
Implementation-Vendor: The Apache Software Foundation
Implementation-Vendor-Id: org.apache
Implementation-Version:
sebb wrote:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
sebb wrote:
It would be useful if the Manifest included the following details:
Implementation-Title: commons-logging
Implementation-Vendor: The Apache Software Foundation
Implementation-Vendor-Id: org.apache
Implementation-Version:
--- On Mon, 5/18/09, Ceki Gulcu c...@qos.ch wrote:
From: Ceki Gulcu c...@qos.ch
Subject: Re: commons-logging version 0.0.0-EMPTY
To: Commons Developers List dev@commons.apache.org
Date: Monday, May 18, 2009, 9:14 AM
Matt Benson wrote:
For the actual source code, see
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
sebb wrote:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
sebb wrote:
It would be useful if the Manifest included the following details:
Implementation-Title: commons-logging
Implementation-Vendor: The Apache
So where are we now with moving/graduating Sanselan?
Regards
Carsten
--
Carsten Ziegeler
cziege...@apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
What kind of work are we talking about?
ie) What's the sandbox karma for - we're nosy and like to hear about ideas :)
For CLI/DBCP - if it's a lot of work then that's a good place to work
on things in the sandbox.
If rather it's some bugfixes, then best is to attach them as patches
to JIRA
On Mon, May 18, 2009 at 5:33 AM, Jim Jagielski j...@jagunet.com wrote:
On May 18, 2009, at 2:39 AM, Henri Yandell wrote:
HttpClient is another example that is complained about by users :) The
only saving grace of v4 is that it is now named HttpComponents Core
(fitting Stephen's suggestion
On May 18, 2009, at 12:10 PM, Henri Yandell wrote:
On Mon, May 18, 2009 at 5:33 AM, Jim Jagielski j...@jagunet.com
wrote:
On May 18, 2009, at 2:39 AM, Henri Yandell wrote:
HttpClient is another example that is complained about by users :)
The
only saving grace of v4 is that it is now
eg: for cli, I find the default help/usage text much too limiting;
it would be nice to be able to have that completely under user control
with some sort of templating interface. It would also be cool if
that could also drive the parser being used (by defining usage
formating string, the matching
Hello,
Thank you for this suggestion. Unfortunately, adding references to parent pom,
addDefaultImplementationEntries and addDefaultSpecificationEntries creates a
manifest file which includes OSGi directives, which is really not desirable.
I changed the contents of the name element to
On 18/05/2009, c...@apache.org c...@apache.org wrote:
Author: ceki
Date: Mon May 18 16:47:32 2009
New Revision: 776006
URL: http://svn.apache.org/viewvc?rev=776006view=rev
Log:
name correction
Huh?
Modified:
commons/sandbox/logging_empty/trunk/pom.xml
Modified:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
Hello,
Thank you for this suggestion. Unfortunately, adding references to parent
pom, addDefaultImplementationEntries and
addDefaultSpecificationEntries creates a
manifest file which includes OSGi directives, which is really not desirable.
Jim Jagielski wrote:
eg: for cli, I find the default help/usage text much too limiting;
it would be nice to be able to have that completely under user control
with some sort of templating interface. It would also be cool if
that could also drive the parser being used (by defining usage
formating
Hi,
On May 18, 2009, at 10:00 AM, sebb wrote:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
Hello,
Thank you for this suggestion. Unfortunately, adding references to
parent
pom, addDefaultImplementationEntries and
addDefaultSpecificationEntries creates a
manifest file which includes OSGi
sebb wrote:
On 18/05/2009, c...@apache.org c...@apache.org wrote:
Author: ceki
Date: Mon May 18 16:47:32 2009
New Revision: 776006
URL: http://svn.apache.org/viewvc?rev=776006view=rev
Log:
name correction
Huh?
My bad. I has forgotten to save my changes in the editor before
--- On Mon, 5/18/09, Craig L Russell craig.russ...@sun.com wrote:
From: Craig L Russell craig.russ...@sun.com
Subject: Re: commons-logging version 0.0.0-EMPTY
To: Commons Developers List dev@commons.apache.org
Date: Monday, May 18, 2009, 12:18 PM
Hi,
On May 18, 2009, at 10:00 AM, sebb
Craig L Russell wrote:
Just for my information, why is it not desirable to package this as an
OSGi compliant jar?
Because we would not want an empty bundle containing no classes to
usurp the place of the real commons-logging OSGi bundle.
Also, why is the maven group id commons-logging and
sebb wrote:
I just tried, and using the default tags works OK for me.
What default tags have you tried exactly?
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
Thanks, Matt and Ceki. It's all clear now.
Craig
On May 18, 2009, at 10:29 AM, Ceki Gulcu wrote:
Craig L Russell wrote:
Just for my information, why is it not desirable to package this as
an OSGi compliant jar?
Because we would not want an empty bundle containing no classes to
usurp the
+1
Could build from the src package running all tests with my complete compiler
zoo.
- Jörg
Christian Grobmeier wrote:
Hi all,
RC2 is based on SVN revision: 774630
It includes minor changes on the site, corrects svn properties and
makes a testcase run on win xp.
Please vote:
Tag:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
sebb wrote:
I just tried, and using the default tags works OK for me.
What default tags have you tried exactly?
The manifest ones I mentioned:
manifest
sebb wrote:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
sebb wrote:
I just tried, and using the default tags works OK for me.
What default tags have you tried exactly?
The manifest ones I mentioned:
manifest
The relevant element should have been inserted within manifest element and not
manifestEntries. Issue solved now. Thank you for your help.
Ceki Gulcu wrote:
sebb wrote:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
sebb wrote:
I just tried, and using the default tags works OK for me.
Mohammady Mahdy wrote:
Thanks ^^
On Mon, May 18, 2009 at 3:06 PM, Christian Grobmeier
grobme...@gmail.comwrote:
The link from:
http://commons.apache.org/resources/source-repository.html is
working correctly.
The browse link on: http://commons.apache.org/resources/ is not though.
This
Ceki Gulcu wrote:
Hello all,
I have created an empty Maven project with groupId commons-logging,
artifactId commons-logging and version 0.0.0-EMPTY. There is very
little content (around 500 bytes) in the whole project. This is to be
expected as the original aim was to produce an empty jar
Craig L Russell wrote:
Hi,
On May 18, 2009, at 10:00 AM, sebb wrote:
On 18/05/2009, Ceki Gulcu c...@qos.ch wrote:
Hello,
Thank you for this suggestion. Unfortunately, adding references to
parent
pom, addDefaultImplementationEntries and
addDefaultSpecificationEntries creates a
also +1 from me!
On Mon, May 18, 2009 at 19:39, Jörg Schaible joerg.schai...@gmx.de wrote:
+1
Could build from the src package running all tests with my complete compiler
zoo.
- Jörg
Christian Grobmeier wrote:
Hi all,
RC2 is based on SVN revision: 774630
It includes minor changes on
Sounds good. If no one does it, I'll make the SVN karma change tonight
to add you to the sandbox. If you have karma to do that, feel free.
General approach for proper is to either work on a dev proposal in
sandbox if you have a lot, or to work on issues in JIRA via patches.
Hen
On Mon, May 18,
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=191999projectId=116
Build statistics:
State: Failed
Previous State: Ok
Started at: Mon 18 May 2009 13:31:41 -0700
Finished at: Mon 18 May 2009 13:34:02 -0700
Total time: 2m 21s
Build Trigger: Schedule
Phil Steitz wrote:
Mark Thomas wrote:
I have finished working my way through the open POOL bugs.
Of the remaining issues, 2 are bugs that only affect the 2.0 branch and
rest are improvements.
Given that Tomcat is waiting on a DBCP release and DBCP is waiting on a
POOL release I would like
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=192004projectId=116
Build statistics:
State: Ok
Previous State: Failed
Started at: Mon 18 May 2009 14:31:30 -0700
Finished at: Mon 18 May 2009 14:33:39 -0700
Total time: 2m 9s
Build Trigger: Schedule
Ouch! Wanted to do it but got
$ svn up
svn: REPORT of '/repos/asf/!svn/vcc/default': Could not read chunk
size: Secure connection truncated (https://svn.apache.org)
instead. Maybe try later?
Me now - bed.
cheers
--
Torsten
On Mon, May 18, 2009 at 22:29, Henri Yandell flame...@gmail.com
Matt Benson wrote:
Which still resounds with my preceding statement, though I admittedly hadn't
thought it through that far. So anytime the API changes in a breaking
way we need to jump major versions, append the new major version to the
component name for the m2 artifact, and do likewise
On May 18, 2009, at 6:10 PM, Stephen Colebourne wrote:
As a minimum, major changes require a package name change, and as
has been pointed out a maven id change.
So:
(1) minor incompatible changes (remove long deprecated methods or
fix details at the edges). These are compatible for 99%
- Original Message -
From: Sam Halliday sam.halli...@gmail.com
To: dev@commons.apache.org
Sent: Monday, May 18, 2009 4:29 AM
Subject: Re: [math] Re: commons-math, matrix-toolkits-java and consolidation
Excellent :-)
I think the consensus is to keep the sparse interfaces empty for
68 matches
Mail list logo
