-
1. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
jamezp Oct 6, 2015 6:44 PM (in response to tadhg.pearson)What does the plugin configuration look like? There's no reason it shouldn't work.
--
James R. Perkins
-
2. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
tadhg.pearson Oct 9, 2015 10:43 AM (in response to jamezp)Absolutely nothing exciting:
<plugin> <groupId>org.wildfly.plugins</groupId> <artifactId>wildfly-maven-plugin</artifactId> <version>1.1.0.Alpha4</version> </plugin> and I'm starting Wildfly using standalone.bat, on Windows 7.
-
3. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
jamezp Oct 9, 2015 4:28 PM (in response to tadhg.pearson)Does it work with an older version of the plugin by chance. Like maybe version 1.0.2.Final.
--
James R. Perkins
-
4. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
tadhg.pearson Oct 9, 2015 4:34 PM (in response to jamezp)No. I've tried 1.0.2, and the latest alpha 1 and alpha 4, none of them work.
-
5. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
jamezp Oct 9, 2015 4:37 PM (in response to tadhg.pearson)What's the rest of the environment look like? I've not heard this issue come up before. Maybe try running mvn clean wildfly:deploy -X to see if anything odd pops up.
--
James R. Perkins
-
6. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
tadhg.pearson Oct 12, 2015 9:27 AM (in response to jamezp)Aha, good idea!
Interestingly, I have this in the debugging output
[DEBUG] Configuring mojo org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Alpha4:redeploy from plugin realm ClassRealm[plugin>org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Alpha4, parent: sun.misc.Launcher$AppClassLoader@4e25154f]
[DEBUG] Configuring mojo 'org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Alpha4:redeploy' with basic configurator -->
[DEBUG] (f) checkPackaging = true
[DEBUG] (f) hostname = localhost
[DEBUG] (f) port = 9990
[DEBUG] (f) project = MavenProject: com.amadeus.inr:sandbox-application:1.2.44-SNAPSHOT @ G:\jdevgit\travel-innovation-sandbox\application\pom.xml
[DEBUG] (f) settings = org.apache.maven.execution.SettingsAdapter@30798137
[DEBUG] (f) skip = true
[DEBUG] (f) targetDir = G:\jdevgit\travel-innovation-sandbox\application\target
[DEBUG] (f) timeout = 60
[DEBUG] -- end configuration --
[DEBUG] Skipping deployment of com.amadeus.inr:sandbox-application
Obviously, if it skips the deployment, well then, it's not going to work.
That said, I haven't changed the default config, and my system is
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T16:10:27-04:00)
Maven home: C:\bin\apache-maven-3.3.1
Java version: 1.8.0_51, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_51\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
I have no idea why it skips, but it's easily fixed with a small config change
Many thanks for your help James!
<plugin> <groupId>org.wildfly.plugins</groupId> <artifactId>wildfly-maven-plugin</artifactId> <version>1.1.0.Alpha4</version> <configuration><skip>false</skip></configuration> </plugin>
-
7. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
jamezp Oct 13, 2015 6:00 AM (in response to tadhg.pearson)Is this possibly a child pom? It could be the parent pom has skip set to true.
--
James R. Perkins
-
8. Re: Wildfly maven plugin commands not acting upon Wildfly 8.2
tadhg.pearson Oct 13, 2015 11:08 AM (in response to jamezp)Yes - that is exactly what happened, it got pushed into a super-parent pom without me noticing. Apparently my team-mates weren't using the same combination of branches, meaning I was the only person experiencing the problem