[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2858) ContextMenu.java: Comparing string with == instead of .equals

[JIRA (on behalf of Hudson CI server)]

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

Hudson CI server commented on MAGNOLIA-2858:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk-deploy 
#2|http://hudson.magnolia-cms.com/job/magnolia_main-trunk-deploy/2/]
  removed accidental use of ==


> ContextMenu.java: Comparing string with == instead of .equals 
> --
>
> Key: MAGNOLIA-2858
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2858
> Project: Magnolia
>  Issue Type: Bug
>  Components: gui
>Affects Versions: 4.1
>Reporter: Luca Boati
>Assignee: Grégory Joseph
> Fix For: 4.1.1
>
> Attachments: ContextMenu.patch
>
>
> Method "public ContextMenuItem getMenuItemByName(String name)" compares two 
> strings using == instead of equals method.
> I'm not able to customize  the function bar of a custom tree using context 
> menu items.
> cheers
> Luca

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




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

[magnolia-dev] Build failed in Hudson: magnolia -bundle_trunk » magnolia-integration-tests #5 20

[Hudson CI]

See 


--
[INFO] 
[INFO] Building magnolia-integration-tests
[INFO]task-segment: [clean, deploy]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory 

[TASKS] Skipping non-existent folder 
'
[TASKS] Skipping non-existent folder 
'
[TASKS] Skipping non-existent folder 
'
[TASKS] File encoding has not been set in pom.xml, using platform encoding 
MacRoman, i.e. build is platform dependent (see http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding";>Maven
 FAQ).
[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 1. September 2009 (scope: 
project)
[INFO] Property magnoliaReleaseDate set to value 1. September 2009 (scope: 
project)
[INFO] Property magnoliaNiceVersion set to value 4.1.1 (Snapshot: 01.09.2009 
22:04:26) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Integration Tests 
(scope: project)
[TASKS] Skipping maven reporter: there is already a result available.
[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] [compiler:testCompile {execution: compile-tests}]
[INFO] Compiling 4 source files to 

[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [compiler:testCompile {execution: default}]
[INFO] Nothing to compile - all classes are up to date
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [site:attach-descriptor]
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [cargo:start {execution: start}]
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [surefire:test {execution: default}]
[INFO] Surefire report directory: 


---
 T E S T S
---
Running info.magnolia.integrationtests.rendering.SimpleRenderingTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.33 sec
Running info.magnolia.integrationtests.MostBasicTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.391 sec
Running info.magnolia.integrationtests.GzipFilterTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.101 sec

Results :

Tests run: 12, Failures: 0, Errors: 0, Skipped: 0

[TASKS] Skipping maven reporter: there is already a result available.
[HUDSON] Recording test results
[INFO] [cargo:stop {execution: stop}]
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] Preparing checkstyle:check
[HUDSON] Archiving 

 to 
/usr/local/hudson/data/jobs/magnolia-bundle_trunk/modules/info.magnolia$magnolia-integration-tests/builds/2009-09-01_21-51-27/archive/info.magnolia/magnolia-integration-tests/4.1.1-SNAPSHOT/pom.xml
[INFO] [checkstyle:checkstyle]
[INFO] Source directory does not exist - skipping report.
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [checkstyle:check {execution: default}]
[INFO] Unable to perform checkstyle:check, unable to find checkstyle:checkstyle 
outputFile.
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [install:install]
[INFO] Installing 

 to 
/usr/local/hudson/maven-local-repo/info/magnolia/magnolia-integration-tests/4.1.1-SNAPSHOT/magnolia-integration-tests-4.1.1-SNAPSHOT.pom
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from magnolia.snaps

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2859) ModuleVersionHandler testability

[JIRA (on behalf of Hudson CI server)]

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

Hudson CI server commented on MAGNOLIA-2859:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-4.0-branch 
#56|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/56/]
  merging r27506:27511 from trunk - custom DependencyChecker can now be 
injected in ModuleManagerImpl (extracted interface),  
ModuleVersionHandlerTestCase now returns the InstallContext for further 
assertions


> ModuleVersionHandler testability
> 
>
> Key: MAGNOLIA-2859
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2859
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> Some improvements have already been committed, some more are coming up
> * abstract test class for version handlers
> * open up the ModuleManager constructor so that we can control more stuff 
> (module reader, dependency checker, ...)

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




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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites

[JIRA (on behalf of Hudson CI server)]

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

Hudson CI server commented on MAGNOLIA-2813:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-4.0-branch 
#56|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/56/]
  removed irrelevant test for 4.0
merging r27506:27515 from trunk -  Added testcases and rewrote task, getting 
rid of typos and hopefully making it a little more legible


> 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: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> 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: 

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2858) ContextMenu.java: Comparing string with == instead of .equals

[JIRA (on behalf of Hudson CI server)]

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

Hudson CI server commented on MAGNOLIA-2858:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#971|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/971/]
  removed accidental use of ==


> ContextMenu.java: Comparing string with == instead of .equals 
> --
>
> Key: MAGNOLIA-2858
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2858
> Project: Magnolia
>  Issue Type: Bug
>  Components: gui
>Affects Versions: 4.1
>Reporter: Luca Boati
>Assignee: Grégory Joseph
> Fix For: 4.1.1
>
> Attachments: ContextMenu.patch
>
>
> Method "public ContextMenuItem getMenuItemByName(String name)" compares two 
> strings using == instead of equals method.
> I'm not able to customize  the function bar of a custom tree using context 
> menu items.
> cheers
> Luca

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




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

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2814) Mail command class not modified by update mechanism

[on behalf of Grégory Joseph]

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

Grégory Joseph reassigned MAGNOLIA-2814:


Assignee: Grégory Joseph  (was: Teresa Miyar)

> 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: Grégory Joseph
>Priority: Critical
> Fix For: 4.1.1, 4.0.3
>
>
> 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: 

[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2858) ContextMenu.java: Comparing string with == instead of .equals

[on behalf of Grégory Joseph]

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

Grégory Joseph resolved MAGNOLIA-2858.
--

Fix Version/s: 4.1.1
   Resolution: Fixed
 Assignee: Grégory Joseph  (was: Fabrizio Giustina)

Oops! Thanks for spotting this Luca, patch applied :)

> ContextMenu.java: Comparing string with == instead of .equals 
> --
>
> Key: MAGNOLIA-2858
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2858
> Project: Magnolia
>  Issue Type: Bug
>  Components: gui
>Affects Versions: 4.1
>Reporter: Luca Boati
>Assignee: Grégory Joseph
> Fix For: 4.1.1
>
> Attachments: ContextMenu.patch
>
>
> Method "public ContextMenuItem getMenuItemByName(String name)" compares two 
> strings using == instead of equals method.
> I'm not able to customize  the function bar of a custom tree using context 
> menu items.
> cheers
> Luca

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




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

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2809) Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode

[on behalf of Grégory Joseph]

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

Grégory Joseph reassigned MAGNOLIA-2809:


Assignee: Grégory Joseph  (was: 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: Grégory Joseph
>Priority: Blocker
> Fix For: 4.1.1, 4.0.3
>
>
> 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: 

[magnolia-dev] [JIRA] Work started: (MAGNOLIA-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites

[on behalf of Grégory Joseph]

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

Work on MAGNOLIA-2813 started by Grégory Joseph.

> 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: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> 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: 

[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

[on behalf of Grégory Joseph]

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

Grégory Joseph reassigned MAGNOLIA-2813:


Assignee: Grégory Joseph  (was: Teresa Miyar)

> 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: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> 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: 

[magnolia-dev] Hudson build is back to normal: magnolia_main-trunk-java6 » magnolia-module-ad mininterface #223

[Hudson CI]

See 





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites

[JIRA (on behalf of Hudson CI server)]

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

Hudson CI server commented on MAGNOLIA-2813:


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

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

[magnolia-dev] Hudson build is back to normal: magnolia_main-trunk » magnolia-module-adminint erface #969

[Hudson CI]

See 





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

[magnolia-dev] Build failed in Hudson: magnolia _main-trunk » magnolia-module-admininterface #968

[Hudson CI]

See 


Changes:

[gjoseph] MAGNOLIA-2813 Added testcases and rewrote task, getting rid of typos 
and hopefully making it a little more legible

--
[INFO] 
[INFO] Building magnolia-module-admininterface
[INFO]task-segment: [clean, deploy]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory 

[TASKS] Scanning folder 
'
 for tasks ... 
[TASKS] Found 12.
[TASKS] Scanning folder 
'
 for tasks ... 
[TASKS] Found 42.
[TASKS] Scanning folder 
'
 for tasks ... 
[TASKS] Found 42.
[TASKS] File encoding has not been set in pom.xml, using platform encoding 
MacRoman, i.e. build is platform dependent (see http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding";>Maven
 FAQ).
[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 1. September 2009 (scope: 
project)
[INFO] Property magnoliaReleaseDate set to value 1. September 2009 (scope: 
project)
[INFO] Property magnoliaNiceVersion set to value 4.1.1 (Snapshot: 01.09.2009 
20:08:34) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Admininterface Module 
(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.
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] Copying 625 resources
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [compiler:compile]
[INFO] Compiling 83 source files to 

[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [compiler:testCompile {execution: compile-tests}]
[INFO] Compiling 4 source files to 

[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 0 resource
[INFO] Copying 3 resources
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [surefire:test]
[INFO] Surefire report directory: 


---
 T E S T S
---
Running info.magnolia.module.admininterface.commands.ActivationCommandTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.627 sec
Running info.magnolia.module.admininterface.SaveHandlerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
Running info.magnolia.module.admininterface.AdminTreeMVCHandlerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.095 sec
Running info.magnolia.module.admininterface.setup.AdminModuleVersionHandlerTest
2009-09-01 20:08:48,146 WARN  info.magnolia.module.InstallContextImpl   
: > Please set the default virtual URI mapping; it was incorrectly reset by a 
previous update.
2009-09-01 20:08:48,886 WARN  info.magnolia.module.InstallContextImpl   
: > Please set the default virtual URI mapping; it was incorrectly reset by a 
previous update.
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.735 sec

Results :

Tests run: 10, Failures: 0, Errors: 0, Skipped: 0

[TASKS] Skipping maven reporter: there is already a result available.
[HUDSON] Recording test results
[INFO] [jar:jar]
[INFO] Building jar: 

[magnolia-dev] Build failed in Hudson: magnolia _main-trunk-java6 » magnolia-module-admininterf ace #222

[Hudson CI]

See 


Changes:

[gjoseph] MAGNOLIA-2813 Added testcases and rewrote task, getting rid of typos 
and hopefully making it a little more legible

--
[INFO] 
[INFO] Building magnolia-module-admininterface
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting directory 

[TASKS] Scanning folder 
'
 for tasks ... 
[TASKS] Found 12.
[TASKS] Scanning folder 
'
 for tasks ... 
[TASKS] Found 42.
[TASKS] Scanning folder 
'
 for tasks ... 
[TASKS] Found 42.
[TASKS] File encoding has not been set in pom.xml, using platform encoding 
MacRoman, i.e. build is platform dependent (see http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding";>Maven
 FAQ).
[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 1. September 2009 (scope: 
project)
[INFO] Property magnoliaReleaseDate set to value 1. September 2009 (scope: 
project)
[INFO] Property magnoliaNiceVersion set to value 4.1.1 (Snapshot: 01.09.2009 
20:05:12) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Admininterface Module 
(scope: project)
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [remote-resources:process {execution: default}]
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 625 resources
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [compiler:compile]
[INFO] Compiling 83 source files to 

[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [compiler:testCompile {execution: compile-tests}]
[INFO] Compiling 4 source files to 

[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 0 resource
[INFO] Copying 3 resources
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[TASKS] Skipping maven reporter: there is already a result available.
[INFO] [surefire:test]
[INFO] Surefire report directory: 


---
 T E S T S
---
Running info.magnolia.module.admininterface.commands.ActivationCommandTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.67 sec
Running info.magnolia.module.admininterface.SaveHandlerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec
Running info.magnolia.module.admininterface.setup.AdminModuleVersionHandlerTest
2009-09-01 20:05:24,578 WARN  info.magnolia.module.InstallContextImpl   
: > Please set the default virtual URI mapping; it was incorrectly reset by a 
previous update.
2009-09-01 20:05:26,097 WARN  info.magnolia.module.InstallContextImpl   
: > Please set the default virtual URI mapping; it was incorrectly reset by a 
previous update.
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.403 sec
Running info.magnolia.module.admininterface.AdminTreeMVCHandlerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.042 sec

Results :

Tests run: 10, Failures: 0, Errors: 0, Skipped: 0

[TASKS] Skipping maven reporter: there is already a result available.
[HUDSON] Recording test resu

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2859) ModuleVersionHandler testability

[JIRA (on behalf of Hudson CI server)]

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

Hudson CI server commented on MAGNOLIA-2859:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#967|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/967/]
 : ModuleVersionHandlerTestCase now returns the InstallContext for further 
assertions


> ModuleVersionHandler testability
> 
>
> Key: MAGNOLIA-2859
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2859
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> Some improvements have already been committed, some more are coming up
> * abstract test class for version handlers
> * open up the ModuleManager constructor so that we can control more stuff 
> (module reader, dependency checker, ...)

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




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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2859) ModuleVersionHandler testability

[JIRA (on behalf of Hudson CI server)]

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

Hudson CI server commented on MAGNOLIA-2859:


Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#965|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/965/]
  a custom DependencyChecker can now be injected in ModuleManagerImpl 
(extracted interface)


> ModuleVersionHandler testability
> 
>
> Key: MAGNOLIA-2859
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2859
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> Some improvements have already been committed, some more are coming up
> * abstract test class for version handlers
> * open up the ModuleManager constructor so that we can control more stuff 
> (module reader, dependency checker, ...)

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




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

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2859) ModuleVersionHandler testability

[on behalf of Grégory Joseph]

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

Grégory Joseph reassigned MAGNOLIA-2859:


Assignee: Grégory Joseph  (was: Philipp Bärfuss)

> ModuleVersionHandler testability
> 
>
> Key: MAGNOLIA-2859
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2859
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> Some improvements have already been committed, some more are coming up
> * abstract test class for version handlers
> * open up the ModuleManager constructor so that we can control more stuff 
> (module reader, dependency checker, ...)

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




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

[magnolia-dev] [JIRA] Work started: (MAGNOLIA-2859) ModuleVersionHandler testability

[on behalf of Grégory Joseph]

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

Work on MAGNOLIA-2859 started by Grégory Joseph.

> ModuleVersionHandler testability
> 
>
> Key: MAGNOLIA-2859
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2859
> Project: Magnolia
>  Issue Type: Improvement
>  Components: core
>Reporter: Grégory Joseph
>Assignee: Grégory Joseph
> Fix For: 4.1.1, 4.0.3
>
>
> Some improvements have already been committed, some more are coming up
> * abstract test class for version handlers
> * open up the ModuleManager constructor so that we can control more stuff 
> (module reader, dependency checker, ...)

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




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

[magnolia-dev] [JIRA] Created: (MAGNOLIA-2859) ModuleVersionHandler testability

[on behalf of Grégory Joseph]

ModuleVersionHandler testability


 Key: MAGNOLIA-2859
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2859
 Project: Magnolia
  Issue Type: Improvement
  Components: core
Reporter: Grégory Joseph
Assignee: Philipp Bärfuss
 Fix For: 4.1.1, 4.0.3


Some improvements have already been committed, some more are coming up
* abstract test class for version handlers
* open up the ModuleManager constructor so that we can control more stuff 
(module reader, dependency checker, ...)

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




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

[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-2814) Mail command class not modified by update mechanism

[on behalf of Grégory Joseph]

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

Grégory Joseph reopened MAGNOLIA-2814:
--


tests missing

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

[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

[on behalf of Grégory Joseph]

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

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

tests missing.

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

[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-2809) Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode

[on behalf of Grégory Joseph]

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

Grégory Joseph reopened MAGNOLIA-2809:
--


tests missing

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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2854) Cleanup obsolete Jackrabbit configuration from default webapp

[on behalf of Grégory Joseph]

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

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

In fact, the default is (according to docs) set to 100, which seemed 
unnecessarily low.

The error JR logs should be harmless; and maybe we should document/recommend a 
longer timeout.

> Cleanup obsolete Jackrabbit configuration from default webapp
> -
>
> Key: MAGNOLIA-2854
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2854
> Project: Magnolia
>  Issue Type: Task
>  Components: core
>Reporter: Fabrizio Giustina
>Assignee: Grégory Joseph
> Fix For: 4.1.1
>
>
> The default webapp contains several jackrabbit sample configurations, but 
> most of them are outdated and should not be suggested.
> this is the list of current files with proposed blacklist:
> {noformat}
> jackrabbit-bundle-derby-search.xml -> ok
> jackrabbit-bundle-mysql-search.xml -> ok
> jackrabbit-derby-search.xml -> should be removed, non-bundle db persistence 
> managers are not suggested
> jackrabbit-file-nosearch.xml -> to be removed: "nosearch" configurations 
> doesn't work with magnolia anymore and the file persistence manager is 
> definitively not suggested
> jackrabbit-file-search.xml -> remove:  file persistence manager is 
> definitively not suggested
> jackrabbit-memory-search.xml -> keep (if update to jackrabbit 1.6 we can 
> modify this to add in memory search index configuration, new in 1.6 and 
> useful for development) 
> jackrabbit-mysql-search.xml -> remove, non-bundle db persistence managers are 
> not suggested
> {noformat} 
> The dtd of surviving configuration file should also be updated (now it's 14, 
> should be moved at least to 1.5 o 1.6 as soon as we upgrade the dependency); 
> all the configurations are now missing a data store, which should be added. 
> Mysql configuration should contain the "autoreconnect" parameter in urls.

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




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

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2386) sometimes the JCR access manager is not initialized

[on behalf of Grégory Joseph]

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

Grégory Joseph updated MAGNOLIA-2386:
-

Summary: sometimes the JCR access manager is not initialized  (was: 
sometimes the JCR access manger is not initialzed)

> sometimes the JCR access manager is not initialized
> ---
>
> Key: MAGNOLIA-2386
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2386
> Project: Magnolia
>  Issue Type: Bug
>Affects Versions: 3.5.8
> Environment: Magnolia 3.5.8, Java 1.6.0_04, Tomcat 6,CentOS 4.5
>Reporter: Philippe Marschall
>Assignee: Boris Kraft
>Priority: Minor
> Fix For: 4.0.x, 4.1.x, 3.6.x
>
>
> Form time to time we get the following stack trace in our logs:
> {code}
> java.lang.IllegalStateException: not initialized
> at 
> org.apache.jackrabbit.core.security.SimpleAccessManager.isGranted(SimpleAccessManager.java:116)
> at 
> org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:321)
> at org.apache.jackrabbit.core.NodeImpl.getProperty(NodeImpl.java:2579)
> at 
> info.magnolia.cms.core.DefaultNodeData.init(DefaultNodeData.java:207)
> at 
> info.magnolia.cms.core.DefaultNodeData.(DefaultNodeData.java:100)
> at 
> info.magnolia.cms.core.DefaultContent.getNodeData(DefaultContent.java:267)
> at info.magnolia.cms.security.MgnlUser.getLanguage(MgnlUser.java:325)
> at 
> info.magnolia.context.UserContextImpl.getLocale(UserContextImpl.java:59)
> at info.magnolia.context.MgnlContext.getLocale(MgnlContext.java:107)
> at 
> info.magnolia.cms.core.AggregationState.getLocale(AggregationState.java:176)
> at 
> ch.netcetera.swccore.magnolia.tags.Functions.getLocale(Functions.java:387)
> at 
> ch.netcetera.swccore.magnolia.filters.BaseFilter.setLanguage(BaseFilter.java:78)
> at 
> ch.netcetera.swccore.magnolia.filters.UrlToLanguageFilter.doFilter(UrlToLanguageFilter.java:50)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> ch.netcetera.swccore.magnolia.filters.DisableBrowserCacheFilter.doFilter(DisableBrowserCacheFilter.java:135)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> ch.netcetera.swccore.magnolia.filters.ForwardFilter.doFilter(ForwardFilter.java:49)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> ch.netcetera.swccore.magnolia.filters.AddExtensionFilter.doFilter(AddExtensionFilter.java:52)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> info.magnolia.cms.filters.CompositeFilter.doFilter(CompositeFilter.java:64)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> info.magnolia.cms.filters.VirtualUriFilter.doFilter(VirtualUriFilter.java:115)
> at 
> info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:62)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:73)
> at 
> ch.netcetera.swccore.magnolia.filters.MappedDiagnosticContextFilter.doFilter(MappedDiagnosticContextFilter.java:155)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:73)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:73)
> at 
> info.magnolia.cms.filters.CosMultipartRequestFilter.doFilter(CosMultipartRequestFilter.java:84)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
> at 
> info.magnolia.cms.security.BaseSecurityFilter.doFilter(BaseSecurityFilter.java:60)
> at 
> info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70)
> at 
> info.magnolia.cms.filter

[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites

[on behalf of Grégory Joseph]

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

Grégory Joseph reopened MAGNOLIA-2813:
--


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

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2858) ContextMenu.java: Comparing string with == instead of .equals

[JIRA (on behalf of Fabrizio Giustina)]

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

Fabrizio Giustina reassigned MAGNOLIA-2858:
---

Assignee: Fabrizio Giustina  (was: Boris Kraft)

> ContextMenu.java: Comparing string with == instead of .equals 
> --
>
> Key: MAGNOLIA-2858
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2858
> Project: Magnolia
>  Issue Type: Bug
>  Components: gui
>Affects Versions: 4.1
>Reporter: Luca Boati
>Assignee: Fabrizio Giustina
> Attachments: ContextMenu.patch
>
>
> Method "public ContextMenuItem getMenuItemByName(String name)" compares two 
> strings using == instead of equals method.
> I'm not able to customize  the function bar of a custom tree using context 
> menu items.
> cheers
> Luca

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




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

[magnolia-dev] Fwd: Product Team Meeting (2009.08.31): Protocol

[Philipp Bärfuss]

Went through the former Protocol

Summer Sprint

• grayed out many currently not relevant topics
	• the sprint will end this week and items will be moved back to the  
backlog

• Magnolia 3.6.7 is released (and now also announced)
• Magnolia 4.0.3 will be released (is ready)
	• Magonlia 4.1.1 will be released (have to investigate what we  
bundle)

• form, newsletter (review by Boris), stk
STK / Magnolia Backlog

• postponed after the conference
5.0 Concept

	• we proceed last week a first prototype and worked out the basics  
of the concept

• Vivian & Philipp are preparing the presentation for the converence
• we will finalize the prototype
...


Best regards,

Philipp Bärfuss
Magnolia International Ltd.

---
 Meet us at the Magnolia Conference
 http://www.magnolia-cms.com/conference
---

Magnolia®  - Simple Open Source Content Management



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

RE: [magnolia-dev] datamodule typedeletecommand

[Bert Leunis]

Hi Jan,

Thanks for the answer. I will stick to only deleting the tree then. The 
datanodes I will leave to the user to delete. And also the dialog definition.

Bye, Bert


-Original Message-
From: dev-list-ow...@magnolia-cms.com [mailto:dev-list-ow...@magnolia-cms.com] 
On Behalf Of Jan Haderka
Sent: maandag 31 augustus 2009 21:08
To: Magnolia Dev-List
Subject: Re: [magnolia-dev] datamodule typedeletecommand


On Mon, 2009-08-31 at 13:56 +0200, Bert Leunis wrote:
> Hi there (especially Jan or Philipp!),
> 
>  
> 
> I think the info.magnolia.module.data.commands.TypeDeleteCommand also
> needs to delete the type tree and the type dialog
> from /modules/data/config/. Do you agree? Deleting the data in the
> rootpath of that tree is not a good idea. In the new setup of the

The tree most likely yes ... the dialog ... I'm not so sure since the
dialog might be reused or referenced from other places. The biggest
problem with the deletion is anyway the fact that you can't delete the
type definiton ... ever (more in
http://jira.magnolia-cms.com/browse/MGNLDATA-30 )

Regarding the path deletion - yes, you are absolutely right, only the
items of given type should be deleted from the rootpath, but not the
rootpath itself, even if it is empty (since other type can have it
assigned at their root path, so if you want to delete it you would have
to first loop all other types definition to ensure it is not used).

When fixing those issues, please add them to Jira first and assign to
yourself so we can keep track of all the changes and reasons for them.
Thx.


Cheers,
Jan





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




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

RE: [magnolia-dev] how to get image of datatype to display in the tree

[Bert Leunis]

Jan, that is great, and works straight away. Just missed this bit of code.

Regards, Bert


-Original Message-
From: dev-list-ow...@magnolia-cms.com [mailto:dev-list-ow...@magnolia-cms.com] 
On Behalf Of Jan Haderka
Sent: maandag 31 augustus 2009 21:00
To: Magnolia Dev-List
Subject: Re: [magnolia-dev] how to get image of datatype to display in the tree


On Mon, 2009-08-31 at 09:06 +0200, Bert Leunis wrote:
> Goodmorning,
>  
> 
> tree.addItemType(typeDefinition.getName(), image);

I believe what you are looking for is:

tree.addItemType(typeDefinition.getName(), typeDefinition.getIcon());

the getIcon() method constructs path to the type image ... something
like: "/dataModule/typeImages/" + typeName + "/image" ... which is
actually an universal path to the type image ... you can type it
directly in the url and get the image back.

HTH,
Jan

> 
>  
> 
> But the image here is a String, not a Binary type or stream or
> whatever. Can you help me here?
> 
>  
> 
> Of course I can put the image in the dms, and then simply link to it,
> but I suspect there is a way to show the binary stored image in the
> tree, but I have no clue.
> 
>  
> 
> Regards, Bert
> 
>  
> 
> 
> 
> 
> 
> __
> 
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: 
> 
-- 
Best regards,

Jan Haderka
Magnolia International Ltd.

Meet us at the Magnolia Conference
http:/www.magnolia-cms.com/conference

Magnolia®  - Simple Open Source Content Management



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





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