[
https://issues.apache.org/jira/browse/GERONIMO-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534032
]
Kevan Miller commented on GERONIMO-3508:
----------------------------------------
I've never experienced this problem. My builds are always able to download the
artifacts from the openejb-3rdparty-builds repo (aka
http://svn.apache.org/repos/asf/openejb/repo/).
It seems that in some situations, maven is associateing the r579367 version of
xbean-naming with non-openejb dependencies. In these cases, the
openejb-3rdparty-builds repo will not be searched -- it's evidently a
maven-style, spooky crapshoot as to whether the openejb repo is searched...
I've added exclusions to try and prevent downloading of the problematic xbean
versions. I haven't been totally successful. At the moment,
xbean-naming-3.2-r579367.jar is not being downloaded. So, seemingly Donald's
problem is fixed. However, xbean-reflect-3.2-r579367.jar and commons-dbcp are
still being downloaded. Possible that moving to a non-snapshot version (i.e.
2.0.2) may help... we'll see.
Even when bad versions are downloaded, they aren't included in our binaries...
> Still cannot build branches/2.0 without building OpenEJB first, due to XBean
> depends
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-3508
> URL: https://issues.apache.org/jira/browse/GERONIMO-3508
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 2.0.2
> Reporter: Donald Woods
> Priority: Blocker
> Fix For: 2.0.2
>
>
> Unless you build openejb-3.0-beta-1 first, you will not be able to build
> Geronimo 2.0.2 (client-corba-yoko config build fails), because of the private
> xbean revisioned jars that are referenced by the openejb POM. The private
> versions are located by their build by -
> <repository>
> <id>openejb-3rdparty-builds</id>
> <name>3rd Party Build Repository</name>
> <url>http://svn.apache.org/repos/asf/openejb/repo/</url>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> Missing:
> ----------
> 1) org.apache.xbean:xbean-naming:jar:3.2-r579367
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.xbean
> -DartifactId=xbean-nam
> ing \
> -Dversion=3.2-r579367 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=org.apache.xbean
> -DartifactId=xbean-naming
> \
> -Dversion=3.2-r579367 -Dpackaging=jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.apache.geronimo.configs:client-corba-yoko:car:2.0.2-SNAPSHOT
> 2)
> org.apache.geronimo.configs:openejb-corba-deployer:car:2.0.2-SNAPSHOT
> 3) org.apache.geronimo.configs:j2ee-deployer:car:2.0.2-SNAPSHOT
> 4) org.apache.geronimo.modules:geronimo-client:jar:2.0.2-SNAPSHOT
> 5) org.apache.geronimo.modules:geronimo-naming:jar:2.0.2-SNAPSHOT
> 6) org.apache.xbean:xbean-naming:jar:3.2-r579367
> ----------
> 1 required artifact is missing.
> for artifact:
> org.apache.geronimo.configs:client-corba-yoko:car:2.0.2-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> java.net (http://download.java.net/maven/1/),
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> codehaus-snapshots (http://snapshots.repository.codehaus.org),
> apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
