5:46 a.m.
[
https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi...
]
Darryl Miles edited comment on JBIDE-18860 at 12/2/14 6:45 AM:
---------------------------------------------------------------
Version 1 of a sample set of 6 Maven projects:
org.example.jbide18860.build/ Faceted:no
org.example.jbide18860.ear/ Faceted:yes EAR:6
org.example.jbide18860.ejb/ Faceted:no
org.example.jbide18860.jar/ Faceted:no
org.example.jbide18860.parent/ Faceted:no
org.example.jbide18860.war/ Faceted:yes (nothing set)
* I indicate the Eclipse faceted project dialog info as maybe it is relevant to the
problem.
* I added projects to workspace with File -> Import -> Existing Maven Projects ->
Select all 6 projects at once
* Did Maven -> Update Project on each project in turn.
* On org.eclipse.jbide18860.build do Run As -> Maven: install, to confirm success.
* Then manually inspect EAR in EAR project targets folder for correctness, this would be:
{noformat}
$ unzip -lv org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear
Archive: org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/
146 Defl:N 119 19% 12-02-2014 11:39 5249c220 META-INF/MANIFEST.MF
0 Stored 0 0% 12-02-2014 11:39 00000000 lib/
3722 Defl:N 1855 50% 12-02-2014 11:39 9fd53ec2
lib/org-example-jbide18860-jar-0.0.1-SNAPSHOT.jar
29257 Defl:N 25597 13% 12-02-2014 11:39 0495bd31
lib/org-slf4j-slf4j-api-1.7.7.jar
632 Defl:N 308 51% 12-02-2014 11:39 991766b3 META-INF/application.xml
438 Defl:N 227 48% 12-02-2014 11:39 604fe086
META-INF/jboss-deployment-structure.xml
4978 Defl:N 2565 49% 12-02-2014 11:39 9ac1bc7b
org-example-jbide18860-ejb-0.0.1-SNAPSHOT.jar
33646 Defl:N 31086 8% 12-02-2014 11:39 2c580520
org-example-jbide18860-war-0.0.1-SNAPSHOT.war
0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/
0 Stored 0 0% 12-02-2014 11:39 00000000
META-INF/maven/org.example.jbide18860/
0 Stored 0 0% 12-02-2014 11:39 00000000
META-INF/maven/org.example.jbide18860/ear/
2651 Defl:N 783 71% 12-02-2014 11:20 dd27064a
META-INF/maven/org.example.jbide18860/ear/pom.xml
124 Defl:N 123 1% 12-02-2014 11:39 9c182c62
META-INF/maven/org.example.jbide18860/ear/pom.properties
-------- ------- --- -------
75594 62663 17% 14 files
{noformat}
* Import all projects into Eclipse workspace.
* Build the *.build project with maven using target verify (or better such as
install/deploy)
* Example the *.ear/target/*.ear file and the contents. Deploy this file manually to the
AS to confirm it is valid and works.
* Now try to use the server runtime, but add the EAR project as the module.
The EJB and WAR projects do not make it into the
wildfly-8.x.0.Final\standalone\deployments\*.ear\ folder for me.
I would expect it to just work in that scenario.
In the server runtime view for me there is nothing listed underneath the EAR tree created.
Sometimes I see my JAR and EJB and WAR. But not after the follow procedure.
was (Author: dlmiles):
Version 1 of a sample set of 6 Maven projects:
org.example.jbide18860.build/ Faceted:no
org.example.jbide18860.ear/ Faceted:yes EAR:6
org.example.jbide18860.ejb/ Faceted:no
org.example.jbide18860.jar/ Faceted:no
org.example.jbide18860.parent/ Faceted:no
org.example.jbide18860.war/ Faceted:yes (nothing set)
* I indicate the Eclipse faceted project dialog info as maybe it is relevant to the
problem.
* I added projects to workspace with File -> Import -> Existing Maven Projects ->
Select all 6 projects at once
* Did Maven -> Update Project on each project in turn.
* On org.eclipse.jbide18860.build do Run As -> Maven: install, to confirm success.
* Then manually inspect EAR in EAR project targets folder for correctness, this would be:
{noformat}
$ unzip -lv org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear
Archive: org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/
146 Defl:N 119 19% 12-02-2014 11:39 5249c220 META-INF/MANIFEST.MF
0 Stored 0 0% 12-02-2014 11:39 00000000 lib/
3722 Defl:N 1855 50% 12-02-2014 11:39 9fd53ec2
lib/org-example-jbide18860-jar-0.0.1-SNAPSHOT.jar
29257 Defl:N 25597 13% 12-02-2014 11:39 0495bd31
lib/org-slf4j-slf4j-api-1.7.7.jar
632 Defl:N 308 51% 12-02-2014 11:39 991766b3 META-INF/application.xml
438 Defl:N 227 48% 12-02-2014 11:39 604fe086
META-INF/jboss-deployment-structure.xml
4978 Defl:N 2565 49% 12-02-2014 11:39 9ac1bc7b
org-example-jbide18860-ejb-0.0.1-SNAPSHOT.jar
33646 Defl:N 31086 8% 12-02-2014 11:39 2c580520
org-example-jbide18860-war-0.0.1-SNAPSHOT.war
0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/
0 Stored 0 0% 12-02-2014 11:39 00000000
META-INF/maven/org.example.jbide18860/
0 Stored 0 0% 12-02-2014 11:39 00000000
META-INF/maven/org.example.jbide18860/ear/
2651 Defl:N 783 71% 12-02-2014 11:20 dd27064a
META-INF/maven/org.example.jbide18860/ear/pom.xml
124 Defl:N 123 1% 12-02-2014 11:39 9c182c62
META-INF/maven/org.example.jbide18860/ear/pom.properties
-------- ------- --- -------
75594 62663 17% 14 files
{noformat}
Import all projects into Eclipse workspace.
Build the *.build project with maven using target verify (or better such as
install/deploy)
Example the *.ear/target/*.ear file and the contents. Deploy this file manually to the AS
to confirm it is valid and works.
* Now try to use the server runtime, but add the EAR project as the module.
The EJB and WAR projects do not make it into the
wildfly-8.x.0.Final\standalone\deployments\*.ear\ folder for me.
I would expect it to just work in that scenario.
In the server runtime view for me there is nothing listed underneath the EAR tree created.
Sometimes I see my JAR and EJB and WAR. But not after the follow procedure.
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)
4144
days inactive
4144
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Darryl Miles (JIRA)