[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3227) Paragraphs/dialogs reloading fails when invalid paragraph definition is in place

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28679#action_28679
 ] 

Hudson CI server commented on MAGNOLIA-3227:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#1717|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1717/]
 MAGNOLIA-3227
Warning is throwed when invalid paragraph definition is set.


 Paragraphs/dialogs reloading fails when invalid paragraph definition is in 
 place
 

 Key: MAGNOLIA-3227
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3227
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Ondřej Chytil
 Attachments: 
 config.modules.standard-templating-kit.paragraphs.teasers.stkTeaserAccordionLinkList.xml,
  log


 See the log snippet. 
 For closer informations you can reproduce the issue with attached xml.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3227) Paragraphs/dialogs reloading fails when invalid paragraph definition is in place

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28680#action_28680
 ] 

Hudson CI server commented on MAGNOLIA-3227:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#1718|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1718/]
 MAGNOLIA-3227
Warning message changed to error.


 Paragraphs/dialogs reloading fails when invalid paragraph definition is in 
 place
 

 Key: MAGNOLIA-3227
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3227
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Ondřej Chytil
 Attachments: 
 config.modules.standard-templating-kit.paragraphs.teasers.stkTeaserAccordionLinkList.xml,
  log


 See the log snippet. 
 For closer informations you can reproduce the issue with attached xml.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3227) Paragraphs/dialogs reloading fails when invalid paragraph definition is in place

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28682#action_28682
 ] 

Hudson CI server commented on MAGNOLIA-3227:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#14|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/14/]
 MAGNOLIA-3227 backport of r35102, 35103


 Paragraphs/dialogs reloading fails when invalid paragraph definition is in 
 place
 

 Key: MAGNOLIA-3227
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3227
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Ondřej Chytil
 Fix For: 4.3.x, 5.0

 Attachments: 
 config.modules.standard-templating-kit.paragraphs.teasers.stkTeaserAccordionLinkList.xml,
  log


 See the log snippet. 
 For closer informations you can reproduce the issue with attached xml.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MGNLSTK-641) When site root is not on level one, navigation does not work properly

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


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

Federico Grilli updated MGNLSTK-641:


Patch included: [Yes]
Attachment: STKTemplateModel.patch
SiteNavigationModel.patch

 When site root is not on level one, navigation does not work properly
 -

 Key: MGNLSTK-641
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-641
 Project: Magnolia Standard Templating Kit
  Issue Type: Improvement
  Components: base system
Reporter: Federico Grilli
Assignee: Federico Grilli
 Fix For: 1.3.x

 Attachments: SiteNavigationModel.patch, STKTemplateModel.patch


 This issue came about when working on the mcs site with Namics. Here is an 
 excerpt from their email analyzing the problem: 
 {quote}With the deep website-structure (mcs/basel/de) we have the problem 
 that the verticalNavigation and contentNavigation do not work properly: 
 In the verticalNavigation the pages on level 1 and 2 are shown instead of 
 level 3 and 4 (if we do not have a horizontalNavigation, but also with that 
 we would have a problem). And the contentNavigation is not shown at all. 
 The reason is that the siteroot-level is not taken into account (in the 
 demo-projekt it is 1, in our case 3). 
 {quote} 
 Problem is the site root is currently hardcoded in stk code. Patches were 
 provided and are going to be attached. 

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3227) Paragraphs/dialogs reloading fails when invalid paragraph definition is in place

2010-06-17 Thread on behalf of Ondřej Chytil


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

Ondřej Chytil updated MAGNOLIA-3227:


Fix Version/s: 4.3.3
   (was: 4.3.x)
  Description: 
See the log snippet. 
For closer informations you can reproduce the issue with attached xml.


  was:

See the log snippet. 
For closer informations you can reproduce the issue with attached xml.



 Paragraphs/dialogs reloading fails when invalid paragraph definition is in 
 place
 

 Key: MAGNOLIA-3227
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3227
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Ondřej Chytil
 Fix For: 4.3.3, 5.0

 Attachments: 
 config.modules.standard-templating-kit.paragraphs.teasers.stkTeaserAccordionLinkList.xml,
  log


 See the log snippet. 
 For closer informations you can reproduce the issue with attached xml.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


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

