When building from trunk: Unknown host nexus.codehaus.org

classic Classic list List threaded Threaded
7 messages Options
javadba javadba
Reply | Threaded
Open this post in threaded view
|

When building from trunk: Unknown host nexus.codehaus.org



I am using the following command line: 

   mvn -Dmaven.javadoc.skip=true  -DskipTests clean package

and end up with:


[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default) on project ignite-core: Execution default of goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java failed: Plugin org.codehaus.mojo:exec-maven-plugin:1.3.2 or one of its dependencies could not be resolved: Could not transfer artifact org.apache.ignite:ignite-tools:jar:1.4.1-SNAPSHOT from/to codehaus-snapshots (http://nexus.codehaus.org/snapshots/): nexus.codehaus.org: Unknown host nexus.codehaus.org -> [Help 1]


[INFO] ignite-apache-license-gen .......................... SUCCESS [  2.200 s]
[INFO] ignite-tools ....................................... SUCCESS [  4.227 s]
[INFO] ignite-core ........................................ FAILURE [ 19.411 s]


What is the workaround for this?
Konstantin Boudnik Konstantin Boudnik
Reply | Threaded
Open this post in threaded view
|

Re: When building from trunk: Unknown host nexus.codehaus.org

Codehaus is out of business. Looks like some of the locally caches artifacts
still refer to that repo server. What might help is wiping out the
~/.m2/repository

Cos

On Mon, Sep 07, 2015 at 02:50PM, Stephen Boesch wrote:

>    I am using the following command line:A
>    A  A mvn -Dmaven.javadoc.skip=true A -DskipTests clean package
>    and end up with:
>    [ERROR] Failed to execute goal
>    org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default) on project
>    ignite-core: Execution default of goal
>    org.codehaus.mojo:exec-maven-plugin:1.3.2:java failed: Plugin
>    org.codehaus.mojo:exec-maven-plugin:1.3.2 or one of its dependencies could
>    not be resolved: Could not transfer artifact
>    org.apache.ignite:ignite-tools:jar:1.4.1-SNAPSHOT from/to
>    codehaus-snapshots (http://nexus.codehaus.org/snapshots/):
>    nexus.codehaus.org: Unknown host nexus.codehaus.org -> [Help 1]
>    [INFO] ignite-apache-license-gen .......................... SUCCESS [
>    A 2.200 s]
>    [INFO] ignite-tools ....................................... SUCCESS [
>    A 4.227 s]
>    [INFO] ignite-core ........................................ FAILURE [
>    19.411 s]
>    What is the workaround for this?
javadba javadba
Reply | Threaded
Open this post in threaded view
|

Re: When building from trunk: Unknown host nexus.codehaus.org

Thx for the insight. .m2/repository is wiped and am rebuilding .. (will take awhile ;) )

2015-09-07 16:01 GMT-07:00 Konstantin Boudnik <[hidden email]>:
Codehaus is out of business. Looks like some of the locally caches artifacts
still refer to that repo server. What might help is wiping out the
~/.m2/repository

Cos

On Mon, Sep 07, 2015 at 02:50PM, Stephen Boesch wrote:
>    I am using the following command line:A
>    A  A mvn -Dmaven.javadoc.skip=true A -DskipTests clean package
>    and end up with:
>    [ERROR] Failed to execute goal
>    org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default) on project
>    ignite-core: Execution default of goal
>    org.codehaus.mojo:exec-maven-plugin:1.3.2:java failed: Plugin
>    org.codehaus.mojo:exec-maven-plugin:1.3.2 or one of its dependencies could
>    not be resolved: Could not transfer artifact
>    org.apache.ignite:ignite-tools:jar:1.4.1-SNAPSHOT from/to
>    codehaus-snapshots (http://nexus.codehaus.org/snapshots/):
>    nexus.codehaus.org: Unknown host nexus.codehaus.org -> [Help 1]
>    [INFO] ignite-apache-license-gen .......................... SUCCESS [
>    A 2.200 s]
>    [INFO] ignite-tools ....................................... SUCCESS [
>    A 4.227 s]
>    [INFO] ignite-core ........................................ FAILURE [
>    19.411 s]
>    What is the workaround for this?

javadba javadba
Reply | Threaded
Open this post in threaded view
|

Re: When building from trunk: Unknown host nexus.codehaus.org

The pom's themselves refer to codehaus plugin:

/examples/pom.xml:                <groupId>org.codehaus.mojo</groupId>
./examples/pom.xml:                        <groupId>org.codehaus.mojo</groupId>
./modules/core/pom.xml:                <groupId>org.codehaus.mojo</groupId>
./parent/pom.xml:                <groupId>org.codehaus.mojo</groupId>


Looks like the org.codehaus.mojo has an issue:


[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default) on project ignite-core: Execution default of goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java failed: Plugin org.codehaus.mojo:exec-maven-plugin:1.3.2 or one of its dependencies could not be resolved: Could not transfer artifact org.apache.ignite:ignite-tools:jar:1.4.1-SNAPSHOT from/to codehaus-snapshots (http://nexus.codehaus.org/snapshots/): nexus.codehaus.org: Unknown host nexus.codehaus.org -> [Help 1]

This error still occurs after I blew away the .m2/repository.  is there something within the plugin internally that "knows" to look for codehaus.org?? How to redirect it?




2015-09-07 16:13 GMT-07:00 Stephen Boesch <[hidden email]>:
Thx for the insight. .m2/repository is wiped and am rebuilding .. (will take awhile ;) )

2015-09-07 16:01 GMT-07:00 Konstantin Boudnik <[hidden email]>:
Codehaus is out of business. Looks like some of the locally caches artifacts
still refer to that repo server. What might help is wiping out the
~/.m2/repository

Cos

On Mon, Sep 07, 2015 at 02:50PM, Stephen Boesch wrote:
>    I am using the following command line:A
>    A  A mvn -Dmaven.javadoc.skip=true A -DskipTests clean package
>    and end up with:
>    [ERROR] Failed to execute goal
>    org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default) on project
>    ignite-core: Execution default of goal
>    org.codehaus.mojo:exec-maven-plugin:1.3.2:java failed: Plugin
>    org.codehaus.mojo:exec-maven-plugin:1.3.2 or one of its dependencies could
>    not be resolved: Could not transfer artifact
>    org.apache.ignite:ignite-tools:jar:1.4.1-SNAPSHOT from/to
>    codehaus-snapshots (http://nexus.codehaus.org/snapshots/):
>    nexus.codehaus.org: Unknown host nexus.codehaus.org -> [Help 1]
>    [INFO] ignite-apache-license-gen .......................... SUCCESS [
>    A 2.200 s]
>    [INFO] ignite-tools ....................................... SUCCESS [
>    A 4.227 s]
>    [INFO] ignite-core ........................................ FAILURE [
>    19.411 s]
>    What is the workaround for this?


vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: When building from trunk: Unknown host nexus.codehaus.org

The build works for me. And actually it looks weird that it tries to go to codehaus repo, because this plugin is available in Maven Central. Is it possible that you have this repo specified somewhere? E.g., in .m2/settings.xml file?

-Val
javadba javadba
Reply | Threaded
Open this post in threaded view
|

Re: When building from trunk: Unknown host nexus.codehaus.org

I had already deleted the entire .m2/repository per another suggestion. I do not have direct access to the build env at this moment - but will check the .m2/settings.xml within a few hours. 

2015-09-08 15:30 GMT-07:00 vkulichenko <[hidden email]>:
The build works for me. And actually it looks weird that it tries to go to
codehaus repo, because this plugin is available in Maven Central. Is it
possible that you have this repo specified somewhere? E.g., in
.m2/settings.xml file?

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/When-building-from-trunk-Unknown-host-nexus-codehaus-org-tp1285p1298.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

javadba javadba
Reply | Threaded
Open this post in threaded view
|

Re: When building from trunk: Unknown host nexus.codehaus.org

I did build successfully on another machine. So yes it seems to be a case of cleaning out local maven settings on that other machine. 

2015-09-08 15:46 GMT-07:00 Stephen Boesch <[hidden email]>:
I had already deleted the entire .m2/repository per another suggestion. I do not have direct access to the build env at this moment - but will check the .m2/settings.xml within a few hours. 

2015-09-08 15:30 GMT-07:00 vkulichenko <[hidden email]>:
The build works for me. And actually it looks weird that it tries to go to
codehaus repo, because this plugin is available in Maven Central. Is it
possible that you have this repo specified somewhere? E.g., in
.m2/settings.xml file?

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/When-building-from-trunk-Unknown-host-nexus-codehaus-org-tp1285p1298.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.