blocking Charles L. Fields?

2010-11-05 Thread Mike Müller
Hi

Isn't it possible to block the account of Charles L. Fields in JIRA?
seems to be only a spam account.

best regards
mike


Re: blocking Charles L. Fields?

2010-11-05 Thread Carsten Ziegeler
I already informed infra, they want to see the attachments before doing
something.

Regards
Carsten

Mike Müller  wrote
 Hi
 
 Isn't it possible to block the account of Charles L. Fields in JIRA?
 seems to be only a spam account.
 
 best regards
 mike
 


-- 
Carsten Ziegeler
cziege...@apache.org


Re: blocking Charles L. Fields?

2010-11-05 Thread Felix Meschberger
Hi

I have created an INFRA JIRA with yesterday's SPAM and removed it again.
So we'll see what's coming out of this...

And yes, we could block, but he would just create another account then;
which he seems to already have done once.

Regards
Felix

Am Freitag, den 05.11.2010, 09:53 +0100 schrieb Mike Müller: 
 Hi
 
 Isn't it possible to block the account of Charles L. Fields in JIRA?
 seems to be only a spam account.
 
 best regards
 mike




[jira] Created: (SLING-1863) upgrade GWT to 2.1

2010-11-05 Thread Justin Edelson (JIRA)
upgrade GWT to 2.1
--

 Key: SLING-1863
 URL: https://issues.apache.org/jira/browse/SLING-1863
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Justin Edelson


GWT 2.1 has been released - 
http://googlewebtoolkit.blogspot.com/2010/10/announcing-final-release-of-gwt-21.html

the contrib module should be upgraded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SLING-1862) Add possibility to get position of a job inside a queue

2010-11-05 Thread Carsten Ziegeler (JIRA)

[ 
https://issues.apache.org/jira/browse/SLING-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928769#action_12928769
 ] 

Carsten Ziegeler commented on SLING-1862:
-

I think this is a rather expensive operation - in addition it would block parts 
of the queue processing as the internal structures need to be synced/locked

You can achieve the same, by querying for all jobs with your desired topic, go 
through the collection (Iterator) you get and find the result by yourself. This 
gives you the possibility to query the position for a collection of items in 
one go.

 Add possibility to get position of a job inside a queue
 ---

 Key: SLING-1862
 URL: https://issues.apache.org/jira/browse/SLING-1862
 Project: Sling
  Issue Type: New Feature
  Components: Extensions
Reporter: Tobias Bocanegra

 would be good, if there was a possibility to determine the position of a job 
 within a queue.
 something like: 
 int Queue.getPosition(Event)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered

2010-11-05 Thread Charles L Fields (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Charles L Fields updated SLING-1848:


Attachment: Plugin 3.js

 registration (or unregistration) of a ScriptEngineFactory doesn't cause the 
 ScriptEngineManager service to be re-registered
 ---

 Key: SLING-1848
 URL: https://issues.apache.org/jira/browse/SLING-1848
 Project: Sling
  Issue Type: Bug
  Components: Scripting
Reporter: Justin Edelson
Assignee: Justin Edelson
Priority: Blocker
 Fix For: Scripting Core 2.0.14

 Attachments: Plugin 3.js


 ScriptEngineManagerFactory.refreshScriptEngineManager() handles the 
 registration of an OSGi service of the ScriptEngineManager. This is used, 
 amongst other places, by SlingScriptAdapterFactory.
 However, refreshScriptEngineManager() is *only* called from activate() and 
 getScriptEngineManager() (and in the latter case, only if the 
 scriptEngineManager is null). Although bindScriptEngineManager() (and unbind) 
 null out scriptEngineManager, they do not call refreshScriptEngineManager(). 
 As a result, new ScriptEngineFactory services are not effective with this 
 call sequence:
 1) activate()
 2) bindScriptEngineManager()
 3) try adapting a script to a javax.servlet.Servlet
 This can be worked around (albeit poorly IMHO) by going to the Configuration 
 Status page in the web console because this causes getScriptEngineManager() 
 to be called when scriptEngineManager is null, thus causing 
 refreshScriptEngineManager() to be called.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered

2010-11-05 Thread Felix Meschberger (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger updated SLING-1848:
-

Attachment: (was: Plugin 3.js)

 registration (or unregistration) of a ScriptEngineFactory doesn't cause the 
 ScriptEngineManager service to be re-registered
 ---

 Key: SLING-1848
 URL: https://issues.apache.org/jira/browse/SLING-1848
 Project: Sling
  Issue Type: Bug
  Components: Scripting
Reporter: Justin Edelson
Assignee: Justin Edelson
Priority: Blocker
 Fix For: Scripting Core 2.0.14


 ScriptEngineManagerFactory.refreshScriptEngineManager() handles the 
 registration of an OSGi service of the ScriptEngineManager. This is used, 
 amongst other places, by SlingScriptAdapterFactory.
 However, refreshScriptEngineManager() is *only* called from activate() and 
 getScriptEngineManager() (and in the latter case, only if the 
 scriptEngineManager is null). Although bindScriptEngineManager() (and unbind) 
 null out scriptEngineManager, they do not call refreshScriptEngineManager(). 
 As a result, new ScriptEngineFactory services are not effective with this 
 call sequence:
 1) activate()
 2) bindScriptEngineManager()
 3) try adapting a script to a javax.servlet.Servlet
 This can be worked around (albeit poorly IMHO) by going to the Configuration 
 Status page in the web console because this causes getScriptEngineManager() 
 to be called when scriptEngineManager is null, thus causing 
 refreshScriptEngineManager() to be called.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.