[jira] [Issue Comment Edited] (CONNECTORS-224) OpenSearchServer connector
[ https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082034#comment-13082034 ] Karl Wright edited comment on CONNECTORS-224 at 8/10/11 1:02 AM: - When I try to crawl using the connector and the connection parameters are bogus, the crawl proceeds a while and does not seem to notice that there is no actual output server present. Very shortly thereafter, after a few hundred files, the whole system runs out of memory: >> agents process ran out of memory - shutting down java.lang.OutOfMemoryError: Java heap space at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:133) at java.lang.StringCoding.decode(StringCoding.java:173) at java.lang.StringCoding.decode(StringCoding.java:185) at java.lang.String.(String.java:570) at java.lang.String.(String.java:593) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Index.getXML(OpenSearchServerIndex.java:58) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Index.(OpenSearchServerIndex.java:28) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Connector.addOrReplaceDocument(OpenSearchServerConnector.java:153) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.ad dOrReplaceDocument(IncrementalIngester.java:1499) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.pe rformIngestion(IncrementalIngester.java:469) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.do cumentIngest(IncrementalIngester.java:364) at org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ing estDocument(WorkerThread.java:1587) at org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.pro cessDocuments(FileConnector.java:283) at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.proc essDocuments(BaseRepositoryConnector.java:423) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja va:564) << I haven't looked at the code, but clearly the connector is trying to queue up documents in memory for some reason. If that's what's going on, that's never going to fly because there cannot possibly be proper feedback of error conditions etc. was (Author: kwri...@metacarta.com): When I try to crawl using the server and the connection is bogus, the crawl proceeds a while and does not seem to notice that there is no output server. Very shortly thereafter, the whole system runs out of memory: >> agents process ran out of memory - shutting down java.lang.OutOfMemoryError: Java heap space at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:133) at java.lang.StringCoding.decode(StringCoding.java:173) at java.lang.StringCoding.decode(StringCoding.java:185) at java.lang.String.(String.java:570) at java.lang.String.(String.java:593) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Index.getXML(OpenSearchServerIndex.java:58) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Index.(OpenSearchServerIndex.java:28) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Connector.addOrReplaceDocument(OpenSearchServerConnector.java:153) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.ad dOrReplaceDocument(IncrementalIngester.java:1499) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.pe rformIngestion(IncrementalIngester.java:469) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.do cumentIngest(IncrementalIngester.java:364) at org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ing estDocument(WorkerThread.java:1587) at org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.pro cessDocuments(FileConnector.java:283) at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.proc essDocuments(BaseRepositoryConnector.java:423) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja va:564) << I haven't looked at the code, but clearly the connector is trying to queue up documents in memory for some reason. If that's what's going on, that's never going to fly because there cannot possibly be proper feedback of error conditions etc. > OpenSearchServer connector > -- > > Key: CONNECTORS-224 > URL: https://issues.apache.org/jira/browse/CONNECTORS-224 > Project: ManifoldCF > Issue Type: New Feature > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.3 >Reporter: Emmanuel Keller >As
[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector
[ https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082034#comment-13082034 ] Karl Wright commented on CONNECTORS-224: When I try to crawl using the server and the connection is bogus, the crawl proceeds a while and does not seem to notice that there is no output server. Very shortly thereafter, the whole system runs out of memory: >> agents process ran out of memory - shutting down java.lang.OutOfMemoryError: Java heap space at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:133) at java.lang.StringCoding.decode(StringCoding.java:173) at java.lang.StringCoding.decode(StringCoding.java:185) at java.lang.String.(String.java:570) at java.lang.String.(String.java:593) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Index.getXML(OpenSearchServerIndex.java:58) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Index.(OpenSearchServerIndex.java:28) at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer Connector.addOrReplaceDocument(OpenSearchServerConnector.java:153) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.ad dOrReplaceDocument(IncrementalIngester.java:1499) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.pe rformIngestion(IncrementalIngester.java:469) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.do cumentIngest(IncrementalIngester.java:364) at org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ing estDocument(WorkerThread.java:1587) at org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.pro cessDocuments(FileConnector.java:283) at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.proc essDocuments(BaseRepositoryConnector.java:423) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja va:564) << I haven't looked at the code, but clearly the connector is trying to queue up documents in memory for some reason. If that's what's going on, that's never going to fly because there cannot possibly be proper feedback of error conditions etc. > OpenSearchServer connector > -- > > Key: CONNECTORS-224 > URL: https://issues.apache.org/jira/browse/CONNECTORS-224 > Project: ManifoldCF > Issue Type: New Feature > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.3 >Reporter: Emmanuel Keller >Assignee: Karl Wright > Labels: OpenSearchServer, connector, outputconnector > Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, > oss-mfc-dev.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Provide an output connector for > [OpenSearchServer|http://www.open-search-server.com]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector
[ https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082030#comment-13082030 ] Karl Wright commented on CONNECTORS-224: The Parameters tab also appears to have no Javascript correctness checking whatsoever. I can specify a blank URL and a blank index name and it still allows me to save it. This too should be addressed. > OpenSearchServer connector > -- > > Key: CONNECTORS-224 > URL: https://issues.apache.org/jira/browse/CONNECTORS-224 > Project: ManifoldCF > Issue Type: New Feature > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.3 >Reporter: Emmanuel Keller >Assignee: Karl Wright > Labels: OpenSearchServer, connector, outputconnector > Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, > oss-mfc-dev.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Provide an output connector for > [OpenSearchServer|http://www.open-search-server.com]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector
[ https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082029#comment-13082029 ] Karl Wright commented on CONNECTORS-224: Trying out the connector, it appears that the connection check() method is not doing anything, as I get back "Connection working" even with completely bogus parameters: View Output Connection Status Name: testDescription: Connection type:OpenSearchServerMax connections:10 Server Location (URL): http://localhost:8080/ Index name: index User name: foo API Key:bar Connection status: Connection working This should be fixed, obviously. > OpenSearchServer connector > -- > > Key: CONNECTORS-224 > URL: https://issues.apache.org/jira/browse/CONNECTORS-224 > Project: ManifoldCF > Issue Type: New Feature > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.3 >Reporter: Emmanuel Keller >Assignee: Karl Wright > Labels: OpenSearchServer, connector, outputconnector > Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, > oss-mfc-dev.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Provide an output connector for > [OpenSearchServer|http://www.open-search-server.com]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector
[
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082027#comment-13082027
]
Karl Wright commented on CONNECTORS-224:
I just discovered that this connector won't build under jdk 1.5, which is a
problem since ManifoldCF has not yet moved to a minimum Java version of 1.6.
These are the errors I get:
>>
compile-connector:
[mkdir] Created dir: C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\b
uild\connector\classes
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\build.xml:10:
warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last;
set to false for repeatable builds
[javac] Compiling 6 source files to C:\wip\mcf\CONNECTORS-224\connectors\ope
nsearchserver\build\connector\classes
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:8: package javax.xml.stream does not exist
[javac] import javax.xml.stream.XMLOutputFactory;
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:9: package javax.xml.stream does not exist
[javac] import javax.xml.stream.XMLStreamException;
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:10: package javax.xml.stream does not exist
[javac] import javax.xml.stream.XMLStreamWriter;
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:42: cannot find symbol
[javac] symbol : class XMLStreamException
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] throws XMLStreamException, IOException {
[javac]^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:34: cannot find symbol
[javac] symbol : class XMLStreamException
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] } catch (XMLStreamException e) {
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:44: cannot find symbol
[javac] symbol : class XMLOutputFactory
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] XMLOutputFactory factory = XMLOutputFactory.newInstance(
);
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:44: cannot find symbol
[javac] symbol : variable XMLOutputFactory
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] XMLOutputFactory factory = XMLOutputFactory.newInstance(
);
[javac]^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:46: cannot find symbol
[javac] symbol : class XMLStreamWriter
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] XMLStreamWriter writer = factory.createXMLStreamWriter(s
w);
[javac] ^
[javac] 8 errors
BUILD FAILED
<<
The XML parser that is used currently throughout ManifoldCF, and is thus
available, is a modified version of xerces - you will see it under the "lib"
directory.
This does NOT affect maven, because maven is at minimum a 1.6 build already.
It will affect the ability, however, to include the opensearchserver connector
in the shipping packages. So it seems to me that you have three choices here:
(1) wait until we officially adopt Java 1.6 as the minimum standard java
version before merging this into trunk; (2) modify your code so that it does
not use the 1.6 features; or (3) change the conditional compilation in the ant
build so that it won't even try to compile the connector under JDK 1.5. Please
let me know what you prefer to do.
> OpenSearchServer connector
> --
>
>
[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector
[ https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082021#comment-13082021 ] Karl Wright commented on CONNECTORS-224: I checked in and tested Maven build files in the branch. > OpenSearchServer connector > -- > > Key: CONNECTORS-224 > URL: https://issues.apache.org/jira/browse/CONNECTORS-224 > Project: ManifoldCF > Issue Type: New Feature > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.3 >Reporter: Emmanuel Keller >Assignee: Karl Wright > Labels: OpenSearchServer, connector, outputconnector > Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, > oss-mfc-dev.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Provide an output connector for > [OpenSearchServer|http://www.open-search-server.com]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Does anyone know enough about maven to answer one simple question?
Hi Karl,
this message just to recap the informations we have talked about during the
chat session.
Here we have an execution of tests based on some Maven artifacts that must
be generated using an execution of the install phase of Maven.
Maven has it own lifecycle that consists of phases that are executed in a
specific order, you can see the complete list here [1].
This means that to allow in our process to have the availability of the new
artifacts, before executing tests, we need to execute maven with the
following command:
mvn clean install
The install phase of Maven, as you can see in the page [1], include the
execution of generate-resource phase and test phase, so I think that this is
the correct way to build and execute tests for the project.
[1] -
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference
2011/8/9 Karl Wright
> A related question: when I run "mvn clean test" I get the following:
>
> >>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:
> 2.1:copy (copy-war) on project mcf-jettyrunner: Error copying artifact from
> C:\w
> ip\mcf\trunk\framework\api-service\target\classes to
> C:\wip\mcf\trunk\framework\
> jetty-runner\target\dependency\classes: File
> C:\wip\mcf\trunk\framework\api-serv
> ice\target\classes does not exist -> [Help 1]
> <<
>
> This is coming from mcf-jettyrunner, which has dependencies on the
> api-service, crawler-ui, and authority-service wars. These components
> seem to build properly:
>
> >>
> [INFO] ManifoldCF SUCCESS [0.003s]
> [INFO] ManifoldCF - Framework SUCCESS [0.001s]
> [INFO] ManifoldCF - Framework - Core . SUCCESS [2.864s]
> [INFO] ManifoldCF - Framework - UI Core .. SUCCESS [0.678s]
> [INFO] ManifoldCF - Framework - Agents ... SUCCESS
> [15.180s]
> [INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS
> [33.034s]
> [INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [0.832s]
> [INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [2.039s]
> [INFO] ManifoldCF - Framework - Authority Service SUCCESS [0.114s]
> [INFO] ManifoldCF - Framework - API Service .. SUCCESS [0.083s]
> [INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [0.088s]
> [INFO] ManifoldCF - Connectors ... SUCCESS [0.001s]
> [INFO] ManifoldCF - Connectors - Active Directory SUCCESS [0.815s]
> [INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS
> [26.844s]
> [INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.093s]
> [INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [1.028s]
> [INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.362s]
> [INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [0.643s]
> [INFO] ManifoldCF - Connectors - Null Output . SUCCESS [0.566s]
> [INFO] ManifoldCF - Connectors - RSS . SUCCESS [1.401s]
> [INFO] ManifoldCF - Connectors - Solr SUCCESS [1.037s]
> [INFO] ManifoldCF - Connectors - Web . SUCCESS [1.624s]
> [INFO] ManifoldCF - Connectors - CMIS SUCCESS
> [32.040s]
> [INFO] ManifoldCF - Framework - Jetty Runner . FAILURE [0.466s]
> <<
>
> ... but they don't seem to be available in the repository after they
> are built during the test run. Yet the dependencies don't stop the
> tests from trying to execute and copy those wars from the repository.
> Can anyone enlighten me as to why this might be?
>
> Karl
>
> On Tue, Aug 9, 2011 at 8:33 AM, Karl Wright wrote:
> > The maven files use the maven-dependency-plugin to copy wars out of
> > the repository into a place where testing and execution code can find
> > them. This currently requires a build-time dependency, but in fact
> > the wars are not needed unless a test is being run. I would like to
> > somehow set the scope of the code that copies the wars so that the
> > copy only takes place when "test" or "runtime" is the scope. Is there
> > any way to do that?
> >
> > Here's the plugin invocation:
> >
> >
> >maven-dependency-plugin
> >
> >
> >copy-war
> >generate-resources
> >
> > copy
> >
> >
> > target/dependency
> >
> >
> > org.apache.chemistry.opencmis
> >
> > chemistry-opencmis-server-inmemory-war
> > 0.5.0-SNAPSHOT
> > war
> > false
> >
> >
> > ${project.groupId}
> > mcf-api-service
> > ${project.version}
> > war
> > false
> >
> >
> >
Re: Does anyone know enough about maven to answer one simple question?
A related question: when I run "mvn clean test" I get the following:
>>
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:
2.1:copy (copy-war) on project mcf-jettyrunner: Error copying artifact from C:\w
ip\mcf\trunk\framework\api-service\target\classes to C:\wip\mcf\trunk\framework\
jetty-runner\target\dependency\classes: File C:\wip\mcf\trunk\framework\api-serv
ice\target\classes does not exist -> [Help 1]
<<
This is coming from mcf-jettyrunner, which has dependencies on the
api-service, crawler-ui, and authority-service wars. These components
seem to build properly:
>>
[INFO] ManifoldCF SUCCESS [0.003s]
[INFO] ManifoldCF - Framework SUCCESS [0.001s]
[INFO] ManifoldCF - Framework - Core . SUCCESS [2.864s]
[INFO] ManifoldCF - Framework - UI Core .. SUCCESS [0.678s]
[INFO] ManifoldCF - Framework - Agents ... SUCCESS [15.180s]
[INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [33.034s]
[INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [0.832s]
[INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [2.039s]
[INFO] ManifoldCF - Framework - Authority Service SUCCESS [0.114s]
[INFO] ManifoldCF - Framework - API Service .. SUCCESS [0.083s]
[INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [0.088s]
[INFO] ManifoldCF - Connectors ... SUCCESS [0.001s]
[INFO] ManifoldCF - Connectors - Active Directory SUCCESS [0.815s]
[INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [26.844s]
[INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.093s]
[INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [1.028s]
[INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.362s]
[INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [0.643s]
[INFO] ManifoldCF - Connectors - Null Output . SUCCESS [0.566s]
[INFO] ManifoldCF - Connectors - RSS . SUCCESS [1.401s]
[INFO] ManifoldCF - Connectors - Solr SUCCESS [1.037s]
[INFO] ManifoldCF - Connectors - Web . SUCCESS [1.624s]
[INFO] ManifoldCF - Connectors - CMIS SUCCESS [32.040s]
[INFO] ManifoldCF - Framework - Jetty Runner . FAILURE [0.466s]
<<
... but they don't seem to be available in the repository after they
are built during the test run. Yet the dependencies don't stop the
tests from trying to execute and copy those wars from the repository.
Can anyone enlighten me as to why this might be?
Karl
On Tue, Aug 9, 2011 at 8:33 AM, Karl Wright wrote:
> The maven files use the maven-dependency-plugin to copy wars out of
> the repository into a place where testing and execution code can find
> them. This currently requires a build-time dependency, but in fact
> the wars are not needed unless a test is being run. I would like to
> somehow set the scope of the code that copies the wars so that the
> copy only takes place when "test" or "runtime" is the scope. Is there
> any way to do that?
>
> Here's the plugin invocation:
>
>
> maven-dependency-plugin
>
>
> copy-war
> generate-resources
>
> copy
>
>
> target/dependency
>
>
> org.apache.chemistry.opencmis
>
> chemistry-opencmis-server-inmemory-war
> 0.5.0-SNAPSHOT
> war
> false
>
>
> ${project.groupId}
> mcf-api-service
> ${project.version}
> war
> false
>
>
> ${project.groupId}
> mcf-authority-service
> ${project.version}
> war
> false
>
>
> ${project.groupId}
> mcf-crawler-ui
> ${project.version}
> war
> false
>
>
>
>
>
>
>
>
> Karl
>
Does anyone know enough about maven to answer one simple question?
The maven files use the maven-dependency-plugin to copy wars out of
the repository into a place where testing and execution code can find
them. This currently requires a build-time dependency, but in fact
the wars are not needed unless a test is being run. I would like to
somehow set the scope of the code that copies the wars so that the
copy only takes place when "test" or "runtime" is the scope. Is there
any way to do that?
Here's the plugin invocation:
maven-dependency-plugin
copy-war
generate-resources
copy
target/dependency
org.apache.chemistry.opencmis
chemistry-opencmis-server-inmemory-war
0.5.0-SNAPSHOT
war
false
${project.groupId}
mcf-api-service
${project.version}
war
false
${project.groupId}
mcf-authority-service
${project.version}
war
false
${project.groupId}
mcf-crawler-ui
${project.version}
war
false
Karl
