You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2013/01/20 17:22:12 UTC
[jira] [Updated] (COCOON-2316) Unable to build Cocoon trunk
[ https://issues.apache.org/jira/browse/COCOON-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated COCOON-2316:
-------------------------------------------
Fix Version/s: (was: 2.2)
2.2.1
> Unable to build Cocoon trunk
> ----------------------------
>
> Key: COCOON-2316
> URL: https://issues.apache.org/jira/browse/COCOON-2316
> Project: Cocoon
> Issue Type: Improvement
> Components: * Cocoon Core, - Build System: Maven, Blocks: (Undefined)
> Affects Versions: 2.2, 2.2.1
> Reporter: Ballu Chegu
> Assignee: Francesco Chicchiriccò
> Priority: Blocker
> Fix For: 2.2.1
>
>
> Dear Cocoon developers,
> We have built a solution on top of Cocoon 2.1. We noticed there are lots features added in 2.2 and most of our custom code can be removed with out-of-the-box capabilities built into 2.2. We tried dowloading Cocoon 2.2 code from the trunk and build. Noticing lot of version related issues with dependencies. There are references to old SNAPSHOT versions, Release Candidate versions and non-existing versions for some of the dependencies. We resolved 5 to 6 of them. But felt there should be a better way to resolve this because of all developers spread across the cities/continents be referring to a repository that would have all those dependencies.
> Please let us know which is the right repository to point to. Currently we are pointing to
>
> the specified remote repositories:
> ibiblioEuropeanMirror (http://mirrors.dotsrc.org/maven2),
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> gkossakowski-maven2 (http://people.apache.org/~gkossakowski/maven2/repository)
> Your response will be greatly appreciated.
> Sincerely,
> Ballu
--
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