Open GoogleCodeExporter opened 8 years ago
I thought that those repositories were necessary to locate the parent POM
(alfresco-parent-sdk); if archetype-generated projects don't point to the
public/private group of Alfresco Nexus, where they get the parent from during
the first build?
Original comment by mauri...@session.it
on 27 Nov 2013 at 9:19
Yeah Mau, Peter is suggesting to have a doc page to add the Alfresco repo in
the settings, and so not need to have in the POMs.
I don't like this solution and I think the real solution is to push the
Alfresco Maven SDK to Maven Central, so that then we can inherit any repository
from there.
I'll look into starting the process with Sonatype as per
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide.
Original comment by colum...@gmail.com
on 27 Nov 2013 at 1:29
Note: documenting the required changes to ~/.m2/settings.xml is standard
practice for commercial vendors with artifact repository-based SDKs (e.g. Jive).
Original comment by pmo...@gmail.com
on 27 Nov 2013 at 3:44
I have opened https://issues.sonatype.org/browse/OSSRH-7948 to deploy the SDK
to Maven Central.
Original comment by colum...@gmail.com
on 27 Nov 2013 at 6:55
Original comment by colum...@gmail.com
on 27 Nov 2013 at 6:57
Original comment by colum...@gmail.com
on 27 Nov 2013 at 6:57
Original comment by colum...@gmail.com
on 18 Jul 2014 at 12:05
Original issue reported on code.google.com by
pmo...@gmail.com
on 26 Nov 2013 at 11:22