Bug 965097
| Summary: | Community maven repo is mentioned in pom.xml when new switchyard project is created in JBDS | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Jiri Sedlacek <jsedlace> |
| Component: | Tooling | Assignee: | Rob Cernich <rcernich> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Len DiMaggio <ldimaggi> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 GA | CC: | apodhrad, atangrin, dlesage, kbabo, ldimaggi, oskutka, soa-p-jira |
| Target Milestone: | ER7 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When you create a new SwitchYard project is in JBDS, there is a hardcoded reference to the community repository in the code.
This can cause problems in the future if you then run 'mvn install' on the project as the wrong URL will be used.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 975725 | ||
*** Bug 1007535 has been marked as a duplicate of this bug. *** Keith Babo <kbabo> made a comment on jira SWITCHYARD-1701 pushed Do we need doc text for this issue any longer? The underlying issue (tooling adding the jboss.org repo) has been resolved. Verified with JBDS-IS 7.0.0.CR2 Keith Babo <kbabo> updated the status of jira SWITCHYARD-1701 to Closed |
Description of problem: When new switchyard project is created in JBDS, there is hardcoded reference to community repo inside: <repositories> <repository> <id>jboss-public-repository</id> <name>JBoss Public Maven Repository</name> <url>http://repository.jboss.org/nexus/content/groups/public</url> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss-public-repository</id> <name>JBoss Public Maven Repository</name> <url>http://repository.jboss.org/nexus/content/groups/public</url> </pluginRepository> </pluginRepositories> This can cause problems in the future if user do 'mvn install' on the project, when this project will be used as a dependency, its dependencies will be looked up on hardcoded url.