[forge-issues] [JBoss JIRA] (FORGE-1705) Could not transfer artifact from/to central
Antonio Goncalves (JIRA)
issues at jboss.org
Tue Mar 10 10:07:18 EDT 2015
[ https://issues.jboss.org/browse/FORGE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048593#comment-13048593 ]
Antonio Goncalves commented on FORGE-1705:
------------------------------------------
I just quickly tried. Still the same :
{code}
Using Forge at C:\PROG_RC\IT\Forge\forge-distribution-2.15.0.Final\bin\..
_____
| ___|__ _ __ __ _ ___
| |_ / _ \| `__/ _` |/ _ \ \\
| _| (_) | | | (_| | __/ //
|_| \___/|_| \__, |\___|
|__/
JBoss Forge, version [ 2.15.0.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ]
[bin]$ project-new --named test
***SUCCESS*** Project named 'test' has been created.
[test]$ jpa-setup
Downloading: http://repo1.maven.org/maven2/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/maven-metadata.xml
***ERROR*** Project 'C:\PROG_RC\IT\Forge\forge-distribution-2.15.0.Final\bin\test' has errors
***ERROR*** Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final from/to central (https://repo.maven.apache.org/maven2): Error transfe
rring file: repo.maven.apache.org from https://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final/jboss-javaee-6.0-3.0.2.Final.pom @ line 16, column 19
***ERROR*** Error while executing 'JPA: Connection Settings'
org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
at org.jboss.forge.addon.facets.AbstractFaceted.getFacet(AbstractFaceted.java:51)
at org.jboss.forge.addon.javaee.jpa.PersistenceOperationsImpl.setup(PersistenceOperationsImpl.java:59)
at org.jboss.forge.addon.javaee.jpa.ui.setup.JPASetupConnectionStep.execute(JPASetupConnectionStep.java:262)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at org.jboss.forge.addon.javaee.jpa.ui.setup.JPASetupConnectionStep_$$_javassist_e3a11110-c8d8-4826-b862-808c8c7753bb.execute(JPASetupConnectionStep_$$_javassist_e3a11110-c
8d8-4826-b862-808c8c7753bb.java)
at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.execute(WizardCommandControllerImpl.java:153)
at org.jboss.forge.addon.ui.impl.controller.NoUIWizardControllerDecorator.execute(NoUIWizardControllerDecorator.java:152)
at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:82)
at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
[test]$
{code}
> Could not transfer artifact from/to central
> -------------------------------------------
>
> Key: FORGE-1705
> URL: https://issues.jboss.org/browse/FORGE-1705
> Project: Forge
> Issue Type: Task
> Components: Addon Manager
> Affects Versions: 2.3.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I am at a customer who uses a in-house Artifactory, no direct access to Maven Central. So when I setup JPA for example :
> {code}
> [MyProj]$ jpa-setup
> ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
> {code}
> I get the following exception :
> {code}
> [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final from/to central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org from http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final/jboss-javaee-6.0-3.0.2.Final.pom @ line 11, column 19
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:179) [maven-core-3.1.1.jar:3.1.1]
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:105) [maven-core-3.1.1.jar:3.1.1]
> at org.jboss.forge.addon.maven.projects.MavenBuildManager.getProjectBuildingResult(MavenBuildManager.java:88) [maven-impl-projects-2.3.0.Final.jar:2.3.0.Final]
> ... 79 more
> Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.MyProj:MyProj:1.0.0-SNAPSHOT
> {code}
> So it looks like, by default, it uses the {{http://repo.maven.apache.org/maven2}} which is not accessible. Is there a way not to specify this repository, but instead, rely on Maven configuration (here, the in-house Artifactory repository) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the forge-issues
mailing list