search cq related information on adobe, day, jackrabbit, sling and other sites
We would like to hear from you. Suggestions to improve cqblueprints.com are very welcome. Please contact us.
We would like to hear from you. Suggestions to improve cqblueprints.com are very welcome. Please contact us.
Loading
Changes for document Using Nexus as a Maven Repository for CQ Team Development
Last modified by Craig S. Dickson on 2012/04/22 00:19
From version 15.3
edited by Craig S. Dickson
on 2012/04/22 00:16
on 2012/04/22 00:16
To version 16.1
edited by Craig S. Dickson
on 2012/04/22 00:19
on 2012/04/22 00:19
Change comment: There is no comment for this version
| Content changes |
|---|
[[image:newrepo.png||style="display: block; margin-left: auto; margin-right: auto;"]] [[image:newrepo.png]] [[image:publicrepo.png]] [[image:publicrepo.png||style="display: block; margin-left: auto; margin-right: auto;"]] ** In the above screen shot when configuring the ##public## group repository, we have placed the Adobe CQ proxy above Maven Central. This means that the artifacts in the Adobe CQ proxy will be given priority over the ones in Maven Central. This is the correct configuration for CQ projects. However, if you or your team also work on non-CQ projects in addition to CQ projects, you will need to evaluate if this configuration works for you. |
Quick Links
Need help with your Adobe CQ 5.4 and 5.5 implementation? We're here to help. Contact us at info@headwire.com
Jumpstart your CQ project - consider the twitter bootstrap implementation with CQ providing a wysiwyg template editor and base components for an every day website.