From helpdesk at onehippo.com Fri Nov 7 14:08:41 2008 From: helpdesk at onehippo.com (Hippo Helpdesk) Date: Fri Nov 7 14:08:41 2008 Subject: [Hippoportal-dev] FW: [JIRA] Created: (PORTAL-89)jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMPenviroment variable, and does not seem configurable at build time. Message-ID: -----Original Message----- From: Hippo Helpdesk Sent: vrijdag 7 november 2008 12:43 To: hippoportal-dev@lists.hippo.nl Subject: [JIRA] Created: (PORTAL-89)jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMPenviroment variable, and does not seem configurable at build time. jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. ------------------------------------------------------------------------ ---------------------------------------------------------------- Key: PORTAL-89 URL: http://issues.hippo.nl/browse/PORTAL-89 Project: Hippo Portal Issue Type: Bug Components: hippo-portal Reporter: Bartosz Oudekerk Priority: Normal When building the portal, jcs.auxiliary.JCSDEFAULT.attributes.DiskPath in conf/hippo-portal.xml seems hardcoded to a value of 'C:\DOCUME~1\${LOGNAME}\LOCALS~1\Temp\' on windows, and '/tmp' on UNIX. At the very least, it should respect the environment variables TEMP (MS Windows) & TMP (MS Windows & UNIX) when building. It would even be better if these were taken from the applications environment each time it starts. If auto-detection at runtime is not an option, I feel they should be configurable at build time, with the defaults respecting the aforementioned variables. This would especially be nice, as it's currently common procedure to replace all configuration with each deploy, and the production environment will rarely be the same as the build environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Fri Nov 7 14:30:58 2008 From: helpdesk at onehippo.com (JIRA (Bartosz Oudekerk)) Date: Fri Nov 7 14:30:58 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-89) jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. In-Reply-To: <2017702.1226058178641.JavaMail.jira@hat01> Message-ID: <24634977.1226064658687.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42083 ] Bartosz Oudekerk commented on PORTAL-89: ---------------------------------------- The variable to be used on UNIX should of course be TMPDIR, not TMP > jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-89 > URL: http://issues.hippo.nl/browse/PORTAL-89 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal > Reporter: Bartosz Oudekerk > Priority: Normal > > When building the portal, jcs.auxiliary.JCSDEFAULT.attributes.DiskPath in conf/hippo-portal.xml seems hardcoded to a value of 'C:\DOCUME~1\${LOGNAME}\LOCALS~1\Temp\' on windows, and '/tmp' on UNIX. > At the very least, it should respect the environment variables TEMP (MS Windows) & TMP (MS Windows & UNIX) when building. > It would even be better if these were taken from the applications environment each time it starts. > If auto-detection at runtime is not an option, I feel they should be configurable at build time, with the defaults respecting the aforementioned variables. > This would especially be nice, as it's currently common procedure to replace all configuration with each deploy, and the production environment will rarely be the same as the build environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 14:14:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 14:14:58 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-90) Minor Demo Portal improvements Message-ID: <29643918.1226322898598.JavaMail.jira@hat01> Minor Demo Portal improvements ------------------------------ Key: PORTAL-90 URL: http://issues.hippo.nl/browse/PORTAL-90 Project: Hippo Portal Issue Type: Improvement Components: demo-pa Affects Versions: 1.10.00m01, 1.07.00 Reporter: Dennis Dam Assignee: Dennis Dam Priority: Low Fix For: 1.07.01, 1.10.00.m02 - create links using linkrewriter instead of manual url construction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 14:18:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 14:19:00 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-90) Minor Demo Portal improvements In-Reply-To: <29643918.1226322898598.JavaMail.jira@hat01> Message-ID: <20482209.1226323138655.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam updated PORTAL-90: ----------------------------- Description: - create links using linkrewriter instead of manual url construction - simplify breadcrumbs portlet: don't use breadcrumb actions (KISS) was:- create links using linkrewriter instead of manual url construction > Minor Demo Portal improvements > ------------------------------ > > Key: PORTAL-90 > URL: http://issues.hippo.nl/browse/PORTAL-90 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-pa > Affects Versions: 1.07.00, 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01, 1.10.00.m02 > > > - create links using linkrewriter instead of manual url construction > - simplify breadcrumbs portlet: don't use breadcrumb actions (KISS) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 14:40:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 14:40:57 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-90) Minor Demo Portal improvements In-Reply-To: <29643918.1226322898598.JavaMail.jira@hat01> Message-ID: <22212044.1226324458681.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam updated PORTAL-90: ----------------------------- Description: - create links using linkrewriter instead of manual url construction - simplify breadcrumbs portlet: don't use breadcrumb actions (KISS) - apply changes of PORTAL-17 and PORTAL-42 to 1.10.xx was: - create links using linkrewriter instead of manual url construction - simplify breadcrumbs portlet: don't use breadcrumb actions (KISS) Component/s: demo-portal > Minor Demo Portal improvements > ------------------------------ > > Key: PORTAL-90 > URL: http://issues.hippo.nl/browse/PORTAL-90 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-pa, demo-portal > Affects Versions: 1.07.00, 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01, 1.10.00.m02 > > > - create links using linkrewriter instead of manual url construction > - simplify breadcrumbs portlet: don't use breadcrumb actions (KISS) > - apply changes of PORTAL-17 and PORTAL-42 to 1.10.xx -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 14:57:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 14:57:58 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-85) Ability to override the mapping of portal url to corresponding repository source In-Reply-To: <20990675.1223463059193.JavaMail.jira@hat01> Message-ID: <11892319.1226325478746.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam updated PORTAL-85: ----------------------------- Affects Version/s: (was: 1.10.00.m02) Fix Version/s: 1.07.01 (was: 1.07.00) (was: 1.10.00.m02) Component/s: (was: hippo-portal-api) > Ability to override the mapping of portal url to corresponding repository source > -------------------------------------------------------------------------------- > > Key: PORTAL-85 > URL: http://issues.hippo.nl/browse/PORTAL-85 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Priority: Normal > Fix For: 1.07.01 > > > see the Mail from Michiel Trimpe on the hippo-portal-dev list, dated Oct. 7, 2008: > I've analyzed the problem a bit further (your solution doesn't work for us) and I've come to the conclusion that we basically need the mapping from a SiteMapItem to a source DocumentPath to be configurable. > At present there's some default logic for mapping a SiteMapItem to a DocumentPath source (adding the postfix and replacing ".html" with ".xml") and we need some extra logic there (if the resource is a collection and there is no postfix then find a document sibling with the same name). > Is there any way to customize that logic? > On a side note, after having implemented the Hippo Portal in our company for the past few weeks I find that the biggest problem I keep running into is the lack of extensibility / configurability, such as described above. It seems like there's been fairly little thought put into defining (and documenting) appropriate extension points and a mechanism to do so. > This problem could for example be resolved by moving CMSRequestContextImpl.getSrc(SiteMapItem, CMSPortalURL, boolean) to an interface CMSSourceResolver(SiteMapItem, CMSPortalURL, CMSService, boolean) and adding the CMSSourceResolver to CMSApplicationRegistryImpl. Another option would be to add a CMSRequestContextFactory which we can configure. > All in all it's been really nice to explore the Hippo Portal internals though; apart from the extensibility it's a really nicely architectured system. > - Michiel Trimpe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 14:57:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 14:57:59 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-84) Finalize release 1.07 In-Reply-To: <29876163.1222702838284.JavaMail.jira@hat01> Message-ID: <10528196.1226325478825.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-84. ------------------------------ Resolution: Fixed > Finalize release 1.07 > --------------------- > > Key: PORTAL-84 > URL: http://issues.hippo.nl/browse/PORTAL-84 > Project: Hippo Portal > Issue Type: Task > Components: demo-pa, demo-portal, demo-portal-installer, hippo-portal, hippo-portal-api, hippo-portal-docs, hippo-portal-j2, hippo-portal-maven-plugin, hippo-portal-pac > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > - set version number in trunk to 1.07.00 > - create installer for demo > - set the tag > - upload doc and artifacts to maven repository > - more? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 15:05:59 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 15:05:59 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-85) Ability to override the mapping of portal url to corresponding repository source In-Reply-To: <20990675.1223463059193.JavaMail.jira@hat01> Message-ID: <15045698.1226325959325.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-85. ------------------------------ Fix Version/s: 1.10.00.m02 Resolution: Fixed provided a workaround solution in the form of a utility class "CMSRequestContextWrapper". This class is available in hippo-portal-j2, and can be used as a basis to wrap the default generated CMSRequestContext with your extension points. > Ability to override the mapping of portal url to corresponding repository source > -------------------------------------------------------------------------------- > > Key: PORTAL-85 > URL: http://issues.hippo.nl/browse/PORTAL-85 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Priority: Normal > Fix For: 1.07.01, 1.10.00.m02 > > > see the Mail from Michiel Trimpe on the hippo-portal-dev list, dated Oct. 7, 2008: > I've analyzed the problem a bit further (your solution doesn't work for us) and I've come to the conclusion that we basically need the mapping from a SiteMapItem to a source DocumentPath to be configurable. > At present there's some default logic for mapping a SiteMapItem to a DocumentPath source (adding the postfix and replacing ".html" with ".xml") and we need some extra logic there (if the resource is a collection and there is no postfix then find a document sibling with the same name). > Is there any way to customize that logic? > On a side note, after having implemented the Hippo Portal in our company for the past few weeks I find that the biggest problem I keep running into is the lack of extensibility / configurability, such as described above. It seems like there's been fairly little thought put into defining (and documenting) appropriate extension points and a mechanism to do so. > This problem could for example be resolved by moving CMSRequestContextImpl.getSrc(SiteMapItem, CMSPortalURL, boolean) to an interface CMSSourceResolver(SiteMapItem, CMSPortalURL, CMSService, boolean) and adding the CMSSourceResolver to CMSApplicationRegistryImpl. Another option would be to add a CMSRequestContextFactory which we can configure. > All in all it's been really nice to explore the Hippo Portal internals though; apart from the extensibility it's a really nicely architectured system. > - Michiel Trimpe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 15:07:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 15:07:57 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-91) Resolve CMSSite before CMSRequestContext is resolved Message-ID: <2609176.1226326078689.JavaMail.jira@hat01> Resolve CMSSite before CMSRequestContext is resolved ---------------------------------------------------- Key: PORTAL-91 URL: http://issues.hippo.nl/browse/PORTAL-91 Project: Hippo Portal Issue Type: New Feature Components: hippo-portal, hippo-portal-api, hippo-portal-j2 Reporter: Dennis Dam Assignee: Dennis Dam Fix For: 1.07.01, 1.10.00.m02 Got a request where the CMSSite object needs to be resolved before the CMSRequestContext is resolved. The idea behind it is that the webdav service can be used to do a lookup in the repository, from which a redirect is calculated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 15:10:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 15:10:57 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-92) Simplify algorithm for resolving CMSRequestContext Message-ID: <4164290.1226326258598.JavaMail.jira@hat01> Simplify algorithm for resolving CMSRequestContext -------------------------------------------------- Key: PORTAL-92 URL: http://issues.hippo.nl/browse/PORTAL-92 Project: Hippo Portal Issue Type: Improvement Components: hippo-portal Reporter: Dennis Dam Assignee: Dennis Dam Priority: Normal Fix For: 1.07.01, 1.10.00.m02 The method resolve() in CMSApplicationRegistryImpl contains a lot of redundant code. Resolving this issue can lead to reducing the amount of code by more than 50%. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 15:14:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 15:14:58 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-86) Linkrewriter urls contain double / In-Reply-To: <24476742.1223635499069.JavaMail.jira@hat01> Message-ID: <22314549.1226326498682.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam reopened PORTAL-86: ------------------------------ sitepath + basepath should be empty instead of "/" to prevent double slashes > Linkrewriter urls contain double / > ---------------------------------- > > Key: PORTAL-86 > URL: http://issues.hippo.nl/browse/PORTAL-86 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Affects Versions: 1.07.01, 1.10.00.m02 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.01, 1.10.00.m02 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 15:27:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 15:27:59 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-86) Linkrewriter urls contain double / In-Reply-To: <24476742.1223635499069.JavaMail.jira@hat01> Message-ID: <10043223.1226327278635.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-86. ------------------------------ Resolution: Fixed > Linkrewriter urls contain double / > ---------------------------------- > > Key: PORTAL-86 > URL: http://issues.hippo.nl/browse/PORTAL-86 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Affects Versions: 1.07.01, 1.10.00.m02 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.01, 1.10.00.m02 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 10 15:31:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 10 15:31:58 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-91) Resolve CMSSite before CMSRequestContext is resolved In-Reply-To: <2609176.1226326078689.JavaMail.jira@hat01> Message-ID: <17872424.1226327518672.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-91. ------------------------------ Resolution: Fixed > Resolve CMSSite before CMSRequestContext is resolved > ---------------------------------------------------- > > Key: PORTAL-91 > URL: http://issues.hippo.nl/browse/PORTAL-91 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.01, 1.10.00.m02 > > > Got a request where the CMSSite object needs to be resolved before the CMSRequestContext is resolved. The idea behind it is that the webdav service can be used to do a lookup in the repository, from which a redirect is calculated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From dtaylor at onehippo.com Tue Nov 11 01:23:07 2008 From: dtaylor at onehippo.com (David Sean Taylor) Date: Tue Nov 11 01:23:15 2008 Subject: [Hippoportal-dev] can't build demo Message-ID: <07F7C011-FE2C-4BA1-B4B3-F5B3A7D61033@onehippo.com> I must have gone to the wrong documentation site. I checked out the demo-pa and demo-portal following the instructions here: http://www.hippoportal.org/setup/build-requirements.html Yet when I go to build I get: Attempting to download hippo-portal-api-1.07.01.jar. WARNING: Failed to download hippo-portal-api-1.07.01.jar. Attempting to download hippo-portal-1.07.01.war. WARNING: Failed to download hippo-portal-1.07.01.war. Attempting to download hippo-portal-j2-1.07.01.jar. WARNING: Failed to download hippo-portal-j2-1.07.01.jar. The build cannot continue because of the following unsatisfied dependencies: hippo-portal-api-1.07.01.jar hippo-portal-1.07.01.war hippo-portal-j2-1.07.01.jar Should I switch back to version .00.jar? or can someone upload the required jars to the repository Thanks, dtaylor@onehippo.com www.onehippo.com San Francisco - Hippo USA Inc. 101 H Street, Suite Q Petaluma CA 94952-3329 +1 (877) 41-HIPPO Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20081110/78d5b966/attachment.htm From a.douma at onehippo.com Tue Nov 11 08:38:33 2008 From: a.douma at onehippo.com (Ate Douma) Date: Tue Nov 11 08:38:37 2008 Subject: [Hippoportal-dev] can't build demo In-Reply-To: <07F7C011-FE2C-4BA1-B4B3-F5B3A7D61033@onehippo.com> References: <07F7C011-FE2C-4BA1-B4B3-F5B3A7D61033@onehippo.com> Message-ID: <49193679.3060801@onehippo.com> David, I think you just got in the middle of a new release process. Dennis bumped the trunk version from 1.07.00 to 1.07.01 only yesterday and at that version is planned to be released today. If you can wait until that release is finished (should be by the time you read this) the new 1.07.01 dependencies will be uploaded to the repository. Otherwise, you can switch from trunk to the 1.07.00 release tag: http://svn.hippocms.org/repos/hippo/hippo-portal/tags/Release-PORTAL-v1_07_00 Regards, Ate David Sean Taylor wrote: > I must have gone to the wrong documentation site. I checked out the > demo-pa and demo-portal following the instructions here: > > http://www.hippoportal.org/setup/build-requirements.html > > Yet when I go to build I get: > > Attempting to download hippo-portal-api-1.07.01.jar. > WARNING: Failed to download hippo-portal-api-1.07.01.jar. > Attempting to download hippo-portal-1.07.01.war. > WARNING: Failed to download hippo-portal-1.07.01.war. > Attempting to download hippo-portal-j2-1.07.01.jar. > WARNING: Failed to download hippo-portal-j2-1.07.01.jar. > The build cannot continue because of the following unsatisfied dependencies: > > hippo-portal-api-1.07.01.jar > hippo-portal-1.07.01.war > hippo-portal-j2-1.07.01.jar > > > Should I switch back to version .00.jar? or can someone upload the > required jars to the repository > > Thanks, > > dtaylor@onehippo.com www.onehippo.com > > San Francisco - Hippo USA Inc. 101 H Street, Suite Q Petaluma CA > 94952-3329 +1 (877) 41-HIPPO > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Hippoportal-dev mailing list > Hippoportal-dev@lists.hippo.nl > http://lists.hippo.nl/mailman/listinfo/hippoportal-dev -- a.douma@onehippo.com www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1(877) 41-HIPPO From helpdesk at onehippo.com Tue Nov 11 12:04:59 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Tue Nov 11 12:04:59 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-91) Resolve CMSSite before CMSRequestContext is resolved In-Reply-To: <2609176.1226326078689.JavaMail.jira@hat01> Message-ID: <7096896.1226401499095.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam reopened PORTAL-91: ------------------------------ minor change: only pass Jetspeed RequestContext to createPortalURL, to be independent of portalURL, and allow to override the method *before* the PortalURLValve > Resolve CMSSite before CMSRequestContext is resolved > ---------------------------------------------------- > > Key: PORTAL-91 > URL: http://issues.hippo.nl/browse/PORTAL-91 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.01, 1.10.00.m02 > > > Got a request where the CMSSite object needs to be resolved before the CMSRequestContext is resolved. The idea behind it is that the webdav service can be used to do a lookup in the repository, from which a redirect is calculated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 13:18:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Tue Nov 11 13:18:58 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-93) Delete log files after building portal with Maven 1 plugin Message-ID: <1146766.1226405938595.JavaMail.jira@hat01> Delete log files after building portal with Maven 1 plugin ---------------------------------------------------------- Key: PORTAL-93 URL: http://issues.hippo.nl/browse/PORTAL-93 Project: Hippo Portal Issue Type: Improvement Components: hippo-portal-maven-plugin Affects Versions: 1.07.00 Reporter: Dennis Dam Assignee: Dennis Dam Priority: Low Fix For: 1.07.01 If you execute maven hp:build-portal, several log files are written. These log files need to be deleted by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 13:26:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Tue Nov 11 13:27:00 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-93) Delete log files after building portal with Maven 1 plugin In-Reply-To: <1146766.1226405938595.JavaMail.jira@hat01> Message-ID: <18044611.1226406418670.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-93. ------------------------------ Resolution: Fixed The build property nl.hippo.portal.build.logging.enabled has the default value "false", which means the logging files created in the root of the portal are deleted after the following goals are executed: hp:deploy-portal hp:build-portal hp:init-portal-db hp:full-portal when the flag is set to "true", the log files will not be cleaned up. Which files are deleted is controlled by the Hippo Portal Maven plugin property nl.hippo.portal.build.logging.files which has a default value of velocity.log,velocity.log.1,apacheds.log > Delete log files after building portal with Maven 1 plugin > ---------------------------------------------------------- > > Key: PORTAL-93 > URL: http://issues.hippo.nl/browse/PORTAL-93 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-maven-plugin > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01 > > > If you execute maven hp:build-portal, several log files are written. These log files need to be deleted by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 13:26:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Tue Nov 11 13:27:01 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-93) Delete log files after building portal with Maven 1 plugin In-Reply-To: <1146766.1226405938595.JavaMail.jira@hat01> Message-ID: <20523258.1226406418694.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam reopened PORTAL-93: ------------------------------ argh.. forgot the final commit, reopening > Delete log files after building portal with Maven 1 plugin > ---------------------------------------------------------- > > Key: PORTAL-93 > URL: http://issues.hippo.nl/browse/PORTAL-93 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-maven-plugin > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01 > > > If you execute maven hp:build-portal, several log files are written. These log files need to be deleted by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 13:26:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Tue Nov 11 13:27:01 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-93) Delete log files after building portal with Maven 1 plugin In-Reply-To: <1146766.1226405938595.JavaMail.jira@hat01> Message-ID: <5858975.1226406418718.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-93. ------------------------------ Resolution: Fixed > Delete log files after building portal with Maven 1 plugin > ---------------------------------------------------------- > > Key: PORTAL-93 > URL: http://issues.hippo.nl/browse/PORTAL-93 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-maven-plugin > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01 > > > If you execute maven hp:build-portal, several log files are written. These log files need to be deleted by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 14:21:58 2008 From: helpdesk at onehippo.com (JIRA (Ate Douma)) Date: Tue Nov 11 14:21:59 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-89) jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. In-Reply-To: <2017702.1226058178641.JavaMail.jira@hat01> Message-ID: <15903247.1226409718657.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma reassigned PORTAL-89: ------------------------------- Assignee: Ate Douma > jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-89 > URL: http://issues.hippo.nl/browse/PORTAL-89 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal > Reporter: Bartosz Oudekerk > Assignee: Ate Douma > Priority: Normal > > When building the portal, jcs.auxiliary.JCSDEFAULT.attributes.DiskPath in conf/hippo-portal.xml seems hardcoded to a value of 'C:\DOCUME~1\${LOGNAME}\LOCALS~1\Temp\' on windows, and '/tmp' on UNIX. > At the very least, it should respect the environment variables TEMP (MS Windows) & TMP (MS Windows & UNIX) when building. > It would even be better if these were taken from the applications environment each time it starts. > If auto-detection at runtime is not an option, I feel they should be configurable at build time, with the defaults respecting the aforementioned variables. > This would especially be nice, as it's currently common procedure to replace all configuration with each deploy, and the production environment will rarely be the same as the build environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 14:23:58 2008 From: helpdesk at onehippo.com (JIRA (Ate Douma)) Date: Tue Nov 11 14:23:59 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-89) jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. In-Reply-To: <2017702.1226058178641.JavaMail.jira@hat01> Message-ID: <31862470.1226409838731.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42309 ] Ate Douma commented on PORTAL-89: --------------------------------- This variable is configured as ${java.io.tmpdir} in hippo-portal.xml which wasn't translated by the maven-1 build, but obviously now is when using maven-2. I'll investigate how to prevent translation of this variable with maven-2 so that it remains ${java.io.tmpdir} to be evaluated at runtime only. > jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-89 > URL: http://issues.hippo.nl/browse/PORTAL-89 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal > Affects Versions: 1.10.00.m02, 2.01.00m01 > Reporter: Bartosz Oudekerk > Assignee: Ate Douma > Priority: Normal > Fix For: 1.10.00.m02, 2.01.00m01 > > > When building the portal, jcs.auxiliary.JCSDEFAULT.attributes.DiskPath in conf/hippo-portal.xml seems hardcoded to a value of 'C:\DOCUME~1\${LOGNAME}\LOCALS~1\Temp\' on windows, and '/tmp' on UNIX. > At the very least, it should respect the environment variables TEMP (MS Windows) & TMP (MS Windows & UNIX) when building. > It would even be better if these were taken from the applications environment each time it starts. > If auto-detection at runtime is not an option, I feel they should be configurable at build time, with the defaults respecting the aforementioned variables. > This would especially be nice, as it's currently common procedure to replace all configuration with each deploy, and the production environment will rarely be the same as the build environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 14:23:58 2008 From: helpdesk at onehippo.com (JIRA (Ate Douma)) Date: Tue Nov 11 14:23:59 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-89) jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. In-Reply-To: <2017702.1226058178641.JavaMail.jira@hat01> Message-ID: <15335254.1226409838764.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-89: ---------------------------- Affects Version/s: 1.10.00.m02 2.01.00m01 Fix Version/s: 1.10.00.m02 2.01.00m01 > jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-89 > URL: http://issues.hippo.nl/browse/PORTAL-89 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal > Affects Versions: 1.10.00.m02, 2.01.00m01 > Reporter: Bartosz Oudekerk > Assignee: Ate Douma > Priority: Normal > Fix For: 1.10.00.m02, 2.01.00m01 > > > When building the portal, jcs.auxiliary.JCSDEFAULT.attributes.DiskPath in conf/hippo-portal.xml seems hardcoded to a value of 'C:\DOCUME~1\${LOGNAME}\LOCALS~1\Temp\' on windows, and '/tmp' on UNIX. > At the very least, it should respect the environment variables TEMP (MS Windows) & TMP (MS Windows & UNIX) when building. > It would even be better if these were taken from the applications environment each time it starts. > If auto-detection at runtime is not an option, I feel they should be configurable at build time, with the defaults respecting the aforementioned variables. > This would especially be nice, as it's currently common procedure to replace all configuration with each deploy, and the production environment will rarely be the same as the build environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 11 15:42:58 2008 From: helpdesk at onehippo.com (JIRA (Vivek Kumar)) Date: Tue Nov 11 15:42:58 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-89) jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. In-Reply-To: <2017702.1226058178641.JavaMail.jira@hat01> Message-ID: <15166368.1226414578721.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Kumar reassigned PORTAL-89: --------------------------------- Assignee: Vivek Kumar (was: Ate Douma) > jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-89 > URL: http://issues.hippo.nl/browse/PORTAL-89 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal > Affects Versions: 1.10.00.m02, 2.01.00m01 > Reporter: Bartosz Oudekerk > Assignee: Vivek Kumar > Priority: Normal > Fix For: 1.10.00.m02, 2.01.00m01 > > > When building the portal, jcs.auxiliary.JCSDEFAULT.attributes.DiskPath in conf/hippo-portal.xml seems hardcoded to a value of 'C:\DOCUME~1\${LOGNAME}\LOCALS~1\Temp\' on windows, and '/tmp' on UNIX. > At the very least, it should respect the environment variables TEMP (MS Windows) & TMP (MS Windows & UNIX) when building. > It would even be better if these were taken from the applications environment each time it starts. > If auto-detection at runtime is not an option, I feel they should be configurable at build time, with the defaults respecting the aforementioned variables. > This would especially be nice, as it's currently common procedure to replace all configuration with each deploy, and the production environment will rarely be the same as the build environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Wed Nov 12 10:08:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Wed Nov 12 10:08:59 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-93) Delete log files after building portal with Maven 1 plugin In-Reply-To: <1146766.1226405938595.JavaMail.jira@hat01> Message-ID: <26491356.1226480938675.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam reopened PORTAL-93: ------------------------------ delete log files dir after build > Delete log files after building portal with Maven 1 plugin > ---------------------------------------------------------- > > Key: PORTAL-93 > URL: http://issues.hippo.nl/browse/PORTAL-93 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-maven-plugin > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01 > > > If you execute maven hp:build-portal, several log files are written. These log files need to be deleted by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Wed Nov 12 13:44:58 2008 From: helpdesk at onehippo.com (JIRA (Vivek Kumar)) Date: Wed Nov 12 13:44:58 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-89) jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. In-Reply-To: <2017702.1226058178641.JavaMail.jira@hat01> Message-ID: <27660735.1226493898725.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Kumar closed PORTAL-89. ----------------------------- Resolution: Fixed Issued has been fixed, by changing in jetspeed-mvn-portal-pom.xml > jcs.auxiliary.JCSDEFAULT.attributes.DiskPath does not respect the TMP enviroment variable, and does not seem configurable at build time. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-89 > URL: http://issues.hippo.nl/browse/PORTAL-89 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal > Affects Versions: 1.10.00.m02, 2.01.00m01 > Reporter: Bartosz Oudekerk > Assignee: Vivek Kumar > Priority: Normal > Fix For: 1.10.00.m02, 2.01.00m01 > > > When building the portal, jcs.auxiliary.JCSDEFAULT.attributes.DiskPath in conf/hippo-portal.xml seems hardcoded to a value of 'C:\DOCUME~1\${LOGNAME}\LOCALS~1\Temp\' on windows, and '/tmp' on UNIX. > At the very least, it should respect the environment variables TEMP (MS Windows) & TMP (MS Windows & UNIX) when building. > It would even be better if these were taken from the applications environment each time it starts. > If auto-detection at runtime is not an option, I feel they should be configurable at build time, with the defaults respecting the aforementioned variables. > This would especially be nice, as it's currently common procedure to replace all configuration with each deploy, and the production environment will rarely be the same as the build environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 17 17:07:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 17 17:07:58 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-91) Resolve CMSSite before CMSRequestContext is resolved In-Reply-To: <2609176.1226326078689.JavaMail.jira@hat01> Message-ID: <33359244.1226938078691.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-91. ------------------------------ Resolution: Fixed > Resolve CMSSite before CMSRequestContext is resolved > ---------------------------------------------------- > > Key: PORTAL-91 > URL: http://issues.hippo.nl/browse/PORTAL-91 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.01, 1.10.00.m02 > > > Got a request where the CMSSite object needs to be resolved before the CMSRequestContext is resolved. The idea behind it is that the webdav service can be used to do a lookup in the repository, from which a redirect is calculated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 17 17:07:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 17 17:07:59 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-87) Update to latest stable version of hippo-repository-java-adapter In-Reply-To: <29183925.1224603239015.JavaMail.jira@hat01> Message-ID: <24003376.1226938078737.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam closed PORTAL-87. ---------------------------- Resolution: Fixed > Update to latest stable version of hippo-repository-java-adapter > ---------------------------------------------------------------- > > Key: PORTAL-87 > URL: http://issues.hippo.nl/browse/PORTAL-87 > Project: Hippo Portal > Issue Type: Task > Components: hippo-portal > Affects Versions: 1.07.01, 1.10.00.m02 > Reporter: Dennis Dam > Priority: Normal > Fix For: 1.07.01, 1.10.00.m02 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 17 17:07:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 17 17:07:59 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-92) Simplify algorithm for resolving CMSRequestContext In-Reply-To: <4164290.1226326258598.JavaMail.jira@hat01> Message-ID: <5176259.1226938078772.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-92. ------------------------------ Resolution: Fixed > Simplify algorithm for resolving CMSRequestContext > -------------------------------------------------- > > Key: PORTAL-92 > URL: http://issues.hippo.nl/browse/PORTAL-92 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.01, 1.10.00.m02 > > > The method resolve() in CMSApplicationRegistryImpl contains a lot of redundant code. Resolving this issue can lead to reducing the amount of code by more than 50%. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 17 17:11:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 17 17:11:57 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-90) Minor Demo Portal improvements In-Reply-To: <29643918.1226322898598.JavaMail.jira@hat01> Message-ID: <32775412.1226938318664.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-90. ------------------------------ Resolution: Fixed > Minor Demo Portal improvements > ------------------------------ > > Key: PORTAL-90 > URL: http://issues.hippo.nl/browse/PORTAL-90 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-pa, demo-portal > Affects Versions: 1.07.00, 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01, 1.10.00.m02 > > > - create links using linkrewriter instead of manual url construction > - simplify breadcrumbs portlet: don't use breadcrumb actions (KISS) > - apply changes of PORTAL-17 and PORTAL-42 to 1.10.xx -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Mon Nov 17 17:11:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Mon Nov 17 17:11:58 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-93) Delete log files after building portal with Maven 1 plugin In-Reply-To: <1146766.1226405938595.JavaMail.jira@hat01> Message-ID: <28419598.1226938318691.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-93. ------------------------------ Resolution: Fixed > Delete log files after building portal with Maven 1 plugin > ---------------------------------------------------------- > > Key: PORTAL-93 > URL: http://issues.hippo.nl/browse/PORTAL-93 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-maven-plugin > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Low > Fix For: 1.07.01 > > > If you execute maven hp:build-portal, several log files are written. These log files need to be deleted by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From d.dam at onehippo.com Mon Nov 17 18:16:11 2008 From: d.dam at onehippo.com (Dennis Dam) Date: Mon Nov 17 18:16:10 2008 Subject: [Hippoportal-dev] [ANNOUNCEMENT] Hippo Portal 1.07.00 released Message-ID: <4921A6DB.8000500@onehippo.com> Hippo is proud to announce the availability of the latest release of its Hippo Portal product, version 1.07.01. This new version provides mainly improvements, bugfixes and enhancements developed since the last release 1.07.00 (released September 19th, 2008), and is to a large extent based on the requests and feedback we got from our community and our partners. For this, we'll like to express our sincere thanks, and are looking forward to continued collaboration on further improving and expanding the usage of Hippo Portal. The new release artifacts are all available through our public Maven-1 repository at: http://repository.hippocms.org/maven/nl.hippo.portal/. The online project documentation is also provided through that location: http://repository.hippocms.org/maven/nl.hippo.portal/docs/hippo-portal-1.07.01/ Finally, the release notes highlighting the new features, improvements and bugs fixed can be found here: http://repository.hippocms.org/maven/nl.hippo.portal/docs/hippo-portal-1.07.01/release-notes.html General usage and getting started information is available at: http://www.hippoportal.org/ The Hippo Portal team -- Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1(877) 41-HIPPO _______________________________________________ Hippoportal-dev mailing list Hippoportal-dev@lists.hippo.nl http://lists.hippo.nl/mailman/listinfo/hippoportal-dev From d.dam at onehippo.com Mon Nov 17 18:17:59 2008 From: d.dam at onehippo.com (Dennis Dam) Date: Mon Nov 17 18:17:58 2008 Subject: [Hippoportal-dev] [ANNOUNCEMENT] Corrected: Hippo Portal 1.07.01 released In-Reply-To: <4921A6DB.8000500@onehippo.com> References: <4921A6DB.8000500@onehippo.com> Message-ID: <4921A747.4030407@onehippo.com> I was too fast with sending, the subject should contain the version number "1.07.01" instead of "1.07.00". regards, Dennis Dam Dennis Dam wrote: > Hippo is proud to announce the availability of the latest release of > its Hippo Portal product, version 1.07.01. > > This new version provides mainly improvements, bugfixes and > enhancements developed since the last release 1.07.00 (released > September 19th, 2008), > and is to a large extent based on the requests and feedback we got > from our community and our partners. > For this, we'll like to express our sincere thanks, and are looking > forward to continued collaboration on further improving > and expanding the usage of Hippo Portal. > > The new release artifacts are all available through our public Maven-1 > repository at: > http://repository.hippocms.org/maven/nl.hippo.portal/. > > The online project documentation is also provided through that location: > > > http://repository.hippocms.org/maven/nl.hippo.portal/docs/hippo-portal-1.07.01/ > > > Finally, the release notes highlighting the new features, improvements > and bugs fixed can be found here: > > > http://repository.hippocms.org/maven/nl.hippo.portal/docs/hippo-portal-1.07.01/release-notes.html > > > General usage and getting started information is available at: > > http://www.hippoportal.org/ > > > The Hippo Portal team > From helpdesk at onehippo.com Tue Nov 18 17:20:58 2008 From: helpdesk at onehippo.com (JIRA (Dennis Dam)) Date: Tue Nov 18 17:20:58 2008 Subject: [Hippoportal-dev] [JIRA] Work started: (PORTAL-29) Sitemap item authentication based on roles In-Reply-To: <28901921.1184680834000.JavaMail.jira@hat01> Message-ID: <21922611.1227025258624.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on PORTAL-29 started by Dennis Dam. > Sitemap item authentication based on roles > ------------------------------------------ > > Key: PORTAL-29 > URL: http://issues.hippo.nl/browse/PORTAL-29 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.10.00.m02 > > > In backend: > * assign roles on sitemap items (based on LDAP / Slide whatever) > > In Portal: > * current set of roles to check against needs to be "pluggable", e.g. "rolesContainer".hasRole(), default implemented using request.isUserInRole() > * prohobit access to forbidden urls > * filter sitemenu items -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Wed Nov 19 16:38:58 2008 From: helpdesk at onehippo.com (JIRA (Woonsan Ko)) Date: Wed Nov 19 16:39:07 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-94) An option for ignoring domain port to find cms site domain Message-ID: <6547182.1227109138696.JavaMail.jira@hat01> An option for ignoring domain port to find cms site domain ---------------------------------------------------------- Key: PORTAL-94 URL: http://issues.hippo.nl/browse/PORTAL-94 Project: Hippo Portal Issue Type: Improvement Components: hippo-portal Affects Versions: 1.10.00m01 Reporter: Woonsan Ko Assignee: Woonsan Ko Priority: Low Fix For: 1.10.00.m02 Currently, if web port changes from the port of a cms domain setting, no content gets available. If administrator synchronizes hippo-portal.properties with server.xml, the problem will be removed. However, in most cases, cms site domains can be separated by the domain names only. So, to have an option to ignore port number can reduce a tedious editing multiple files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Wed Nov 19 16:49:58 2008 From: helpdesk at onehippo.com (JIRA (Woonsan Ko)) Date: Wed Nov 19 16:50:01 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-94) An option for ignoring domain port to find cms site domain In-Reply-To: <6547182.1227109138696.JavaMail.jira@hat01> Message-ID: <9204224.1227109798767.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko resolved PORTAL-94. ------------------------------ Resolution: Fixed Fixed. > An option for ignoring domain port to find cms site domain > ---------------------------------------------------------- > > Key: PORTAL-94 > URL: http://issues.hippo.nl/browse/PORTAL-94 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Woonsan Ko > Assignee: Woonsan Ko > Priority: Low > Fix For: 1.10.00.m02 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Currently, if web port changes from the port of a cms domain setting, no content gets available. > If administrator synchronizes hippo-portal.properties with server.xml, the problem will be removed. > However, in most cases, cms site domains can be separated by the domain names only. So, to have an option to ignore port number can reduce a tedious editing multiple files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Thu Nov 20 09:38:58 2008 From: helpdesk at onehippo.com (JIRA (Woonsan Ko)) Date: Thu Nov 20 09:39:00 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-95) Repository-based menu needs to have an option to include the root node itself. Message-ID: <29966307.1227170338599.JavaMail.jira@hat01> Repository-based menu needs to have an option to include the root node itself. ------------------------------------------------------------------------------ Key: PORTAL-95 URL: http://issues.hippo.nl/browse/PORTAL-95 Project: Hippo Portal Issue Type: Improvement Components: hippo-portal Affects Versions: 1.10.00m01 Reporter: Woonsan Ko Assignee: Woonsan Ko Priority: Normal Fix For: 1.10.00.m02 By repository-based menu item, all sub nodes are included as site map items. It is useful to have an option to allow to include the root node (starting node) itself. Of course, the existing behavior should be kept by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Thu Nov 20 09:47:58 2008 From: helpdesk at onehippo.com (JIRA (Woonsan Ko)) Date: Thu Nov 20 09:47:59 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-95) Repository-based menu needs to have an option to include the root node itself. In-Reply-To: <29966307.1227170338599.JavaMail.jira@hat01> Message-ID: <28475114.1227170878642.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko resolved PORTAL-95. ------------------------------ Resolution: Fixed fixed. > Repository-based menu needs to have an option to include the root node itself. > ------------------------------------------------------------------------------ > > Key: PORTAL-95 > URL: http://issues.hippo.nl/browse/PORTAL-95 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Woonsan Ko > Assignee: Woonsan Ko > Priority: Normal > Fix For: 1.10.00.m02 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > By repository-based menu item, all sub nodes are included as site map items. > It is useful to have an option to allow to include the root node (starting node) itself. Of course, the existing behavior should be kept by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 25 10:33:59 2008 From: helpdesk at onehippo.com (JIRA (Woonsan Ko)) Date: Tue Nov 25 10:34:00 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-95) Repository-based menu needs to have an option to include the root node itself. In-Reply-To: <29966307.1227170338599.JavaMail.jira@hat01> Message-ID: <570257.1227605639474.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko reopened PORTAL-95: ------------------------------ When the "firstDocumentAsIndex" option is true, it is not checking if the first node is a collection or not. > Repository-based menu needs to have an option to include the root node itself. > ------------------------------------------------------------------------------ > > Key: PORTAL-95 > URL: http://issues.hippo.nl/browse/PORTAL-95 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Woonsan Ko > Assignee: Woonsan Ko > Priority: Normal > Fix For: 1.10.00.m02 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > By repository-based menu item, all sub nodes are included as site map items. > It is useful to have an option to allow to include the root node (starting node) itself. Of course, the existing behavior should be kept by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 25 10:33:59 2008 From: helpdesk at onehippo.com (JIRA (Woonsan Ko)) Date: Tue Nov 25 10:34:01 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-95) Repository-based menu needs to have an option to include the root node itself. In-Reply-To: <29966307.1227170338599.JavaMail.jira@hat01> Message-ID: <27173628.1227605639500.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko resolved PORTAL-95. ------------------------------ Resolution: Fixed fixed. > Repository-based menu needs to have an option to include the root node itself. > ------------------------------------------------------------------------------ > > Key: PORTAL-95 > URL: http://issues.hippo.nl/browse/PORTAL-95 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Woonsan Ko > Assignee: Woonsan Ko > Priority: Normal > Fix For: 1.10.00.m02 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > By repository-based menu item, all sub nodes are included as site map items. > It is useful to have an option to allow to include the root node (starting node) itself. Of course, the existing behavior should be kept by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at onehippo.com Tue Nov 25 15:51:58 2008 From: helpdesk at onehippo.com (JIRA (Woonsan Ko)) Date: Tue Nov 25 15:51:58 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-95) Repository-based menu needs to have an option to include the root node itself. In-Reply-To: <29966307.1227170338599.JavaMail.jira@hat01> Message-ID: <5119161.1227624718993.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woonsan Ko reopened PORTAL-95: ------------------------------ Sometimes, the first index document is not found. > Repository-based menu needs to have an option to include the root node itself. > ------------------------------------------------------------------------------ > > Key: PORTAL-95 > URL: http://issues.hippo.nl/browse/PORTAL-95 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Woonsan Ko > Assignee: Woonsan Ko > Priority: Normal > Fix For: 1.10.00.m02 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > By repository-based menu item, all sub nodes are included as site map items. > It is useful to have an option to allow to include the root node (starting node) itself. Of course, the existing behavior should be kept by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira