[
https://jira.codehaus.org/browse/MAVEN-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MAVEN-1680.
---------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> par files don't go to the maven.dependency.classpath see similar problem:
> http://jira.codehaus.org/browse/MAVEN-835
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAVEN-1680
> URL: https://jira.codehaus.org/browse/MAVEN-1680
> Project: Maven 1
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.0.2
> Environment: all
> Reporter: Juraj Burian
> Priority: Blocker
>
> According to EJB3 SPECIFICATION !!!!!. entity beans are stored in par-files,
> unfortunatelly par files (types) do not apperar in maven.dependency.classpath.
> My personal recomendation is to create variable containing a set of types
> that are added to the maven.dependency.classpath or remove all calls of
> method Dependency. isAddedToClasspath().
> I think that the world of extensions of "jar" archives is dynamic and that
> this kind of restriction is CONTRAPRODUCTIVE!
> Please please could you at least add this one type we (developers) need.
> -------------------------------------------------------------------------------------------------
> Thanks
> best regards
> J.Burian
> p.s. sorry for strong language ;)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
