[jira] Commented: (MEJB-33) Add support for fewer dependencies in client-jars
[ http://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189610#action_189610 ] Gabriel Guerrero commented on MEJB-33: -- Hey guys I had a lot of issues because of this, some class loading problems because one of my ejb-client was bringing to much unnecesary dependencies it was also very used in several projects so we endend excluding lots of libs everywhere, the work arround works, so could you guys add the workaround at least to usage guide in the site or FAQ, it will save many people a lot of time Thanks > Add support for fewer dependencies in client-jars > - > > Key: MEJB-33 > URL: http://jira.codehaus.org/browse/MEJB-33 > Project: Maven 2.x EJB Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Karsten Tinnefeld > > Given a scenario, where several application tiers are installed on different > servers, are realized as EJB3 applications, and packaged using maven. > When configuring an ejb module, I give dependencies to all dependency jars > that are used to implement the features. However, they are currently all > added as dependency to the client-jar artifacts as well, so that unused > libraries are deployed on client servers. > I'd like to mark dependencies as server-jar only, e.g. by an > clientJarExclusions configuration element to the plugin, which takes a set of > exclusion elements like the exclusions-element in a dependency. These > dependencies should behave as compile-scope in the server- and provided-scope > in the client-jars. -- 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
[jira] Commented: (MNG-2720) Multiproject dependencies not accurate for project.compileClasspathElements when run from root project
[ http://jira.codehaus.org/browse/MNG-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171746#action_171746 ] Gabriel Guerrero commented on MNG-2720: --- I have a problem with this fix, I have several projects, and I use and the ant plugin to run my app in debug mode, what i liked is that because the classes directories was included in the classpath I was able to run eclipse in debug mode for multi projects so I could change a classes in any of the projects and just run compile , know this doesnt work could it you guys add a flag to make it work the old way? > Multiproject dependencies not accurate for project.compileClasspathElements > when run from root project > -- > > Key: MNG-2720 > URL: http://jira.codehaus.org/browse/MNG-2720 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0.4 >Reporter: Jeff Genender >Assignee: John Casey > Fix For: 2.1.0, 3.0-alpha-3 > > > In a plugin I wrote (jspc), needs the dependency jars. It asks for this with > the request for the project.compileClasspathElements. In a multiproject > environment, when each project is built individually, it seems correct. > Example (when run with -X ina subproject dir) showing classpath: > /Users/mbp/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar > /Users/mbp/.m2/repository/taglibs/standard/1.1.2/standard-1.1.2.jar > /Users/mbp/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar > /Users/mbp/.m2/repository/tldtestapp/testexttld/1/testexttld-1.jar > <-NOTICE HERE - THIS IS AN ARTIFACT FROM ANOTHER SUBPROJECT > /Users/mbp/.m2/repository/javax/servlet/jstl/1.1.2/jstl-1.1.2.jar] > When it is run from the Top level/Root project...here is the output: > Users/mbp/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar > /Users/mbp/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar > /Users/mbp/.m2/repository/taglibs/standard/1.1.2/standard-1.1.2.jar > /Users/mbp/Desktop/jsp-example/TestTldProject/target/classes >INSTEAD > /Users/mbp/.m2/repository/javax/servlet/jstl/1.1.2/jstl-1.1.2.jar] > The second project has a dependency on the testexttld-1.jar because it > contains tag libs which must be wrapped in a jar. When run from a top level, > it uses the other project's classes directory instead of the JAR artifact. > WIth JSPC and taglibs, this makes it so it cannot work. If I have a > dependency on a jar, that jar should be the dependency as expected and not a > classes directory. For full explanation and example see here: > http://jira.codehaus.org/browse/MJSPC-4 -- 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
