[ 
http://jira.codehaus.org/browse/MASPECTJ-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MASPECTJ-64.
----------------------------------

    Resolution: Not A Bug
      Assignee: Robert Scholte

First an answer to your question: yes: the classes under WEB-INF/classes are 
always loaded before the jars.

A maven-plugin is not capable of removing a dependency from the project. 
So in this case you have to set the scope to {{provided}} for those 
dependencies which are also part of the weaven dependencies.



> Class and resources weaved with the weaveDepedencies mecanism are present 
> both. One with the original code and another with the weaved code.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MASPECTJ-64
>                 URL: http://jira.codehaus.org/browse/MASPECTJ-64
>             Project: Mojo AspectJ Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: pkernevez
>            Assignee: Robert Scholte
>
> I use the mecanism with a war.
> My class and theire resources are add in the target/classes (and then in the 
> WEB-INF/classes) folder, but the original dependcies are keep and the classes 
> are also present in the WEB-INF/lib/XXX.jar. They are duplicated in a couple 
> versions.
> I don't know if the J2EE spec garantee that web-inf/classes are loaded first 
> to the web-inf/lib/xxx.jar but that's not a good thing.
> Tough when this jar contains hibernate mapping that cause and error during 
> the hibernate initialization according that hibernate doesn't accept 
> duplicated mapping files entries: 
> {code}Error creating bean with name 'sessionFactory' defined in class path 
> resource [jmonitoring-sample.xml]: Invocation of init method failed; nested 
> exception is org.hibernate.DuplicateMappingException: Duplicate class/entity 
> mapping org.jmonitoring.sample.main.ItemPO{code}
> The plugin should remove the www.jar from dependencies or provide a mecanism 
> for filtering the resources (*.hbm.xml in my example) when weaving 
> dependencies.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to