On Mon, 2007-07-23 at 02:47 +0200, Dennis Lundberg wrote:
Hi
There is now a 1.1.1-SNAPSHOT of commons-logging in the Apache snapshot
repository:
http://people.apache.org/repo/m2-snapshot-repository/commons-logging/commons-logging/1.1.1-SNAPSHOT/
Please have a look at it.
We still need
the Ant testing script, because I
couldn't find a way to rewrite the MockSecurityManager so that it could
run on earlier JVMs.
Fine with me.
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
[
https://issues.apache.org/jira/browse/LOGGING-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511853
]
Simon Kitching commented on LOGGING-114:
JCL has adopted the principle that logging problems should never
;
Can someone help me?
I would guess that you have the wrong version of the activation jar in
your classpath.
Check the requirements for commons-email:
http://jakarta.apache.org/commons/email/dependencies.html
Regards,
Simon
On Sun, 2007-06-24 at 21:16 +0100, Niall Pemberton wrote:
Hi Simon,
You've been nominated to become a part of the Apache Commons PMC and the vote
has passed.
Would you be interested in accepting the nomination?
We understand that you were not in favour of the Commons TLP but,
since
not understood?
And what would a new JCL do for anyone that they could not do by just
using SLF4J via its JCL API? The SLF4J team have already done a lot of
hard work; what benefit would there be to duplicating that?
Regards,
Simon
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
a simple
JCL-to-java.util.logging mapping, as most apps should probably be using
java.util.logging now.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
on a release,
so it seems sensible to do it for 1.1.1 even if this is just a bugfix
release.
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
an existing jar and
precompiled unit tests, and just re-execute those unit tests with the
old jdk. I have been meaning to set this up for a long while now but
just cannot find the time..
Cheers,
Simon
-
To unsubscribe, e-mail
[
https://issues.apache.org/jira/browse/DIGESTER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching closed DIGESTER-29.
--
Resolution: Fixed
Fix Version/s: 1.8 Final
Fixed in 1.8 release.
[digester] Loading
CompiledExpression not completely thread-safe
-
Key: JXPATH-76
URL: https://issues.apache.org/jira/browse/JXPATH-76
Project: Commons JXPath
Issue Type: Bug
Reporter: Simon Raess
Some
[
https://issues.apache.org/jira/browse/JXPATH-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Raess updated JXPATH-76:
--
Attachment: jxpath.patch
patch fixing (some?) multithreading bugs in compiled expressions
Affects Versions: 1.2 Final
Reporter: Simon Raess
Priority: Minor
Attachments: patch2.txt
CompiledExpression did not have the methods selectNodes / selectSingleNodes.
The attached patch adds those methods.
--
This message is automatically generated by JIRA.
-
You
[
https://issues.apache.org/jira/browse/JXPATH-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Raess updated JXPATH-76:
--
Affects Version/s: 1.2 Final
CompiledExpression not completely thread-safe
[
https://issues.apache.org/jira/browse/JXPATH-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Raess updated JXPATH-77:
--
Attachment: patch2.txt
Added selectNodes / selectSingleNode to CompiledExpression
[
https://issues.apache.org/jira/browse/JXPATH-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Raess updated JXPATH-77:
--
You're right. I haven't thought about that. I've created a patched version, so
I don't really care when
[
https://issues.apache.org/jira/browse/JXPATH-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469179
]
Simon Raess commented on JXPATH-76:
---
I've thought about that solution too, but the change without synchronized
On Thu, 2007-01-11 at 21:37 -0800, Henri Yandell wrote:
Yeah, I'm quite interested in what the response is to having this in
the API. It's novel (for me), but could be interesting to release IO
as is and see what feedback we get from users on the feature.
My $0.02: I'm quite happy with an
[
https://issues.apache.org/jira/browse/BETWIXT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464413
]
Simon Kitching commented on BETWIXT-57:
---
Ok, I've made this default to true. I've also ensured that when set
On Sat, 2007-01-13 at 02:16 +0100, Dennis Lundberg wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
+1
2. Release commons-skin
processes here
are reasonably strict. Writing libraries is hard - and quite different
from writing full applications (eg tomcat, ant) or frameworks.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[
https://issues.apache.org/jira/browse/BETWIXT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463858
]
Simon Kitching commented on BETWIXT-57:
---
Robert, I see that the new useContextClassLoader attribute defaults
the Apache SVN repository.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
is about the
oldest outstanding feature request...
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/JXPATH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462419
]
Simon Raess commented on JXPATH-12:
---
I've just applied your patch to version 1.2. The reported problem is solved
[
https://issues.apache.org/jira/browse/LOGGING-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching updated LOGGING-110:
---
Fix Version/s: 2.0
Affects Version/s: (was: 1.0.4)
As there appears
[
https://issues.apache.org/jira/browse/LOGGING-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching closed LOGGING-108.
--
Resolution: Won't Fix
As no responses were received on my last comment, closing as wontfix
[
http://issues.apache.org/jira/browse/LANG-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461664
]
Simon Kitching commented on LANG-238:
-
I would agree with Stephen that an allEquals(a) method isn't likely
to a release candidate..
B. Distributions. As far as I can see we need to have source and binary
distros as well. I'll have a look at producing these with M2 as well.
That would be cool. Having a -src jarfile for the next JCL release would
be great.
Cheers,
Simon
[ http://issues.apache.org/jira/browse/LOGGING-25?page=all ]
Simon Kitching closed LOGGING-25.
-
Resolution: Fixed
That's ok David; I've done that before :-). Marking as closed/fixed.
[logging] call to getClassLoader() in LogFactoryImpl not checked
[
http://issues.apache.org/jira/browse/LOGGING-25?page=comments#action_12459088 ]
Simon Kitching commented on LOGGING-25:
---
Applying this patch would cause some undesirable side-effects. For example,
method logClassLoaderEnvironment uses
[ http://issues.apache.org/jira/browse/LOGGING-25?page=all ]
Simon Kitching reopened LOGGING-25:
---
Reopen due to report by David Smiley
[logging] call to getClassLoader() in LogFactoryImpl not checked for null
Saturday, Dec 2nd (ping if you need more time).
+0
The process followed seems to be fine, and I'm not aware of any issues,
but unfortunately don't have enough time to check the RC myself, so
don't feel I can contribute a +1.
Regards,
Simon
[ http://issues.apache.org/jira/browse/LOGGING-111?page=all ]
Simon Kitching resolved LOGGING-111.
Resolution: Fixed
Small patch to make debugging easier
Key: LOGGING-111
URL
[
http://issues.apache.org/jira/browse/LOGGING-111?page=comments#action_12451127
]
Simon Kitching commented on LOGGING-111:
Looks good to me. I've committed this patch (with a couple of extra checks for
null causes).
Thanks very much
[
http://issues.apache.org/jira/browse/LOGGING-106?page=comments#action_12451130
]
Simon Kitching commented on LOGGING-106:
Fixed by SVN r423654.
Re the last paragraph above, using an AccessController too broadly is a
security risk so
[ http://issues.apache.org/jira/browse/LOGGING-106?page=all ]
Simon Kitching resolved LOGGING-106.
Resolution: Fixed
AccessControlException when loading LogFactory class without system
properties permission
[ http://issues.apache.org/jira/browse/LOGGING-106?page=all ]
Simon Kitching reopened LOGGING-106:
AccessControlException when loading LogFactory class without system
properties permission
[ http://issues.apache.org/jira/browse/LOGGING-106?page=all ]
Simon Kitching resolved LOGGING-106.
Fix Version/s: 1.1.1
Resolution: Fixed
AccessControlException when loading LogFactory class without system
properties permission
[ http://issues.apache.org/jira/browse/LOGGING-106?page=all ]
Simon Kitching closed LOGGING-106.
--
AccessControlException when loading LogFactory class without system
properties permission
[ http://issues.apache.org/jira/browse/LOGGING-107?page=all ]
Simon Kitching resolved LOGGING-107.
Fix Version/s: 1.1.1
Resolution: Fixed
AccessController use
Key: LOGGING-107
URL
[
http://issues.apache.org/jira/browse/LOGGING-110?page=comments#action_12451136
]
Simon Kitching commented on LOGGING-110:
You're right; sorry I got a little mixed up; trying to juggle too many things
:0). What avalon doesn't support
of issues that had not been resolved have now been Resolved.
Issues that had a Fix for: 1.1.0 have been closed. The issues for
earlier releases that have been Resolved but not Closed, I have left
untouched.
Simon, would you mind adding Fix for and Resolution on the issues
that you have solved
running on my machine would be the first goal..
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, 2006-11-17 at 21:19 -0700, Wendy Smoak wrote:
On 11/17/06, Simon Kitching [EMAIL PROTECTED] wrote:
Are you saying that if you mark the dependencies optional, you get
compilation errors? That doesn't sound right.
Well, that's exactly what happens.
Found it. Optional
[
http://issues.apache.org/jira/browse/LOGGING-110?page=comments#action_12450911
]
Simon Kitching commented on LOGGING-110:
I agree it would be convenient to have a log level that can be queried and a
generic log method that takes
://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/RELEASE-NOTES.txt
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
, please put the
commons component in the subject line, eg
[jelly] need help building from source
Jelly doesn't support maven 2.x yet (pom.xml file), just maven 1.x
(project.xml).
And the command you want is:
maven package
or
maven install
not
maven jar
Regards,
Simon
On Wed, 2006
On Fri, 2006-11-17 at 18:52 -0800, Craig McClanahan wrote:
The pom.xml file for Commons Logging in the trunk has an interesting
approach to declaring dependencies, based on the existence or non-existence
of a file named commons-logging-README.txt. AFAICT, the purpose for this
is to make the
failure
/home/simon/apache/commons-svn/proper/logging/trunk/src/java/org/apache/commons/logging/impl/Log4JLogger.java:[23,24]
package org.apache.log4j does not exist
etc
If you mark it optional, it will be excluded from transitive
dependency resolution when a project depends on commons
the test under m1). Any more details
about your setup or other clues?
Works for me too (Sun java 1.5.0 on Linux).
Initially it would look like the xml parser in use is behaving
differently from what most people get.
What JVM are you using - not gcj by any chance?
Cheers,
Simon
Hi Rahul,
On Thu, 2006-11-09 at 13:44 -0500, Rahul Akolkar wrote:
On 9/25/06, Simon Kitching (JIRA) [EMAIL PROTECTED] wrote:
snip/
It's probably a good time; a couple of minor bugfixes/enhancements have
been made that deserve release (see RELEASE-NOTES.txt).
snap/
Coming back
On Mon, 2006-11-06 at 18:47 +0100, Dennis Lundberg wrote:
Hello
This is a new vote following up on the failed vote [1] that was held
previously.
As far as I can tell, all the issues that were raised in the earlier
vote has been addressed. So please cast your votes.
This vote will be
This is the old-style license header. The new style is as shown at the
top of this file:
http://svn.apache.org/repos/asf/jakarta/commons/proper/digester/trunk/build.xml
Regards,
Simon
On Tue, 2006-11-07 at 06:39 +, [EMAIL PROTECTED] wrote:
Author: jochen
Date: Mon Nov 6 22:39:17 2006
On Tue, 2006-11-07 at 07:43 +0100, Jochen Wiedmann wrote:
On 11/7/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
c) The svn log is confident [1] the antrun bit is needed due to a bug
in the source plugin, but subsequent conversations not so [2]. What is
it, IYO? Figure you're as good a resource
currently going on for a Betwixt release. It would be
nice to have maven2 support for that too...
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
http://issues.apache.org/jira/browse/BEANUTILS-255?page=comments#action_12446722
]
Simon Kitching commented on BEANUTILS-255:
--
I'm not sure this is a good idea.
Presumably this converter would use the system locale to determine how
[
http://issues.apache.org/jira/browse/DIGESTER-109?page=comments#action_12446203
]
Simon Kitching commented on DIGESTER-109:
-
I'd be keener to implement support for null classloaders if I could think of a
sane reason for putting
Hi,
I'd like to enable building of digester with maven2. Any suggestions as
to which commons project's pom.xml I should base it on? I know some work
has been going on for maven2 support recently..
Thanks,
Simon
[
http://issues.apache.org/jira/browse/DIGESTER-109?page=comments#action_12444275
]
Simon Kitching commented on DIGESTER-109:
-
I suggest trying this:
cd $JAVA_HOME/jre
find . -name *.jar
There should *not* be any commons libraries
[ http://issues.apache.org/jira/browse/DIGESTER-109?page=all ]
Simon Kitching updated DIGESTER-109:
Summary: FromXmlRuleSet and SetNextRule classloader issue (was:
FromXmlRuleSet and SetNextRule classes not working in Unix enviroment)
Hi
[
http://issues.apache.org/jira/browse/DIGESTER-109?page=comments#action_12443997
]
Simon Kitching commented on DIGESTER-109:
-
Good point Henri.
I had assumed that the NullPointerException Anna was reporting in
FromXmlRuleSet
+1
On Sun, 2006-10-15 at 15:44 +0200, Jochen Wiedmann wrote:
Hi,
AFAIK the policy is still that three votes of PMC members are
required. In other words, may I point you to
http://marc.theaimsgroup.com/?t=11606631873
and ask kindly for positive votes? (Unless you have reason for
operation is much less
critical.
Of course I'm open to persuasion on this (eg performance stats)..
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
are garbage collected much more reliably from
what I understand. And, as Simon pointed out, the probable disk i/o would
be the big bottleneck, not the object instantiation.
Ok, so next issue: this member is declared protected:
static protected DateFormat dateFormatter = null
committed R464108 which implements the synchronized fix.
All comments welcome.
Regards,
Simon
On Sun, 2006-10-15 at 15:50 +1300, Simon Kitching wrote:
On Sat, 2006-10-14 at 08:07 -0400, James Carman wrote:
Tomcat had this same issue a while back. It was trying to use a single
SimpleDateFormat
performance than
creating one new in every log invocation.
Just my 2 cents,
Thanks,
Ken
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 11, 2006 5:05 AM
To: Jakarta Commons Developers List
Subject: Re: Logging: SimpleLog not thread-safe
which may not be noticed anyway.
But it should be fixed; I'll try to do that this weekend.
Regards,
Simon
On Fri, 2006-10-06 at 17:15 +0100, Martin Wilson wrote:
Hi,
I'm not sure if anyone else uses the SimpleLog class - anyway I've
noticed that SimpleLog.log is not thread-safe
[
http://issues.apache.org/jira/browse/DIGESTER-107?page=comments#action_12437643
]
Simon Kitching commented on DIGESTER-107:
-
Looks good to me. I´d be happy for this to be committed.
I guess you'll be asking about when a new Digester
[
http://issues.apache.org/jira/browse/DIGESTER-107?page=comments#action_12437190
]
Simon Kitching commented on DIGESTER-107:
-
Ok, let's go with the simplest patch (no caching).
I don't think the code should be catching and ignoring
[
http://issues.apache.org/jira/browse/DIGESTER-107?page=comments#action_12437112
]
Simon Kitching commented on DIGESTER-107:
-
This looks pretty good to me. The only question I have is whether the new
members of the Digester class
Sorry, text and xml are the only clirr formats supported as far as I
know (last time I looked). The text output is fairly readable though not
pretty I agree.
I'm not sure how well clirr handles java 1.5.
Cheers,
Simon
On Wed, 2006-09-13 at 11:14 +0100, Rory Winston wrote:
Sure,
I can
mechanism for handling
multiple versions of the same library (as Microsoft's CLR has I
believe)..
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://issues.apache.org/jira/browse/BEANUTILS-245?page=all ]
Simon Kitching closed BEANUTILS-245.
Resolution: Invalid
Closing as requested by original poster.
Problem setting nested index property or combined property (with index
property
MutableBigDecimal and MutableBigInteger
---
Key: LANG-276
URL: http://issues.apache.org/jira/browse/LANG-276
Project: Commons Lang
Issue Type: New Feature
Reporter: Simon Kitching
the whole combined work, but that doesn't
necessarily correspond to copyright on any particular part. That means
that there is no need to update the copyright in files before a release.
Regards,
Simon
-
To unsubscribe, e-mail
,
Simon
On Mon, 2006-08-21 at 07:26 -0400, Mark Thomas wrote:
Simon Kitching wrote:
Firstly, the 1.1.0 release of commons-logging will hopefully not have
this problem; you don't indicate what version of commons-logging is
present when this problem occurs. Could you try upgrading the JCL
isn't it? I must be missing something..will think about
it some more.
Mark, what specifically is your issue here? Are you a tomcat developer,
or trying to write webapps to run on tomcat, or something else?
Regards,
Simon
On Sun, 2006-08-20 at 19:36 -0400, Mark Thomas wrote:
Hi,
The most
for commons-logging-api.jar without modifications.
Regards,
Simon
On Fri, 2006-08-11 at 21:03 +0200, Dennis Lundberg wrote:
Carlos Sanchez wrote:
If it's this one
http://svn.apache.org/viewvc/jakarta/commons/proper/logging/trunk/commons-logging-api.pom?view=markup
Yes, that's the one
On Tue, 2006-08-01 at 06:17 +, [EMAIL PROTECTED] wrote:
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/attributes/trunk/api/manifest.mf?rev=427459view=auto
==
+X-Compile-Source-JDK: 1.4
maven1. I'm planning on creating a
maven2 buildfile for Digester soon, and maybe a few others.
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
extracting it as a project of the logging.apache.org group?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
API (probably bound to JULI,
which is a java.util.logging implementation). I think SLF4J even offers
an implementation of the JCL api that maps to SLF4J adapters.
Regards,
Simon
On Fri, 2006-07-28 at 10:14 -0400, James Carman wrote:
Regardless, it's still not an ASF project. We should try
agree that a minimal first
release is a good idea.
BTW, I generally like maven2. For certain special projects (eg
logging) it can be awkward but for most projects the rewards are well
worth the learning curve.
Regards,
Simon
On Tue, 2006-07-25 at 09:13 +, [EMAIL PROTECTED] wrote:
Author: dennisl
Date: Tue Jul 25 02:13:44 2006
New Revision: 425343
URL: http://svn.apache.org/viewvc?rev=425343view=rev
Log:
Add trailing slashes to URLs.
- urlhttp://jakarta.apache.org/commons/logging/url
+
has.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
to all lists in one go. As
far as I know, though, the apache system doesn't provide this.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
http://issues.apache.org/jira/browse/COLLECTIONS-218?page=comments#action_12422391
]
Simon Kitching commented on COLLECTIONS-218:
I was a little surprised by the comment that changing void-non-void was binary
incompatible, so I
Hi,
I don't appear to be able to close JIRA issues for LOGGING. Do I need to
explicitly be granted privileges for this?
If so, could someone please do so?
Thanks,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED
[ http://issues.apache.org/jira/browse/LOGGING-25?page=all ]
Simon Kitching closed LOGGING-25.
-
Resolution: Fixed
As there has been no response from original poster, this is being closed
presumed fixed.
[logging] call to getClassLoader
[
http://issues.apache.org/jira/browse/LOGGING-108?page=comments#action_12422527
]
Simon Kitching commented on LOGGING-108:
Thanks for reporting this. Your analyis is excellent, thanks.
however I think this is really the responsibility
in, I would
like to hear from them.
That's an excellent idea..
Brett, what's the feedback on the split of the Maven list? Why do you
think it was a good idea?
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED
?
It would seem to me that secure data obtained via an AccessController
should never be permitted to propagate out of any non-private method.
Comments anyone?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
what's ok.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
in.
Regards,
Simon
On Thu, 2006-06-22 at 19:47 +0200, Ortwin Glück wrote:
Neelesh,
Please see http://jakarta.apache.org/commons/httpclient/dependencies.html
for the correct version of the dependencies.
Note: HttpClient is no longer in Jakarta Commons. Our mailing lists are
these:
http
Logging
Type: Bug
Versions: 1.1.0
Reporter: Simon Kitching
The LogFactory static initializer calls createFactoryStore which calls
System.getProperty. If the class doesn't have access rights to see system
properties (eg when in an applet) then the LogFactory class cannot load
AccessController use
Key: LOGGING-107
URL: http://issues.apache.org/jira/browse/LOGGING-107
Project: Commons Logging
Type: Bug
Versions: 1.1 Final
Reporter: Simon Kitching
A problem has been reported with 1.1 by Aaron Bruegl on 6
that it's a shame there is no decent search facility though. I
thought that last year's Google Summer of Code included a project to
enhance the apache http mod_mbox to provide search functionality. Do I
remember wrong, or did that project not work out?
Cheers,
Simon
the release happens.
Making a tag in subversion has exactly the same price as checking in one
new file, ie is trivial. I think the existing release advice is
therefore good; creating a tag for an RC should be the regular
practice.
Cheers,
Simon
1 - 100 of 826 matches
Mail list logo
