[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2814) Mail command class not modified by update mechanism
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=23838#action_23838
]
Hudson CI server commented on MAGNOLIA-2814:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#933|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/933/]
add update task for mail module command
Mail command class not modified by update mechanism
---
Key: MAGNOLIA-2814
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2814
Project: Magnolia
Issue Type: Bug
Components: admininterface, mail, updatemechanism
Affects Versions: 4.1
Reporter: Grégory Joseph
Assignee: Teresa Miyar
Priority: Critical
Fix For: 4.1.1
When updating the docu instance from 3.6.5 to 4.1.1 (snapshot), somehow, the
mail command's class property was *not* updated!
After the update, it was still {{info.magnolia.cms.mail.commands.MailCommand}}
--
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-2814) Mail command class not modified by update mechanism
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=23839#action_23839
]
Hudson CI server commented on MAGNOLIA-2814:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-4.0-branch
#44|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/44/]
merged with trunk r26971
Mail command class not modified by update mechanism
---
Key: MAGNOLIA-2814
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2814
Project: Magnolia
Issue Type: Bug
Components: admininterface, mail, updatemechanism
Affects Versions: 4.1
Reporter: Grégory Joseph
Assignee: Teresa Miyar
Priority: Critical
Fix For: 4.1.1
When updating the docu instance from 3.6.5 to 4.1.1 (snapshot), somehow, the
mail command's class property was *not* updated!
After the update, it was still {{info.magnolia.cms.mail.commands.MailCommand}}
--
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 -bundle_4-0-branch » magnolia-tomcat-bundle #67
See
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/67/
--
[INFO]
[INFO] Building magnolia-tomcat-bundle
[INFO]task-segment: [clean, deploy]
[INFO]
[INFO] [clean:clean]
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/java'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[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] Scipping maven reporter: there is already a result available.
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaReleaseDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaNiceVersion set to value 4.0.3 (Snapshot: 04.08.2009
10:15:24) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Tomcat Bundle (scope:
project)
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [remote-resources:process {execution: default}]
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [bundle:download {execution: get-tomcat}]
[INFO] Downloading apache-tomcat-5.5.27.tar.gz from
http://www.apache.org/dist/tomcat/tomcat-5/v5.5.27/bin/apache-tomcat-5.5.27.tar.gz
[INFO] Extracting
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/tmp/apache-tomcat-5.5.27.tar.gz
to
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/target/extracted-tomcat
[TASKS] Scipping maven reporter: there is already a result available.
[HUDSON] Archiving
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/pom.xml
to
/usr/local/hudson/data/jobs/magnolia-bundle_4-0-branch/modules/info.magnolia$magnolia-tomcat-bundle/builds/2009-08-04_10-03-46/archive/info.magnolia/magnolia-tomcat-bundle/4.0.3-SNAPSHOT/pom.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Unexpected end of ZLIB input stream
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 13 minutes 16 seconds
[INFO] Finished at: Tue Aug 04 10:17:07 CEST 2009
[INFO] Final Memory: 45M/83M
[INFO]
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-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teresa Miyar reassigned MAGNOLIA-2813: -- Assignee: Teresa Miyar (was: Philipp Bärfuss) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites --- Key: MAGNOLIA-2813 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2813 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.0 Reporter: Grégory Joseph Assignee: Teresa Miyar Fix For: 4.1.1, 4.0.x An update task registered for 4.0 overrides the defaultPublicURI on *public* instances. What is this for? Shouldn't do like the website tree class does - do this only if the site is empty ? This happens even if there is content and templates. Updating the docu site from 3.5.8 to 4.1.1 broke the default public uri mapping, for example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Build failed in Hudson: magnolia -bundle_4-0-branch » magnolia-tomcat-bundle #68
See
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/68/
--
[INFO]
[INFO] Building magnolia-tomcat-bundle
[INFO]task-segment: [clean, deploy]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/target
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/java'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[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] Scipping maven reporter: there is already a result available.
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaReleaseDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaNiceVersion set to value 4.0.3 (Snapshot: 04.08.2009
10:45:32) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Tomcat Bundle (scope:
project)
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [remote-resources:process {execution: default}]
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [bundle:download {execution: get-tomcat}]
[INFO] apache-tomcat-5.5.27.tar.gz is already available, not downloading
[INFO] Extracting
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/tmp/apache-tomcat-5.5.27.tar.gz
to
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/target/extracted-tomcat
[TASKS] Scipping maven reporter: there is already a result available.
[HUDSON] Archiving
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/pom.xml
to
/usr/local/hudson/data/jobs/magnolia-bundle_4-0-branch/modules/info.magnolia$magnolia-tomcat-bundle/builds/2009-08-04_10-38-47/archive/info.magnolia/magnolia-tomcat-bundle/4.0.3-SNAPSHOT/pom.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Unexpected end of ZLIB input stream
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 minutes 42 seconds
[INFO] Finished at: Tue Aug 04 10:45:34 CEST 2009
[INFO] Final Memory: 46M/85M
[INFO]
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: (MGNLGA-1) Initial implementation of Google Analytics
Initial implementation of Google Analytics -- Key: MGNLGA-1 URL: http://jira.magnolia-cms.com/browse/MGNLGA-1 Project: Magnolia Google Analytics Issue Type: New Feature Reporter: Christian Ringele Assignee: Christian Ringele First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. -- 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: (MGNLGA-1) Initial implementation of Google Analytics
[ http://jira.magnolia-cms.com/browse/MGNLGA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLGA-1: --- Description: First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation showed, that Google Analytics is being implemented best as a module and not as additional functionality directly in STK. Future expansion are better to implement in a separate module like: - Customization/Updating of the used JS's - For later retrieving of data from GA was:First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation of Google Analytics -- Key: MGNLGA-1 URL: http://jira.magnolia-cms.com/browse/MGNLGA-1 Project: Magnolia Google Analytics Issue Type: New Feature Reporter: Christian Ringele Assignee: Christian Ringele First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation showed, that Google Analytics is being implemented best as a module and not as additional functionality directly in STK. Future expansion are better to implement in a separate module like: - Customization/Updating of the used JS's - For later retrieving of data from GA -- 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-2782) EditButton edits MainContent instead of CurrentContent
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka reassigned MAGNOLIA-2782: - Assignee: Jan Haderka (was: Philipp Bärfuss) EditButton edits MainContent instead of CurrentContent -- Key: MAGNOLIA-2782 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2782 Project: Magnolia Issue Type: Bug Components: taglibs Affects Versions: 4.0.1, 4.1 Reporter: Christian Menzel Assignee: Jan Haderka Priority: Critical Fix For: 4.1.1 Attachments: EditButton-patch.txt When using cms:loadPage/ before cms:editButton/ the edit dialog opens with the hande of the 'main' content in the parameter 'mgnlPath'. Expected is the handle of the 'current' content. -- 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: (MAGNOLIA-2831) cmsfn:currentPage() returns local content node
cmsfn:currentPage() returns local content node -- Key: MAGNOLIA-2831 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2831 Project: Magnolia Issue Type: Bug Components: taglibs Affects Versions: 4.1.1 Reporter: Will Scheidegger Assignee: Fabrizio Giustina When using cmsfn:currentPage() inside a paragraph it will return the paragraph instead of the page. I would assume that this also has to do with the deprecated Resource class because this used to work fine before. I did not have the time to dig further yet though... -- 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: (MAGNOLIA-2782) EditButton edits MainContent instead of CurrentContent
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka resolved MAGNOLIA-2782. --- Resolution: Fixed Done as of r26985. EditButton edits MainContent instead of CurrentContent -- Key: MAGNOLIA-2782 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2782 Project: Magnolia Issue Type: Bug Components: taglibs Affects Versions: 4.0.1, 4.1 Reporter: Christian Menzel Assignee: Jan Haderka Priority: Critical Fix For: 4.1.1 Attachments: EditButton-patch.txt When using cms:loadPage/ before cms:editButton/ the edit dialog opens with the hande of the 'main' content in the parameter 'mgnlPath'. Expected is the handle of the 'current' content. -- 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-2782) EditButton edits MainContent instead of CurrentContent
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=23844#action_23844 ] Hudson CI server commented on MAGNOLIA-2782: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #934|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/934/] EditBar should read handle from current content instead of from main content to behave properly in the context of node in which it is used. EditButton edits MainContent instead of CurrentContent -- Key: MAGNOLIA-2782 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2782 Project: Magnolia Issue Type: Bug Components: taglibs Affects Versions: 4.0.1, 4.1 Reporter: Christian Menzel Assignee: Jan Haderka Priority: Critical Fix For: 4.1.1 Attachments: EditButton-patch.txt When using cms:loadPage/ before cms:editButton/ the edit dialog opens with the hande of the 'main' content in the parameter 'mgnlPath'. Expected is the handle of the 'current' content. -- 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: (MGNLGA-1) Initial implementation of Google Analytics
[ http://jira.magnolia-cms.com/browse/MGNLGA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele resolved MGNLGA-1. Resolution: Fixed First implementation done. The module keeps its site configurations within it's config path, and not within the STK site configuration. For each STK site configuration a configuration within the module must be added, named the same as the STK site. The Module uses JQuery GA script which tracks the external/download/mailto links too. For start tracking a site only two values must be entered: - enabled=true - trackerID = your project/site Google Analytics trackerID provided by Google. Initial implementation of Google Analytics -- Key: MGNLGA-1 URL: http://jira.magnolia-cms.com/browse/MGNLGA-1 Project: Magnolia Google Analytics Issue Type: New Feature Reporter: Christian Ringele Assignee: Christian Ringele First implementation of the Google Analytics module as described in STK Jira task MGNLSTK-406. Initial implementation showed, that Google Analytics is being implemented best as a module and not as additional functionality directly in STK. Future expansion are better to implement in a separate module like: - Customization/Updating of the used JS's - For later retrieving of data from GA -- 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-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=23848#action_23848 ] Hudson CI server commented on MAGNOLIA-2813: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #935|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/935/] fixed by adding a new tasks that checks for templates before setting the defaulturi defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites --- Key: MAGNOLIA-2813 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2813 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.0 Reporter: Grégory Joseph Assignee: Teresa Miyar Fix For: 4.1.1, 4.0.x An update task registered for 4.0 overrides the defaultPublicURI on *public* instances. What is this for? Shouldn't do like the website tree class does - do this only if the site is empty ? This happens even if there is content and templates. Updating the docu site from 3.5.8 to 4.1.1 broke the default public uri mapping, for example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=23849#action_23849 ] Hudson CI server commented on MAGNOLIA-2813: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-4.0-branch #45|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/45/] merged with trunk r26992 defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites --- Key: MAGNOLIA-2813 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2813 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.0 Reporter: Grégory Joseph Assignee: Teresa Miyar Fix For: 4.1.1, 4.0.x An update task registered for 4.0 overrides the defaultPublicURI on *public* instances. What is this for? Shouldn't do like the website tree class does - do this only if the site is empty ? This happens even if there is content and templates. Updating the docu site from 3.5.8 to 4.1.1 broke the default public uri mapping, for example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Build failed in Hudson: magnolia -bundle_4-0-branch » magnolia-tomcat-bundle #70
See
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/70/
--
[INFO]
[INFO] Building magnolia-tomcat-bundle
[INFO]task-segment: [clean, deploy]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/target
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/java'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[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] Scipping maven reporter: there is already a result available.
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaReleaseDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaNiceVersion set to value 4.0.3 (Snapshot: 04.08.2009
16:12:44) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Tomcat Bundle (scope:
project)
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [remote-resources:process {execution: default}]
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [bundle:download {execution: get-tomcat}]
[INFO] apache-tomcat-5.5.27.tar.gz is already available, not downloading
[INFO] Extracting
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/tmp/apache-tomcat-5.5.27.tar.gz
to
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/target/extracted-tomcat
[TASKS] Scipping maven reporter: there is already a result available.
[HUDSON] Archiving
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/pom.xml
to
/usr/local/hudson/data/jobs/magnolia-bundle_4-0-branch/modules/info.magnolia$magnolia-tomcat-bundle/builds/2009-08-04_16-05-44/archive/info.magnolia/magnolia-tomcat-bundle/4.0.3-SNAPSHOT/pom.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Unexpected end of ZLIB input stream
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 minutes 56 seconds
[INFO] Finished at: Tue Aug 04 16:12:46 CEST 2009
[INFO] Final Memory: 46M/85M
[INFO]
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-2809) Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Teresa Miyar reassigned MAGNOLIA-2809:
--
Assignee: Teresa Miyar (was: Philipp Bärfuss)
Update task incorrectly moves 'templatePath' nodes of templates to parameters
subnode
-
Key: MAGNOLIA-2809
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2809
Project: Magnolia
Issue Type: Bug
Components: templating, updatemechanism
Affects Versions: 4.0
Reporter: Grégory Joseph
Assignee: Teresa Miyar
Priority: Blocker
Fix For: 4.1.1, 4.0.x
There are 2 conflicting tasks for templates:
# renamed {{path}} to {{templatePath}} - that is 100% correct
# move non-default template parameters to the {{parameters}} subnode. The bug
is that this task consider {{path}} to be the property to keep, while these
have just been renamed to {{templatePath}}.
Fixing this will require careful writing of update tasks for both 4.0.3 *and*
4.1.1
(!) workaround: move the {{templatePath}} nodedata of your templates from the
{{parameters}} subnode back into the template node itself.
--
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-2809) Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MAGNOLIA-2809 started by Teresa Miyar.
Update task incorrectly moves 'templatePath' nodes of templates to parameters
subnode
-
Key: MAGNOLIA-2809
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2809
Project: Magnolia
Issue Type: Bug
Components: templating, updatemechanism
Affects Versions: 4.0
Reporter: Grégory Joseph
Assignee: Teresa Miyar
Priority: Blocker
Fix For: 4.1.1, 4.0.x
There are 2 conflicting tasks for templates:
# renamed {{path}} to {{templatePath}} - that is 100% correct
# move non-default template parameters to the {{parameters}} subnode. The bug
is that this task consider {{path}} to be the property to keep, while these
have just been renamed to {{templatePath}}.
Fixing this will require careful writing of update tasks for both 4.0.3 *and*
4.1.1
(!) workaround: move the {{templatePath}} nodedata of your templates from the
{{parameters}} subnode back into the template node itself.
--
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 -bundle_4-0-branch » magnolia-tomcat-bundle #71
See
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/71/
--
[INFO]
[INFO] Building magnolia-tomcat-bundle
[INFO]task-segment: [clean, deploy]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/target
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/java'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[TASKS] Scipping non-existent folder
'http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/src/main/resources'...
[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] Scipping maven reporter: there is already a result available.
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaReleaseDate set to value 4. August 2009 (scope: project)
[INFO] Property magnoliaNiceVersion set to value 4.0.3 (Snapshot: 04.08.2009
17:04:15) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Tomcat Bundle (scope:
project)
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [remote-resources:process {execution: default}]
[TASKS] Scipping maven reporter: there is already a result available.
[INFO] [bundle:download {execution: get-tomcat}]
[INFO] apache-tomcat-5.5.27.tar.gz is already available, not downloading
[INFO] Extracting
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/tmp/apache-tomcat-5.5.27.tar.gz
to
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/target/extracted-tomcat
[TASKS] Scipping maven reporter: there is already a result available.
[HUDSON] Archiving
http://hudson.magnolia-cms.com/job/magnolia-bundle_4-0-branch/info.magnolia$magnolia-tomcat-bundle/ws/pom.xml
to
/usr/local/hudson/data/jobs/magnolia-bundle_4-0-branch/modules/info.magnolia$magnolia-tomcat-bundle/builds/2009-08-04_16-57-06/archive/info.magnolia/magnolia-tomcat-bundle/4.0.3-SNAPSHOT/pom.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Unexpected end of ZLIB input stream
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unexpected end of ZLIB
input stream
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:584)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:158)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:579)
at
[magnolia-dev] GenUIne prototyping
Dear all, you might have noticed that we get back on the tracks of GenUIne. We're preparing ourself to get started with prototyping: for an introduction on August's prototyping session please see the presentation from this afternoon under [1]. Regards, Vivian Steller Magnolia International Ltd. - vivian.stel...@magnolia-cms.com http://www.magnolia-cms.com Magnolia® - Simple Open-Source Content Management - [1] http://wiki.magnolia-cms.com/download/attachments/32473168/Magnolia+GenUIne+Prototyping+-+2.0.pdf 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: (MPBUN-10) Discard un-extractable archive
[ http://jira.magnolia-cms.com/browse/MPBUN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MPBUN-10 started by Grégory Joseph. Discard un-extractable archive -- Key: MPBUN-10 URL: http://jira.magnolia-cms.com/browse/MPBUN-10 Project: Magnolia Bundle Maven Plugin Issue Type: Improvement Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 1.1 Currently, if the tomcat download fails, the file still stays in the filesystem. Subsequent calls to the mojo will skip the download part, because the file is already present, and thus all builds will fail, since it can't be extracted. -- 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
