Bug 952136
| Summary: | Spring MVC archetype cannot be deployed using jboss-as:deploy | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Karel Piwko <kpiwko> |
| Component: | Spring | Assignee: | Tejas Mehta <tmehta> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Repel <trepel> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.0 | CC: | jowilson, kpiwko, mnovotny, myarboro, ppenicka, rruss |
| Target Milestone: | GA | ||
| Target Release: | 2.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-06-18 05:53:27 UTC | 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: | 914685 | ||
| Bug Blocks: | |||
|
Description
Karel Piwko
2013-04-15 09:36:31 UTC
Fred Bricon <fbricon> made a comment on jira JBIDE-12148 You need to request adding the new archetype to JDF [Stacks|https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml] at https://issues.jboss.org/browse/JDF The WFK BOM POMs need to be updated as well I imagine. Basically, the workflow is : - open JIRA on JDF - you PR or someone from JDF PR requested changes - JIRA is assigned to someone from JBDS/JBT QE. - Archetype will be tested in JBT/JBDS using property like -Dorg.jboss.examples.stacks.url=https://raw.github.com/forker/jdf-stack/commitId/stacks.yaml - Once QE vetted the changes, JIRA is reassigned to JDF for proper merging Should I release CR8 or final with the fix before sending PR to https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml? Also, with jboss-javaee-6.0-with-spring now available in community: http://search.maven.org/#search|ga|1|a%3Ajboss-javaee-6.0-with-spring, should the enterprise=false be update to use this? Tejas, the first step would indeed be to release CR8 or Final. Once it is on maven central, QE will validate and then PR to update stacks.yml should be sent. As for the latter, think it is up to you. IMHO such update will make archetype simpler and easier to maintain. I have released CR8, with jboss maven plugin version: 7.3.Final and also updated it to use jboss-javaee-6.0-with-spring bom when enterprise=false. It should be on maven central by tomorrow. Once its validated I will release 1.0.0.Final (because stacks.yaml contains only .Finals) and send PR as Fred suggested. Verified, project generated via org.jboss.spring.archetypes:spring-mvc-webapp:1.0.0.CR8 archetype can be deployed via `mvn jboss-as:deploy` to EAP 6.0.1.GA correctly. Marking as modified. This issue is verified an we are waiting for async upstream push of 1.0.0. Setting 2.2.0 as target version. Verified again with 1.0.0.Final version of archetype. Tomas Repel <trepel> updated the status of jira SNOWDROP-70 to Resolved Fred Bricon <fbricon> updated the status of jira JBIDE-12148 to Resolved Radim Hopp <rhopp> updated the status of jira JBIDE-12148 to Closed |