[jira] Commented: (MASSEMBLY-206) Filtering does not work when using in fileSet inside moduleSet
[ http://jira.codehaus.org/browse/MASSEMBLY-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179769#action_179769 ] Helge Olav Aarstein commented on MASSEMBLY-206: --- Have a similar problem on a multi-module project using a re-usable assembly descriptor: Filtering works fine on elements across the modules, but the variables are not expanded on elements if mvn package is executed on the parent project. > Filtering does not work when using in fileSet inside moduleSet > -- > > Key: MASSEMBLY-206 > URL: http://jira.codehaus.org/browse/MASSEMBLY-206 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: win32 >Reporter: Liya Katz > Fix For: 2.2 > > > i have a descriptor : > > > com.cc:module1 > com.cc:module2 > com.cc:module3 > > > > > src/main > true > core > > conf/* > > > > false > > > and although there is "true", the copied sources are not > filtered. -- 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] Created: (MPIR-37) Dependency report fails on system-scope dependencies
Dependency report fails on system-scope dependencies
Key: MPIR-37
URL: http://jira.codehaus.org/browse/MPIR-37
Project: Maven 2.x Project Info Reports Plugin
Type: Bug
Versions: 2.0
Reporter: Helge Olav Aarstein
Dependency to local weblogic.jar causes the dependency project report to fail.
Error caused by following dependency setting in the pom.xml -file:
com.bea.weblogic
webservices
9.1.0
system
${wls910.server.lib}/weblogic.jar
If I put weblogic.jar into the repository the dependency report seems to work
fine, but then my compile fails (but that's a completely different story and
should not affect this problem).
Stacktrace follows:
[INFO] Generate "Dependencies" report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:386)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:351)
at
org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository(DependenciesReport.java:362)
at
org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:242)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:157)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
at
org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:802)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:47
--
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: (MPIR-37) Dependency report fails on system-scope dependencies
[ http://jira.codehaus.org/browse/MPIR-37?page=comments#action_65574 ]
Helge Olav Aarstein commented on MPIR-37:
-
Try downloading updated maven package (2.0.4 fixed the problem for me)
> Dependency report fails on system-scope dependencies
>
>
> Key: MPIR-37
> URL: http://jira.codehaus.org/browse/MPIR-37
> Project: Maven 2.x Project Info Reports Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Helge Olav Aarstein
> Assignee: Brett Porter
>
>
> Dependency to local weblogic.jar causes the dependency project report to
> fail.
> Error caused by following dependency setting in the pom.xml -file:
>
> com.bea.weblogic
> webservices
> 9.1.0
> system
> ${wls910.server.lib}/weblogic.jar
>
> If I put weblogic.jar into the repository the dependency report seems to work
> fine, but then my compile fails (but that's a completely different story and
> should not affect this problem).
> Stacktrace follows:
> [INFO] Generate "Dependencies" report.
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:386)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:351)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository(DependenciesReport.java:362)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:242)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:157)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
> at
> org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:802)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:47
--
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
