You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2006/12/07 19:00:41 UTC
[jira] Updated: (MAVEN-1680) par files don't go to the
maven.dependency.classpath see similar problem:
http://jira.codehaus.org/browse/MAVEN-835
[ http://jira.codehaus.org/browse/MAVEN-1680?page=all ]
Wendy Smoak updated MAVEN-1680:
-------------------------------
Comment: was deleted
> par files don't go to the maven.dependency.classpath see similar problem: http://jira.codehaus.org/browse/MAVEN-835
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAVEN-1680
> URL: http://jira.codehaus.org/browse/MAVEN-1680
> Project: Maven 1.x
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira