[jira] [Comment Edited] (CONNECTORS-1754) Converting release scripts to GitHub workflows
[ https://issues.apache.org/jira/browse/CONNECTORS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823638#comment-17823638 ] Piergiorgio Lucidi edited comment on CONNECTORS-1754 at 3/5/24 2:17 PM: A first workflow for creating a new release candidate is pushed here: [https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml] We need to debug it but I think that it could be something close to what we need: # Create the new branch # Update CHANGES.txt, build.xml and all the poms # Run the Ant build # Run the Maven build (if we want to push artifacts on public repos) # Check licenses using Apache RAT # Commit and push the new branch # Upload artifacts as GitHub release assets Any feedback? Thanks. was (Author: piergiorgioluc...@gmail.com): A first workflow for creating a new release candidate is pushed here: [https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml] We need to debug it but I think that it could be something close to what we need. Any feedback? > Converting release scripts to GitHub workflows > -- > > Key: CONNECTORS-1754 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1754 > Project: ManifoldCF > Issue Type: Task > Components: Build >Affects Versions: ManifoldCF 2.26 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Original Estimate: 120h > Remaining Estimate: 120h > > We currently have SVN in readonly mode, so we urgently need to rebuild from > scratch our release scripts as GitHub workflows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1754) Converting release scripts to GitHub workflows
[ https://issues.apache.org/jira/browse/CONNECTORS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823638#comment-17823638 ] Piergiorgio Lucidi commented on CONNECTORS-1754: A first workflow for creating a new release candidate is pushed here: [https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml] We need to debug it but I think that it could be something close to what we need. Any feedback? > Converting release scripts to GitHub workflows > -- > > Key: CONNECTORS-1754 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1754 > Project: ManifoldCF > Issue Type: Task > Components: Build >Affects Versions: ManifoldCF 2.26 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Original Estimate: 120h > Remaining Estimate: 120h > > We currently have SVN in readonly mode, so we urgently need to rebuild from > scratch our release scripts as GitHub workflows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1755) Copyright footer must be updated
Piergiorgio Lucidi created CONNECTORS-1755:
--
Summary: Copyright footer must be updated
Key: CONNECTORS-1755
URL: https://issues.apache.org/jira/browse/CONNECTORS-1755
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 2.26
Reporter: Piergiorgio Lucidi
Fix For: ManifoldCF next
The footer in the UI must be updated with the current year, now we have the
following:
{{Copyright© 2010-2020}}
And we should update it to:
{{Copyright© 2010-2024{*}{*}}}
The resource bundle is located here:
{{https://github.com/apache/manifoldcf/tree/trunk/framework/ui-core/src/main/native2ascii/org/apache/manifoldcf/ui/i18n}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1744) Migrate away from Travis-CI
[ https://issues.apache.org/jira/browse/CONNECTORS-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816556#comment-17816556 ] Piergiorgio Lucidi commented on CONNECTORS-1744: [~schuch] I think that we can close this ticket, what do you think? > Migrate away from Travis-CI > --- > > Key: CONNECTORS-1744 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1744 > Project: ManifoldCF > Issue Type: Task > Components: Build >Reporter: Markus Schuch >Priority: Major > Attachments: .travis.yml > > > On November 2nd, 2020, Travis-CI announced the end of unlimited support for > open source projects. > Infra is therefore moving our CI offerings away from Travis-CI in order to > keep our builds pipeline cost-effective > *Deadline: December 31st 2022* > Infrastructure is moving ASF projects away from using Travis-CI at the end of > 2022. > Please take a look at > https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1754) Converting release scripts to GitHub workflows
[ https://issues.apache.org/jira/browse/CONNECTORS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816554#comment-17816554 ] Piergiorgio Lucidi commented on CONNECTORS-1754: The License Check workflow is correctly working now: [https://github.com/apache/manifoldcf/blob/trunk/.github/workflows/license-check.yml] [https://github.com/apache/manifoldcf/actions/runs/7782541234] > Converting release scripts to GitHub workflows > -- > > Key: CONNECTORS-1754 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1754 > Project: ManifoldCF > Issue Type: Task > Components: Build >Affects Versions: ManifoldCF 2.26 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Original Estimate: 120h > Remaining Estimate: 120h > > We currently have SVN in readonly mode, so we urgently need to rebuild from > scratch our release scripts as GitHub workflows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1754) Converting release scripts to GitHub workflows
[
https://issues.apache.org/jira/browse/CONNECTORS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813581#comment-17813581
]
Piergiorgio Lucidi commented on CONNECTORS-1754:
It seems that we have some restrictions for GitHub actions, we can't use all
the GitHub actions publicly available. The current RAT License check workflow
that I'm configuring is returning the following error:
{noformat}
Error: .github#L1
cedx/setup-ant@v2 and s4u/setup-maven-action@1.11.0 are not allowed to be used
in apache/manifoldcf. Actions in this workflow must be: within a repository
owned by apache, created by GitHub, verified in the GitHub Marketplace, or
matching the following:
*/*@[a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9]+,
AdoptOpenJDK/install-jdk@*,
JamesIves/github-pages-deploy-action@5dc1d5a192aeb5ab5b7d5a77b7d36aea4a7f5c92,
TobKed/label-when-approved-action@*, actions-cool/issues-helper@*,
actions-rs/*, al-cheb/configure-pagefile-action@*,
amannn/action-semantic-pull-request@*, apache/*,
burrunan/gradle-cache-action@*, bytedeco/javacpp-presets/.github/actions/*,
chromaui/action@*, codecov/codecov-action@*, conda-incubator/setup-miniconda@*,
container-tools/kind-action@*, container-tools/microshift-action@*,
dawidd6/action-download-artifact@*, delaguardo/setup-graalvm@*,
docker://jekyll/jekyll:*, docker://pandoc/core:2.9,
eps1lon/actions-label-merge-conflict@*, gaurav-nelson/github-actio... {noformat}
I'm currently using cedx/setup-ant@v2 and s4u/setup-maven-action for using a
specific version of Ant and Maven. I'm investigating to found alternatives
officially supported by ASF.
> Converting release scripts to GitHub workflows
> --
>
> Key: CONNECTORS-1754
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1754
> Project: ManifoldCF
> Issue Type: Task
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> We currently have SVN in readonly mode, so we urgently need to rebuild from
> scratch our release scripts as GitHub workflows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1754) Converting release scripts to GitHub workflows
[
https://issues.apache.org/jira/browse/CONNECTORS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813581#comment-17813581
]
Piergiorgio Lucidi edited comment on CONNECTORS-1754 at 2/2/24 9:12 AM:
It seems that we have some restrictions for GitHub actions, we can't use all
the GitHub actions publicly available. The current RAT License check workflow
that I'm configuring is returning the following error:
{noformat}
Error: .github#L1
cedx/setup-ant@v2 and s4u/setup-maven-action@1.11.0 are not allowed to be used
in apache/manifoldcf. Actions in this workflow must be: within a repository
owned by apache, created by GitHub, verified in the GitHub Marketplace, or
matching the following:
*/*@[a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9]+,
AdoptOpenJDK/install-jdk@*,
JamesIves/github-pages-deploy-action@5dc1d5a192aeb5ab5b7d5a77b7d36aea4a7f5c92,
TobKed/label-when-approved-action@*, actions-cool/issues-helper@*,
actions-rs/*, al-cheb/configure-pagefile-action@*,
amannn/action-semantic-pull-request@*, apache/*,
burrunan/gradle-cache-action@*, bytedeco/javacpp-presets/.github/actions/*,
chromaui/action@*, codecov/codecov-action@*, conda-incubator/setup-miniconda@*,
container-tools/kind-action@*, container-tools/microshift-action@*,
dawidd6/action-download-artifact@*, delaguardo/setup-graalvm@*,
docker://jekyll/jekyll:*, docker://pandoc/core:2.9,
eps1lon/actions-label-merge-conflict@*, gaurav-nelson/github-actio... {noformat}
I'm currently using cedx/setup-ant@v2 and s4u/setup-maven-action for using a
specific version of Ant and Maven. I'm investigating to found alternatives
officially supported by ASF.
was (Author: piergiorgioluc...@gmail.com):
It seems that we have some restrictions for GitHub actions, we can't use all
the GitHub actions publicly available. The current RAT License check workflow
that I'm configuring is returning the following error:
{noformat}
Error: .github#L1
cedx/setup-ant@v2 and s4u/setup-maven-action@1.11.0 are not allowed to be used
in apache/manifoldcf. Actions in this workflow must be: within a repository
owned by apache, created by GitHub, verified in the GitHub Marketplace, or
matching the following:
*/*@[a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9]+,
AdoptOpenJDK/install-jdk@*,
JamesIves/github-pages-deploy-action@5dc1d5a192aeb5ab5b7d5a77b7d36aea4a7f5c92,
TobKed/label-when-approved-action@*, actions-cool/issues-helper@*,
actions-rs/*, al-cheb/configure-pagefile-action@*,
amannn/action-semantic-pull-request@*, apache/*,
burrunan/gradle-cache-action@*, bytedeco/javacpp-presets/.github/actions/*,
chromaui/action@*, codecov/codecov-action@*, conda-incubator/setup-miniconda@*,
container-tools/kind-action@*, container-tools/microshift-action@*,
dawidd6/action-download-artifact@*, delaguardo/setup-graalvm@*,
docker://jekyll/jekyll:*, docker://pandoc/core:2.9,
eps1lon/actions-label-merge-conflict@*, gaurav-nelson/github-actio... {noformat}
I'm currently using cedx/setup-ant@v2 and s4u/setup-maven-action for using a
specific version of Ant and Maven. I'm investigating to found alternatives
officially supported by ASF.
> Converting release scripts to GitHub workflows
> --
>
> Key: CONNECTORS-1754
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1754
> Project: ManifoldCF
> Issue Type: Task
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> We currently have SVN in readonly mode, so we urgently need to rebuild from
> scratch our release scripts as GitHub workflows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CONNECTORS-1754) Converting release scripts to GitHub workflows
Piergiorgio Lucidi created CONNECTORS-1754: -- Summary: Converting release scripts to GitHub workflows Key: CONNECTORS-1754 URL: https://issues.apache.org/jira/browse/CONNECTORS-1754 Project: ManifoldCF Issue Type: Task Components: Build Affects Versions: ManifoldCF 2.26 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF next We currently have SVN in readonly mode, so we urgently need to rebuild from scratch our release scripts as GitHub workflows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811896#comment-17811896 ] Piergiorgio Lucidi commented on CONNECTORS-1495: Michele Piazzolla is working on the new Pelican configuration: [https://github.com/vecio88/manifoldcf-site/tree/preview/pelican] > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CONNECTORS-1753) ant make-core-deps fails
[ https://issues.apache.org/jira/browse/CONNECTORS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-1753. Resolution: Fixed Applied fix taken from the GitHub pull request in r1915308. > ant make-core-deps fails > > > Key: CONNECTORS-1753 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1753 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 2.26 >Reporter: Guylaine Bassette >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > > Working on a new contribution I have noticed the make-core-deps failed on > downloading zip plugins. I have fixed this and everything is OK now. I have > prepared a PR: [Fix URLs for manifoldCF plugins downloads for > make-core-deps|https://github.com/apache/manifoldcf/pull/160] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1753) ant make-core-deps fails
[ https://issues.apache.org/jira/browse/CONNECTORS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808104#comment-17808104 ] Piergiorgio Lucidi edited comment on CONNECTORS-1753 at 1/18/24 9:21 AM: - Applied fix taken from the GitHub pull request in r1915308. Thank you so much [~guylaine.bassette] for your contribution. was (Author: piergiorgioluc...@gmail.com): Applied fix taken from the GitHub pull request in r1915308. > ant make-core-deps fails > > > Key: CONNECTORS-1753 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1753 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 2.26 >Reporter: Guylaine Bassette >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > > Working on a new contribution I have noticed the make-core-deps failed on > downloading zip plugins. I have fixed this and everything is OK now. I have > prepared a PR: [Fix URLs for manifoldCF plugins downloads for > make-core-deps|https://github.com/apache/manifoldcf/pull/160] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1753) ant make-core-deps fails
Piergiorgio Lucidi created CONNECTORS-1753: -- Summary: ant make-core-deps fails Key: CONNECTORS-1753 URL: https://issues.apache.org/jira/browse/CONNECTORS-1753 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 2.26 Reporter: Guylaine Bassette Assignee: Piergiorgio Lucidi Fix For: ManifoldCF next Working on a new contribution I have noticed the make-core-deps failed on downloading zip plugins. I have fixed this and everything is OK now. I have prepared a PR: [Fix URLs for manifoldCF plugins downloads for make-core-deps|https://github.com/apache/manifoldcf/pull/160] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1752) Solr 9 Ingester connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807237#comment-17807237 ] Guylaine Bassette commented on CONNECTORS-1752: --- I have created the [CONNECTOR-1752|https://github.com/guylaine-bassette/manifoldcf/tree/CONNECTORS-1752] in my Fork Project. The solution is ready to merge as soon as my [PR 160 - Fix URLs for manifoldCF plugins downloads for make-core-deps|https://github.com/apache/manifoldcf/pull/160] is applied. > Solr 9 Ingester connector > - > > Key: CONNECTORS-1752 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1752 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.26 >Reporter: Guylaine Bassette >Priority: Major > > The current Solr ingester connector fails to ingest Sorl 9 documents properly. > The current version of the ingester uses Sorlj 9, so it probably only needs a > few adjustments to get it working. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1752) Solr 9 Ingester connector
Guylaine Bassette created CONNECTORS-1752: - Summary: Solr 9 Ingester connector Key: CONNECTORS-1752 URL: https://issues.apache.org/jira/browse/CONNECTORS-1752 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 2.26 Reporter: Guylaine Bassette The current Solr ingester connector fails to ingest Sorl 9 documents properly. The current version of the ingester uses Sorlj 9, so it probably only needs a few adjustments to get it working. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1744) Migrate away from Travis-CI
[ https://issues.apache.org/jira/browse/CONNECTORS-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806914#comment-17806914 ] Piergiorgio Lucidi commented on CONNECTORS-1744: Ticket created: https://issues.apache.org/jira/browse/INFRA-25386 > Migrate away from Travis-CI > --- > > Key: CONNECTORS-1744 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1744 > Project: ManifoldCF > Issue Type: Task > Components: Build >Reporter: Markus Schuch >Priority: Major > Attachments: .travis.yml > > > On November 2nd, 2020, Travis-CI announced the end of unlimited support for > open source projects. > Infra is therefore moving our CI offerings away from Travis-CI in order to > keep our builds pipeline cost-effective > *Deadline: December 31st 2022* > Infrastructure is moving ASF projects away from using Travis-CI at the end of > 2022. > Please take a look at > https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1744) Migrate away from Travis-CI
[ https://issues.apache.org/jira/browse/CONNECTORS-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806911#comment-17806911 ] Piergiorgio Lucidi commented on CONNECTORS-1744: I'm going to create a ticket to INFRA in order to switch to GitHub for commits and actions. We have to avoid to release the software using manual steps and specific operating systems. > Migrate away from Travis-CI > --- > > Key: CONNECTORS-1744 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1744 > Project: ManifoldCF > Issue Type: Task > Components: Build >Reporter: Markus Schuch >Priority: Major > Attachments: .travis.yml > > > On November 2nd, 2020, Travis-CI announced the end of unlimited support for > open source projects. > Infra is therefore moving our CI offerings away from Travis-CI in order to > keep our builds pipeline cost-effective > *Deadline: December 31st 2022* > Infrastructure is moving ASF projects away from using Travis-CI at the end of > 2022. > Please take a look at > https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805440#comment-17805440 ] Piergiorgio Lucidi commented on CONNECTORS-1495: The new website that is using Pelican is available here: [https://manifoldcf-pelican.staged.apache.org/] The website is the result of what Sebb created for us in the pelican branches included in the manifold-site project on GitHub. Unfortunately we should invest some time to adapt a new layout and reorganize all the contents. I'll try to understand if the old layout built using Jekyll can be used. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799595#comment-17799595 ] Piergiorgio Lucidi commented on CONNECTORS-1495: ??Have you thought about licensing of those materials? This would be the time...?? [~kwri...@metacarta.com] do you mean building an official Docker Image of ManifoldCF? > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799590#comment-17799590 ] Piergiorgio Lucidi commented on CONNECTORS-1495: I have just migrated the ManifoldCF SDK project into ASF GitHub here: [https://github.com/apache/manifoldcf-sdk] > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CONNECTORS-1706) ManifoldCF SDK
[ https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-1706. Resolution: Fixed > ManifoldCF SDK > -- > > Key: CONNECTORS-1706 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1706 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Original Estimate: 168h > Remaining Estimate: 168h > > I'm working on a ManifoldCF SDK, a Maven project with Docker integration that > we could also use for testing purposes. > Below you can find the current status of this development, totally separated > from the ManifoldCF source code because it is a totally independent project. > In my mind I would like to have something like the following: # Creating a > new Docker image with OpenJDK 11, Ant and Maven installed - DONE > # Downloading ManifoldCF source code (MCF version is an argument) - DONE > # Running the Docker container for installing all the Maven dependencies: > ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - > DONE > # Storing the Maven Repo and the installation in two separated Docker > Volumes - DONE > # Running the Docker container for executing tests: ant test - DONE (I have > issues with Elasticsearch at the moment for this) > # Copy the overall Maven Repo locally on the host in order to have all the > Maven dependencies available the MCF SDK classpath - DONE > # Compiling a mcf-extensions-jar module in order to compile new connectors > or extensions that developers want to implement (DONE) > # Overlaying the ManifoldCF Docker image with extensions compiled with the > SDK (DONE) > # Running the final container with extensions (DONE) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1706) ManifoldCF SDK
[ https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799589#comment-17799589 ] Piergiorgio Lucidi commented on CONNECTORS-1706: Now we have ManifoldCF SDK 0.0.4 finally published on the ASF Github here: [https://github.com/apache/manifoldcf-sdk] > ManifoldCF SDK > -- > > Key: CONNECTORS-1706 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1706 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Original Estimate: 168h > Remaining Estimate: 168h > > I'm working on a ManifoldCF SDK, a Maven project with Docker integration that > we could also use for testing purposes. > Below you can find the current status of this development, totally separated > from the ManifoldCF source code because it is a totally independent project. > In my mind I would like to have something like the following: # Creating a > new Docker image with OpenJDK 11, Ant and Maven installed - DONE > # Downloading ManifoldCF source code (MCF version is an argument) - DONE > # Running the Docker container for installing all the Maven dependencies: > ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - > DONE > # Storing the Maven Repo and the installation in two separated Docker > Volumes - DONE > # Running the Docker container for executing tests: ant test - DONE (I have > issues with Elasticsearch at the moment for this) > # Copy the overall Maven Repo locally on the host in order to have all the > Maven dependencies available the MCF SDK classpath - DONE > # Compiling a mcf-extensions-jar module in order to compile new connectors > or extensions that developers want to implement (DONE) > # Overlaying the ManifoldCF Docker image with extensions compiled with the > SDK (DONE) > # Running the final container with extensions (DONE) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1706) ManifoldCF SDK
[ https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi updated CONNECTORS-1706: --- Fix Version/s: ManifoldCF next > ManifoldCF SDK > -- > > Key: CONNECTORS-1706 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1706 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Original Estimate: 168h > Remaining Estimate: 168h > > I'm working on a ManifoldCF SDK, a Maven project with Docker integration that > we could also use for testing purposes. > Below you can find the current status of this development, totally separated > from the ManifoldCF source code because it is a totally independent project. > In my mind I would like to have something like the following: # Creating a > new Docker image with OpenJDK 11, Ant and Maven installed - DONE > # Downloading ManifoldCF source code (MCF version is an argument) - DONE > # Running the Docker container for installing all the Maven dependencies: > ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - > DONE > # Storing the Maven Repo and the installation in two separated Docker > Volumes - DONE > # Running the Docker container for executing tests: ant test - DONE (I have > issues with Elasticsearch at the moment for this) > # Copy the overall Maven Repo locally on the host in order to have all the > Maven dependencies available the MCF SDK classpath - DONE > # Compiling a mcf-extensions-jar module in order to compile new connectors > or extensions that developers want to implement (DONE) > # Overlaying the ManifoldCF Docker image with extensions compiled with the > SDK (DONE) > # Running the final container with extensions (DONE) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798641#comment-17798641 ] Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/19/23 3:57 PM: -- ManifoldCF SDK 0.0.4 is released and available here (actually on my github account): [https://github.com/OpenPj/manifoldcf-sdk/releases/tag/v0.0.4] I'm going to create a new GitHub project in ASF for hosting this project. I have also added Windows .bat scripts but it would be great if someone can spend some time testing them :P README available here: https://github.com/OpenPj/manifoldcf-sdk was (Author: piergiorgioluc...@gmail.com): ManifoldCF SDK 0.0.4 is released and available here (actually on my github account): [https://github.com/OpenPj/manifoldcf-sdk/releases/tag/v0.0.4] I'm going to create a new GitHub project in ASF for hosting this project. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798641#comment-17798641 ] Piergiorgio Lucidi commented on CONNECTORS-1495: ManifoldCF SDK 0.0.4 is released and available here (actually on my github account): [https://github.com/OpenPj/manifoldcf-sdk/releases/tag/v0.0.4] I'm going to create a new GitHub project in ASF for hosting this project. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798551#comment-17798551 ] Karl Wright commented on CONNECTORS-1495: - Nice work!! That was fast, and I agree with putting all the materials in the repo for it. Have you thought about licensing of those materials? This would be the time... > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798539#comment-17798539 ] Piergiorgio Lucidi commented on CONNECTORS-1495: The website is now online with all the contents correctly published. I'm going to move the manifoldcf-sdk project from my own repo to the Apache GitHub organization, this in order to configure a GitHub workflow that can execute the build of the website just pressing a button. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798513#comment-17798513
]
Piergiorgio Lucidi commented on CONNECTORS-1495:
Solved!
Ok it seems that now I can regenerate the website content using ManifoldCF SDK.
I'm going to update the website and then I'll publish a new version of the SDK
supporting the site contents generation.
Here the result of the build process inside the Docker container:
{code:java}
[exec] Total time: 0 minutes 2 seconds, Site size: 756,544 Site pages: 41
[exec]
[exec] Copying broken links file to site root.
[exec]
[exec] Copying 1 file to /usr/src/manifoldcf-site/build/site
[exec]
[exec] -
[exec] Static site was successfully generated at:
[exec] /usr/src/manifoldcf-site/build/site
[exec] --
[exec]
[exec]
[exec] BUILD SUCCESSFUL
[exec] Total time: 6 seconds {code}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17797940#comment-17797940
]
Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/17/23 3:59 PM:
--
Here I have something working as a preliminary environment for building the
website using Docker:
{code:java}
FROM alpine:3.15.11
ARG ANT_VERSION=1.9.16
RUN apk update \
&& apk upgrade \
&& apk --update add openjdk7 \
&& apk --update add subversion
#Installing Apache Ant 1.9.x
RUN mkdir -p /opt/ant/ \
&& wget
http://archive.apache.org/dist/ant/binaries/apache-ant-${ANT_VERSION}-bin.tar.gz
-P /opt/ant \
&& tar -xvzf /opt/ant/apache-ant-${ANT_VERSION}-bin.tar.gz -C /opt/ant/ \
&& rm -f /opt/ant/apache-ant-${ANT_VERSION}-bin.tar.gz
ENV ANT_HOME=/opt/ant/apache-ant-${ANT_VERSION}ENV ANT_OPTS="-Xms256M -Xmx512M"
ENV PATH="${PATH}:${HOME}/bin:${ANT_HOME}/bin"
RUN apk add --no-cache python2 && \
python -m ensurepip && \
rm -r /usr/lib/python*/ensurepip && \
pip install --upgrade pip setuptools && \
rm -r /root/.cache{code}
Trying to use the container built with the image above, I have the following
results:
{code:java}
/ # ant -version
Apache Ant(TM) version 1.9.16 compiled on July 10 2021
/ # java -version
java version "1.7.0_311"
OpenJDK Runtime Environment (IcedTea 2.6.27) (Alpine 7.311.2.6.27-r1)
OpenJDK 64-Bit Server VM (build 24.311-b01, mixed mode)
/ # python2
Python 2.7.18 (default, Oct 16 2021, 08:19:50)
[GCC 10.3.1 20210921] on linux2 {code}
I think that this can be a good start for managing the generation of the site
contents.
I'm continuing investigating...
was (Author: piergiorgioluc...@gmail.com):
Here I have something working as a preliminary environment for building the
website using Docker:
{code:java}
FROM alpine:3.15.11
ARG ANT_VERSION=1.9.16
RUN apk update \
&& apk upgrade \
&& apk --update add openjdk7 \
&& apk --update add subversion
#Installing Apache Ant 1.9.x
RUN mkdir -p /opt/ant/ \
&& wget
http://archive.apache.org/dist/ant/binaries/apache-ant-${ANT_VERSION}-bin.tar.gz
-P /opt/ant \
&& tar -xvzf /opt/ant/apache-ant-${ANT_VERSION}-bin.tar.gz -C /opt/ant/ \
&& rm -f /opt/ant/apache-ant-${ANT_VERSION}-bin.tar.gz
ENV ANT_HOME=/opt/ant/apache-ant-${ANT_VERSION}ENV ANT_OPTS="-Xms256M -Xmx512M"
ENV PATH="${PATH}:${HOME}/bin:${ANT_HOME}/bin"
RUN apk add --no-cache python2 && \
python -m ensurepip && \
rm -r /usr/lib/python*/ensurepip && \
pip install --upgrade pip setuptools && \
rm -r /root/.cache{code}
Trying to use the container built with the image above, I have the following
results:
{code:java}
/ # ant -version
Apache Ant(TM) version 1.9.16 compiled on July 10 2021
/ # java -version
java version "1.7.0_311"
OpenJDK Runtime Environment (IcedTea 2.6.27) (Alpine 7.311.2.6.27-r1)
OpenJDK 64-Bit Server VM (build 24.311-b01, mixed mode)
/ # python2
Python 2.7.18 (default, Oct 16 2021, 08:19:50)
[GCC 10.3.1 20210921] on linux2 {code}
I think that this can be a good start for managing the generation of the site
contents.
I'm continuing investigating...
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17797940#comment-17797940
]
Piergiorgio Lucidi commented on CONNECTORS-1495:
Here I have something working as a preliminary environment for building the
website using Docker:
{code:java}
FROM alpine:3.15.11
ARG ANT_VERSION=1.9.16
RUN apk update \
&& apk upgrade \
&& apk --update add openjdk7 \
&& apk --update add subversion
#Installing Apache Ant 1.9.x
RUN mkdir -p /opt/ant/ \
&& wget
http://archive.apache.org/dist/ant/binaries/apache-ant-${ANT_VERSION}-bin.tar.gz
-P /opt/ant \
&& tar -xvzf /opt/ant/apache-ant-${ANT_VERSION}-bin.tar.gz -C /opt/ant/ \
&& rm -f /opt/ant/apache-ant-${ANT_VERSION}-bin.tar.gz
ENV ANT_HOME=/opt/ant/apache-ant-${ANT_VERSION}ENV ANT_OPTS="-Xms256M -Xmx512M"
ENV PATH="${PATH}:${HOME}/bin:${ANT_HOME}/bin"
RUN apk add --no-cache python2 && \
python -m ensurepip && \
rm -r /usr/lib/python*/ensurepip && \
pip install --upgrade pip setuptools && \
rm -r /root/.cache{code}
Trying to use the container built with the image above, I have the following
results:
{code:java}
/ # ant -version
Apache Ant(TM) version 1.9.16 compiled on July 10 2021
/ # java -version
java version "1.7.0_311"
OpenJDK Runtime Environment (IcedTea 2.6.27) (Alpine 7.311.2.6.27-r1)
OpenJDK 64-Bit Server VM (build 24.311-b01, mixed mode)
/ # python2
Python 2.7.18 (default, Oct 16 2021, 08:19:50)
[GCC 10.3.1 20210921] on linux2 {code}
I think that this can be a good start for managing the generation of the site
contents.
I'm continuing investigating...
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17797507#comment-17797507 ] Piergiorgio Lucidi commented on CONNECTORS-1495: In a few days, I'll try to use the ManifoldCF SDK to create a container with OpenJDK 1.5 in order to build correctly the site with Forrest. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796773#comment-17796773 ] Piergiorgio Lucidi commented on CONNECTORS-1495: The current production website is managed inside the asf-site branch: [https://github.com/apache/manifoldcf-site/tree/asf-site] The generated staged website should be hosted in the asf-staging branch automatically generated by the build process if everything is correctly generated. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796773#comment-17796773 ] Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 2:34 PM: -- The current production website is managed inside the asf-site branch: [https://github.com/apache/manifoldcf-site/tree/asf-site] The staged website should be hosted in the asf-staging branch created by the build process if everything is correctly generated. was (Author: piergiorgioluc...@gmail.com): The current production website is managed inside the asf-site branch: [https://github.com/apache/manifoldcf-site/tree/asf-site] The generated staged website should be hosted in the asf-staging branch automatically generated by the build process if everything is correctly generated. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796762#comment-17796762
]
Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 2:31 PM:
--
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
I have restored a partial website dropping the generated content in the
asf-site branch of the manifoldcf-site GitHub project. Unfortunately I had the
following error that it doesn't allow me to generate all the pages:
{code:java}
Finished copying the non-generated resources.
[exec] Now Cocoon will generate the rest.
[exec]
[exec]
[exec] Static site will be generated at:
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/site
[exec]
[exec] Cocoon will report the status of each document:
[exec] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
[exec]
[exec] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[exec]
-Djava.endorsed.dirs=/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/lib/endorsed:${java.endorsed.dirs}
is not supported. Endorsed standards and standalone APIs
[exec] in modular form will be supported via the concept of upgradeable
modules.
[exec] Error: Could not create the Java Virtual Machine.
[exec] Error: A fatal exception has occurred. Program will exit.
[exec]
[exec] Copying broken links file to site root.
[exec]
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 secondsBUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1{code}
was (Author: piergiorgioluc...@gmail.com):
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
I have restored a partial website due to the following error:
{code:java}
Finished copying the non-generated resources.
[exec] Now Cocoon will generate the rest.
[exec]
[exec]
[exec] Static site will be generated at:
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/site
[exec]
[exec] Cocoon will report the status of each document:
[exec] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
[exec]
[exec] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[exec]
-Djava.endorsed.dirs=/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/lib/endorsed:${java.endorsed.dirs}
is not supported. Endorsed standards and standalone APIs
[exec] in modular form will be supported via the concept of upgradeable
modules.
[exec] Error: Could not create the Java Virtual Machine.
[exec] Error: A fatal exception has occurred. Program will exit.
[exec]
[exec] Copying broken links file to site root.
[exec]
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 secondsBUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1{code}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: M
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796762#comment-17796762
]
Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 2:30 PM:
--
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
I have restored a partial website due to the following error:
{code:java}
Finished copying the non-generated resources.
[exec] Now Cocoon will generate the rest.
[exec]
[exec]
[exec] Static site will be generated at:
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/site
[exec]
[exec] Cocoon will report the status of each document:
[exec] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
[exec]
[exec] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[exec]
-Djava.endorsed.dirs=/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/lib/endorsed:${java.endorsed.dirs}
is not supported. Endorsed standards and standalone APIs
[exec] in modular form will be supported via the concept of upgradeable
modules.
[exec] Error: Could not create the Java Virtual Machine.
[exec] Error: A fatal exception has occurred. Program will exit.
[exec]
[exec] Copying broken links file to site root.
[exec]
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 secondsBUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1{code}
was (Author: piergiorgioluc...@gmail.com):
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
but now I have the following:
{code:java}
Finished copying the non-generated resources.
[exec] Now Cocoon will generate the rest.
[exec]
[exec]
[exec] Static site will be generated at:
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/site
[exec]
[exec] Cocoon will report the status of each document:
[exec] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
[exec]
[exec] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[exec]
-Djava.endorsed.dirs=/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/lib/endorsed:${java.endorsed.dirs}
is not supported. Endorsed standards and standalone APIs
[exec] in modular form will be supported via the concept of upgradeable
modules.
[exec] Error: Could not create the Java Virtual Machine.
[exec] Error: A fatal exception has occurred. Program will exit.
[exec]
[exec] Copying broken links file to site root.
[exec]
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 secondsBUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1{code}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
>
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796762#comment-17796762
]
Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 2:05 PM:
--
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
but now I have the following:
{code:java}
Finished copying the non-generated resources.
[exec] Now Cocoon will generate the rest.
[exec]
[exec]
[exec] Static site will be generated at:
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/site
[exec]
[exec] Cocoon will report the status of each document:
[exec] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
[exec]
[exec] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[exec]
-Djava.endorsed.dirs=/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/lib/endorsed:${java.endorsed.dirs}
is not supported. Endorsed standards and standalone APIs
[exec] in modular form will be supported via the concept of upgradeable
modules.
[exec] Error: Could not create the Java Virtual Machine.
[exec] Error: A fatal exception has occurred. Program will exit.
[exec]
[exec] Copying broken links file to site root.
[exec]
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 secondsBUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1{code}
was (Author: piergiorgioluc...@gmail.com):
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
but now I have the following:
{code:java}
Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 seconds
BUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1Total time: 1 minute 14 seconds{code}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796762#comment-17796762
]
Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 2:04 PM:
--
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
but now I have the following:
{code:java}
Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 seconds
BUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1Total time: 1 minute 14 seconds{code}
was (Author: piergiorgioluc...@gmail.com):
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
but now I have the following:
{code:java}
Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 secondsBUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1Total time: 1 minute 14 seconds{code}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796762#comment-17796762
]
Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 2:04 PM:
--
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
but now I have the following:
{code:java}
Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene/images
not found.
[exec] Warning:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/webapp/skins/lucene
not found.
[exec] Java Result: 1
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/tmp/forrest/main/targets/site.xml:180:
Warning: Could not find file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/tmp/brokenlinks.xml
to copy.
[exec]
[exec] Total time: 0 secondsBUILD FAILED
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build.xml:473:
exec returned: 1Total time: 1 minute 14 seconds{code}
was (Author: piergiorgioluc...@gmail.com):
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796762#comment-17796762
]
Piergiorgio Lucidi commented on CONNECTORS-1495:
I'm using OpenJDK 1.8 so this means that I can use JDK 1.7, updating the Java
version in the build/forrest/main/build.xml solved this problem:
{{}}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796755#comment-17796755 ] Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 1:54 PM: -- Considering that I have an Apple Silicon probably I can't use JDK 1.5... I'm trying to understand how to solve... was (Author: piergiorgioluc...@gmail.com): Considering that I have an Apple Silicon probably I can't use JDK 1.5... > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796755#comment-17796755 ] Piergiorgio Lucidi commented on CONNECTORS-1495: Considering that I have an Apple Silicon probably I can't use JDK 1.5... > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796746#comment-17796746
]
Piergiorgio Lucidi commented on CONNECTORS-1495:
Pelican is not working properly with the new markdown files.
I'm trying to regenerate all the website but the build procedure is returning
the following error about forrest:
{code:java}
build-forrest:
[exec] Using classpath:
../lib/endorsed/jakarta-bcel-20040329.jar:../lib/endorsed/jakarta-regexp-1.5.jar:../lib/endorsed/xalan-2.7.1.jar:../lib/endorsed/xercesImpl-2.9.1.jar:../lib/endorsed/xml-apis-1.3.04.jar
[exec] Buildfile: build.xml
[exec]
[exec] init:
[exec]
[exec] --
[exec]
[exec] Using Apache Ant version 1.7.1 compiled on September 26 2008
[exec] Build file
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/forrest/main/build.xml
[exec] Use 'build.[sh|bat] -projecthelp' to see other options.
[exec] Build system home
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/forrest/tools/ant
[exec] Build number 2
[exec] Project Name Forrest build file
[exec] Java Version 1.6
[exec] Timestamp 202312141445
[exec] This is: apache-forrest 0.9
[exec]
[exec] --
[exec]
[exec]
[exec] compile:
[exec] Compiling 33 source files to
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/forrest/build/classes
[exec] error: Source option 5 is no longer supported. Use 7 or later.
[exec] error: Target option 5 is no longer supported. Use 7 or later.
[exec]
[exec] BUILD FAILED
[exec]
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/site-trunk/build/forrest/main/build.xml:522:
Compile failed; see the compiler error output for details.
[exec]
[exec] Total time: 0 seconds{code}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796720#comment-17796720 ] Karl Wright commented on CONNECTORS-1495: - Hi [~piergiorgioluc...@gmail.com], I see no actual HTML pages for your new site. What am I missing? To publish this, all that is needed is to: (1) svn remove all directories and files under the svn pub/sub URL (2) Copy the new site in (3) Use svn add * to add all the directories and files (4) svn commit publishes it. The svn url is URL: https://svn.apache.org/repos/asf/manifoldcf/site/publish > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796715#comment-17796715 ] Piergiorgio Lucidi commented on CONNECTORS-1495: Unfortunately our website is broken now, I'm so sorry for that. [~kwri...@metacarta.com] I think that currently I need your help to republish our website. What we could do is to generate all the content in the old way and publishing in the new GitHub project until the Pelican procedure will work on staging. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796616#comment-17796616 ] Piergiorgio Lucidi edited comment on CONNECTORS-1495 at 12/14/23 9:07 AM: -- A new GitHub repository for the website is available here: [https://github.com/apache/manifoldcf-site] In this new repo you will also find the site contents correctly converted in markdown format: [https://github.com/apache/manifoldcf-site/tree/main/content/pages] Our new staged website is available here: [https://manifoldcf.staged.apache.org/] I'm currently trying to figure out how to configure ASF Pelican in order to correctly render our pages. I raised a new ticket to INFRA to understand what is missing: https://issues.apache.org/jira/browse/INFRA-25278 was (Author: piergiorgioluc...@gmail.com): A new GitHub repository for the website is available here: [https://github.com/apache/manifoldcf-site] In this new repo you will also find the site contents correctly converted in markdown format: [https://github.com/apache/manifoldcf-site/tree/main/content/pages] I'm currently trying to figure out how to configure ASF Pelican in order to correctly render our pages. Our new staged website is available here: [https://manifoldcf.staged.apache.org/] > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796616#comment-17796616 ] Piergiorgio Lucidi commented on CONNECTORS-1495: A new GitHub repository for the website is available here: [https://github.com/apache/manifoldcf-site] In this new repo you will also find the site contents correctly converted in markdown format: [https://github.com/apache/manifoldcf-site/tree/main/content/pages] I'm currently trying to figure out how to configure ASF Pelican in order to correctly render our pages. Our new staged website is available here: [https://manifoldcf.staged.apache.org/] > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png, > PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status - > 20180510.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1492) Add support for Docker
[ https://issues.apache.org/jira/browse/CONNECTORS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792393#comment-17792393 ] Piergiorgio Lucidi commented on CONNECTORS-1492: A first goal is accomplished because now developers can use the ManifoldCF SDK to extend the platform with new connectors and extensions. Anyway I think that we should definitely distribute a Docker image without including the connectors that are not compliant with the Apache License. I'm thinking of all the connectors requiring additional libraries in the connectors-lib-proprietary, in this case we could remove these JARs from the Docker distribution. It would be interesting to understand what we could distribute inside a Docker image and I think that the effort for creating a Docker image it will be not so heavy. > Add support for Docker > -- > > Key: CONNECTORS-1492 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1492 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Labels: devops, docker > Original Estimate: 240h > Remaining Estimate: 240h > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > To discuss this or other ideas with your potential mentor from the Apache > ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, > including "[GSOC]" in the subject. You may also comment on this Jira issue if > you have created an account. > We would like to adopt Docker to provide ready to use images with > preconfigured architecture stack for ManifoldCF. This will include ManifoldCF > itself but also the related database that can be MySQL, PostgreSQL and so on. > This will help developers to work and put in production a complete ManifoldCF > installation. > You will be involved in the development of the following tasks, you will > learn how to: > * Write Docker files > * Write Docker Compose files > * Implement unit tests > * Build all the integration tests > * Write the documentation for new component > We have a complete documentation about ManifioldCF: > [https://manifoldcf.apache.org/release/release-2.9.1/en_US/concepts.html] > Take a look at our book to understand better the framework and how to extend > it in different ways: > [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs] > > Prospective GSOC mentor: > [piergior...@apache.org|mailto:piergior...@apache.org] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1492) Add support for Docker
[ https://issues.apache.org/jira/browse/CONNECTORS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790085#comment-17790085 ] Piergiorgio Lucidi commented on CONNECTORS-1492: Please see ManifoldCF SDK that I have released on my Github account: [https://github.com/OpenPj/manifoldcf-sdk] > Add support for Docker > -- > > Key: CONNECTORS-1492 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1492 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Labels: devops, docker > Original Estimate: 240h > Remaining Estimate: 240h > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > To discuss this or other ideas with your potential mentor from the Apache > ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, > including "[GSOC]" in the subject. You may also comment on this Jira issue if > you have created an account. > We would like to adopt Docker to provide ready to use images with > preconfigured architecture stack for ManifoldCF. This will include ManifoldCF > itself but also the related database that can be MySQL, PostgreSQL and so on. > This will help developers to work and put in production a complete ManifoldCF > installation. > You will be involved in the development of the following tasks, you will > learn how to: > * Write Docker files > * Write Docker Compose files > * Implement unit tests > * Build all the integration tests > * Write the documentation for new component > We have a complete documentation about ManifioldCF: > [https://manifoldcf.apache.org/release/release-2.9.1/en_US/concepts.html] > Take a look at our book to understand better the framework and how to extend > it in different ways: > [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs] > > Prospective GSOC mentor: > [piergior...@apache.org|mailto:piergior...@apache.org] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1706) ManifoldCF SDK
[ https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790084#comment-17790084 ] Piergiorgio Lucidi commented on CONNECTORS-1706: A first working version of the ManifoldCF SDK is released here: [https://github.com/OpenPj/manifoldcf-sdk] I'm wondering if it is something that we want to include in the Apache project as an official SDK. > ManifoldCF SDK > -- > > Key: CONNECTORS-1706 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1706 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Original Estimate: 168h > Remaining Estimate: 168h > > I'm working on a ManifoldCF SDK, a Maven project with Docker integration that > we could also use for testing purposes. > Below you can find the current status of this development, totally separated > from the ManifoldCF source code because it is a totally independent project. > In my mind I would like to have something like the following: # Creating a > new Docker image with OpenJDK 11, Ant and Maven installed - DONE > # Downloading ManifoldCF source code (MCF version is an argument) - DONE > # Running the Docker container for installing all the Maven dependencies: > ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - > DONE > # Storing the Maven Repo and the installation in two separated Docker > Volumes - DONE > # Running the Docker container for executing tests: ant test - DONE (I have > issues with Elasticsearch at the moment for this) > # Copy the overall Maven Repo locally on the host in order to have all the > Maven dependencies available the MCF SDK classpath - DONE > # Compiling a mcf-extensions-jar module in order to compile new connectors > or extensions that developers want to implement (DONE) > # Overlaying the ManifoldCF Docker image with extensions compiled with the > SDK (DONE) > # Running the final container with extensions (DONE) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1706) ManifoldCF SDK
[ https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790084#comment-17790084 ] Piergiorgio Lucidi edited comment on CONNECTORS-1706 at 11/27/23 1:36 PM: -- A first working version of the ManifoldCF SDK is released here: [https://github.com/OpenPj/manifoldcf-sdk/releases/tag/v0.0.3] I'm wondering if it is something that we want to include in the Apache project as an official SDK. was (Author: piergiorgioluc...@gmail.com): A first working version of the ManifoldCF SDK is released here: [https://github.com/OpenPj/manifoldcf-sdk] I'm wondering if it is something that we want to include in the Apache project as an official SDK. > ManifoldCF SDK > -- > > Key: CONNECTORS-1706 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1706 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Original Estimate: 168h > Remaining Estimate: 168h > > I'm working on a ManifoldCF SDK, a Maven project with Docker integration that > we could also use for testing purposes. > Below you can find the current status of this development, totally separated > from the ManifoldCF source code because it is a totally independent project. > In my mind I would like to have something like the following: # Creating a > new Docker image with OpenJDK 11, Ant and Maven installed - DONE > # Downloading ManifoldCF source code (MCF version is an argument) - DONE > # Running the Docker container for installing all the Maven dependencies: > ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - > DONE > # Storing the Maven Repo and the installation in two separated Docker > Volumes - DONE > # Running the Docker container for executing tests: ant test - DONE (I have > issues with Elasticsearch at the moment for this) > # Copy the overall Maven Repo locally on the host in order to have all the > Maven dependencies available the MCF SDK classpath - DONE > # Compiling a mcf-extensions-jar module in order to compile new connectors > or extensions that developers want to implement (DONE) > # Overlaying the ManifoldCF Docker image with extensions compiled with the > SDK (DONE) > # Running the final container with extensions (DONE) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1706) ManifoldCF SDK
[ https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi updated CONNECTORS-1706: --- Description: I'm working on a ManifoldCF SDK, a Maven project with Docker integration that we could also use for testing purposes. Below you can find the current status of this development, totally separated from the ManifoldCF source code because it is a totally independent project. In my mind I would like to have something like the following: # Creating a new Docker image with OpenJDK 11, Ant and Maven installed - DONE # Downloading ManifoldCF source code (MCF version is an argument) - DONE # Running the Docker container for installing all the Maven dependencies: ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - DONE # Storing the Maven Repo and the installation in two separated Docker Volumes - DONE # Running the Docker container for executing tests: ant test - DONE (I have issues with Elasticsearch at the moment for this) # Copy the overall Maven Repo locally on the host in order to have all the Maven dependencies available the MCF SDK classpath - DONE # Compiling a mcf-extensions-jar module in order to compile new connectors or extensions that developers want to implement (DONE) # Overlaying the ManifoldCF Docker image with extensions compiled with the SDK (DONE) # Running the final container with extensions (DONE) was: I'm working on a ManifoldCF SDK, a Maven project with Docker integration that we could also use for testing purposes. Below you can find the current status of this development, totally separated from the ManifoldCF source code because it is a totally independent project. In my mind I would like to have something like the following: # Creating a new Docker image with OpenJDK 11, Ant and Maven installed - DONE # Downloading ManifoldCF source code (MCF version is an argument) - DONE # Running the Docker container for installing all the Maven dependencies: ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - DONE # Storing the Maven Repo and the installation in two separated Docker Volumes - DONE # Running the Docker container for executing tests: ant test - DONE (I have issues with Elasticsearch at the moment for this) # Copy the overall Maven Repo locally on the host in order to have all the Maven dependencies available the MCF SDK classpath - DONE # Compiling a mcf-extensions-jar module in order to compile new connectors or extensions that developers want to implement (TODO) # Overlaying the ManifoldCF Docker image with extensions compiled with the SDK (TODO) # Running the final container with extensions (TODO) > ManifoldCF SDK > -- > > Key: CONNECTORS-1706 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1706 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Original Estimate: 168h > Remaining Estimate: 168h > > I'm working on a ManifoldCF SDK, a Maven project with Docker integration that > we could also use for testing purposes. > Below you can find the current status of this development, totally separated > from the ManifoldCF source code because it is a totally independent project. > In my mind I would like to have something like the following: # Creating a > new Docker image with OpenJDK 11, Ant and Maven installed - DONE > # Downloading ManifoldCF source code (MCF version is an argument) - DONE > # Running the Docker container for installing all the Maven dependencies: > ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - > DONE > # Storing the Maven Repo and the installation in two separated Docker > Volumes - DONE > # Running the Docker container for executing tests: ant test - DONE (I have > issues with Elasticsearch at the moment for this) > # Copy the overall Maven Repo locally on the host in order to have all the > Maven dependencies available the MCF SDK classpath - DONE > # Compiling a mcf-extensions-jar module in order to compile new connectors > or extensions that developers want to implement (DONE) > # Overlaying the ManifoldCF Docker image with extensions compiled with the > SDK (DONE) > # Running the final container with extensions (DONE) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Deleted] (CONNECTORS-1711) ManifoldCF SDK
[ https://issues.apache.org/jira/browse/CONNECTORS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi deleted CONNECTORS-1711: --- > ManifoldCF SDK > -- > > Key: CONNECTORS-1711 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1711 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Priority: Major > Original Estimate: 360h > Remaining Estimate: 360h > > I'm working on a ManifoldCF SDK, a Maven project with Docker integration, the > main purpose is to provide a smart way to developers for implementing, > testing and packaging new connectors and any other extensions. > This SDK is using the same containerization strategy used in the > CONNECTORS-1492. > > Below you can find the current status of this development, totally separated > from the ManifoldCF source code because it is a totally independent project. > > In my mind I would like to have something like the following: # Creating a > new Docker image with OpenJDK 11, Ant and Maven installed - DONE > # Downloading ManifoldCF source code (MCF version is an argument) - DONE > # Running the Docker container for installing all the Maven dependencies: > ant make-core-deps make-deps build; mvn clean install -DskipTests,skipITs - > DONE > # Storing the Maven Repo and the installation in two separated Docker > Volumes - DONE > # Running the Docker container for executing tests: ant test - DONE (I have > issues with Elasticsearch at the moment for this) > # Copy the overall Maven Repo locally on the host in order to have all the > Maven dependencies available the MCF SDK classpath - DONE > # Compiling a mcf-extensions-jar module in order to compile new connectors > or extensions that developers want to implement (DONE) > # Overlaying the ManifoldCF Docker image with extensions compiled with the > SDK (DONE) > # Running the final container with extensions (DONE) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CONNECTORS-1751) HDFS Connector - Maven build issue
[
https://issues.apache.org/jira/browse/CONNECTORS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-1751.
Resolution: Fixed
Resolved in r1914159.
> HDFS Connector - Maven build issue
> --
>
> Key: CONNECTORS-1751
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1751
> Project: ManifoldCF
> Issue Type: Bug
> Components: HDFS connector
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Thanks to the ManifoldCF SDK, I found another issue with the Maven build.
> Steps to reproduce the issue with the Manifold SDK:
>
> 1. Clone the ManifoldCF SDK project from the following URL:
> git clone [https://github.com/OpenPj/manifoldcf-sdk.git]
>
> 2. Remove row 27 from the {{run.sh}} script, this line is including the
> hotfix for the Hadoop version upgrading it to the latest version 3.3.6.
>
> 3. Run the following command in order to download the MCF source code and run
> the Ant and Maven build process in a Docker container (Maven 3.9.5 and JDK
> Temurin 11).
>
> This in order to install locally all the Maven dependencies needed to
> implement custom extensions / connectors. The Docker Volume includes the
> entire Maven repo (around 1GB) used by the ManifoldCF build process and it
> will be copied in the SDK target folder and configured in order to compile
> your Java Custom code:
>
> ./run.sh init 2.26 ga
>
> The current version of the ManifoldCF SDK 0.0.3 includes all the sep
> instructions to fix all the build problems described here including the
> Hadoop one:
> https://issues.apache.org/jira/browse/CONNECTORS-1750
>
> These issues are also resolved in ManifoldCF main trunk, except the Hadoop
> one, but these are still present in the latest release packages (source code
> packages).
> I have to confess that I don't know if those issue are also included in other
> releases.
>
> The SDK is returning the following error that should be related to the Hadoop
> Annotations dependencies of Hadoop 2.6.0, an old version of Hadoop that
> includes a JDK 1.6 dependency: }} jdk.tools:jdk.tools:jar:1.6{}}}.
>
> {code:java}
> [ERROR] Failed to execute goal on project mcf-hdfs-connector: Could not
> resolve dependencies for project
> org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following artifacts
> could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find artifact
> jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project mcf-hdfs-connector: Could not resolve dependencies for
> project org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following
> artifacts could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find
> artifact jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResolver.java:243)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
> (LifecycleDependencyResolver.java:136)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
> (MojoExecutor.java:355)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:313)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.ut
[jira] [Updated] (CONNECTORS-1751) HDFS Connector - Maven build issue
[
https://issues.apache.org/jira/browse/CONNECTORS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1751:
---
Description:
Thanks to the ManifoldCF SDK, I found another issue with the Maven build.
Steps to reproduce the issue with the Manifold SDK:
1. Clone the ManifoldCF SDK project from the following URL:
git clone [https://github.com/OpenPj/manifoldcf-sdk.git]
2. Remove row 27 from the {{run.sh}} script, this line is including the hotfix
for the Hadoop version upgrading it to the latest version 3.3.6.
3. Run the following command in order to download the MCF source code and run
the Ant and Maven build process in a Docker container (Maven 3.9.5 and JDK
Temurin 11).
This in order to install locally all the Maven dependencies needed to implement
custom extensions / connectors. The Docker Volume includes the entire Maven
repo (around 1GB) used by the ManifoldCF build process and it will be copied in
the SDK target folder and configured in order to compile your Java Custom code:
./run.sh init 2.26 ga
The current version of the ManifoldCF SDK 0.0.3 includes all the sep
instructions to fix all the build problems described here including the Hadoop
one:
https://issues.apache.org/jira/browse/CONNECTORS-1750
These issues are also resolved in ManifoldCF main trunk, except the Hadoop one,
but these are still present in the latest release packages (source code
packages).
I have to confess that I don't know if those issue are also included in other
releases.
The SDK is returning the following error that should be related to the Hadoop
Annotations dependencies of Hadoop 2.6.0, an old version of Hadoop that
includes a JDK 1.6 dependency: }} jdk.tools:jdk.tools:jar:1.6{}}}.
{code:java}
[ERROR] Failed to execute goal on project mcf-hdfs-connector: Could not resolve
dependencies for project org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The
following artifacts could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could
not find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
/opt/java/openjdk/../lib/tools.jar -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project mcf-hdfs-connector: Could not resolve dependencies for project
org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following artifacts
could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find artifact
jdk.tools:jdk.tools:jar:1.6 at specified path /opt/java/openjdk/../lib/tools.jar
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:243)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:136)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
(MojoExecutor.java:355)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:313)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:628)
at java.lang.Thread.run (Thread.java:829)
. . .
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
/opt/java/openjdk/../lib/tools.jar
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:305)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:261)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
(DefaultRepositorySystem.java:
[jira] [Assigned] (CONNECTORS-1751) HDFS Connector - Maven build issue
[
https://issues.apache.org/jira/browse/CONNECTORS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi reassigned CONNECTORS-1751:
--
Assignee: Piergiorgio Lucidi
> HDFS Connector - Maven build issue
> --
>
> Key: CONNECTORS-1751
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1751
> Project: ManifoldCF
> Issue Type: Bug
> Components: HDFS connector
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Thanks to the ManifoldCF SDK, I found another issue with the Maven build.
> Steps to reproduce the issue with the Manifold SDK:
>
> 1. Clone the ManifoldCF SDK project from the following URL:
> git clone [https://github.com/OpenPj/manifoldcf-sdk.git]
>
> 2. Remove row 27 from the {{run.sh}} script, this line is including the
> hotfix for the Hadoop version upgrading it to the latest version 3.3.6.
>
> 3. Run the following command in order to download the MCF source code and run
> the Ant and Maven build process in a Docker container (Maven 3.9.5 and JDK
> Temurin 11).
>
> This in order to install locally all the Maven dependencies needed to
> implement custom extensions / connectors. The Docker Volume includes the
> entire Maven repo (around 1GB) used by the ManifoldCF build process and it
> will be copied in the SDK target folder and configured in order to compile
> your Java Custom code:
>
> ./run.sh init 2.26 ga
>
> The current version of the ManifoldCF SDK 0.0.3 includes all the sep
> instructions to fix all the build problems described here including the
> Hadoop one:
> https://issues.apache.org/jira/browse/CONNECTORS-1750
>
> These issues are also resolved in ManifoldCF main trunk, except the Hadoop
> one, but these are still present in the latest release packages (source code
> packages).
> I have to confess that I don't know if those issue are also included in other
> releases.
>
> The SDK is returning the following error that should be related to the Hadoop
> Annotations dependencies of Hadoop 2.6.0, an old version of Hadoop that
> includes a JDK 1.6 dependency: }} jdk.tools:jdk.tools:jar:1.6{}}}.
>
> {code:java}
> [ERROR] Failed to execute goal on project mcf-hdfs-connector: Could not
> resolve dependencies for project
> org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following artifacts
> could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find artifact
> jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project mcf-hdfs-connector: Could not resolve dependencies for
> project org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following
> artifacts could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find
> artifact jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResolver.java:243)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
> (LifecycleDependencyResolver.java:136)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
> (MojoExecutor.java:355)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:313)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:193)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:180)
> at java.ut
[jira] [Comment Edited] (CONNECTORS-1751) HDFS Connector - Maven build issue
[
https://issues.apache.org/jira/browse/CONNECTORS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789591#comment-17789591
]
Piergiorgio Lucidi edited comment on CONNECTORS-1751 at 11/24/23 10:39 PM:
---
Using ManifoldCF SDK, adding the following dependency in the
{{connectors/hdfs/pom.xml}} solved the issue:
{code:java}
org.apache.hadoop
hadoop-annotations
${hadoop.version}
jdk.tools
jdk.tools
{code}
was (Author: piergiorgioluc...@gmail.com):
Using ManifoldCF SDK, adding the following dependency solved the issue:
{code:java}
org.apache.hadoop
hadoop-annotations
${hadoop.version}
jdk.tools
jdk.tools
{code}
> HDFS Connector - Maven build issue
> --
>
> Key: CONNECTORS-1751
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1751
> Project: ManifoldCF
> Issue Type: Bug
> Components: HDFS connector
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Thanks to the ManifoldCF SDK, I found another issue with the Maven build.
> Steps to reproduce the issue with the Manifold SDK:
>
> 1. Clone the ManifoldCF SDK project from the following URL:
> git clone [https://github.com/OpenPj/manifoldcf-sdk.git]
>
> 2. Remove row 27 from the {{run.sh}} script, this line is including the
> hotfix for the Hadoop version upgrading it to the latest version 3.3.6.
>
> 3. Run the following command in order to download the MCF source code and run
> the Ant and Maven build process in a Docker container (Maven 3.9.5 and JDK
> Temurin 11).
>
> This in order to install locally all the Maven dependencies needed to
> implement custom extensions / connectors. The Docker Volume includes the
> entire Maven repo (around 1GB) used by the ManifoldCF build process and it
> will be copied in the SDK target folder and configured in order to compile
> your Java Custom code:
>
> ./run.sh init 2.26 ga
>
> The current version of the [ManifoldCF SDK
> (0.0.2-Beta)|https://github.com/OpenPj/manifoldcf-sdk/releases/tag/v0.0.2-Beta]
> includes all the sep instructions to fix all the build problems described
> here including the Hadoop one:
> https://issues.apache.org/jira/browse/CONNECTORS-1750
>
> These issues are also resolved in ManifoldCF main trunk, except the Hadoop
> one, but these are still present in the latest release packages (source code
> packages).
> I have to confess that I don't know if those issue are also included in other
> releases.
>
> The SDK is returning the following error that should be related to the Hadoop
> Annotations dependencies of Hadoop 2.6.0, an old version of Hadoop that
> includes a JDK 1.6 dependency: }} jdk.tools:jdk.tools:jar:1.6{}}}.
>
> {code:java}
> [ERROR] Failed to execute goal on project mcf-hdfs-connector: Could not
> resolve dependencies for project
> org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following artifacts
> could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find artifact
> jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project mcf-hdfs-connector: Could not resolve dependencies for
> project org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following
> artifacts could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find
> artifact jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResolver.java:243)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
> (LifecycleDependencyResolver.java:136)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
> (MojoExecutor.java:355)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:313)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.Mo
[jira] [Commented] (CONNECTORS-1751) HDFS Connector - Maven build issue
[
https://issues.apache.org/jira/browse/CONNECTORS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789591#comment-17789591
]
Piergiorgio Lucidi commented on CONNECTORS-1751:
Using ManifoldCF SDK, adding the following dependency solved the issue:
{code:java}
org.apache.hadoop
hadoop-annotations
${hadoop.version}
jdk.tools
jdk.tools
{code}
> HDFS Connector - Maven build issue
> --
>
> Key: CONNECTORS-1751
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1751
> Project: ManifoldCF
> Issue Type: Bug
> Components: HDFS connector
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Thanks to the ManifoldCF SDK, I found another issue with the Maven build.
> Steps to reproduce the issue with the Manifold SDK:
>
> 1. Clone the ManifoldCF SDK project from the following URL:
> git clone [https://github.com/OpenPj/manifoldcf-sdk.git]
>
> 2. Remove row 27 from the {{run.sh}} script, this line is including the
> hotfix for the Hadoop version upgrading it to the latest version 3.3.6.
>
> 3. Run the following command in order to download the MCF source code and run
> the Ant and Maven build process in a Docker container (Maven 3.9.5 and JDK
> Temurin 11).
>
> This in order to install locally all the Maven dependencies needed to
> implement custom extensions / connectors. The Docker Volume includes the
> entire Maven repo (around 1GB) used by the ManifoldCF build process and it
> will be copied in the SDK target folder and configured in order to compile
> your Java Custom code:
>
> ./run.sh init 2.26 ga
>
> The current version of the [ManifoldCF SDK
> (0.0.2-Beta)|https://github.com/OpenPj/manifoldcf-sdk/releases/tag/v0.0.2-Beta]
> includes all the sep instructions to fix all the build problems described
> here including the Hadoop one:
> https://issues.apache.org/jira/browse/CONNECTORS-1750
>
> These issues are also resolved in ManifoldCF main trunk, except the Hadoop
> one, but these are still present in the latest release packages (source code
> packages).
> I have to confess that I don't know if those issue are also included in other
> releases.
>
> The SDK is returning the following error that should be related to the Hadoop
> Annotations dependencies of Hadoop 2.6.0, an old version of Hadoop that
> includes a JDK 1.6 dependency: }} jdk.tools:jdk.tools:jar:1.6{}}}.
>
> {code:java}
> [ERROR] Failed to execute goal on project mcf-hdfs-connector: Could not
> resolve dependencies for project
> org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following artifacts
> could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find artifact
> jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project mcf-hdfs-connector: Could not resolve dependencies for
> project org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following
> artifacts could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find
> artifact jdk.tools:jdk.tools:jar:1.6 at specified path
> /opt/java/openjdk/../lib/tools.jar
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
> (LifecycleDependencyResolver.java:243)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
> (LifecycleDependencyResolver.java:136)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
> (MojoExecutor.java:355)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:313)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.li
[jira] [Updated] (CONNECTORS-1751) HDFS Connector - Maven build issue
[
https://issues.apache.org/jira/browse/CONNECTORS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1751:
---
Description:
Thanks to the ManifoldCF SDK, I found another issue with the Maven build.
Steps to reproduce the issue with the Manifold SDK:
1. Clone the ManifoldCF SDK project from the following URL:
git clone [https://github.com/OpenPj/manifoldcf-sdk.git]
2. Remove row 27 from the {{run.sh}} script, this line is including the hotfix
for the Hadoop version upgrading it to the latest version 3.3.6.
3. Run the following command in order to download the MCF source code and run
the Ant and Maven build process in a Docker container (Maven 3.9.5 and JDK
Temurin 11).
This in order to install locally all the Maven dependencies needed to implement
custom extensions / connectors. The Docker Volume includes the entire Maven
repo (around 1GB) used by the ManifoldCF build process and it will be copied in
the SDK target folder and configured in order to compile your Java Custom code:
./run.sh init 2.26 ga
The current version of the [ManifoldCF SDK
(0.0.2-Beta)|https://github.com/OpenPj/manifoldcf-sdk/releases/tag/v0.0.2-Beta]
includes all the sep instructions to fix all the build problems described here
including the Hadoop one:
https://issues.apache.org/jira/browse/CONNECTORS-1750
These issues are also resolved in ManifoldCF main trunk, except the Hadoop one,
but these are still present in the latest release packages (source code
packages).
I have to confess that I don't know if those issue are also included in other
releases.
The SDK is returning the following error that should be related to the Hadoop
Annotations dependencies of Hadoop 2.6.0, an old version of Hadoop that
includes a JDK 1.6 dependency: }} jdk.tools:jdk.tools:jar:1.6{}}}.
{code:java}
[ERROR] Failed to execute goal on project mcf-hdfs-connector: Could not resolve
dependencies for project org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The
following artifacts could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could
not find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
/opt/java/openjdk/../lib/tools.jar -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project mcf-hdfs-connector: Could not resolve dependencies for project
org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following artifacts
could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find artifact
jdk.tools:jdk.tools:jar:1.6 at specified path /opt/java/openjdk/../lib/tools.jar
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:243)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:136)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
(MojoExecutor.java:355)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:313)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:628)
at java.lang.Thread.run (Thread.java:829)
. . .
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
/opt/java/openjdk/../lib/tools.jar
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:305)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:261)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependenc
[jira] [Created] (CONNECTORS-1751) HDFS Connector - Maven build issue
Piergiorgio Lucidi created CONNECTORS-1751:
--
Summary: HDFS Connector - Maven build issue
Key: CONNECTORS-1751
URL: https://issues.apache.org/jira/browse/CONNECTORS-1751
Project: ManifoldCF
Issue Type: Bug
Components: HDFS connector
Affects Versions: ManifoldCF 2.26
Reporter: Piergiorgio Lucidi
Fix For: ManifoldCF next
Thanks to the ManifoldCF SDK, I found another issue with the Maven build.
Steps to reproduce the issue with the Manifold SDK:
1. Clone the ManifoldCF SDK project from the following URL:
git clone [https://github.com/OpenPj/manifoldcf-sdk.git]
2. Remove row 27 from the {{run.sh}} script, this line is including the hotfix
for the Hadoop version upgrading it to the latest version 3.3.6.
3. Run the following command in order to download the MCF source code and run
the Ant and Maven build process in a Docker container (Maven 3.9.5 and JDK
Temurin 11).
This in order to install locally all the Maven dependencies needed to implement
custom extensions / connectors. The Docker Volume includes the entire Maven
repo (around 1GB) used by the ManifoldCF build process and it will be copied in
the SDK target folder and configured in order to compile your Java Custom code:
./run.sh init 2.26 ga
The current version of the ManifoldCF SDK (0.0.2-SNAPSHOT) includes all the sep
instructions to fix all the build problems described here including the Hadoop
one:
https://issues.apache.org/jira/browse/CONNECTORS-1750
These issues are also resolved in ManifoldCF main trunk, except the Hadoop one,
but these are still present in the latest release packages (source code
packages).
I have to confess that I don't know if those issue are also included in other
releases.
The SDK is returning the following error that should be related to the Hadoop
Annotations dependencies of Hadoop 2.6.0, an old version of Hadoop that
includes a JDK 1.6 dependency: {{{} jdk.tools:jdk.tools:jar:1.6{}}}.
[ERROR] Failed to execute goal on project mcf-hdfs-connector: Could not resolve
dependencies for project org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The
following artifacts could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could
not find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
/opt/java/openjdk/../lib/tools.jar -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project mcf-hdfs-connector: Could not resolve dependencies for project
org.apache.manifoldcf:mcf-hdfs-connector:jar:2.26: The following artifacts
could not be resolved: jdk.tools:jdk.tools:jar:1.6: Could not find artifact
jdk.tools:jdk.tools:jar:1.6 at specified path /opt/java/openjdk/../lib/tools.jar
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:243)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:136)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
(MojoExecutor.java:355)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:313)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:628)
at java.lang.Thread.run (Thread.java:829)
. . .
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
find artifact jdk.tools:jdk.tools:jar:1.6 at specified path
/opt/java/openjdk/../lib/tools.jar
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:
[jira] [Comment Edited] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789473#comment-17789473
]
Piergiorgio Lucidi edited comment on CONNECTORS-1750 at 11/24/23 3:08 PM:
--
I found an issue related to the Ant build of the Solr connector:
{code:java}
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials{code}
I updated the {{connectors/solr/build.xml}} adding a new attribute
{{{}erroronmissingdir="false"{}}}:
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
In order to patch the Ant and Maven build process for any recent version of
ManifoldCF source package, we could share the following commands for string
replacement:
{code:java}
sed -i -e 's// /g'
connectors/csv/pom.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases/https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
build.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases\//https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
connectors/nuxeo/pom.xml;{code}
I had to include these sed instructions in the run.sh of the ManifoldCF SDK in
order to solve all the build problems.
was (Author: piergiorgioluc...@gmail.com):
I found an issue related to the Ant build of the Solr connector:
{code:java}
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials{code}
I updated the {{connectors/solr/build.xml}} adding a new attribute
{{{}erroronmissingdir="false"{}}}:
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
In order to patch the Ant and Maven build process for any recent version of
ManifoldCF source package, we could share the following commands for string
replacement:
{code:java}
sed -i -e 's// /g'
connectors/csv/pom.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases/https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
build.xml;{code}
I had to include these sed instructions in the run.sh of the ManifoldCF SDK in
order to solve all the build problems.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for UR
[jira] [Resolved] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-1750.
Resolution: Fixed
Resolved in r1914089.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789473#comment-17789473
]
Piergiorgio Lucidi edited comment on CONNECTORS-1750 at 11/24/23 2:47 PM:
--
I found an issue related to the Ant build of the Solr connector:
{code:java}
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials{code}
I updated the {{connectors/solr/build.xml}} adding a new attribute
{{{}erroronmissingdir="false"{}}}:
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
In order to patch the Ant and Maven build process for any recent version of
ManifoldCF source package, we could share the following commands for string
replacement:
{code:java}
sed -i -e 's// /g'
connectors/csv/pom.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases/https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
build.xml;{code}
I had to include these sed instructions in the run.sh of the ManifoldCF SDK in
order to solve all the build problems.
was (Author: piergiorgioluc...@gmail.com):
I found an issue related to the Ant build of the Solr connector:
{code:java}
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials{code}
I updated the {{connectors/solr/build.xml}} adding a new attribute
{{{}erroronmissingdir="false"{}}}:
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
In order to patch the Ant and Maven build process for any recent version of
ManifoldCF source package, we could share the following commands for string
replacement:
{code:java}
sed -i -e 's// /g'
connectors/csv/pom.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases/https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
build.xml;{code}
I had to include these sed instructions in the run.sh of the ManifoldCF SDK in
order to solve all the build problems.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https:/
[jira] [Comment Edited] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789473#comment-17789473
]
Piergiorgio Lucidi edited comment on CONNECTORS-1750 at 11/24/23 2:46 PM:
--
I found an issue related to the Ant build of the Solr connector:
{code:java}
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials{code}
I updated the {{connectors/solr/build.xml}} adding a new attribute
{{{}erroronmissingdir="false"{}}}:
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
In order to patch the Ant and Maven build process for any recent version of
ManifoldCF source package, we could share the following commands for string
replacement:
{code:java}
sed -i -e 's// /g'
connectors/csv/pom.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases/https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
build.xml;{code}
I had to include these sed instructions in the run.sh of the ManifoldCF SDK in
order to solve all the build problems.
was (Author: piergiorgioluc...@gmail.com):
I found an issue related to the Ant build of the Solr connector:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials
I have updated the connectors/solr/build.xml adding a new attribute
erroronmissingdir="false":
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
In order to patch the Ant and Maven build process for any recent version of
ManifoldCF source package, we could share the following commands for string
replacement:
{code:java}
sed -i -e 's// /g'
connectors/csv/pom.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases/https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
build.xml;{code}
I had to include these sed instructions in the run.sh of the ManifoldCF SDK in
order to solve all the build problems.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org
[jira] [Comment Edited] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789473#comment-17789473
]
Piergiorgio Lucidi edited comment on CONNECTORS-1750 at 11/24/23 2:45 PM:
--
I found an issue related to the Ant build of the Solr connector:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials
I have updated the connectors/solr/build.xml adding a new attribute
erroronmissingdir="false":
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
In order to patch the Ant and Maven build process for any recent version of
ManifoldCF source package, we could share the following commands for string
replacement:
{code:java}
sed -i -e 's// /g'
connectors/csv/pom.xml; \
sed -i -e
's/https\:\/\/maven.nuxeo.org\/nexus\/content\/repositories\/public-releases/https\:\/\/packages.nuxeo.com\/repository\/maven-public-archives/g'
build.xml;{code}
I had to include these sed instructions in the run.sh of the ManifoldCF SDK in
order to solve all the build problems.
was (Author: piergiorgioluc...@gmail.com):
I found an issue related to the Ant build of the Solr connector:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials
I have updated the connectors/solr/build.xml adding a new attribute
erroronmissingdir="false":
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789473#comment-17789473
]
Piergiorgio Lucidi commented on CONNECTORS-1750:
I found an issue related to the Ant build of the Solr connector:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:485: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/build.xml:471: The following
error occurred while executing this line:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/build.xml:108:
Directory does not exist:
/home/jenkins/workspace/ManifoldCF/ManifoldCF-ant/connectors/solr/test-materials
I have updated the connectors/solr/build.xml adding a new attribute
erroronmissingdir="false":
{code:java}
{code}
Another issue related to the Maven build of the CSV connector, the Maven pom
was not valid and finally I updated the URL of the Nuxeo Maven repo.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi reopened CONNECTORS-1750:
We have to update also the Maven build
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1750:
---
Affects Version/s: ManifoldCF 2.26
(was: ManifoldCF next)
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-1750.
Fix Version/s: ManifoldCF next
Resolution: Fixed
Fixed in r1914074
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF next
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1750:
---
Affects Version/s: ManifoldCF next
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF next
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1750:
---
Affects Version/s: (was: ManifoldCF 2.26)
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1750:
---
Component/s: Build
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1750:
---
Affects Version/s: ManifoldCF 2.26
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 2.26
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789259#comment-17789259
]
Piergiorgio Lucidi commented on CONNECTORS-1750:
It seems that the new Maven repo is available on a new Nexus Pro instance, the
JAR can be downloaded here:
[https://packages.nuxeo.com/repository/maven-public-archives/org%2Fnuxeo%2Fclient%2Fnuxeo-java-client%2F3.0.1%2Fnuxeo-java-client-3.0.1.jar]
I'm going to change our build script in order to get this JAR from this new URL.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-1750:
---
Description:
Trying to build ManifoldCF, during the first step when we run:
{{ant make-core-deps}}
the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
It seems that they have a problem with that Nexus instance at the moment:
{noformat}
download-via-nuxeo:
[get] Getting:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] To:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Can't get
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
to
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
Anyway I noticed that this Maven dependency is also available in Maven Central
at the following URL:
[https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
So we could just change the URL for downloading this JAR.
was:
Trying to build ManifoldCF, during the first step when we run:
{{ant make-core-deps}}
the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
It seems that they have a problem with that Nexus instance at the moment:
{noformat}
download-via-nuxeo:
[get] Getting:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] To:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Can't get
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
to
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
Anyway I noticed that this Maven dependency is also available in Maven Central
at the following URL:
[https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
So we could just change the URL for downloading this JAR.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP
[jira] [Commented] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
[
https://issues.apache.org/jira/browse/CONNECTORS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789257#comment-17789257
]
Piergiorgio Lucidi commented on CONNECTORS-1750:
Unfortunately the Maven Central is just forwarding the download request to:
[https://maven-eu.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar]
That unfortunately it doesn't work.
> Build broken due to the Nuxeo Maven repo not available
> --
>
> Key: CONNECTORS-1750
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
> Project: ManifoldCF
> Issue Type: Bug
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>
> Trying to build ManifoldCF, during the first step when we run:
> {{ant make-core-deps}}
> the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
> It seems that they have a problem with that Nexus instance at the moment:
>
> {noformat}
> download-via-nuxeo:
> [get] Getting:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] To:
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Error opening connection java.io.IOException: Server returned
> HTTP response code: 500 for URL:
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> [get] Can't get
> https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
> to
> /Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
>
> Anyway I noticed that this Maven dependency is also available in Maven
> Central at the following URL:
> [https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
> So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available
Piergiorgio Lucidi created CONNECTORS-1750:
--
Summary: Build broken due to the Nuxeo Maven repo not available
Key: CONNECTORS-1750
URL: https://issues.apache.org/jira/browse/CONNECTORS-1750
Project: ManifoldCF
Issue Type: Bug
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Trying to build ManifoldCF, during the first step when we run:
{{ant make-core-deps}}
the nuxeo-java-client-3.0.1.jar is not available from the Nuxeo Maven repo.
It seems that they have a problem with that Nexus instance at the moment:
{noformat}
download-via-nuxeo:
[get] Getting:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] To:
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Error opening connection java.io.IOException: Server returned HTTP
response code: 500 for URL:
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
[get] Can't get
https://maven.nuxeo.org/nexus/content/repositories/public-releases/org/nuxeo/client/nuxeo-java-client/3.0.1/nuxeo-java-client-3.0.1.jar
to
/Users/piergiorgiolucidi/Documents/workspaces/manifoldNew/mcf-trunk-2023/lib/nuxeo-java-client-3.0.1.jar{noformat}
Anyway I noticed that this Maven dependency is also available in Maven Central
at the following URL:
[https://mvnrepository.com/artifact/org.nuxeo.client/nuxeo-java-client/3.0.1]
So we could just change the URL for downloading this JAR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785779#comment-17785779
]
Guylaine Bassette commented on CONNECTORS-1749:
---
Hello,
I have added a few more details in the description to help.
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
> !image-2023-11-14-08-28-57-668.png!
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> you need to have a working query for the group part. Indeed, if the groups
> query is invalid and if you obtain an error code 52 into ldapsearch and MCF
> logs, it means that this query is the issue.
> Try the default query of MCF :
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-28-57-668.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But you
need to have a working query for the group part. Indeed, if the groups query is
invalid and if you obtain an error code 52 into ldapsearch and MCF logs, it
means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-28-57-668.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But you
need to have a working query for the group part. Indeed, if the groups query is
invalid and if you obtain an error code 52 into ldapsearch and MCF logs, it
means that this query is the issue.
Try the default query of MCF :
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-28-57-668.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But you
need to have a working query for the group part. Indeed, if the groups query is
invalid and if you obtain an error code 52 into ldapsearch and MCF logs, it
means that this query is the issue.
Try the default query of MCF :
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Attachment: (was: image-2023-11-14-08-12-53-191.png)
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
>
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> when you try to
> If this part is OK, you need to have a working query for the group part.
> Indeed, if the groups query is invalid and if you obtain an error code 52
> into ldapsearch and MCF logs, it means that this query is the issue.
> Try the default query of MCF :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-27-49-930.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> LDAP Authority: make Group parameters optional
> --
>
&
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-27-49-930.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
> !image-2023-11-14-08-27-49-930.png!
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
>
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Attachment: image-2023-11-14-08-28-57-668.png
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
>
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> when you try to
> If this part is OK, you need to have a working query for the group part.
> Indeed, if the groups query is invalid and if you obtain an error code 52
> into ldapsearch and MCF logs, it means that this query is the issue.
> Try the default query of MCF :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Attachment: (was: image-2023-11-14-08-27-49-930.png)
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
> !image-2023-11-14-08-27-49-930.png!
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> when you try to
> If this part is OK, you need to have a working query for the group part.
> Indeed, if the groups query is invalid and if you obtain an error code 52
> into ldapsearch and MCF logs, it means that this query is the issue.
> Try the default query of MCF :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: image-2023-11-14-08-27-49-930.png > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png, > image-2023-11-14-08-27-49-930.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: image-2023-11-14-08-21-20-901.png > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: (was: image-2023-11-14-08-21-20-901.png) > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: image-2023-11-14-08-12-53-191.png > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Description: The group parameters are mandatory in MCF, but some LDAP servers don't require such parameters to answer to queries related to a user in order to get back authorization tokens. With such LDAP servers, you therefore do not need to input group related information to have a working search. But there is a negative aspect: there are scenarios where you may NOT know any group related information since it is not needed for those LDAP servers. But since MCF requires these parameters, anything that you put in, in order for MCF to validate the configuration, will be sent to the LDAP server that will generate an error answer because the group parameters are incorrect: Error code 52 - Object Not Found Error. was: The group parameters are mandatory in MCF, but some LDAP servers don't require such parameters to answer to queries related to a user in order to get back authorization tokens. With such LDAP servers, you therefore do not need to input group related information to have a working search. But there is a negative aspect: there are scenarios where you may NOT know any group related information since it is not needed for those LDAP servers. But since MCF requires these parameters, anything that you put in, in order for MCF to validate the configuration, will be sent to the LDAP server that will generate an error answer because the group parameters are incorrect: Object Not Found Error. > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
Guylaine Bassette created CONNECTORS-1749: - Summary: LDAP Authority: make Group parameters optional Key: CONNECTORS-1749 URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 Project: ManifoldCF Issue Type: Improvement Components: LDAP authority Reporter: Guylaine Bassette The group parameters are mandatory in MCF, but some LDAP servers don't require such parameters to answer to queries related to a user in order to get back authorization tokens. With such LDAP servers, you therefore do not need to input group related information to have a working search. But there is a negative aspect: there are scenarios where you may NOT know any group related information since it is not needed for those LDAP servers. But since MCF requires these parameters, anything that you put in, in order for MCF to validate the configuration, will be sent to the LDAP server that will generate an error answer because the group parameters are incorrect: Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
[ https://issues.apache.org/jira/browse/CONNECTORS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773001#comment-17773001 ] Mingchun Zhao edited comment on CONNECTORS-1748 at 10/11/23 7:56 PM: - Hi [~daddywri] , I've prepared a PR as below: https://github.com/apache/manifoldcf/pull/154 Could you confirm this please? Best regards, Mingchun was (Author: mingchun.zhao): Hi [~daddywri] , I've prepared a PR as below: [https://github.com/apache/manifoldcf/pull/153] Could you confirm this please? Best regards, Mingchun > Add "User-Agent platform" option for crawling mobile websites > - > > Key: CONNECTORS-1748 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Mingchun Zhao >Priority: Major > > Hi [~daddywri] , > Allow me propose a new feature for crawling mobile sites which restrict > access to content based on User-Agent header. > Actually, Our customer's mobile website was failing to crawl because access > was restricted based on whether the User-Agent request header includes the > mobile info. For this reason, we added the "User-Agent platform" option to > the new "Request Headers" tab on the web repository connector page so that > this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773278#comment-17773278 ] Julien Massiera commented on CONNECTORS-1740: - Bonjour, Merci pour votre email. Mr Massiera a quitte ses fonctions le 14 avril 2023 et cet email sera bientot desactive. Pour toute question sur France Labs ou sur des projets en cours, merci de contacter cedric.ulmer att francelabs.com > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773277#comment-17773277 ] Guylaine Bassette commented on CONNECTORS-1740: --- Hello [~kwri...@metacarta.com], Thanks to have merged my Zookeeper fix ! We have tested it in our application and everything works well: job configuration and Solr indexation. > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773268#comment-17773268 ] Julien Massiera commented on CONNECTORS-1740: - Bonjour, Merci pour votre email. Mr Massiera a quitte ses fonctions le 14 avril 2023 et cet email sera bientot desactive. Pour toute question sur France Labs ou sur des projets en cours, merci de contacter cedric.ulmer att francelabs.com > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773266#comment-17773266 ] Guylaine Bassette commented on CONNECTORS-1740: --- Hello [~mingchun.zhao], Thanks for your contribution with Java 11 ! (y) I have integrated your patch with my contribution to fix the Zookeeper bug (PR 150, al ready merged to the master Branch). > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
[ https://issues.apache.org/jira/browse/CONNECTORS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao reassigned CONNECTORS-1748: - Assignee: (was: Mingchun Zhao) > Add "User-Agent platform" option for crawling mobile websites > - > > Key: CONNECTORS-1748 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Mingchun Zhao >Priority: Major > > Hi [~daddywri] , > Allow me propose a new feature for crawling mobile sites which restrict > access to content based on User-Agent header. > Actually, Our customer's mobile website was failing to crawl because access > was restricted based on whether the User-Agent request header includes the > mobile info. For this reason, we added the "User-Agent platform" option to > the new "Request Headers" tab on the web repository connector page so that > this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
[ https://issues.apache.org/jira/browse/CONNECTORS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773001#comment-17773001 ] Mingchun Zhao commented on CONNECTORS-1748: --- Hi [~daddywri] , I've prepared a PR as below: [https://github.com/apache/manifoldcf/pull/153] Could you confirm this please? Best regards, Mingchun > Add "User-Agent platform" option for crawling mobile websites > - > > Key: CONNECTORS-1748 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Mingchun Zhao >Assignee: Mingchun Zhao >Priority: Major > > Hi [~daddywri] , > Allow me propose a new feature for crawling mobile sites which restrict > access to content based on User-Agent header. > Actually, Our customer's mobile website was failing to crawl because access > was restricted based on whether the User-Agent request header includes the > mobile info. For this reason, we added the "User-Agent platform" option to > the new "Request Headers" tab on the web repository connector page so that > this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
Mingchun Zhao created CONNECTORS-1748: - Summary: Add "User-Agent platform" option for crawling mobile websites Key: CONNECTORS-1748 URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 Project: ManifoldCF Issue Type: New Feature Reporter: Mingchun Zhao Assignee: Mingchun Zhao Hi [~daddywri] , Allow me propose a new feature for crawling mobile sites which restrict access to content based on User-Agent header. Actually, Our customer's mobile website was failing to crawl because access was restricted based on whether the User-Agent request header includes the mobile info. For this reason, we added the "User-Agent platform" option to the new "Request Headers" tab on the web repository connector page so that this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740 ] Julien Massiera deleted comment on CONNECTORS-1740: - was (Author: julienfl): Bonjour, Merci pour votre email. Mr Massiera a quitte ses fonctions le 14 avril 2023 et cet email sera bientot desactive. Pour toute question sur France Labs ou sur des projets en cours, merci de contacter cedric.ulmer att francelabs.com > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740 ] Julien Massiera deleted comment on CONNECTORS-1740: - was (Author: julienfl): Bonjour, Merci pour votre email. Mr Massiera a quitte ses fonctions le 14 avril 2023 et cet email sera bientot desactive. Pour toute question sur France Labs ou sur des projets en cours, merci de contacter cedric.ulmer att francelabs.com > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740 ] Julien Massiera deleted comment on CONNECTORS-1740: - was (Author: julienfl): Bonjour, Merci pour votre email. Mr Massiera a quitte ses fonctions le 14 avril 2023 et cet email sera bientot desactive. Pour toute question sur France Labs ou sur des projets en cours, merci de contacter cedric.ulmer att francelabs.com > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
