[jira] Created: (MPH-58) effective pom file created with mixed newlines
effective pom file created with mixed newlines -- Key: MPH-58 URL: http://jira.codehaus.org/browse/MPH-58 Project: Maven 2.x Help Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: james ahlborn Priority: Minor the "effective-pom" goal with the "output" property is generating an xml file with mixed newlines (running on unix). the comment at the top uses unix newlines, but the rest of the content uses windows newlines. the newlines should be consistent and appropriate for the relevant platform. -- 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: (MAVENUPLOAD-2203) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148108#action_148108 ] Stefan Hübner commented on MAVENUPLOAD-2203: David, I just tried your bundle locally by extracting it directly into my local repository. It didn't work. The reason is the wrongly named files: org `-- umlgraph `-- doclet `-- 5.1 |-- umlgraph-5.1-javadoc.jar |-- umlgraph-5.1-javadoc.jar.md5 |-- umlgraph-5.1-javadoc.jar.sha1 |-- umlgraph-5.1.jar |-- umlgraph-5.1.jar.md5 |-- umlgraph-5.1.jar.sha1 |-- umlgraph-5.1.pom |-- umlgraph-5.1.pom.md5 `-- umlgraph-5.1.pom.sha1 All files umlgraph-5.1* need to be named doclet-5.1* to meet the artifactId "org.umlgraph:doclet" which you suggested inside the pom. Stefan PS: I'm no member of the upload team. I just found your package and tried it out. > Upload bundle org.umlgraph.doclet 5.1 > - > > Key: MAVENUPLOAD-2203 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2203 > Project: Maven Upload Requests > Issue Type: Task >Reporter: David J. M. Karlsen > Attachments: org.umlgraph.doclet-5.1.zip > > > Upload bundle for umlgraph 5.1 -- 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-312) outputFileNameMapping not respected when the unpack=true
[
http://jira.codehaus.org/browse/MASSEMBLY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-312.
Resolution: Won't Fix
outputFileNameMapping has a default value which will cause all sorts of
problems when appended to outputDirectory automatically in cases where unpack
== true. The element name: outputFileNameMapping should be a hint at its realm
of influence: single files. In other words, when the dependency is NOT unpacked.
The documentation for this element needs to be updated to reflect this, and
I'll take care of that now.
> outputFileNameMapping not respected when the unpack=true
>
>
> Key: MASSEMBLY-312
> URL: http://jira.codehaus.org/browse/MASSEMBLY-312
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-2
>Reporter: Calvin Yu
>Assignee: John Casey
> Fix For: 2.2-beta-3
>
> Attachments: massembly-312.txt, massembly312-integration-test.patch
>
>
> If I configure a dependencySet to unpack = true, the outputFileNameMapping is
> not respected, and instead the artifact is decompressed into the output
> directory. Looking at the code, this looks like it'll affect moduleSets as
> well.
> For example:
>
> some_directory
>
> ${artifact.artifactId}.${artifact.extension}
> true
>
--
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-345) a"ppxml attribute is required" error when making ears with the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MASSEMBLY-345: - Assignee: John Casey Fix Version/s: 2.2-beta-3 > a"ppxml attribute is required" error when making ears with the assembly plugin > -- > > Key: MASSEMBLY-345 > URL: http://jira.codehaus.org/browse/MASSEMBLY-345 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: all >Reporter: Petar Tahchiev >Assignee: John Casey > Fix For: 2.2-beta-3 > > Attachments: AbstractAssemblyMojo-345.patch, > AssemblyConfiguration-345.patch, DefaultAsemblyArchiver-345.patch, > massembly-345-integration-tests.txt, massembly-345.zip > > > So what I am doing is trying to make ears with the assembly plugin. For > instance here is my assembly descriptor: > > > src > > ear > > > > false > > ** > > > > > > But instead, I get the following exception: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to create assembly: Error creating assembly archive src: appxml > attribute is required > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:368) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: > Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:136) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > ... 18 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: appxml attribute > is required > at > org.codehaus.plexus.archiver.ear.EarArchiver.initZipOutputStream(EarArchiver.java:90) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:340) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:249) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:762) > at > o
[jira] Closed: (MASSEMBLY-297) Assembly broke on GNU/Linux - NullPointerException
[ http://jira.codehaus.org/browse/MASSEMBLY-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MASSEMBLY-297. Resolution: Duplicate > Assembly broke on GNU/Linux - NullPointerException > -- > > Key: MASSEMBLY-297 > URL: http://jira.codehaus.org/browse/MASSEMBLY-297 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1, 2.2-beta-2 > Environment: $ mvn -version > Maven version: 2.0.8 > Java version: 1.5.0_15 > OS name: "linux" version: "2.6.18-8.el5" arch: "amd64" Family: "unix" >Reporter: Robin Roos >Assignee: John Casey >Priority: Critical > Fix For: 2.2-beta-3 > > Attachments: buildlog.txt, MASSEMBLY-297.zip, unix.xml > > > I have an assembly descriptor "src/main/assembly/unix.xml" which works on > Windows but broke on Unix. When I commented out the following lines of the > assembly descriptor then it worked on Unix: > > > README* > LICENSE* > NOTICE* > > true > > I have no README*, LICENSE* or NOTICE* files in my src tree. > I have no filters defined in my pom.xml. The true makes > the assembly invoke filtering if the pom does define filters. > With the above included in the element I get the > following exception on assembly (on Unix only): > (I had variously used lib and /lib as target directory when debugging this so > ignore discrepencies in this regard) > [INFO] Processing DependencySet (output=lib) > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at java.io.File.(File.java:194) > at > org.apache.maven.shared.model.fileset.util.FileSetManager.scan(FileSetManager.java:598) > at > org.apache.maven.shared.model.fileset.util.FileSetManager.getIncludedFiles(FileSetManager.java:186) > at > org.apache.maven.plugin.assembly.format.FileSetFormatter.formatFileSetForAssembly(FileSetFormatter.java:67) > at > org.apache.maven.plugin.assembly.archive.task.AddFileSetsTask.addFileSet(AddFileSetsTask.java:133) > at > org.apache.maven.plugin.assembly.archive.task.AddFileSetsTask.execute(AddFileSetsTask.java:87) > at > org.apache.maven.plugin.assembly.archive.phase.FileSetAssemblyPhase.execute(FileSetAssemblyPhase.java:54) > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:129) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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:585) > 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) > [INFO] > > [INFO] Total time: 9 seconds > [INFO] Finished at: Thu Mar 13 12:42:17 GMT 2008 > [INFO] Final Memory: 19M/470M > [INFO] > -- This message is automatically
[jira] Reopened: (MASSEMBLY-297) Assembly broke on GNU/Linux - NullPointerException
[ http://jira.codehaus.org/browse/MASSEMBLY-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey reopened MASSEMBLY-297: -- wrong resolution > Assembly broke on GNU/Linux - NullPointerException > -- > > Key: MASSEMBLY-297 > URL: http://jira.codehaus.org/browse/MASSEMBLY-297 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1, 2.2-beta-2 > Environment: $ mvn -version > Maven version: 2.0.8 > Java version: 1.5.0_15 > OS name: "linux" version: "2.6.18-8.el5" arch: "amd64" Family: "unix" >Reporter: Robin Roos >Assignee: John Casey >Priority: Critical > Fix For: 2.2-beta-3 > > Attachments: buildlog.txt, MASSEMBLY-297.zip, unix.xml > > > I have an assembly descriptor "src/main/assembly/unix.xml" which works on > Windows but broke on Unix. When I commented out the following lines of the > assembly descriptor then it worked on Unix: > > > README* > LICENSE* > NOTICE* > > true > > I have no README*, LICENSE* or NOTICE* files in my src tree. > I have no filters defined in my pom.xml. The true makes > the assembly invoke filtering if the pom does define filters. > With the above included in the element I get the > following exception on assembly (on Unix only): > (I had variously used lib and /lib as target directory when debugging this so > ignore discrepencies in this regard) > [INFO] Processing DependencySet (output=lib) > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at java.io.File.(File.java:194) > at > org.apache.maven.shared.model.fileset.util.FileSetManager.scan(FileSetManager.java:598) > at > org.apache.maven.shared.model.fileset.util.FileSetManager.getIncludedFiles(FileSetManager.java:186) > at > org.apache.maven.plugin.assembly.format.FileSetFormatter.formatFileSetForAssembly(FileSetFormatter.java:67) > at > org.apache.maven.plugin.assembly.archive.task.AddFileSetsTask.addFileSet(AddFileSetsTask.java:133) > at > org.apache.maven.plugin.assembly.archive.task.AddFileSetsTask.execute(AddFileSetsTask.java:87) > at > org.apache.maven.plugin.assembly.archive.phase.FileSetAssemblyPhase.execute(FileSetAssemblyPhase.java:54) > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:129) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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:585) > 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) > [INFO] > > [INFO] Total time: 9 seconds > [INFO] Finished at: Thu Mar 13 12:42:17 GMT 2008 > [INFO] Final Memory: 19M/470M > [INFO] > -- This message is automatically gen
[jira] Closed: (MASSEMBLY-297) Assembly broke on GNU/Linux - NullPointerException
[ http://jira.codehaus.org/browse/MASSEMBLY-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MASSEMBLY-297. Assignee: John Casey Resolution: Fixed > Assembly broke on GNU/Linux - NullPointerException > -- > > Key: MASSEMBLY-297 > URL: http://jira.codehaus.org/browse/MASSEMBLY-297 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1, 2.2-beta-2 > Environment: $ mvn -version > Maven version: 2.0.8 > Java version: 1.5.0_15 > OS name: "linux" version: "2.6.18-8.el5" arch: "amd64" Family: "unix" >Reporter: Robin Roos >Assignee: John Casey >Priority: Critical > Fix For: 2.2-beta-3 > > Attachments: buildlog.txt, MASSEMBLY-297.zip, unix.xml > > > I have an assembly descriptor "src/main/assembly/unix.xml" which works on > Windows but broke on Unix. When I commented out the following lines of the > assembly descriptor then it worked on Unix: > > > README* > LICENSE* > NOTICE* > > true > > I have no README*, LICENSE* or NOTICE* files in my src tree. > I have no filters defined in my pom.xml. The true makes > the assembly invoke filtering if the pom does define filters. > With the above included in the element I get the > following exception on assembly (on Unix only): > (I had variously used lib and /lib as target directory when debugging this so > ignore discrepencies in this regard) > [INFO] Processing DependencySet (output=lib) > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at java.io.File.(File.java:194) > at > org.apache.maven.shared.model.fileset.util.FileSetManager.scan(FileSetManager.java:598) > at > org.apache.maven.shared.model.fileset.util.FileSetManager.getIncludedFiles(FileSetManager.java:186) > at > org.apache.maven.plugin.assembly.format.FileSetFormatter.formatFileSetForAssembly(FileSetFormatter.java:67) > at > org.apache.maven.plugin.assembly.archive.task.AddFileSetsTask.addFileSet(AddFileSetsTask.java:133) > at > org.apache.maven.plugin.assembly.archive.task.AddFileSetsTask.execute(AddFileSetsTask.java:87) > at > org.apache.maven.plugin.assembly.archive.phase.FileSetAssemblyPhase.execute(FileSetAssemblyPhase.java:54) > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:129) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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:585) > 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) > [INFO] > > [INFO] Total time: 9 seconds > [INFO] Finished at: Thu Mar 13 12:42:17 GMT 2008 > [INFO] Final Memory: 19M/470M > [INFO] > -- This m
[jira] Work started: (MASSEMBLY-345) a"ppxml attribute is required" error when making ears with the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MASSEMBLY-345 started by John Casey. > a"ppxml attribute is required" error when making ears with the assembly plugin > -- > > Key: MASSEMBLY-345 > URL: http://jira.codehaus.org/browse/MASSEMBLY-345 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: all >Reporter: Petar Tahchiev >Assignee: John Casey > Fix For: 2.2-beta-3 > > Attachments: AbstractAssemblyMojo-345.patch, > AssemblyConfiguration-345.patch, DefaultAsemblyArchiver-345.patch, > massembly-345-integration-tests.txt, massembly-345.zip > > > So what I am doing is trying to make ears with the assembly plugin. For > instance here is my assembly descriptor: > > > src > > ear > > > > false > > ** > > > > > > But instead, I get the following exception: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to create assembly: Error creating assembly archive src: appxml > attribute is required > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:368) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: > Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:136) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > ... 18 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: appxml attribute > is required > at > org.codehaus.plexus.archiver.ear.EarArchiver.initZipOutputStream(EarArchiver.java:90) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:340) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:249) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:762) > at > org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive
[jira] Commented: (MSITE-306) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ http://jira.codehaus.org/browse/MSITE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148115#action_148115 ] David Trott commented on MSITE-306: --- You can suppress the warning by mandating version 1.1.3 of the plexus-velocity jar. Note you will also need the exclusions section. org.apache.maven.plugins maven-checkstyle-plugin 2.2 org.codehaus.plexus plexus-velocity 1.1.3 commons-collections commons-collections plexus-utils plexus > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > > > Key: MSITE-306 > URL: http://jira.codehaus.org/browse/MSITE-306 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Alexandre Navarro >Priority: Minor > > I always get the error below: > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > this does not seem to affect my site generation. > I get rid of this because my build server (Luntbuild/Quickbuild) thinks there > is an error. > thanks, > Alexandre > PS : The same bug was reported before > http://jira.codehaus.org/browse/MSITE-286 > normally it mght be fixed in 2.0-beta-6 but it not true (not for me). -- 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: (MREACTOR-1) Reactor plugin doesn't work with sibling aggregated modules
Reactor plugin doesn't work with sibling aggregated modules
---
Key: MREACTOR-1
URL: http://jira.codehaus.org/browse/MREACTOR-1
Project: Maven 2.x Reactor Plugin
Issue Type: Bug
Affects Versions: Future
Reporter: Dan Fabulich
Normally when you have an aggregator POM with a list of , the element
lists out subdirectories of the aggregator, like this:
{code}
foo
bar
{code}
But modules can be anywhere; the module list can declare relative paths to
anywhere, like this:
{code}
../foo
../../bar
{code}
Since the reactor plugin currently works by using "mvn --reactor", which only
accepts subdirectories, it will silently fail to run these sibling modules.
Ultimately we should fix this by using the new command line switches available
in 2.1. http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode In the
meantime, we'll have to live with it. (Possibly include a warning? error?)
--
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: (MREACTOR-1) Reactor plugin doesn't work with sibling aggregated modules
[
http://jira.codehaus.org/browse/MREACTOR-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148117#action_148117
]
Dan Fabulich commented on MREACTOR-1:
-
Alternately we could construct a temporary POM file with a list of modules in
it, execute the POM file and mark it to be deleted on exit...?
> Reactor plugin doesn't work with sibling aggregated modules
> ---
>
> Key: MREACTOR-1
> URL: http://jira.codehaus.org/browse/MREACTOR-1
> Project: Maven 2.x Reactor Plugin
> Issue Type: Bug
>Affects Versions: Future
>Reporter: Dan Fabulich
>
> Normally when you have an aggregator POM with a list of , the
> element lists out subdirectories of the aggregator, like this:
> {code}
>
> foo
> bar
>
> {code}
> But modules can be anywhere; the module list can declare relative paths to
> anywhere, like this:
> {code}
>
> ../foo
> ../../bar
>
> {code}
> Since the reactor plugin currently works by using "mvn --reactor", which only
> accepts subdirectories, it will silently fail to run these sibling modules.
> Ultimately we should fix this by using the new command line switches
> available in 2.1.
> http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode In the
> meantime, we'll have to live with it. (Possibly include a warning? error?)
--
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: (MREACTOR-2) Make a reverse dependency tree
Make a reverse dependency tree -- Key: MREACTOR-2 URL: http://jira.codehaus.org/browse/MREACTOR-2 Project: Maven 2.x Reactor Plugin Issue Type: New Feature Reporter: Dan Fabulich mvn dependency:tree shows you all of the projects that the current project depends on, even if they aren't in the current reactor. This plugin (or the dependency plugin?) should generate a tree of projects that depend on you (within the current reactor). (Note that in 2.1 the ProjectSorter will expose its DAG, so at that point maybe the dependency plugin will be a better place for this.) -- 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: (MREACTOR-3) Integration tests
Integration tests - Key: MREACTOR-3 URL: http://jira.codehaus.org/browse/MREACTOR-3 Project: Maven 2.x Reactor Plugin Issue Type: Task Reporter: Dan Fabulich There should be integration tests for this plugin. -- 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: (MREACTOR-4) Basic unit test of make goal
Basic unit test of make goal Key: MREACTOR-4 URL: http://jira.codehaus.org/browse/MREACTOR-4 Project: Maven 2.x Reactor Plugin Issue Type: Task Reporter: Dan Fabulich Fix For: 1.0 There should be a basic unit test of the make goal. (This will require the ProjectSorter to be injected, I think... But how do I set that up?) -- 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: (MREACTOR-2) Make a reverse dependency tree
[ http://jira.codehaus.org/browse/MREACTOR-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MREACTOR-2: Fix Version/s: Future > Make a reverse dependency tree > -- > > Key: MREACTOR-2 > URL: http://jira.codehaus.org/browse/MREACTOR-2 > Project: Maven 2.x Reactor Plugin > Issue Type: New Feature >Reporter: Dan Fabulich > Fix For: Future > > > mvn dependency:tree shows you all of the projects that the current project > depends on, even if they aren't in the current reactor. This plugin (or the > dependency plugin?) should generate a tree of projects that depend on you > (within the current reactor). > (Note that in 2.1 the ProjectSorter will expose its DAG, so at that point > maybe the dependency plugin will be a better place for this.) -- 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: (MREACTOR-1) Reactor plugin doesn't work with sibling aggregated modules
[
http://jira.codehaus.org/browse/MREACTOR-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich updated MREACTOR-1:
Fix Version/s: Future
> Reactor plugin doesn't work with sibling aggregated modules
> ---
>
> Key: MREACTOR-1
> URL: http://jira.codehaus.org/browse/MREACTOR-1
> Project: Maven 2.x Reactor Plugin
> Issue Type: Bug
>Affects Versions: Future
>Reporter: Dan Fabulich
> Fix For: Future
>
>
> Normally when you have an aggregator POM with a list of , the
> element lists out subdirectories of the aggregator, like this:
> {code}
>
> foo
> bar
>
> {code}
> But modules can be anywhere; the module list can declare relative paths to
> anywhere, like this:
> {code}
>
> ../foo
> ../../bar
>
> {code}
> Since the reactor plugin currently works by using "mvn --reactor", which only
> accepts subdirectories, it will silently fail to run these sibling modules.
> Ultimately we should fix this by using the new command line switches
> available in 2.1.
> http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode In the
> meantime, we'll have to live with it. (Possibly include a warning? error?)
--
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: (MREACTOR-4) Basic unit test of make goal
[ http://jira.codehaus.org/browse/MREACTOR-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MREACTOR-4: Fix Version/s: 1.0 > Basic unit test of make goal > > > Key: MREACTOR-4 > URL: http://jira.codehaus.org/browse/MREACTOR-4 > Project: Maven 2.x Reactor Plugin > Issue Type: Task >Reporter: Dan Fabulich > Fix For: 1.0 > > > There should be a basic unit test of the make goal. (This will require the > ProjectSorter to be injected, I think... But how do I set that up?) -- 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: (MAVENUPLOAD-2203) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MAVENUPLOAD-2203: - Attachment: org.umlgraph.doclet-5.1.zip Uh - big bummer - thanks for pointing it out! Please use the second attachment > Upload bundle org.umlgraph.doclet 5.1 > - > > Key: MAVENUPLOAD-2203 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2203 > Project: Maven Upload Requests > Issue Type: Task >Reporter: David J. M. Karlsen > Attachments: org.umlgraph.doclet-5.1.zip, org.umlgraph.doclet-5.1.zip > > > Upload bundle for umlgraph 5.1 -- 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: (MECLIPSE-488) InstallPluginsMojo throws NPE if a jar has no manifest
[ http://jira.codehaus.org/browse/MECLIPSE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-488. --- Assignee: Barrie Treloar Resolution: Fixed Fix Version/s: 2.6 Applied path as well as creating a unit test. > InstallPluginsMojo throws NPE if a jar has no manifest > -- > > Key: MECLIPSE-488 > URL: http://jira.codehaus.org/browse/MECLIPSE-488 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: PDE support >Affects Versions: 2.5.1 >Reporter: Baptiste MATHUS >Assignee: Barrie Treloar > Fix For: 2.6 > > Attachments: jarWithoutManifest.patch > > > Some library we're using (namely xdb, from the oracle XDK) doesn't have any > manifest file. > This makes InstallPluginsMojo crash because it seems to consider jars always > have a manifest. > After checking the Jar File Specification > (http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html), as the whole META-INF > is optional, it's legal for a Jar to not have a manifest. > Cheers. -- 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-345) a"ppxml attribute is required" error when making ears with the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MASSEMBLY-345. Resolution: Fixed Rather than applying the specific fix for EAR archives, I added a new plugin parameter called which allows configuration of any specific Archiver instance, including the EarArchiver, which allows the following: /path/to/application.xml. Thanks for the integration test, Petar. > a"ppxml attribute is required" error when making ears with the assembly plugin > -- > > Key: MASSEMBLY-345 > URL: http://jira.codehaus.org/browse/MASSEMBLY-345 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: all >Reporter: Petar Tahchiev >Assignee: John Casey > Fix For: 2.2-beta-3 > > Attachments: AbstractAssemblyMojo-345.patch, > AssemblyConfiguration-345.patch, DefaultAsemblyArchiver-345.patch, > massembly-345-integration-tests.txt, massembly-345.zip > > > So what I am doing is trying to make ears with the assembly plugin. For > instance here is my assembly descriptor: > > > src > > ear > > > > false > > ** > > > > > > But instead, I get the following exception: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to create assembly: Error creating assembly archive src: appxml > attribute is required > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:368) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: > Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:136) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > ... 18 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: appxml attribute > is required > at > org.codehaus.plexus.archiver.ear.EarArchiver.initZipOutputStream(EarArchiver.java:90) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArc
[jira] Updated: (MREACTOR-3) Integration tests
[ http://jira.codehaus.org/browse/MREACTOR-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MREACTOR-3: Fix Version/s: Future > Integration tests > - > > Key: MREACTOR-3 > URL: http://jira.codehaus.org/browse/MREACTOR-3 > Project: Maven 2.x Reactor Plugin > Issue Type: Task >Reporter: Dan Fabulich > Fix For: Future > > > There should be integration tests for this plugin. -- 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: (MREACTOR-4) Basic unit test of make goal
[ http://jira.codehaus.org/browse/MREACTOR-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed MREACTOR-4. --- Resolution: Fixed > Basic unit test of make goal > > > Key: MREACTOR-4 > URL: http://jira.codehaus.org/browse/MREACTOR-4 > Project: Maven 2.x Reactor Plugin > Issue Type: Task >Reporter: Dan Fabulich > Fix For: 1.0 > > > There should be a basic unit test of the make goal. (This will require the > ProjectSorter to be injected, I think... But how do I set that up?) -- 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: (MECLIPSE-206) IdeUtils.toRelativeAndFixSeparator broken on Windows
[ http://jira.codehaus.org/browse/MECLIPSE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-206. --- Assignee: Barrie Treloar Resolution: Fixed Fix Version/s: 2.6 Already has been fixed. Added in unit tests to IdeUtilsTest. > IdeUtils.toRelativeAndFixSeparator broken on Windows > > > Key: MECLIPSE-206 > URL: http://jira.codehaus.org/browse/MECLIPSE-206 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Workspace settings > Environment: Windows XP >Reporter: Barrie Treloar >Assignee: Barrie Treloar >Priority: Critical > Fix For: 2.6 > > Attachments: MECLIPSE-206-patch.txt > > > See http://www.nabble.com/forum/ViewPost.jtp?post=7753417&framed=y&skin=177 > The problem is that IdeUtils.toRelativeAndFixSeparator attempts to > canonicalise relative paths. > This will cause the result to be based on the current directory of the > processor and not the project basedir as intended. > This causes the build to fail with canonicalisation errors. > I have supplied a patch against r485327 which includes extra test cases and > all test cases pass. > I have also: > * removed the project > * removed use of assertTrue and converted to assertEquals (tests were > succeeding when they should not have because the check was on the trailing > path not the entire path) > * removed MavenProject from extractResourceDirs (it was never used) > Some other comments: > baseDir and projectBaseDir seem to be used but I can not see any use cases > where these two are not the same value. Shouldn't the pom file always be > located at the top of the eclipse project workspace? The similar names and > mostly the same value caused me trouble in understanding the system. If they > could get removed it would make things easier. -- 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: (MECLIPSE-194) NPE during eclipse:make-artifacts
[ http://jira.codehaus.org/browse/MECLIPSE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-194. --- Resolution: Won't Fix MakeArtifactsMojo has been deprecated in favor of EclipseToMavenMojo. If you can reproduce with this new mojo please re-open. > NPE during eclipse:make-artifacts > - > > Key: MECLIPSE-194 > URL: http://jira.codehaus.org/browse/MECLIPSE-194 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: I'm using maven with ubuntu edgy. Running eclipse 3.2.1 > with many installed features/plugins. >Reporter: Markus Wolf > > During the eclipse:make-artifacts goal is a NPE for the > org.apache.geronimo.runtime.v1_1.0.0 plugin with the following stacktrace: > java.lang.NullPointerException > at > org.apache.maven.plugin.eclipse.MakeArtifactsMojo.processSingleFile(MakeArtifactsMojo.java:288) > at > org.apache.maven.plugin.eclipse.MakeArtifactsMojo.execute(MakeArtifactsMojo.java:199) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:219) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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:585) > 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) -- 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: (MECLIPSE-166) Configure Eclipse Checkstyle plugin
[
http://jira.codehaus.org/browse/MECLIPSE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar closed MECLIPSE-166.
---
Resolution: Fixed
This is possible now.
Here is the snipper we use.
I have added this into the site docs as configure-checkstyle.apt.
{code:xml}
[...]
[...]
[...]
org.apache.maven.plugins
maven-eclipse-plugin
com.atlassw.tools.eclipse.checkstyle.CheckstyleBuilder
com.atlassw.tools.eclipse.checkstyle.CheckstyleNature
.checkstyle
[...]
[...]
[...]
{code}
> Configure Eclipse Checkstyle plugin
> ---
>
> Key: MECLIPSE-166
> URL: http://jira.codehaus.org/browse/MECLIPSE-166
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
>Reporter: Julien HENRY
>
> It would be great if checkstyle eclipse plugin is automatically configured
> from pom configuration.
--
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: (MECLIPSE-244) NPE in MakeArtifactsMojo.java:301
[ http://jira.codehaus.org/browse/MECLIPSE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-244. --- Resolution: Duplicate This looks like a duplicate of MECLIPSE-194 and the resolution was: MakeArtifactsMojo has been deprecated in favor of EclipseToMavenMojo. If you can reproduce with this new mojo please re-open. > NPE in MakeArtifactsMojo.java:301 > - > > Key: MECLIPSE-244 > URL: http://jira.codehaus.org/browse/MECLIPSE-244 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: j2sdk_1.4.2_13 on XP Pro latest patch >Reporter: Jörn Guy Süß > Attachments: com.nilswinkler.eclipse.accessmodifier_1.2.zip > > > eclipse:make-artifacts in eclipse3.2 with attached plugin unpacked in plugins > directory causes NPE as follows: > [INFO] Processing file C:\Program > Files\eclipse\plugins\com.nilswinkler.eclipse.accessmodifier_1.2.6 > [INFO] Building jar: C:\TEMP\mvn-eclipse7072.tmp > java.lang.NullPointerException > at > org.apache.maven.plugin.eclipse.MakeArtifactsMojo.processSingleFile(MakeArtifactsMojo.java:301) > at > org.apache.maven.plugin.eclipse.MakeArtifactsMojo.execute(MakeArtifactsMojo.java:211) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382) > at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68) -- 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: (MECLIPSE-150) [with PATCH] Plugin generates invalid Eclipse project files when multiproject contains two references to the same artifact
[
http://jira.codehaus.org/browse/MECLIPSE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar closed MECLIPSE-150.
---
Resolution: Fixed
Fix Version/s: 2.6
IdeDependency is comparable and equals delegates to compare, hashCode() also
defined.
AbstractIdeSupportMojo.doDependencyResolution() maintains a list of
dependencies and code already guards against duplicates:
{code:java}
// no duplicate entries allowed. System paths can cause this problem.
if ( !dependencies.contains( dep ) )
{
dependencies.add( dep );
}
{code}
This should resolve your problem.
> [with PATCH] Plugin generates invalid Eclipse project files when multiproject
> contains two references to the same artifact
> --
>
> Key: MECLIPSE-150
> URL: http://jira.codehaus.org/browse/MECLIPSE-150
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path, Core :
> Multi-projects
>Affects Versions: 2.2
>Reporter: Kristian Köhler
> Fix For: 2.6
>
> Attachments: dependency-patch.txt
>
>
> HI
> in same circumstances the eclipse-plugin will generate a Eclipse project file
> which contains two references to the same artifact/project which will cause
> Eclipse to fail loading the project. The attached patch is very small and
> solves this problem by managing the references within a java.util.Set and
> using equals() within the IdeDependency.java class.
> Thanks
> Kristian
--
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: (MECLIPSE-337) test failure needed to be commented out
[ http://jira.codehaus.org/browse/MECLIPSE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-337. --- Resolution: Fixed Fix Version/s: 2.6 Added back in test. Test just works, nothing else needed > test failure needed to be commented out > --- > > Key: MECLIPSE-337 > URL: http://jira.codehaus.org/browse/MECLIPSE-337 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support >Affects Versions: 2.4 >Reporter: Brett Porter > Fix For: 2.6 > > > see r589625 - this was failing on my machine, and in CI, so the test was > disabled -- 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: (MECLIPSE-101) Replace the integration tests in eclipse plugin with the test harness
[ http://jira.codehaus.org/browse/MECLIPSE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148147#action_148147 ] Barrie Treloar commented on MECLIPSE-101: - The proof of concept doesn't validate the contents of the files, just their existence. A lot of work has gone into making the expected files correct. And unfortunately the expected files can have dynamic content that needs mangling before checking against the actual files. I guess this can be AbstractEclipsePluginIT.compareDirectoryContent() into a groovy script as long as it can be reused by all the tests. > Replace the integration tests in eclipse plugin with the test harness > - > > Key: MECLIPSE-101 > URL: http://jira.codehaus.org/browse/MECLIPSE-101 > Project: Maven 2.x Eclipse Plugin > Issue Type: Test >Reporter: Edwin Punzalan >Assignee: Edwin Punzalan > Attachments: test.patch > > -- 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: (MECLIPSE-38) Allow custom code formatters to be written to .settings
[ http://jira.codehaus.org/browse/MECLIPSE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148148#action_148148 ] Barrie Treloar commented on MECLIPSE-38: For loading code styles, is this example not what you need? http://maven.apache.org/plugins/maven-eclipse-plugin/examples/load-code-styles.html For checkstyle see MECLIPSE-166 Not sure about configuring project-specific settings like compiler warnings and such. They all fall into the preferences api, the files all live in WORKSPACE\.plugins\org.eclipse.core.runtime\.settings I'd raise a separate issue for configuring Eclipse Preference values. But it is definitely something I would use. > Allow custom code formatters to be written to .settings > --- > > Key: MECLIPSE-38 > URL: http://jira.codehaus.org/browse/MECLIPSE-38 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Mark Hobson > > It'd be handy if there was a way of embedding custom code formatters to > .settings. Eclipse can currently export code formatter profiles as a list of > properties in an XML format, so this file could be configured against the > eclipse plugin for it to generate the corresponding properties-format > .settings/org.eclipse.jdt.core.prefs 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] Commented: (MECLIPSE-440) unit tests depends on local configuration and artifacts in local repository
[ http://jira.codehaus.org/browse/MECLIPSE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148149#action_148149 ] Barrie Treloar commented on MECLIPSE-440: - Is this still an issue? EclipsePluginTest does not exist anymore. The choices are: * EclipsePluginUnitTest * EclipsePluginIT EclipsePluginUnitTest does not contain testProjectXX but EclipsePluginIT does. EclipsePluginIT does not use local repos but a static one as part of the subversion repository which is copied into target/test-classes/m2repo. I don't think you will have this problem anymore. Can you confirm and close if it is ok? > unit tests depends on local configuration and artifacts in local repository > --- > > Key: MECLIPSE-440 > URL: http://jira.codehaus.org/browse/MECLIPSE-440 > Project: Maven 2.x Eclipse Plugin > Issue Type: Task > Components: Core : Workspace settings >Affects Versions: 2.6 >Reporter: nicolas de loof > > My local repository contans -sources.jar for junit and servlet-api. > I then have failing tests : > testProject13(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject22(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject28(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject29(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject30(org.apache.maven.plugin.eclipse.EclipsePluginTest) > ... > All of them fail beacuse the .classpath contains link to the sources archive : > Checking .classpath, line #3 expected:<...servlet-api-2.3.jar"[]/>> but > was:<...servlet-api-2.3.jar"[ > sourcepath="M2_REPO/javax/servlet/servlet-api/2.3/servlet-api-2.3-sources.jar"]/>> > An option would be to package with the plugin test resource a repository > containing fake (0byte) artifacts, and use it as local repo with offline mode > set, so that the available artifacts are fully under control. -- 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: (MECLIPSE-377) eclipse:eclipse -DdownloadSources=true shouldn't attempt download more than once in a multi-project
[ http://jira.codehaus.org/browse/MECLIPSE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-377. --- Resolution: Fixed Fix Version/s: 2.6 2.5.2 never got released so marking this closed against 2.6. > eclipse:eclipse -DdownloadSources=true shouldn't attempt download more than > once in a multi-project > --- > > Key: MECLIPSE-377 > URL: http://jira.codehaus.org/browse/MECLIPSE-377 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path, Core : > Multi-projects >Affects Versions: 2.4 >Reporter: Steinar Bang > Fix For: 2.6 > > > If you run "mvn eclipse:eclipse -DdownloadSources=true" it attempts to > download source jars for all projects, even when it has tried (and failed) to > download the jars in earlier projects. This slows down the goal a lot on > slow network connections. -- 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: (MECLIPSE-447) maven eclipse:eclipse does not generate .checkstyle file
[ http://jira.codehaus.org/browse/MECLIPSE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-447. --- Resolution: Duplicate > maven eclipse:eclipse does not generate .checkstyle file > > > Key: MECLIPSE-447 > URL: http://jira.codehaus.org/browse/MECLIPSE-447 > Project: Maven 2.x Eclipse Plugin > Issue Type: Wish > Environment: all >Reporter: Sebastian Dietrich > > eclipse:eclipse does not generate .checkstyle file, so all configurations for > checkstyle have to be repeated manually in eclipse -- 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: (MECLIPSE-425) NPE in install-plugins when processing JARs without a manifest file
[ http://jira.codehaus.org/browse/MECLIPSE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-425. --- Resolution: Duplicate > NPE in install-plugins when processing JARs without a manifest file > --- > > Key: MECLIPSE-425 > URL: http://jira.codehaus.org/browse/MECLIPSE-425 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path >Affects Versions: 2.5.1 > Environment: Windows XP Professional SP2 >Reporter: Roland Schneider > Attachments: InstallPluginsMojo.patch, mvn_eclipse_npe_log.txt > > > The goal "install-plugins" throws a NullPointerException when processing JARs > that don't have a manifest file. > See attached file for details. -- 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: (MECLIPSE-261) IdeUtils.toRelativeAndFixSeparator returns incomplete path
[ http://jira.codehaus.org/browse/MECLIPSE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148151#action_148151 ] Barrie Treloar commented on MECLIPSE-261: - For Z: basedirPath.length() + 1=4 basedirPath =Z:\ absolutePath=Z:\target\main-output relative=arget\main-output relative fix=arget/main-output basedirPath.length() + 1=5 basedirPath =Z:\s absolutePath=Z:\s\target\main-output relative=target\main-output relative fix=target/main-output The problem is that the code assumes there is a directory at the end of the absolute basedir and therefore after the end of basedir, there is a file separator in the fileToAdd. As fileToAdd = new File( basedir, fileToAdd.getPath() ); Which for basedir = Z: basedirPath =Z:\ absolutePath=Z:\target\main-output and for basedirPath =Z:\s absolutePath=Z:\s\target\main-output In the case of Z: there is no file separator after so the +1 assumption causes the problem. > IdeUtils.toRelativeAndFixSeparator returns incomplete path > -- > > Key: MECLIPSE-261 > URL: http://jira.codehaus.org/browse/MECLIPSE-261 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path >Affects Versions: 2.3 > Environment: Windows XP, jdk 1.5.0_11-b03, maven 2.0.5 >Reporter: Marcio Paulo Guedes >Assignee: Arnaud Heritier > Attachments: .classpath, baseDirIsRoot.patch, > EclipseClasspathWriter.java, EclipsePlugin-2.4.zip, IdeUtils.java, patch.txt, > pom.xml > > > .classpath file is generated with incomplete path for classpathentry when > kind is "var". > Example: > > when path="M2_REPO/ognl/ognl/2.6.9/ognl-2.6.9.jar"/> is expected. > It's caused by IdeUtils.toRelativeAndFixSeparator when basepath is not equal > absolutepath. Code on line 99 shifts the string 1 character to the right, > corrupting the result path. -- 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: (MCLEAN-38) Allow a global set of include and exclude filters
Allow a global set of include and exclude filters - Key: MCLEAN-38 URL: http://jira.codehaus.org/browse/MCLEAN-38 Project: Maven 2.x Clean Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: Nick Pellow I am about to submit a patch to the maven-clean-plugin which will allow a global includes and excludes patterns to be configured. Currently, it is not possibly to easily do a clean and have specific files in the default output directories preserved. The patch will allow a comma separated list of exclusions and inclusions to use when removing the default output directories. -- 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: (MECLIPSE-261) IdeUtils.toRelativeAndFixSeparator returns incomplete path
[ http://jira.codehaus.org/browse/MECLIPSE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-261. --- Resolution: Fixed Fix Version/s: 2.6 The canonical form of a windows root dir ends in a slash, whereas the canonical form of any other file does not. The absolutePath is assumed to be: basedirPath + Separator + fileToAdd In the case of a windows root directory the Separator is missing since it is contained within basedirPath. Added unit test and fixed code. > IdeUtils.toRelativeAndFixSeparator returns incomplete path > -- > > Key: MECLIPSE-261 > URL: http://jira.codehaus.org/browse/MECLIPSE-261 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path >Affects Versions: 2.3 > Environment: Windows XP, jdk 1.5.0_11-b03, maven 2.0.5 >Reporter: Marcio Paulo Guedes >Assignee: Arnaud Heritier > Fix For: 2.6 > > Attachments: .classpath, baseDirIsRoot.patch, > EclipseClasspathWriter.java, EclipsePlugin-2.4.zip, IdeUtils.java, patch.txt, > pom.xml > > > .classpath file is generated with incomplete path for classpathentry when > kind is "var". > Example: > > when path="M2_REPO/ognl/ognl/2.6.9/ognl-2.6.9.jar"/> is expected. > It's caused by IdeUtils.toRelativeAndFixSeparator when basepath is not equal > absolutepath. Code on line 99 shifts the string 1 character to the right, > corrupting the result path. -- 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: (MCLEAN-38) Allow a global set of include and exclude filters
[ http://jira.codehaus.org/browse/MCLEAN-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Pellow updated MCLEAN-38: -- Attachment: MCLEAN-38-maven-clean-plugin.patch This patch allows the following parameters to be passed to the maven-clean-plugin: # *includes* a comma-delimited list of file patterns to be deleted when removing the defaultOutputDirectories # *excludes* a comma-delimited list of file patterns to be preserved when removing the defaultOutputDirectories > Allow a global set of include and exclude filters > - > > Key: MCLEAN-38 > URL: http://jira.codehaus.org/browse/MCLEAN-38 > Project: Maven 2.x Clean Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Nick Pellow > Attachments: MCLEAN-38-maven-clean-plugin.patch > > > I am about to submit a patch to the maven-clean-plugin which will allow a > global includes and excludes patterns to be configured. > Currently, it is not possibly to easily do a clean and have specific files in > the default output directories preserved. > The patch will allow a comma separated list of exclusions and inclusions to > use when removing the default output directories. -- 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: (MECLIPSE-461) NPE with eclipse:install-plugins
[ http://jira.codehaus.org/browse/MECLIPSE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-461. --- Resolution: Duplicate > NPE with eclipse:install-plugins > > > Key: MECLIPSE-461 > URL: http://jira.codehaus.org/browse/MECLIPSE-461 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: XP / mvn 2.0.9 >Reporter: Nico > Attachments: hibernate-3.2.6.ga.jar > > > Hi, > I'm having a NPE when doing mvn eclipse:install-plugins with a bundle that > have a dependency with the bundle attached: > [WARNING] Attempting to build MavenProject instance for Artifact > (org.escapek:domain-orm:0.1-20080610.073952-1) of type: > jar; constructing POM artifact instead. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.plugin.eclipse.InstallPluginsMojo.install(InstallPluginsMojo.java:279) > at > org.apache.maven.plugin.eclipse.InstallPluginsMojo.execute(InstallPluginsMojo.java:216) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav > a:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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) > As i've found, this NPE occurs when the bundle has not MANIFEST.MF file. The > problem is that this bundle have 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
