[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2810) Dialog node type: change log message to debug level -- or fix all our bootstrap files !

2010-02-17 Thread JIRA (on behalf of Zdenek Skodik) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zdenek Skodik updated MAGNOLIA-2810:


Fix Version/s: 4.3
   (was: 4.2.x)

> Dialog node type: change log message to debug level -- or fix all our 
> bootstrap files !
> ---
>
> Key: MAGNOLIA-2810
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2810
> Project: Magnolia
>  Issue Type: Improvement
>  Components: admininterface
>Affects Versions: 4.1, 4.0.2
>Reporter: Grégory Joseph
>Assignee: Philipp Bärfuss
> Fix For: 4.3
>
>
> When updating or even installing a clean instance, there are tons of 
> unnecessary log messages such as:
> {noformat}
>  WARN: Dialog definitions should be of type contentNode but 
> [/modules/abc/dialogs/paragraphs/xyz] is of type content.
> {noformat}
> We should either make these debug messages, or fix our own content !
> (and consider writing an update task)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2810) Dialog node type: change log message to debug level -- or fix all our bootstrap files !

2010-02-17 Thread JIRA (on behalf of Zdenek Skodik) 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26586#action_26586
 ] 

Zdenek Skodik commented on MAGNOLIA-2810:
-

There appears the questions related to this topic repeatedly, so I'm going to 
fix it (btw 4.2.x was marked as fix version previously).
I personally prefer to fix our own dialog definitions rather than decrease 
level of log messages or
even rewrite the related piece of code at {{DialogHandlerManager}}.

> Dialog node type: change log message to debug level -- or fix all our 
> bootstrap files !
> ---
>
> Key: MAGNOLIA-2810
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2810
> Project: Magnolia
>  Issue Type: Improvement
>  Components: admininterface
>Affects Versions: 4.1, 4.0.2
>Reporter: Grégory Joseph
>Assignee: Philipp Bärfuss
> Fix For: 4.3
>
>
> When updating or even installing a clean instance, there are tons of 
> unnecessary log messages such as:
> {noformat}
>  WARN: Dialog definitions should be of type contentNode but 
> [/modules/abc/dialogs/paragraphs/xyz] is of type content.
> {noformat}
> We should either make these debug messages, or fix our own content !
> (and consider writing an update task)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Created: (MAGNOLIA-3089) DefaultMessagesImpl.keys() throws NPE

2010-02-17 Thread JIRA (on behalf of Federico Grilli) 

DefaultMessagesImpl.keys() throws NPE
-

 Key: MAGNOLIA-3089
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3089
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3 M1
Reporter: Federico Grilli
Assignee: Federico Grilli
 Fix For: 4.3


Calling the keys(..) method will throw a NPE if the underlying ResourceBundle 
is not found (e.g. it is null). Just check if the bundle is null and, if so, 
handle  it gracefully by returning an empty iterator.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-3089) DefaultMessagesImpl.keys() throws NPE

2010-02-17 Thread JIRA (on behalf of Federico Grilli) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Federico Grilli resolved MAGNOLIA-3089.
---

Resolution: Fixed

> DefaultMessagesImpl.keys() throws NPE
> -
>
> Key: MAGNOLIA-3089
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3089
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3 M1
>Reporter: Federico Grilli
>Assignee: Federico Grilli
> Fix For: 4.3
>
>
> Calling the keys(..) method will throw a NPE if the underlying ResourceBundle 
> is not found (e.g. it is null). Just check if the bundle is null and, if so, 
> handle  it gracefully by returning an empty iterator.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] Hudson build is still unstable: magnolia_main-trunk » magnolia-templating-ui-c omponents #1375

2010-02-17 Thread Hudson CI 

See 





For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] Hudson build is still unstable: magnolia_main-trunk #1375

2010-02-17 Thread Hudson CI 

See 




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3089) DefaultMessagesImpl.keys() throws NPE

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26592#action_26592
 ] 

Hudson CI server commented on MAGNOLIA-3089:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! 
[magnolia_main-trunk 
#1375|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1375/]
 MAGNOLIA-3089: check for null resource bundle


> DefaultMessagesImpl.keys() throws NPE
> -
>
> Key: MAGNOLIA-3089
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3089
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3 M1
>Reporter: Federico Grilli
>Assignee: Federico Grilli
> Fix For: 4.3
>
>
> Calling the keys(..) method will throw a NPE if the underlying ResourceBundle 
> is not found (e.g. it is null). Just check if the bundle is null and, if so, 
> handle  it gracefully by returning an empty iterator.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk » magnolia-templating-ui-c omponents #1376

2010-02-17 Thread Hudson CI 

See 





For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk #1376

2010-02-17 Thread Hudson CI 

See 




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MGNLSTK- 568) Revert MGNLSTK-533 for 1.3 ?

2010-02-17 Thread JIRA (on behalf of Federico Grilli) 


 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Federico Grilli resolved MGNLSTK-568.
-

Resolution: Fixed

> Revert MGNLSTK-533 for 1.3 ?
> 
>
> Key: MGNLSTK-568
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-568
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Reporter: Grégory Joseph
>Assignee: Federico Grilli
> Fix For: 1.3
>
>
> Since MAGNOLIA-3037, the changes for MGNLSTK-533 are not necessary anymore.
> To be discussed/confirmed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3037) Handle UnsupportedOperationException for User implementation within the Freemarker model/wrapper

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26598#action_26598
 ] 

Hudson CI server commented on MAGNOLIA-3037:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[standard-templating-kit 
#2427|http://hudson.magnolia-cms.com/job/standard-templating-kit/2427/]
 MGNLSTK-568: Since MAGNOLIA-3037, these changes are not necessary anymore.


> Handle UnsupportedOperationException for User implementation within the 
> Freemarker model/wrapper
> 
>
> Key: MAGNOLIA-3037
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3037
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.3 M1
>
>
> When Freemarker templates attempt to output properties out of 
> {{info.magnolia.cms.security.User}} instances which throw 
> {{UnsupportedOperationException}}s (typically 
> {{info.magnolia.cms.security.ExternalUser}}), this results in ugly exceptions 
> thrown all over the place. Since templates should anyway be aware of this and 
> provide fallback behaviour, our Freemarker wrapper for User could handle 
> those exceptions, giving templates the chance to handle absent properties. 
> They should be able to do {{user.myProperty!'default value'}}, for example.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2810) Dialog node type: change log message to debug level -- or fix all our bootstrap files !

2010-02-17 Thread JIRA (on behalf of Zdenek Skodik) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zdenek Skodik reassigned MAGNOLIA-2810:
---

Assignee: Zdenek Skodik  (was: Philipp Bärfuss)

> Dialog node type: change log message to debug level -- or fix all our 
> bootstrap files !
> ---
>
> Key: MAGNOLIA-2810
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2810
> Project: Magnolia
>  Issue Type: Improvement
>  Components: admininterface
>Affects Versions: 4.1, 4.0.2
>Reporter: Grégory Joseph
>Assignee: Zdenek Skodik
> Fix For: 4.3
>
>
> When updating or even installing a clean instance, there are tons of 
> unnecessary log messages such as:
> {noformat}
>  WARN: Dialog definitions should be of type contentNode but 
> [/modules/abc/dialogs/paragraphs/xyz] is of type content.
> {noformat}
> We should either make these debug messages, or fix our own content !
> (and consider writing an update task)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Work started: (MAGNOLIA-2810) Dialog node type: change log message to debug level -- or fix all our bootstrap files !

2010-02-17 Thread JIRA (on behalf of Zdenek Skodik) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on MAGNOLIA-2810 started by Zdenek Skodik.

> Dialog node type: change log message to debug level -- or fix all our 
> bootstrap files !
> ---
>
> Key: MAGNOLIA-2810
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2810
> Project: Magnolia
>  Issue Type: Improvement
>  Components: admininterface
>Affects Versions: 4.1, 4.0.2
>Reporter: Grégory Joseph
>Assignee: Zdenek Skodik
> Fix For: 4.3
>
>
> When updating or even installing a clean instance, there are tons of 
> unnecessary log messages such as:
> {noformat}
>  WARN: Dialog definitions should be of type contentNode but 
> [/modules/abc/dialogs/paragraphs/xyz] is of type content.
> {noformat}
> We should either make these debug messages, or fix our own content !
> (and consider writing an update task)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MGNLSTK -568) Revert MGNLSTK-533 for 1.3 ?

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26597#action_26597
 ] 

Hudson CI server commented on MGNLSTK-568:
--

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[standard-templating-kit 
#2427|http://hudson.magnolia-cms.com/job/standard-templating-kit/2427/]
 MGNLSTK-568: Since MAGNOLIA-3037, these changes are not necessary anymore.


> Revert MGNLSTK-533 for 1.3 ?
> 
>
> Key: MGNLSTK-568
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-568
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Reporter: Grégory Joseph
>Assignee: Federico Grilli
> Fix For: 1.3
>
>
> Since MAGNOLIA-3037, the changes for MGNLSTK-533 are not necessary anymore.
> To be discussed/confirmed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MGNLSTK -568) Revert MGNLSTK-533 for 1.3 ?

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26599#action_26599
 ] 

Hudson CI server commented on MGNLSTK-568:
--

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[standard-templating-kit 
#2428|http://hudson.magnolia-cms.com/job/standard-templating-kit/2428/]
 MGNLSTK-568: restored last update task


> Revert MGNLSTK-533 for 1.3 ?
> 
>
> Key: MGNLSTK-568
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-568
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Reporter: Grégory Joseph
>Assignee: Federico Grilli
> Fix For: 1.3
>
>
> Since MAGNOLIA-3037, the changes for MGNLSTK-533 are not necessary anymore.
> To be discussed/confirmed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2810) Dialog node type: change log message to debug level -- or fix all our bootstrap files !

2010-02-17 Thread JIRA (on behalf of Zdenek Skodik) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zdenek Skodik updated MAGNOLIA-2810:


Attachment: list of affected dialog definitions

list is attached ~ 42 items/14 modules

> Dialog node type: change log message to debug level -- or fix all our 
> bootstrap files !
> ---
>
> Key: MAGNOLIA-2810
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2810
> Project: Magnolia
>  Issue Type: Improvement
>  Components: admininterface
>Affects Versions: 4.1, 4.0.2
>Reporter: Grégory Joseph
>Assignee: Zdenek Skodik
> Fix For: 4.3
>
> Attachments: list of affected dialog definitions
>
>
> When updating or even installing a clean instance, there are tons of 
> unnecessary log messages such as:
> {noformat}
>  WARN: Dialog definitions should be of type contentNode but 
> [/modules/abc/dialogs/paragraphs/xyz] is of type content.
> {noformat}
> We should either make these debug messages, or fix our own content !
> (and consider writing an update task)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Reopened: (MGNLSTK- 568) Revert MGNLSTK-533 for 1.3 ?

2010-02-17 Thread on behalf of Grégory Joseph 


 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph reopened MGNLSTK-568:



What happens for users having upgrade to 1.2.2 then to 1.3 ?

> Revert MGNLSTK-533 for 1.3 ?
> 
>
> Key: MGNLSTK-568
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-568
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Reporter: Grégory Joseph
>Assignee: Federico Grilli
> Fix For: 1.3
>
>
> Since MAGNOLIA-3037, the changes for MGNLSTK-533 are not necessary anymore.
> To be discussed/confirmed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MGNLGA-2) Testing: Link tracking doesn't work as expected

2010-02-17 Thread JIRA (on behalf of Christian Ringele) 


 [ 
http://jira.magnolia-cms.com/browse/MGNLGA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MGNLGA-2.


Fix Version/s: RC-6
   Resolution: Fixed

Is resolved by:

jQuery.noConflict();
(function($){
$(document).ready(function(){
...
}

> Testing: Link tracking doesn't work as expected
> ---
>
> Key: MGNLGA-2
> URL: http://jira.magnolia-cms.com/browse/MGNLGA-2
> Project: Magnolia Google Analytics
>  Issue Type: Bug
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>Priority: Blocker
> Fix For: RC-6
>
> Attachments: Picture 2.png
>
>
> I am testing the GA module on the demo http://demo.magnolia-cms.com/demo 
> instance.
> Generally the tracking of the pages themselves work as expected. All the 
> pages and page hits are tracked and show up in the GA.
> The JS tracking script the module is using is a JQuery plugin (in module JS 
> 'jquery.gatracker.js'). It is supposed to track all links too: external 
> links, download links and mailto links.
> It adds if found, a prefix to the link URL: 'external' or 'downloads' or 
> 'mailtos'.
> Setup:
> - First I tried a advanced tracker function call with more defined file 
> extensions (in module init.gatracker.js').
> - Then I tried the original function call. So its the unchanged JS running as 
> provided by JQuery:
> (function($){
>   $.gaTracker('${trackerID}');
> })(jQuery);
> This call activates the link tracking with the original options defined in 
> the original JS script 'jquery.gatracker.js'.
> Results:
> - External links are never tracked
> - mailto links are never tracked
> - download links are only very seldom tracked:
> Only download links which point to a .jpg provided by the image 
> module/image-zoom generator. See attached file. 
> I think the problem is located within the js function 'function 
> decorateLink(u){'.
> The regex expression within this function does not apply to the links 
> analyzed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MGNLGA-4) Remove redundant basic install tasks from extra install tasks in version handler

2010-02-17 Thread JIRA (on behalf of Christian Ringele) 


 [ 
http://jira.magnolia-cms.com/browse/MGNLGA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MGNLGA-4.


Fix Version/s: RC-6
   Resolution: Fixed

Done

> Remove redundant basic install tasks from extra install tasks in version 
> handler
> 
>
> Key: MGNLGA-4
> URL: http://jira.magnolia-cms.com/browse/MGNLGA-4
> Project: Magnolia Google Analytics
>  Issue Type: Bug
>Reporter: Nils Breunese
>Assignee: Christian Ringele
>Priority: Minor
> Fix For: RC-6
>
>
> The getExtraInstallTasks() method has the following call:
> installTasks.addAll(super.getBasicInstallTasks(ctx));
> This is redundant and should be removed. Please see the thread at 
> http://www.nabble.com/Version-handler-install-tasks-td26011961.html for Jan 
> Haderka's comment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MGNLGA-3) Rename GoggleAnalyticsJSResourceModel.java to GoogleAnalyticsJSResourceModel.java

2010-02-17 Thread JIRA (on behalf of Christian Ringele) 


 [ 
http://jira.magnolia-cms.com/browse/MGNLGA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MGNLGA-3.


Fix Version/s: RC-6
   Resolution: Fixed

Done

> Rename GoggleAnalyticsJSResourceModel.java to 
> GoogleAnalyticsJSResourceModel.java
> -
>
> Key: MGNLGA-3
> URL: http://jira.magnolia-cms.com/browse/MGNLGA-3
> Project: Magnolia Google Analytics
>  Issue Type: Bug
>Reporter: Nils Breunese
>Assignee: Christian Ringele
>Priority: Trivial
> Fix For: RC-6
>
>   Original Estimate: 0.01d
>  Remaining Estimate: 0.01d
>
> Please refactor 
> src/main/java/info/magnolia/module/googleanalytics/model/GoggleAnalyticsJSResourceModel.java
>  to 
> src/main/java/info/magnolia/module/googleanalytics/model/GoogleAnalyticsJSResourceModel.java.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3000) Update copyright headers : 2010 !

2010-02-17 Thread on behalf of Grégory Joseph 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph updated MAGNOLIA-3000:
-

Priority: Blocker  (was: Major)

> Update copyright headers : 2010 !
> -
>
> Key: MAGNOLIA-3000
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3000
> Project: Magnolia
>  Issue Type: Task
>  Components: build
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
>Priority: Blocker
> Fix For: 4.0.4, 4.2.x, 4.3
>
>
> todo on branches, all modules (ce, ee, ...)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-3087) Allow configurable of shared variables for FreeMarker

2010-02-17 Thread on behalf of Grégory Joseph 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph resolved MAGNOLIA-3087.
--

Fix Version/s: 4.3 M2
   (was: 4.3)
   Resolution: Fixed

> Allow configurable of shared variables for FreeMarker
> -
>
> Key: MAGNOLIA-3087
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3087
> Project: Magnolia
>  Issue Type: Sub-task
>  Components: freemarker
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.3 M2
>
>
> Shared variables in Freemarker are a recommended way to have objects 
> available to templates which do not change over the life time of the 
> Freemarker configuration object. In the case of Magnolia, the configuration 
> object is bound to Freemarker - which currently is a "permanent" singleton; 
> it could eventually become an observed one. In any case, adding shared 
> variables is possible.
> The advantage of shared variables vs "regular" variables added to the context 
> for each render are:
> * these variables are wrapped once and only once over the lifetime of the 
> application
> * they are also (obviously) added to a map only once, thus slightly reducing 
> the complexity/time needed to build the context before rendering.
> There are probably a few context variable which we could also move to shared 
> variables.
> ref: http://freemarker.org/docs/pgui_config_sharedvariables.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3087) Allow configuration of shared variables for FreeMarker

2010-02-17 Thread on behalf of Grégory Joseph 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph updated MAGNOLIA-3087:
-

Summary: Allow configuration of shared variables for FreeMarker  (was: 
Allow configurable of shared variables for FreeMarker)

> Allow configuration of shared variables for FreeMarker
> --
>
> Key: MAGNOLIA-3087
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3087
> Project: Magnolia
>  Issue Type: Sub-task
>  Components: freemarker
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.3 M2
>
>
> Shared variables in Freemarker are a recommended way to have objects 
> available to templates which do not change over the life time of the 
> Freemarker configuration object. In the case of Magnolia, the configuration 
> object is bound to Freemarker - which currently is a "permanent" singleton; 
> it could eventually become an observed one. In any case, adding shared 
> variables is possible.
> The advantage of shared variables vs "regular" variables added to the context 
> for each render are:
> * these variables are wrapped once and only once over the lifetime of the 
> application
> * they are also (obviously) added to a map only once, thus slightly reducing 
> the complexity/time needed to build the context before rendering.
> There are probably a few context variable which we could also move to shared 
> variables.
> ref: http://freemarker.org/docs/pgui_config_sharedvariables.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Created: (MGNLSTK-586) When using AutogeneratedParagraph main are is not optional but extras area is.

2010-02-17 Thread JIRA (on behalf of Teresa Miyar) 

When using AutogeneratedParagraph main are is not optional but extras area is.
--

 Key: MGNLSTK-586
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-586
 Project: Magnolia Standard Templating Kit
  Issue Type: Improvement
Affects Versions: 1.3 M1
Reporter: Teresa Miyar
Assignee: Philipp Bärfuss
Priority: Minor
 Fix For: 1.3


Patch

{code}
Index: 
magnolia-module-standard-templating-kit/src/main/java/info/magnolia/module/templatingkit/templates/SingletonParagraphTemplateModel.java
===
--- 
magnolia-module-standard-templating-kit/src/main/java/info/magnolia/module/templatingkit/templates/SingletonParagraphTemplateModel.java
 (revision 31608)
+++ 
magnolia-module-standard-templating-kit/src/main/java/info/magnolia/module/templatingkit/templates/SingletonParagraphTemplateModel.java
 (working copy)
@@ -118,20 +118,22 @@
 }
 
 private void createMainArea(STKTemplate templateDef) {
-SingletonParagraphMainArea singletonDef = 
(SingletonParagraphMainArea)templateDef.getMainArea();
-try {
-Content mainCollection = ContentUtil.getOrCreateContent(content, 
"main", ItemType.CONTENTNODE, true);
-if (!mainCollection.hasContent(SINGLETON_NODE_NAME)) {
-Content singletonNode = 
mainCollection.createContent(SINGLETON_NODE_NAME, ItemType.CONTENTNODE);
-
singletonNode.getMetaData().setTemplate(singletonDef.getAutoGeneratedParagraph().getName());
+if( templateDef.getMainArea() != null && templateDef.getMainArea() 
instanceof SingletonParagraphMainArea) {
+  SingletonParagraphMainArea singletonDef = 
(SingletonParagraphMainArea)templateDef.getMainArea();
+  try {
+  Content mainCollection = ContentUtil.getOrCreateContent(content, 
"main", ItemType.CONTENTNODE, true);
+  if (!mainCollection.hasContent(SINGLETON_NODE_NAME)) {
+  Content singletonNode = 
mainCollection.createContent(SINGLETON_NODE_NAME, ItemType.CONTENTNODE);
+  
singletonNode.getMetaData().setTemplate(singletonDef.getAutoGeneratedParagraph().getName());
 
-setDefaultValues(singletonNode, 
singletonDef.getAutoGeneratedParagraph().getDefaultValues());
+  setDefaultValues(singletonNode, 
singletonDef.getAutoGeneratedParagraph().getDefaultValues());
 
-mainCollection.save();
-}
-} catch (Exception e) {
-throw new IllegalStateException("Can't create singleton 
paragraph", e);
-}
+  mainCollection.save();
+  }
+  } catch (Exception e) {
+  throw new IllegalStateException("Can't create singleton 
paragraph", e);
+  }
+}//end if generate main area
 }
 
 protected void setDefaultValues(Content singletonNode, Map defaultValues)

{code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLI A-3082) DefaultClassFactory.newInstance(Class< T>, Class[], Object...) sho uld not use invokeExactConstructor but invokeConstruct or

2010-02-17 Thread on behalf of Grégory Joseph 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26608#action_26608
 ] 

Grégory Joseph commented on MAGNOLIA-3082:
--

Now that I read the tests again, I'm not sure about this anymore. I see why we 
need it - but it's the second part of 
{{testCanInstantiateWithBestMatchingConstructorWhenTheSignatureIsMorePrecise()}}
 I don't feel comfortable with. IMO, we should be able to do
{code}
classFactory.newInstance(FooBar.class, arr(Baz.class), 
someInstanceOfABazSubclass)
{code} - ie we know the constructor takes exactly 1 Baz instance, and we pass 
it whatever we have. If you can't do that, you either
* create an array with the types *of your arguments* with defaults to handle 
nulls
* use the newInstance(class, args) variation of the method, and can't have null 
parameters. 

In any case, we should also have a couple of tests using generics to validate 
the cases in question.

> DefaultClassFactory.newInstance(Class, Class[], Object...) should not 
> use invokeExactConstructor but invokeConstructor
> 
>
> Key: MAGNOLIA-3082
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3082
> Project: Magnolia
>  Issue Type: Improvement
>Affects Versions: 4.3 M1
>Reporter: Philipp Bärfuss
>Assignee: Philipp Bärfuss
> Fix For: 4.3
>
>
> The method DefaultClassFactory.newInstance(Class, Object...) calls 
> ConstructorUtils.invokeConstructor(Class, Object[]) while this is not the 
> case for DefaultClassFactory.newInstance(Class, Class[], Object...).
> This is especially a problem if you have more precise constructors in 
> subclasses (especially if you use generics).
> Example: after introducing generics for models (MAGNOLIA-3081) the method 
> AbstractRenderable.newModel(...) fails to find the correct constructor. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2927) Introduce generics in various classes

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26609#action_26609
 ] 

Hudson CI server commented on MAGNOLIA-2927:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#1377|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1377/]
 MAGNOLIA-2927 some more generics in MultipartForm


> Introduce generics in various classes
> -
>
> Key: MAGNOLIA-2927
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2927
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 4.1.1
>Reporter: Jan Haderka
>Assignee: Jan Haderka
> Fix For: 4.3
>
> Attachments: core-generics.patch
>
>
> such as for example
> * {{QueryUtil}} or
> * {{FactoryUtil}}
> See comments for change log / status !

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Created: (MAGNOLIA-3090) SSL and TLS can only be configured in mail smtp config, for consistency with all other parameters should be configurable at template level as well

2010-02-17 Thread JIRA (on behalf of Teresa Miyar) 

SSL and TLS can only be configured in mail smtp config, for consistency with 
all other parameters should be configurable at template level as well 
---

 Key: MAGNOLIA-3090
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3090
 Project: Magnolia
  Issue Type: Bug
  Components: mail
Reporter: Teresa Miyar
Assignee: Boris Kraft




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Work started: (MAGNOLIA-3090) SSL and TLS can only be configured in mail smtp config, for consistency with all other parameters should be configurable at template level as well

2010-02-17 Thread JIRA (on behalf of Teresa Miyar) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on MAGNOLIA-3090 started by Teresa Miyar.

> SSL and TLS can only be configured in mail smtp config, for consistency with 
> all other parameters should be configurable at template level as well 
> ---
>
> Key: MAGNOLIA-3090
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3090
> Project: Magnolia
>  Issue Type: Bug
>  Components: mail
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-3090) SSL and TLS can only be configured in mail smtp config, for consistency with all other parameters should be configurable at template level as well

2010-02-17 Thread JIRA (on behalf of Teresa Miyar) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Teresa Miyar reassigned MAGNOLIA-3090:
--

Assignee: Teresa Miyar  (was: Boris Kraft)

> SSL and TLS can only be configured in mail smtp config, for consistency with 
> all other parameters should be configurable at template level as well 
> ---
>
> Key: MAGNOLIA-3090
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3090
> Project: Magnolia
>  Issue Type: Bug
>  Components: mail
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-3090) SSL and TLS can only be configured in mail smtp config, for consistency with all other parameters should be configurable at template level as well

2010-02-17 Thread JIRA (on behalf of Teresa Miyar) 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Teresa Miyar resolved MAGNOLIA-3090.


Fix Version/s: 4.3 M2
   Resolution: Fixed

> SSL and TLS can only be configured in mail smtp config, for consistency with 
> all other parameters should be configurable at template level as well 
> ---
>
> Key: MAGNOLIA-3090
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3090
> Project: Magnolia
>  Issue Type: Bug
>  Components: mail
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.3 M2
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3090) SSL and TLS can only be configured in mail smtp config, for consistency with all other parameters should be configurable at template level as well

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26610#action_26610
 ] 

Hudson CI server commented on MAGNOLIA-3090:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#1378|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1378/]
 MAGNOLIA-3090 make ssl and tsl configurable also at template level, before 
was looking for a value in mail confi and is not found set same value


> SSL and TLS can only be configured in mail smtp config, for consistency with 
> all other parameters should be configurable at template level as well 
> ---
>
> Key: MAGNOLIA-3090
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3090
> Project: Magnolia
>  Issue Type: Bug
>  Components: mail
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.3 M2
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3028) Introduce generics in mail module

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26611#action_26611
 ] 

Hudson CI server commented on MAGNOLIA-3028:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#1379|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1379/]
 MAGNOLIA-3028 more usages of generics (and foreach) in mail module


> Introduce generics in mail module
> -
>
> Key: MAGNOLIA-3028
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3028
> Project: Magnolia
>  Issue Type: Sub-task
>  Components: mail
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.3 M2
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-3028) Introduce generics in mail module

2010-02-17 Thread on behalf of Grégory Joseph 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph resolved MAGNOLIA-3028.
--

Fix Version/s: 4.3 M2
   (was: 4.3)
   Resolution: Fixed

> Introduce generics in mail module
> -
>
> Key: MAGNOLIA-3028
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3028
> Project: Magnolia
>  Issue Type: Sub-task
>  Components: mail
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.3 M2
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2553) FactoryUtil: should return a proxy object for observed objects

2010-02-17 Thread on behalf of Grégory Joseph 


 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph resolved MAGNOLIA-2553.
--

Fix Version/s: 4.3 M2
   (was: 4.3)
   Resolution: Fixed

> FactoryUtil: should return a proxy object for observed objects
> --
>
> Key: MAGNOLIA-2553
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2553
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Philipp Bärfuss
>Assignee: Grégory Joseph
> Fix For: 4.3 M2
>
> Attachments: proxy.patch
>
>
> The problematic point is that code which keeps a reference to an object will 
> never see an reloaded changes. It would be more convenient and saver if the 
> factory would return and cache a proxy instead.
> Before this, code using such objects always had to get a fresh instance 
> through the factory; once this is implemented, they can keep a reference (i.e 
> get it in their constructor - potentially injected)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2927) Introduce generics in various classes

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26612#action_26612
 ] 

Hudson CI server commented on MAGNOLIA-2927:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#1380|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1380/]
 MAGNOLIA-2927


> Introduce generics in various classes
> -
>
> Key: MAGNOLIA-2927
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2927
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 4.1.1
>Reporter: Jan Haderka
>Assignee: Jan Haderka
> Fix For: 4.3
>
> Attachments: core-generics.patch
>
>
> such as for example
> * {{QueryUtil}} or
> * {{FactoryUtil}}
> See comments for change log / status !

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2553) FactoryUtil: should return a proxy object for observed objects

2010-02-17 Thread on behalf of Grégory Joseph 


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26613#action_26613
 ] 

Grégory Joseph commented on MAGNOLIA-2553:
--

See linked issues for further improvements

> FactoryUtil: should return a proxy object for observed objects
> --
>
> Key: MAGNOLIA-2553
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2553
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Philipp Bärfuss
>Assignee: Grégory Joseph
> Fix For: 4.3 M2
>
> Attachments: proxy.patch
>
>
> The problematic point is that code which keeps a reference to an object will 
> never see an reloaded changes. It would be more convenient and saver if the 
> factory would return and cache a proxy instead.
> Before this, code using such objects always had to get a fresh instance 
> through the factory; once this is implemented, they can keep a reference (i.e 
> get it in their constructor - potentially injected)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] Build failed in Hudson: magnolia-module-groovy #210

2010-02-17 Thread Hudson CI 

See 

Changes:

[fgrilli] MGNLGROOVY-16: moved setting of MgnlGroovyContext in evaluate method 
so that also scripts run from the console can take advantage of it.

--
A SCM change trigger started this job
Updating 
http://svn.magnolia-cms.com/svn/community/modules/magnolia-module-groovy/trunk
U 
src/main/java/info/magnolia/module/groovy/console/MgnlGroovyInteractiveConsole.java
At revision 32004
Parsing POMs
[trunk] $ 
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home//bin/java -cp 
/usr/local/hudson/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.324.jar:/usr/local/hudson/maven/apache-maven-2.0.10/boot/classworlds-1.1.jar
 hudson.maven.agent.Main /usr/local/hudson/maven/apache-maven-2.0.10 
/Library/Tomcat/work/Catalina/hudson.magnolia-cms.com/_/WEB-INF/lib/remoting-1.324.jar
 
/usr/local/hudson/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.324.jar
 55343
<===[HUDSON REMOTING CAPACITY]===>   channel started
Executing Maven:  -B -f 
 
clean install
[INFO] Scanning for projects...
[INFO] 
[INFO] Building magnolia-module-groovy
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory 

[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 17. February 2010 (scope: 
project)
[INFO] Property magnoliaReleaseDate set to value 17. February 2010 (scope: 
project)
[INFO] Property magnoliaNiceVersion set to value 1.0 (Snapshot: 17.02.2010 
17:57:03) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Groovy Module (scope: 
project)
[INFO] Setting property: classpath.resource.loader.class => 
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] inceptionYear not specified, defaulting to 2010
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 14 resources
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 13 source files to 

[INFO] [compiler:testCompile {execution: compile-tests}]
[INFO] Compiling 4 source files to 

[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory: 


---
 T E S T S
---
Running info.magnolia.module.groovy.support.classes.GroovyClassFactoryTest
2010-02-17 17:57:11,422 ERROR 
a.module.groovy.support.classes.GroovyClassFactory: Could not compile 
info.magnolia.module.groovy.test.Buggy with Groovy:
startup failed:
info.magnolia.module.groovy.test.Buggy: 2: unable to resolve class 
info.magnolia.non.existent.Foo
 @ line 2, column 1.
   import info.magnolia.non.existent.Foo
   ^

1 error

2010-02-17 17:57:12,201 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,223 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: 
info.magnolia.module.groovy.test.Duplicate source has not changed
2010-02-17 17:57:12,311 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,317 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has 
changed
2010-02-17 17:57:12,333 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has 
changed
2010-02-17 17:57:12,373 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,379 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,379 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has 
changed
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.591 sec
Running info.magnolia.module.gr

[magnolia-dev] Build failed in Hudson: magnolia -module-groovy » magnolia-module-groovy #210

2010-02-17 Thread Hudson CI 

See 


Changes:

[fgrilli] MGNLGROOVY-16: moved setting of MgnlGroovyContext in evaluate method 
so that also scripts run from the console can take advantage of it.

--
<===[HUDSON REMOTING CAPACITY]===>   channel started
Executing Maven:  -B -f 

 clean install
[INFO] Scanning for projects...
[INFO] 
[INFO] Building magnolia-module-groovy
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory 

[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 17. February 2010 (scope: 
project)
[INFO] Property magnoliaReleaseDate set to value 17. February 2010 (scope: 
project)
[INFO] Property magnoliaNiceVersion set to value 1.0 (Snapshot: 17.02.2010 
17:57:03) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Groovy Module (scope: 
project)
[INFO] Setting property: classpath.resource.loader.class => 
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] inceptionYear not specified, defaulting to 2010
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 14 resources
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 13 source files to 

[INFO] [compiler:testCompile {execution: compile-tests}]
[INFO] Compiling 4 source files to 

[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory: 


---
 T E S T S
---
Running info.magnolia.module.groovy.support.classes.GroovyClassFactoryTest
2010-02-17 17:57:11,422 ERROR 
a.module.groovy.support.classes.GroovyClassFactory: Could not compile 
info.magnolia.module.groovy.test.Buggy with Groovy:
startup failed:
info.magnolia.module.groovy.test.Buggy: 2: unable to resolve class 
info.magnolia.non.existent.Foo
 @ line 2, column 1.
   import info.magnolia.non.existent.Foo
   ^

1 error

2010-02-17 17:57:12,201 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,223 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: 
info.magnolia.module.groovy.test.Duplicate source has not changed
2010-02-17 17:57:12,311 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,317 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has 
changed
2010-02-17 17:57:12,333 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has 
changed
2010-02-17 17:57:12,373 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,379 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has not 
changed
2010-02-17 17:57:12,379 INFO  
odule.groovy.support.classes.MgnlGroovyClassLoader: foo.bar.Baz source has 
changed
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.591 sec
Running info.magnolia.module.groovy.support.classes.MgnlGroovyClassLoaderTest
2010-02-17 17:57:12,419 WARN  
odule.groovy.support.classes.MgnlGroovyClassLoader: compilation failed: you 
must specify a package for your class.
2010-02-17 17:57:12,422 WARN  
odule.groovy.support.classes.MgnlGroovyClassLoader: compilation failed: class 
package 'non.existent.' does not match an existing '/non/existent/' path in the 
scripts repository
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec
Running info.magnolia.module.groovy.support.classes.GroovyModuleTest

[magnolia-dev] Hudson build is back to normal: magnolia-module-groovy » magnolia-module-groovy #211

2010-02-17 Thread Hudson CI 

See 





For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] [JIRA] Commented: (MGNLGROOVY-16) Content retrieved via the console should always be wrapped

2010-02-17 Thread JIRA (on behalf of Hudson CI server) 


[ 
http://jira.magnolia-cms.com/browse/MGNLGROOVY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26614#action_26614
 ] 

Hudson CI server commented on MGNLGROOVY-16:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia-module-groovy 
#211|http://hudson.magnolia-cms.com/job/magnolia-module-groovy/211/]
 

> Content retrieved via the console should always be wrapped
> --
>
> Key: MGNLGROOVY-16
> URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-16
> Project: Magnolia Groovy Module
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 1.0 M1
>Reporter: Grégory Joseph
>Assignee: Federico Grilli
> Fix For: 1.0 M2
>
>
> I'd expect the following to work {code}
> site = hm.getContent('/demo-project')
> DumperUtil.dump(site)
> {code}
> But it doesn't, because the content retrieved in the first line is attached 
> to a session that expires when the 2nd line is executed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] Hudson build is back to normal: magnolia-module-groovy #211

2010-02-17 Thread Hudson CI 

See 




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:

[magnolia-dev] Build failed in Hudson: magnolia_main-trunk #1381

2010-02-17 Thread Hudson CI 

See 

Changes:

[gjoseph] [maven-release-plugin] prepare for next development iteration

[gjoseph] [maven-release-plugin] prepare release magnolia-4.3-m2

--
[...truncated 1355 lines...]
[INFO] Building tar : 

[INFO] Preparing checkstyle:check
[HUDSON] Archiving 

 to 
/usr/local/hudson/data/jobs/magnolia_main-trunk/modules/info.magnolia$magnolia-module-workflow/builds/2010-02-17_18-16-54/archive/info.magnolia/magnolia-module-workflow/4.3-SNAPSHOT/pom.xml
[HUDSON] Archiving 

 to 
/usr/local/hudson/data/jobs/magnolia_main-trunk/modules/info.magnolia$magnolia-module-workflow/builds/2010-02-17_18-16-54/archive/info.magnolia/magnolia-module-workflow/4.3-SNAPSHOT/magnolia-module-workflow-4.3-SNAPSHOT.jar
[HUDSON] Archiving 

 to 
/usr/local/hudson/data/jobs/magnolia_main-trunk/modules/info.magnolia$magnolia-module-workflow/builds/2010-02-17_18-16-54/archive/info.magnolia/magnolia-module-workflow/4.3-SNAPSHOT/magnolia-module-workflow-4.3-SNAPSHOT-bundle.zip
[HUDSON] Archiving 

 to 
/usr/local/hudson/data/jobs/magnolia_main-trunk/modules/info.magnolia$magnolia-module-workflow/builds/2010-02-17_18-16-54/archive/info.magnolia/magnolia-module-workflow/4.3-SNAPSHOT/magnolia-module-workflow-4.3-SNAPSHOT-bundle.tar.gz
[INFO] [checkstyle:checkstyle]
[WARNING] File encoding has not been set, using platform encoding MacRoman, 
i.e. build is platform dependent!
[INFO] Starting audit...
Audit done.

[INFO] [checkstyle:check {execution: default}]
[INFO] [install:install]
[INFO] Installing 

 to 
/usr/local/hudson/maven-local-repo/info/magnolia/magnolia-module-workflow/4.3-SNAPSHOT/magnolia-module-workflow-4.3-SNAPSHOT.jar
[INFO] Installing 

 to 
/usr/local/hudson/maven-local-repo/info/magnolia/magnolia-module-workflow/4.3-SNAPSHOT/magnolia-module-workflow-4.3-SNAPSHOT-bundle.zip
[INFO] Installing 

 to 
/usr/local/hudson/maven-local-repo/info/magnolia/magnolia-module-workflow/4.3-SNAPSHOT/magnolia-module-workflow-4.3-SNAPSHOT-bundle.tar.gz
[INFO] 
[INFO] Building magnolia-module-samples
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory 

[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 17. February 2010 (scope: 
project)
[INFO] Property magnoliaReleaseDate set to value 17. February 2010 (scope: 
project)
[INFO] Property magnoliaNiceVersion set to value 4.3 (Snapshot: 17.02.2010 
18:22:15) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Samples Module (scope: 
project)
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 34 resources
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 7 source files to 

[INFO] [compiler:testCompile {execution: compile-tests}]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory

[magnolia-dev] Hudson build is back to normal: magnolia_main-trunk #1382

2010-02-17 Thread Hudson CI 

See 




For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: