[
https://issues.jboss.org/browse/CDITCK-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Muir closed CDITCK-192.
----------------------------
Fix Version/s: 1.1.0.CR1
Resolution: Done
> All test wars are invalid javaee artifacts since they have "Class-Path: null"
> manifest header
> ---------------------------------------------------------------------------------------------
>
> Key: CDITCK-192
> URL: https://issues.jboss.org/browse/CDITCK-192
> Project: CDI TCK
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Tests
> Affects Versions: 1.0.2.CR3
> Reporter: David Jencks
> Assignee: Pete Muir
> Fix For: 1.0.3.Final, 1.1.0.CR1
>
>
> cf javaee_platform-6_0-fr-spec.pdf EE.8.2.1:
> Only JAR format files or directories containing class files or resources to
> be loaded directly by a standard class loader should be the target of a
> Class-Path reference; such files are always named with a .jar extension. Top
> level JAR files that are processed by a deployment tool should not contain
> Class-Path entries; such entries would, by definition, reference other files
> external to the deployment unit. A deployment tool is not required to process
> such external references.
> 2
> So there should be no Class-Path header, and if there is it should only have
> .jar files in it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
