[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359700#comment-15359700 ] Chris A. Mattmann commented on NUTCH-1371: -- Sounds fantastic! CC [~ndouba] > Replace Ivy with Maven Ant tasks > > > Key: NUTCH-1371 > URL: https://issues.apache.org/jira/browse/NUTCH-1371 > Project: Nutch > Issue Type: Improvement > Components: build >Affects Versions: 1.7, 2.2.1 >Reporter: Julien Nioche >Assignee: Lewis John McGibbney > Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, > NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch > > > We might move to Maven altogether but a good intermediate step could be to > rely on the maven ant tasks for managing the dependencies. Ivy does a good > job but we need to have a pom file anyway for publishing the artefacts which > means keeping the pom.xml and ivy.xml contents in sync. Most devs are also > more familiar with Maven, and it is well integrated in IDEs. Going the > ANT+MVN way also means that we don't have to rewrite the whole building > process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359556#comment-15359556 ] Thamme Gowda commented on NUTCH-1371: - [~jnioche] Yes, we have a plan to convert all plugins to maven artifacts and then publish them to maven central repo. > Replace Ivy with Maven Ant tasks > > > Key: NUTCH-1371 > URL: https://issues.apache.org/jira/browse/NUTCH-1371 > Project: Nutch > Issue Type: Improvement > Components: build >Affects Versions: 1.7, 2.2.1 >Reporter: Julien Nioche >Assignee: Lewis John McGibbney > Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, > NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch > > > We might move to Maven altogether but a good intermediate step could be to > rely on the maven ant tasks for managing the dependencies. Ivy does a good > job but we need to have a pom file anyway for publishing the artefacts which > means keeping the pom.xml and ivy.xml contents in sync. Most devs are also > more familiar with Maven, and it is well integrated in IDEs. Going the > ANT+MVN way also means that we don't have to rewrite the whole building > process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359504#comment-15359504 ] Julien Nioche commented on NUTCH-1371: -- None whatsoever [~lewismc]. Maybe mark it as duplicate and link to the new issue. Out of curiosity are you planning to revamp the plugin mechanism as well? > Replace Ivy with Maven Ant tasks > > > Key: NUTCH-1371 > URL: https://issues.apache.org/jira/browse/NUTCH-1371 > Project: Nutch > Issue Type: Improvement > Components: build >Affects Versions: 1.7, 2.2.1 >Reporter: Julien Nioche >Assignee: Lewis John McGibbney > Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, > NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch > > > We might move to Maven altogether but a good intermediate step could be to > rely on the maven ant tasks for managing the dependencies. Ivy does a good > job but we need to have a pom file anyway for publishing the artefacts which > means keeping the pom.xml and ivy.xml contents in sync. Most devs are also > more familiar with Maven, and it is well integrated in IDEs. Going the > ANT+MVN way also means that we don't have to rewrite the whole building > process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359367#comment-15359367 ] Lewis John McGibbney commented on NUTCH-1371: - Hi [~jnioche] and everyone else. [~thammegowda] and me are working on implementing a Maven build. I therefore propose to close this issue as Won't resolve. Any objections? > Replace Ivy with Maven Ant tasks > > > Key: NUTCH-1371 > URL: https://issues.apache.org/jira/browse/NUTCH-1371 > Project: Nutch > Issue Type: Improvement > Components: build >Affects Versions: 1.7, 2.2.1 >Reporter: Julien Nioche >Assignee: Lewis John McGibbney > Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, > NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch > > > We might move to Maven altogether but a good intermediate step could be to > rely on the maven ant tasks for managing the dependencies. Ivy does a good > job but we need to have a pom file anyway for publishing the artefacts which > means keeping the pom.xml and ivy.xml contents in sync. Most devs are also > more familiar with Maven, and it is well integrated in IDEs. Going the > ANT+MVN way also means that we don't have to rewrite the whole building > process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144637#comment-14144637 ] Viacheslav Dobromyslov commented on NUTCH-1371: --- It's my dream to be able to build Nutch with Maven. Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.10 Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14144970#comment-14144970 ] Chris A. Mattmann commented on NUTCH-1371: -- someday...Nutch...Maven..winning Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.10 Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13890616#comment-13890616 ] Julien Nioche commented on NUTCH-1371: -- Hi Talat bq. Actually I have some problems with ant+ivy style. Firstly, when I change a configuration file I always have to run ant runtime target. that has nothing to do with Ant+ivy itself. It is just that you need to rebuild the runtime environments if you want the content of conf to be there. You can edit the content of runtime/local/conf directly if you want your changes to be operational without recompiling bq. In addition to this, When I change a build dependency, I always have to run ant eclipse target for working on the IDE. At the present dependencies are managed from the built files. I think when we migrate maven, they will be solved. How do you solve this type of problems ? use IvyDE in Eclipse. it will use the ivy deps file in the same way as the Maven plugin does Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864133#comment-13864133 ] Talat UYARER commented on NUTCH-1371: - Is there any opinion ? Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864168#comment-13864168 ] Lewis John McGibbney commented on NUTCH-1371: - Hi [~talat] that sounds good to me, I have no objection. Are you proposing to follow [~jnioche] suggestion RE the patch he attached? Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864182#comment-13864182 ] Talat UYARER commented on NUTCH-1371: - Hi [~lewismc], Different from the [~jnioche]'s suggestion, I want to learn why do we 'not' migrate Nutch completely as Maven project ? If it wont be a problem to migrate completely, I am volunteer to do it. Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864189#comment-13864189 ] Lewis John McGibbney commented on NUTCH-1371: - I think for trunk this would not be a problem. For 2.x we would need to write a gora-maven-plugin which could be included in pom.xml. This is in planning but not implemented yet. If you are ready to migrate trunk code to maven lifecycle management then I would back this effort 100% Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864190#comment-13864190 ] Julien Nioche commented on NUTCH-1371: -- Talat, Moving to Maven altogether won't be a problem only if all the functionalities of the ANT+IVY build are preserved. For instance we'd need an elegant way of dealing with the Nutch plugins with Maven, etc... Not a high priority task in my views, but if you want to provide a patch, I'll be happy to review it Thanks Julien Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864215#comment-13864215 ] Talat UYARER commented on NUTCH-1371: - Hi [~jnioche], Actually I have some problems with ant+ivy style. Firstly, when I change a configuration file I always have to run ant runtime target. In addition to this, When I change a build dependency, I always have to run ant eclipse target for working on the IDE. At the present dependencies are managed from the built files. I think when we migrate maven, they will be solved. How do you solve this type of problems ? Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862941#comment-13862941 ] Talat UYARER commented on NUTCH-1371: - May I learn Why do we completely migrate to Maven ? If you think it's ok I'm up for this task. Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797729#comment-13797729 ] Julien Nioche commented on NUTCH-1371: -- Hi Talat. That would be great, the latest one is just about the plugins and can be tested separately from the initial one. Ideally if we could replace all the ivy files from the plugins with a pom equivalent, that would be quite an improvement. Thanks Julien Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371.patch, NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796626#comment-13796626 ] Julien Nioche commented on NUTCH-1371: -- Does anyone have a bit of time to test this stuff? Would be nice to simplify the build architecture and get rid of Ivy if we can Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371.patch, NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797070#comment-13797070 ] Talat UYARER commented on NUTCH-1371: - I can test Julien. I am intersted in this issue. Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Affects Versions: 1.7, 2.2.1 Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.8, 2.4 Attachments: NUTCH-1371.patch, NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614414#comment-13614414 ] Lewis John McGibbney commented on NUTCH-1371: - Hi Roland. I think the ivy directory should be removed here? Additionally there are other discrepancies here such as the accuracy of pom.xml for truly reflecting an accurate representation of current ivy.xml (including exclusions, etc). Finally, every plugin needs to be addressed does they not? Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.7, 2.2 Attachments: NUTCH-1371.patch, NUTCH-1371-r1461140.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614447#comment-13614447 ] Roland von Herget commented on NUTCH-1371: -- Hi Lewis, the patch is the original one from Julien, it's just a version which applies cleanly against 2.x-trunk now. So, this is just a start, and does nothing new about dependencies. I just merged it into the actual version and I didn't want to loose this, so I posted it here. Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.7, 2.2 Attachments: NUTCH-1371.patch, NUTCH-1371-r1461140.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614459#comment-13614459 ] Lewis John McGibbney commented on NUTCH-1371: - Thank you so much Roland. Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.7, 2.2 Attachments: NUTCH-1371.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552513#comment-13552513 ] Julien Nioche commented on NUTCH-1371: -- Hi Lewis. Yep the plugins need to be managed in the same way + cleanup the ivy stuff etc... Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Reporter: Julien Nioche Assignee: Lewis John McGibbney Fix For: 1.7, 2.2 Attachments: NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
[ https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552365#comment-13552365 ] Lewis John McGibbney commented on NUTCH-1371: - Hi Julien. So what is the plan here? I know that this patch is just a start. It does not take into consideration the plugin dependencies which I suppose should also be managed via Maven. In addition, the ivy directory should ideally be removed. The maven-ant-tasks jar can then be added to out lib directory. Replace Ivy with Maven Ant tasks Key: NUTCH-1371 URL: https://issues.apache.org/jira/browse/NUTCH-1371 Project: Nutch Issue Type: Improvement Components: build Reporter: Julien Nioche Fix For: 1.7, 2.2 Attachments: NUTCH-1371.patch We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
