Opened 17 years ago
Closed 16 years ago
#112 closed defect (fixed)
Illumina plug-in installer script fails (in some cases)
Reported by: | Jari Häkkinen | Owned by: | Martin Svensson |
---|---|---|---|
Priority: | major | Milestone: | Illumina package v1.2 |
Component: | net.sf.basedb.illumina | Keywords: | |
Cc: |
Description
The plug-in installer fails when I try to rerun it with the below stack trace. I have set the error option to 'skip' for already existing items.
net.sf.basedb.core.ItemAlreadyExistsException: Item already exists: nullBGX file has invalid jar path. This datafiletype can not be used. at net.sf.basedb.illumina.install.Install.createDataFileType(Install.java:780) at net.sf.basedb.illumina.install.Install.installIlluminaItems(Install.java:469) at net.sf.basedb.illumina.install.Install.run(Install.java:266) at net.sf.basedb.core.PluginExecutionRequest.invoke(PluginExecutionRequest.java:108) at net.sf.basedb.core.InternalJobQueue$JobRunner.run(InternalJobQueue.java:487) at java.lang.Thread.run(Thread.java:619)
Change History (7)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Component: | net.sf.basedb.examples.extensions → net.sf.basedb.illumina |
---|
comment:3 by , 17 years ago
Summary: | Illumina plug-in installer script fails → Illumina plug-in installer script fails (in some cases) |
---|
comment:4 by , 16 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 16 years ago
In some way the jar path of the validator and the meta-data reader is different compare to the jar path used by the installation plug-in.
The message is a bit cryptic and should be changed.
Perhaps a 'use'-option should be added to alternatives of how existing items should be handled?
comment:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I should maybe mention that on my 2.7.0pre I have no problems but on a 2.6.2 I get the stacktrace.