Re: Create Release Candidate GitHub Workflow

[Piergiorgio Lucidi]

Hi folks,

in order to finalize the new release process, I created a ticket in the
INFRA project:
https://issues.apache.org/jira/browse/INFRA-25665

Then I had to involve the Apache Security Team for letting us use GitHub
GPG keys.
It seems that we have to adopt a release process similar to what our
friends at OpenDAL did for their project:
https://github.com/apache/opendal/blob/main/website/community/committers/verify.md#check-the-maven-artifacts-of-opendal-java

This is because the GitHub CI platform is not a trusted hardware for the
ASF, so for validating any new release, we have to build locally the same
package and verify the GPG sign and the checksums.

Here is the documentation of the OpenDAL check script:
https://github.com/apache/opendal/tree/main/scripts

I think that we could adopt exactly the same process.
What do you think?

Cheers,
PG

Il giorno ven 29 mar 2024 alle ore 20:13 Karl Wright 
ha scritto:

> Svn url for review:
>
>  https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26
>
> Our area in this svn:
>
>  https://dist.apache.org/repos/dist/dev/manifoldcf
> <https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26>
>
> Our area for releases in this svn:
>
>  https://dist.apache.org/repos/dist/release/manifoldcf
> <https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26>
>
> To move a release candidate from one to the other (e.g. do the release):
>
> svn move
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26
>
> https://dist.apache.org/repos/dist/release/manifoldcf/apache-manifoldcf-2.26
> <https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26>
>
>
>
> On Fri, Mar 29, 2024 at 3:09 PM Karl Wright  wrote:
>
> > The script as it exists now (release.bat) creates the release artifacts,
> > signs them, and copies them into the svn development area.  To actually
> > release, you then just need to move them (using svn move) to the release
> > part of the area.
> >
> > The machine I used to do this on died but the svn URL for the dev area is
> > the one I would send around for the review and signoff for the releases.
> > Let me look it up.
> >
> >
> >
> >
> > On Fri, Mar 29, 2024 at 11:44 AM Piergiorgio Lucidi <
> > piergior...@apache.org> wrote:
> >
> >> The open points now are related to the last two steps of our workflow:
> >>
> >>- Generating the file hashes using a shared GPG secret (in
> progress...)
> >>- Updating SVN public folders for publishing releases (TODO)
> >>
> >> We should agree with the Automated Release Process before proceeding:
> >>
> >>
> https://issues.apache.org/jira/browse/INFRA-25665?focusedCommentId=17832209=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17832209
> >>
> >> Practically INFRA will generate a new GPG key and they will add the
> public
> >> key into the ManifoldCF KEYS file.
> >> This will let us manage the generation of file hashes using a GitHub
> >> actions.
> >>
> >> Do you all agree with this?
> >> Please let me know.
> >> Thanks.
> >>
> >> Cheers,
> >> PG
> >>
> >> Il giorno mar 26 mar 2024 alle ore 17:19 Karl Wright <
> daddy...@gmail.com>
> >> ha scritto:
> >>
> >> > Well we obviously need something that works, and just updating the
> >> script
> >> > to use github commands is one way to do that and would generate
> releases
> >> > like we do now.
> >> >
> >> >
> >> >
> >> > On Tue, Mar 12, 2024 at 9:00 AM Piergiorgio Lucidi <
> >> piergior...@apache.org
> >> > >
> >> > wrote:
> >> >
> >> > > Hi Karl,
> >> > >
> >> > > I tried to look at the current process but It's not clear to me what
> >> > > I should do now.
> >> > > Should I just use svn commands from GitHub in order to execute the
> >> same
> >> > > steps?
> >> > > Or do we have an alternative way without using svn?
> >> > >
> >> > > Do you know if we have something GitHub-centric for managing
> releases?
> >> > >
> >> > > Cheers,
> >> > > PG
> >> > >
> >> > > Il giorno mar 5 mar 2024 alle ore 21:53 Karl Wright <
> >> daddy...@gmail.com>
> >> > > ha
> >> > > scritto:
> >> > >
> >> > > > Very good!
> &g

Re: Create Release Candidate GitHub Workflow

[Piergiorgio Lucidi]

The open points now are related to the last two steps of our workflow:

   - Generating the file hashes using a shared GPG secret (in progress...)
   - Updating SVN public folders for publishing releases (TODO)

We should agree with the Automated Release Process before proceeding:
https://issues.apache.org/jira/browse/INFRA-25665?focusedCommentId=17832209=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17832209

Practically INFRA will generate a new GPG key and they will add the public
key into the ManifoldCF KEYS file.
This will let us manage the generation of file hashes using a GitHub
actions.

Do you all agree with this?
Please let me know.
Thanks.

Cheers,
PG

Il giorno mar 26 mar 2024 alle ore 17:19 Karl Wright 
ha scritto:

> Well we obviously need something that works, and just updating the script
> to use github commands is one way to do that and would generate releases
> like we do now.
>
>
>
> On Tue, Mar 12, 2024 at 9:00 AM Piergiorgio Lucidi  >
> wrote:
>
> > Hi Karl,
> >
> > I tried to look at the current process but It's not clear to me what
> > I should do now.
> > Should I just use svn commands from GitHub in order to execute the same
> > steps?
> > Or do we have an alternative way without using svn?
> >
> > Do you know if we have something GitHub-centric for managing releases?
> >
> > Cheers,
> > PG
> >
> > Il giorno mar 5 mar 2024 alle ore 21:53 Karl Wright 
> > ha
> > scritto:
> >
> > > Very good!
> > >
> > > In the past we've often had to add new commits to the release branch
> and
> > > create a new RC.  The RCs have to be copied into the staging area (in
> an
> > > svn repo) and then when actually released there's a simple svn command
> to
> > > do that.  Are you familiar with that process?  For this reason it may
> be
> > > better to separate the creation of the release branch from everything
> > else.
> > >
> > > Karl
> > >
> > >
> > > On Tue, Mar 5, 2024 at 9:23 AM Piergiorgio Lucidi <
> > piergior...@apache.org>
> > > wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I have just pushed a potential GitHub workflow for creating the
> release
> > > > candidate branch and artifacts [1]. The related issue is available in
> > > JIRA
> > > > [2].
> > > >
> > > > We need to test it but I think that it could be something close to
> what
> > > we
> > > > need:
> > > >
> > > > 1. Create the new branch
> > > > 2. Update CHANGES.txt, build.xml and all the poms
> > > > 3. Run the Ant build
> > > > 4. Run the Maven build (if we want to push artifacts on public repos)
> > > > 5. Check licenses using Apache RAT
> > > > 6. Commit and push the new branch
> > > > 7. Upload artifacts as GitHub release assets
> > > >
> > > > Any feedback?
> > > > Thanks everyone.
> > > >
> > > > Cheers,
> > > > PG
> > > >
> > > > [1] -
> > > >
> > > >
> > >
> >
> https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml
> > > >
> > > > [2] - https://issues.apache.org/jira/browse/CONNECTORS-1754
> > > > --
> > > > Piergiorgio
> > > >
> > >
> >
> >
> > --
> > Piergiorgio
> >
>


-- 
Piergiorgio

Re: Create Release Candidate GitHub Workflow

[Piergiorgio Lucidi]

Hi folks,

now this workflow works correctly, you can take a look at the run log here:
https://github.com/apache/manifoldcf/actions/runs/8437275847

You can see the new RC created as a tag in Github:
https://github.com/apache/manifoldcf/releases/tag/2.27-RC0

There are some deprecated instructions used by the upload-release-artifact
action that should be replaced with something different.
Probably I should use the hub command to simplify everything.

I only need to upload the RC artifacts in SVN and I think that the tricky
part is done :-P

What do you think?
Please let me know.

Cheers,
PG

Il giorno mar 12 mar 2024 alle ore 13:59 Piergiorgio Lucidi <
piergior...@apache.org> ha scritto:

> Hi Karl,
>
> I tried to look at the current process but It's not clear to me what
> I should do now.
> Should I just use svn commands from GitHub in order to execute the same
> steps?
> Or do we have an alternative way without using svn?
>
> Do you know if we have something GitHub-centric for managing releases?
>
> Cheers,
> PG
>
> Il giorno mar 5 mar 2024 alle ore 21:53 Karl Wright 
> ha scritto:
>
>> Very good!
>>
>> In the past we've often had to add new commits to the release branch and
>> create a new RC.  The RCs have to be copied into the staging area (in an
>> svn repo) and then when actually released there's a simple svn command to
>> do that.  Are you familiar with that process?  For this reason it may be
>> better to separate the creation of the release branch from everything
>> else.
>>
>> Karl
>>
>>
>> On Tue, Mar 5, 2024 at 9:23 AM Piergiorgio Lucidi > >
>> wrote:
>>
>> > Hi folks,
>> >
>> > I have just pushed a potential GitHub workflow for creating the release
>> > candidate branch and artifacts [1]. The related issue is available in
>> JIRA
>> > [2].
>> >
>> > We need to test it but I think that it could be something close to what
>> we
>> > need:
>> >
>> > 1. Create the new branch
>> > 2. Update CHANGES.txt, build.xml and all the poms
>> > 3. Run the Ant build
>> > 4. Run the Maven build (if we want to push artifacts on public repos)
>> > 5. Check licenses using Apache RAT
>> > 6. Commit and push the new branch
>> > 7. Upload artifacts as GitHub release assets
>> >
>> > Any feedback?
>> > Thanks everyone.
>> >
>> > Cheers,
>> > PG
>> >
>> > [1] -
>> >
>> >
>> https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml
>> >
>> > [2] - https://issues.apache.org/jira/browse/CONNECTORS-1754
>> > --
>> > Piergiorgio
>> >
>>
>
>
> --
> Piergiorgio
>


-- 
Piergiorgio

Re: Create Release Candidate GitHub Workflow

[Piergiorgio Lucidi]

Hi Karl,

I tried to look at the current process but It's not clear to me what
I should do now.
Should I just use svn commands from GitHub in order to execute the same
steps?
Or do we have an alternative way without using svn?

Do you know if we have something GitHub-centric for managing releases?

Cheers,
PG

Il giorno mar 5 mar 2024 alle ore 21:53 Karl Wright  ha
scritto:

> Very good!
>
> In the past we've often had to add new commits to the release branch and
> create a new RC.  The RCs have to be copied into the staging area (in an
> svn repo) and then when actually released there's a simple svn command to
> do that.  Are you familiar with that process?  For this reason it may be
> better to separate the creation of the release branch from everything else.
>
> Karl
>
>
> On Tue, Mar 5, 2024 at 9:23 AM Piergiorgio Lucidi 
> wrote:
>
> > Hi folks,
> >
> > I have just pushed a potential GitHub workflow for creating the release
> > candidate branch and artifacts [1]. The related issue is available in
> JIRA
> > [2].
> >
> > We need to test it but I think that it could be something close to what
> we
> > need:
> >
> > 1. Create the new branch
> > 2. Update CHANGES.txt, build.xml and all the poms
> > 3. Run the Ant build
> > 4. Run the Maven build (if we want to push artifacts on public repos)
> > 5. Check licenses using Apache RAT
> > 6. Commit and push the new branch
> > 7. Upload artifacts as GitHub release assets
> >
> > Any feedback?
> > Thanks everyone.
> >
> > Cheers,
> > PG
> >
> > [1] -
> >
> >
> https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml
> >
> > [2] - https://issues.apache.org/jira/browse/CONNECTORS-1754
> > --
> > Piergiorgio
> >
>


-- 
Piergiorgio

Create Release Candidate GitHub Workflow

[Piergiorgio Lucidi]

Hi folks,

I have just pushed a potential GitHub workflow for creating the release
candidate branch and artifacts [1]. The related issue is available in JIRA
[2].

We need to test it but I think that it could be something close to what we
need:

1. Create the new branch
2. Update CHANGES.txt, build.xml and all the poms
3. Run the Ant build
4. Run the Maven build (if we want to push artifacts on public repos)
5. Check licenses using Apache RAT
6. Commit and push the new branch
7. Upload artifacts as GitHub release assets

Any feedback?
Thanks everyone.

Cheers,
PG

[1] -
https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml

[2] - https://issues.apache.org/jira/browse/CONNECTORS-1754
--
Piergiorgio

[jira] [Comment Edited] (CONNECTORS-1754) Converting release scripts to GitHub workflows

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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 (Jira)]

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)

Big changes: SDK, GitHub and a new website

[Piergiorgio Lucidi]

Hi all,

We are currently working on big changes in order to facilitate the adoption
of ManifoldCF for users and developers with the following activities:

   1. Introducing the new Apache ManifoldCF SDK: a Maven / Docker SDK
   facilitating developers to implement connectors, extensions and containers
   [1]
   2. Migrating the source code repository to GitHub: letting us to work on
   pull requests
   3. Converting build and release scripts into GitHub workflows [2]
   4. Designing the new website using ASF-Pelican [3]

This could take some time to be completed and we are sorry if for a while
there will be some latency in the project development and support
activities.

If you want to contribute to one of the tasks above, please let us know by
replying here or in the related issue on JIRA.

[1] - https://github.com/apache/manifoldcf-sdk
[2] - https://issues.apache.org/jira/browse/CONNECTORS-1754
[3] - https://github.com/apache/manifoldcf-site

-- 
Piergiorgio

[jira] [Commented] (CONNECTORS-1744) Migrate away from Travis-CI

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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)

Re: New feature for AD connector

[Piergiorgio Lucidi]

Hi Guylaine,

Thank you so much for contributing with this new feature.
I'm sorry for this delay, currently we are in the middle of a big change
for this project in order to accept pull requests directly from Github, a
new website and a new release process.

I think that it is something interesting to add in the project, maybe some
of the committers can take a look at this in the next few days.
Is there any volunteer to take a look at this?

Cheers,
PG

Il giorno mar 6 feb 2024 alle ore 12:36 Guylaine BASSETTE <
guylaine.basse...@francelabs.com> ha scritto:

> Hello,
>
> I have a new feature to suggest for the Active Directory connector. We've
> added a new tab that lets you add the groups name to which the user
> belongs. It appears that for some of our customers, it is more meaningful
> to secure their documents according to the name of their groups.
>
> For example, it can retrieve for one user, a list of token like this:
> *S-1-8-35-345*
> *S-1-8-24-4063278141-1379863503-3448703509-74688*
> HR_MEDICAL_SOCIAL
> HYPERINFO_MNG
> Users
> Domain+Users
> S-1-1-0
>
> Group names are retrieved, using their SID in the "sub-tree" search scope
> level, from the "sAMAccountName" attribute of the AD.
>
> If you are interested in, I have prepared a PR:
> https://github.com/apache/manifoldcf/pull/163
> --
> Best regards,
> Guylaine
>
> France Labs – Your knowledge, now
> Datafari Enterprise Search – Découvrez la version 5 / Discover our version
> 5
> www.datafari.com
>
> Datafari Enterprise Search – Retrouvez-nous à WAICF Cannes
>  du 8 au 10 février
>
> [image: Logo_temp_waicf_2024] 
>
>
>


-- 
Piergiorgio

[jira] [Commented] (CONNECTORS-1754) Converting release scripts to GitHub workflows

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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 (Jira)]

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

[Piergiorgio Lucidi (Jira)]

[ 
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)

Re: ant make-core-deps fails

[Piergiorgio Lucidi]

Hi Guylaine,

your fix is merged in the main trunk.
Thank you so much.

Cheers,
PG

Il giorno lun 15 gen 2024 alle ore 17:20 Piergiorgio Lucidi <
piergior...@apache.org> ha scritto:

> Hi Guylaine,
>
> Thank you so much for your pull request, I'll try to merge your fix
> tomorrow.
> Have a nice day.
>
> Cheers,
> PG
>
> Il giorno lun 15 gen 2024 alle ore 17:11 Guylaine BASSETTE <
> guylaine.basse...@francelabs.com> ha scritto:
>
>> Hello Piergiorgio,
>>
>> Thank you for your URLs updates for ManifoldCF distribution building. And
>> thanks for having fixed the CSV connector pom, I intended to do it in my
>> next contribution.
>>
>> 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>
>> --
>> Best Regards,
>> Guylaine
>>
>> France Labs – Your knowledge, now
>> Datafari Enterprise Search – Découvrez la version 5 / Discover our
>> version 5
>> www.datafari.com
>>
>> Datafari Enterprise Search – Retrouvez-nous à WAICF Cannes
>> <https://www.worldaicannes.com/en> du 8 au 10 février
>>
>> [image: Logo_temp_waicf_2024] <https://www.worldaicannes.com/en>
>>
>>
>>
>
>
> --
> Piergiorgio
>


-- 
Piergiorgio

[jira] [Resolved] (CONNECTORS-1753) ant make-core-deps fails

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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 (Jira)]

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-1744) Migrate away from Travis-CI

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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)

Re: ant make-core-deps fails

[Piergiorgio Lucidi]

Hi Guylaine,

Thank you so much for your pull request, I'll try to merge your fix
tomorrow.
Have a nice day.

Cheers,
PG

Il giorno lun 15 gen 2024 alle ore 17:11 Guylaine BASSETTE <
guylaine.basse...@francelabs.com> ha scritto:

> Hello Piergiorgio,
>
> Thank you for your URLs updates for ManifoldCF distribution building. And
> thanks for having fixed the CSV connector pom, I intended to do it in my
> next contribution.
>
> 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 
> --
> Best Regards,
> Guylaine
>
> France Labs – Your knowledge, now
> Datafari Enterprise Search – Découvrez la version 5 / Discover our version
> 5
> www.datafari.com
>
> Datafari Enterprise Search – Retrouvez-nous à WAICF Cannes
>  du 8 au 10 février
>
> [image: Logo_temp_waicf_2024] 
>
>
>


-- 
Piergiorgio

[jira] [Commented] (CONNECTORS-1495) Brand new website

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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)

Re: JAXBContext - JDK 11

[Piergiorgio Lucidi]

Hi Uwe,

Thank you for sharing this issue and I think that the jaxb library is
needed to solve this problem.
I didn't tested it yet but probably adding these dependencies should solve
it:

   - jaxb-core:2.3.1
   - jaxb-api:2.3.1
   - jaxb-impl:2.3.1

I'm going to replicate the issue and raise a ticket on Jira about this.
Thank you again and hope this helps ;)

Cheers,
PG





Il giorno mar 5 dic 2023 alle ore 11:55 Wolfinger Uwe 
ha scritto:

> When trying to use the Generic Authority Connector
> (org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority) we
> experienced some problems:
>
> Line 681 (context = JAXBContext.newInstance(Auth.class);) results in an
> error:
>
> javax.xml.bind.JAXBException: Implementation of JAXB-API has not been
> found on module path or classpath.
> - with linked exception:
> [java.lang.ClassNotFoundException:
> com.sun.xml.internal.bind.v2.ContextFactory]
> javax.xml.bind.JAXBException: Implementation of JAXB-API has not been
> found on module path or classpath.
> - with linked exception:
> [java.lang.ClassNotFoundException:
> com.sun.xml.internal.bind.v2.ContextFactory]
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232)
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:375)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632)
> at
> org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority$FetchTokensThread.run(GenericAuthority.java:717)
> Caused by: java.lang.ClassNotFoundException:
> com.sun.xml.internal.bind.v2.ContextFactory
> at
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412)
> at
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220)
> at
> javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:92)
> at
> javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:125)
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:230)
> ... 4 more
>
> We are using JDK 11 as our runtime envirnoment. As far as i understood,
> support for jaxb was removed in JDK 11. So my question is, does anybody
> know a workaround for this problem (adding jaxb libs manually?) or are
> there any plans to upgrade the GenericAuthority Connector to JDK 11
> (jakarta.xml.bind).
>
> Kind Regards,
> Uwe
>


-- 
Piergiorgio

[jira] [Commented] (CONNECTORS-1492) Add support for Docker

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

Re: HDFS Connector - Maven build issue found thanks to the ManifoldCF SDK

[Piergiorgio Lucidi]

Hi Karl,

it works perfectly so this means that we don't need to upgrade to a newer
version of Hadoop.
I added the following sed instruction to the ManifoldCF SDK using version
2.26 and it worked:

sed -i -e
's/<\/dependencies>/org.apache.hadoop<\/groupId>hadoop-annotations<\/artifactId>${hadoop.version}<\/version>jdk.tools<\/groupId>jdk.tools<\/artifactId><\/exclusion><\/exclusions><\/dependency><\/dependencies>/g'
connectors/hdfs/pom.xml

We have to declare the following dependency in the connectors/hdfs/pom.xml:


  org.apache.hadoop
  hadoop-annotations
  ${hadoop.version}
  

  jdk.tools
  jdk.tools

  


Cheers,
PG


Il giorno ven 24 nov 2023 alle ore 23:26 Piergiorgio Lucidi <
piergior...@apache.org> ha scritto:

> Hi Karl,
>
> the problem is that the unique dependency declared in that pom.xml is the
> hadoop-common importing hadoop-annotations that is causing the issue.
> Below what I see in the hadoop-annotations pom:
>
> 
> 
>   os.linux
>   
> 
>   !Mac
> 
>   
>   
> 
>   jdk.tools
>   jdk.tools
>   1.6
>   system
>   ${java.home}/../lib/tools.jar
> 
>   
> 
> 
>   jdk1.7
>   
> 1.7
>   
>   
> 
>   jdk.tools
>   jdk.tools
>   1.7
>   system
>   ${java.home}/../lib/tools.jar
> 
>   
> 
>   
>
> Probably we could solve declaring hadoop-annotations dependency by adding
> an exclusion related to the jdk.tools dependency.
> Something like this:
>
> 
>   org.apache.hadoop
>   hadoop-annotations
>   ${hadoop.version}
>   
> 
>   jdk.tools
>   jdk.tools
> 
>   
> 
>
> I'll try to apply this using the ManifoldCF SDK and I'll let you know
>
> Cheers,
> PG
>
>
> Il giorno ven 24 nov 2023 alle ore 21:34 Karl Wright 
> ha scritto:
>
>> Hi - the jar it's looking for may no longer be part of the java 11 jdk.
>> I'm not exactly sure how to best handle this in Maven.  It may simply be
>> possible to remove the dependency entirely from the maven pom.
>>
>>
>> On Fri, Nov 24, 2023 at 12:34 PM Piergiorgio Lucidi <
>> piergior...@apache.org>
>> wrote:
>>
>> > I have just created this ticket:
>> > https://issues.apache.org/jira/browse/CONNECTORS-1751
>> >
>> > Il giorno ven 24 nov 2023 alle ore 18:19 Piergiorgio Lucidi <
>> > piergior...@apache.org> ha scritto:
>> >
>> > > Hi folks,
>> > >
>> > > 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 ManifoldCF
>> source
>> > > code and run the Ant and Maven build process in a Docker container
>> based
>> > on
>> > > Maven 3.9.5 and OpenJDK Temurin 11This in order to install locally all
>> > the
>> > > Maven dependencies needed to implement custom extensions / connectors.
>> > The
>> > > Docker Volume includes the entire Maven repo 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 SDK includes the sep instruction to fix all
>> > the
>> > > build problems described here:
>> > > https://issues.apache.org/jira/browse/CONNECTORS-1750
>> > >
>> > > These issues are also resolved in ManifoldCF main trunk but still
>> present
>> > > in the latest previous release packages (source code packages).
>> > > I have to confess that I don't know if this issue is also included in
>> > > other releases.
>> > > The SDK is returning the following error that should be related to the
>> > > Hadoop Annotations dependencies of Hado

Re: HDFS Connector - Maven build issue found thanks to the ManifoldCF SDK

[Piergiorgio Lucidi]

Hi Karl,

the problem is that the unique dependency declared in that pom.xml is the
hadoop-common importing hadoop-annotations that is causing the issue.
Below what I see in the hadoop-annotations pom:



  os.linux
  

  !Mac

  
  

  jdk.tools
  jdk.tools
  1.6
  system
  ${java.home}/../lib/tools.jar

  


  jdk1.7
  
1.7
  
  

  jdk.tools
  jdk.tools
  1.7
  system
  ${java.home}/../lib/tools.jar

  

  

Probably we could solve declaring hadoop-annotations dependency by adding
an exclusion related to the jdk.tools dependency.
Something like this:


  org.apache.hadoop
  hadoop-annotations
  ${hadoop.version}
  

  jdk.tools
  jdk.tools

  


I'll try to apply this using the ManifoldCF SDK and I'll let you know

Cheers,
PG


Il giorno ven 24 nov 2023 alle ore 21:34 Karl Wright 
ha scritto:

> Hi - the jar it's looking for may no longer be part of the java 11 jdk.
> I'm not exactly sure how to best handle this in Maven.  It may simply be
> possible to remove the dependency entirely from the maven pom.
>
>
> On Fri, Nov 24, 2023 at 12:34 PM Piergiorgio Lucidi <
> piergior...@apache.org>
> wrote:
>
> > I have just created this ticket:
> > https://issues.apache.org/jira/browse/CONNECTORS-1751
> >
> > Il giorno ven 24 nov 2023 alle ore 18:19 Piergiorgio Lucidi <
> > piergior...@apache.org> ha scritto:
> >
> > > Hi folks,
> > >
> > > 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 ManifoldCF source
> > > code and run the Ant and Maven build process in a Docker container
> based
> > on
> > > Maven 3.9.5 and OpenJDK Temurin 11This in order to install locally all
> > the
> > > Maven dependencies needed to implement custom extensions / connectors.
> > The
> > > Docker Volume includes the entire Maven repo 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 SDK includes the sep instruction to fix all
> > the
> > > build problems described here:
> > > https://issues.apache.org/jira/browse/CONNECTORS-1750
> > >
> > > These issues are also resolved in ManifoldCF main trunk but still
> present
> > > in the latest previous release packages (source code packages).
> > > I have to confess that I don't know if this issue is 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, a very 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.LifecycleDependencyResol

[jira] [Updated] (CONNECTORS-1751) HDFS Connector - Maven build issue

[Piergiorgio Lucidi (Jira)]

 [ 
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

Re: HDFS Connector - Maven build issue found thanks to the ManifoldCF SDK

[Piergiorgio Lucidi]

I have just created this ticket:
https://issues.apache.org/jira/browse/CONNECTORS-1751

Il giorno ven 24 nov 2023 alle ore 18:19 Piergiorgio Lucidi <
piergior...@apache.org> ha scritto:

> Hi folks,
>
> 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 ManifoldCF source
> code and run the Ant and Maven build process in a Docker container based on
> Maven 3.9.5 and OpenJDK Temurin 11This in order to install locally all the
> Maven dependencies needed to implement custom extensions / connectors. The
> Docker Volume includes the entire Maven repo 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 SDK includes the sep instruction to fix all the
> build problems described here:
> https://issues.apache.org/jira/browse/CONNECTORS-1750
>
> These issues are also resolved in ManifoldCF main trunk but still present
> in the latest previous release packages (source code packages).
> I have to confess that I don't know if this issue is 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, a very 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

[jira] [Created] (CONNECTORS-1751) HDFS Connector - Maven build issue

[Piergiorgio Lucidi (Jira)]

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:

HDFS Connector - Maven build issue found thanks to the ManifoldCF SDK

[Piergiorgio Lucidi]

Hi folks,

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 ManifoldCF source
code and run the Ant and Maven build process in a Docker container based on
Maven 3.9.5 and OpenJDK Temurin 11This in order to install locally all the
Maven dependencies needed to implement custom extensions / connectors. The
Docker Volume includes the entire Maven repo 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 SDK includes the sep instruction to fix all the
build problems described here:
https://issues.apache.org/jira/browse/CONNECTORS-1750

These issues are also resolved in ManifoldCF main trunk but still present
in the latest previous release packages (source code packages).
I have to confess that I don't know if this issue is 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, a very 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:305)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:261)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
(DefaultRepositorySystem.java:353)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve
(DefaultProjectDependenciesResolver.java:182)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:224)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:136)
at

[jira] [Comment Edited] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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)

Re: Build failed in Jenkins: ManifoldCF » ManifoldCF-ant #88

[Piergiorgio Lucidi]

It seems that Jenkins can't compile with JDK 11, we can't build ManifoldCF
for a month:
https://ci-builds.apache.org/blue/organizations/jenkins/ManifoldCF%2FManifoldCF-ant/activity/

I'm going to change the jdk version on Jenkins in order to fix this problem.

Cheers,
PG


Il giorno ven 24 nov 2023 alle ore 03:23 Apache Jenkins Server <
jenk...@builds.apache.org> ha scritto:

> See <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/88/display/redirect?page=changes
> >
>
> Changes:
>
> [Piergiorgio Lucidi] updated the URL to the new Nuxeo Maven Repo in order
> to download the nuxeo-java-client (CONNECTORS-1750)
>
>
> --
> [...truncated 698.95 KB...]
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/pdfbox/jempbox/1.8.16/jempbox-1.8.16.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/jempbox-1.8.16.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/pdfbox/pdfbox/2.0.25/pdfbox-2.0.25.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/pdfbox-2.0.25.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/pdfbox/fontbox/2.0.25/fontbox-2.0.25.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/fontbox-2.0.25.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/pdfbox/preflight/2.0.25/preflight-2.0.25.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/preflight-2.0.25.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/pdfbox/xmpbox/2.0.25/xmpbox-2.0.25.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/xmpbox-2.0.25.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/pdfbox/pdfbox-debugger/2.0.25/pdfbox-debugger-2.0.25.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/pdfbox-debugger-2.0.25.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/pdfbox/pdfbox-tools/2.0.25/pdfbox-tools-2.0.25.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/pdfbox-tools-2.0.25.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.21/commons-compress-1.21.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/commons-compress-1.21.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/com/googlecode/juniversalchardet/juniversalchardet/1.0.3/juniversalchardet-1.0.3.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/juniversalchardet-1.0.3.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/de/l3s/boilerpipe/boilerpipe/1.1.0/boilerpipe-1.1.0.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/boilerpipe-1.1.0.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/dom4j-1.6.1.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/org/tallison/xmp/xmpcore-shaded/6.1.11/xmpcore-shaded-6.1.11.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/xmpcore-shaded-6.1.11.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/com/mchange/mchange-commons-java/0.2.19/mchange-commons-java-0.2.19.jar
>   [get] To: <
> https://ci-builds.apache.org/job/ManifoldCF/job/ManifoldCF-ant/ws/lib/mchange-commons-java-0.2.19.jar
> >
>
> setup-maven-url:
>
> download-via-maven:
>   [get] Getting:
> https://repo1.maven.org/maven2/com/googlecode/plist/dd-plist/1.23/dd-plist-1.23.jar
> 

[jira] [Reopened] (CONNECTORS-1750) Build broken due to the Nuxeo Maven repo not available

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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

[Piergiorgio Lucidi (Jira)]

 [ 
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

[Piergiorgio Lucidi (Jira)]

[ 
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 (Jira)]

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)

Re: [VOTE] Release ManifoldCF 2.26, RC0

[Piergiorgio Lucidi]

Hi Mingchun,

thank you for your message and I was trying to build ManifoldCF using
OpenJDK 17 so probably in the future for supporting this version of Java we
should include Jaxb libraries as well.

The build is ok now and I can compile and package everything correctly.
Unfortunately executing tests I have the following error:

compile-tests:
[javac] Compiling 1 source file to
/Users/piergiorgiolucidi/Downloads/apache-manifoldcf-2.26/connectors/kafka/build/connector-tests/classes
[javac]
/Users/piergiorgiolucidi/Downloads/apache-manifoldcf-2.26/connectors/kafka/connector/src/test/java/org/apache/manifoldcf/agents/output/kafka/ZooKeeperLocal.java:45:
error: unreported exception AdminServerException; must be caught or
declared to be thrown
[javac]   zooKeeperServer.runFromConfig(configuration);
[javac]^
[javac] 1 error

BUILD FAILED
/Users/piergiorgiolucidi/Downloads/apache-manifoldcf-2.26/build.xml:497:
The following error occurred while executing this line:
/Users/piergiorgiolucidi/Downloads/apache-manifoldcf-2.26/build.xml:471:
The following error occurred while executing this line:
/Users/piergiorgiolucidi/Downloads/apache-manifoldcf-2.26/dist/connector-build.xml:720:
Compile failed; see the compiler error output for details.

Any ideas?

Thanks.

Cheers,
PG



Il giorno gio 12 ott 2023 alle ore 10:39 Mingchun Zhao <
mingchun.zha...@gmail.com> ha scritto:

> Hi Piergiorgio,
>
> FYI, Allow me to share the java and ant versions and the build steps I ran
> in my environment.
>
> ```
> $ java --version
> openjdk 11.0.11 2021-04-20
> OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
> OpenJDK 64-Bit Server VM AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed
> mode)
>
> $ ant -version
> Apache Ant(TM) version 1.10.0 compiled on December 27 2016
> ```
> ```
> ant clean
> ant clean-deps
> ant clean-core-deps
> ant make-core-deps
> ant make-deps
> ant build
> ```
>
> Regards,
> Mingchun
>
> 2023年10月12日(木) 17:32 Piergiorgio Lucidi :
>
> > Hi folks,
> >
> > it seems that I can't compile the CswsConnector:
> >
> >[javac] public List getAttributeGroups()
> > [javac]   ^
> > [javac]   symbol:   class AttributeGroup
> > [javac]   location: class CswsConnector.ObjectInformation
> > [javac]
> >
> >
> /Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/connectors/csws/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/csws/CswsConnector.java:3966:
> > error: cannot find symbol
> > [javac] public NodePermissions getPermissions()
> > [javac]^
> > [javac]   symbol:   class NodePermissions
> > [javac]   location: class CswsConnector.ObjectInformation
> > [javac] 100 errors
> > [javac] 1 warning
> > [javac] only showing the first 100 errors, of 123 total; use
> -Xmaxerrs
> > if you would like to see more
> >
> > BUILD FAILED
> >
> /Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/build.xml:489:
> > The following error occurred while executing this line:
> >
> /Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/build.xml:471:
> > The following error occurred while executing this line:
> >
> >
> /Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/dist/connector-build.xml:686:
> > Compile failed; see the compiler error output for details.
> >
> > Do you have any ideas?
> >
> > Thanks,
> > PG
> >
> > Il giorno gio 12 ott 2023 alle ore 09:03 Guylaine BASSETTE <
> > guylaine.basse...@francelabs.com> ha scritto:
> >
> > > Hi,
> > >
> > > +1 from France Labs
> > >
> > > Regards,
> > > Guylaine
> > >
> > > France Labs – Your knowledge, now
> > > Datafari Enterprise Search – Découvrez la version 5 / Discover our
> > version
> > > 5
> > > www.datafari.com <http://www.datafari.com>
> > > Le 11/10/2023 à 23:12, Furkan KAMACI a écrit :
> > > > Hi,
> > > >
> > > > +1!
> > > >
> > > > Kind regards,
> > > > Furkan Kamaci
> > > >
> > > > On Wed, Oct 11, 2023 at 11:13 PM Mingchun Zhao<
> > mingchun.zha...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > >> Hi,
> > > >> Ran all the tests.
> > > >> +1 from me.
> > > >>
> > > >> Kind regards,
> > > >> Mingchun
> > > >>
> > > >> 2023年10月12日(木) 4:29 Cihad Guze

Re: [VOTE] Release ManifoldCF 2.26, RC0

[Piergiorgio Lucidi]

Hi folks,

it seems that I can't compile the CswsConnector:

   [javac] public List getAttributeGroups()
[javac]   ^
[javac]   symbol:   class AttributeGroup
[javac]   location: class CswsConnector.ObjectInformation
[javac]
/Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/connectors/csws/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/csws/CswsConnector.java:3966:
error: cannot find symbol
[javac] public NodePermissions getPermissions()
[javac]^
[javac]   symbol:   class NodePermissions
[javac]   location: class CswsConnector.ObjectInformation
[javac] 100 errors
[javac] 1 warning
[javac] only showing the first 100 errors, of 123 total; use -Xmaxerrs
if you would like to see more

BUILD FAILED
/Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/build.xml:489:
The following error occurred while executing this line:
/Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/build.xml:471:
The following error occurred while executing this line:
/Volumes/BackupPJ/ManifoldCF-release/apache-manifoldcf-2.26/dist/connector-build.xml:686:
Compile failed; see the compiler error output for details.

Do you have any ideas?

Thanks,
PG

Il giorno gio 12 ott 2023 alle ore 09:03 Guylaine BASSETTE <
guylaine.basse...@francelabs.com> ha scritto:

> Hi,
>
> +1 from France Labs
>
> Regards,
> Guylaine
>
> France Labs – Your knowledge, now
> Datafari Enterprise Search – Découvrez la version 5 / Discover our version
> 5
> www.datafari.com 
> Le 11/10/2023 à 23:12, Furkan KAMACI a écrit :
> > Hi,
> >
> > +1!
> >
> > Kind regards,
> > Furkan Kamaci
> >
> > On Wed, Oct 11, 2023 at 11:13 PM Mingchun Zhao >
> > wrote:
> >
> >> Hi,
> >> Ran all the tests.
> >> +1 from me.
> >>
> >> Kind regards,
> >> Mingchun
> >>
> >> 2023年10月12日(木) 4:29 Cihad Guzel:
> >>
> >>> Hi,
> >>>
> >>> +1 from me
> >>>
> >>> Regards,
> >>> Cihad Guzel
> >>>
> >>> 11 Eki 2023 Çar, saat 15:08 tarihinde Karl Wright
> >>> şunu
> >>> yazdı:
> >>>
>  Please vote on whether to release Apache ManifoldCF 2.26, RC0.
>  This release is the first release that requires at least Java 11, and
> >> it
>  also includes a new CSV connector along with support for Solr 9.  The
>  release artifact can be found at:
> 
> >>
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26
> >>> ,
>  and there is a release tag also at
>  https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.26-RC0  .
> 
>  Karl
> 



-- 
Piergiorgio

Re: Site release 2.24 docs do NOT contain release 2.24 docs, even though release artifact has them

[Piergiorgio Lucidi]

Hi Karl,

Thank you for this update.
It seems so strange because I think no one updated that part.

Cheers,
PJ

Il giorno lun 5 dic 2022 alle ore 12:42 Karl Wright  ha
scritto:

> Hi,
>
> I updated the release site yesterday evening with appropriate 2.24
> references, and checked before I mirrored it that the site as built did
> correctly contain the 2.24 release documents.  But when I uploaded to the
> publish svn directory and committed these, the release documents all went
> away. (!!!).  I don't have any explanation whatsoever for this at the
> moment.  It will require further research when I have a chance to do so.
>
> Karl
>


-- 
Piergiorgio

Re: [VOTE] Release Apache ManifoldCF 2.24, RC0

[Piergiorgio Lucidi]

Ran all the tests.

+1 from me

Cheers,
PJ

Il giorno mer 30 nov 2022 alle ore 13:27 Karl Wright 
ha scritto:

> Please vote on whether to release Apache ManifoldCF 2.24, RC0.  The release
> artifact can be found at:
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.24 .
> There is also a release tag at
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.24-RC0 .
>
> This release contains a number of fixes for issues found externally, some
> of them high priority.  We have therefore chosen to accelerate the release
> schedule, since it was originally scheduled for the end of December.  You
> can review CHANGES.txt for a partial list of the changes.
>
> Thanks,
> Karl
>


-- 
Piergiorgio

Re: [VOTE] Release Apache ManifoldCF 2.23, RC0

[Piergiorgio Lucidi]

Big +1 from me after running all the tests correctly!

Cheers,
PJ


Il giorno ven 2 set 2022 alle ore 02:25 Karl Wright  ha
scritto:

> Ran tests.
> +1 from me.
> Karl
>
>
> On Wed, Aug 24, 2022 at 3:47 AM Karl Wright  wrote:
>
> > Please vote on whether to release Apache ManifoldCF 2.23, RC0.  The
> > artifact can be found at
> > https://svn.apache.org/repos/asf/manifoldcf/branches/release-2.23-branch
> > .  There is also a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.23-RC0 .
> >
> > This release contains few changes from 2.22.1 but does include many
> > dependency related minor fixes, such as:
> >
> > 
> > r1902902 | kwright | 2022-07-21 04:27:31 -0400 (Thu, 21 Jul 2022) | 1
> line
> >
> > CONNECTORS-1541, revisited
> > 
> > r1902854 | jmssiera | 2022-07-19 09:27:31 -0400 (Tue, 19 Jul 2022) | 1
> line
> >
> > CONNECTORS-1721: Confluence v6 does not distinguish 404 errors
> > 
> > r1902717 | kwright | 2022-07-14 06:57:25 -0400 (Thu, 14 Jul 2022) | 1
> line
> >
> > Armor code against null bin names
> > 
> > r1902684 | kwright | 2022-07-12 16:29:10 -0400 (Tue, 12 Jul 2022) | 1
> line
> >
> > Fix for CONNECTORS-1720.
> > 
> > r1902537 | jmssiera | 2022-07-07 13:02:53 -0400 (Thu, 07 Jul 2022) | 1
> line
> >
> > CONNECTORS-1719: Handle MariaDB in JDBC connector
> > 
> > r1901792 | kwright | 2022-06-09 17:13:01 -0400 (Thu, 09 Jun 2022) | 1
> line
> >
> > Update xerces version
> > 
> > r1901783 | kwright | 2022-06-09 10:12:30 -0400 (Thu, 09 Jun 2022) | 1
> line
> >
> > CONNECTORS-1717: Update log4j dependency
> > 
> > r1901778 | kwright | 2022-06-09 08:30:52 -0400 (Thu, 09 Jun 2022) | 1
> line
> >
> > More fixes related to CONNECTORS-1714
> > 
> > r1901777 | kwright | 2022-06-09 07:25:31 -0400 (Thu, 09 Jun 2022) | 1
> line
> >
> > CONNECTORS-1714: Update commons-beanutils to latest version
> > 
> > r1901774 | kwright | 2022-06-09 05:58:24 -0400 (Thu, 09 Jun 2022) | 1
> line
> >
> > CONNECTORS-1716: Use SSL for downloading nuxeo
> > 
> > r1900835 | kwright | 2022-05-12 07:45:26 -0400 (Thu, 12 May 2022) | 1
> line
> >
> > Karl
> >
> >
> >
>


-- 
Piergiorgio

[jira] [Comment Edited] (CONNECTORS-1706) ManifoldCF SDK

[Piergiorgio Lucidi (Jira)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537363#comment-17537363
 ] 

Piergiorgio Lucidi edited comment on CONNECTORS-1706 at 5/16/22 6:53 AM:
-

A first version of the SDK is available here on my github account:

[https://github.com/OpenPj/manifoldcf-sdk]

After cloning the project, you can use it executing the following commands:
 # ./run.sh init 2.21 ga -> start the init process for ManifoldCF 2.21 GA
 # mvn clean install docker:build docker:start -> build extensions and run 
everything with Docker locally
 # mvn docker:stop -> stop all the containers (MCF and PostgreSQL)


was (Author: piergiorgioluc...@gmail.com):
A first version of the SDK is available here on my github account:

[https://github.com/OpenPj/manifoldcf-sdk]

After cloning the project, you can use it executing the following commands:
 # {{{}{}}}./run.sh init 2.21 ga -> start the init process for ManifoldCF 2.21 
GA
 # mvn clean install docker:build docker:start -> build extensions and run 
everything with Docker locally
 # mvn docker:stop -> stop all the containers (MCF and PostgreSQL)

> 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 (TODO)
>  # Overlaying the ManifoldCF Docker image with extensions compiled with the 
> SDK (TODO)
>  # Running the final container with extensions (TODO)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (CONNECTORS-1706) ManifoldCF SDK

[Piergiorgio Lucidi (Jira)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537363#comment-17537363
 ] 

Piergiorgio Lucidi commented on CONNECTORS-1706:


A first version of the SDK is available here on my github account:

[https://github.com/OpenPj/manifoldcf-sdk]

After cloning the project, you can use it executing the following commands:
 # {{{}{}}}./run.sh init 2.21 ga -> start the init process for ManifoldCF 2.21 
GA
 # mvn clean install docker:build docker:start -> build extensions and run 
everything with Docker locally
 # mvn docker:stop -> stop all the containers (MCF and PostgreSQL)

> 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 (TODO)
>  # Overlaying the ManifoldCF Docker image with extensions compiled with the 
> SDK (TODO)
>  # Running the final container with extensions (TODO)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [VOTE] Release Apache ManifoldCF 2.22.1, RC1

[Piergiorgio Lucidi]

Tests pass also for me, a big +1 from me!

Cheers,
PJ

Il giorno mar 10 mag 2022 alle ore 11:41 Karl Wright 
ha scritto:

> Tests pass for me. +1
>
> Karl
>
>
> On Tue, May 10, 2022 at 5:34 AM Julien Massiera <
> julien.massi...@francelabs.com> wrote:
>
> > All tests ok + manual UI test ok. +1
> >
> > Julien
> >
> > -Message d'origine-
> > De : Karl Wright 
> > Envoyé : mardi 10 mai 2022 03:19
> > À : dev 
> > Objet : [VOTE] Release Apache ManifoldCF 2.22.1, RC1
> >
> > Please vote on whether to release Apache ManifoldCF 2.22.1, RC1.  The
> > release artifact can be found at
> >
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.22.1
> > .
> > There is also a release tag at
> > https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.22.1-RC1.
> >
> > This patch release fixes two problems in 2.22: (1) the new LDAP mapper
> had
> > the same name as the Regexp mapper, which caused a unique index
> constraint
> > violation, and (2) there were conflicting versions of Apache Velocity
> > installed, which meant that template resolution failed in some cases.
> >
> > Further changes included fixing the Maven build to add missing
> > dependencies.
> >
> > Thanks,
> > Karl
> >
> >
>


-- 
Piergiorgio

Re: Docker support and ManifoldCF SDK

[Piergiorgio Lucidi]

Hi folks,

I have just shared in my github account the project:
https://github.com/OpenPj/manifoldcf-sdk

This is just a temporary location, it would be great to have it managed
officially in the ASF.

The main run.sh script is currently available only for Linux but I think
that can be easily converted for Windows.
Probably a lot of things can be embedded in the pom.xml using the
docker-maven-plugin so please consider that this is just the first version.

Please let me know what you think.
Thanks.

Cheers,
PJ

Il giorno dom 8 mag 2022 alle ore 00:16 Furkan KAMACI <
furkankam...@gmail.com> ha scritto:

> Hi Piergiorgio,
>
> Is there any link to check the source code of the current status?
>
> Kind Regards,
> Furkan KAMACI
>
> On Thu, May 5, 2022 at 12:01 AM Markus Schuch 
> wrote:
>
> > Hi PJ,
> >
> > If the SDK project has a dependency on the Sources ZIP file, then it
> > also seems more natural to me to set up the SDK project as a separate
> > repository.
> >
> > A standalone repository would also have the advantage that we don't make
> > the module structure and the build in the trunk even more complex and
> > bloatet further. And it is also easier for us to introduce modern
> > tooling without being slowed down by the legacy in the the main
> repository.
> >
> > It might even be our ticket to gaining a foothold in git.
> >
> > Cheers,
> > Markus
> >
> >
> > Am 04.05.2022 um 13:29 schrieb Piergiorgio Lucidi:
> > > Hi folks,
> > >
> > > I added an initial Docker support in the branch CONNECTORS-1492 and I
> > have
> > > also created a new issue related to the ManifoldCF SDK:
> > >
> >
> https://issues.apache.org/jira/projects/CONNECTORS/issues/CONNECTORS-1706
> > >
> > > The current status of this new project is described in the issue,
> > > practically it works correctly, we only need to provide some examples
> of
> > > each type of connector.
> > > So I'm wondering where we could host this new project.
> > >
> > > Should we put the code in the main trunk?
> > > In this case I could continue to work on the branch CONNECTORS-1492
> > > creating a new folder in the root of the project with the sdk.
> > > I have to confess that following this way it sounds strange to me
> because
> > > the sdk is referring to the source code downloading it during the
> > > initialization process.
> > >
> > > Or should we create a separate project for this sdk?
> > > It sounds better to me this approach but I would like to receive your
> > > feedback.
> > >
> > > Please let me know.
> > > Thanks.
> > >
> > > Cheers,
> > > PJ
> > >
> >
>


-- 
Piergiorgio

Docker support and ManifoldCF SDK

[Piergiorgio Lucidi]

Hi folks,

I added an initial Docker support in the branch CONNECTORS-1492 and I have
also created a new issue related to the ManifoldCF SDK:
https://issues.apache.org/jira/projects/CONNECTORS/issues/CONNECTORS-1706

The current status of this new project is described in the issue,
practically it works correctly, we only need to provide some examples of
each type of connector.
So I'm wondering where we could host this new project.

Should we put the code in the main trunk?
In this case I could continue to work on the branch CONNECTORS-1492
creating a new folder in the root of the project with the sdk.
I have to confess that following this way it sounds strange to me because
the sdk is referring to the source code downloading it during the
initialization process.

Or should we create a separate project for this sdk?
It sounds better to me this approach but I would like to receive your
feedback.

Please let me know.
Thanks.

Cheers,
PJ

-- 
Piergiorgio

[jira] [Commented] (CONNECTORS-1706) ManifoldCF SDK

[Piergiorgio Lucidi (Jira)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531674#comment-17531674
 ] 

Piergiorgio Lucidi commented on CONNECTORS-1706:


The containerization method is the same used for the ManifoldCF source code

> 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 (TODO)
>  # Overlaying the ManifoldCF Docker image with extensions compiled with the 
> SDK (TODO)
>  # Running the final container with extensions (TODO)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (CONNECTORS-1711) ManifoldCF SDK

[Piergiorgio Lucidi (Jira)]

Piergiorgio Lucidi created CONNECTORS-1711:
--

 Summary: ManifoldCF SDK
 Key: CONNECTORS-1711
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1711
 Project: ManifoldCF
  Issue Type: New Feature
Reporter: Piergiorgio Lucidi


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.7#820007)

Re: [VOTE] Release Apache ManifoldCF 2.22, RC3

[Piergiorgio Lucidi]

Hi folks,

ran all the tests correctly.
+1 from me

Cheers,
PG

Il giorno ven 29 apr 2022 alle ore 15:41 Karl Wright 
ha scritto:

> Hi,
>
> Please vote on whether to release Apache ManifoldCF 2.22, RC3.  The release
> artifact is at
> https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.22 .
> There is also a release tag at
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-2.22-RC3 .
>
> This release contains a Tika update which required extensive dependency
> updates, which needs some degree of testing, as well as a new LDAP Mapper.
>
> RC1 also contains a CMIS fix from Piergiorgio, as well as an LDAP Mapper
> pom fix.
> RC2 has a fix for the MongoDB test download issue.
> RC3 has several fixes for other connectors.
>
> Thanks in advance,
> Karl
>


-- 
Piergiorgio

Re: [CANCEL] [VOTE] Release Apache ManifoldCF 2.22, RC2

[Piergiorgio Lucidi]

Nope, no errors, I have a BUILD SUCCESSFUL

Il giorno ven 29 apr 2022 alle ore 14:54 Karl Wright 
ha scritto:

> once again, I have the same.
>
> Can you try this:
>
> cd connectors/mongodb
> ant run-tests
>
> Do you get a compilation exception?
>
> Karl
>
>
> On Fri, Apr 29, 2022 at 8:49 AM Piergiorgio Lucidi  >
> wrote:
>
> > -rw-r--r--  1 pjlucidi  staff  613352 29 Apr 11:46
> > mongo-java-driver-2.14.3.jar
> >
> > Il giorno ven 29 apr 2022 alle ore 14:48 Karl Wright  >
> > ha scritto:
> >
> > > I have same:
> > >
> > > 04/28/2022  06:24 AM  .
> > > 04/28/2022  06:24 AM  ..
> > > 04/28/2022  06:24 AM   189,132
> > de.flapdoodle.embed.mongo-3.4.5.jar
> > > 04/28/2022  06:24 AM   111,113
> > > de.flapdoodle.embed.mongo.packageresolver-1.0.3.jar
> > > 04/28/2022  06:24 AM   215,729
> > > de.flapdoodle.embed.process-3.1.10.jar
> > > 04/28/2022  06:24 AM   107,870 de.flapdoodle.os-1.1.8.jar
> > > 04/19/2020  05:47 AM 1,197 README.txt
> > >5 File(s)625,041 bytes
> > >2 Dir(s)  106,148,036,608 bytes free
> > >
> > > What version of mongo* do you have in your lib directory?
> > >
> > > Karl
> > >
> > >
> > > On Fri, Apr 29, 2022 at 8:42 AM Piergiorgio Lucidi <
> > piergior...@apache.org
> > > >
> > > wrote:
> > >
> > > > -rw-r--r--  1 pjlucidi  staff  107870 29 Apr 11:47
> > > > de.flapdoodle.os-1.1.8.jar
> > > > -rw-r--r--  1 pjlucidi  staff  215729 29 Apr 11:47
> > > > de.flapdoodle.embed.process-3.1.10.jar
> > > > -rw-r--r--  1 pjlucidi  staff  13 29 Apr 11:47
> > > > de.flapdoodle.embed.mongo.packageresolver-1.0.3.jar
> > > > -rw-r--r--  1 pjlucidi  staff  189132 29 Apr 11:47
> > > > de.flapdoodle.embed.mongo-3.4.5.jar
> > > >
> > >
> >
> >
> > --
> > Piergiorgio
> >
>


-- 
Piergiorgio