Comments on: Maven PAR Plugin 1.0.0.M1

By: Primeiros passos no uso do Spring MVC » klebermota.eti.br

Primeiros passos no uso do Spring MVC » klebermota.eti.br — Mon, 21 Nov 2011 13:12:13 +0000

[...] Maven PAR Plugin 1.0.0.M1 [...]

By: Ben Hale

Ben Hale — Thu, 19 Nov 2009 08:42:25 +0000

PAR files are not supposed to have a persistence.xml file in META-INF/ in fact the only thing they can currently contain are JARs at the root level. Therefore the plugin does not support including any files other than JARs and putting them in the root level.

By: ralph

ralph — Mon, 16 Nov 2009 18:57:48 +0000

I'm trying to use this plugin to build a par file, however I could not include within this par file the file META-INF/persistence.xml assuming that this folder META-INF is in src/main/resources of my maven project.

Could you please if it is possible to do it?

Thanks.

By: Neale

Neale — Tue, 13 Oct 2009 13:38:17 +0000

@Ben

As someone using Maven in anger, you might like to comment on http://jira.codehaus.org/browse/MNG-4391, which is proposing a cleaner way (for Maven 3) to deal with artifactId changes that come from the use of Spring EBR bundles. It would be good to get a "SpringSource view" on this, as you guys are using Maven quite heavily now.

By: Zac Thompson

Zac Thompson — Fri, 31 Jul 2009 23:47:59 +0000

@Ben – I see, but as it also says on that page, the Maven project is assumed to have control over that groupId. You are colliding with an existing unrelated plugin.

http://maven.apache.org/guides/mini/guide-naming-conventions.html

Since you are already asking users to add a repository, adding a pluginGroup is a reasonable step, and would avoid confusion.

By: Ben Hale

Ben Hale — Mon, 27 Jul 2009 11:06:04 +0000

@Adrian

There is now a 1.0.0.RELEASE version available for you.

By: Adrian Skehill

Adrian Skehill — Mon, 27 Jul 2009 10:58:50 +0000

@Ben,

Finally got to test this plug-in after doing a build with git and it worked well for me. I'll revert my builds back to the older version until the new milestone is published.

Cheers,
Adrian.

By: Ben Hale

Ben Hale — Mon, 27 Jul 2009 06:35:17 +0000

@Zac,

We used the org.apache.maven.plugins group because that is the only group that Maven will search automatically for a plugin based on convention. Any other group would have required extra user configuration. See here: http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html

By: Zac Thompson

Zac Thompson — Fri, 24 Jul 2009 17:45:20 +0000

Why are you using org.apache.maven.plugins as the group for this? Is this associated with the apache sandbox effort here?:

http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-par-plugin/pom.xml

By: Ben Hale

Ben Hale — Wed, 22 Jul 2009 05:16:31 +0000

@Leonid,

Thanks for the tip about the typo. I've updated the post with the proper tag name.

The release repository is the proper location for the 1.0.0.RELEASE version (and subsequent releases). A good place to keep an eye on changes and features being added is in the fisheye for the maven-par-plugin. https://fisheye.springsource.org/changelog/maven-par-plugin

The way the sample works without applicationDescription is by the use of defaulting. Since the POM has a ${project.description} specified, it's automatically populated in the par-plugin configuration. One thing that you have illustrated though is that Application-Description is not a required header in a PAR. I'm going to fix and rev the release shortly making that and some of the other headers properly optional.

Thanks again for looking at the plugin and providing feedback.