Migrate ant build to maven2

[GoogleCodeExporter]

Migrate ant build to maven2

[GoogleCodeExporter]

Some time ago I prepared a migration script that reorgenises the svn repo 
directory 
structure to align with maven2. Also I created a pom each for the core, 
piccolox and 
examples.

Todos are the reactor build, a parent pom and reports (cobertura, findbugs, 
etc.).

If there's no veto until 2008-06-26 08:00 UTC I'll prepare a branch named 
"mavenize" 
and propose it for reviewing.

Greetings,
    M

Original comment by [email protected] on 21 Jun 2008 at 1:05

• Changed state: Started
• Added labels: Effort-Medium
• Removed labels: Effort-High

[GoogleCodeExporter]

attach files

Original comment by [email protected] on 21 Jun 2008 at 1:16

Attachments:

• piccolo-mavenize.sh
• piccolo-pom.zip

[GoogleCodeExporter]

Original comment by [email protected] on 21 Jun 2008 at 2:30

• Changed state: Accepted

[GoogleCodeExporter]

The migrated build is prepared in a branch.

I'd like you to review the result and tell me if you think it's ready to merge.

Short summary:
- changed directory structure to fit maven2
- added a pom for each jar (piccolo, piccolox, examples)
- added a parent pom with common build settings
- added a reactor build pom to build all at once

Todos:
- maven site destination url
- maven repo url (repo1.maven.org or our own?)
- upload/release process (persons, permissions, urls)

To test the merge, fire the commands in the attached merge.sh against a shell.

Original comment by [email protected] on 23 Jun 2008 at 1:10

• Changed state: Started

Attachments:

• merge.sh

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The correct url is 

http://code.google.com/p/piccolo2d/source/diff?old=26&r=95&format=side&path=
%2Fpiccolo.java%2Fbranches%2Fmavenize

Original comment by [email protected] on 8 Jul 2008 at 10:30

[GoogleCodeExporter]

schedule to 1.3

Original comment by [email protected] on 8 Jul 2008 at 10:31

• Added labels: Milestone-1.3

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I started a new branch (mavenize-1.3), as we want to keep the recent trunk 
changes 
which cannot be merged into the existing mavenize branch. (r117)

After that, I 
- applied the script piccolo-mavenize.sh, 
- added the script to svn
- added the poms from the (old) mavenize branch
- modified the poms to refer to piccolo2d rather than piccolo
- (temporarily) removed checkstyle reports (will come soon)
- and commited r118

If you agree with that, please vote for r118 and we can merge the mavenize-1.3 
into 
trunk and delete both branches (after re-introducing the checkstyle reports).

There are still some minor flaws in the reports (urls pointing wrong) which I 
would 
like to fix in the trunk.

Please note the subprojects are named
- piccolo
- piccolox
- examples

Should we change the naming to
- piccolo2d
- piccolo2dx
- examples
?

Greetings,
    M

Original comment by [email protected] on 21 Jul 2008 at 2:40

[GoogleCodeExporter]

I put the subdirectory renaming into issue#44

Original comment by [email protected] on 22 Jul 2008 at 9:24

[GoogleCodeExporter]

merge done: r121

Original comment by [email protected] on 22 Jul 2008 at 9:47

[GoogleCodeExporter]

Remaining todos:
- checkstyle reports
- deploy maven site (rather a process than a single action)
- verify correctness of site content, especially linking.

Original comment by [email protected] on 22 Jul 2008 at 10:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

As Michael re-added the checkstyle reports, we can drop the two branches 
(mavenize 
and mavenize-1.3) under 
http://piccolo2d.googlecode.com/svn/piccolo2d.java/branches

Ok? If no veto comes I'll do this on saturday.

The maven site deployment also is prepared (issue#45), so this issue just needs 
verification, right?

Original comment by [email protected] on 31 Jul 2008 at 2:00

• Changed state: Fixed

[GoogleCodeExporter]

As nobody seems to object to, I removed the two branches, see r325 and r326

Original comment by [email protected] on 14 Aug 2008 at 5:59

[GoogleCodeExporter]

Original comment by [email protected] on 15 May 2009 at 7:04

• Changed state: Verified