https://github.com/stephenc/java-iso-tools is how I write the ISO

On 21 October 2014 08:18, Stephen Connolly <stephen.alan.conno...@gmail.com>
wrote:

> Bernd, no the iso plugin writes ISO files in java. I cannot remember if
> there is a special parser for the format or if I was able to borrow a 3rd
> party one
>
> On 21 October 2014 01:46, Bernd Eckenfels <e...@zusammenkunft.net> wrote:
>
>> Hello David,
>>
>> you can replace the ISO in local builds with a a ZIP file for most
>> cases - but there is also a Windows/cygwin binary available.
>>
>> Or you use the original mkisofs which offers a win32 executable.
>> (http://www.student.tugraz.at/thomas.plank/index_en.html)
>>
>> BTW: for unpacking the ISO in integration test we use loopy, but not
>> sure if it is easy to use for creating.
>>
>> Stephen, does the maven plugin indirectly use loopy as well?
>>
>> Gruss
>> Bernd
>>
>> Am Mon, 20 Oct 2014 18:26:35 -0600
>> schrieb David Hoffer <dhoff...@gmail.com>:
>>
>> > Hi Bernd,
>> >
>> > Tanks for the suggestion, that's an interesting approach.  However I
>> > suspect that's Linux only and that might be deal breaker.  We have
>> > some CI build agents that are Linux but most developers use Windows
>> > and I suspect they will want to run this too.
>> >
>> > Thanks,
>> > -Dave
>> >
>> > On Mon, Oct 20, 2014 at 6:03 PM, Bernd Eckenfels
>> > <e...@zusammenkunft.net> wrote:
>> >
>> > > Hello David,
>> > >
>> > > we are using an external executable to do this.
>> > >
>> > > It is genisoimage from crdkit.org (debian fork of cdrtools). It can
>> > > produce for example Joilet extensions (which are used for long
>> > > filenames AFAIK). There are still filename limitations for ISO names
>> > > (but the joilet names seen on linux/windows are less restrictive). I
>> > > think the tools prints them:
>> > >
>> > > http://linux.die.net/man/1/genisoimage
>> > >
>> > >             <plugin>
>> > >                 <!-- ISO generation. -->
>> > >                 <groupId>org.codehaus.mojo</groupId>
>> > >                 <artifactId>exec-maven-plugin</artifactId>
>> > >                 <version>1.2.1</version>
>> > >                 <executions>
>> > >                     <execution>
>> > >                         <goals>
>> > >                             <goal>exec</goal>
>> > >                         </goals>
>> > >                         <phase>verify</phase>
>> > >                     </execution>
>> > >                 </executions>
>> > >                 <configuration>
>> > >                     <executable>genisoimage</executable>
>> > >                     <arguments>
>> > >                         <argument>-V</argument>
>> > >                         <argument>${iso.name}</argument>
>> > >                         <argument>-m</argument>
>> > >                         <argument>*.iso</argument>
>> > >                         <argument>-dir-mode</argument>
>> > >                         <argument>0555</argument>
>> > >                         <argument>-file-mode</argument>
>> > >                         <argument>0555</argument>
>> > >                         <argument>-gid</argument>
>> > >                         <argument>0</argument>
>> > >                         <argument>-uid</argument>
>> > >                         <argument>0</argument>
>> > >                         <argument>-iso-level</argument>
>> > >                         <argument>2</argument>
>> > >                         <argument>-J</argument>
>> > >                         <argument>-joliet-long</argument>
>> > >                         <argument>-r</argument>
>> > >                         <argument>-o</argument>
>> > >                         <argument>${project.build.directory}/${
>> iso.name
>> > > }</argument>
>> > >                         <argument>${iso.preparation.dir}</argument>
>> > >                     </arguments>
>> > >                 </configuration>
>> > >             </plugin>
>> > >
>> > > The above tries to be rather compatible (not using level 3 or
>> > > version 2 or enforcing Rock Ridge or UDF).
>> > >
>> > > Gruss
>> > > Bernd
>> > >
>> > > Mon, 20 Oct 2014 15:42:42 -0600 schrieb David Hoffer
>> > > <dhoff...@gmail.com>:
>> > >
>> > > > I'm trying to use iso9660-maven-plugin to generate an iso image
>> > > > and I'm getting string index out of range errors.  My input has
>> > > > long file names, e.g.
>> > > >
>> > >
>> 7b0a8ad702ee0be0b971a082023550bd71bd33d3cbb4fa17f1de6af66f1871d4-comps-Server.x86_64.xml.gz
>> > > > and I suspect this is causing the problem.
>> > > >
>> > > > How can I resolve this?  I don't technically need/want an 9660
>> > > > image as I'm creating DVD images (actually these will be used by
>> > > > vSphere and I think it's quite tolerant of ISO format).  Is there
>> > > > a way to configure iso9660-maven-plugin to allow long file names
>> > > > or is there a different goal/plugin that I should be using that
>> > > > supports this? Currently I'm running the 'iso' goal on
>> > > > iso9660-maven-plugin.
>> > > >
>> > > > Example error:
>> > > > Execution generate-iso of goal
>> > > > com.github.stephenc.java-iso-tools:iso9660-maven-plugin:2.0.0:iso
>> > > > failed: String index out of range: -2
>> > > >
>> > > > -Dave
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> > > For additional commands, e-mail: users-h...@maven.apache.org
>> > >
>> > >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

Reply via email to