The atlassian sdk setup does recommends not mixing the atlassian maven+maven
repo with any other repo...apparently this is why.

Were they exceptions during testing or just logging output?  There is a
considerable number of logs printed during testing...97% of which mean
nothing and should be removed (some are not preventable though).  I think
there is a ticket for this already...

Ben

On Fri, Aug 12, 2011 at 4:06 PM, Burke Mamlin <[email protected]>wrote:

> It wasn't a mirror, but Atlassian had inserted a profile into my
> ~/.m2/settings.xml.  I commented it out and, despite a number of exceptions
> thrown during testing, was able to successfully run mvn package on OpenMRS.
>
> Merci beaucoup!
>
> -Burke
>
>
> On Thu, Aug 11, 2011 at 11:21 PM, Pier-Luc Caron St-Pierre <
> [email protected]> wrote:
>
>> You probably have a maven mirror configured. If I understand
>> correctly, _ALL_ requests made by Maven pass by your atlassian mirror.
>> Since Atlassian does not contain the dependencies OpenMRS need, it
>> fail.
>>
>> I suggest you to open your ~.m2/settings.xml and comment out the
>> "mirrors" part. Oh, and do mvn -U package for forcing the update. If
>> you do not force, Maven cache the result for 24 hours.
>>
>> On Thu, Aug 11, 2011 at 20:12, Burke Mamlin <[email protected]>
>> wrote:
>> > I checked out OpenMRS 1.8.2:
>> > $ svn co http://svn.openmrs.org/openmrs/tags/1.8.2/ openmrs-1.8.2
>> > then I changed to the local copy and tried to package it:
>> > $ cd openmrs-1.8.2
>> > $ mvn package
>> > It fails with this message:
>> > [ERROR] Failed to execute goal
>> >
>> com.googlecode.maven-java-formatter-plugin:maven-java-formatter-plugin:0.2.0:format
>> > (default) on project openmrs-api: Execution default of goal
>> >
>> com.googlecode.maven-java-formatter-plugin:maven-java-formatter-plugin:0.2.0:format
>> > failed: Plugin
>> >
>> com.googlecode.maven-java-formatter-plugin:maven-java-formatter-plugin:0.2.0
>> > or one of its dependencies could not be resolved: The following
>> artifacts
>> > could not be resolved: org.eclipse.core:jobs:jar:3.3.1,
>> > org.eclipse.equinox:registry:jar:3.3.1: Failure to find
>> > org.eclipse.core:jobs:jar:3.3.1 in
>> > https://m2proxy.atlassian.com/repository/public was cached in the local
>> > repository, resolution will not be reattempted until the update interval
>> of
>> > atlassian-public has elapsed or updates are forced -> [Help 1]
>> > I can see that it's going
>> > to https://m2proxy.atlassian.com/repository/public, presumably because
>> of
>> > some development on Atlassian plugins I've done previously using maven,
>> but
>> > the OpenMRS repository URL is included in pom.xml, so shouldn't it be
>> > checking there as well?  Can somebody point out what I'm doing wrong?
>>  Does
>> > it really require special configuration of maven to compile/package
>> OpenMRS?
>> >  Or has my prior work on Atlassian plugins done something nefarious to
>> my
>> > maven configuration?
>> > Thanks.
>> > -Burke
>> > ________________________________
>> > Click here to unsubscribe from OpenMRS Developers' mailing list
>>
>>
>>
>> --
>> Cordialement,
>> Pier-Luc
>>
>> _________________________________________
>>
>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
>> [email protected] with "SIGNOFF openmrs-devel-l" in the  body
>> (not the subject) of your e-mail.
>>
>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
>>
>>
> ------------------------------
> Click here to 
> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from 
> OpenMRS Developers' mailing list
>

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to