[jira] Closed: (MENFORCER-19) Add an option to enforce dependencyManagement
[
http://jira.codehaus.org/browse/MENFORCER-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MENFORCER-19.
Resolution: Won't Fix
With some flags set,
[maven-dependency-plugin|http://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html]
can be used to enforce dependencyManagement. A little verbose, but does the
job well.
{code:xml}
maven-dependency-plugin
analyze-dep-mgt
verify
true
false
{code}
> Add an option to enforce dependencyManagement
> -
>
> Key: MENFORCER-19
> URL: http://jira.codehaus.org/browse/MENFORCER-19
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: Carlos Sanchez
>
> Add something to the dependencyManagement section like
> true
> to make build fail if a subproject uses a different version
> Currently a subproject can specify the version of a dependency already
> defined in dependencyManagement, which is error prone
--
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: (MSHARED-169) *-SNAPSHOT.jar referenced in manifest as *-20101029.223815-3.jar
[ http://jira.codehaus.org/browse/MSHARED-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253981#action_253981 ] Neil Tingley commented on MSHARED-169: -- I think its still broken in maven 3. Have been having exactly the same problem. Adding false under didn't work - are the docs correct ? Will adding that config in the manifest section instead. > *-SNAPSHOT.jar referenced in manifest as *-20101029.223815-3.jar > > > Key: MSHARED-169 > URL: http://jira.codehaus.org/browse/MSHARED-169 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4 > Environment: Maven 2.2.1 and Maven 3.0. Linux build machine and > Windows xp development box >Reporter: Martin Jozef Jamszolik >Priority: Critical > > Build involves an EAR, WAR and JAR projects. > Steps to reproduce: > 1)project business.jar hold dependency on project security.jar > 2)security.jar is accessible only from remote repository (important!) and as > an snapshot. ( ex security-10.04.20-20101029.223815-3.jar) > 3)business.jar adds classpath entries to manifest as > security-10.04.20-20101029.223815-3.jar. > 4)business.jar and security.jar get packaged in an EAR as > business-SNAPSHOT.jar and security-SNAPSHOT.jar. > On startup application fails to load due to unresolved compilation errors. > security-10.04.20-20101029.223815-3.jar cannot be found. > I believe that the entry in the manifest should have been > security-SNAPSHOT.jar to match the actual jar that's copied into the ear or > war. -- 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: (MSHARED-169) *-SNAPSHOT.jar referenced in manifest as *-20101029.223815-3.jar
[ http://jira.codehaus.org/browse/MSHARED-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253982#action_253982 ] Neil Tingley commented on MSHARED-169: -- BTW all is fine in maven 2.2.1 however have forced non-unique snapshots in so perhaps its always going to behave like that. > *-SNAPSHOT.jar referenced in manifest as *-20101029.223815-3.jar > > > Key: MSHARED-169 > URL: http://jira.codehaus.org/browse/MSHARED-169 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4 > Environment: Maven 2.2.1 and Maven 3.0. Linux build machine and > Windows xp development box >Reporter: Martin Jozef Jamszolik >Priority: Critical > > Build involves an EAR, WAR and JAR projects. > Steps to reproduce: > 1)project business.jar hold dependency on project security.jar > 2)security.jar is accessible only from remote repository (important!) and as > an snapshot. ( ex security-10.04.20-20101029.223815-3.jar) > 3)business.jar adds classpath entries to manifest as > security-10.04.20-20101029.223815-3.jar. > 4)business.jar and security.jar get packaged in an EAR as > business-SNAPSHOT.jar and security-SNAPSHOT.jar. > On startup application fails to load due to unresolved compilation errors. > security-10.04.20-20101029.223815-3.jar cannot be found. > I believe that the entry in the manifest should have been > security-SNAPSHOT.jar to match the actual jar that's copied into the ear or > war. -- 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: (MWAR-164) Support for specifying which encoding to use when filtering resources
[
http://jira.codehaus.org/browse/MWAR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254557#action_254557
]
Florian Fray commented on MWAR-164:
---
Hi!
Has somebody had the chance to review this patch ?
Best regards,
Florian
> Support for specifying which encoding to use when filtering resources
> -
>
> Key: MWAR-164
> URL: http://jira.codehaus.org/browse/MWAR-164
> Project: Maven 2.x WAR Plugin
> Issue Type: Improvement
>Affects Versions: 2.1-alpha-1
>Reporter: kai lilleby
> Fix For: 2.2
>
> Attachments: MWAR-164-maven-war-plugin.patch
>
>
> Quoting Hervé:
> {quote}
> Maven filtering provides an encoding parameter to set encoding used when
> reading/writing files. But war plugin uses null value, which means platform
> encoding... Sorry, encoding support won't be totally "free" ;)
> I added TODOs in the code.
> For web.xml and container config XML file, I set encoding to UTF-8, which is a
> better default value than platform encoding.
> For other filtered resources, you'll need to add an encoding attribute to
> o.a.m.model.Resource class, to let the user define which encoding he wants to
> use when filtering. Perhaps using project.build.sourceEncoding as a default
> value is a good idea.
> Seems like this is worth a Jira issue to track this new feature.
> {quote}
--
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-220) IOException: Failed to open file During Site generation
IOException: Failed to open file During Site generation
---
Key: MPIR-220
URL: http://jira.codehaus.org/browse/MPIR-220
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.3.1
Environment: Linux (Ubuntu)
java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-27-generic", arch: "amd64", family: "unix"
Reporter: Karl Heinz Marbaise
I have build which is working completely fine which means mvn clean package
works perfect.
If i try to do a mvn site i got the following Exception message:
{code}[INFO] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.3.1
[ERROR] IOException: Failed to open file
/home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
opening zip file
java.util.zip.ZipException: Failed to open file
/home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
opening zip file
at org.apache.maven.shared.jar.JarAnalyzer.(JarAnalyzer.java:109)
at
org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:273)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1374)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:544)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:271)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:206)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:165)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:159)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:122)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:114)
at java.util.jar.JarFile.(JarFile.java:135)
at java.util.jar.JarFile.(JarFile.java:99)
at org.apache.maven
[jira] Commented: (MPIR-220) IOException: Failed to open file During Site generation
[
http://jira.codehaus.org/browse/MPIR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254568#action_254568
]
Karl Heinz Marbaise commented on MPIR-220:
--
What i missed to say is that this project has not been installed till that
point. So no mvn install has been run before.
> IOException: Failed to open file During Site generation
> ---
>
> Key: MPIR-220
> URL: http://jira.codehaus.org/browse/MPIR-220
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.3.1
> Environment: Linux (Ubuntu)
> java -version
> java version "1.6.0_22"
> Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-27-generic", arch: "amd64", family: "unix"
>Reporter: Karl Heinz Marbaise
>
> I have build which is working completely fine which means mvn clean package
> works perfect.
> If i try to do a mvn site i got the following Exception message:
> {code}[INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.3.1
> [ERROR] IOException: Failed to open file
> /home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
> opening zip file
> java.util.zip.ZipException: Failed to open file
> /home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
> opening zip file
> at org.apache.maven.shared.jar.JarAnalyzer.(JarAnalyzer.java:109)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:273)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1374)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:544)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:271)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:206)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:165)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:159)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:122)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org
[jira] Updated: (MASSEMBLY-527) [REGRESSION] Sharing assembly descriptors doesn't work any more
[ http://jira.codehaus.org/browse/MASSEMBLY-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-527: -- Fix Version/s: (was: 2.3) 2.2.1 > [REGRESSION] Sharing assembly descriptors doesn't work any more > --- > > Key: MASSEMBLY-527 > URL: http://jira.codehaus.org/browse/MASSEMBLY-527 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Dennis Lundberg >Assignee: John Casey > Fix For: 2.2.1 > > Attachments: shared-assembly-descriptor.zip > > > When fixing the documentation issue in MASSEMBLY-519 I discovered that > sharing assembly descriptors in that way doesn't work in 2.2. > Using the corrected (as described in MASSEMBLY-519) example at > http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html > this fails in 2.2 but works in 2.2-beta-5. See attached demo project. > First run 'mvn install' on my-assembly-descriptor > then run 'mvn package' on my-project -- 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] Updated: (MASSEMBLY-512) Plugin documentation refers to "Maven 2"
[ http://jira.codehaus.org/browse/MASSEMBLY-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-512: -- Fix Version/s: (was: 2.3) 2.2.1 > Plugin documentation refers to "Maven 2" > > > Key: MASSEMBLY-512 > URL: http://jira.codehaus.org/browse/MASSEMBLY-512 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.2.1 > > Attachments: MNG-4868-maven-antrun-plugin.patch, > MNG-4868-maven-archetype.patch, MNG-4868-maven-assembly-plugin.patch, > MNG-4868-maven-compiler-plugin.patch, MNG-4868-maven-reactor-plugin.patch > > > Documentation for these plugins makes them appear specific to Maven 2 - which > at this point in time, makes them appear to NOT be for Maven 3. > Plugins: antrun, archetype, assembly, compiler, reactor -- 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] Updated: (MASSEMBLY-516) Error in Example for sharing-descriptors?
[ http://jira.codehaus.org/browse/MASSEMBLY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-516: -- Fix Version/s: (was: 2.3) 2.2.1 > Error in Example for sharing-descriptors? > - > > Key: MASSEMBLY-516 > URL: http://jira.codehaus.org/browse/MASSEMBLY-516 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug > Environment: - >Reporter: Knut Pape >Assignee: John Casey > Fix For: 2.2.1 > > > On Page > http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html > It says that the assembly file from a jar on the class-path shoulld be > included the following way: > >myassembly.xml > > This didn't work for me. After some fidling (I'm pritty sure that the problem > was not a spelling mistake) I came to the following solution: Instead of > referencing the assembly by filename I referenced it by it's ID and voila - > it worked: > > my-assembly-descriptor-id > -- 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] Updated: (MASSEMBLY-514) The value for prerequisites/maven in the pom.xml should be 2.2.1 for Maven Assembly Plugin 2.2
[
http://jira.codehaus.org/browse/MASSEMBLY-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-514:
--
Fix Version/s: (was: 2.3)
2.2.1
> The value for prerequisites/maven in the pom.xml should be 2.2.1 for Maven
> Assembly Plugin 2.2
> --
>
> Key: MASSEMBLY-514
> URL: http://jira.codehaus.org/browse/MASSEMBLY-514
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Guillaume Husta
>Assignee: John Casey
>Priority: Minor
> Fix For: 2.2.1
>
>
> The 2.2 version of the Assembly Plugin doesn't work with Maven 2.0.11.
> The pom.xml indicates :
> {code:xml}
>
> 2.0.11
>
>
> 1.1.2
> 2.2.1
> true
>
> {code}
> When I invoke the 'single' goal (jar-with-dependencies) in the package phase
> of a module, I get an error when working with Maven 2.0.11.
> It seems to already have been fixed in the next version.
> See :
> [http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/pom.xml?r1=1021399&r2=1021398&pathrev=1021399]
--
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] Updated: (MASSEMBLY-519) Documentation problem: description of how to share assemble descriptors is wrong
[ http://jira.codehaus.org/browse/MASSEMBLY-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-519: -- Fix Version/s: (was: 2.3) 2.2.1 > Documentation problem: description of how to share assemble descriptors is > wrong > > > Key: MASSEMBLY-519 > URL: http://jira.codehaus.org/browse/MASSEMBLY-519 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Thomas Arand >Assignee: Dennis Lundberg > Fix For: 2.2.1 > > > The page > http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html > describes the way to access the shared descriptor like follows: > > > > myassembly.xml > > > Due to the layout of the shared assembly descriptor project (myassembly.xml > is stored in src/main/resources/assemblies/) this is wrong. It must be > > > > assemblies/myassembly.xml > > -- 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] Updated: (MASSEMBLY-218) repository does not handle classified artifacts properly
[
http://jira.codehaus.org/browse/MASSEMBLY-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-218:
--
Description:
I am creating a simple repository with a project that contains classified
dependencies (obfuscated jars):
true test
repo
The assembly plugins generates a weird structure based on that: shared
{noformat}
|-- bar
| `-- foo-bar
| |-- 5.10.4-20070613.122033-2
| | |-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar
| | |-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar.md5
| | `-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar.sha1
| |-- 5.10.4-SNAPSHOT
| | |-- foo-bar-5.10.4-SNAPSHOT.pom
| | |-- foo-bar-5.10.4-SNAPSHOT.pom.md5
| | `-- foo-bar-5.10.4-SNAPSHOT.pom.sha1
| |-- maven-metadata-central.xml
| |-- maven-metadata-central.xml.md5
| |-- maven-metadata-central.xml.sha1
| |-- maven-metadata.xml
| |-- maven-metadata.xml.md5
| `-- maven-metadata.xml.sha1
{noformat}
Non classified dependencies are stored properly.
was:
I am creating a simple repository with a project that contains classified
dependencies (obfuscated jars):
true test
repo
The assembly plugins generates a weird structure based on that: shared
|-- bar
| `-- foo-bar
| |-- 5.10.4-20070613.122033-2
| | |-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar
| | |-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar.md5
| | `-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar.sha1
| |-- 5.10.4-SNAPSHOT
| | |-- foo-bar-5.10.4-SNAPSHOT.pom
| | |-- foo-bar-5.10.4-SNAPSHOT.pom.md5
| | `-- foo-bar-5.10.4-SNAPSHOT.pom.sha1
| |-- maven-metadata-central.xml
| |-- maven-metadata-central.xml.md5
| |-- maven-metadata-central.xml.sha1
| |-- maven-metadata.xml
| |-- maven-metadata.xml.md5
| `-- maven-metadata.xml.sha1
Non classified dependencies are stored properly.
> repository does not handle classified artifacts properly
>
>
> Key: MASSEMBLY-218
> URL: http://jira.codehaus.org/browse/MASSEMBLY-218
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
>Reporter: Stephane Nicoll
> Fix For: 2.3
>
>
> I am creating a simple repository with a project that contains classified
> dependencies (obfuscated jars):
> true test
> repo
> The assembly plugins generates a weird structure based on that: shared
> {noformat}
> |-- bar
> | `-- foo-bar
> | |-- 5.10.4-20070613.122033-2
> | | |-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar
> | | |-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar.md5
> | | `-- foo-bar-5.10.4-20070613.122033-2-obfuscated.jar.sha1
> | |-- 5.10.4-SNAPSHOT
> | | |-- foo-bar-5.10.4-SNAPSHOT.pom
> | | |-- foo-bar-5.10.4-SNAPSHOT.pom.md5
> | | `-- foo-bar-5.10.4-SNAPSHOT.pom.sha1
> | |-- maven-metadata-central.xml
> | |-- maven-metadata-central.xml.md5
> | |-- maven-metadata-central.xml.sha1
> | |-- maven-metadata.xml
> | |-- maven-metadata.xml.md5
> | `-- maven-metadata.xml.sha1
> {noformat}
> Non classified dependencies are stored properly.
--
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] Closed: (MASSEMBLY-535) [Regression] Filtered fileSet are not filtered since version 2.2
[
http://jira.codehaus.org/browse/MASSEMBLY-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MASSEMBLY-535.
-
Resolution: Duplicate
> [Regression] Filtered fileSet are not filtered since version 2.2
>
>
> Key: MASSEMBLY-535
> URL: http://jira.codehaus.org/browse/MASSEMBLY-535
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: Maven 2.2.1 & 3.0.1, maven-assembly-plugin 2.2
>Reporter: Eric Chatellier
>Priority: Critical
> Attachments: build.cmd
>
>
> Since maven-assembly-plugin version 2.2 (stable version)
> assembly descriptor containing filtered resources
> doesn't filters resources anymore.
> Here is our configuration :
>
> src/main/assembly
>
> true
> 0755
>
> go.sh
> go.bat
>
>
> Script containts following variables:
> java -jar ${project.build.finalName}.${project.packaging}
> Swithing back to version 2.2-beta-5 is a workaround for now.
--
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] Updated: (MASSEMBLY-538) filtering broken in files containing '@'
[
http://jira.codehaus.org/browse/MASSEMBLY-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-538:
--
Fix Version/s: (was: 2.3)
2.2.1
> filtering broken in files containing '@'
>
>
> Key: MASSEMBLY-538
> URL: http://jira.codehaus.org/browse/MASSEMBLY-538
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: mvn -v
> Apache Maven 2.2.1 (rNON-CANONICAL_2010-08-13_17-44_abuild; 2010-08-13
> 19:44:44+0200)
> Java version: 1.6.0_22
> Java home: /usr/lib64/jvm/java-1.6.0-sun-1.6.0/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux" version: "2.6.34.7-0.7-desktop" arch: "amd64" Family: "unix"
>Reporter: Alexander Rettig
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.2.1
>
> Attachments: filter-test-1.0.zip
>
>
> Files containing the '@' sign as eg within e-mail URLs are only filtered up
> to the occurrence of this sign.
> To check this, unpack the attached ZIP, cd into the created directory
> 'filter-test-01' and run
> mvn assembly:single
> The created target/filter-test-1.0-filtertest.zip contains a README, which
> has only the first occurrence of ${project.artifactId} replaced, but not the
> second one.
--
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: (MASSEMBLY-538) filtering broken in files containing '@'
[
http://jira.codehaus.org/browse/MASSEMBLY-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254594#action_254594
]
Dennis Lundberg commented on MASSEMBLY-538:
---
Updated to maven-filtering 1.0-SNAPSHOT in
[r1066942|http://svn.apache.org/viewvc?view=revision&revision=1066942].
New 2.2.1-SNAPSHOT of the assembly plugin deployed. Please test it.
> filtering broken in files containing '@'
>
>
> Key: MASSEMBLY-538
> URL: http://jira.codehaus.org/browse/MASSEMBLY-538
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: mvn -v
> Apache Maven 2.2.1 (rNON-CANONICAL_2010-08-13_17-44_abuild; 2010-08-13
> 19:44:44+0200)
> Java version: 1.6.0_22
> Java home: /usr/lib64/jvm/java-1.6.0-sun-1.6.0/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux" version: "2.6.34.7-0.7-desktop" arch: "amd64" Family: "unix"
>Reporter: Alexander Rettig
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.2.1
>
> Attachments: filter-test-1.0.zip
>
>
> Files containing the '@' sign as eg within e-mail URLs are only filtered up
> to the occurrence of this sign.
> To check this, unpack the attached ZIP, cd into the created directory
> 'filter-test-01' and run
> mvn assembly:single
> The created target/filter-test-1.0-filtertest.zip contains a README, which
> has only the first occurrence of ${project.artifactId} replaced, but not the
> second one.
--
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] Closed: (MASSEMBLY-374) useProjectArtifact is missing from XSD file
[
http://jira.codehaus.org/browse/MASSEMBLY-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MASSEMBLY-374.
-
Resolution: Fixed
Fix Version/s: 2.2
In the 1.1.2 xsd this has been fixed.
http://maven.apache.org/xsd/assembly-1.1.2.xsd
> useProjectArtifact is missing from XSD file
> ---
>
> Key: MASSEMBLY-374
> URL: http://jira.codehaus.org/browse/MASSEMBLY-374
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Environment: N/A
>Reporter: Chris Graham
> Fix For: 2.2
>
>
> The field useProjectArtifact is missing from the following XSD files:
> http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd
> http://maven.apache.org/xsd/assembly-1.0.0.xsd
> I found a reference to it in:
> http://books.sonatype.com/maven-book/reference/assemblies.html
> Here is a working example that uses it:
>
>
>
>
> zip
>
> false
>
>
>
>
> ${artifact.artifactId}.${artifact.extension}
> false
>
>
>
> There are other missing attributes (useProjectAttachments at least) as well.
> Using these XSD files to validate assembly xml files that use these fields
> will incorrectly fail.
> -Chris
--
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] Closed: (MASSEMBLY-381) Classpath entry of MANIFEST breaks jar filenames
[ http://jira.codehaus.org/browse/MASSEMBLY-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MASSEMBLY-381. - Resolution: Not A Bug The attached manifest is correct according to the JAR specification: "No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE)." See http://download.oracle.com/javase/1.4.2/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files > Classpath entry of MANIFEST breaks jar filenames > > > Key: MASSEMBLY-381 > URL: http://jira.codehaus.org/browse/MASSEMBLY-381 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Reporter: Alexander > Attachments: MANIFEST.MF > > > See attached MANIFEST for an example. > Solution: Add each jar file on a newline, and rename jar files which are > longer than 72 chars. -- 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] Closed: (MASSEMBLY-472) Doc includes gz but plugin doesn't support it
[ http://jira.codehaus.org/browse/MASSEMBLY-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MASSEMBLY-472. - Resolution: Fixed Fix Version/s: 2.2.1 Assignee: Dennis Lundberg Fixed in [r1066980|http://svn.apache.org/viewvc?view=revision&revision=1066980]. > Doc includes gz but plugin doesn't support it > -- > > Key: MASSEMBLY-472 > URL: http://jira.codehaus.org/browse/MASSEMBLY-472 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-5 >Reporter: Benson Margulies >Assignee: Dennis Lundberg > Fix For: 2.2.1 > > > Doc mentions gz, but using it results in > [INFO] Failed to create assembly: Unable to obtain archiver for extension 'gz' -- 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] Closed: (MASSEMBLY-465) unable to customize manifest while specifying my own descriptor file
[
http://jira.codehaus.org/browse/MASSEMBLY-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MASSEMBLY-465.
-
Resolution: Not A Bug
Creating a zip format assembly will never include a manifest. Only jar format
assemblies can have a manifest.
> unable to customize manifest while specifying my own descriptor file
>
>
> Key: MASSEMBLY-465
> URL: http://jira.codehaus.org/browse/MASSEMBLY-465
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-5
> Environment: windows
>Reporter: Elisha Ebenezer
>
> I've configured my maven-jar-plugin and maven-assembly-plugin to
> add 'lib/' prefix to Classpath entries in the manifest file for
> project-artifact jar. as below
>
>
>
> true
> lib/
>
>
>
> I've created my own assembly descriptor to do:
> 1. Place project artifact in / folder
> 2. Place all the dependencies (excluding project artifact) in /lib folder
>
> dist
>
> zip
>
>
>
> ${project.build.directory}
> /
>
> *.jar
>
>
>
>
>
> false
> lib
>
>
>
> I expected the following behavior:
> 1. artifact jar in build directory should have manifest as mentioned in the
> arhive configuration.
> 2. artifact jar in assembly jar should also have manifest as mentioned above.
> BUT, I observed the following:
> 1. artifact jar in build directory is* having manifest as mentioned in
> archive config.
> 2. artifact jar in assembly is *NOT* having the manifest as mentioned.
>a. classpath has ONLY compile time dependencies and NOT runtime
> dependencies
>b. And also, lib prefix is NOT present.
> I'm not sure whether I've got my descriptor wrong or whether there is some
> serious bug in the plugin. Please investigate.
>
--
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] Closed: (MASSEMBLY-500) Embedded error: Unrecognised tag: 'files' (position: START_TAG seen ...\n\n\n... @9:8)
[ http://jira.codehaus.org/browse/MASSEMBLY-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MASSEMBLY-500. Resolution: Cannot Reproduce Assignee: John Casey > Embedded error: Unrecognised tag: 'files' (position: START_TAG seen > ...\n\n\n... @9:8) > > > Key: MASSEMBLY-500 > URL: http://jira.codehaus.org/browse/MASSEMBLY-500 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Reporter: Dayashankar >Assignee: John Casey > Attachments: assembly.xml > > > Hi team, > I'm using attached assembly.xml file and while doing mvn assembly:assembly is > resulting in following error: > [INFO] Error reading descriptor > Embedded error: Unrecognised tag: 'files' (position: START_TAG seen > ...\n\n\n... @9:8) > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error reading > descriptor > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error reading > descriptor > at > org.apache.maven.plugin.assembly.AssemblyMojo.readAssembly(AssemblyMojo.java:238) > at > org.apache.maven.plugin.assembly.AssemblyMojo.execute(AssemblyMojo.java:144) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > ... 17 more > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: > Unrecognised tag: 'files' (position: START_TAG seen > ...\n\n\n... @9:8) > at > org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.parseAssembly(AssemblyXpp3Reader.java:371) > at > org.apache.maven.plugins.assembly.model.io.xpp3.AssemblyXpp3Reader.read(AssemblyXpp3Reader.java:982) > at > org.apache.maven.plugin.assembly.AssemblyMojo.readAssembly(AssemblyMojo.java:230) -- 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] Updated: (MASSEMBLY-510) leading period ('.') added to directory names
[
http://jira.codehaus.org/browse/MASSEMBLY-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-510:
-
Fix Version/s: 2.2.1
Assignee: John Casey
This should be a relatively simple fix. Time permitting I'll try to get it done
for 2.2.1 release.
> leading period ('.') added to directory names
> -
>
> Key: MASSEMBLY-510
> URL: http://jira.codehaus.org/browse/MASSEMBLY-510
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: Windows XP, SP3
> Maven 2.2.1
> Maven Assembly 2.2
>Reporter: KP
>Assignee: John Casey
> Fix For: 2.2.1
>
> Attachments: dist.xml, pom.xml
>
>
> $ cat dist.xml
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
> dist
>
> zip
>
>
>
>
>
> ${project.basedir}/../paper
>
>
> ${project.basedir}/../boots
>
>
>
>
> $ mvn clean assembly:assembly
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building oracle-sql-assembly
> [INFO]task-segment: [clean]
> [INFO]
>
> [INFO] [clean:clean {execution: default-clean}]
> [INFO] Deleting directory F:\test-assembly\target
> [INFO]
>
> [INFO] Building oracle-sql-assembly
> [INFO]task-segment: [assembly:assembly] (aggregator-style)
> [INFO]
>
> [INFO] Preparing assembly:assembly
> [INFO]
>
> [INFO] Building oracle-sql-assembly
> [INFO]
>
> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> [INFO] [assembly:assembly {execution: default-cli}]
> [INFO] Reading assembly descriptor: src/main/assembly/dist.xml
> [INFO] Building zip:
> F:\test-assembly\target\test-assembly-3.1-SNAPSHOT-dist.zip
> [INFO]
>
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Mon Oct 11 15:34:37 EDT 2010
> [INFO] Final Memory: 18M/45M
> [INFO]
>
> $ unzip -l target/test-assembly-dist.zip
> Archive: target/test-assembly-dist.zip
> Length DateTimeName
> - -- -
> 0 10-11-2010 15:34 test-assembly/
> 0 10-11-2010 15:27 test-assembly/.paper/
> 0 10-11-2010 15:27 test-assembly/.paper/random.txt
> 0 10-11-2010 15:27 test-assembly/.boots/
> 0 10-11-2010 15:27 test-assembly/.boots/boots.txt
> - ---
> 0 5 files
> Do you notice the '.paper' and '.boots' directories? It should just be
> 'paper' and 'boots', if I'm understanding it correctly.
> I tried other versions of the plugin (e.g., beta-4), I tried removing
> "${project.basedir}/".
> No go. :(
> P.S. If someone points me in the right direction, like a class name, I'll
> write a test case.
--
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] Updated: (MASSEMBLY-528) FileSet does not support filtering (again)
[ http://jira.codehaus.org/browse/MASSEMBLY-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MASSEMBLY-528: - Fix Version/s: 2.2.1 Assignee: John Casey I'll try to get this one fixed for 2.2.1 as well. > FileSet does not support filtering (again) > -- > > Key: MASSEMBLY-528 > URL: http://jira.codehaus.org/browse/MASSEMBLY-528 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Maik Richey >Assignee: John Casey >Priority: Critical > Fix For: 2.2.1 > > Attachments: MASSEMBLY-528_sample.zip > > > After switching to version 2.2 of the Assembly Plugin filtering for FileSets > does not work again as in versions prior to 2.2-beta-3. > Can anybody confirm this issue? -- 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] Updated: (MASSEMBLY-524) Make recommended goal usage more explicit; separate non-deprecated goals from deprecated ones explicitly
[ http://jira.codehaus.org/browse/MASSEMBLY-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MASSEMBLY-524: - Fix Version/s: 2.2.1 Assignee: John Casey This is probably a documentation issue at least until 2.3, when we can probably remove the deprecated mojos altogether. I'll try to get it done for 2.2.1. > Make recommended goal usage more explicit; separate non-deprecated goals from > deprecated ones explicitly > > > Key: MASSEMBLY-524 > URL: http://jira.codehaus.org/browse/MASSEMBLY-524 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: John Casey >Assignee: John Casey > Fix For: 2.2.1 > > > currently, the deprecation notices / warnings dominate any list of goals in > the assembly plugin, largely owing to their large number. > We need to review the documents and be more direct about telling the user > which goals *should* be used. -- 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] Closed: (MASSEMBLY-475) Flattening directories in file sets
[ http://jira.codehaus.org/browse/MASSEMBLY-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MASSEMBLY-475. Resolution: Duplicate Assignee: John Casey This issue is contained within the larger issue MASSEMBLY-45 > Flattening directories in file sets > --- > > Key: MASSEMBLY-475 > URL: http://jira.codehaus.org/browse/MASSEMBLY-475 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Andrew Rampulla >Assignee: John Casey > > A feature I would like is to be able to specify a fileSet such that I specify > a root directory X and an include pattern of "a/*/target/*.war" and have it > populate the archive with a flattened directory. > For example: > My source structure > a/test1/target/test1.war > a/test2/target/test2.war > Desired output archive: > test1.war > test2.war > This way I can just include everything I want from a subdirectory into my > distribution archive. -- 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] Updated: (MASSEMBLY-371) Converting line endings corrupts ISO-8859-1 files when platform encoding is UTF-8
[ http://jira.codehaus.org/browse/MASSEMBLY-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-371: -- Affects Version/s: 2.2 > Converting line endings corrupts ISO-8859-1 files when platform encoding is > UTF-8 > - > > Key: MASSEMBLY-371 > URL: http://jira.codehaus.org/browse/MASSEMBLY-371 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-2, 2.2 > Environment: Linux with platform encoding set to UTF-8 >Reporter: Håvard Wigtil > Attachments: assembly-encoding.zip > > > Converting line endings for a text file encoded in ISO-8859-1 replaces any > character in the set above ASCII with the three characters ï¿. > What happens is that the file to be converted is read as text in the platform > encoding (seems to be method readFile in class FileFormatter), and when the > platform encoding is UTF-8, any non-ASCII character from ISO-8859-1 is > converted to the UTF-8 character "�" (i.e. the placeholder for unknown > / broken character). > I've attached a small sample project that shows this problem on Linux with > platform encoding set to UTF-8. > I see two possible fixes for this, one is to read the file as bytes and do a > search /replace for line endings, and the other is to be able to specify > encoding for a fileset or file. -- 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] Closed: (MASSEMBLY-525) Ant Tokens can now be multi-line when filtering - regression from 2.2-beta-5
[
http://jira.codehaus.org/browse/MASSEMBLY-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MASSEMBLY-525.
-
Resolution: Duplicate
> Ant Tokens can now be multi-line when filtering - regression from 2.2-beta-5
>
>
> Key: MASSEMBLY-525
> URL: http://jira.codehaus.org/browse/MASSEMBLY-525
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Ryan Lea
> Attachments: assembly-filter-test.zip
>
>
> I've looked through existing issues and cannot find anything similar.
> In 2.2-beta-5 I was able to specify in scripts
> {code}
> @echo off
> java ${project.build.finalName}.jar
> {code}
> with filtering turned on for the final name. However, 2.2 appears to have
> allowed for ant tokens '@' to be carried over multiple lines. I don't think
> this is expected behaviour.
> I've attached a small test project with two files to demonstrate the case.
--
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] Updated: (MASSEMBLY-534) Doc unclear on descriptor refs
[ http://jira.codehaus.org/browse/MASSEMBLY-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-534: -- Fix Version/s: 2.2.1 > Doc unclear on descriptor refs > -- > > Key: MASSEMBLY-534 > URL: http://jira.codehaus.org/browse/MASSEMBLY-534 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Benson Margulies > Fix For: 2.2.1 > > Attachments: MASSEMBLY-534.patch, MASSEMBLY-534.patch > > > The param doc for descriptor refs makes it sound like they can *only* > reference the builtins. > I'll attach a patch to clarify it. -- 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] Updated: (MASSEMBLY-540) Web site uses the 1.1.0.xsd but 1.1.2 recommended
[ http://jira.codehaus.org/browse/MASSEMBLY-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-540: -- Fix Version/s: 2.2.1 > Web site uses the 1.1.0.xsd but 1.1.2 recommended > - > > Key: MASSEMBLY-540 > URL: http://jira.codehaus.org/browse/MASSEMBLY-540 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: all >Reporter: Karl Heinz Marbaise > Fix For: 2.2.1 > > Attachments: patch-xsd.diff > > > On The [Web > Site|http://maven.apache.org/plugins/maven-assembly-plugin/index.html] is > stated that starting with 2.2-beta-6 the > http://maven.apache.org/xsd/assembly-1.1.2.xsd (for version 2.2-beta-6 and > higher) should be used but all examples are using 1.1.0.xsd instead. > I have attached a patch which contains fixes for the web-site. I'm not sure > if the integration tests and the resources assemblies should be updated as > well. -- 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] Updated: (MASSEMBLY-541) XSD for component
[ http://jira.codehaus.org/browse/MASSEMBLY-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-541: -- Fix Version/s: 2.2.1 I'm not sure if there's a link somewhere on the site, but the XSD's for components can be found in the same place as the ones for assemblies. We should add a link to the site if there isn't one. http://maven.apache.org/xsd/component-1.1.2.xsd > XSD for component > - > > Key: MASSEMBLY-541 > URL: http://jira.codehaus.org/browse/MASSEMBLY-541 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2 > Environment: all >Reporter: Karl Heinz Marbaise > Fix For: 2.2.1 > > > I couldn't find any XSD's for the components. Based on the Modello the build > process will create one but it seemed to me that it's not available or i > oversight something. -- 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] Updated: (MASSEMBLY-334) Can not generate class-path from Manifest
[
http://jira.codehaus.org/browse/MASSEMBLY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-334:
--
Description:
I have a maven's projet multi-module.
I have a problem when i launch mvn package assembly:assembly
In the Manifest file, the class path does not generated.
Pom project
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.ipsis.pacha
Pacha
pom
1.0-SNAPSHOT
PACHA
maven-antrun-plugin
print-maven-runtime-classpath
compile
run
print-maven-test-classpath
test-compile
run
maven-compiler-plugin
1.6
1.6
512m
1024m
true
true
true
${JAVA_HOME}\bin\javac.exe
1.6
true
maven-deploy-plugin
true
org.apache.maven.plugins
maven-release-plugin
deploy
maven-surefire-plugin
maven-eclipse-plugin
2.0
/classes
false
org.eclipse.jdt.launching.JRE_CONTAINER
maven-site-plugin
fr
ISO-8859-1
ISO-8859-1
[jira] Commented: (MASSEMBLY-545) While loading multiple Filter files, already known filter values are not applied (see MSHARED-177)
[ http://jira.codehaus.org/browse/MASSEMBLY-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254610#action_254610 ] Dennis Lundberg commented on MASSEMBLY-545: --- Please try the 2.2.1-SNAPSHOT and tell us if it solves your problem. > While loading multiple Filter files, already known filter values are not > applied (see MSHARED-177) > -- > > Key: MASSEMBLY-545 > URL: http://jira.codehaus.org/browse/MASSEMBLY-545 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Daniel Mohni > Fix For: 2.2.1 > > > Fix has been submitted to maven-filtering project. > MASSEMBLY shoud update to new version as soon it is released -- 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] Updated: (MASSEMBLY-545) While loading multiple Filter files, already known filter values are not applied (see MSHARED-177)
[ http://jira.codehaus.org/browse/MASSEMBLY-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-545: -- Fix Version/s: 2.2.1 > While loading multiple Filter files, already known filter values are not > applied (see MSHARED-177) > -- > > Key: MASSEMBLY-545 > URL: http://jira.codehaus.org/browse/MASSEMBLY-545 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Daniel Mohni > Fix For: 2.2.1 > > > Fix has been submitted to maven-filtering project. > MASSEMBLY shoud update to new version as soon it is released -- 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] Closed: (MASSEMBLY-377) Maven Assembly Plugin XSD link is broken
[ http://jira.codehaus.org/browse/MASSEMBLY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MASSEMBLY-377. - Resolution: Fixed This has been fixed now. > Maven Assembly Plugin XSD link is broken > > > Key: MASSEMBLY-377 > URL: http://jira.codehaus.org/browse/MASSEMBLY-377 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Reporter: Asaf Mesika >Priority: Minor > Attachments: mngsite-74.patch > > > The link to the Maven Assembly Plugin Descriptor XSD is broken. > The link is found at the bottom of the following page: > http://maven.apache.org/plugins/maven-assembly-plugin/ > The link should be: > http://maven.apache.org/xsd/assembly-1.1.0.xsd > The current (wrong) link is: > http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd -- 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: (MASSEMBLY-481) small typo in log message
[ http://jira.codehaus.org/browse/MASSEMBLY-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254614#action_254614 ] Dennis Lundberg commented on MASSEMBLY-481: --- I've searched the current source code, but cannot find that message any longer. > small typo in log message > - > > Key: MASSEMBLY-481 > URL: http://jira.codehaus.org/browse/MASSEMBLY-481 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Reporter: Jon Osborn >Priority: Trivial > > when using unpack, the log message shows: > [INFO] Unpacking > /java_build/maven/repo/company/utils/15.0.0-SNAPSHOT/company-utils-15.0.0-SNAPSHOT.jarto > > /java_build/hudson/jobs/WL10UpgradeDev/workspace/shared-services/ws-clients/fee/target/classes > Note the space missing between the '.jar' and the 'to'. > Folks wanting to parse log files may find the lack of whitespace troublesome. -- 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] Updated: (MASSEMBLY-255) Typo in error message
[ http://jira.codehaus.org/browse/MASSEMBLY-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-255: -- Fix Version/s: 2.2.1 Assignee: Dennis Lundberg Summary: Typo in error message (was: type in error message) > Typo in error message > - > > Key: MASSEMBLY-255 > URL: http://jira.codehaus.org/browse/MASSEMBLY-255 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Cygwin, XP, Java 1.5 >Reporter: blue >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.2.1 > > Attachments: windows-eol.patch > > > Accidentally used "windows" instead of "dos" as a line ending type, and it > spit this message: > [ERROR] BUILD ERROR > [INFO] > [INFO] Failed to create assembly: Illlegal lineEnding specified: 'windows' > (Illegal has one too many L's) -- 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] Closed: (MASSEMBLY-481) small typo in log message
[ http://jira.codehaus.org/browse/MASSEMBLY-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MASSEMBLY-481. - Resolution: Cannot Reproduce > small typo in log message > - > > Key: MASSEMBLY-481 > URL: http://jira.codehaus.org/browse/MASSEMBLY-481 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Reporter: Jon Osborn >Priority: Trivial > > when using unpack, the log message shows: > [INFO] Unpacking > /java_build/maven/repo/company/utils/15.0.0-SNAPSHOT/company-utils-15.0.0-SNAPSHOT.jarto > > /java_build/hudson/jobs/WL10UpgradeDev/workspace/shared-services/ws-clients/fee/target/classes > Note the space missing between the '.jar' and the 'to'. > Folks wanting to parse log files may find the lack of whitespace troublesome. -- 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: (MASSEMBLY-255) Typo in error message
[ http://jira.codehaus.org/browse/MASSEMBLY-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254615#action_254615 ] Dennis Lundberg commented on MASSEMBLY-255: --- Typo fixed in [r1067010|http://svn.apache.org/viewvc?view=revision&revision=1067010]. > Typo in error message > - > > Key: MASSEMBLY-255 > URL: http://jira.codehaus.org/browse/MASSEMBLY-255 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Cygwin, XP, Java 1.5 >Reporter: blue >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.2.1 > > Attachments: windows-eol.patch > > > Accidentally used "windows" instead of "dos" as a line ending type, and it > spit this message: > [ERROR] BUILD ERROR > [INFO] > [INFO] Failed to create assembly: Illlegal lineEnding specified: 'windows' > (Illegal has one too many L's) -- 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] Closed: (MASSEMBLY-255) Typo in error message
[ http://jira.codehaus.org/browse/MASSEMBLY-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MASSEMBLY-255. - Resolution: Fixed Applied Benjamin's patch in [r1067016|http://svn.apache.org/viewvc?view=revision&revision=1067016]. > Typo in error message > - > > Key: MASSEMBLY-255 > URL: http://jira.codehaus.org/browse/MASSEMBLY-255 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Cygwin, XP, Java 1.5 >Reporter: blue >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.2.1 > > Attachments: windows-eol.patch > > > Accidentally used "windows" instead of "dos" as a line ending type, and it > spit this message: > [ERROR] BUILD ERROR > [INFO] > [INFO] Failed to create assembly: Illlegal lineEnding specified: 'windows' > (Illegal has one too many L's) -- 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: (MASSEMBLY-541) XSD for component
[ http://jira.codehaus.org/browse/MASSEMBLY-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254619#action_254619 ] Karl Heinz Marbaise commented on MASSEMBLY-541: --- On this page http://maven.apache.org/plugins/maven-assembly-plugin/index.html is a list of the xsd for the assembly..So there would be a good place to add a link to the xsd of the components. > XSD for component > - > > Key: MASSEMBLY-541 > URL: http://jira.codehaus.org/browse/MASSEMBLY-541 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2 > Environment: all >Reporter: Karl Heinz Marbaise > Fix For: 2.2.1 > > > I couldn't find any XSD's for the components. Based on the Modello the build > process will create one but it seemed to me that it's not available or i > oversight something. -- 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: (MCOMPILER-147) The usage page should use pluginManagement for configuring the plugin
The usage page should use pluginManagement for configuring the plugin - Key: MCOMPILER-147 URL: http://jira.codehaus.org/browse/MCOMPILER-147 Project: Maven 2.x Compiler Plugin Issue Type: Improvement Affects Versions: 2.3.2 Environment: n/a Reporter: Anders Hammar Priority: Minor Attachments: m-compiler-p_site-usage.patch IMO, when configuring plugins (especially those bound to the lifecycle through the packaging) the pluginManagement section should be used. Like when specifying the version. The current usage page does not say so. The attached patch updates thsi page to use pluginManagent. Also, I added a note about Maven 3.0 complaining if you don't specify the version (as related question has been brought up on the users mailing list twice with a few weeks). Also, a typos with regards to the goals of the plugin on the usage page was also fixed. -- 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: (MCOMPILER-147) The usage page should use pluginManagement for configuring the plugin
[ http://jira.codehaus.org/browse/MCOMPILER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254637#action_254637 ] Anders Hammar commented on MCOMPILER-147: - Possibly all the examples should be updated accordingly? If you want, I can provide patches for this as well. > The usage page should use pluginManagement for configuring the plugin > - > > Key: MCOMPILER-147 > URL: http://jira.codehaus.org/browse/MCOMPILER-147 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Affects Versions: 2.3.2 > Environment: n/a >Reporter: Anders Hammar >Priority: Minor > Attachments: m-compiler-p_site-usage.patch > > > IMO, when configuring plugins (especially those bound to the lifecycle > through the packaging) the pluginManagement section should be used. Like when > specifying the version. > The current usage page does not say so. > The attached patch updates thsi page to use pluginManagent. Also, I added a > note about Maven 3.0 complaining if you don't specify the version (as related > question has been brought up on the users mailing list twice with a few > weeks). > Also, a typos with regards to the goals of the plugin on the usage page was > also fixed. -- 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] Issue Comment Edited: (MPIR-220) IOException: Failed to open file During Site generation
[
http://jira.codehaus.org/browse/MPIR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254568#action_254568
]
Karl Heinz Marbaise edited comment on MPIR-220 at 2/4/11 1:43 AM:
--
What i missed to say is that this project has not been installed till that
point. So no mvn install hasn't been run before.
was (Author: khmarbaise):
What i missed to say is that this project has not been installed till that
point. So no mvn install has been run before.
> IOException: Failed to open file During Site generation
> ---
>
> Key: MPIR-220
> URL: http://jira.codehaus.org/browse/MPIR-220
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.3.1
> Environment: Linux (Ubuntu)
> java -version
> java version "1.6.0_22"
> Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-27-generic", arch: "amd64", family: "unix"
>Reporter: Karl Heinz Marbaise
>
> I have build which is working completely fine which means mvn clean package
> works perfect.
> If i try to do a mvn site i got the following Exception message:
> {code}[INFO] Generating "Dependencies" report---
> maven-project-info-reports-plugin:2.3.1
> [ERROR] IOException: Failed to open file
> /home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
> opening zip file
> java.util.zip.ZipException: Failed to open file
> /home/ubuntu/ws-git/pustefix-workspace/pws-config/target/classes : error in
> opening zip file
> at org.apache.maven.shared.jar.JarAnalyzer.(JarAnalyzer.java:109)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:273)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1374)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:544)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:271)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:206)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:165)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:159)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:122)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java
