[
https://issues.apache.org/jira/browse/CONNECTORS-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476053#comment-13476053
]
Karl Wright commented on CONNECTORS-555:
----------------------------------------
Huh, the problem is that the dependency is calling for activation 1.0.2, and
that is apparently no longer available from the alfresco maven repository.
Since 1.1.1, at least, is available from the Apache Maven repository, we could
in theory override the dependency and allow it to use 1.1.1. Or, we could
download 1.0.2 and push it into the local repository. Would that work?
> Alfresco maven build is broken
> ------------------------------
>
> Key: CONNECTORS-555
> URL: https://issues.apache.org/jira/browse/CONNECTORS-555
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
> Affects Versions: ManifoldCF 1.0, ManifoldCF 1.0.1, ManifoldCF 1.1
> Reporter: Karl Wright
> Assignee: Piergiorgio Lucidi
> Fix For: ManifoldCF 1.0.1
>
>
> The maven build steps:
> {code}
> mvn-bootstrap
> mvn clean -DskipTests install
> {code}
> fail in the following way:
> {code}
> [ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
> reso
> lve dependencies for project
> org.apache.manifoldcf:mcf-alfresco-connector:jar:1.
> 1-SNAPSHOT: Could not find artifact javax.activation:activation:jar:1.0.2 in
> alf
> resco-release
> (https://artifacts.alfresco.com/nexus/content/repositories/release
> s) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> swit
> ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> rea
> d the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
> lutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :mcf-alfresco-connector
> C:\wip\mcf\trunk>
> {code}
> It looks like there is a missing dependency we may need. I think
> activation.jar was there before, not sure what happened to it.
--
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
