[jira] [Created] (TIKA-1825) Add 2.x branch to Hudson
Tim Allison created TIKA-1825: - Summary: Add 2.x branch to Hudson Key: TIKA-1825 URL: https://issues.apache.org/jira/browse/TIKA-1825 Project: Tika Issue Type: Task Reporter: Tim Allison Would it make sense to add the 2.x branch to our Hudson builds...or have we already done this? [~lewismc], do I remember correctly that you last fixed our Hudson builds? I have no idea how to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TIKA-1824) Tika 2.0 - Create Initial Parser Modules
[ https://issues.apache.org/jira/browse/TIKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085946#comment-15085946 ] Tim Allison commented on TIKA-1824: --- [~bobpaulin], this is an awesome step forward. Must have been a fair amount of work. Thank you! Few questions...not just for you, but for all. I'm happy to submit/commit patches, but I want to make sure I don't do anything objectionable to the community * This is probably user error, but I'm getting: \[ERROR\] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack (unpack) on project tika-text-module: Unable to find artifact. Could not find artifact org.apache.tika:tika-test-resources:jar:tests:2.0-SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots) * Perhaps rename artifact names in parser sub-components to include "Parser(s?)", e.g. Apache Tika Parser Advanced Module so that the names sort more clearly (at least in the maven window in Intellij)? * Perhaps add "parser(s?) to the artifactId, e.g. tika-parser-cad-module * Perhaps lowercase names in parser-subcomponents so that they're inline with legacy: "Apache Tika parser advanced module" * Pkcs7Parser ... should that be under advanced...or somewhere else ...own crypto package? * iwork ...should we move that to office? * tika-test-resources...should we move TikaTest into that and change the name to tika-test? I have a vague memory of wanting to carve out a separate test package earlier and adding TikaTest and something else... * OutlookPSTParser...move that to office? * Does MBox belong in web? Not sure where to put it? * Move CommonsDigester to core _if_ we're willing to add a dependency on commons-digest into core? * Move Activator to tika-bundle? * Move pot to multimedia or add tika-parsers-multimedia-advanced-module? * Move geo.topic to "advanced"...perhaps we rename "advanced" to ner? * Move ctakes to "advanced/ner"? * Collapse web and text? Again, this is fantastic. Thank you! > Tika 2.0 - Create Initial Parser Modules > - > > Key: TIKA-1824 > URL: https://issues.apache.org/jira/browse/TIKA-1824 > Project: Tika > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Bob Paulin >Assignee: Bob Paulin > > Create initial break down of parser modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TIKA-1824) Tika 2.0 - Create Initial Parser Modules
[ https://issues.apache.org/jira/browse/TIKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085946#comment-15085946 ] Tim Allison edited comment on TIKA-1824 at 1/6/16 6:08 PM: --- [~bobpaulin], this is an awesome step forward. Must have been a fair amount of work. Thank you! Few questions...not just for you, but for all. I'm happy to submit/commit patches, but I want to make sure I don't do anything objectionable to the community * This is probably user error, but I'm getting: \[ERROR\] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack (unpack) on project tika-text-module: Unable to find artifact. Could not find artifact org.apache.tika:tika-test-resources:jar:tests:2.0-SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots) * Perhaps rename artifact names in parser sub-components to include "Parser(s?)", e.g. Apache Tika Parser Advanced Module so that the names sort more clearly (at least in the maven window in Intellij)? * Perhaps add "parser(s?) to the artifactId, e.g. tika-parser-cad-module * Perhaps lowercase names in parser-subcomponents so that they're inline with legacy: "Apache Tika parser advanced module" * Pkcs7Parser ... should that be under advanced...or somewhere else ...own crypto package? * iwork ...should we move that to office? * tika-test-resources...should we move TikaTest into that and change the name to tika-test? I have a vague memory of wanting to carve out a separate test package earlier and adding TikaTest and something else... * OutlookPSTParser...move that to office? * Does MBox belong in web? Not sure where to put it? * Move CommonsDigester to core _if_ we're willing to add a dependency on commons-codec into core? * Move Activator to tika-bundle? * Move pot to multimedia or add tika-parsers-multimedia-advanced-module? * Move geo.topic to "advanced"...perhaps we rename "advanced" to ner? * Move ctakes to "advanced/ner"? * Collapse web and text? Again, this is fantastic. Thank you! was (Author: talli...@mitre.org): [~bobpaulin], this is an awesome step forward. Must have been a fair amount of work. Thank you! Few questions...not just for you, but for all. I'm happy to submit/commit patches, but I want to make sure I don't do anything objectionable to the community * This is probably user error, but I'm getting: \[ERROR\] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack (unpack) on project tika-text-module: Unable to find artifact. Could not find artifact org.apache.tika:tika-test-resources:jar:tests:2.0-SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots) * Perhaps rename artifact names in parser sub-components to include "Parser(s?)", e.g. Apache Tika Parser Advanced Module so that the names sort more clearly (at least in the maven window in Intellij)? * Perhaps add "parser(s?) to the artifactId, e.g. tika-parser-cad-module * Perhaps lowercase names in parser-subcomponents so that they're inline with legacy: "Apache Tika parser advanced module" * Pkcs7Parser ... should that be under advanced...or somewhere else ...own crypto package? * iwork ...should we move that to office? * tika-test-resources...should we move TikaTest into that and change the name to tika-test? I have a vague memory of wanting to carve out a separate test package earlier and adding TikaTest and something else... * OutlookPSTParser...move that to office? * Does MBox belong in web? Not sure where to put it? * Move CommonsDigester to core _if_ we're willing to add a dependency on commons-digest into core? * Move Activator to tika-bundle? * Move pot to multimedia or add tika-parsers-multimedia-advanced-module? * Move geo.topic to "advanced"...perhaps we rename "advanced" to ner? * Move ctakes to "advanced/ner"? * Collapse web and text? Again, this is fantastic. Thank you! > Tika 2.0 - Create Initial Parser Modules > - > > Key: TIKA-1824 > URL: https://issues.apache.org/jira/browse/TIKA-1824 > Project: Tika > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Bob Paulin >Assignee: Bob Paulin > > Create initial break down of parser modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
tika-2.x - Build # 1 - Failure
The Apache Jenkins build system has built tika-2.x (build #1) Status: Failure Check console output at https://builds.apache.org/job/tika-2.x/1/ to view the results.
[jira] [Resolved] (TIKA-1825) Add 2.x branch to Hudson
[ https://issues.apache.org/jira/browse/TIKA-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney resolved TIKA-1825. Resolution: Fixed Assignee: Lewis John McGibbney Done https://builds.apache.org/view/Tika/job/tika-2.x/ Thanks > Add 2.x branch to Hudson > > > Key: TIKA-1825 > URL: https://issues.apache.org/jira/browse/TIKA-1825 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Assignee: Lewis John McGibbney > > Would it make sense to add the 2.x branch to our Hudson builds...or have we > already done this? > [~lewismc], do I remember correctly that you last fixed our Hudson builds? > I have no idea how to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
tika-2.x - Build # 2 - Still Failing
The Apache Jenkins build system has built tika-2.x (build #2) Status: Still Failing Check console output at https://builds.apache.org/job/tika-2.x/2/ to view the results.
[jira] [Commented] (TIKA-1824) Tika 2.0 - Create Initial Parser Modules
[ https://issues.apache.org/jira/browse/TIKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086784#comment-15086784 ] Hudson commented on TIKA-1824: -- FAILURE: Integrated in tika-2.x #3 (See [https://builds.apache.org/job/tika-2.x/3/]) TIKA-1824 - Disable Dependency Reduced POM in tika-parsers. This is causing dependencies not to get pulled into tika-app. (bob: [http://svn.apache.org/viewvc/tika/trunk/?view=rev=1723453]) * trunk/tika-parsers/pom.xml > Tika 2.0 - Create Initial Parser Modules > - > > Key: TIKA-1824 > URL: https://issues.apache.org/jira/browse/TIKA-1824 > Project: Tika > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Bob Paulin >Assignee: Bob Paulin > > Create initial break down of parser modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
tika-2.x - Build # 3 - Still Failing
The Apache Jenkins build system has built tika-2.x (build #3) Status: Still Failing Check console output at https://builds.apache.org/job/tika-2.x/3/ to view the results.
[jira] [Commented] (TIKA-1824) Tika 2.0 - Create Initial Parser Modules
[ https://issues.apache.org/jira/browse/TIKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086735#comment-15086735 ] Hudson commented on TIKA-1824: -- FAILURE: Integrated in tika-2.x #2 (See [https://builds.apache.org/job/tika-2.x/2/]) TIKA-1824 - Added tika-test-resources to module list so it is built. (bob: [http://svn.apache.org/viewvc/tika/trunk/?view=rev=1723446]) * trunk/pom.xml > Tika 2.0 - Create Initial Parser Modules > - > > Key: TIKA-1824 > URL: https://issues.apache.org/jira/browse/TIKA-1824 > Project: Tika > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Bob Paulin >Assignee: Bob Paulin > > Create initial break down of parser modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TIKA-1824) Tika 2.0 - Create Initial Parser Modules
[ https://issues.apache.org/jira/browse/TIKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086170#comment-15086170 ] Bob Paulin commented on TIKA-1824: -- A bit in a rush today but the answer to bullet one is you need to build the tika-test-resources project first before anything else. I think we should add tika-test-resources as a module to a parent pom so this happens automatically. Otherwise I'm sure many will hit this issue! > Tika 2.0 - Create Initial Parser Modules > - > > Key: TIKA-1824 > URL: https://issues.apache.org/jira/browse/TIKA-1824 > Project: Tika > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Bob Paulin >Assignee: Bob Paulin > > Create initial break down of parser modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
