date:20120227

hello,

 Or are you afraid, that I
 get the feeling that I wasted my time, if you disagree with my proposed
 changes?


exactly. Already experienced that frustration, so better holding-on sometimes.


 If you are worried about my spare time, let me just say it was just fun
 working with the source. Even if you don't like the patch, that is no
 problem for me. I'm not offended or something. :)


nice to know, that makes the difference between passionates and mercenaries :)

keep in touch, alles gute,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



 Or are you afraid, that I
 get the feeling that I wasted my time, if you disagree with my proposed
 changes?

 As you said, it is just a proposal. Even if I had write access to the svn I
 wouldn't have commited such a big change without discussing it. I had some
 spare time this weekend so I just wanted to try my ideas out. I guess a
 patch is a better basis for discussion than just outlining what I had in
 mind (you can see it the other way around: I had an idea I wanted to
 discuss, so I wrote a patch). If you disagree with (parts) of the
 modifications, I'll just adjust the patch and submit it again.


 _I think it is the right thing to do_ doesn't mean that *it is*.


 That is why I wrote I think ;)


 I'll let you know as soon as I get the chance to have a look at your
 patches, and provide you feedbacks.


 TIA!
 Benedikt


 [BeanUtils2] Replace NullPointerExceptions been thrown in
 DefaultBeanAccessor with NoSuchMethodEceptions

 

                 Key: SANDBOX-397
                 URL: https://issues.apache.org/jira/browse/SANDBOX-397
             Project: Commons Sandbox
          Issue Type: Task
          Components: BeanUtils2
    Affects Versions: Nightly Builds
            Reporter: Benedikt Ritter
         Attachments: SANDBOX-397.txt, SANDBOX-397_SRP.txt,
 SANDBOX-397_SRPv2.txt


 At the moment, methods in {{DefaultBeanAccessor}} throw a
 {{NullPointerException}}, if no {{PropertyDescriptor}} for a given property
 name can be retrieved. As discussed on the ML (see
 http://markmail.org/thread/zlehclmybp5xgn5n) this behavior should be changed
 to throwing {{NoSuchMethodException}}.


 --
 This message is automatically generated by JIRA.
 If you think it was sent incorrectly, please contact your JIRA
 administrators:
 https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
 For more information on JIRA, see: http://www.atlassian.com/software/jira




 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [math] LocalizedFormats.DIVISION_BY_ZERO?

On Mon, Feb 27, 2012 at 07:28:30AM +0100, Sébastien Brisard wrote:
 Hello,
 while working on MATH-755, I've noticed that there is no error message
 corresponding to a division by zero. So for the time being, when such
 a situation occurs, I use ZERO_NOT_ALLOWED, but I was considering
 adding an entry DIVISION_BY_ZERO to LocalizedFormats. What do you
 think? I could do this fairly quickly, in order not to interfere with
 the current release process.

There are several (overlapping) entries, a.o.:

FRACTION(fraction), /* keep */
DENOMINATOR(denominator), /* keep */
ZERO_DENOMINATOR(denominator must be different from 0),
ZERO_DENOMINATOR_IN_FRACTION(zero denominator in fraction {0}/{1}),
ZERO_FRACTION_TO_DIVIDE_BY(the fraction to divide by must not be zero: 
{0}/{1}),
ZERO_NOT_ALLOWED(zero not allowed here);
IDENTICAL_ABSCISSAS_DIVISION_BY_ZERO(identical abscissas x[{0}] == x[{1}] 
== {2} cause division by zero),

My preference would be to rationalize, using the ExceptionContext to add
more information where needed. E.g. something like:

   MathArithmeticException iae = new 
MathArithmeticException(LocalizedFormats.FRACTION);
   iae.getContext().addMessage(LocalizedFormats.DENOMINATOR);
   iae.getContext().addMessage(LocalizedFormats.ZERO_NOT_ALLOWED);

But, if DIVISION_BY_ZERO is going to be used in several places, it might
be good to add it. [Still, the redundant entries should at some point be
removed (their use being replaced by a combination of the basic ones).]


Best,
Gilles

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [math] LocalizedFormats.DIVISION_BY_ZERO?

On Mon, Feb 27, 2012 at 12:17:36PM +0100, Sébastien Brisard wrote:
 Hello,
 
 2012/2/27 Gilles Sadowski gil...@harfang.homelinux.org:
  On Mon, Feb 27, 2012 at 07:28:30AM +0100, Sébastien Brisard wrote:
  Hello,
  while working on MATH-755, I've noticed that there is no error message
  corresponding to a division by zero. So for the time being, when such
  a situation occurs, I use ZERO_NOT_ALLOWED, but I was considering
  adding an entry DIVISION_BY_ZERO to LocalizedFormats. What do you
  think? I could do this fairly quickly, in order not to interfere with
  the current release process.
 
  There are several (overlapping) entries, a.o.:
 
     FRACTION(fraction), /* keep */
     DENOMINATOR(denominator), /* keep */
     ZERO_DENOMINATOR(denominator must be different from 0),
     ZERO_DENOMINATOR_IN_FRACTION(zero denominator in fraction {0}/{1}),
     ZERO_FRACTION_TO_DIVIDE_BY(the fraction to divide by must not be zero: 
  {0}/{1}),
     ZERO_NOT_ALLOWED(zero not allowed here);
     IDENTICAL_ABSCISSAS_DIVISION_BY_ZERO(identical abscissas x[{0}] == 
  x[{1}] == {2} cause division by zero),
 
  My preference would be to rationalize, using the ExceptionContext to add
  more information where needed. E.g. something like:
 
    MathArithmeticException iae = new 
  MathArithmeticException(LocalizedFormats.FRACTION);
    iae.getContext().addMessage(LocalizedFormats.DENOMINATOR);
    iae.getContext().addMessage(LocalizedFormats.ZERO_NOT_ALLOWED);
 
 I like this use of the context.
 
 
  But, if DIVISION_BY_ZERO is going to be used in several places, it might
  be good to add it. [Still, the redundant entries should at some point be
  removed (their use being replaced by a combination of the basic ones).]
 
 I have to say that my preference would be to have DIVISION_BY_ZERO as
 a master message, as it is pretty self-explanatory (and also
 standard across different libraries/softwares). Additional messages
 (like FRACTION, or DENOMINATOR) would be provided as context (if they
 do turn out to be informative). This is my preference,

OK.

 but in fact,
 any option suits me fine, provided that we do rationalize.

OK. OK. ;-)

 As this is
 not an API change, this can certainly wait. Shall I open a new ticket,
 or keep MATH-755 open for this purpose? (MATH-755 is supposed to fix
 3.1 anyway).

You can keep it open, or maybe you'll solve it too before the release...


Regards,
Gilles

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Math] Toward releasing 3.0 ?

