JBoss Fuse 6.3, Maven and settings.xml - maven

I'm trying to follow Red Hat JBoss Fuse-6.3 Developer Guide. I added everything to the Windows: Documents and Settings\User\.m2\settings.xml (which didnt exist) as per the document.The build command I'm using is
C:\Apps\apache-maven-3.5.0\bin\mvn archetype:generate -DarchetypeGroupId=io.fabric8.archetypes -DarchetypeArtifactId=karaf-soap-archetype -DarchetypeVersion=1.2.0.redhat-630187 -DgroupId=org.fusesource.example -DartifactId=cxf-basic -Dversion=1.0-SNAPSHOT -Dfabric8-profile=cxf-basic-profile
I'm now getting this error:
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) > generate-sources # standalone-pom >>>
[INFO]
[INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) < generate-sources # standalone-pom <<<
[INFO]
[INFO]
[INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) # standalone-pom ---
[INFO] Generating project in Interactive mode
[INFO] Archetype repository not defined. Using the one from [io.fabric8.archetypes:karaf-soap-archetype:1.2.0.redhat-133] found in catalog remote
[WARNING] The POM for io.fabric8.archetypes:karaf-soap-archetype:jar:1.2.0.redhat-630187 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.056 s
[INFO] Finished at: 2018-01-17T10:31:19-07:00
[INFO] Final Memory: 12M/54M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate (default-cli) on project standalone-pom: The desired archetype does not exist (io.fabric8.archetypes:karaf-soap-archetype:1.2.0.redhat-630187) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
C:\P\Projects\JBoss_Dev_Studio-10.1.0.GA_SideProjects\get-started>
I do see that archetype exists.
Googling around for archetype does not exist (io.fabric8.archetypes:karaf-soap-archetype:1.2.0.redhat-630187 and yes! It's one of those 0 results found!

The key turned out to be this
[INFO] Archetype repository not defined. Using the one from [io.fabric8.archetypes:karaf-soap-archetype:1.2.0.redhat-133] found in catalog remote
[WARNING] The POM for io.fabric8.archetypes:karaf-soap-archetype:jar:1.2.0.redhat-630187 is missing, no dependency information available
And me being a bit of a newb with Maven - I didnt understand it first. I then googled a bit more for settings.xml - I then found mention of a settings.xml also contained in C:\Apps\apache-maven-3.5.0\conf
I added the Red Hat repositories to that file instead (as it was completely empty) and everything now builds properly. Hopefully this might help someone else figure out a similar problem faster than I did whether it's with regards to jboss fuse or maven not being correctly setup,

Related

Codename One online building error by terminal

I'm trying to use my CN1 account to compile online my project whit Ubuntu 16.04 LTS terminal command:
$ mvn cn1:build -Dcodename1.platform=android -Dcodename1.buildTarget=android-device
but I got this long error:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for bo.conectica.carry:carry-common:jar:1.0-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for com.codenameone:codenameone-buildclient:jar refers to a non-existing file /home/synapsido/.codenameone/CodeNameOneBuildClient.jar # bo.conectica.carry:carry:1.0-SNAPSHOT, /home/synapsido/Documentos/carry/pom.xml, line 293, column 21
[WARNING]
[WARNING] Some problems were encountered while building the effective model for bo.conectica.carry:carry-android:jar:1.0-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for com.codenameone:codenameone-buildclient:jar refers to a non-existing file /home/synapsido/.codenameone/CodeNameOneBuildClient.jar # bo.conectica.carry:carry:1.0-SNAPSHOT, /home/synapsido/Documentos/carry/pom.xml, line 293, column 21
[WARNING]
[WARNING] Some problems were encountered while building the effective model for bo.conectica.carry:carry:pom:1.0-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.systemPath' for com.codenameone:codenameone-buildclient:jar refers to a non-existing file /home/synapsido/.codenameone/CodeNameOneBuildClient.jar # line 293, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] carry [pom]
[INFO] carry-common [jar]
[INFO] carry-android [jar]
[INFO]
[INFO] ----------------------< bo.conectica.carry:carry >----------------------
[INFO] Building carry 1.0-SNAPSHOT [1/3]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] >>> codenameone-maven-plugin:7.0.36:build (default-cli) > package # carry >>>
[INFO]
[INFO] <<< codenameone-maven-plugin:7.0.36:build (default-cli) < package # carry <<<
[INFO]
[INFO]
[INFO] --- codenameone-maven-plugin:7.0.36:build (default-cli) # carry ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for carry 1.0-SNAPSHOT:
[INFO]
[INFO] carry .............................................. FAILURE [ 10.155 s]
[INFO] carry-common ....................................... SKIPPED
[INFO] carry-android ...................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.516 s
[INFO] Finished at: 2022-01-09T21:32:07-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.codenameone:codenameone-maven-plugin:7.0.36:build (default-cli) on project carry: Execution default-cli of goal com.codenameone:codenameone-maven-plugin:7.0.36:build failed: Plugin com.codenameone:codenameone-maven-plugin:7.0.36 or one of its dependencies could not be resolved: Could not find artifact com.codenameone:codenameone-buildclient:jar:7.0.36 at specified path /home/synapsido/.codenameone/CodeNameOneBuildClient.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
maybe my mvn plugin version is deprecated? How to Update?
That particular target doesn't seem to trigger the download of that dependency. If you run mvn verify first, or the "Run In Simulator" option in your IDE, it will cause these dependencies to be downloaded.
e.g.
mvn verify
then
mvn cn1:build -Dcodename1.platform=android -Dcodename1.buildTarget=android-device
will work.
It seems that this is an older version of the maven plugin (7.0.36) where the current is 7.0.55. Make sure to update the version and dependencies. You can use https://start.codenameone.com/ to generate a new reference.
The new version no longer depends on the file in that location.

CodeHaus Maven JAXB2 plugin error MojoExecutionException: NoSchemasException

I am trying to build my project ,in that i got error called [ERROR] Failed to execute goal org.codehaus.mojo:jaxb2-maven-plugin:2.4:xjc (One) on project tg-tg-tems-ota-common-service: : MojoExecutionException: NoSchemasException -> [Help 1]
we are using java8 ,apache maven 3.6.3 ,jaxb2 plugin 2.4
Please find below error
INFO] Building TravelGrid-Tems-Ota-Service 3.0.0-SNAPSHOT [2/3]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) # tg-tg-tems-ota-common-service ---
[INFO]
[INFO] --- jaxb2-maven-plugin:2.4:xjc (One) # tg-tg-tems-ota-common-service ---
[INFO] Created EpisodePath [D:\Sushma_Project\TG_UPGRADATION\Project\branches\3.0.0-SNAPSHOT\tems\tg-tems-servicelayer\tg-tems-ota-common-service\target\generated-sources\jaxb\emt\hotelSearchRequest\META-INF\JAXB]: true
[INFO] Ignored given or default xjbSources [D:\Sushma_Project\TG_UPGRADATION\Project\branches\3.0.0-SNAPSHOT\tems\tg-tems-servicelayer\tg-tems-ota-common-service\src\main\xjb], since it is not an existent file or directory.
[INFO] Ignored given or default sources [D:\Sushma_Project\TG_UPGRADATION\Project\branches\3.0.0-SNAPSHOT\tems\tg-tems-servicelayer\tg-tems-ota-common-service\src\main\xsd], since it is not an existent file or directory.
[WARNING] No XSD files found. Please check your plugin configuration.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for tg-servicelayer 3.0.0-SNAPSHOT:
[INFO]
[INFO] tg-servicelayer .................................... SUCCESS [ 0.697 s]
[INFO] TravelGrid-Tems-Ota-Service ........................ FAILURE [ 0.909 s]
[INFO] TravelGrid-Subsystems .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.941 s
[INFO] Finished at: 2020-06-30T15:50:30+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:jaxb2-maven-plugin:2.4:xjc (One) on project tg-tg-tems-ota-common-service: : MojoExecutionException: NoSchemasException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :tg-tg-tems-ota-common-service
D:\Sushma_Project\TG_UPGRADATION\Project\branches\3.0.0-SNAPSHOT\tems\tg-tems-servicelayer>
I am new to jaxb plugin ,can anyone help me
Please user "mvn clean install" it will clean the target folder and regenerate everything from scratch.

Apache Quickstart not working: "The defined artifact is not an archetype"

I'm trying to get started with the basic Flink quickstart examples.
https://ci.apache.org/projects/flink/flink-docs-release-1.2/quickstart/java_api_quickstart.html
I'm getting an error at the very first step with Maven. Regardless of whether I try to install using Maven or the "curl" command, I get the same error "The defined artifact is not an archetype":
Command:
mvn archetype:generate \
> -DarchetypeGroupId=org.apache.flink \
> -DarchetypeArtifactId=flink-quickstart-java \
> -DarchetypeVersion=1.2.0
Response:
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) > generate-sources # standalone-pom >>>
[INFO]
[INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) < generate-sources # standalone-pom <<<
[INFO]
[INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) # standalone-pom ---
[INFO] Generating project in Interactive mode
[INFO] Archetype repository not defined. Using the one from [org.apache.flink:flink-quickstart-java:1.2.1] found in catalog remote
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.916 s
[INFO] Finished at: 2017-05-03T18:16:55+02:00
[INFO] Final Memory: 18M/280M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate (default-cli) on project standalone-pom: The defined artifact is not an archetype -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
I'm very confused as I was able to execute these quickstarts last week without problem, and I'm completely new to Maven/Flink so I'm having trouble pinpointing what could have changed since then. Any ideas?
Only defining the archetype is not enough. You also need to provide details for the current maven project itself.
Either you have to pass the 'groupId', 'artifactId' and 'version' in the interactive mode when you run the above mentioned command.
Or, you can use the following command mvn archetype:generate -DarchetypeGroupId=org.apache.flink -DarchetypeArtifactId=flink-quickstart-java -DarchetypeVersion=1.2.0 -DgroupId=com.example -DartifactId=flink -Dversion=0.1
I have encountered with a similar error while I was trying to generate the "graphwalker" archetype using below command.
mvn archetype:generate -B \
-DarchetypeGroupId=org.graphwalker \
-DarchetypeArtifactId=graphwalker-maven-archetype \
-DgroupId=com.company -DartifactId=myProject \
-DarchetypeVersion=LATEST
However, my clue was I could generate it in the first time, but the second time it threw a similar error.
I was able to solve it by removing ./m2/repository and generating the archetype again.
rm -rf ./m2/repository

Sakai 10 clog not compiling :(

I'm having a little trouble on compiling the clog tool for sakai 10...
https://github.com/adrianfish/clog/issues/5
I suspect adrian is busy on the 11 build at the moment, but I'm wondering if it's actually something that can be fixed by the user, or maybe others have hit this and are doing something simple that I don't know about..?
Basically the current stable version of clog (0.9.3 -https://confluence.sakaiproject.org/display/CLOG/Home) doesn't compile for the sakai 10 code base, there is what looks to be a related issue (CLOG-113) here...
https://github.com/adrianfish/clog/pull/3
but I'm not sure if the sakai-10 repository for maven exists as the error you get for compiling the sakai-10 branch of clog (https://github.com/adrianfish/clog/tree/sakai-10) is as follows:
bash-3.2$ mvn clean install
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.sakaiproject.clog:clog:0.9.5-SNAPSHOT (/usr/local/sakai/sakai-src-10.0/clog-0.9.5-sakai-10branch/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact org.sakaiproject:master:pom:10.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM # line 12, column 13 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Has anyone managed to get clog to compile on sakai 10? This is a bit of a blocker for our sakai 10 deployment :(
Edit: (Also see "further edit" for solution)
After trying the suggestion (https://stackoverflow.com/a/24769111/3737856) below I get this error
*---snip---*
Downloaded: http://repo1.maven.org/maven2/org/apache/commons/commons-parent/17/commons-parent-17.pom (31 KB at 507.6 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom
Downloaded: http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom (15 KB at 320.3 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/projectlombok/lombok/0.11.6/lombok-0.11.6.pom
Downloaded: http://repo1.maven.org/maven2/org/projectlombok/lombok/0.11.6/lombok-0.11.6.pom (2 KB at 34.0 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] CLOG .............................................. SUCCESS [ 7.693 s]
[INFO] CLOG API .......................................... FAILURE [ 3.520 s]
[INFO] CLOG IMPL ......................................... SKIPPED
[INFO] CLOG PACK ......................................... SKIPPED
[INFO] CLOG HELP ......................................... SKIPPED
[INFO] CLOG TOOL ......................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.166 s
[INFO] Finished at: 2014-07-16T10:11:38+00:00
[INFO] Final Memory: 10M/59M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project clog-api: Could not resolve dependencies for project org.sakaiproject.clog:clog-api:jar:0.9.5-SNAPSHOT: Failed to collect depend encies at org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Failed to read artifact descriptor for org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Could not find arti fact org.sakaiproject:kernel:pom:10.0 in central (http://repo1.maven.org/maven2) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :clog-api
I have built the current sakai 10 release build from source (building the master directory then the root), placed the clog source in the root and built it there. This usually works.
In addition I also tried changing in the clog pom:
<name>CLOG</name>
<groupId>org.sakaiproject.clog</groupId>
<artifactId>clog</artifactId>
<version>0.9.5-SNAPSHOT</version>
<packaging>pom</packaging>
to:
<name>CLOG</name>
<groupId>org.sakaiproject.clog</groupId>
<artifactId>clog</artifactId>
<version>0.9.5</version>
<packaging>pom</packaging>
building with this and the other suggested change resulted in this error:
-bash-3.2$ mvn clean install
[INFO] Scanning for projects...
Downloading: http://repo.maven.apache.org/maven2/org/sakaiproject/master/10.0/master-10.0.pom
Downloaded: http://repo.maven.apache.org/maven2/org/sakaiproject/master/10.0/master-10.0.pom (59 KB at 172.0 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] CLOG API
[INFO] CLOG IMPL
[INFO] CLOG PACK
[INFO] CLOG HELP
[INFO] CLOG TOOL
[INFO] CLOG
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building CLOG API 0.9.5-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] CLOG API .......................................... FAILURE [ 1.374 s]
[INFO] CLOG IMPL ......................................... SKIPPED
[INFO] CLOG PACK ......................................... SKIPPED
[INFO] CLOG HELP ......................................... SKIPPED
[INFO] CLOG TOOL ......................................... SKIPPED
[INFO] CLOG .............................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.584 s
[INFO] Finished at: 2014-07-16T10:19:02+00:00
[INFO] Final Memory: 8M/59M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project clog-api: Could not resolve dependencies for project org.sakaiproject.clog:clog-api:jar:0.9.5-SNAPSHOT: Failed to collect dependencies at org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Failed to read artifact descriptor for org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Failure to find org.sakaiproject:kernel:pom:10.0 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Additionally... I notice the donwloads are referencing maven2 repositories, I don't suppose that makes any difference, I'm definitely using maven3...
-bash-3.2$ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T17:37:52+00:00)
Maven home: /usr/local/maven2/current
Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
Java home: /usr/local/java/jdk1.6.0_27/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "2.6.18-348.18.1.el5", arch: "amd64", family: "unix"
Further edit:
D'OH!!!
It works now, I changed the pom only in the way suggested (10-SNAPSHOT -> 10) and --> "compiled as root" <-- what I was doing before was compiling as a non-super user, it looks like the initial build was compiled with root and/or I have permissions wrong somewhere, but clog is now compiling.
I think I'm going to submit a pull request to adrian for the pom change though...
It looks like Clog is setup correctly. You need to have the parent that this is depending on checked out (master) and built locally if you're doing a full source compile. Then you can build clog.
https://confluence.sakaiproject.org/pages/viewpage.action?pageId=93028745
Optionally you can change the version to 10.0 (which has released dependencies) and clog will compile. For instance:
--- a/pom.xml
+++ b/pom.xml
## -12,7 +12,7 ##
<parent>
<groupId>org.sakaiproject</groupId>
<artifactId>master</artifactId>
- <version>10.0-SNAPSHOT</version>
+ <version>10.0</version>
<relativePath>../master/pom.xml</relativePath>
</parent>
The externals for the tools which are on nightly and are known to work on 10 is here.
https://source.sakaiproject.org/svn/sakai/branches/sakai-trunk-experimental/.externals

Maven - issue running mvn help:effective-pom

I am working through a basic Maven tutorial, and managed to create a simple archetype and run a mvn install. However, when trying to do a mvn help:effective-pom, I just seem to get this output:
mvn help:effective-pom [INFO] Scanning for projects... [INFO]
[INFO]
------------------------------------------------------------------------ [INFO] Building simple 1.0-SNAPSHOT [INFO]
------------------------------------------------------------------------ [INFO] [INFO] --- maven-help-plugin:2.2:effective-pom (default-cli) #
simple --- Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.2.1/maven-plugin-parameter-documenter-2.2.1.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.2.1/maven-plugin-parameter-documenter-2.2.1.pom
[INFO]
------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO]
------------------------------------------------------------------------ [INFO] Total time: 0.925s [INFO] Finished at: Mon May 13 21:41:09 BST
2013 [INFO] Final Memory: 9M/131M [INFO]
------------------------------------------------------------------------ [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom
(default-cli) on project simple: Execution default-cli of goal
org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom failed:
Plugin org.apache.maven.plugins:maven-help-plugin:2.2 or one of its
dependencies could not be resolved: Failed to collect dependencies for
org.apache.maven.plugins:maven-help-plugin:jar:2.2 (): Failed to read
artifact descriptor for
org.apache.maven:maven-plugin-parameter-documenter:jar:2.2.1: Could
not transfer artifact
org.apache.maven:maven-plugin-parameter-documenter:pom:2.2.1 from/to
central (http://repo1.maven.org/maven2): Access denied to:
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.2.1/maven-plugin-parameter-documenter-2.2.1.pom
-> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using
the -X switch to enable full debug logging. [ERROR] [ERROR] For more
information about the errors and possible solutions, please read the
following articles: [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
not much hope for me if I cant get past "Hello World" example...any advice appreciated.
Regards
i
One of your network components blocks access to http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.2.1/maven-plugin-parameter-documenter-2.2.1.pom, that's all.

Resources