[jbosstools-issues] [JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

[Darryl Miles (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024373#comment-13024373 ] 

Darryl Miles commented on JBIDE-18860:
--------------------------------------

>> If there is anyway you can give us a copy of the project or even just its dot-metadata (files/folders starting with ., i.e. .project, .classpath, .settings/* etc.) so we could try and reproduce.

I am using this test case org.example.jbide18860.* Maven project suite to re-create the issues I face in a more complex scenario and report one issue at a time as I find it.

I shall make the TAR.GZ file more complex as time goes by (multiple JARs/EJBs/WARs etc... as necessary to cause the problem(s) I see).

But I must knock down each issue as I re-create it.  The journey towards the more complex environment should help find the areas of problems to maybe allow auto-detection/fix by JBIDE tooling by using error markers on the project explaining what is badly configured or wrong with the setup.

> Publish to Wildfly AS does not update files
> -------------------------------------------
>
>                 Key: JBIDE-18860
>                 URL: https://issues.jboss.org/browse/JBIDE-18860
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Final
>         Environment: Windows7 64bit, JDK8u25
>            Reporter: Darryl Miles
>            Priority: Critical
>             Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1
>
>         Attachments: org.example.jbide18860.tar.gz
>
>
> I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016)
> I have an EAR Maven project published to Wildfly 8.x.
> there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml
> If this file is edited and saved, and I perform publish operation on server.  The change is never made to the deployments directory.
> If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted.
> The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server.
> Now the file is updated.
> I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there.
> I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\**
> The timestamps on the files in this directory appear to be up-to-date at each publish event.
> As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear  and I use a manual Maven build profile to create this file.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)