|
|
Re: maven archetype catalog requires authentication [message #1124246 is a reply to message #1124131] |
Thu, 03 October 2013 10:33 |
Tim Stephenson Messages: 6 Registered: October 2013 |
Junior Member |
|
|
Hi Tanmoy,
At this stage I am using the New > Project > New Maven Project wizard inside Eclipse. I attach a screenshot of the preference page configured for the new URL you mentioned and in the background you can see that no archetypes are found still.
However, I can confirm that using a browser I do get access to the new URL you mentioned (is it possible that you could update the references to the sungard on the wiki page?). Furthermore using this command line I am able to generate a project ok:
mvn -DarchetypeArtifactId=tc6-ipp-portal-war -DarchetypeGroupId=org.eclipse.stardust.deploy.jee.archetypes -DarchetypeVersion=1.0.1 archetype:generate
I then cd into the project directory and ran mvn package which produced this error in finding the tomcat60-ipp-portal-war pom:
[ERROR] The build could not read 2 projects -> [Help 1]
[ERROR]
[ERROR] The project com.knowprocess:stardust2-ipp-portal:1.0-SNAPSHOT (/Users/timstephenson/tmp/stardust2/ipp-portal/pom.xml) has 2 errors
[ERROR] Non-resolvable import POM: Failure to find org.eclipse.stardust.deploy.jee.server:tomcat60-war:pom:1.0.1 in http://archive.eclipse.org/stardust/maven/3rdparty/eclipse was cached in the local repository, resolution will not be reattempted until the update interval of stardust-3rdparty-eclipse-repo has elapsed or updates are forced @ line 26, column 21 -> [Help 2]
[ERROR] Non-resolvable import POM: Failure to find org.eclipse.stardust.deploy.jee.rtenv:tomcat60-ipp-portal-war:pom:1.0.1 in http://archive.eclipse.org/stardust/maven/3rdparty/eclipse was cached in the local repository, resolution will not be reattempted until the update interval of stardust-3rdparty-eclipse-repo has elapsed or updates are forced @ line 33, column 22 -> [Help 2]
[ERROR]
[ERROR] The project com.knowprocess:stardust2-custom:1.0-SNAPSHOT (/Users/timstephenson/tmp/stardust2/custom/pom.xml) has 1 error
[ERROR] Non-resolvable import POM: Failure to find org.eclipse.stardust.deploy.jee.server:tomcat60-war:pom:1.0.1 in http://archive.eclipse.org/stardust/maven/3rdparty/eclipse was cached in the local repository, resolution will not be reattempted until the update interval of stardust-3rdparty-eclipse-repo has elapsed or updates are forced @ line 18, column 22 -> [Help 2]
It looks like those artefacts are in the download.eclipse.org rather than archive.eclipse.org repository but I am not able to find what is directing Maven to the wrong place.
Thanks in advance,
Tim
|
|
|
|
|
Re: maven archetype catalog requires authentication [message #1124292 is a reply to message #1124247] |
Thu, 03 October 2013 11:40 |
|
Tim,
the page should no longer point to the infinity maven repo because we now have the archetypes in the eclipse maven repo. However, what is still missing there is the catalog file I hope we can add it shortly and will then adjust the wiki page to the new URL.
Without archetype catalog the eclipse wizard for the maven project creation based on an archetype will not work so comfortably. However, an easy workaround would be to simply create the archetype using Maven on the command line and then use Eclipse's 'import existing maven project' function. Will that work for you? Which archetype are you trying to build?
Best regards
Rob
|
|
|
Re: maven archetype catalog requires authentication [message #1124453 is a reply to message #1124279] |
Thu, 03 October 2013 14:51 |
Tim Stephenson Messages: 6 Registered: October 2013 |
Junior Member |
|
|
Next error:
[ERROR] Failed to execute goal on project stardust2-custom: Could not resolve dependencies for project com.knowprocess:stardust2-custom:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: stax:stax-api:jar:1.0.1-eclipse01, rhino:js:jar:1.7R2-eclipse01, javax.activation:activation:jar:1.1-eclipse01, commons-jxpath:commons-jxpath:jar:1.3-eclipse01, aopalliance:aopalliance:jar:1.0-eclipse01, org.icefaces:icefaces:jar:1.8.2-r33557, commons-logging:commons-logging:jar:1.1.1-eclipse01, org.icefaces:icefaces-comps:jar:1.8.2-r33557, org.icefaces:icefaces-facelets:jar:1.8.2-r33557-eclipse01, log4j:log4j:jar:1.2.15-eclipse01, org.slf4j:slf4j-api:jar:1.5.11-eclipse01, javax.ws.rs:jsr311-api:jar:1.1.1-eclipse01, com.google.code.gson:gson:jar:1.6-eclipse01, backport-util-concurrent:backport-util-concurrent:jar:3.1-eclipse01, commons-collections:commons-collections:jar:3.2-eclipse01, commons-lang:commons-lang:jar:2.4-eclipse01, javax.mail:mail:jar:1.4-eclipse01, org.icepdf:icepdf-core:jar:4.3.2, net.sourceforge.htmlcleaner:htmlcleaner:jar:2.1, com.sun.media:jai_imageio:jar:1.1-eclipse01, org.apache.cxf:cxf-api:jar:2.6.1-eclipse01, com.sun.xml.bind:jaxb-impl:jar:2.1.12-eclipse01: Failure to find stax:stax-api:jar:1.0.1-eclipse01 in http://download.eclipse.org/stardust/maven/releases was cached in the local repository, resolution will not be reattempted until the update interval of stardust-3rdparty-eclipse-repo has elapsed or updates are forced -> [Help 1]
Analysing the pom with the Maven POM Editor's dependency tool shows that the carnot-engine 1.0.1 depends on this version of stax suffixed -eclipse01. A number of the other ipp dependencies seem to have similar dependencies on the other -eclipse01 variants.
And I am not able to locate these -eclipse01 dependencies in the eclipse maven repo.
Tim
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04335 seconds