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
Bear in mind however that feedparser is in 'Dormant' (meaning not
being worked on). I doubt it's likely to become active again.
Hen
On Wed, May 11, 2011 at 9:55 AM, sebb wrote:
> On 11 May 2011 17:08, Diego Peroni wrote:
>> Hi,
>>
>> I've fixed a bug in org.apache.commons.feedparser.MetaFeedPar
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
On 11 May 2011 22:14, Simone Tripodi wrote:
> Salut Olivier!!!
> since AST* classes are generated by JavaCC, I suggest you to don't pay
> so much attention on fixing this stuff, sorry for not having warned
> before :(
> Indeed, build process has to be reviewed in a way to include the
> JavaCC plug
Salut Olivier!!!
since AST* classes are generated by JavaCC, I suggest you to don't pay
so much attention on fixing this stuff, sorry for not having warned
before :(
Indeed, build process has to be reviewed in a way to include the
JavaCC plugin and remove generated classes from SCM.
I'll write a mo
Am 11.05.2011 22:26, schrieb sebb:
On 11 May 2011 21:07, Oliver Heger wrote:
Build works fine with Java 1.5 and 1.6 on Windows 7. Artifacts and site look
good.
Minor nit: When I build the site on my local machine I get 64 findbugs
errors. These are not shown on the staged site. According to my
On 11 May 2011 21:07, Oliver Heger wrote:
> Build works fine with Java 1.5 and 1.6 on Windows 7. Artifacts and site look
> good.
>
> Minor nit: When I build the site on my local machine I get 64 findbugs
> errors. These are not shown on the staged site. According to my local
> findbugs report 572
Build works fine with Java 1.5 and 1.6 on Windows 7. Artifacts and site
look good.
Minor nit: When I build the site on my local machine I get 64 findbugs
errors. These are not shown on the staged site. According to my local
findbugs report 572 classes have been checked while the report on the
On 11 May 2011 17:08, Diego Peroni wrote:
> Hi,
>
> I've fixed a bug in org.apache.commons.feedparser.MetaFeedParser.java to
> allow correct date parsing in case of presence of white spaces before or
> after the date string.
Bugs should normally be reported via JIRA issues please.
http://commons
Hi,
I've fixed a bug in org.apache.commons.feedparser.MetaFeedParser.java to
allow correct date parsing in case of presence of white spaces before or
after the date string.
try {
//ok. Support dc:date
//String v = state.current.getChildText( name, ns );
On 11 May 2011 16:15, Gary Gregory wrote:
> +1.
>
> If there is another RC, please add a code coverage report.
>
> Shouldn't code coverage be part of the parent POM?
I suggest you file a JIRA so that does not get forgotten.
> Gary
>
> Looks good on:
>
> Apache Maven 3.0.3 (r1075438; 2011-02-28 1
Merci beaucoup!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, May 11, 2011 at 6:06 PM, Olivier Lamy wrote:
> Docs are here : https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin
>
> 2011/5/11 Simone Tripodi :
>> Salut Olivier,
>> I noticed it while receiving
Torsten,
I have moved my code base from my old version of jci 1.1 to the trunk and
everything looks good. I did have trouble building the trunk, because the fam
module is not included in the module list. I have opened JCI-66 to address
that. I will take a look at 1.0/1.1 compatibility late
Docs are here : https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin
2011/5/11 Simone Tripodi :
> Salut Olivier,
> I noticed it while receiving JIRA notifications, it *rocks* (and
> please teach me how you did it! :D)
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
Salut Olivier,
I noticed it while receiving JIRA notifications, it *rocks* (and
please teach me how you did it! :D)
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, May 11, 2011 at 5:31 PM, Olivier Lamy wrote:
> Yup sorry I have missed some.
> Note I have setup the
Yup sorry I have missed some.
Note I have setup the jenkins build to update jira if you use the
pattern [jiraId]
/Olivier
2011/5/11 Antonio Petrelli :
> All OGNL-ers
> Can you please insert the Jira issue you are working on when you commit?
> This way, Jira links commits to the issues.
>
> Thanks
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8210&projectId=73
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 11 May 2011 15:26:52 +
Finished at: Wed 11 May 2011 15:27:52 +
Total time: 59s
Build Trigger: Schedule
Buil
+1.
If there is another RC, please add a code coverage report.
Shouldn't code coverage be part of the parent POM?
Gary
Looks good on:
Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
Maven home: C:\Java\apache-maven-3.0.3\bin\..
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java
On 5/11/11 8:07 AM, Mark Thomas wrote:
> On 11/05/2011 16:04, Phil Steitz wrote:
>> On 5/11/11 7:59 AM, ma...@apache.org wrote:
>>> Author: markt
>>> Date: Wed May 11 14:59:52 2011
>>> New Revision: 1101912
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1101912&view=rev
>>> Log:
>>> More clean-up
>>
On 11/05/2011 16:04, Phil Steitz wrote:
> On 5/11/11 7:59 AM, ma...@apache.org wrote:
>> Author: markt
>> Date: Wed May 11 14:59:52 2011
>> New Revision: 1101912
>>
>> URL: http://svn.apache.org/viewvc?rev=1101912&view=rev
>> Log:
>> More clean-up
>>
>> Modified:
>>
>> commons/proper/pool/trun
On 5/11/11 7:59 AM, ma...@apache.org wrote:
> Author: markt
> Date: Wed May 11 14:59:52 2011
> New Revision: 1101912
>
> URL: http://svn.apache.org/viewvc?rev=1101912&view=rev
> Log:
> More clean-up
>
> Modified:
>
> commons/proper/pool/trunk/src/java/org/apache/commons/pool2/impl/CursorableLi
2011/5/11 Olivier Lamy
> nope.
> But it's defined in the parent without any version so maven 3 check
> metadata to know the version.
> It's just to prevent non usefull http requests :-) when building.
>
So the question is: why is it present in the parent pom? :-D
Thanks for the clarification
An
On 5/11/11 5:42 AM, Mark Thomas wrote:
> On 11/05/2011 11:31, Mark Thomas wrote:
>> On 11/05/2011 04:34, Phil Steitz wrote:
>>> On 5/10/11 7:26 PM, Phil Steitz wrote:
On 5/10/11 8:48 AM, ma...@apache.org wrote:
> Author: markt
> Date: Tue May 10 15:48:22 2011
> New Revision: 110151
nope.
But it's defined in the parent without any version so maven 3 check
metadata to know the version.
It's just to prevent non usefull http requests :-) when building.
2011/5/11 Antonio Petrelli :
> 2011/5/11
>
>> +
>> +
>> +
>> + org.apache.maven.plugins
>> +
On 5/11/11 3:30 AM, Mark Thomas wrote:
> On 11/05/2011 03:26, Phil Steitz wrote:
>> On 5/10/11 8:48 AM, ma...@apache.org wrote:
>>> Author: markt
>>> Date: Tue May 10 15:48:22 2011
>>> New Revision: 1101516
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1101516&view=rev
>>> Log:
>>> Move to using Li
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8206&projectId=73
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 11 May 2011 14:26:42 +
Finished at: Wed 11 May 2011 14:27:42 +
Total time: 59s
Build Trigger: Schedule
Buil
2011/5/11
> +
> +
> +
> + org.apache.maven.plugins
> + maven-idea-plugin
> + 2.2
> +
> +
> +
>
Why so? Do you really need to link idea plugin to a specific version?
Antonio
On 11 May 2011 14:51, Jochen Wiedmann wrote:
> On Wed, May 11, 2011 at 3:45 PM, sebb wrote:
>
>> However, if a breaking API change is needed, then the package
>> name/Maven ids will *have* to be changed.
>
> That's not different from a new major release in commons. If you
> anticipate the necessi
All OGNL-ers
Can you please insert the Jira issue you are working on when you commit?
This way, Jira links commits to the issues.
Thanks
Antonio
I agree and moreover I hate whenever I try to add a maven dependency
through Intellij Idea and I see 3 different major version, realizing
that the small version is the latter.
On 11 May 2011 15:41, Paul Benedict wrote:
> Would you guys be willing to start at 4.0-SNAPSHOT so there's a direct
> con
Hi Paul!
yes I agree, according to Joerg's suggestion, version should be
4.0-incubating-SNAPSHOT.
@Joerg: absolutely right, thanks for your help!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, May 11, 2011 at 3:41 PM, Paul Benedict wrote:
> Would you guys be w
On Wed, May 11, 2011 at 3:45 PM, sebb wrote:
> However, if a breaking API change is needed, then the package
> name/Maven ids will *have* to be changed.
That's not different from a new major release in commons. If you
anticipate the necessity of binary changes, consider creating a
maintenance br
On 11 May 2011 14:36, Jochen Wiedmann wrote:
> On Wed, May 11, 2011 at 2:28 PM, sebb wrote:
>
>> I'd be inclined to keep the current package name and Maven ids during
>> (most of) incubation.
>
> Disagreed. Changing package names etc. should be the first steps in
> incubation. As should be the pu
Would you guys be willing to start at 4.0-SNAPSHOT so there's a direct
continuation of versioning? Just a novel thought since it might help
others to see it's not a re-invention of OGNL, per se, but the
continuation of it.
On Wed, May 11, 2011 at 8:38 AM, Gary Gregory wrote:
> On May 11, 2011, at
On May 11, 2011, at 9:36, Jochen Wiedmann wrote:
> On Wed, May 11, 2011 at 2:28 PM, sebb wrote:
>
>> I'd be inclined to keep the current package name and Maven ids during
>> (most of) incubation.
>
> Disagreed. Changing package names etc. should be the first steps in
> incubation. As should be t
On Wed, May 11, 2011 at 2:28 PM, sebb wrote:
> I'd be inclined to keep the current package name and Maven ids during
> (most of) incubation.
Disagreed. Changing package names etc. should be the first steps in
incubation. As should be the publication of an early release with the
new package names
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8202&projectId=73
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 11 May 2011 13:26:28 +
Finished at: Wed 11 May 2011 13:27:27 +
Total time: 59s
Build Trigger: Schedule
Buil
that is *great*, congrats!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, May 11, 2011 at 2:50 PM, wrote:
> Author: markt
> Date: Wed May 11 12:50:33 2011
> New Revision: 1101862
>
> URL: http://svn.apache.org/viewvc?rev=1101862&view=rev
> Log:
> Restore Java 1
On 11/05/2011 11:31, Mark Thomas wrote:
> On 11/05/2011 04:34, Phil Steitz wrote:
>> On 5/10/11 7:26 PM, Phil Steitz wrote:
>>> On 5/10/11 8:48 AM, ma...@apache.org wrote:
Author: markt
Date: Tue May 10 15:48:22 2011
New Revision: 1101516
URL: http://svn.apache.org/viewvc?r
On May 11, 2011, at 4:24, Simone Tripodi wrote:
> Salut Olivier! hi all!
> Since the OGNL version we'll release is the ASF one, I wonder if:
>
> - groupId should be org.apache.commons
> - artifactId should be commons-ognl
> - version should be 1.0-incubating-SNAPSHOT
+1
Gary
>
> WDYT?
> Have a
On 11 May 2011 13:00, Jörg Schaible wrote:
> Hi Simone,
>
> Simone Tripodi wrote:
>
>> Hi all guys,
>> as you maybe already noticed, we started working on OGNL codebase, I
>> some question that PMCs/Mentors can help to reply:
>>
>> * is it fine updating groupId to `org.apache.commons` and artifac
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8199&projectId=73
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 11 May 2011 12:22:25 +
Finished at: Wed 11 May 2011 12:22:35 +
Total time: 9s
Build Trigger: Schedule
Build
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8198&projectId=98
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 11 May 2011 12:22:12 +
Finished at: Wed 11 May 2011 12:22:23 +
Total time: 11s
Build Trigger: Schedule
Buil
2011/5/11 Jörg Schaible
> > * version number: there are 2 way of thinking about it. For someone
> > is fine continuing from the old version number, IMHO it should be
> > 0.1-incubating, since in my mind ognl != commons-ognl. Which one
> > sounds better? I tried to see how running projects manage
Hi Simone,
Simone Tripodi wrote:
> Hi all guys,
> as you maybe already noticed, we started working on OGNL codebase, I
> some question that PMCs/Mentors can help to reply:
>
> * is it fine updating groupId to `org.apache.commons` and artifactId
> `commons-ognl` even if under incubation?
+1
>
Hi all guys,
as you maybe already noticed, we started working on OGNL codebase, I
some question that PMCs/Mentors can help to reply:
* is it fine updating groupId to `org.apache.commons` and artifactId
`commons-ognl` even if under incubation?
* version number: there are 2 way of thinking about i
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8196&projectId=73
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 11 May 2011 11:21:38 +
Finished at: Wed 11 May 2011 11:21:53 +
Total time: 15s
Build Trigger: Schedule
Buil
On 11/05/2011 04:34, Phil Steitz wrote:
> On 5/10/11 7:26 PM, Phil Steitz wrote:
>> On 5/10/11 8:48 AM, ma...@apache.org wrote:
>>> Author: markt
>>> Date: Tue May 10 15:48:22 2011
>>> New Revision: 1101516
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1101516&view=rev
>>> Log:
>>> Move to using Li
On 11/05/2011 03:26, Phil Steitz wrote:
> On 5/10/11 8:48 AM, ma...@apache.org wrote:
>> Author: markt
>> Date: Tue May 10 15:48:22 2011
>> New Revision: 1101516
>>
>> URL: http://svn.apache.org/viewvc?rev=1101516&view=rev
>> Log:
>> Move to using LinkedBlockingDeque for the queue of idle objects.
On 11/05/2011 01:59, Phil Steitz wrote:
> On 5/10/11 8:48 AM, ma...@apache.org wrote:
> Could be I am not following the logic here, but seems to me that
> better names below would be startMaintenance / endMaintenance
>
> Phil
>
>> +public synchronized boolean startEvictionTest() {
I did t
On 11/05/2011 01:18, Phil Steitz wrote:
> Please raise issues and/or update changes.xml to keep track of these
> changes.
Will do. My focus so far has been on seeing if it is possible to get
DBCP to a point where it is on a par with jdbc-pool performance-wise. I
purposely skipped a lot of house-ke
On 11 May 2011 10:02, Luc Maisonobe wrote:
> Le 10/05/2011 16:13, sebb a écrit :
>>
>> This is a vote to release Apache Commons NET 3.0 based on RC1.
>>
>> [ ] +1 release it
>
> +1
>
> I just noticed you didn't put yourself in the developers section of the pom
> file. With all the work you have do
On Wed, May 11, 2011 at 07:23:34AM +, Continuum@vmbuild wrote:
> [...]
>
>
> Test Summary:
>
> Tests: 2391
> Failures: 1
> Errors: 0
> Succe
Merci Olivier!
I think they are interchangeable and non respective blocking, thanks
for taking care of it!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, May 11, 2011 at 11:24 AM, Olivier Lamy wrote:
> 2011/5/11 Simone Tripodi :
>> Salut Olivier!
>> yes, the goal
2011/5/11 Simone Tripodi :
> Salut Olivier!
> yes, the goal is promoting OGNL under commons, once incubation is over
> so java package should be org.apache.commons.ognl, feel free to fill
> an issue and work on it if you have spare time!
Issue loaded here https://issues.apache.org/jira/browse/OGNL
Hi Mau,
I understand your POV, but at the same time this is apache
commons-ognl and no more ognl...
Anyway, do we have other cases of projects that joined the incubator
during their life cycle to see how they managed that situation?
I thing Apache OpenNPL is one of this case, let me bug that people
Le 10/05/2011 16:13, sebb a écrit :
This is a vote to release Apache Commons NET 3.0 based on RC1.
[ ] +1 release it
+1
I just noticed you didn't put yourself in the developers section of the
pom file. With all the work you have done, you should get some credit.
Luc
[ ] +0 go ahead I don
+1 for refactoring the package to o.a.c.ognl
I'd like to keep the version history (so I vote in favor of 4.0.0),
sometimes is very difficult to understand that a 2.xx version is older
than a 1.xx version.
On 11 May 2011 10:54, Olivier Lamy wrote:
> +1 (as I have understand the goal is to be unde
Salut Olivier!
yes, the goal is promoting OGNL under commons, once incubation is over
so java package should be org.apache.commons.ognl, feel free to fill
an issue and work on it if you have spare time!
What someone else thinks about it?
Many thanks in advance!!!
Simo
http://people.apache.org/~sim
+1 (as I have understand the goal is to be under the commons umbrella).
What about the java package ? (ognl -> org.apache.commons.ognl ? )
2011/5/11 Simone Tripodi :
> Salut Olivier! hi all!
> Since the OGNL version we'll release is the ASF one, I wonder if:
>
> - groupId should be org.apache.com
Salut Olivier! hi all!
Since the OGNL version we'll release is the ASF one, I wonder if:
- groupId should be org.apache.commons
- artifactId should be commons-ognl
- version should be 1.0-incubating-SNAPSHOT
WDYT?
Have a nice day, all the best!
Simo
http://people.apache.org/~simonetripodi/
http:
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=8190&projectId=97
Build statistics:
State: Failed
Previous State: Ok
Started at: Wed 11 May 2011 07:21:51 +
Finished at: Wed 11 May 2011 07:23:32 +
Total time: 1m 41s
Build Trigger: Schedule
Build
62 matches
Mail list logo
