[#BAM-1460] Bamboo POM's need to be updated for the next point release

Bamboo

Bamboo POM's need to be updated for the next point release

Created: 12/Jul/07 02:21 AM Updated: 29/Jan/08 06:26 PM

Component/s:

Remote API

Affects Version/s:

1.2

Fix Version/s:

1.2.1

Time Tracking:

Not Specified

File Attachments:

atlassian-johnson-0.6.jar (25 kB)

Participants:	Ajay Sridhar [Atlassian], Lilians Auvigne, Mark Chaimungkalanont [Atlassian] and Paul Schifferer
Since last comment:	42 weeks, 3 days ago
Number of comments:	6
Internal Priority:	1. Highest
Internal Work Bucket:	Confirmed
Labels:

Description

« Hide

As per BSP-163,

The POM's in Bamboo 1.2 need to be updated with correct repositories for.

Artifact com.atlassian.johnson:atlassian-johnson:jar:0.6

AND

Artifact com.atlassian.bucket:atlassian-bucket:jar:0.11

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Lilians Auvigne added a comment - 20/Jul/07 01:53 AM

I have tested with version 1.2.1, but I have this error :

Path to dependency: 
1) fr.sgf.tools.atlassian.bamboo:bamboo-wave-plugin:jar:1.1-SNAPSHOT
2) com.atlassian.bamboo:atlassian-bamboo-web:jar:1.2.1
3) com.atlassian.johnson:atlassian-johnson:jar:0.6

Caused by I/O exception: Server returned HTTP response code: 403 for URL: http://repository.atlassian.com/private/com/atlassian/johnson/atlassian-johnson/0.6/atlassian-johnson-0.6.jar

Surely due to private token in URL.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 24/Jul/07 08:40 PM

Lillians,

Sorry about this, it looks like the private repo (not suprisingly in retrospect) doesn't allow access from outside out firewall.

We'll make sure we get this sorted ASAP.

Cheers,

Mark C

[ Permlink | « Hide ]

Ajay Sridhar [Atlassian] added a comment - 25/Jul/07 02:19 AM

Hi Guys,

Sorry for the hassle, I have attached atlassian-johnson-0.6.jar to this issue, to instruct maven to install the is plugin type;

mvn install:install-file -DgroupId=com.atlassian.johnson -DartifactId=atlassian-johnson -Dversion=0.6 -Dpackaging=jar -Dfile=/YOUR/PATH/TO/atlassian-johnson-0.6.jar

We will also be adding this to out public maven2 repository shortly.

Regards,
Ajay

[ Permlink | « Hide ]

Ajay Sridhar [Atlassian] added a comment - 27/Jul/07 01:35 AM

Hi guys,

All the missing Atlassian artifacts have now been fixed!

However, due to licensing restrictions, we are not allowed to re-distribute native SUN libraries through our maven2 public repositories. Please read our confluence guide on coping with Sun Jar's for further details.

Regards,
Ajay

[ Permlink | « Hide ]

Paul Schifferer added a comment - 29/Jan/08 05:40 PM

I have just started a new Bamboo plugin project, and the POM from the dev kit template still attempts to pull in artifacts from the private area that are not under the Sun license. I've gotten errors on xercesImpl.jar 2.8.1 and commons-lang 2.3, both Apache projects and freely distributable, AFAIK.

[ Permlink | « Hide ]

Ajay Sridhar [Atlassian] added a comment - 29/Jan/08 06:26 PM

Hi Paul,

Thats interesting, Maven should pull down the artifacts from the public Maven ibibilo repository. I have added an additional step to our Bamboo setup guide to use Atlassian settings.xml file which proxies the public ibibilo repository - could you try using the settings.xml file attached our guide? To do this -

Download the settings.xml file, to ../<USER_HOME>/.m2/settings.xml
Run mvn and your build should succeed.

Also, we had several issues with maven 2.0.4 - could you try using maven 2.0.7 (I have updated the maven version in our guide as well).

Please let me know how you fared?

Regards,
Ajay.