On Sat, Feb 25, 2012 at 12:25:49PM +, sebb wrote:
 On 25 February 2012 09:59, Gilles Sadowski gil...@harfang.homelinux.org 
 wrote:
  Hello.
 
  
   How do we proceed from here in order to release 3.0? Cf. ticket MATH-746,
   Things to do before releasing 3.0.
 
  Sorry for being late on this.
 
  
   Can we start to talk about an expected release date?
 
  I guess you did a wonderful job for closing everything. As it is clean
  enough, I think we could even skip the step of using a release branch
  and we could simply tag the release candidates from the trunk. This
  would simply imply refraining from any change which is not related to
  the release for a few days.
 
  Someone has to volunteer to act as the release manager. The task is
  simply to perform the few commands described for example here:
  http://wiki.apache.org/commons/UsingNexus. The release manager also
  signs the packages using a gpg key, which should be put in the global
  KEYS file. This file can be retrieved using the following svn command:
 
  svn checkout --depth=immediates \
    https://[your-commiter-id]@svn.apache.org/repos/asf/commons/trunks-proper
 
  The artifacts for the release candidate must be made available and a
  VOTE thread must be started on the dev list for at least 72 hours (see
  http://www.apache.org/foundation/voting.html). There can be several
  release candidate before a version finally goes out (when I release
  version 2.0 I think, we needed 6 candidates ...). When the vote passes,
  the exact artifacts which were used for voting will be published by
  uploading the source and binary zip and tar files and by promoting the
  maven artifacts with Nexus. Not a single bit is changed (this would
  change the gpg signatures). This means that for example the release date
  which appears in the release notes must be estimated before the vote
  taking the voting delay into account (plus one or two days as a safety
  margin) and it must be updated as each release candidate is cut.
 
  So there is no predefined release date until the vote finally passes.
 
  At the pace at which you go now, I would say we could target a first
  release candidate early next week.
 
  Any volunteer as release manager ?
 
  OK, I started to try the commands listed in the UsingNexus file. Not
  everything works directly... [maven2 could not find a plugin, which led me
 
 Which plugin?

I couldn't tell you now because installing maven3 implied desinstalling
maven2.

 
  to upgrade to maven3, which printed a warning about parent being a broken
  project, etc.]

This is the warning from maven3:
---CUT---
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.commons:commons-math3:jar:3.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-idea-plugin is missing. 
@org.apache.commons:commons-parent:20, 
/home/eran/.m2/repository/org/apache/commons/commons-parent/20/commons-parent-20.pom,
 line 316, column 15
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
---CUT---

 
  I don't know maven (apart from the basics to build CM) so, it is not always
  obvious which are the mandatory steps and what result must be observed in
  order to check that everything went fine...
 
  For the encryption key: I was always advised against writing a passphrase in
  clear in a file; maven seems to support asking for the passphrase but when
  it prints:
  ---CUT---
  Enter passphrase: gpg: gpg-agent is not available in this session
  ---CUT---
  When I enter the passphrase, it just prints that same message again...
 
 Works for me using Maven 2.2.1 and 3.0.4

Maven version is also 3.0.4 here.

 
 Which version of gpg have you installed locally?

---CUT---
$ gpg --version
gpg (GnuPG) 1.4.11
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, 
CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
---CUT---

 
 To test it out, just use
 
 mvn gpg:sign
 
 It will fail later as it needs package first.

This seems to work (if this is where you expected it to fail); it produces:
---CUT---
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.commons:commons-math3:jar:3.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-idea-plugin is missing.

[Commons Wiki] Update of MathWishList by monnoo

2012-02-27 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Commons Wiki for 
change notification.

The MathWishList page has been changed by monnoo:
http://wiki.apache.org/commons/MathWishList?action=diffrev1=70rev2=71

  ##language:en
  = Commons-Math Wish List =
  A list of feature requests made by Commons-Math users, contributors, and 
committers.  These requests will be considered when deciding on new 
functionality for future releases.  At any time, additional feature requests 
can be added simply by editing this page.
+ 
-  * Add more special math functions such as Bessel functions and so on. 
+  * Add more special math functions such as Bessel functions and so on.
   * Add support for iterative linear solvers (see discussion 
[[http://mail-archives.apache.org/mod_mbox/commons-dev/201104.mbox/20110413062230.2b0e414059...@svoboda.polytechnique.org|http://mail-archives.apache.org/mod_mbox/commons-dev/201104.mbox/%3c20110413062230.2b0e414059...@svoboda.polytechnique.org%3E]]):
 see wiki page IterativeLinearSolvers
   * Add remedian statistic - 
[[http://www.agoras.ua.ac.be/abstract/Remrob90.htm|The Remedian: a Robust 
Averaging method for Large Data Sets]]
   * Add ability to compute the density of normal distribution and other well 
behaved distributions (done for some distributions 
https://issues.apache.org/jira/browse/MATH-222)

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[Commons Wiki] Update of MathWishList by monnoo

2012-02-27 Thread Apache Wiki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Commons Wiki for 
change notification.

The MathWishList page has been changed by monnoo:
http://wiki.apache.org/commons/MathWishList?action=diffrev1=71rev2=72

  = Commons-Math Wish List =
  A list of feature requests made by Commons-Math users, contributors, and 
committers.  These requests will be considered when deciding on new 
functionality for future releases.  At any time, additional feature requests 
can be added simply by editing this page.
  
+  * Enabling math3.stat for ANY usage in the data mining context, there must 
be a MissingValues class that is able to be switched off, to hold a list of 
missing values, etc. This refers to any class that imports data (like 
DescriptiveStatistics or clustering); this is also mandatory for clustering in 
real-life contexts (see next entry)
+  * Enabling math3.clustering for ANY reasonable usage in the data mining 
context, there must be a small extension for the KNN++ clustering method: a 
usevector, of the same length as the variable vector, holding 0|1 and 
indicating whether a variable (column) should be used: a working versoin 
(exhibits also the MissingValues class) is prototypicall available here: 
http://code.google.com/p/noolabsimplecluster/
   * Add more special math functions such as Bessel functions and so on.
   * Add support for iterative linear solvers (see discussion 
[[http://mail-archives.apache.org/mod_mbox/commons-dev/201104.mbox/20110413062230.2b0e414059...@svoboda.polytechnique.org|http://mail-archives.apache.org/mod_mbox/commons-dev/201104.mbox/%3c20110413062230.2b0e414059...@svoboda.polytechnique.org%3E]]):
 see wiki page IterativeLinearSolvers
   * Add remedian statistic - 
[[http://www.agoras.ua.ac.be/abstract/Remrob90.htm|The Remedian: a Robust 
Averaging method for Large Data Sets]]

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: svn commit: r1293496 - /commons/proper/commons-parent/trunk/pom.xml

2012-02-27 Thread Gary Gregory

On Sat, Feb 25, 2012 at 8:14 PM, Gary Gregory garydgreg...@gmail.comwrote:

 On Feb 25, 2012, at 19:18, sebb seb...@gmail.com wrote:

  On 25 February 2012 14:46, Gary Gregory garydgreg...@gmail.com wrote:
  On Sat, Feb 25, 2012 at 9:23 AM, sebb seb...@gmail.com wrote:
 
  On 25 February 2012 14:11, Gary Gregory garydgreg...@gmail.com
 wrote:
  On Fri, Feb 24, 2012 at 8:23 PM, sebb seb...@gmail.com wrote:
 
  On 25 February 2012 00:47,  ggreg...@apache.org wrote:
  Author: ggregory
  Date: Sat Feb 25 00:47:00 2012
  New Revision: 1293496
 
  URL: http://svn.apache.org/viewvc?rev=1293496view=rev
  Log:
  Update plugins.
 
  Modified:
 commons/proper/commons-parent/trunk/pom.xml
 
  Modified: commons/proper/commons-parent/trunk/pom.xml
  URL:
 
 
 http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=1293496r1=1293495r2=1293496view=diff
 
 
 
 ==
  --- commons/proper/commons-parent/trunk/pom.xml (original)
  +++ commons/proper/commons-parent/trunk/pom.xml Sat Feb 25 00:47:00
  2012
  @@ -193,12 +193,12 @@ Version 23:
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
  -  version1.6/version
  +  version1.7/version
  /plugin
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
  -  version2.2.1/version
  +  version2.3/version
  /plugin
  plugin
groupIdorg.apache.maven.plugins/groupId
  @@ -262,7 +262,7 @@ Version 23:
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
  -  version2.2.1/version
  +  version2.2.2/version
  /plugin
  plugin
!-- TODO see above - find better way to add NL files to
  jars
  and test jars --
  @@ -318,7 +318,7 @@ Version 23:
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
!-- N.B. 2.3.5 does not work on Java 5; see profile
  java-1.5-detected for the workround --
  -  version2.3.5/version
  +  version2.3.6/version
 
  Does 2.3.6 work with java 1.5?
 
  If so, maybe the work-round can be commented out or removed?
 
 
  Sure, that makes sense.
 
  Seems to be ok for me when I build [codec] with:
 
  Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
  Maven home: C:\Java\apache-maven-3.0.4\bin\..
  Java version: 1.5.0_22, vendor: Sun Microsystems Inc.
  Java home: C:\Program Files\Java\jdk1.5.0_22\jre
  Default locale: en_US, platform encoding: Cp1252
  OS name: windows 7, version: 6.1, arch: amd64, family: windows
 
  I see:
 
  [INFO] --- maven-bundle-plugin:2.3.6:manifest (bundle-manifest) @
  commons-codec ---
 
  No stack traces or errors.
 
  Need to check M2.2.1 as well.
 
 
  Build successful with:
 
  Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
  Java version: 1.5.0_22
  Java home: C:\Program Files\Java\jdk1.5.0_22\jre
  Default locale: en_US, platform encoding: Cp1252
  OS name: windows 7 version: 6.1 arch: amd64 Family: windows
 
  Did you disable the java-1.5-detected profile?
 
  That is automatically enabled when running under Java 1.5, and selects
  earlier versions in order to fix this.


I deleted the java-1.5-detected profile in the parent POM and installed it
locally (mvn install).

Then I made [codec] use this 24-SNAPSHOT parent POM with M3 and M2 (mvn
install) and builds were successful and create jars with OSGi-looking
manifests.

So I suppose this means the java-1.5-detected profile is not needed anymore
but as I am not a Maven expert on this specific issue I'll not delete it
ATM.

Gary


 How do I disable it from the cli?

 Gary
 
  Testing with Java 1.5 and bundle 2.3.6 does not prove anything unless
  the profile override is disabled.
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
  For additional commands, e-mail: dev-h...@commons.apache.org
 




-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
JUnit in Action, 2nd Ed: http://goog_1249600977http://bit.ly/ECvg0
Spring Batch in Action: http://s.apache.org/HOqhttp://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [Math] Toward releasing 3.0 ?

On 27 February 2012 12:27, Gilles Sadowski gil...@harfang.homelinux.org wrote:
 On Sat, Feb 25, 2012 at 12:25:49PM +, sebb wrote:
 On 25 February 2012 09:59, Gilles Sadowski gil...@harfang.homelinux.org 
 wrote:
  Hello.
 
  
   How do we proceed from here in order to release 3.0? Cf. ticket 
   MATH-746,
   Things to do before releasing 3.0.
 
  Sorry for being late on this.
 
  
   Can we start to talk about an expected release date?
 
  I guess you did a wonderful job for closing everything. As it is clean
  enough, I think we could even skip the step of using a release branch
  and we could simply tag the release candidates from the trunk. This
  would simply imply refraining from any change which is not related to
  the release for a few days.
 
  Someone has to volunteer to act as the release manager. The task is
  simply to perform the few commands described for example here:
  http://wiki.apache.org/commons/UsingNexus. The release manager also
  signs the packages using a gpg key, which should be put in the global
  KEYS file. This file can be retrieved using the following svn command:
 
  svn checkout --depth=immediates \
    
  https://[your-commiter-id]@svn.apache.org/repos/asf/commons/trunks-proper
 
  The artifacts for the release candidate must be made available and a
  VOTE thread must be started on the dev list for at least 72 hours (see
  http://www.apache.org/foundation/voting.html). There can be several
  release candidate before a version finally goes out (when I release
  version 2.0 I think, we needed 6 candidates ...). When the vote passes,
  the exact artifacts which were used for voting will be published by
  uploading the source and binary zip and tar files and by promoting the
  maven artifacts with Nexus. Not a single bit is changed (this would
  change the gpg signatures). This means that for example the release date
  which appears in the release notes must be estimated before the vote
  taking the voting delay into account (plus one or two days as a safety
  margin) and it must be updated as each release candidate is cut.
 
  So there is no predefined release date until the vote finally passes.
 
  At the pace at which you go now, I would say we could target a first
  release candidate early next week.
 
  Any volunteer as release manager ?
 
  OK, I started to try the commands listed in the UsingNexus file. Not
  everything works directly... [maven2 could not find a plugin, which led me

 Which plugin?

 I couldn't tell you now because installing maven3 implied desinstalling
 maven2.

I've got both installed (Win XP) with no issues; I just change the
PATH as needed to switch between them.


  to upgrade to maven3, which printed a warning about parent being a broken
  project, etc.]

 This is the warning from maven3:
 ---CUT---
 [WARNING]
 [WARNING] Some problems were encountered while building the effective model 
 for org.apache.commons:commons-math3:jar:3.0-SNAPSHOT
 [WARNING] 'build.plugins.plugin.version' for 
 org.apache.maven.plugins:maven-idea-plugin is missing. 
 @org.apache.commons:commons-parent:20, 
 /home/eran/.m2/repository/org/apache/commons/commons-parent/20/commons-parent-20.pom,
  line 316, column 15
 [WARNING]
 [WARNING] It is highly recommended to fix these problems because they 
 threaten the stability of your build.
 [WARNING]
 [WARNING] For this reason, future Maven versions might no longer support 
 building such malformed projects.
 [WARNING]
 ---CUT---

Can ignore that - IDEA is used for reports only (if then).

 
  I don't know maven (apart from the basics to build CM) so, it is not always
  obvious which are the mandatory steps and what result must be observed in
  order to check that everything went fine...
 
  For the encryption key: I was always advised against writing a passphrase 
  in
  clear in a file; maven seems to support asking for the passphrase but when
  it prints:
  ---CUT---
  Enter passphrase: gpg: gpg-agent is not available in this session
  ---CUT---
  When I enter the passphrase, it just prints that same message again...

 Works for me using Maven 2.2.1 and 3.0.4

 Maven version is also 3.0.4 here.


 Which version of gpg have you installed locally?

 ---CUT---
 $ gpg --version
 gpg (GnuPG) 1.4.11
 Copyright (C) 2010 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later
 http://gnu.org/licenses/gpl.html
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.

 Home: ~/.gnupg
 Supported algorithms:
 Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
 Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,
        CAMELLIA192, CAMELLIA256
 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
 Compression: Uncompressed, ZIP, ZLIB, BZIP2
 ---CUT---


 To test it out, just use

 mvn gpg:sign

 It will fail later as it needs package first.

 This seems to work (if this is where you expected it to fail); it produces:
 ---CUT---

Re: svn commit: r1293496 - /commons/proper/commons-parent/trunk/pom.xml

On 27 February 2012 14:48, Gary Gregory garydgreg...@gmail.com wrote:
 On Sat, Feb 25, 2012 at 8:14 PM, Gary Gregory garydgreg...@gmail.comwrote:

 On Feb 25, 2012, at 19:18, sebb seb...@gmail.com wrote:

  On 25 February 2012 14:46, Gary Gregory garydgreg...@gmail.com wrote:
  On Sat, Feb 25, 2012 at 9:23 AM, sebb seb...@gmail.com wrote:
 
  On 25 February 2012 14:11, Gary Gregory garydgreg...@gmail.com
 wrote:
  On Fri, Feb 24, 2012 at 8:23 PM, sebb seb...@gmail.com wrote:
 
  On 25 February 2012 00:47,  ggreg...@apache.org wrote:
  Author: ggregory
  Date: Sat Feb 25 00:47:00 2012
  New Revision: 1293496
 
  URL: http://svn.apache.org/viewvc?rev=1293496view=rev
  Log:
  Update plugins.
 
  Modified:
     commons/proper/commons-parent/trunk/pom.xml
 
  Modified: commons/proper/commons-parent/trunk/pom.xml
  URL:
 
 
 http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=1293496r1=1293495r2=1293496view=diff
 
 
 
 ==
  --- commons/proper/commons-parent/trunk/pom.xml (original)
  +++ commons/proper/commons-parent/trunk/pom.xml Sat Feb 25 00:47:00
  2012
  @@ -193,12 +193,12 @@ Version 23:
          plugin
            groupIdorg.apache.maven.plugins/groupId
            artifactIdmaven-antrun-plugin/artifactId
  -          version1.6/version
  +          version1.7/version
          /plugin
          plugin
            groupIdorg.apache.maven.plugins/groupId
            artifactIdmaven-assembly-plugin/artifactId
  -          version2.2.1/version
  +          version2.3/version
          /plugin
          plugin
            groupIdorg.apache.maven.plugins/groupId
  @@ -262,7 +262,7 @@ Version 23:
          plugin
            groupIdorg.apache.maven.plugins/groupId
            artifactIdmaven-release-plugin/artifactId
  -          version2.2.1/version
  +          version2.2.2/version
          /plugin
          plugin
            !-- TODO see above - find better way to add NL files to
  jars
  and test jars --
  @@ -318,7 +318,7 @@ Version 23:
            groupIdorg.apache.felix/groupId
            artifactIdmaven-bundle-plugin/artifactId
            !-- N.B. 2.3.5 does not work on Java 5; see profile
  java-1.5-detected for the workround --
  -          version2.3.5/version
  +          version2.3.6/version
 
  Does 2.3.6 work with java 1.5?
 
  If so, maybe the work-round can be commented out or removed?
 
 
  Sure, that makes sense.
 
  Seems to be ok for me when I build [codec] with:
 
  Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
  Maven home: C:\Java\apache-maven-3.0.4\bin\..
  Java version: 1.5.0_22, vendor: Sun Microsystems Inc.
  Java home: C:\Program Files\Java\jdk1.5.0_22\jre
  Default locale: en_US, platform encoding: Cp1252
  OS name: windows 7, version: 6.1, arch: amd64, family: windows
 
  I see:
 
  [INFO] --- maven-bundle-plugin:2.3.6:manifest (bundle-manifest) @
  commons-codec ---
 
  No stack traces or errors.
 
  Need to check M2.2.1 as well.
 
 
  Build successful with:
 
  Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
  Java version: 1.5.0_22
  Java home: C:\Program Files\Java\jdk1.5.0_22\jre
  Default locale: en_US, platform encoding: Cp1252
  OS name: windows 7 version: 6.1 arch: amd64 Family: windows
 
  Did you disable the java-1.5-detected profile?
 
  That is automatically enabled when running under Java 1.5, and selects
  earlier versions in order to fix this.


 I deleted the java-1.5-detected profile in the parent POM and installed it
 locally (mvn install).

 Then I made [codec] use this 24-SNAPSHOT parent POM with M3 and M2 (mvn
 install) and builds were successful and create jars with OSGi-looking
 manifests.

 So I suppose this means the java-1.5-detected profile is not needed anymore
 but as I am not a Maven expert on this specific issue I'll not delete it
 ATM.

OK, I may have time to try it later this week;
What I intend to do is:
- disable the current override for java 1.5
- check that the bind command fails when building (IIRC, the problem
was a bind plugin dependency that was built with Java 1.6)
- update to the latest bind plugin
- check that the bind command succeeds

If anyone else can try that too, so much the better.

 Gary


 How do I disable it from the cli?

 Gary
 
  Testing with Java 1.5 and bundle 2.3.6 does not prove anything unless
  the profile override is disabled.
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
  For additional commands, e-mail: dev-h...@commons.apache.org
 




 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 JUnit in Action, 2nd Ed: http://goog_1249600977http://bit.ly/ECvg0
 Spring Batch in Action: http://s.apache.org/HOqhttp://bit.ly/bqpbCK
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory

-

[chain] release roadmap

Hi all guys!

thanks to Elijah Zupancich's contributions, we now have a fresh new
[chain] on trunk that uses generics. I can have (limited) spare time
to dedicate to [chain] and I would like to put energies on it in order
to have it released ASAP.

This is my roadmap to have [chain] released in a short time:

 * CHAIN-65
 * CHAIN-66
 * CHAIN-55

since some other issues are really old and never fixed, I'd tend to
keep them open and move to release 2.1

groupId:artifactId:version will be updated to
org.apache.common:commons-chain2:2.0

Does anyone have objections/suggestions/... ?
TIA, all the best!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: svn commit: r1293496 - /commons/proper/commons-parent/trunk/pom.xml

On 27 February 2012 15:49, sebb seb...@gmail.com wrote:
 On 27 February 2012 14:48, Gary Gregory garydgreg...@gmail.com wrote:
 On Sat, Feb 25, 2012 at 8:14 PM, Gary Gregory garydgreg...@gmail.comwrote:

 On Feb 25, 2012, at 19:18, sebb seb...@gmail.com wrote:

  On 25 February 2012 14:46, Gary Gregory garydgreg...@gmail.com wrote:
  On Sat, Feb 25, 2012 at 9:23 AM, sebb seb...@gmail.com wrote:
 
  On 25 February 2012 14:11, Gary Gregory garydgreg...@gmail.com
 wrote:
  On Fri, Feb 24, 2012 at 8:23 PM, sebb seb...@gmail.com wrote:
 
  On 25 February 2012 00:47,  ggreg...@apache.org wrote:
  Author: ggregory
  Date: Sat Feb 25 00:47:00 2012
  New Revision: 1293496
 
  URL: http://svn.apache.org/viewvc?rev=1293496view=rev
  Log:
  Update plugins.
 
  Modified:
     commons/proper/commons-parent/trunk/pom.xml
 
  Modified: commons/proper/commons-parent/trunk/pom.xml
  URL:
 
 
 http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=1293496r1=1293495r2=1293496view=diff
 
 
 
 ==
  --- commons/proper/commons-parent/trunk/pom.xml (original)
  +++ commons/proper/commons-parent/trunk/pom.xml Sat Feb 25 00:47:00
  2012
  @@ -193,12 +193,12 @@ Version 23:
          plugin
            groupIdorg.apache.maven.plugins/groupId
            artifactIdmaven-antrun-plugin/artifactId
  -          version1.6/version
  +          version1.7/version
          /plugin
          plugin
            groupIdorg.apache.maven.plugins/groupId
            artifactIdmaven-assembly-plugin/artifactId
  -          version2.2.1/version
  +          version2.3/version
          /plugin
          plugin
            groupIdorg.apache.maven.plugins/groupId
  @@ -262,7 +262,7 @@ Version 23:
          plugin
            groupIdorg.apache.maven.plugins/groupId
            artifactIdmaven-release-plugin/artifactId
  -          version2.2.1/version
  +          version2.2.2/version
          /plugin
          plugin
            !-- TODO see above - find better way to add NL files to
  jars
  and test jars --
  @@ -318,7 +318,7 @@ Version 23:
            groupIdorg.apache.felix/groupId
            artifactIdmaven-bundle-plugin/artifactId
            !-- N.B. 2.3.5 does not work on Java 5; see profile
  java-1.5-detected for the workround --
  -          version2.3.5/version
  +          version2.3.6/version
 
  Does 2.3.6 work with java 1.5?
 
  If so, maybe the work-round can be commented out or removed?
 
 
  Sure, that makes sense.
 
  Seems to be ok for me when I build [codec] with:
 
  Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
  Maven home: C:\Java\apache-maven-3.0.4\bin\..
  Java version: 1.5.0_22, vendor: Sun Microsystems Inc.
  Java home: C:\Program Files\Java\jdk1.5.0_22\jre
  Default locale: en_US, platform encoding: Cp1252
  OS name: windows 7, version: 6.1, arch: amd64, family: windows
 
  I see:
 
  [INFO] --- maven-bundle-plugin:2.3.6:manifest (bundle-manifest) @
  commons-codec ---
 
  No stack traces or errors.
 
  Need to check M2.2.1 as well.
 
 
  Build successful with:
 
  Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
  Java version: 1.5.0_22
  Java home: C:\Program Files\Java\jdk1.5.0_22\jre
  Default locale: en_US, platform encoding: Cp1252
  OS name: windows 7 version: 6.1 arch: amd64 Family: windows
 
  Did you disable the java-1.5-detected profile?
 
  That is automatically enabled when running under Java 1.5, and selects
  earlier versions in order to fix this.


 I deleted the java-1.5-detected profile in the parent POM and installed it
 locally (mvn install).

 Then I made [codec] use this 24-SNAPSHOT parent POM with M3 and M2 (mvn
 install) and builds were successful and create jars with OSGi-looking
 manifests.

 So I suppose this means the java-1.5-detected profile is not needed anymore
 but as I am not a Maven expert on this specific issue I'll not delete it
 ATM.

 OK, I may have time to try it later this week;
 What I intend to do is:
 - disable the current override for java 1.5
 - check that the bind command fails when building (IIRC, the problem
 was a bind plugin dependency that was built with Java 1.6)
 - update to the latest bind plugin
 - check that the bind command succeeds

 If anyone else can try that too, so much the better.

If I disable the 1.5 workround, for example by using

mvn bundle:manifest -P-java-1.5-detected

[i.e. no need to edit the pom to test this]

then Maven 2.2.1/Java 1.5/ Bundle 2.3.5 fails for me with

[ERROR] FATAL ERROR
[INFO] 
[INFO] java.lang.String.getBytes(Ljava/nio/charset/Charset;)[B
[INFO] 
[INFO] Trace
java.lang.NoSuchMethodError:
java.lang.String.getBytes(Ljava/nio/charset/Charset;)[B
at aQute.lib.osgi.Jar.clinit(Jar.java:290)

However, updating the bundle plugin to 2.3.6 fixes the issue, so it
does look like

[RESULT] Was: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

2012-02-27 Thread Mladen Turk


With required 3 binding +1's from Luc, Jörg and I
and one -0 from Garry I declare this vote as passed.
Will copy the artefacts to dist site and make ANN tomorrow
after the mirrors pick up.


On 02/24/2012 12:41 AM, Mladen Turk wrote:

Fixed a typo in RC1 which caused compile failure in case there
were no sys/capability.h header on the system.
The new set of artefacts [1] and site [2] are at usual place
based on tag [3]


Please vote (vote will remain open for at least 72 hours).

Apache Commons Daemon 1.0.10 is
[ ] +1 Release
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...


[1] http://people.apache.org/~mturk/daemon-1.0.10/
[2] http://people.apache.org/~mturk/daemon-1.0.10-site/
[3] 
https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_10_RC2/



Regards
--
^TM

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [RESULT] Was: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

On 27 February 2012 17:10, Mladen Turk mt...@apache.org wrote:
 With required 3 binding +1's from Luc, Jörg and I
 and one -0 from Garry I declare this vote as passed.
 Will copy the artefacts to dist site and make ANN tomorrow
 after the mirrors pick up.

Can you also release the jar to Maven please?


 On 02/24/2012 12:41 AM, Mladen Turk wrote:

 Fixed a typo in RC1 which caused compile failure in case there
 were no sys/capability.h header on the system.
 The new set of artefacts [1] and site [2] are at usual place
 based on tag [3]


 Please vote (vote will remain open for at least 72 hours).

 Apache Commons Daemon 1.0.10 is
 [ ] +1 Release
 [ ] +0 OK, but...
 [ ] -0 OK, but really should fix...
 [ ] -1 I oppose this release because...


 [1] http://people.apache.org/~mturk/daemon-1.0.10/
 [2] http://people.apache.org/~mturk/daemon-1.0.10-site/
 [3]
 https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_10_RC2/


 Regards
 --
 ^TM

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: svn commit: r1294233 - in /commons/proper/daemon/branches/1.0.x: ./ src/native/unix/native/ src/native/windows/apps/prunmgr/ src/native/windows/apps/prunsrv/

On 27 February 2012 17:17,  mt...@apache.org wrote:
 Author: mturk
 Date: Mon Feb 27 17:17:10 2012
 New Revision: 1294233

 URL: http://svn.apache.org/viewvc?rev=1294233view=rev
 Log:
 Bump the version numbers

 Modified:
    commons/proper/daemon/branches/1.0.x/build.xml
    commons/proper/daemon/branches/1.0.x/pom.xml
    commons/proper/daemon/branches/1.0.x/src/native/unix/native/version.h
    
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.h
    
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.rc
    
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunsrv/prunsrv.h
    
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunsrv/prunsrv.rc

 Modified: commons/proper/daemon/branches/1.0.x/build.xml
 URL: 
 http://svn.apache.org/viewvc/commons/proper/daemon/branches/1.0.x/build.xml?rev=1294233r1=1294232r2=1294233view=diff
 ==
 --- commons/proper/daemon/branches/1.0.x/build.xml (original)
 +++ commons/proper/daemon/branches/1.0.x/build.xml Mon Feb 27 17:17:10 2012
 @@ -59,7 +59,7 @@
   property name=component.title         value=Java Daemons/

   !-- The current version number of this component --
 -  property name=component.version       value=1.0.10/
 +  property name=component.version       value=1.0.11-SNAPSHOT/

   !-- The base directory for compilation targets --
   property name=build.home              value=target/

 Modified: commons/proper/daemon/branches/1.0.x/pom.xml
 URL: 
 http://svn.apache.org/viewvc/commons/proper/daemon/branches/1.0.x/pom.xml?rev=1294233r1=1294232r2=1294233view=diff
 ==
 --- commons/proper/daemon/branches/1.0.x/pom.xml (original)
 +++ commons/proper/daemon/branches/1.0.x/pom.xml Mon Feb 27 17:17:10 2012
 @@ -27,7 +27,7 @@
   modelVersion4.0.0/modelVersion
   groupIdcommons-daemon/groupId
   artifactIdcommons-daemon/artifactId
 -  version1.0.10/version
 +  version1.0.11-SNAPSHOT/version
   nameCommons Daemon/name
   !-- Daemon started in Commons in 2002 with an import of code from Tomcat,
        which is why the NOTICE file has an earlier date than the 
 inceptionYear --
 @@ -92,7 +92,7 @@
     maven.compile.source1.3/maven.compile.source
     maven.compile.target1.3/maven.compile.target
     commons.componentiddaemon/commons.componentid
 -    commons.release.version1.0.10/commons.release.version
 +    commons.release.version1.0.11-SNAPSHOT/commons.release.version

Since this property is used for releases only, the -SNAPSHOT suffix is
not needed here.

     commons.jira.idDAEMON/commons.jira.id
     commons.jira.pid12310468/commons.jira.pid
   /properties

 Modified: 
 commons/proper/daemon/branches/1.0.x/src/native/unix/native/version.h
 URL: 
 http://svn.apache.org/viewvc/commons/proper/daemon/branches/1.0.x/src/native/unix/native/version.h?rev=1294233r1=1294232r2=1294233view=diff
 ==
 --- commons/proper/daemon/branches/1.0.x/src/native/unix/native/version.h 
 (original)
 +++ commons/proper/daemon/branches/1.0.x/src/native/unix/native/version.h Mon 
 Feb 27 17:17:10 2012
 @@ -31,13 +31,13 @@
  #define JSVC_MINOR_VERSION      0

  /** patch level */
 -#define JSVC_PATCH_VERSION     10
 +#define JSVC_PATCH_VERSION     11

  /**
  *  This symbol is defined for internal, development copies of JSVC.
  *  This symbol will be #undef'd for releases.
  */
 -#define JSVC_IS_DEV_VERSION     0
 +#define JSVC_IS_DEV_VERSION     1

  /** Properly quote a value as a string in the C preprocessor */
  #define JSVC_STRINGIFY(n) JSVC_STRINGIFY_HELPER(n)

 Modified: 
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.h
 URL: 
 http://svn.apache.org/viewvc/commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.h?rev=1294233r1=1294232r2=1294233view=diff
 ==
 --- 
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.h
  (original)
 +++ 
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.h
  Mon Feb 27 17:17:10 2012
 @@ -24,7 +24,7 @@
  #define _PRUNMGR_H

  #undef  PRG_VERSION
 -#define PRG_VERSION    1.0.10.0
 +#define PRG_VERSION    1.0.11.0
  #define PRG_REGROOT   LApache Software Foundation\\Procrun 2.0

  #define IDM_TM_EXIT                     2000

 Modified: 
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.rc
 URL: 
 http://svn.apache.org/viewvc/commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.rc?rev=1294233r1=1294232r2=1294233view=diff
 ==
 --- 
 commons/proper/daemon/branches/1.0.x/src/native/windows/apps/prunmgr/prunmgr.rc
  (original)
 +++

Re: [RESULT] Was: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

2012-02-27 Thread Mladen Turk


On 02/27/2012 06:14 PM, sebb wrote:

Can you also release the jar to Maven please?


Sure, already did steps described at
http://commons.apache.org/releases/release.html

files are already inside
/x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-daemon
and maven-metadata.xml updated.

According to the release.html this should sync to repo1.maven.org
(if the instructions are valid of course)


Regards
--
^TM

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [graph] Doubts on DFS algorithm implementation

2012-02-27 Thread Claudio Squarcella


Hi,


[...] Also, I don't know if we have an abstraction for
this, but the order in which you add your connected vertices can be
important, too (might want to do a greedy bfs/dfs).


+1.
So far the algorithm has no control over that, as it simply scans an 
IteratorV of adjacent vertices.


--
Claudio Squarcella
PhD student at Roma Tre University
http://www.dia.uniroma3.it/~squarcel
http://squarcella.com/


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [chain] release roadmap

2012-02-27 Thread Elijah Zupancic

Hi Simo,

Here is my comment from the ticket: My plan is to take this on. I'm
just very busy at work right now, so I've been trying to learn docbook
format on the bus on my way to and from work. If you want to take on
breaking chain into separate modules, that would be much appreciated.

-Elijah

On Mon, Feb 27, 2012 at 8:58 AM, Simone Tripodi
simonetrip...@apache.org wrote:

 Hi all guys!

 thanks to Elijah Zupancich's contributions, we now have a fresh new
 [chain] on trunk that uses generics. I can have (limited) spare time
 to dedicate to [chain] and I would like to put energies on it in order
 to have it released ASAP.

 This is my roadmap to have [chain] released in a short time:

  * CHAIN-65
  * CHAIN-66
  * CHAIN-55

 since some other issues are really old and never fixed, I'd tend to
 keep them open and move to release 2.1

 groupId:artifactId:version will be updated to
 org.apache.common:commons-chain2:2.0

 Does anyone have objections/suggestions/... ?
 TIA, all the best!
 -Simo

 http://people.apache.org/~simonetripodi/
 http://simonetripodi.livejournal.com/
 http://twitter.com/simonetripodi
 http://www.99soft.org/

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [graph] Doubts on DFS algorithm implementation

2012-02-27 Thread Claudio Squarcella

Hello,

the method discoveryEdge currently tells whether or not the algorithm should explore a
subtree/branch and add related vertices to the stack/queue. So I see no conflict in the implementation. Maybe
you are saying that the edge should be explored *right before* the vertex it leads to -- but why? AFAIK a
standard graph search is only concerned with *vertices*. In that sense finishEdge becomes
useless, as the responsibility for returning prematurely is entirely covered by finishVertex. Am
I raving mad? :-)

yes you are right, the visit should be only concerned the vertices, but in our
implementation we added also the discoveryEdge that in a dfs has invoked like a
BFS. This in my opinion can be frustrating for the user because the edge is not
visit in depth but in breadth.
So IMHO we should visit also the edge in depth, (only in a dfs of course) or
remove the invocation of discover/finish edge that can get confused the user.

if you want to postpone the edge visit to the right time (i.e. when the
corresponding tail vertex is removed from the waiting list) then I
guess the waiting list itself should also keep track of the edge and/or
the predecessor (vertex). The class PredecessorsList probably does that
job fairly well.

Rephrasing a bit: we are seeking a unified implementation for both
standard graph searches (only concerned with vertices) and more
general graph visits (e.g. the one needed for max flow algorithms). So
yeah, let's use our brains for something cool :)

P.S. I would not remove discoverEdge anyway because, as I said before,
it can help pruning the graph and avoiding to explore dead ends (e.g.
for max flow, there is no point in traversing edges with no residual
flow capacity).

Ciao
Claudio

--
Claudio Squarcella
PhD student at Roma Tre University
http://www.dia.uniroma3.it/~squarcel
http://squarcella.com/

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: svn commit: r1293496 - /commons/proper/commons-parent/trunk/pom.xml

2012-02-27 Thread Gary Gregory

On Mon, Feb 27, 2012 at 11:58 AM, sebb seb...@gmail.com wrote:

 On 27 February 2012 15:49, sebb seb...@gmail.com wrote:
  On 27 February 2012 14:48, Gary Gregory garydgreg...@gmail.com wrote:
  On Sat, Feb 25, 2012 at 8:14 PM, Gary Gregory garydgreg...@gmail.com
 wrote:
 
  On Feb 25, 2012, at 19:18, sebb seb...@gmail.com wrote:
 
   On 25 February 2012 14:46, Gary Gregory garydgreg...@gmail.com
 wrote:
   On Sat, Feb 25, 2012 at 9:23 AM, sebb seb...@gmail.com wrote:
  
   On 25 February 2012 14:11, Gary Gregory garydgreg...@gmail.com
  wrote:
   On Fri, Feb 24, 2012 at 8:23 PM, sebb seb...@gmail.com wrote:
  
   On 25 February 2012 00:47,  ggreg...@apache.org wrote:
   Author: ggregory
   Date: Sat Feb 25 00:47:00 2012
   New Revision: 1293496
  
   URL: http://svn.apache.org/viewvc?rev=1293496view=rev
   Log:
   Update plugins.
  
   Modified:
  commons/proper/commons-parent/trunk/pom.xml
  
   Modified: commons/proper/commons-parent/trunk/pom.xml
   URL:
  
  
 
 http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=1293496r1=1293495r2=1293496view=diff
  
  
  
 
 ==
   --- commons/proper/commons-parent/trunk/pom.xml (original)
   +++ commons/proper/commons-parent/trunk/pom.xml Sat Feb 25
 00:47:00
   2012
   @@ -193,12 +193,12 @@ Version 23:
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-antrun-plugin/artifactId
   -  version1.6/version
   +  version1.7/version
   /plugin
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-assembly-plugin/artifactId
   -  version2.2.1/version
   +  version2.3/version
   /plugin
   plugin
 groupIdorg.apache.maven.plugins/groupId
   @@ -262,7 +262,7 @@ Version 23:
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-release-plugin/artifactId
   -  version2.2.1/version
   +  version2.2.2/version
   /plugin
   plugin
 !-- TODO see above - find better way to add NL
 files to
   jars
   and test jars --
   @@ -318,7 +318,7 @@ Version 23:
 groupIdorg.apache.felix/groupId
 artifactIdmaven-bundle-plugin/artifactId
 !-- N.B. 2.3.5 does not work on Java 5; see profile
   java-1.5-detected for the workround --
   -  version2.3.5/version
   +  version2.3.6/version
  
   Does 2.3.6 work with java 1.5?
  
   If so, maybe the work-round can be commented out or removed?
  
  
   Sure, that makes sense.
  
   Seems to be ok for me when I build [codec] with:
  
   Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
   Maven home: C:\Java\apache-maven-3.0.4\bin\..
   Java version: 1.5.0_22, vendor: Sun Microsystems Inc.
   Java home: C:\Program Files\Java\jdk1.5.0_22\jre
   Default locale: en_US, platform encoding: Cp1252
   OS name: windows 7, version: 6.1, arch: amd64, family:
 windows
  
   I see:
  
   [INFO] --- maven-bundle-plugin:2.3.6:manifest (bundle-manifest) @
   commons-codec ---
  
   No stack traces or errors.
  
   Need to check M2.2.1 as well.
  
  
   Build successful with:
  
   Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
   Java version: 1.5.0_22
   Java home: C:\Program Files\Java\jdk1.5.0_22\jre
   Default locale: en_US, platform encoding: Cp1252
   OS name: windows 7 version: 6.1 arch: amd64 Family: windows
  
   Did you disable the java-1.5-detected profile?
  
   That is automatically enabled when running under Java 1.5, and
 selects
   earlier versions in order to fix this.
 
 
  I deleted the java-1.5-detected profile in the parent POM and installed
 it
  locally (mvn install).
 
  Then I made [codec] use this 24-SNAPSHOT parent POM with M3 and M2 (mvn
  install) and builds were successful and create jars with OSGi-looking
  manifests.
 
  So I suppose this means the java-1.5-detected profile is not needed
 anymore
  but as I am not a Maven expert on this specific issue I'll not delete it
  ATM.
 
  OK, I may have time to try it later this week;
  What I intend to do is:
  - disable the current override for java 1.5
  - check that the bind command fails when building (IIRC, the problem
  was a bind plugin dependency that was built with Java 1.6)
  - update to the latest bind plugin
  - check that the bind command succeeds
 
  If anyone else can try that too, so much the better.

 If I disable the 1.5 workround, for example by using

 mvn bundle:manifest -P-java-1.5-detected

 [i.e. no need to edit the pom to test this]

 then Maven 2.2.1/Java 1.5/ Bundle 2.3.5 fails for me with

 [ERROR] FATAL ERROR
 [INFO]
 
 [INFO] java.lang.String.getBytes(Ljava/nio/charset/Charset;)[B
 [INFO]
 
 [INFO] Trace

Re: [graph] Doubts on DFS algorithm implementation

+1 to Claudio!

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Mon, Feb 27, 2012 at 7:35 PM, Claudio Squarcella
squar...@dia.uniroma3.it wrote:
 Hello,


 the method discoveryEdge currently tells whether or not the algorithm
 should explore a subtree/branch and add related vertices to the stack/queue.
 So I see no conflict in the implementation. Maybe you are saying that the
 edge should be explored *right before* the vertex it leads to -- but why?
 AFAIK a standard graph search is only concerned with *vertices*. In that
 sense finishEdge becomes useless, as the responsibility for returning
 prematurely is entirely covered by finishVertex. Am I raving mad? :-)

 yes you are right, the visit should be only concerned the vertices, but in
 our implementation we added also the discoveryEdge that in a dfs has invoked
 like a BFS. This in my opinion can be frustrating for the user because the
 edge is not visit in depth but in breadth.
 So IMHO we should visit also the edge in depth, (only in a dfs of course)
 or remove the invocation of discover/finish edge that can get confused the
 user.


 if you want to postpone the edge visit to the right time (i.e. when the
 corresponding tail vertex is removed from the waiting list) then I guess
 the waiting list itself should also keep track of the edge and/or the
 predecessor (vertex). The class PredecessorsList probably does that job
 fairly well.

 Rephrasing a bit: we are seeking a unified implementation for both standard
 graph searches (only concerned with vertices) and more general graph
 visits (e.g. the one needed for max flow algorithms). So yeah, let's use
 our brains for something cool :)

 P.S. I would not remove discoverEdge anyway because, as I said before, it
 can help pruning the graph and avoiding to explore dead ends (e.g. for max
 flow, there is no point in traversing edges with no residual flow capacity).

 Ciao
 Claudio


 --
 Claudio Squarcella
 PhD student at Roma Tre University
 http://www.dia.uniroma3.it/~squarcel
 http://squarcella.com/


 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [chain] release roadmap

Hi Elijah,

no needs to learn docbook, the docbook page you see on svn repo is a
donation from an old book. Deployed documentation is generated from
/src/site/xdoc sources, the format is an html-alike [1] markup. Just
run ``mvn site  open target/site/index.html` to see the produced
documentation.
HTH!
-Simo

[1] http://maven.apache.org/doxia/references/xdoc-format.html

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Mon, Feb 27, 2012 at 7:32 PM, Elijah Zupancic eli...@zupancic.name wrote:
 Hi Simo,

 Here is my comment from the ticket: My plan is to take this on. I'm
 just very busy at work right now, so I've been trying to learn docbook
 format on the bus on my way to and from work. If you want to take on
 breaking chain into separate modules, that would be much appreciated.

 -Elijah

 On Mon, Feb 27, 2012 at 8:58 AM, Simone Tripodi
 simonetrip...@apache.org wrote:

 Hi all guys!

 thanks to Elijah Zupancich's contributions, we now have a fresh new
 [chain] on trunk that uses generics. I can have (limited) spare time
 to dedicate to [chain] and I would like to put energies on it in order
 to have it released ASAP.

 This is my roadmap to have [chain] released in a short time:

  * CHAIN-65
  * CHAIN-66
  * CHAIN-55

 since some other issues are really old and never fixed, I'd tend to
 keep them open and move to release 2.1

 groupId:artifactId:version will be updated to
 org.apache.common:commons-chain2:2.0

 Does anyone have objections/suggestions/... ?
 TIA, all the best!
 -Simo

 http://people.apache.org/~simonetripodi/
 http://simonetripodi.livejournal.com/
 http://twitter.com/simonetripodi
 http://www.99soft.org/

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org


 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Math] Toward releasing 3.0 ?

  I couldn't tell you now because installing maven3 implied desinstalling
  maven2.
 
 I've got both installed (Win XP) with no issues; I just change the
 PATH as needed to switch between them.

It's Debian GNU/Linux here.

  [...]

  [INFO] 
  
  [INFO] Building Commons Math 3.0-SNAPSHOT
  [INFO] 
  
  [INFO]
  [INFO] --- maven-gpg-plugin:1.1:sign (default-cli) @ commons-math3 ---
  GPG Passphrase: ***
 
 Good, so it does prompt.
 
  [INFO] 
  
  [INFO] BUILD FAILURE
  [INFO] 
  
  [INFO] Total time: 11.345s
  [INFO] Finished at: Mon Feb 27 13:05:15 CET 2012
  [INFO] Final Memory: 9M/105M
  [INFO] 
  
  [ERROR] Failed to execute goal
  org.apache.maven.plugins:maven-gpg-plugin:1.1:sign (default-cli) on project
  commons-math3: The project artifact has not been assembled yet. Please do
  not invoke this goal before the lifecycle phase package. - [Help 1]
  [ERROR]
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
  switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR]
  [ERROR] For more information about the errors and possible solutions, 
  please read the following articles:
  [ERROR] [Help 1] 
  http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
  ---CUT---
 
  However, when I run
 
   $ mvn clean deploy -Papache-release -Ptest-deploy
 
 Try using
 
 mvn clean package deploy -Prelease -Ptest-deploy
 
 instead.

Same error (bad passphrase).

 [...]
 Some encrypted passphrases can contain invalid characters; check that
 {} only appear at the ends.

There are no { or } inside the encrypted passphrase.

 [Very poor design of the Maven decrypt routine - it should only check
 for {} at the ends of the value and so avoid the hassle of escaping
 chars]
 
  [INFO] 
  
  [INFO] BUILD FAILURE
  [INFO] 
  
  [INFO] Total time: 2:20.088s
  [INFO] Finished at: Mon Feb 27 13:15:10 CET 2012
  [INFO] Final Memory: 36M/370M
  [INFO] 
  
  [ERROR] Failed to execute goal
  org.apache.maven.plugins:maven-gpg-plugin:1.1:sign (default) on project 
  commons-math3: Exit code: 2 - [Help 1]
  ---CUT---
 
 
  Better than plain text, but still not ideal if your host is not
  physically secure.
 
  It would have been good enough if it worked.
  I must be missing some additional configuration...
 
 Does the encryption setup work for logins, e.g. can you deploy snapshots?

When there is no GPG step, it seems to work; here is a listing of the
created files:

$ ls -1 target/deploy/org/apache/commons/commons-math3/3.0-SNAPSHOT/
commons-math3-3.0-20120227.204940-1.jar
commons-math3-3.0-20120227.204940-1.jar.md5
commons-math3-3.0-20120227.204940-1.jar.sha1
commons-math3-3.0-20120227.204940-1.pom
commons-math3-3.0-20120227.204940-1.pom.md5
commons-math3-3.0-20120227.204940-1.pom.sha1
commons-math3-3.0-20120227.204940-1-site.xml
commons-math3-3.0-20120227.204940-1-site.xml.md5
commons-math3-3.0-20120227.204940-1-site.xml.sha1
maven-metadata.xml
maven-metadata.xml.md5
maven-metadata.xml.sha1


I only tried test-deploy; can I just try deploy as is, and see what is
going to happen? I was wary of messing with Nexus until it could at least
work flawlessly with test-deploy...

I think that this, indeed, did not test the use of the encrypted password
for login.

  [...]


Gilles

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE][Lang] Update to Java 6

volunteers maintaining [lang] have to work in the more comfortable
conditions they need - if keeping the Java5 backward compatibility
became more a pain than something to enjoy in their spare time,
there's no reason to continue getting crazy with the risk they lose
the interest - and [lang] won't be released anymore.

so, +1

all the best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Mon, Feb 27, 2012 at 10:16 PM, Gary Gregory ggreg...@apache.org wrote:
 Hello All:

 This VOTE is to update the platform requirement for Commons Lang trunk to
 Java 6 from Java 5.

 The reasons are:

 - Stop wasting time back porting code contributions from Java 6 to Java 5.
 - Stop fixing erroneous commits that happened to use Java 6 methods.
 - Stop using a dead version of Java for current development

 - Use a current version of Java for current development in trunk
 - Attract more developers and interest.

 The current version of Lang is 3.1 and requires Java 5. If more Java 5-only
 patches are needed, they will be performed on a branch.

 This VOTE is open for at least 72 hours (March 1, 2012 at 16:20PM EST)

 Thank you,
 Gary

 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
 Spring Batch in Action: http://bit.ly/bqpbCK
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory http://twitter.com/GaryGregory

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE][Lang] Update to Java 6

2012-02-27 Thread Dave Brosius

 +1  - Original Message -From: quot;Gary Gregoryquot; 
;ggreg...@apache.org;http://twitter.com/GaryGregory

Re: [RESULT] Was: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

On 27 February 2012 17:57, Mladen Turk mt...@apache.org wrote:
On 02/27/2012 06:14 PM, sebb wrote:

Can you also release the jar to Maven please?

Sure, already did steps described at
http://commons.apache.org/releases/release.html

files are already inside
/x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-daemon
and maven-metadata.xml updated.

According to the release.html this should sync to repo1.maven.org
(if the instructions are valid of course)

They are out of date for Nexus-enabled components, which Daemon is.

Not sure how you managed to update the directory; when a component
uses Nexus, manual updates are supposed to be disabled.

I see that the 1.0.9 jar is also present, but has not been propagated
to Maven Central (as we know from the Clirr story).

[Later]

Just realised what the problem is - the files are installed under the
directory which corresponds to the groupId org.apache.commons, but the
pom actually has groupId commons-daemon. This is one of the pitfalls
of the manual deployment method in the (outdated) release docs.

I can probably fix that via Nexus.

Note: we could change the groupId to o.a.c, but that would require a
package name change as well otherwise classpath clashes could occur.

Regards
--
^TM

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Math] Toward releasing 3.0 ?

On 27 February 2012 21:22, Gilles Sadowski gil...@harfang.homelinux.org wrote:
  I couldn't tell you now because installing maven3 implied desinstalling
  maven2.

 I've got both installed (Win XP) with no issues; I just change the
 PATH as needed to switch between them.

 It's Debian GNU/Linux here.

  [...]

  [INFO] 
  
  [INFO] Building Commons Math 3.0-SNAPSHOT
  [INFO] 
  
  [INFO]
  [INFO] --- maven-gpg-plugin:1.1:sign (default-cli) @ commons-math3 ---
  GPG Passphrase: ***

 Good, so it does prompt.

  [INFO] 
  
  [INFO] BUILD FAILURE
  [INFO] 
  
  [INFO] Total time: 11.345s
  [INFO] Finished at: Mon Feb 27 13:05:15 CET 2012
  [INFO] Final Memory: 9M/105M
  [INFO] 
  
  [ERROR] Failed to execute goal
  org.apache.maven.plugins:maven-gpg-plugin:1.1:sign (default-cli) on project
  commons-math3: The project artifact has not been assembled yet. Please do
  not invoke this goal before the lifecycle phase package. - [Help 1]
  [ERROR]
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
  switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR]
  [ERROR] For more information about the errors and possible solutions, 
  please read the following articles:
  [ERROR] [Help 1] 
  http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
  ---CUT---
 
  However, when I run
 
   $ mvn clean deploy -Papache-release -Ptest-deploy

 Try using

 mvn clean package deploy -Prelease -Ptest-deploy

 instead.

 Same error (bad passphrase).

 [...]
 Some encrypted passphrases can contain invalid characters; check that
 {} only appear at the ends.

 There are no { or } inside the encrypted passphrase.

 [Very poor design of the Maven decrypt routine - it should only check
 for {} at the ends of the value and so avoid the hassle of escaping
 chars]

  [INFO] 
  
  [INFO] BUILD FAILURE
  [INFO] 
  
  [INFO] Total time: 2:20.088s
  [INFO] Finished at: Mon Feb 27 13:15:10 CET 2012
  [INFO] Final Memory: 36M/370M
  [INFO] 
  
  [ERROR] Failed to execute goal
  org.apache.maven.plugins:maven-gpg-plugin:1.1:sign (default) on project 
  commons-math3: Exit code: 2 - [Help 1]
  ---CUT---
 
 
  Better than plain text, but still not ideal if your host is not
  physically secure.
 
  It would have been good enough if it worked.
  I must be missing some additional configuration...

 Does the encryption setup work for logins, e.g. can you deploy snapshots?

 When there is no GPG step, it seems to work; here is a listing of the
 created files:

 $ ls -1 target/deploy/org/apache/commons/commons-math3/3.0-SNAPSHOT/
 commons-math3-3.0-20120227.204940-1.jar
 commons-math3-3.0-20120227.204940-1.jar.md5
 commons-math3-3.0-20120227.204940-1.jar.sha1
 commons-math3-3.0-20120227.204940-1.pom
 commons-math3-3.0-20120227.204940-1.pom.md5
 commons-math3-3.0-20120227.204940-1.pom.sha1
 commons-math3-3.0-20120227.204940-1-site.xml
 commons-math3-3.0-20120227.204940-1-site.xml.md5
 commons-math3-3.0-20120227.204940-1-site.xml.sha1
 maven-metadata.xml
 maven-metadata.xml.md5
 maven-metadata.xml.sha1


 I only tried test-deploy; can I just try deploy as is, and see what is
 going to happen?

AFAIK, there is no point - the gpg stage happens before deploy;
changing the deploy target won't change anything to do with gpg.

 I was wary of messing with Nexus until it could at least
 work flawlessly with test-deploy...

Nexus is the safety net; it's not possible to accidentally deploy when
using Nexus, as the release upload has to be closed and then released
before it gets sent further.

 I think that this, indeed, did not test the use of the encrypted password
 for login.

To test the login encryption, I suggest you try deploying a snapshot
release instead (e.g. install from trunk, which should remain a
snapshot).

  [...]


 Gilles

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE][Lang] Update to Java 6

2012-02-27 Thread Christian Grobmeier

On Mon, Feb 27, 2012 at 11:53 PM, sebb seb...@gmail.com wrote:
 On 27 February 2012 21:16, Gary Gregory ggreg...@apache.org wrote:
 Hello All:

 This VOTE is to update the platform requirement for Commons Lang trunk to
 Java 6 from Java 5.

 The reasons are:

 - Stop wasting time back porting code contributions from Java 6 to Java 5.
 - Stop fixing erroneous commits that happened to use Java 6 methods.
 - Stop using a dead version of Java for current development

 Is it dead for Android?

http://developer.android.com/sdk/requirements.html
you need JDK 1.6 to develop android apps (I actually do this)

Btw I expect Dart apps to become the main app language in middle term.
 And hey, lang 3.1 will still be there.

Cheers
Christian


 - Use a current version of Java for current development in trunk
 - Attract more developers and interest.

 The current version of Lang is 3.1 and requires Java 5. If more Java 5-only
 patches are needed, they will be performed on a branch.

 This VOTE is open for at least 72 hours (March 1, 2012 at 16:20PM EST)

 Thank you,
 Gary

 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
 Spring Batch in Action: http://bit.ly/bqpbCK
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory http://twitter.com/GaryGregory

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org




-- 
http://www.grobmeier.de
https://www.timeandbill.de

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [RESULT] Was: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

On 27 February 2012 22:45, sebb seb...@gmail.com wrote:
On 27 February 2012 17:57, Mladen Turk mt...@apache.org wrote:
On 02/27/2012 06:14 PM, sebb wrote:

Can you also release the jar to Maven please?

Sure, already did steps described at
http://commons.apache.org/releases/release.html

files are already inside
/x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-daemon
and maven-metadata.xml updated.

According to the release.html this should sync to repo1.maven.org
(if the instructions are valid of course)

They are out of date for Nexus-enabled components, which Daemon is.

Not sure how you managed to update the directory; when a component
uses Nexus, manual updates are supposed to be disabled.

I see that the 1.0.9 jar is also present, but has not been propagated
to Maven Central (as we know from the Clirr story).

[Later]

I can probably fix that via Nexus.

Done. Should appear in Maven Central in a day or so.

Note: we could change the groupId to o.a.c, but that would require a
package name change as well otherwise classpath clashes could occur.

Regards
--
^TM

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-digester3 (in module apache-commons) failed

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-digester3 has an issue affecting its community integration.
This issue affects 2 projects,
 and has been outstanding for 32 runs.
The current state of this project is 'Failed', with reason 'Missing Build 
Outputs'.
For reference only, the following projects are affected by this:
- commons-digester3 :  XML to Java Object Configuration
- commons-digester3-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [commons-digester3-*[0-9T].jar] identifier set to 
project name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/apache-commons/digester/pom.xml
 -INFO- Failed with reason missing build outputs
 -ERROR- Missing Output: 
/srv/gump/public/workspace/apache-commons/digester/target/commons-digester3-*[0-9T].jar
 -ERROR- See Directory Listing Work for Missing Outputs
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/gump_work/build_apache-commons_commons-digester3.html
Work Name: build_apache-commons_commons-digester3 (Type: Build)
Work ended in a state of : Success
Elapsed: 1 min 38 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml 
package 
[Working Directory: /srv/gump/public/workspace/apache-commons/digester]
M2_HOME: /opt/maven2
-
Downloading: 
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.1/plexus-archiver-1.1.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-repository-builder/1.0-alpha-2/maven-repository-builder-1.0-alpha-2.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.0-alpha-1/maven-common-artifact-filters-1.0-alpha-1.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-shared-components/6/maven-shared-components-6.pom

Downloading: 
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.1/plexus-archiver-1.1.jar
Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar


Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-repository-builder/1.0-alpha-2/maven-repository-builder-1.0-alpha-2.jar

[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor: 
/srv/gump/public/workspace/apache-commons/digester/dist/src/main/assembly/bin.xml
[INFO] Reading assembly descriptor: 
/srv/gump/public/workspace/apache-commons/digester/dist/src/main/assembly/src.xml
[INFO] Building tar : 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-bin.tar.gz
[INFO] Building zip: 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-bin.zip
[INFO] Building tar : 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-src.tar.gz
[INFO] Building zip: 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-src.zip
[INFO] 
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Commons Digester ... SUCCESS [10.219s]
[INFO] Apache Commons Digester :: Core ... SUCCESS [31.791s]
[INFO] Apache Commons Digester :: Annotations Processor .. SUCCESS [2.264s]
[INFO] Commons Digester :: Examples .. SUCCESS [0.492s]
[INFO] Apache Commons Digester :: Examples :: Annotations :: Atom  SUCCESS 
[3.118s]
[INFO] Apache Commons Digester :: Examples :: API :: Address Book  SUCCESS 
[2.229s]
[INFO] Apache Commons Digester :: Examples :: API :: Catalog . SUCCESS [1.957s]
[INFO] Apache Commons Digester :: Examples :: API :: DB Insert  SUCCESS [2.229s]
[INFO] Apache Commons Digester :: Examples :: API :: Document Markup  SUCCESS 
[1.606s]
[INFO] Apache Commons Digester :: Examples :: EDSL :: Atom ... SUCCESS [1.894s]
[INFO] Apache Commons Digester :: Examples :: Plugins :: Pipeline  SUCCESS 
[1.491s]
[INFO] Apache Commons Digester ::

[GUMP@vmgump]: Project commons-exec-test (in module apache-commons) failed

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-exec-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 4 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-exec-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/exec/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/gump_work/build_apache-commons_commons-exec-test.html
Work Name: build_apache-commons_commons-exec-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 24 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/exec]
M2_HOME: /opt/maven2
-
FOO..
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 
(Exit value: 143)
Process completed in 2012 millis; below is its output
Process timed out and was killed.
Executing [sh, -c, src/test/scripts/invoker.sh]
invoker.sh -- going to start daemon process
invoker.sh --  daemon process was started
cd: 21: can't cd to ../../../target
Process completed in 8027 millis; above is its output
0: process has terminated: false
1: process has terminated: false
2: process has terminated: false
3: process has terminated: false
4: process has terminated: false
5: process has terminated: false
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.023 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.027 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.027 ms
Process completed in 2004 millis; below is its output
Process timed out and was killed by watchdog.
gdal_translate
HDF5:/home/kk/grass/data/4404.he5://HDFEOS/GRIDS/OMI_Column_Amount_O3/Data_Fields/ColumnAmountO3/home/kk/4.tif
FOO..
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.856 sec  
FAILURE!

Results :

Failed tests: 
  testExec_60(org.apache.commons.exec.DefaultExecutorTest)

Tests run: 95, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 minute 23 seconds
[INFO] Finished at: Tue Feb 28 02:35:35 UTC 2012
[INFO] Final Memory: 25M/65M
[INFO] 
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/atom.xml

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 1028022012, vmgump.apache.org:vmgump:1028022012
Gump E-mail Identifier (unique within run) #17.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed

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 issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-proxy-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/proxy/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html
Work Name: build_apache-commons_commons-proxy-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 11 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/proxy]
M2_HOME: /opt/maven2
-
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.factory.util.TestMethodSignature
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.apache.commons.proxy.provider.TestConstantProvider
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
Running org.apache.commons.proxy.interceptor.TestInterceptorChain
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.proxy.invoker.TestNullInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec
Running org.apache.commons.proxy.exception.TestDelegateProviderException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.invoker.TestChainInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.188 sec
Running org.apache.commons.proxy.exception.TestProxyFactoryException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.provider.TestBeanProvider
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec

Results :

Tests in error: 
  testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker)

Tests run: 179, Failures: 0, Errors: 1, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 10 seconds
[INFO] Finished at: Tue Feb 28 06:13:05 UTC 2012
[INFO] Final Memory: 24M/58M
[INFO] 
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml
- Atom:

Re: [RESULT] Was: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

2012-02-27 Thread Mladen Turk


On 02/27/2012 11:45 PM, sebb wrote:

On 27 February 2012 17:57, Mladen Turkmt...@apache.org  wrote:


According to the release.html this should sync to repo1.maven.org
(if the instructions are valid of course)


They are out of date for Nexus-enabled components, which Daemon is.

Not sure how you managed to update the directory; when a component
uses Nexus, manual updates are supposed to be disabled.



using unix cp from ssh as explained in the
http://commons.apache.org/releases/release.html




This is one of the pitfalls
of the manual deployment method in the (outdated) release docs.



So you are saying that release.html is incorrect?
If you know how it should be done please update the release.html.


Regards
--
^TM

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-vfs2-test (in module apache-commons) failed