Patch applied in 3.3.x and trunk.

I'd still like Rob Stryker to take a look at what I might have missed.

Change By: Fred Bricon (15/Jun/12 10:46 AM)
Description: *  open *JBDS* (after having installed the eap server)
*
 Create a new remote catalog in preferences > maven > archetypes, poiting to http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml
* Create a new maven project (select Open Archetypes catalog, check "include snapshot archetypes")
* select multi-javaee6-archetype
* define GAV properties and finish
* A multimodule project will be created : Parent project, EAR containing EJB and Web. The web project references a utility project.
* Deploy on EAP6 
* ASSERT the utility project is deployed under <web>.war/WEB-INF/lib <= FAILS
* ASSERT the utility project has no red cross in the server view, under the deployed modules <= FAILS


Logs show that stacktrace : 
{noformat}
java.io.IOException: Le chemin d’accès spécifié est introuvable
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createTempFile(File.java:1879)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.createForceZippedChild(AbstractServerToolsPublisher.java:254)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.transferForceZippedChild(AbstractServerToolsPublisher.java:303)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:223)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:117)
at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7JSTPublisher.publishModuleToAS7(JBoss7JSTPublisher.java:60)
at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7JSTPublisher.publishModule(JBoss7JSTPublisher.java:40)
at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:75)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at org.jboss.ide.eclipse.as.core.server.internal.v7.DelegatingJBoss7ServerBehavior.publishModule(DelegatingJBoss7ServerBehavior.java:75)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

{noformat}

IOException message = path not found

The same project deploys properly in AS 7.1

!JBIDE_12188.png!
Workaround Description: Manually create <workspace>\.metadata\.plugins\org.jboss.ide.eclipse.as.core\jboss-eap\tempDeploy\
Workaround: Workaround Exists
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira