Bug 899536 (JBPAPP6-31)
| Summary: | Spring and other jars in the eap6 repo | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Max Rydahl Andersen <max.andersen> | ||||||
| Component: | Maven Repository | Assignee: | Vladimir Dosoudil <dosoudil> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | unspecified | CC: | max.andersen, pgier, rajesh.rajasekaran | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | EAP 6.0.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-31 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-11-19 15:02:41 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Max Rydahl Andersen
2011-10-10 14:40:43 UTC
Docs QE Status: Added: NEW Link: Added: This issue relates to JBPAPP-7663 Attaching the list of jar files that are part of the maven repo and those that are packaged within the EAP zip distribution. The number of jar files in each distribution are: EAP Zip dist: 294 jars Maven repo: 924 jars (excluding source and javadocs) https://docspace.corp.redhat.com/docs/DOC-75666 states "The repository will include all jars necessary for development which is a superset of the jars required for application runtime deployment." But we also have a policy that if we ship a jar, we support it. So unless Support agrees to distribute these additional 630 jars, the maven repo should be in sync with the EAP distribution. Attachment: Added: mavenrepojarlist.txt Attachment: Added: zipdistjarlist.txt This should be resolved by JBPAPP-7663 which will include only the set of jars that are in AS + a few other things such as BOMs. just a comment "if we ship a jar, we support it" does not mean it cannot be included. There are many parts of AS7 that are shipped but we don't support for any other use than running the server. Similar here - these jars should be looked at as if they are necessary for correct build. Not for *usage* alone. in other words - it might be perfect ok a jar is included in the mvn repo and not in EAP. In JBPAPP-7663 we moved to an includes model, so we'll only include stuff in our list. That includes all EAP jars, plus there is a text file which can be updated manually to add any additional poms/jars. As I understand this issue, we don't need to include more artifacts to EAP6 repository than we have now in daily builds [1]: * build dependency of EAP (artifacts in dependency:list of EAP/AS) * all artifacts under org.jboss.as (incl. sub-groups) -- it's safe to have them all * all artifacts under org.jboss.spec (incl. sub-groups) -- it's safe to have them all You can validate it by checking maven-repository.zip in the Jenkins job [1] creating the maven repository and quickstarts. If you see any inconsistency and want to include or exclude any artifacts to/from the generated maven repository, please re-open the JIRA or send me a mail request. Multiple versions of particular artifacts will be checked. Non-latest ones could be removed if they're not necessary to have them in the repository zip. [1] https://hudson.qa.jboss.com/hudson/job/JBoss-EAP-6.0.x-Maven-Repository/ Docs QE Status: Removed: NEW |