[WG: Sakai QA] 2.7.x build failure

Steve Swinsburg steve.swinsburg at gmail.com
Thu Apr 29 23:04:38 PDT 2010 

It doesn't look like the artifacts have been added to the Sakai repo correctly, there is no metadata for them. So a build for me slows down tremendously when it hits those artifacts.

That said, it does eventually build, but the artifacts should be updated.

cheers,
Steve


On 30/04/2010, at 3:15 PM, Charles Hedrick wrote:

> I should note that the .pom files were my problem only because I already took the .jar files from the prevoius email. It didn't come from any repository. Could someone with the necessary permissions either fix malarchive to use current versions or upload all necessary files? I strongly suggest blowing away your repository and trying to build 2.7.x.
> 
> 
> On Apr 30, 2010, at 12:52:14 AM, Charles Hedrick wrote:
> 
>> I can't build 2.7x. Still problems with the bouncycastle stuff. I'm currently stuck on bcmail-jdk14-129.pom. That wasn't in the file you attached last time.
>> 
>> Isn't there some way to update to a more recent version, which is still online in the repositories? I really don't like the idea of having Sakai builds depend upon somebody's home directory that happens to have an old version of some of the software.
>> 
>> 
>> On Mar 25, 2010, at 6:14:38 AM, David Horwitz wrote:
>> 
>>> Ok Uploaded the jars to the sakai repo that seems to have fixed it
>>> 
>>> On 03/25/2010 12:02 PM, Nuno Fernandes wrote:
>>>> Hi David,
>>>> 
>>>> If you have permissions to upload to Sakai Maven Repo, that would be
>>>> perfect!
>>>> I have archived the "org.bouncycastle" repo with the required version (in
>>>> attachment).
>>>> 
>>>> Thanks,
>>>> Nuno
>>>> 
>>>> On Thu, Mar 25, 2010 at 9:45 AM, David Horwitz <david.horwitz at uct.ac.za>wrote:
>>>> 
>>>> 
>>>>> This seems to be caused by the failure of people.apache.org which I
>>>>> presume hosts thos artefacts (their too old to be in central)
>>>>> 
>>>>> D
>>>>> 
>>>>> On 03/25/2010 11:05 AM, David Horwitz wrote:
>>>>> 
>>>>>>   [exec] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> 
>>>>>>   [exec] [ERROR] BUILD
>>>>>> ERROR
>>>>>> 
>>>>>>   [exec] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> 
>>>>>>   [exec] [INFO] Failed to resolve
>>>>>> artifact.
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]
>>>>>> Missing:
>>>>>> 
>>>>>>   [exec]
>>>>>> ----------
>>>>>> 
>>>>>>   [exec] 1)
>>>>>> org.bouncycastle:bcmail-jdk14:jar:129
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Try downloading the file manually from the project
>>>>>> website.
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Then, install it using the
>>>>>> command:
>>>>>> 
>>>>>>   [exec]       mvn install:install-file -DgroupId=org.bouncycastle
>>>>>> -DartifactId=bcmail-jdk14 -Dversion=129 -Dpackaging=jar
>>>>>> -Dfile=/path/to/file
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Alternatively, if you host your own repository you can
>>>>>> deploy the file
>>>>>> there:
>>>>>> 
>>>>>>   [exec]       mvn deploy:deploy-file -DgroupId=org.bouncycastle
>>>>>> -DartifactId=bcmail-jdk14 -Dversion=129 -Dpackaging=jar
>>>>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Path to
>>>>>> dependency:
>>>>>> 
>>>>>>   [exec]     1)
>>>>>> org.sakaiproject:sakai-mailarchive-james:war:2.7-SNAPSHOT
>>>>>> 
>>>>>>   [exec]     2)
>>>>>> org.apache.james:james-server:jar:2.3.2
>>>>>> 
>>>>>>   [exec]     3)
>>>>>> org.bouncycastle:bcmail-jdk14:jar:129
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec] 2)
>>>>>> org.bouncycastle:bcmail-jdk14-workaround:jar:129
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Try downloading the file manually from the project
>>>>>> website.
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Then, install it using the
>>>>>> command:
>>>>>> 
>>>>>>   [exec]       mvn install:install-file -DgroupId=org.bouncycastle
>>>>>> -DartifactId=bcmail-jdk14-workaround -Dversion=129 -Dpackaging=jar
>>>>>> -Dfile=/path/to/file
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Alternatively, if you host your own repository you can
>>>>>> deploy the file
>>>>>> there:
>>>>>> 
>>>>>>   [exec]       mvn deploy:deploy-file -DgroupId=org.bouncycastle
>>>>>> -DartifactId=bcmail-jdk14-workaround -Dversion=129 -Dpackaging=jar
>>>>>> -Dfile=/path/to/file -Durl=[url]
>>>>>> -DrepositoryId=[id]
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]   Path to
>>>>>> dependency:
>>>>>> 
>>>>>>   [exec]     1)
>>>>>> org.sakaiproject:sakai-mailarchive-james:war:2.7-SNAPSHOT
>>>>>> 
>>>>>>   [exec]     2)
>>>>>> org.apache.james:james-server:jar:2.3.2
>>>>>> 
>>>>>>   [exec]     3)
>>>>>> org.bouncycastle:bcmail-jdk14-workaround:jar:129
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec]
>>>>>> ----------
>>>>>> 
>>>>>>   [exec] 2 required artifacts are
>>>>>> missing.
>>>>>> 
>>>>>> 
>>>>>> [exec]
>>>>>> 
>>>>>>   [exec] for artifact:
>>>>>>   [exec]   org.sakaiproject:sakai-mailarchive-james:war:2.7-SNAPSHOT
>>>>>>   [exec]
>>>>>>   [exec] from the specified remote repositories:
>>>>>>   [exec]   sakai-maven2-snapshots
>>>>>> (http://source.sakaiproject.org/maven2-snapshots),
>>>>>>   [exec]   central (http://repo1.maven.org/maven2),
>>>>>>   [exec]   sakai-maven (http://source.sakaiproject.org/maven2),
>>>>>>   [exec]   uct-mirror2
>>>>>> (http://source.cet.uct.ac.za:8081/nexus/content/groups/public/),
>>>>>>   [exec]   uct-mirror3
>>>>>> (http://source.cet.uct.ac.za:8081/nexus/content/groups/public/)
>>>>>>   [exec]
>>>>>>   [exec]
>>>>>>   [exec]
>>>>>>   [exec] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>   [exec] [INFO] For more information, run Maven with the -e switch
>>>>>>   [exec] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>   [exec] [INFO] Total time: 7 minutes 10 seconds
>>>>>>   [exec] [INFO] Finished at: Thu Mar 25 10:58:57 SAST 2010
>>>>>>   [exec] [INFO] Final Memory: 255M/456M
>>>>>>   [exec] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] ---------------------------------------------------------------
>>>>>> _______________________________________________
>>>>>> sakai-qa mailing list
>>>>>> sakai-qa at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>>>>>> 
>>>>>> TO UNSUBSCRIBE: send email to
>>>>>> 
>>>>> sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of
>>>>> "unsubscribe"
>>>>> 
>>>>>> 
>>>>> _______________________________________________
>>>>> sakai-qa mailing list
>>>>> sakai-qa at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>>>>> 
>>>>> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.orgwith a subject of "unsubscribe"
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>> _______________________________________________
>>> sakai-qa mailing list
>>> sakai-qa at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>>> 
>>> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>> 
>> _______________________________________________
>> sakai-qa mailing list
>> sakai-qa at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>> 
>> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-qa mailing list
> sakai-qa at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
> 
> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

More information about the sakai-qa mailing list