Rats, I musta screwed something up on my end.... I hear RC2 will
contain the only patch we've applied, so I'm thinking we'll just skip
RC1 if I can't make the source build anymore...
I just checked out a clean copy (
http://svn.apache.org/repos/asf/mina/trunk ) and ran ' mvn clean install
' and am still getting the same odd version failure....
boB
Ashish wrote:
Its working fine for me. Build was successful.
To be on safe side, I did SVN cleanup, and then ran "mvn clean install".
- ashish
On Thu, Oct 22, 2009 at 1:33 AM, boB Gage <bg...@merge.com> wrote:
I updated my mina source (first time in awhile) and am getting the oddest
build-time error.
I type 'mvn clean install' and everything chugs along happy as can be, until
...
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache MINA XBean Integration
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: org.codehaus.mojo:build-helper-maven-plugin
Reason: Error getting POM for 'org.codehaus.mojo:build-helper-maven-plugin'
from the repository: Failed to resolve artifact, possibly due to a
repository list that is not appropriately equipped for this artifact's
metadata.
org.codehaus.mojo:build-helper-maven-plugin:pom:1.5-SNAPSHOT
I checked -- our repository mirror does not have codehaus's
build-helper-maven-plugin, so I'm working on that part. BUT.... far as
I can tell from looking at
http://repository.codehaus.org/org/codehaus/mojo/build-helper-maven-plugin/
the latest version is 1.4, so 1.5-SNAPSHOT is an unreleased working copy.
I double-checked: renamed my mina directory and checked out clean from the
trunk. Same results.
Do I now need codehaus source too?? Oddly enough, I can't find "1.5" in
any Mina project files (pom.xml et al) in relation to this plugin so am
confused as to where that tag is even coming from.