[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-11-10 Thread commons-jelly-tags-jaxme development
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 [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This

Re: [site] issue-tracking link has gone missing somewhere

2007-11-10 Thread Dennis Lundberg
simon wrote: On Sat, 2007-11-10 at 19:21 +0100, Dennis Lundberg wrote: I had a look at why the Issue tracking report is missing from the menu. It took a while, but I finally found that logging has it's own version of this file in /xdocs/issue-tracking.xml Digester has this file too. Removing

Re: [site] issue-tracking link has gone missing somewhere

2007-11-10 Thread simon
On Sat, 2007-11-10 at 19:21 +0100, Dennis Lundberg wrote: > I had a look at why the Issue tracking report is missing from the menu. > It took a while, but I finally found that logging has it's own version > of this file in /xdocs/issue-tracking.xml Digester has this file too. Removing it does c

Re: [site] issue-tracking link has gone missing somewhere

2007-11-10 Thread Dennis Lundberg
That was me publishing the site earlier today. I had a look at why the Issue tracking report is missing from the menu. It took a while, but I finally found that logging has it's own version of this file in /xdocs/issue-tracking.xml It seems that M2 doesn't work in the same way that M1 does in

[EMAIL PROTECTED]: Project commons-id (in module commons-sandbox) failed

2007-11-10 Thread Adam Jack
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 [EMAIL PROTECTED] Project commons-id has an issue affecting its community integration. This issue affects 1

[site] issue-tracking link has gone missing somewhere

2007-11-10 Thread simon
Hi, I just noticed that in the current logging website (pushed out on 10 nov) there is no link to JIRA in the "project info" section. It is there for the current commons-digester (published 7 september). However if I rebuild the commons-digester site, it is no longer there. I guess this is somet

Re: [VOTE] Release Commons Configuration 1.5 based on RC2

2007-11-10 Thread nicolas de loof
+1 2007/11/10, Oliver Heger <[EMAIL PROTECTED]>: > > After some comments and suggestions for improvements a new release > candidate for the 1.5 release of Commons Configuration has been created. > > The artifacts can be found at > http://people.apache.org/~oheger/commons-configuration-1.5rc2/ > >

website tidying (was: [jira] Resolved: (JEXL-38) Link to JEXL grammar is broken since move to TLP)

2007-11-10 Thread sebb
On 10/11/2007, Rahul Akolkar (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/JEXL-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Rahul Akolkar resolved JEXL-38. > --- > >Resolution: Fixed > > All tha

Re: [VOTE] Release Commons Configuration 1.5 based on RC2

2007-11-10 Thread Rahul Akolkar
+1 Nits: * pom is missing md5 * better-off adding maven.compile.{source,target} to project.properties * we should remove ${pom.artifactId.substring(8)} from all poms -Rahul On 11/10/07, Oliver Heger <[EMAIL PROTECTED]> wrote: > After some comments and suggestions for improvements a new relea

[VOTE] Release Commons Configuration 1.5 based on RC2

2007-11-10 Thread Oliver Heger
After some comments and suggestions for improvements a new release candidate for the 1.5 release of Commons Configuration has been created. The artifacts can be found at http://people.apache.org/~oheger/commons-configuration-1.5rc2/ The site is available under http://people.apache.org/~oheger/com

Re: [JEXL] Any plans for a BSF wrapper?

2007-11-10 Thread Rahul Akolkar
On 11/10/07, sebb <[EMAIL PROTECTED]> wrote: > Or both: > > the classname and extension type(s) should be added to > Languages.properties (*) in BSF, and the implementation included in > the JEXL jar. > > (*) If BSF allows for scanning additional property files, that would > not be essential. > I

Re: [all] Please check your svn client configs

2007-11-10 Thread Rahul Akolkar
On 11/10/07, sebb <[EMAIL PROTECTED]> wrote: > > I got a -1 to adding svn:executable, so I've updated the discussion > page and txt file accordingly. > > Also the discussion page is hopefully now a bit clearer on what config > is needed: > > http://www.apache.org/dev/version-control.html#https-svn

Re: [JEXL] Any plans for a BSF wrapper?

2007-11-10 Thread sebb
Or both: the classname and extension type(s) should be added to Languages.properties (*) in BSF, and the implementation included in the JEXL jar. (*) If BSF allows for scanning additional property files, that would not be essential. S. On 10/11/2007, Dion Gillard <[EMAIL PROTECTED]> wrote: > So

Re: [all] Please check your svn client configs

2007-11-10 Thread sebb
On 10/11/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > On 11/8/07, sebb <[EMAIL PROTECTED]> wrote: > > On 08/11/2007, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > > On 11/8/07, sebb <[EMAIL PROTECTED]> wrote: > > > > > Perhaps the file should be updated to add these? > > > > > > > > The file sh

Re: [VOTE] Release commons-logging 1.1.1

2007-11-10 Thread Dennis Lundberg
sebb wrote: On 08/11/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Agreed. The logging site was deployed as part of the TLP move. Unfortunately the site that got deployed was the one for the not-yet-released 1.1.1 version. Perhaps the previous version needs to be redeployed? Well, if som