Re: [udig-devel] uDig build & walkthrough for MacOs

["Severin (aka Cliff)" <djseverin@xxxxxxxxx>]

Hi Jody,

Would you please take a look at https://github.com/uDig/udig-platform/pull/134

I have added some extra sexy to the Mac side of the deploy scripts.

Paths are now "space" safe & I've added basic Mac DMG generation.

Cheers,

--Sev

On 31 August 2012 14:52, Severin (aka Cliff) <djseverin@xxxxxxxxx> wrote:

Or just plug the deploy directly into maven:

'

<artifactId>exec-maven-plugin</artifactId>

<groupId>org.codehaus.mojo</groupId>

<executions>

  <execution>

    <id>Pre-deployment packaging</id>

    <phase>install</phase>

    <goals>

      <goal>exec</goal>

    </goals>

    <configuration>

      <executable>${basedir}/deploy/all.sh</executable>

    </configuration>

  </execution>

<executions>

On 31 August 2012 14:47, Severin (aka Cliff) <djseverin@xxxxxxxxx> wrote:

The deploy script is rather nice.

It would/will be very easy for me to build a real DMG file rather than a zip.

:-)

On 31 August 2012 14:44, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

just submit a pull request; we can save jira for actual application problems :-)

And yes I am only a noob at writing scripts

-- 

Jody Garnett

On Friday, 31 August 2012 at 2:43 PM, Severin (aka Cliff) wrote:

Found a bug in the deploy script. It doesn't account for spaces in the file system path.

I've written a fix that I'm testing. Will raise a Jira, fix and submit a push request.

On 31 August 2012 13:39, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

The .options file is "optional"; it is generally used when debugging a users install of uDig. As a developer you can email out a ".options" file to turn on different tracing options; and then ask for a log to be sent back.

We found it easier to make a big .options file of everything; so we can ask people to just turn to "true" the bit they are interested in debugging.

The workflow is described in our users guide:

- http://udig.github.com/docs/user/Support.html

-- 

Jody Garnett

On Friday, 31 August 2012 at 1:23 PM, Severin (aka Cliff) wrote:

Out of curiosity, why do you manually copy .options to the package's MacOS directory?

The support functions shell script, prepare_resources for mac performs a copy of .options into the udig.app/MacOS directory.

Just curious as to why you did this.

--Sev

On 31 August 2012 12:25, Severin (aka Cliff) <djseverin@xxxxxxxxx> wrote:

Figured it was something I was (not) doing. :-)

I'll run the deploy script and re-test. I assume that's the step I was missing.

I have been testing against head from GitHub. I can test Walkthrough 2 against the snapshots from uDig website rather than building myself.

On 31 August 2012 12:23, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

If you get a few moments, would be great to compare notes. It's probably something simple. :-)

I'm building uDig packages using "mvn clean install -Pproduct -DskipTests"

When it's all done, I look in:

"udig-platform-HEAD/features/net.refractions.udig-product/target/products/"

The next step is:

cd deploy

./all.sh

This will take the  features/net.refractions.udig-product/target/products contents and fix them up and place them in deploy/build 

If you have makensis installed it will also produce windows installers.

If you need to check configuration please edit the file "version.sh".

Still this does answer my question - you have not been testing the snapshots I uploaded :-)

(whew I thought i was doing something wrong)

Jody

--
"We are dreamers, shapers, singers and makers..."

--
"We are dreamers, shapers, singers and makers..."

--
"We are dreamers, shapers, singers and makers..."

--
"We are dreamers, shapers, singers and makers..."

--
"We are dreamers, shapers, singers and makers..."

--
"We are dreamers, shapers, singers and makers..."