[
https://issues.jboss.org/browse/JBDS-4637?page=com.atlassian.jira.plugin....
]
Vojtech Prusa commented on JBDS-4637:
-------------------------------------
[~ ctomc] Because the integration tests download the entire repo as zip and then import
each folder / quickstart as Maven -> Import -> Existing project, this process does
not distinguish if it should be buildable just verifies that the project is importable and
imported without errors.
So I suggest exclude "template" from integration tests, because if valid errors
would occur, errors in "template" would be duplicates.
What do you think [jkopriva]?
Failing quickstart WildFly-11 [template]
----------------------------------------
Key: JBDS-4637
URL:
https://issues.jboss.org/browse/JBDS-4637
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: project-examples
Affects Versions: 11.2.0.AM2
Environment:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
WF11
quickstartes 11.0.0.Final
Reporter: Vojtech Prusa
Assignee: Vojtech Prusa
Attachments: pom.xml
Automation fails because of error after template project is imported.
Test report:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
Solutions:
https://stackoverflow.com/questions/31835033/web-xml-is-missing-and-failo...
Updated pom.xml as attachment does no show errors after Project Maven -> Update
project ..
Idk if right solution is to change pom or generate web.xml with "Java EE Tools ->
Generate Deployment Descriptor Stub" in test.
Please comment recommendations [~n1hility] [~ctomc] [~trepel] [~sgilda] [~jkopriva]
Thank you.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)