Opened 14 years ago
Closed 13 years ago
#29305 closed defect (fixed)
Can't build groovy 1.8.0
Reported by: | henri.gomez@… | Owned by: | breskeby@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | zeph@…, kylesm@…, bruno@… | |
Port: | groovy |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
During build, i got the following error :
:info:build ---------- :info:build 1) biz.aQute:bnd:jar:0.0.401 :info:build :info:build Try downloading the file manually from the project website. :info:build :info:build Then, install it using the command: :info:build mvn install:install-file -DgroupId=biz.aQute -DartifactId=bnd -Dversion=0.0.401 -Dpackaging=jar -Dfile=/path/to/file :info:build :info:build Alternatively, if you host your own repository you can deploy the file there: :info:build mvn deploy:deploy-file -DgroupId=biz.aQute -DartifactId=bnd -Dversion=0.0.401 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Maven artifact biz.aQute / bnd, version 0.0.401 is not available from central.
Latest version available there is 0.0.384:
Change History (11)
comment:1 Changed 14 years ago by henri.gomez@…
comment:2 Changed 14 years ago by breskeby@…
Owner: | changed from macports-tickets@… to breskeby@… |
---|---|
Status: | new → assigned |
bnd is a moving target and we had this problems for earlier versions. I'll have a look into this.
comment:3 Changed 14 years ago by jmroot (Joshua Root)
Port: | groovy added |
---|
comment:4 Changed 13 years ago by kylesm@…
There are 3 different dependencies that will cause this to fail.
Initially it fails on bnd. Manually installing 0.0.401 from Peter Kriens' site gets you past that, but then it fails on the version of jarjar available. Maven Central has 1.1 instead of 1.0. Once I manually installed 1.0 it finally failed on org.eclipse:osgi because 3.4.3.R34x_v20081215-1030 is no longer available from Maven Central. 3.5.0.v20090520 is now the preferred version.
comment:6 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:7 Changed 13 years ago by bruno@…
There is the same problem for a couple of different jars from the now-disabled JBoss repository.
The repository id used in the Groovy build file (config/maven/groovy-tools.pom
) is "jboss repo
", so putting this in ~/.m2/settings.xml
makes the build work:
<settings> <mirrors> <mirror> <id>jboss-public</id> <name>JBoss Public Nexus Repository</name> <url>https://repository.jboss.org/nexus/content/groups/public/</url> <mirrorOf>jboss repo</mirrorOf> </mirror> </mirrors> </settings>
(Modifying the address in config/maven/groovy-tools.pom
would probably work too.)
comment:8 follow-ups: 9 10 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | kylesm@… bruno@… added |
---|
Is this still a problem with groovy 1.8.5?
comment:9 Changed 13 years ago by kylesm@…
Replying to ryandesign@…:
Is this still a problem with groovy 1.8.5?
Don't have access to either of my machines today, but if it was 1.8.5 that came out last week that built cleanly on 1-2 of them. Can confirm versions tomorrow.
comment:10 Changed 13 years ago by kylesm@…
So it was Groovy 1.8.4 that I updated to last week without any problems, but 1.8.5 built successfully today.
comment:11 Changed 13 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Closing as per comment:10.
Note, I'm using a Nexus proxy, may and the extra Maven repo, http://www.aQute.biz/repo, is not available from there :