Tomas Repel created FORGE-858:
---------------------------------
Summary: Forge can't find dependencies from Maven Central if there is an
active profile with repository setup in settings.xml
Key: FORGE-858
URL:
https://issues.jboss.org/browse/FORGE-858
Project: Forge
Issue Type: Bug
Components: Maven Integration
Affects Versions: 1.2.3.Final
Reporter: Tomas Repel
It seems that Forge does not recognize the dependencies form Maven Central. This happens
when there is an active profile with some repository setup in settings.xml file.
I experience this when using Forge with Ticket Monster
(
https://github.com/jboss-jdf/ticket-monster) and empty maven local repository.
settings.xml snippet:
{noformat}
</profiles>
<profile>
<id>test-profile</id>
<repositories>
<repository>
<id>obsolete-enterprise-repository</id>
<name>Obsolete Enterprise Repository</name>
<url>file:///home/trepel/maven/some-repo-with-missing-dependencies</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>test-profile</activeProfile>
</activeProfiles>
{noformat}
Running Forge in ticket-monster/demo directory results in following:
{noformat}
Using Forge at /home/trepel/workspace/apps/forge-distribution-1.2.3.Final
_____
| ___|__ _ __ __ _ ___
| |_ / _ \| `__/ _` |/ _ \ \\
| _| (_) | | | (_| | __/ //
|_| \___/|_| \__, |\___|
|___/
Error during Startup event
org.jboss.forge.project.ProjectModelException:
org.apache.maven.project.ProjectBuildingException: 29 problems were encountered while
building the effective model for org.jboss.jdf.examples:ticket-monster:2.1.2-SNAPSHOT
[ERROR] Non-resolvable import POM: Could not find artifact
org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.5.CR2 in obsolete-enterprise-repository
(file:///home/trepel/maven/some-repo-with-missing-dependencies) @ line 50, column 25
{noformat}
--
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