[ http://jira.magnolia.info/browse/MAGNOLIA-1910?page=all ]
Grégory Joseph closed MAGNOLIA-1910.
------------------------------------
Resolution: Won't Fix
Tom,
The DMS module has a separate lifecycle than the main Magnolia project. Hence,
we won't change the dependencies back to snapshot after each release.
The current solutions for you are either:
- change the dms' pom.xml locally (least preferred)
- grab the main project's corresponding tag and build/install that to your
local repo, at least the parent pom (mvn -N clean install from the root)
- get the magnolia repositories in your settings.xml (subject to change in the
coming weeks/month)
- specify the repository from command line (can't find the specific parameters
just now)
The only clean/real solution will be:SYS-19
> unable to do a mvn -Dall=true -Pwith-optional-modules clean install as of
> rev. 13323
> ------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-1910
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1910
> Project: Magnolia
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 3.5 RC2
> Reporter: Tom Jensen
> Assigned To: Grégory Joseph
> Original Estimate: 5 minutes
> Remaining Estimate: 5 minutes
>
> Trying to build magnolia at rev. 13323 I get the following from maven:
> [INFO] Scanning for projects...
> Downloading:
> http://repo1.maven.org/maven2/info/magnolia/magnolia-project/3.5-rc2/magnolia-project-3.5-rc2.pom
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: info.magnolia
> ArtifactId: magnolia-project
> Version: 3.5-rc2
> Reason: Unable to download the artifact from any repository
> info.magnolia:magnolia-project:pom:3.5-rc2
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> ...
> I don't understand maven but did some poking around and figured out how to
> add magnolia's maven repository as a mirror (in settings.xml) that fixed the
> problem so I could build, but I'd imagine no one else who is just doing a
> default install will be able to build; needs to be fixed in the appropriate
> pom.xml I guess?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
