[jira] [Resolved] (CONNECTORS-1637) New Confluence connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Massiera resolved CONNECTORS-1637. - Fix Version/s: ManifoldCF 2.16 Resolution: Fixed > New Confluence connector > > > Key: CONNECTORS-1637 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1637 > Project: ManifoldCF > Issue Type: New Feature > Components: Confluence connector >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Fix For: ManifoldCF 2.16 > > > We need to address 3 main issues of the current Confluence connector : > - it does not correctly implements the security > - it has performance problems when handling a huge dataset > - it generates a version string for documents that is not sufficient to > detect all changes > To resolve some of these issues, the connector has to use the new confluence > API which is available from the v6. For that reason we need to release a new > connector. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CONNECTORS-1637) New Confluence connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053598#comment-17053598 ] Julien Massiera commented on CONNECTORS-1637: - [~kwri...@metacarta.com] I fixed the ant build. The branch is done ! > New Confluence connector > > > Key: CONNECTORS-1637 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1637 > Project: ManifoldCF > Issue Type: New Feature > Components: Confluence connector >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > > We need to address 3 main issues of the current Confluence connector : > - it does not correctly implements the security > - it has performance problems when handling a huge dataset > - it generates a version string for documents that is not sufficient to > detect all changes > To resolve some of these issues, the connector has to use the new confluence > API which is available from the v6. For that reason we need to release a new > connector. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CONNECTORS-1637) New Confluence connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053563#comment-17053563
]
Karl Wright commented on CONNECTORS-1637:
-
At the root level:
{code}
ant make-core-deps
ant build
{code}
This will download the dependencies, then build the framework and build all the
connectors. After that you can debug your build locally for your connector by:
{code}
cd connectors/
ant build
{code}
> New Confluence connector
>
>
> Key: CONNECTORS-1637
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1637
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Confluence connector
>Reporter: Julien Massiera
>Assignee: Julien Massiera
>Priority: Major
>
> We need to address 3 main issues of the current Confluence connector :
> - it does not correctly implements the security
> - it has performance problems when handling a huge dataset
> - it generates a version string for documents that is not sufficient to
> detect all changes
> To resolve some of these issues, the connector has to use the new confluence
> API which is available from the v6. For that reason we need to release a new
> connector.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CONNECTORS-1637) New Confluence connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053558#comment-17053558 ] Julien Massiera commented on CONNECTORS-1637: - [~kwri...@metacarta.com] I think the branch is done, but what is the process to test the build with ant ? cause when I execute "ant all" in the connector's folder it says that the dist/connector-build.xml file is not found in the manifoldcf root folder ? Executing "ant build" in the root folder does not solve my issue > New Confluence connector > > > Key: CONNECTORS-1637 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1637 > Project: ManifoldCF > Issue Type: New Feature > Components: Confluence connector >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > > We need to address 3 main issues of the current Confluence connector : > - it does not correctly implements the security > - it has performance problems when handling a huge dataset > - it generates a version string for documents that is not sufficient to > detect all changes > To resolve some of these issues, the connector has to use the new confluence > API which is available from the v6. For that reason we need to release a new > connector. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CONNECTORS-1637) New Confluence connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053396#comment-17053396 ] Julien Massiera commented on CONNECTORS-1637: - Yes [~kwri...@metacarta.com], I am working on this and also make sure it does not conflicts with the original connector > New Confluence connector > > > Key: CONNECTORS-1637 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1637 > Project: ManifoldCF > Issue Type: New Feature > Components: Confluence connector >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > > We need to address 3 main issues of the current Confluence connector : > - it does not correctly implements the security > - it has performance problems when handling a huge dataset > - it generates a version string for documents that is not sufficient to > detect all changes > To resolve some of these issues, the connector has to use the new confluence > API which is available from the v6. For that reason we need to release a new > connector. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CONNECTORS-1637) New Confluence connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053389#comment-17053389 ] Karl Wright commented on CONNECTORS-1637: - I saw you committed code in a branch (CONNECTORS-1637) for this. Wonderful! Can you let me know when you think the branch is done? Key things: getting the ant build to work, and making sure ant rat-sources is happy with your Apache headers. > New Confluence connector > > > Key: CONNECTORS-1637 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1637 > Project: ManifoldCF > Issue Type: New Feature > Components: Confluence connector >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > > We need to address 3 main issues of the current Confluence connector : > - it does not correctly implements the security > - it has performance problems when handling a huge dataset > - it generates a version string for documents that is not sufficient to > detect all changes > To resolve some of these issues, the connector has to use the new confluence > API which is available from the v6. For that reason we need to release a new > connector. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CONNECTORS-1637) New Confluence connector
Julien Massiera created CONNECTORS-1637: --- Summary: New Confluence connector Key: CONNECTORS-1637 URL: https://issues.apache.org/jira/browse/CONNECTORS-1637 Project: ManifoldCF Issue Type: New Feature Components: Confluence connector Reporter: Julien Massiera Assignee: Julien Massiera We need to address 3 main issues of the current Confluence connector : - it does not correctly implements the security - it has performance problems when handling a huge dataset - it generates a version string for documents that is not sufficient to detect all changes To resolve some of these issues, the connector has to use the new confluence API which is available from the v6. For that reason we need to release a new connector. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: New confluence connector
Hi Julien, I agree if there are significant version restrictions it should be released as a different connector than the one that is already there. Can you create an svn branch and start setting this up in it? There should also be a ticket created that you can use to name your branch. It's important to make sure there are no name collisions with the existing connector, of course. Thanks! Karl On Thu, Mar 5, 2020 at 12:59 PM wrote: > Hi Karl, > > > > I have developed a new Confluence connector based on the existing one in > order to address 3 main issues : > > - the current connector does not correctly implements the security > > - the current connector has performance problems when handling a huge > dataset > > - the current connector generates a version string for documents that is > not > sufficient to detect all changes > > > > I would like to contribute it to the MCF community. But I am not sure what > is the best way to do it, since the core code is very different from the > original one. Furthermore it is only compatible from confluence v6 and > above. So I was thinking that we may release it as a different connector, > but I'd prefer to have your opinion on that. > > > > What do you think? > > > > Best regards, > > Julien > >
New confluence connector
Hi Karl, I have developed a new Confluence connector based on the existing one in order to address 3 main issues : - the current connector does not correctly implements the security - the current connector has performance problems when handling a huge dataset - the current connector generates a version string for documents that is not sufficient to detect all changes I would like to contribute it to the MCF community. But I am not sure what is the best way to do it, since the core code is very different from the original one. Furthermore it is only compatible from confluence v6 and above. So I was thinking that we may release it as a different connector, but I'd prefer to have your opinion on that. What do you think? Best regards, Julien