Zdenek Skodik reassigned MAGNOLIA-3229:
---

Assignee: Zdenek Skodik  (was: Boris Kraft)

 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik

 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Work started: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


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

Work on MAGNOLIA-3229 started by Zdenek Skodik.

 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik

 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Work started: (MGNLFORM-48) Form field 'selection': default value is not used - null is passed to the freemarker

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


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

Work on MGNLFORM-48 started by Zdenek Skodik.

 Form field 'selection': default value is not used - null is passed to the 
 freemarker
 -

 Key: MGNLFORM-48
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-48
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Christian Ringele
Assignee: Zdenek Skodik

 When adding a 'selection' field, and defining a label:value, the value is 
 passed to the template if the checkbox is checked.
 If not checked, the defined default value should be passed. But 'null' is 
 passed to the freemaker instead.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Assigned: (MGNLFORM-48) Form field 'selection': default value is not used - null is passed to the freemarker

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


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

Zdenek Skodik reassigned MGNLFORM-48:
-

Assignee: Zdenek Skodik  (was: Teresa Miyar)

 Form field 'selection': default value is not used - null is passed to the 
 freemarker
 -

 Key: MGNLFORM-48
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-48
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Christian Ringele
Assignee: Zdenek Skodik

 When adding a 'selection' field, and defining a label:value, the value is 
 passed to the template if the checkbox is checked.
 If not checked, the defined default value should be passed. But 'null' is 
 passed to the freemaker instead.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28690#action_28690
 ] 

Hudson CI server commented on MAGNOLIA-3229:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#1719|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1719/]
 MAGNOLIA-3229 - fix for 5.0


 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik

 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




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

2010-06-17 Thread Hudson CI

See http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/809/changes

Changes:

[zdenekskodik] MAGNOLIA-3229 - fix for 5.0

--
[...truncated 4090 lines...]
Downloading: 
http://download.java.net/maven/2//org/apache/maven/maven-artifact-manager/2.0/maven-artifact-manager-2.0.pom
Downloading: 
http://mirrors.ibiblio.org/pub/mirrors/maven2//org/apache/maven/maven-artifact-manager/2.0/maven-artifact-manager-2.0.pom
1K downloaded
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://maven.atlassian.com/public//org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/restricted/org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/projects/org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/internal/org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/enterprise/org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://download.java.net/maven/2//org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
Downloading: 
http://mirrors.ibiblio.org/pub/mirrors/maven2//org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom
1K downloaded
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://maven.atlassian.com/public//org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/restricted/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/projects/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/internal/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/enterprise/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://download.java.net/maven/2//org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
Downloading: 
http://mirrors.ibiblio.org/pub/mirrors/maven2//org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom
723b downloaded
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://maven.atlassian.com/public//org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://repo.magnolia-cms.com/restricted/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://repo.magnolia-cms.com/projects/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://repo.magnolia-cms.com/internal/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://repo.magnolia-cms.com/enterprise/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://download.java.net/maven/2//org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
Downloading: 
http://mirrors.ibiblio.org/pub/mirrors/maven2//org/apache/maven/wagon/wagon-provider-api/1.0-alpha-5/wagon-provider-api-1.0-alpha-5.pom
4K downloaded
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom
Downloading: 
http://maven.atlassian.com/public//org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom
Downloading: 
http://maven.atlassian.com/public//org/apache/maven/shared/file-management/1.2/file-management-1.2.pom
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom
Downloading: 
http://repo.magnolia-cms.com/m2/org/apache/maven/shared/maven-shared-components/8/maven-shared-components-8.pom
Downloading: 
http://maven.atlassian.com/public//org/apache/maven/shared/maven-shared-components/8/maven-shared-components-8.pom
Downloading: 

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28691#action_28691
 ] 

Hudson CI server commented on MAGNOLIA-3229:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.1-branch 
#32|http://hudson.magnolia-cms.com/job/magnolia_main-4.1-branch/32/]
 MAGNOLIA-3229 - backport of r35111 into 4.1 branch for the case we'll 
release something there again


 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik

 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28692#action_28692
 ] 

Hudson CI server commented on MAGNOLIA-3229:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.2-branch 
#33|http://hudson.magnolia-cms.com/job/magnolia_main-4.2-branch/33/]
 MAGNOLIA-3229 - backport of r35111 into 4.2 branch


 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik

 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MGNLFORM-49) formSelection: treat the case when no {{labels}} are definied

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


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

Zdenek Skodik updated MGNLFORM-49:
--

Affects Version/s: 1.1.1

 formSelection: treat the case when no {{labels}} are definied
 -

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Zdenek Skodik
Assignee: Teresa Miyar

 At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Created: (MGNLFORM-49) formSelection: treat the case when no {{labels}} are definied

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

formSelection: treat the case when no {{labels}} are definied
-

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Reporter: Zdenek Skodik
Assignee: Teresa Miyar


At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MGNLFORM-49) formSelection: treat the case when no {{labels}} are definied

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


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

Zdenek Skodik updated MGNLFORM-49:
--

Attachment: log

 formSelection: treat the case when no {{labels}} are definied
 -

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Zdenek Skodik
Assignee: Teresa Miyar
 Attachments: log


 At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Work started: (MGNLFORM-49) formSelection: treat the case when no labels are definied

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


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

Work on MGNLFORM-49 started by Zdenek Skodik.

 formSelection: treat the case when no labels are definied
 -

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Attachments: log


 At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Assigned: (MGNLFORM-49) formSelection: treat the case when no labels are definied

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


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

Zdenek Skodik reassigned MGNLFORM-49:
-

Assignee: Zdenek Skodik  (was: Teresa Miyar)

 formSelection: treat the case when no labels are definied
 -

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Attachments: log


 At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MGNLFORM-49) formSelection: treat the case when no labels are definied

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


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

Zdenek Skodik updated MGNLFORM-49:
--

Summary: formSelection: treat the case when no labels are definied  (was: 
formSelection: treat the case when no {{labels}} are definied)

 formSelection: treat the case when no labels are definied
 -

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Zdenek Skodik
Assignee: Teresa Miyar
 Attachments: log


 At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Commented: (MGNLFORM-49) formSelection: treat the case when no labels are definied

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


[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28693#action_28693
 ] 

Hudson CI server commented on MGNLFORM-49:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1148|http://hudson.magnolia-cms.com/job/magnolia-module-form/1148/]
 MGNLFORM-49


 formSelection: treat the case when no labels are definied
 -

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Attachments: log


 At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Resolved: (MGNLFORM-49) formSelection: treat the case when no labels are definied

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


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

Zdenek Skodik resolved MGNLFORM-49.
---

Fix Version/s: 1.1.2
   Resolution: Fixed

 formSelection: treat the case when no labels are definied
 -

 Key: MGNLFORM-49
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-49
 Project: Magnolia Form Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Fix For: 1.1.2

 Attachments: log


 At the moment ugly freemarker exception is thrown. See the attachment.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-module -templating #810

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-module-templating/810/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-jaas #810

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-jaas/810/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-projec t #810

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-project/810/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-gui #810

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-gui/810/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-module -admininterface #810

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-module-admininterface/810/




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




[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


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

Zdenek Skodik resolved MAGNOLIA-3229.
-

Fix Version/s: 4.2.x
   4.1.x
   4.3.3
   5.0
   4.0.x
   Resolution: Fixed

 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Fix For: 4.2.x, 4.1.x, 4.3.3, 5.0, 4.0.x


 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28694#action_28694
 ] 

Hudson CI server commented on MAGNOLIA-3229:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.0-branch 
#77|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/77/]
 MAGNOLIA-3229 - backport of r35111 to 4.0 branch


 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Fix For: 4.2.x, 4.1.x, 4.3.3, 5.0, 4.0.x


 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3230) incorrect indication of status after edit during activation workflow

2010-06-17 Thread JIRA (on behalf of Jan Haderka)


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

Jan Haderka updated MAGNOLIA-3230:
--

Description: 
If a page is edited while it is within the activation workflow, the edits will 
be reflected on the authoring system, but the (default implementation of the) 
activation workflow will publish the original version of the page, regardless 
of the edits.

The problem is that the status indication for the page will change to green 
when the activation workflow completes, even though the version published is 
not the most recent one.

So this creates a situation where the page is marked as green on the authoring 
system, even though it is not the same version as on the live system. 


  was:

If a page is edited while it is within the activation workflow, the edits will 
be reflected on the authoring system, but the (default implementation of the) 
activation workflow will publish the original version of the page, regardless 
of the edits.

The problem is that the status indication for the page will change to green 
when the activation workflow completes, even though the version published is 
not the most recent one.

So this creates a situation where the page is marked as green on the authoring 
system, even though it is not the same version as on the live system. 


Component/s: activation
 workflow

 incorrect indication of status after edit during activation workflow
 

 Key: MAGNOLIA-3230
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3230
 Project: Magnolia
  Issue Type: Bug
  Components: activation, workflow
Affects Versions: 4.3.2
 Environment: Tested under Windows, using Magnolia Tomcat Bundle for 
 EE 4.3.2
Reporter: Richard Unger
Assignee: Grégory Joseph

 If a page is edited while it is within the activation workflow, the edits 
 will be reflected on the authoring system, but the (default implementation of 
 the) activation workflow will publish the original version of the page, 
 regardless of the edits.
 The problem is that the status indication for the page will change to green 
 when the activation workflow completes, even though the version published is 
 not the most recent one.
 So this creates a situation where the page is marked as green on the 
 authoring system, even though it is not the same version as on the live 
 system. 

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Moved: (MAGNOLIA-3230) incorrect indication of status after edit during activation workflow

2010-06-17 Thread JIRA (on behalf of Jan Haderka)


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

Jan Haderka moved MGNLEE-182 to MAGNOLIA-3230:
--

  Project: Magnolia  (was: Magnolia Enterprise Edition)
  Key: MAGNOLIA-3230  (was: MGNLEE-182)
Affects Version/s: 4.3.2
   (was: 4.3.2)
 Security: (was: Public)

 incorrect indication of status after edit during activation workflow
 

 Key: MAGNOLIA-3230
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3230
 Project: Magnolia
  Issue Type: Bug
  Components: activation, workflow
Affects Versions: 4.3.2
 Environment: Tested under Windows, using Magnolia Tomcat Bundle for 
 EE 4.3.2
Reporter: Richard Unger
Assignee: Grégory Joseph

 If a page is edited while it is within the activation workflow, the edits 
 will be reflected on the authoring system, but the (default implementation of 
 the) activation workflow will publish the original version of the page, 
 regardless of the edits.
 The problem is that the status indication for the page will change to green 
 when the activation workflow completes, even though the version published is 
 not the most recent one.
 So this creates a situation where the page is marked as green on the 
 authoring system, even though it is not the same version as on the live 
 system. 

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-module -templating-components #811

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-module-templating-components/811/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » GenUIne Admin C entral #811

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-genuine-central/811/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-module -cache #811

2010-06-17 Thread Hudson CI

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




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » CMS Tag Library #811

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-taglib-cms/811/




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




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

2010-06-17 Thread Hudson CI

See http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/811/

--
[...truncated 1402 lines...]
[INFO] Installing 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-module-templating-components/target/magnolia-module-templating-components-5.0-SNAPSHOT.jar
 to 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/.repository/info/magnolia/magnolia-module-templating-components/5.0-SNAPSHOT/magnolia-module-templating-components-5.0-SNAPSHOT.jar
[INFO] Installing 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-module-templating-components/target/magnolia-module-templating-components-5.0-SNAPSHOT-bundle.zip
 to 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/.repository/info/magnolia/magnolia-module-templating-components/5.0-SNAPSHOT/magnolia-module-templating-components-5.0-SNAPSHOT-bundle.zip
[INFO] Installing 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-module-templating-components/target/magnolia-module-templating-components-5.0-SNAPSHOT-bundle.tar.gz
 to 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/.repository/info/magnolia/magnolia-module-templating-components/5.0-SNAPSHOT/magnolia-module-templating-components-5.0-SNAPSHOT-bundle.tar.gz
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] 
[INFO] Building CMS Tag Library
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/target
[TASKS] Scanning folder 
'http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/src/main/java'
 for tasks ... 
[TASKS] Found 7.
[TASKS] Scanning folder 
'http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/src/test/java'
 for tasks ... 
[TASKS] Found 1.
[TASKS] Scanning folder 
'http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/src/main/resources'
 for tasks ... 
[TASKS] Found 0.
[TASKS] Scanning folder 
'http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/src/main/resources'
 for tasks ... 
[TASKS] Found 0.
[TASKS] Skipping non-existent folder 
'http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/target/generated-resources/taglibs'...
[TASKS] Scanning folder 
'http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/src/test/resources'
 for tasks ... 
[TASKS] Found 0.
[TASKS] Scanning folder 
'http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/src/test/java'
 for tasks ... 
[TASKS] Found 1.
[TASKS] File encoding has not been set in pom.xml, using platform encoding 
MacRoman, i.e. build is platform dependent (see a 
href=http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding;Maven
 FAQ/a).
[INFO] [enforcer:enforce {execution: enforce}]
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [2-xdoclet2:xdoclet {execution: xdoclet-tld}]
Running org.xdoclet.plugin.web.TaglibPlugin
Unknown tag: @TODO: in 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/src/main/java/info/magnolia/cms/taglibs/EditButton.java
 (line 187)
[TASKS] Skipping maven reporter: there is already a result available.[INFO] 
[setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 17. June 2010 (scope: project)
[INFO] Property magnoliaReleaseDate set to value 17. June 2010 (scope: project)
[INFO] Property magnoliaNiceVersion set to value 5.0 (Snapshot: 17.06.2010 
15:47:01) (scope: project)
[INFO] Property magnoliaNiceName set to value CMS Tag Library (scope: project)

[TASKS] Skipping maven reporter: there is already a result available.[INFO] 
[remote-resources:process {execution: default}]

[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[TASKS] Skipping maven reporter: there is already a result available.[INFO] 
Copying 0 resource
[INFO] Copying 1 resource
[INFO] Copying 3 resources

[TASKS] Skipping maven reporter: there is already a result available.[INFO] 
[compiler:compile]
[INFO] Compiling 32 source files to 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/target/classes

[TASKS] Skipping maven reporter: there is already a result available.[INFO] 
[compiler:testCompile {execution: compile-tests}]
[INFO] Compiling 5 source files to 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/ws/trunk/magnolia-taglib-cms/target/test-classes

[INFO] [resources:testResources]

[magnolia-dev] Build failed in Hudson: magnolia_main-4.3-branch #15

2010-06-17 Thread Hudson CI

See http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/15/changes

Changes:

[zdenekskodik] MAGNOLIA-3229 - fix for 4.3 branch

--
[...truncated 205 lines...]
Running info.magnolia.setup.for3_5.CheckAndUpdateExistingFiltersTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.387 sec
Running info.magnolia.module.delta.MoveAndRenamePropertyTaskTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running info.magnolia.nodebuilder.task.NodeBuilderTaskTest
2010-06-17 13:08:35,167 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
2010-06-17 13:08:35,558 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.858 sec
Running info.magnolia.module.model.VersionComparatorTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running info.magnolia.cms.util.WebXmlUtilTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.115 sec
Running info.magnolia.cms.filters.ServletDispatchingFilterTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.048 sec
Running info.magnolia.cms.security.AccessManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running info.magnolia.test.SelfTest
2010-06-17 13:08:35,941 WARN  
t.core.security.authentication.AbstractLoginModule: No credentials available - 
try default (anonymous) authentication.
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.121 sec
Running info.magnolia.module.model.reader.DependencyLevelComparatorTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running info.magnolia.module.delta.BootstrapConditionallyTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running info.magnolia.module.delta.PropertyValuesTaskTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running info.magnolia.freemarker.models.ContentModelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec
Running info.magnolia.cms.util.SiblingsHelperTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running info.magnolia.cms.security.auth.callback.RedirectClientCallbackTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running info.magnolia.cms.i18n.DefaultI18NContentSupportTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.236 sec
Running info.magnolia.cms.util.ExtendingContentWrapperTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.561 sec
Running info.magnolia.cms.util.WorkspaceXmlUtilTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running info.magnolia.cms.util.ClasspathResourcesUtilTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running info.magnolia.context.WebContextImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec
Running info.magnolia.cms.filters.FilterTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.204 sec
Running info.magnolia.nodebuilder.NodeBuilderTest
2010-06-17 13:08:37,416 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
2010-06-17 13:08:37,823 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
2010-06-17 13:08:38,392 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.42 sec
Running info.magnolia.cms.core.version.BaseVersionManagerTest
2010-06-17 13:08:38,914 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.518 sec
Running info.magnolia.freemarker.FreemarkerHelperTest
Tests run: 51, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.304 sec
Running info.magnolia.module.delta.BackupTaskTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec
Running info.magnolia.nodebuilder.OpsTest
2010-06-17 13:08:39,730 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
2010-06-17 13:08:40,143 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
2010-06-17 13:08:40,575 WARN  info.magnolia.context.AbstractRepositoryStrategy  
: won't close session because of registered observation listener config
2010-06-17 13:08:41,038 WARN  

[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-modul e-exchange-simple #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-module-exchange-simple/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » CMS Tag Librar y #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-taglib-cms/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-gui #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-gui/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-modul e-fckeditor #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-module-fckeditor/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-modul e-templating-components #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-module-templating-components/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-jaas #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-jaas/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-modul e-store-client #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-module-store-client/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-modul e-cache #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-module-cache/16/




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




[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

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


[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28696#action_28696
 ] 

Hudson CI server commented on MAGNOLIA-3229:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#16|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/16/]
 

 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Fix For: 4.2.x, 4.1.x, 4.3.3, 5.0, 4.0.x


 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » CMS Utility Ta g Library #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-taglib-utility/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-modul e-samples #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-module-samples/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-modul e-templating #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-module-templating/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch #16

2010-06-17 Thread Hudson CI

See http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/16/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-4.3-branch » magnolia-empty -webapp #16

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/info.magnolia$magnolia-empty-webapp/16/




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




[magnolia-dev] Build failed in Hudson: magnolia-bundle_4-3-branch #11

2010-06-17 Thread Hudson CI

See http://hudson.magnolia-cms.com/job/magnolia-bundle_4-3-branch/11/

--
[...truncated 132 lines...]
[INFO]   magnolia-bundle-parent
[INFO]   magnolia-bundled-webapp
[INFO]   magnolia-integration-tests-parent
[INFO]   magnolia-integration-tests-module
[INFO]   magnolia-test-webapp
[INFO]   magnolia-test-public-webapp
[INFO]   magnolia-integration-tests
[INFO]   magnolia-tomcat-bundle
[INFO] 
[INFO] Building magnolia-bundle-parent
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[TASKS] Skipping non-existent folder 
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-3-branch/ws/magnolia-bundle-4.3/src/main/java'...
[TASKS] Skipping non-existent folder 
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-3-branch/ws/magnolia-bundle-4.3/src/test/java'...
[TASKS] Skipping non-existent folder 
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-3-branch/ws/magnolia-bundle-4.3/src/main/resources'...
[TASKS] Skipping non-existent folder 
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-3-branch/ws/magnolia-bundle-4.3/src/main/resources'...
[TASKS] Skipping non-existent folder 
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-3-branch/ws/magnolia-bundle-4.3/src/test/resources'...
[TASKS] Skipping non-existent folder 
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-3-branch/ws/magnolia-bundle-4.3/src/test/java'...
[TASKS] File encoding has not been set in pom.xml, using platform encoding 
MacRoman, i.e. build is platform dependent (see a 
href=http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding;Maven
 FAQ/a).
[INFO] [enforcer:enforce {execution: enforce}]
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 17. June 2010 (scope: project)
[INFO] Property magnoliaReleaseDate set to value 17. June 2010 (scope: project)
[INFO] Property magnoliaNiceVersion set to value 4.3.3 (Snapshot: 17.06.2010 
17:13:12) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Bundle Parent (scope: 
project)
[TASKS] Skipping maven reporter: there is already a result available.
[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}]
[ERROR] Left side ($project.description) of '!=' operation has null value. 
Operation not possible. README.txt.vm [line 22, column 29]
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [site:attach-descriptor]
[INFO] Preparing checkstyle:check
[TASKS] Skipping maven reporter: there is already a result available.
[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] ** 
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File: 
org/apache/velocity/runtime/defaults/velocity.properties
[INFO] Default ResourceManager initializing. (class 
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated: 
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class 
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any 
resource loader.
[INFO] Velocimacro : error using  VM library template VM_global_library.vm : 
org.apache.velocity.exception.ResourceNotFoundException: Unable to find 
resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3215) Encapsulate usage on JackRabbit APIs to parse paths

2010-06-17 Thread JIRA (on behalf of Jan Haderka)


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

Jan Haderka updated MAGNOLIA-3215:
--

Affects Version/s: 4.0.3
   (was: 4.3.1)

 Encapsulate usage on JackRabbit APIs to parse paths
 ---

 Key: MAGNOLIA-3215
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3215
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.0.3
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.3.2


 Wrap the usage of JR specific APIs so when using other repository 
 implementations used does not need to keep JR jars around.
 The reason for using implementation specific API is that JCR API doesn't have 
 any methods to validate the path prior to attempt to use it and using 
 incorrect path results in an error logged by the JackRabbit.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3215) Encapsulate usage of JackRabbit specific API to parse paths

2010-06-17 Thread JIRA (on behalf of Jan Haderka)


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

Jan Haderka updated MAGNOLIA-3215:
--

Summary: Encapsulate usage of JackRabbit specific API to parse paths  (was: 
Encapsulate usage on JackRabbit APIs to parse paths)

 Encapsulate usage of JackRabbit specific API to parse paths
 ---

 Key: MAGNOLIA-3215
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3215
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.0.3
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.3.2


 Wrap the usage of JR specific APIs so when using other repository 
 implementations used does not need to keep JR jars around.
 The reason for using implementation specific API is that JCR API doesn't have 
 any methods to validate the path prior to attempt to use it and using 
 incorrect path results in an error logged by the JackRabbit.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3215) Encapsulate usage on JackRabbit APIs to parse paths

2010-06-17 Thread JIRA (on behalf of Jan Haderka)


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

Jan Haderka updated MAGNOLIA-3215:
--

Summary: Encapsulate usage on JackRabbit APIs to parse paths  (was: 
Usage on JackRabbit APIs)
Description: 
Wrap the usage of JR specific APIs so when using other repository 
implementations used does not need to keep JR jars around.

The reason for using implementation specific API is that JCR API doesn't have 
any methods to validate the path prior to attempt to use it and using incorrect 
path results in an error logged by the JackRabbit.

  was:Wrap the usage of JR specific APIs so when using other repository 
implementations used does not need to keep JR jars around.


 Encapsulate usage on JackRabbit APIs to parse paths
 ---

 Key: MAGNOLIA-3215
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3215
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.1
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.3.2


 Wrap the usage of JR specific APIs so when using other repository 
 implementations used does not need to keep JR jars around.
 The reason for using implementation specific API is that JCR API doesn't have 
 any methods to validate the path prior to attempt to use it and using 
 incorrect path results in an error logged by the JackRabbit.

-- 
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: dev-list-unsubscr...@magnolia-cms.com




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-module -store-client #812

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-module-store-client/812/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-module -workflow #812

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-module-workflow/812/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » CMS Utility Tag Library #812

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-taglib-utility/812/




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




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

2010-06-17 Thread Hudson CI

See http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/812/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-empty- webapp #812

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-empty-webapp/812/




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




[magnolia-dev] Hudson build is back to normal : magnolia_main-trunk-java6 » magnolia-module -samples #812

2010-06-17 Thread Hudson CI

See 
http://hudson.magnolia-cms.com/job/magnolia_main-trunk-java6/info.magnolia$magnolia-module-samples/812/




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