Ticket #820 (new Improvement)

Opened 3 years ago

Last modified 3 years ago

Alternative genscript implementation.

Reported by: karel Owned by: somebody
Priority: Minor Milestone: 2.5
Component: Maven plugin Version:
Keywords: Cc:

Description

Currently the genscript plugin generates a script containing a long CLASSPATH=... line.
Alternatively we could generate an empty jar with a META-INF/MANIFEST.MF. In the manifest you can put (relative) references to other jars.

The daisy-classpath can be a maven artifact:
daisy/lib/daisy/daisy-classpath/{version}/daisy-classpath-{version}.jar

Now the genscript plugin doesn't need a classpath, but can use
java -cp $DAISY_HOME/.../daisy-classpath-{version}.jar MainClass? ...

Change History

comment:1 Changed 3 years ago by karel

The currently generated CLASSPATH=... line matches the dependencies listed in each project. If we have a single daisy-classpath.jar file, all scripts will use the same classpath.

This is not really a problem, but we have to make sure that the MANIFEST-MF classpath lists enough jars to be usable by many plugins, but small enough not to cause any problems (if there ever are problems, we can still use the CLASSPATH=... approach)
Perhaps the genscript plugin should have an option to choose between using the common classpath.jar or using a full CLASSPATH=... declaration

Note: See TracTickets for help on using tickets.