Maven EAR deployment - gfdeploy directory issues

[joelstewart]

Glassfish 3.1, Netbeans 7.

After converting my large netbean projects to maven projects, I am having a problem deploying via netbeans.

My ear is being successfully created, and it deploys fine from the registry to glassfish using the admin console.

however when trying to run with netbeas, the gfdeploy ends up doing something strange.

With netbeans projects, the ear modules were copied to directories, so an EJB module name ejbone.jar would be copied as a directory to gfdeploy as ejbone_jar.

When deploying my large ear the gfdeploy directory has BOTH the artifact and exploded versions. Glassfish seems to think I want to deploy the same ejb components multiple times, and so complains and does not deploy the module.

Any idea what might be causing this? Like I said, the EAR produced before trying to run does deploy fine if using the glassfish console. So I don't think it is how the ear is being built - just how the IDE tools in the are trying to deploy it.

[joelstewart]

I installed netbeans 6.9.1 and with no changes, the project deploys to glassfish.

So there is a problem with maven deployment in Netbeans 7.

[jyeary]

Please open an issue in the bug tracker with as much detail as you can provide.

On Mon, Jun 27, 2011 at 2:34 PM, joelstewart <address-removed ([email]address-removed[/email])> wrote: