[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2517) Cleaner refactoring for previewMode

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2517:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#328|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/328/]
 MAGNOLIA-2245 /  previewMode is now in AggregationState and set by the 
InterceptFilter


> Cleaner refactoring for previewMode
> ---
>
> Key: MAGNOLIA-2517
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2517
> Project: Magnolia
>  Issue Type: Improvement
>  Components: admininterface, core, gui
>Reporter: Gregory Joseph
>Assignee: Gregory Joseph
> Fix For: 4.0
>
>
> While working on MAGNOLIA-2245, previewMode is being moved from 
> info.magnolia.cms.util.Resource to AggregationState.
> Given the InterceptFilter is setting this flag, and uses the session to do 
> so, it seems we could use a cleaner implementation.
> Using the session is somehow still needed, for instance to serve resources / 
> images appropriately.
> One of the things that bother me with the current implementation is that gui 
> components access the aggregation state freely (global state) - this c/should 
> instead be passed to the output methods.

-- 
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-2245) Review and suppress usage of deprecated code

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2245:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#328|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/328/]
  / MAGNOLIA-2517 previewMode is now in AggregationState and set by the 
InterceptFilter


> Review and suppress usage of deprecated code
> 
>
> Key: MAGNOLIA-2245
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2245
> Project: Magnolia
>  Issue Type: Task
>Reporter: Gregory Joseph
>Assignee: Gregory Joseph
> Fix For: 4.0
>
> Attachments: deprecation-report-for-core.zip
>
>
> We deprecated a lot of code for 3.5
> Unfortunately, we're showing a bad example by still using some of it 
> ourselves :) We should get rid of that.
> See http://confluence.magnolia-cms.com/display/DEV/Deprecation+cleanup+for+4.0

-- 
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-2517) Cleaner refactoring for previewMode

2008-12-16 Thread JIRA (on behalf of Gregory Joseph)


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

Gregory Joseph updated MAGNOLIA-2517:
-

Description: 
While working on MAGNOLIA-2245, previewMode is being moved from 
info.magnolia.cms.util.Resource to AggregationState.
Given the InterceptFilter is setting this flag, and uses the session to do so, 
it seems we could use a cleaner implementation.

Using the session is somehow still needed, for instance to serve resources / 
images appropriately.

One of the things that bother me with the current implementation is that gui 
components access the aggregation state freely (global state) - this c/should 
instead be passed to the output methods.

  was:
While working on MAGNOLIA-2245, previewMode is being moved from 
info.magnolia.cms.util.Resource to AggregationState.
Given the InterceptFilter is setting this flag, and uses the session to do so, 
it seems we could use a cleaner implementation.

Using the session is somehow still needed, for instance to serve resources / 
images appropriately.


> Cleaner refactoring for previewMode
> ---
>
> Key: MAGNOLIA-2517
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2517
> Project: Magnolia
>  Issue Type: Improvement
>  Components: admininterface, core, gui
>Reporter: Gregory Joseph
>Assignee: Gregory Joseph
> Fix For: 4.0
>
>
> While working on MAGNOLIA-2245, previewMode is being moved from 
> info.magnolia.cms.util.Resource to AggregationState.
> Given the InterceptFilter is setting this flag, and uses the session to do 
> so, it seems we could use a cleaner implementation.
> Using the session is somehow still needed, for instance to serve resources / 
> images appropriately.
> One of the things that bother me with the current implementation is that gui 
> components access the aggregation state freely (global state) - this c/should 
> instead be passed to the output methods.

-- 
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-2517) Cleaner refactoring for previewMode

2008-12-16 Thread JIRA (on behalf of Gregory Joseph)

Cleaner refactoring for previewMode
---

 Key: MAGNOLIA-2517
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2517
 Project: Magnolia
  Issue Type: Improvement
  Components: admininterface, core, gui
Reporter: Gregory Joseph
Assignee: Gregory Joseph
 Fix For: 4.0


While working on MAGNOLIA-2245, previewMode is being moved from 
info.magnolia.cms.util.Resource to AggregationState.
Given the InterceptFilter is setting this flag, and uses the session to do so, 
it seems we could use a cleaner implementation.

Using the session is somehow still needed, for instance to serve resources / 
images appropriately.

-- 
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-2516) Cleanup/consolidate i.m.cms.beans.runtime.File and the various Document classes

2008-12-16 Thread JIRA (on behalf of Gregory Joseph)

Cleanup/consolidate i.m.cms.beans.runtime.File and the various Document classes
---

 Key: MAGNOLIA-2516
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2516
 Project: Magnolia
  Issue Type: Improvement
  Components: core
Reporter: Gregory Joseph
Assignee: Philipp Bracher
 Fix For: 4.0


{{info.magnolia.cms.beans.runtime.File}}, 
{{info.magnolia.cms.beans.runtime.FileProperties}}, 
{{info.magnolia.cms.beans.runtime.Document}} and even 
{{info.magnolia.module.dms.beans.Document}} all seem to have a fairly similar 
purpose. They should be cleaned up, given better name(s) and packages.

-- 
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-bundle_trunk » magnolia-integration-t ests #156

