[jira] [Commented] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13109390#comment-13109390 ] Alex Ott commented on CONNECTORS-258: - Some of dependencies (hsqldb, jcifs) already exist in central maven repository - you only need to ask developers to upload latest versions. There is guide on submitting jars to central repository - https://maven.apache.org/guides/mini/guide-central-repository-upload.html, there are some requirements to jars, described separately (https://docs.sonatype.org/display/Repository/Central+Sync+Requirements). Regarding modified versions of xerces and httpclient - do patches MCF-specific, or they are already submitted to upstream? If already submitted, then we can use SNAPSHOT versions of them, taking them from Apache repository pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Ott updated CONNECTORS-258: Attachment: mvn-bootstrap.sh Script to prepare clean system for maven build pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Attachments: mvn-bootstrap.sh Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions
[ https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13108894#comment-13108894 ] Alex Ott commented on CONNECTORS-223: - I'm not sure, that packages not available at Maven central, or other repositories, should be used in pom's - in Tika project another approach is used - all needed jars are promoted to repository first, and only after it are used... Tests in project hierarchy do not adhere to maven conventions - Key: CONNECTORS-223 URL: https://issues.apache.org/jira/browse/CONNECTORS-223 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: CONNECTORS-223.patch, CONNECTORS-223_forkMode.patch, CONNECTORS-223_jetty-runner.patch, CONNECTORS-223_tests.patch, test_reset.patch Maven expects unit tests under .../src/test/java, and root-level project tests under tests/xxx/src/test/java (or equivalent, along with their own pom.xml at tests and tests/xxx). This is basically compatible with the ant build except in location detail. The proposal is to move stuff around to make the tests work with maven. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13108928#comment-13108928 ] Alex Ott commented on CONNECTORS-258: - another possibility - setup separate maven repository and server missing jars from it pom.xml refers to jars not available in public repositories --- Key: CONNECTORS-258 URL: https://issues.apache.org/jira/browse/CONNECTORS-258 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.4 Environment: all supported platforms Reporter: Alex Ott Priority: Minor Labels: maven Maven's pom.xmls refers to jars that aren't available in public repositories, as maven central, apache repository, etc. This includes: - com.bitmechanic:jdbcpool - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 is available right now) I think, that ManifoldCF should adopt the same approach as other Apache projects, like Tika, when all needed jars first promoted to public repositories, and only after that, they are used as dependency... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
