[Dspace-tech] debugging the project assembler

0 views
Skip to first unread message

Ingram, William A

unread,
Aug 26, 2015, 10:53:52 AM8/26/15
to dspac...@lists.sourceforge.net

Does anyone know how to debug the assembly plugin? Something is amiss with my install—something obvious, probably—but I can’t find it. It happens on my staging server but not my dev box. This is 3.1.

 

[INFO] ------------------------------------------------------------------------

[INFO] Building DSpace Assembly and Configuration

[INFO]    task-segment: [package]

[INFO] ------------------------------------------------------------------------

[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]

[INFO] [assembly:single {execution: default}]

[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml

[INFO] ------------------------------------------------------------------------

[ERROR] FATAL ERROR

[INFO] ------------------------------------------------------------------------

[INFO] null

[INFO] ------------------------------------------------------------------------

[INFO] Trace

java.lang.NullPointerException

                at java.io.File.<init>(File.java:222)

                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:490)

                at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)

                at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)

                at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)

                at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)

                at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)

                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)

 

Thanks!

Bill

--

Bill Ingram

Scholarly Communication and

Repository Services

University of Illinois at Urbana-Champaign

135 GELIC, MC274

1301 W. Springfield Ave.

Urbana, IL 61801

217-333-4648

wing...@illinois.edu

 

helix84

unread,
Aug 26, 2015, 10:53:53 AM8/26/15
to Ingram, William A, dspac...@lists.sourceforge.net
Hi Bill,

it looks like it might be this issue (probably related to a filtering
feature introduced in DSpace 3):

http://jira.codehaus.org/browse/MASSEMBLY-342

What Maven version are you using? According to our docs DSpace 3.x
builds with 2.2.x and higher, but you may have hit a bug. As a
workaround, you could try using a higher version of Maven.

Hopefully other guys more familiar with Maven will chime in and help
resolve the issue. Can you think of anything out of the ordinary you
might have done to trigger this? Perhaps any customizations to the
source?


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Ingram, William A

unread,
Aug 26, 2015, 10:53:54 AM8/26/15
to hel...@centrum.sk, dspac...@lists.sourceforge.net
The Maven version sounds likely. It would explain why it works on dev but not on staging.

Will verify.

Thanks!
Bill

Ingram, William A

unread,
Aug 26, 2015, 10:53:55 AM8/26/15
to hel...@centrum.sk, dspac...@lists.sourceforge.net
No good. Both dev and staging are running Maven 2.2.1. One works, the other doesn't.

-----Original Message-----
From: Ingram, William A [mailto:wing...@illinois.edu]
Sent: Monday, May 20, 2013 5:55 PM
To: hel...@centrum.sk
Cc: dspac...@lists.sourceforge.net
Subject: Re: [Dspace-tech] debugging the project assembler

The Maven version sounds likely. It would explain why it works on dev but not on staging.

Will verify.

Thanks!
Bill


-----Original Message-----
From: ivan....@gmail.com [mailto:ivan....@gmail.com] On Behalf Of helix84
Sent: Monday, May 20, 2013 5:50 PM
To: Ingram, William A
Cc: dspac...@lists.sourceforge.net
Subject: Re: [Dspace-tech] debugging the project assembler

Hi Bill,

it looks like it might be this issue (probably related to a filtering feature introduced in DSpace 3):

http://jira.codehaus.org/browse/MASSEMBLY-342

What Maven version are you using? According to our docs DSpace 3.x builds with 2.2.x and higher, but you may have hit a bug. As a workaround, you could try using a higher version of Maven.

Hopefully other guys more familiar with Maven will chime in and help resolve the issue. Can you think of anything out of the ordinary you might have done to trigger this? Perhaps any customizations to the source?


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
DSpace-tech mailing list
DSpac...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Ingram, William A

unread,
Aug 26, 2015, 10:53:56 AM8/26/15
to dspac...@lists.sourceforge.net
I fixed it by adding <directory>.</directory> under the <fileSet> elements in assembly.xml. Now it works.

Solved.
Reply all
Reply to author
Forward
0 new messages