Initial Auction Example Project structure is available

Imported from Google Groups
1

Hi all,

I created the initial project structure for the new Axon Auction
Example project:
http://code.google.com/p/axon-auction-example/

To make team work easier I will create a shared Pulse (http://
www.poweredbypulse.com/) configuration. This includes all projects and
an (almost) completely configured Eclipse 3.5 environment. Usage of
the Pulse Community Edition is free.

Cheers,
Michael

2

No idea what this pulse is, but if it is only eclipse, I am sure I will not use it. Sorry, I am an intellij user myself.

By the way, am I missing a one pom to build them all? How to build the complete project?

Jettro

3

Hi Jettro,

Yes, it's a tool for Eclipse - It's used to synchronize eclipse
settings (plugins, workspace settings, projects) between users. If you
don't use Eclipse you don't need it.

By the way, am I missing a one pom to build them all? How to build the complete project?

Hmm... I normally use Maven's project inheritance (I have no POM to
build everythig together)... But now I added the other projects as
modules in the "auction-parent" (following the suggestion in the Maven
documentation "Project Inheritance vs Project Aggregation"). I hope
this helps.

Cheers,
Michael

4

Fair enough, I personally prefer to have the parent pom in the root of the project. I guess it is just a matter of taste. I have no problem with this setup

Just a few remarks going over the code:

  • The version of the compiler plugin is a bit strange. Not in a normal maven repository. Better to take 2.3.1 I think
  • I think it is better to generate the MANIFEST.MF file, and if not, put in in the resources folder.
  • project.properties belong in the resources folder as well
  • What is the difference between project.properties and auction-command.properties?
  • I also prefer to have a config module setup, not config property files for each and every module

regards Jettro

5

Hi,

Good work. I’ll start checking out this weekend.

Regards,
Edward Yakop

6

Hi Jettro,

- The version of the compiler plugin is a bit strange. Not in a
normal maven repository. Better to take 2.3.1 I think

Tnx for the hint - It was copied from an old configuration... I
checked all plugins and updated the versions to the newest available
version.

- I think it is better to generate the MANIFEST.MF file, and if not, put
in in the resources folder.

So do I - The files were automatically created by the Eclipse Maven
plugin... I deleted them (until the plugin creates it again :wink:

- What is the difference between project.properties and
auction-command.properties?

The properties in the "resources" folder of the project is included to
get programatically access to the name, version and build time of the
project. You can use Utils.getProjectInfo(..) to read the information.
The other "project.properties" was a bad named duplicate - I deleted
it.

- I also prefer to have a config module setup, not config property files for
each and every module

Hmm... We don't have other properties files at the moment (except
"[project-name].properties") - Not sure what kind of setup you mean
exactly?

Cheers,
Michael

7

Hi all,

I faced problems with the combination of "parent pom" and "modules" in
the same file. Therefore I moved the module definition into a separate
project (auction-root) that can be used to build the complete project.

Cheers,
Michael