10:42 a.m.
[
https://issues.jboss.org/browse/FORGE-1705?page=com.atlassian.jira.plugin...
]
Antonio Goncalves commented on FORGE-1705:
------------------------------------------
Yes, the settings.xml is like this, so no chance to have the maven central directly :
{code}
<repositories>
<repository>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>proto-snapshot-local</id>
<name>proto-snapshot-local</name>
<url>http://solar-repo.retraite.lan/proto-snapshot-local</url>
</repository>
<repository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>central</id>
<name>libs-release</name>
<url>http://stelar.traite.lan/libs-release</url>
</repository>
<repository>
<id>fmk-release-local</id>
<name>fmk-release-local</name>
<url>http://stelar.traite.lan/fmk-release-local</url>
</repository>
<repository>
<snapshots />
<id>snapshots</id>
<name>libs-snapshot</name>
<url>http://stelar.traite.lan/libs-snapshot</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>central</id>
<name>plugins-release</name>
<url>http://stelar.traite.lan/plugins-release</url>
</pluginRepository>
<pluginRepository>
<snapshots />
<id>snapshots</id>
<name>plugins-snapshot</name>
<url>http://stelar.traite.lan/plugins-snapshot</url>
</pluginRepository>
</pluginRepositories>
{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...
@ 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4392
days inactive
4392
days old
0 comments
1 participants
participants (1)
-
Antonio Goncalves (JIRA)