I'm trying to upgrade from a 2.0.0-M7 local build to the 2.0.2 release
build and am having problems with maven.
My pom.xml entries look like:
<dependency>
<groupId>org.apache.mina</groupId>
<artifactId>mina-core</artifactId>
<version>${mina-version}</version>
</dependency>
<dependency>
<groupId>org.apache.mina</groupId>
<artifactId>mina-integration-beans</artifactId>
<version>${mina-version}</version>
</dependency>
<dependency>
<groupId>org.apache.mina</groupId>
<artifactId>mina-integration-jmx</artifactId>
<version>${mina-version}</version>
</dependency>
<dependency>
<groupId>org.apache.mina</groupId>
<artifactId>mina-transport-serial</artifactId>
<version>${mina-version}</version>
</dependency>
Changing ${mina-version} from 2.0.0-RC1 to 2.0.2 results in a series of
errors at build time.
Three artifacts are declared "missing."
1) org.apache.mina:mina-core:bundle:2.0.2
2) org.apache.mina:mina-integration-beans:bundle:2.0.2
3) org.apache.mina:mina-integration-ognl:bundle:2.0.2
For each of these, a pom file is downloaded which designates <packaging>
as "bundle." Following that a jar file is successfully downloaded, and
then a *.bundle file is attempted and fails. Not finding these
"bundle" files, the build dies.
I am using the public artifact repository at mirrors.ibiblio.org. I
have examined the files manually, there is no *.bundle file, and the
packaging token in the pom file is indeed set to "bundle."
When I download the sources from svn, I see the much more familiar
packaging token of "pom."
Thanks in advance!
boB Gage
--
boB Gage
Software Developer
Merge Healthcare
Blacksburg, Virginia
Phone:
Skype: bob_gage
[email protected]
Privacy Statement: This message is a PRIVATE communication. This
message and all attachments are a private communication and
may be confidential or protected by privilege. If you are not the
intended recipient, you are hereby notified that any disclosure,
copying, distribution or use of the information contained in or
attached to this message is strictly prohibited. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.
