[jira] Commented: (MNG-3870) Cannot use Wagon ftp on Mac OSX
[
http://jira.codehaus.org/browse/MNG-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166923#action_166923
]
Patrick Moore commented on MNG-3870:
Brett,
Retesting. We use "deploy" to push via ssh to the production server. Works fine
on windows. But now that I am on the Mac I get
http://jira.codehaus.org/browse/MDEPLOY-62
(Obviously this is *not* an ftp issue.)
Doing more ftp testing -- but ftp looks o.k. now.
> Cannot use Wagon ftp on Mac OSX
> ---
>
> Key: MNG-3870
> URL: http://jira.codehaus.org/browse/MNG-3870
> Project: Maven 2
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 2.1.0-M1
> Environment: mvn -version
> Using Java version: 1.6
> Maven version: 2.1.0-M1
> Java version: 1.6.0_07
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.5.5" arch: "x86_64" family: "mac"
>Reporter: Patrick Moore
>Assignee: Brett Porter
>
> Seems to be MacOSX-specific. I have used Wagon ftp to deploy files to a ftp
> server on windows. Using the same configuration that successfully "mvn
> deploy"'s on windows fails on Mac OSX.
> Please note that Wagon-ftp-1.0-beta-4 jars are downloaded and in the MacOSX
> repository. So this seems different than: MNG-2227 (but maybe not?)
> mvn -Dmaven.test.skip=true -e deploy
> Using Java version: 1.6
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Amplafi Hivemind
> [INFO] Amplafi Test
> [INFO] Tapestry Javaforge Acegi
> [INFO] Amplafi Json
> [INFO] Amplafi Sworddance
> [INFO] Amplafi Flow - Core
> [INFO] Flow - Web
> [INFO] Amplafi - James Mailet
> [INFO] Amplafi Wireservice - Foundation
> [INFO] Amplafi Wireservice - IO Management
> [INFO] Amplafi Wireservice - Core
> [INFO] Amplafi Wireservice - Web
> [INFO] Amplafi Project
> [INFO]
>
> [INFO] Building Amplafi Hivemind
> [INFO]task-segment: [deploy]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Not compiling test sources
> [INFO] [surefire:test]
> [INFO] Tests are skipped.
> [INFO] [jar:jar]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Preparing source:test-jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [WARNING] Removing: test-jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:test-jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] [javadoc:jar {execution: attach-javadocs}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [install:install]
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [deploy:deploy]
> altDeploymentRepository =
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Using alternate deployment repository
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Retrieving previous build number from amplafi.public
> [INFO]
>
[jira] Commented: (MNG-3870) Cannot use Wagon ftp on Mac OSX
[
http://jira.codehaus.org/browse/MNG-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166322#action_166322
]
Patrick Moore commented on MNG-3870:
Sorry forgot to tell you this:
1.0-beta-2
so no ... we never went beyonf beta-2 (seemed there was reported problems )
after that build.
I have not tried on 2.0.10 I see its freshly released. Will download and try.
> Cannot use Wagon ftp on Mac OSX
> ---
>
> Key: MNG-3870
> URL: http://jira.codehaus.org/browse/MNG-3870
> Project: Maven 2
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 2.1.0-M1
> Environment: mvn -version
> Using Java version: 1.6
> Maven version: 2.1.0-M1
> Java version: 1.6.0_07
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.5.5" arch: "x86_64" family: "mac"
>Reporter: Patrick Moore
>Assignee: Brett Porter
>
> Seems to be MacOSX-specific. I have used Wagon ftp to deploy files to a ftp
> server on windows. Using the same configuration that successfully "mvn
> deploy"'s on windows fails on Mac OSX.
> Please note that Wagon-ftp-1.0-beta-4 jars are downloaded and in the MacOSX
> repository. So this seems different than: MNG-2227 (but maybe not?)
> mvn -Dmaven.test.skip=true -e deploy
> Using Java version: 1.6
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Amplafi Hivemind
> [INFO] Amplafi Test
> [INFO] Tapestry Javaforge Acegi
> [INFO] Amplafi Json
> [INFO] Amplafi Sworddance
> [INFO] Amplafi Flow - Core
> [INFO] Flow - Web
> [INFO] Amplafi - James Mailet
> [INFO] Amplafi Wireservice - Foundation
> [INFO] Amplafi Wireservice - IO Management
> [INFO] Amplafi Wireservice - Core
> [INFO] Amplafi Wireservice - Web
> [INFO] Amplafi Project
> [INFO]
>
> [INFO] Building Amplafi Hivemind
> [INFO]task-segment: [deploy]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Not compiling test sources
> [INFO] [surefire:test]
> [INFO] Tests are skipped.
> [INFO] [jar:jar]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Preparing source:test-jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [WARNING] Removing: test-jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:test-jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] [javadoc:jar {execution: attach-javadocs}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [install:install]
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [deploy:deploy]
> altDeploymentRepository =
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Using alternate deployment repository
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Retrieving previous build number from amplafi.public
> [INFO]
>
> [ERROR] BUILD E
[jira] Commented: (MNG-3870) Cannot use Wagon ftp on Mac OSX
[
http://jira.codehaus.org/browse/MNG-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166205#action_166205
]
Patrick Moore commented on MNG-3870:
No.
I have this in the pom.xml since the beginning:
org.apache.maven.wagon
wagon-ssh-external
${wagon-build}
org.apache.maven.wagon
wagon-ftp
${wagon-build}
> Cannot use Wagon ftp on Mac OSX
> ---
>
> Key: MNG-3870
> URL: http://jira.codehaus.org/browse/MNG-3870
> Project: Maven 2
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 2.1.0-M1
> Environment: mvn -version
> Using Java version: 1.6
> Maven version: 2.1.0-M1
> Java version: 1.6.0_07
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.5.5" arch: "x86_64" family: "mac"
>Reporter: Patrick Moore
>Assignee: Brett Porter
>
> Seems to be MacOSX-specific. I have used Wagon ftp to deploy files to a ftp
> server on windows. Using the same configuration that successfully "mvn
> deploy"'s on windows fails on Mac OSX.
> Please note that Wagon-ftp-1.0-beta-4 jars are downloaded and in the MacOSX
> repository. So this seems different than: MNG-2227 (but maybe not?)
> mvn -Dmaven.test.skip=true -e deploy
> Using Java version: 1.6
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Amplafi Hivemind
> [INFO] Amplafi Test
> [INFO] Tapestry Javaforge Acegi
> [INFO] Amplafi Json
> [INFO] Amplafi Sworddance
> [INFO] Amplafi Flow - Core
> [INFO] Flow - Web
> [INFO] Amplafi - James Mailet
> [INFO] Amplafi Wireservice - Foundation
> [INFO] Amplafi Wireservice - IO Management
> [INFO] Amplafi Wireservice - Core
> [INFO] Amplafi Wireservice - Web
> [INFO] Amplafi Project
> [INFO]
>
> [INFO] Building Amplafi Hivemind
> [INFO]task-segment: [deploy]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Not compiling test sources
> [INFO] [surefire:test]
> [INFO] Tests are skipped.
> [INFO] [jar:jar]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Preparing source:test-jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [WARNING] Removing: test-jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:test-jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] [javadoc:jar {execution: attach-javadocs}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [install:install]
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [deploy:deploy]
> altDeploymentRepository =
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Using alternate deployment repository
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Retrieving previous build number from amplafi.pu
[jira] Commented: (MNG-3870) Cannot use Wagon ftp on Mac OSX
[
http://jira.codehaus.org/browse/MNG-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157446#action_157446
]
Patrick Moore commented on MNG-3870:
copying the wagon-ftp-1.0-beta-4.jar , oro-2.0.8.jar and commons-net-2.0.jar to
${MAVEN_HOME}/lib is work around for this problem.
> Cannot use Wagon ftp on Mac OSX
> ---
>
> Key: MNG-3870
> URL: http://jira.codehaus.org/browse/MNG-3870
> Project: Maven 2
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 2.1.0-M1
> Environment: mvn -version
> Using Java version: 1.6
> Maven version: 2.1.0-M1
> Java version: 1.6.0_07
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.5.5" arch: "x86_64" family: "mac"
>Reporter: Patrick Moore
>
> Seems to be MacOSX-specific. I have used Wagon ftp to deploy files to a ftp
> server on windows. Using the same configuration that successfully "mvn
> deploy"'s on windows fails on Mac OSX.
> Please note that Wagon-ftp-1.0-beta-4 jars are downloaded and in the MacOSX
> repository. So this seems different than: MNG-2227 (but maybe not?)
> mvn -Dmaven.test.skip=true -e deploy
> Using Java version: 1.6
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Amplafi Hivemind
> [INFO] Amplafi Test
> [INFO] Tapestry Javaforge Acegi
> [INFO] Amplafi Json
> [INFO] Amplafi Sworddance
> [INFO] Amplafi Flow - Core
> [INFO] Flow - Web
> [INFO] Amplafi - James Mailet
> [INFO] Amplafi Wireservice - Foundation
> [INFO] Amplafi Wireservice - IO Management
> [INFO] Amplafi Wireservice - Core
> [INFO] Amplafi Wireservice - Web
> [INFO] Amplafi Project
> [INFO]
>
> [INFO] Building Amplafi Hivemind
> [INFO]task-segment: [deploy]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Not compiling test sources
> [INFO] [surefire:test]
> [INFO] Tests are skipped.
> [INFO] [jar:jar]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Preparing source:test-jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [WARNING] Removing: test-jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:test-jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] [javadoc:jar {execution: attach-javadocs}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [install:install]
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [deploy:deploy]
> altDeploymentRepository =
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Using alternate deployment repository
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Retrieving previous build number from amplafi.public
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error retrieving previ
[jira] Created: (MNG-3870) Cannot use Wagon ftp on Mac OSX
Cannot use Wagon ftp on Mac OSX
---
Key: MNG-3870
URL: http://jira.codehaus.org/browse/MNG-3870
Project: Maven 2
Issue Type: Bug
Components: Deployment
Affects Versions: 2.1.0-M1
Environment: mvn -version
Using Java version: 1.6
Maven version: 2.1.0-M1
Java version: 1.6.0_07
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.5.5" arch: "x86_64" family: "mac"
Reporter: Patrick Moore
Seems to be MacOSX-specific. I have used Wagon ftp to deploy files to a ftp
server on windows. Using the same configuration that successfully "mvn
deploy"'s on windows fails on Mac OSX.
Please note that Wagon-ftp-1.0-beta-4 jars are downloaded and in the MacOSX
repository. So this seems different than: MNG-2227 (but maybe not?)
mvn -Dmaven.test.skip=true -e deploy
Using Java version: 1.6
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Amplafi Hivemind
[INFO] Amplafi Test
[INFO] Tapestry Javaforge Acegi
[INFO] Amplafi Json
[INFO] Amplafi Sworddance
[INFO] Amplafi Flow - Core
[INFO] Flow - Web
[INFO] Amplafi - James Mailet
[INFO] Amplafi Wireservice - Foundation
[INFO] Amplafi Wireservice - IO Management
[INFO] Amplafi Wireservice - Core
[INFO] Amplafi Wireservice - Web
[INFO] Amplafi Project
[INFO]
[INFO] Building Amplafi Hivemind
[INFO]task-segment: [deploy]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Not compiling test sources
[INFO] [surefire:test]
[INFO] Tests are skipped.
[INFO] [jar:jar]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar:
/Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
[INFO] Preparing source:test-jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[WARNING] Removing: test-jar from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:test-jar {execution: attach-sources}]
[INFO] Building jar:
/Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
[INFO] [javadoc:jar {execution: attach-javadocs}]
[INFO] Building jar:
/Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
[INFO] [install:install]
[INFO] Installing
/Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT.jar
to
/Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT.jar
[INFO] Installing
/Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
to
/Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
[INFO] Installing
/Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
to
/Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
[INFO] Installing
/Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
to
/Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
[INFO] [deploy:deploy]
altDeploymentRepository =
amplafi.public::default::ftp://amplafi.com/httpdocs/repository
[INFO] Using alternate deployment repository
amplafi.public::default::ftp://amplafi.com/httpdocs/repository
[INFO] Retrieving previous build number from amplafi.public
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error retrieving previous build number for artifact
'com.amplafi:amplafi-hivemind:jar': repository metadata for: 'snapshot
com.amplafi:amplafi-hivemind:0.8-SNAPSHOT' could not be retrieved from
repository: amplafi.public due to an error: Unsupported Protocol: 'ftp': Cannot
find wagon which supports the requested protocol: ftp
Component descriptor cannot be found in the component repository:
org.apache.maven.wagon.Wagonftp.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error retrievin
[jira] Updated: (MEV-443) Several projects have maven-metadata.xml files that are missing released versions
[ http://jira.codehaus.org/browse/MEV-443?page=all ] Patrick Moore updated MEV-443: -- Attachment: maven-metadata.xml This is a sample file showing what I think the maven-metadata.xml file should look like > Several projects have maven-metadata.xml files that are missing released > versions > - > > Key: MEV-443 > URL: http://jira.codehaus.org/browse/MEV-443 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Patrick Moore > Attachments: maven-metadata.xml > > > I am trying to use the version range feature that is talked about in Better > builds with Maven. I am specifying the commons-httpclient dependency as > > commons-httpclient > commons-httpclient > [3.1-alpha1,) > > Unfortunately, the usefulness of this feature is being sabotaged because the > latest version of artificat is not listed in the maven-metadata.xml. > Please update the maven-metadata.xml in this project and others. In > particular > hsqldb, > commons-*, > rhino/js > htmlunit > When updating those files, please do not list the versions using dates as > their version id as it screws up the maven feature that allows dependencies > to specify a version range. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-441) Several projects have bad maven-metadata.xml files that are screwing up dependencies with version range feature
[ http://jira.codehaus.org/browse/MEV-441?page=comments#action_74114 ] Patrick Moore commented on MEV-441: --- I have added a new issue so that the two problems of missing versions and badly numbered versions can be tracked separately. http://jira.codehaus.org/browse/MEV-443 > Several projects have bad maven-metadata.xml files that are screwing up > dependencies with version range feature > --- > > Key: MEV-441 > URL: http://jira.codehaus.org/browse/MEV-441 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Patrick Moore > > I am trying to use the version range feature that is talked about in Better > builds with Maven. I am specifying the commons-httpclient dependency as > > commons-httpclient > commons-httpclient > [3.1-alpha1,) > > Unfortunately, the usefulness of this feature is being sabotaged in 2 ways. > 1) maven-metadata.xml in the commons-httpclient directory does not list > version 3.1-alpha1. This means that it will not find that version. > 2) maven-metadata.xml lists a "20020423" which is > numerically the highest number version, so my build is picking up this very > old version. > Other projects with this problem include: commons-chain and jmock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-443) Several projects have maven-metadata.xml files that are missing released versions
Several projects have maven-metadata.xml files that are missing released versions - Key: MEV-443 URL: http://jira.codehaus.org/browse/MEV-443 Project: Maven Evangelism Issue Type: Bug Reporter: Patrick Moore I am trying to use the version range feature that is talked about in Better builds with Maven. I am specifying the commons-httpclient dependency as commons-httpclient commons-httpclient [3.1-alpha1,) Unfortunately, the usefulness of this feature is being sabotaged because the latest version of artificat is not listed in the maven-metadata.xml. Please update the maven-metadata.xml in this project and others. In particular hsqldb, commons-*, rhino/js htmlunit When updating those files, please do not list the versions using dates as their version id as it screws up the maven feature that allows dependencies to specify a version range. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEV-442) Several projects have maven-metadata.xml files that are missing released versions
[ http://jira.codehaus.org/browse/MEV-442?page=all ] Patrick Moore closed MEV-442. - Resolution: Duplicate cloning an issue didn't let me edit the issue. will make a new issue > Several projects have maven-metadata.xml files that are missing released > versions > - > > Key: MEV-442 > URL: http://jira.codehaus.org/browse/MEV-442 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Patrick Moore > > I am trying to use the version range feature that is talked about in Better > builds with Maven. I am specifying the commons-httpclient dependency as > > commons-httpclient > commons-httpclient > [3.1-alpha1,) > > Unfortunately, the usefulness of this feature is being sabotaged in 2 ways. > 1) maven-metadata.xml in the commons-httpclient directory does not list > version 3.1-alpha1. This means that it will not find that version. > 2) maven-metadata.xml lists a "20020423" which is > numerically the highest number version, so my build is picking up this very > old version. > Other projects with this problem include: commons-chain and jmock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-442) Several projects have maven-metadata.xml files that are missing released versions
Several projects have maven-metadata.xml files that are missing released versions - Key: MEV-442 URL: http://jira.codehaus.org/browse/MEV-442 Project: Maven Evangelism Issue Type: Bug Reporter: Patrick Moore I am trying to use the version range feature that is talked about in Better builds with Maven. I am specifying the commons-httpclient dependency as commons-httpclient commons-httpclient [3.1-alpha1,) Unfortunately, the usefulness of this feature is being sabotaged in 2 ways. 1) maven-metadata.xml in the commons-httpclient directory does not list version 3.1-alpha1. This means that it will not find that version. 2) maven-metadata.xml lists a "20020423" which is numerically the highest number version, so my build is picking up this very old version. Other projects with this problem include: commons-chain and jmock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-441) Several projects have bad maven-metadata.xml files that are screwing up dependencies with version range feature
[ http://jira.codehaus.org/browse/MEV-441?page=comments#action_74088 ] Patrick Moore commented on MEV-441: --- a large % of the projects have incomplete maven-metadata.xml files in their repositories. Additional examples: hsqldb, commons-collections, rhino/js htmlunit > Several projects have bad maven-metadata.xml files that are screwing up > dependencies with version range feature > --- > > Key: MEV-441 > URL: http://jira.codehaus.org/browse/MEV-441 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Patrick Moore > > I am trying to use the version range feature that is talked about in Better > builds with Maven. I am specifying the commons-httpclient dependency as > > commons-httpclient > commons-httpclient > [3.1-alpha1,) > > Unfortunately, the usefulness of this feature is being sabotaged in 2 ways. > 1) maven-metadata.xml in the commons-httpclient directory does not list > version 3.1-alpha1. This means that it will not find that version. > 2) maven-metadata.xml lists a "20020423" which is > numerically the highest number version, so my build is picking up this very > old version. > Other projects with this problem include: commons-chain and jmock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINSTALL-33) mvn install:install-file should create appropriate entries so that dependencies with version ranges will use installed file.
mvn install:install-file should create appropriate entries so that dependencies with version ranges will use installed file. Key: MINSTALL-33 URL: http://jira.codehaus.org/browse/MINSTALL-33 Project: Maven 2.x Install Plugin Issue Type: Bug Affects Versions: 2.1 Environment: all Reporter: Patrick Moore when using install:install-file it should cooperate with the code that handles versions that don't have an explicit version, but specify a version range. For example, if I install hibernate-3.2.0rc4, and my pom.xml has the hibernate dependency specified as: hibernate hibernate [3.2.0rc4,) maven will complain that it cannot find the hibernate version 3.2.0rc4. However if the dependency is specified as : hibernate hibernate 3.2.0rc4 then the project builds successfully. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-441) Several projects have bad maven-metadata.xml files that are screwing up dependencies with version range feature
Several projects have bad maven-metadata.xml files that are screwing up dependencies with version range feature --- Key: MEV-441 URL: http://jira.codehaus.org/browse/MEV-441 Project: Maven Evangelism Issue Type: Bug Reporter: Patrick Moore I am trying to use the version range feature that is talked about in Better builds with Maven. I am specifying the commons-httpclient dependency as commons-httpclient commons-httpclient [3.1-alpha1,) Unfortunately, the usefulness of this feature is being sabotaged in 2 ways. 1) maven-metadata.xml in the commons-httpclient directory does not list version 3.1-alpha1. This means that it will not find that version. 2) maven-metadata.xml lists a "20020423" which is numerically the highest number version, so my build is picking up this very old version. Other projects with this problem include: commons-chain and jmock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
