Hi gang,
No surprise for those scanning the svn commit list, but for the rest
of you humans, I just wanted to let you know I just commited a maven
archetype for creating Magnolia modules. I also deployed a snapshot
on the maven repository.
For those wondering what the hell I'm talking about:
http://maven.apache.org/guides/introduction/introduction-to-
archetypes.html
http://maven.apache.org/guides/mini/guide-creating-archetypes.html
For those who want to give it a try:
mvn archetype:create -DarchetypeGroupId=info.magnolia \
-DarchetypeArtifactId=maven-archetype-magnolia-
module \
-DarchetypeVersion=1.0.0-SNAPSHOT \
-DgroupId=com.foo.bar \
-DartifactId=my-module \
-DremoteRepositories=http://svn.magnolia.info/
maven/snapshots
Please try it out and tell us what you think !
Jira: http://jira.magnolia.info/browse/MPARCH
As a site note, I introduced a parent pom for our maven plugins: you
can checkout http://svn.magnolia.info/view/maven-plugins/maven-
plugins-parent/trunk/ and download all the modules from there with
the shell script. However, the parent pom version 1 is released/
deploy. The simple sequence number version scheme was chosen because
in the case of a pom that doesnt "belong" to a given project, the
x.y.z versioning doesn't really make sense, since there won't be such
things as bugs or api changes for it. So all plugins currently use
maven-plugins-parent version 1 as their parent.
Cheers
greg
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