2008-12-16 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/info.magnolia$magnolia-integration-tests/156/changes




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




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#324|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/324/]
  messages for dialogs and paragraphs


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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: (DOCU-63) Topic "Filter" > What to document in javadoc and what in the docu

2008-12-16 Thread JIRA (on behalf of Samuel Staehelin)

Topic "Filter"  > What to document in javadoc and what in the docu
--

 Key: DOCU-63
 URL: http://jira.magnolia-cms.com/browse/DOCU-63
 Project: Documentation
  Issue Type: Task
Affects Versions: short term
Reporter: Samuel Staehelin
Assignee: Gregory Joseph
 Fix For: mid term




-- 
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: (DOCU-62) Topic "Configuration Mechanisms" > Singletons and Configuration

2008-12-16 Thread JIRA (on behalf of Samuel Staehelin)

Topic  "Configuration Mechanisms" > Singletons and Configuration


 Key: DOCU-62
 URL: http://jira.magnolia-cms.com/browse/DOCU-62
 Project: Documentation
  Issue Type: Improvement
Affects Versions: short term
Reporter: Samuel Staehelin
Assignee: Gregory Joseph
Priority: Minor
 Fix For: mid term


Open todo and comments:

- instead of defining an implementation class one can define a path (leading /) 
which points to the config repository. The object is the loaded from there and 
reinitialized on configuration changes. (Philipp)

- do we want to go in details here about what a singleton is and how we 
implement this? I'd rather stress on the fact that these components are 
replaceable than how they're implemented - switched the paragraph order might 
suffice in changing this. (Greg)

-- 
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-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#323|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/323/]
  clean up messages


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#322|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/322/]
  messages for dialogs and paragraphs


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#320|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/320/]
  re-fixing class name


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-bundle_trunk » magnolia-integration-t ests #155

2008-12-16 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/info.magnolia$magnolia-integration-tests/155/changes




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




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#319|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/319/]
  clean import
 fix access to jsp sources


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-2366) Provide access to commonly used objects (content, page, etc) via context

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2366:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! 
[magnolia-bundle_trunk 
#154|http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/154/]
 back to 4.0-snapshot and fixed tests for MAGNOLIA-2506 and 


> Provide access to commonly used objects (content, page, etc) via context
> 
>
> Key: MAGNOLIA-2366
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2366
> Project: Magnolia
>  Issue Type: Improvement
>  Components: templating
>Reporter: Jan Haderka
>Assignee: Gregory Joseph
> Fix For: 4.0
>
>
> This will allow accessing such objects direcly from EL, thus simplify the 
> template coding.
> See 
> http://wiki.magnolia.info/display/DEV/3.7+Templating+notes#3.7Templatingnotes-4.2JSPELandFreemarkersupport
>  for details (not final yet)

-- 
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-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! 
[magnolia-bundle_trunk 
#154|http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/154/]
 back to 4.0-snapshot and fixed tests for  and MAGNOLIA-2366


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


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


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-bundle_trunk » magnolia-integration-t ests #154

2008-12-16 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/info.magnolia$magnolia-integration-tests/154/changes




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




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


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


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Gregory Joseph)


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

Gregory Joseph updated MAGNOLIA-2506:
-

Comment: was deleted

> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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] Deleted: (MAGNOLIA-2500) Samples: dev-oriented samples / used for integration tests

2008-12-16 Thread JIRA (on behalf of Gregory Joseph)


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

Gregory Joseph deleted MAGNOLIA-2500:
-


> Samples: dev-oriented samples / used for integration tests
> --
>
> Key: MAGNOLIA-2500
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2500
> Project: Magnolia
>  Issue Type: Task
>Reporter: Gregory Joseph
>Assignee: Teresa Miyar
>
> Rationale:
>  It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-2506) Samples: replace by dev-oriented samples

2008-12-16 Thread JIRA (on behalf of Gregory Joseph)


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

Gregory Joseph updated MAGNOLIA-2506:
-

Summary: Samples: replace by dev-oriented samples  (was: refactor 
module samples)
Description: 
Rationale:

It's been a very long time we're bothered by our current samples module; it was 
rarely up-to-date, and it never really fulfilled both of the goals it tried to 
achieve: providing usable examples of Magnolia usage AND providing a showcase 
for template developers.

Instead, we will now have a sample module geared towards template/module 
developers, which will certainly not show best-of-breed design and layout, but 
will attempt to encompass and demonstrate all features modules and templates 
can use.

Details / concept at:
http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module

Existing templates at:
http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/

This module will also be used to execute a bunch of integration tests - for 
instance for rendering validation.

  was:will now try to be generic samples for developers on how to create 
templates and access data


> Samples: replace by dev-oriented samples
> 
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> Rationale:
> It's been a very long time we're bothered by our current samples module; it 
> was rarely up-to-date, and it never really fulfilled both of the goals it 
> tried to achieve: providing usable examples of Magnolia usage AND providing a 
> showcase for template developers.
> Instead, we will now have a sample module geared towards template/module 
> developers, which will certainly not show best-of-breed design and layout, 
> but will attempt to encompass and demonstrate all features modules and 
> templates can use.
> Details / concept at:
> http://wiki.magnolia-cms.com/display/DEV/Dev+Samples+Module
> Existing templates at:
> http://svn.magnolia-cms.com/svn/community/bundle/trunk/magnolia-integration-tests/magnolia-integration-tests-module/
> This module will also be used to execute a bunch of integration tests - for 
> instance for rendering validation.

-- 
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-2506) refactor module samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#315|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/315/]
  no need to bottstrap servlet
 menu items


> refactor module samples
> ---
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> will now try to be generic samples for developers on how to create templates 
> and access data

-- 
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-module-cache #315

2008-12-16 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-cache/315/changes




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




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2506) refactor module samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! 
[magnolia_main-trunk 
#314|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/314/]
  search


> refactor module samples
> ---
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> will now try to be generic samples for developers on how to create templates 
> and access data

-- 
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 became unstable: ma gnolia_main-trunk » magnolia-module-cache #31 4

2008-12-16 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-cache/314/changes




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




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2504) DeploymentUtilsPage is completely outdated

2008-12-16 Thread JIRA (on behalf of Vasko Gjurovski)


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

Vasko Gjurovski commented on MAGNOLIA-2504:
---

Yes, I like the idea of automatically extract the jsps. However, I tried it and 
it does not extract all of the files (hmm..?). I know that the files are 
supposed to be in mgnl-files, and xmls in mgnl-bootrap (and so on), but am I 
required to have some kind of predefined structure beyond those folders (ex: in 
docroot are only css, js and imgs folders allowed?). I tried the new 
"extractor" of files, but it didnt help either. So what I have now is the 
following situation, some of the modules have all of their files extracted, 
some (one) has none, and one module have some of the files extracted, and some 
not.. very, very, very weird...

> DeploymentUtilsPage is completely outdated
> --
>
> Key: MAGNOLIA-2504
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2504
> Project: Magnolia
>  Issue Type: Sub-task
>  Components: admininterface, core
>Reporter: Gregory Joseph
>Assignee: Gregory Joseph
> Fix For: 4.0
>
>
> DeploymentUtilsPage is outdated - the only part of it that still works is the 
> i18n reload button. The rest... we're not sure. It's hardly relevant now that 
> we also support freemarker. We'll move the i18n button to the development 
> tools page, and trash this one completely.

-- 
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: (MGNLFORM-3) Forms: Error messages - Markup missing - Accessibility Problems

2008-12-16 Thread JIRA (on behalf of Teresa Miyar)


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

Teresa Miyar resolved MGNLFORM-3.
-

Resolution: Fixed

> Forms: Error messages - Markup missing - Accessibility Problems
> ---
>
> Key: MGNLFORM-3
> URL: http://jira.magnolia-cms.com/browse/MGNLFORM-3
> Project: Magnolia Form Module
>  Issue Type: Bug
>Reporter: Timo Wirth
>Assignee: Teresa Miyar
> Fix For: 1.0
>
>
> - Inform the user in the window / page title that something went wrong
>  Error Contact - Magnolia Media Edition
> - Inform the user in the label "Please correct the form"
> now
> 
> 
>  E-Mail:
> better
> *
> 
> 
> Please correct here: E-Mail:
> further details: forms-contact.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] Work started: (MGNLFORM-4) Add specific label to edit form

2008-12-16 Thread JIRA (on behalf of Teresa Miyar)


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

Work on MGNLFORM-4 started by Teresa Miyar.

> Add specific label to edit form
> ---
>
> Key: MGNLFORM-4
> URL: http://jira.magnolia-cms.com/browse/MGNLFORM-4
> Project: Magnolia Form Module
>  Issue Type: Improvement
>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: (MGNLFORM-4) Add specific label to edit form

2008-12-16 Thread JIRA (on behalf of Teresa Miyar)


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

Teresa Miyar resolved MGNLFORM-4.
-

Fix Version/s: 1.0
   Resolution: Fixed

> Add specific label to edit form
> ---
>
> Key: MGNLFORM-4
> URL: http://jira.magnolia-cms.com/browse/MGNLFORM-4
> Project: Magnolia Form Module
>  Issue Type: Improvement
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 1.0
>
>


-- 
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: (MGNLFORM-4) Add specific label to edit form

2008-12-16 Thread JIRA (on behalf of Teresa Miyar)

Add specific label to edit form
---

 Key: MGNLFORM-4
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-4
 Project: Magnolia Form Module
  Issue Type: Improvement
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] Commented: (MAGNOLIA-2506) refactor module samples

2008-12-16 Thread JIRA (on behalf of Hudson CI server)


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

Hudson CI server commented on MAGNOLIA-2506:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#313|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/313/]
  added search and servlet
 bootstrap samples


> refactor module samples
> ---
>
> Key: MAGNOLIA-2506
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2506
> Project: Magnolia
>  Issue Type: Improvement
>  Components: samples
>Reporter: Teresa Miyar
>Assignee: Teresa Miyar
> Fix For: 4.0
>
>
> will now try to be generic samples for developers on how to create templates 
> and access data

-- 
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: