[jboss-jira] [JBoss JIRA] (WFLY-8173) Make build scripts handle default settings.xml correctly
Peter Palaga (JIRA)
issues at jboss.org
Tue Feb 21 03:48:01 EST 2017
[ https://issues.jboss.org/browse/WFLY-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Palaga moved JBEAP-8984 to WFLY-8173:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8173 (was: JBEAP-8984)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Build System
Test Suite
(was: Build System)
(was: Productization)
(was: Test Suite)
Affects Version/s: (was: 7.1.0.DR12)
Affects Testing: (was: Regression)
> Make build scripts handle default settings.xml correctly
> --------------------------------------------------------
>
> Key: WFLY-8173
> URL: https://issues.jboss.org/browse/WFLY-8173
> Project: WildFly
> Issue Type: Bug
> Components: Build System, Test Suite
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Priority: Critical
>
> *Wrong behaviour in EAP 7.1.0.DR12*
> * mvnw, build.sh and integration-tests.sh does't use productized settings.xml by default.
> *Desired behaviour*
> * mvnw, build.sh and integration-tests.sh should use productized settings.xml by default.
> *Workaround for build.sh*
> Productized settings.xml needs to be defined manually by "-s" maven property, example:
> ./build.sh clean -Dmaven.repo.local=$NEW_REPO -DallTests -Djboss.test.mixed.domain.dir=$\{HUDSON_STATIC_ENV\}/eap/archives-repository/mixed-domain -s tools/maven/conf/settings.xml
> *Workaround for integration-tests.sh*
> Absolute path needs to be used (see JBEAP-8947), example: "-s /mnt/hudson_workspace/mkopecky/ts/tools/maven/conf/settings.xml"
> *Additional information:*
> * productized settings.xml is added in [this productization commit|http://git.app.eng.bos.redhat.com/git/wildfly/wildfly.git/commit/tools/maven/conf/settings.xml?h=7.1.0.DR12-redhat-fix&id=683ffbac0085d799a1f098337d3a786f9bf1eb7c]
> * "tools/maven/conf/settings.xml" location doesn't make sense, because [download-maven.sh script was removed|https://github.com/jbossas/jboss-eap7/pull/1334/files#diff-d91a6a26c84e56bc56b5270a3549ae7cL1]. But I recommend to keep current location because of backward compatibility
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list