Carlo --

I don't have an immediate 64-bit Windows install to try this out, but
I have a few notes for you.

The fastest route to get you up & running is to install a 32-bit JDK
on your machine, point your path to that, and then run the piccolo2d
build (w/o any modifications) and that should work.


* I'm not sure why Piccolo is pegged to 3.3.0 of SWT, but looking at
the "older releases" download section on,
I don't see a 64-bit version of SWT 3.3.0, there may not be one. This
is why I suggest your fastest route is to just use the 32-bit
* If you want to try 64-bit then the SWT site *does* have 64-bit
binaries of its latest stable release (SWT 3.6.1). You should get this
64-bit version into your local maven repository and try to build
against that. It's possible/likely that SWT3.6.1 is not yet in a maven
public repo, so to get it into your local Maven repo, you'll want to
download it straight from the SWT website and then do a mvn
install:install-file to get it into your local repo. (For more on mvn
* Once you get SWT 64-bit into your local repo, then you'll need to
update the Piccolo2D swt pom to point to that. Not the parent pom, but
the *swt* pom. You'll see a dependency there that looks like this:


You can update this directly, replacing the two ${swt.*}s with the
groupId and artifactId you specified when you did the mvn
install:install-file. Then you should be able to build, assuming
Piccolo2D works nicely on SWT 3.6.1. (You don't really need to mess
with the profiles just yet, they are a way to set swt.groupId and
swt.artifactId based on your system.)

Would love to hear how this goes for you, and maybe we could use what
you learn to make the Piccolo2D build even more cross-platform.

Oh, as you're learning maven, this might help you as you iterate to
get the swt build to work for you....

* Execute "mvn -Dmaven.test.skip install" at the project's root this
will build & install all the piccolo2d binaries to the root, without
running unit tests (faster).
* Even if the SWT build fails, all the previous modules should be
installed, so now you can just "cd swt" and simply "mvn install" there
as you sort out your SWT stuff.


On Dec 23, 9:46 am, Carlo Salinari <> wrote:
> Hi,
> Being maven-ignorant (I'll study it. Promise.) I need a little hand
> building branches\release-1.3\swt under windows 7 64bit.
> My mvn -version says:
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_23
> Java home: C:\Program Files\Java\jdk1.6.0_23\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
> following
> tried adding this to release-1.3\swt\pom.xml:
>     <profile>
>       <id>windows_64</id>
>       <activation>
>         <os>
>           <family>windows</family>
>           <arch>amd64</arch>
>         </os>
>       </activation>
>       <properties>
>         <swt.groupId>org.eclipse.swt.win32.win32</swt.groupId>
>         <swt.artifactId>x86_64</swt.artifactId>
>       </properties>
>     </profile>
>     <profile>
> but it didn't make the trick. I guess I also have to tell maven where to
> fetch swt.win32.win32.x86_64, right? Should I modify the parent pom?
> Btw: why is the dependency
>       <version>[3.3.0-v3346,)</version>
> so strict?
> cheers,
> Carlo

Piccolo2D Developers Group:

Reply via email to