Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WFLY-2] Convert domain deployments to use operations. Exploded deplo… #102

Merged
merged 1 commit into from
May 18, 2016

Conversation

jamezp
Copy link
Member

@jamezp jamezp commented May 18, 2016

…yments should now work for domain and standalone containers.

…yments should now work for domain and standalone containers.
@jamezp jamezp merged commit ebfa22d into wildfly:master May 18, 2016
@jamezp jamezp deleted the WFMP-2 branch May 18, 2016 18:19
@jwgmeligmeyling
Copy link

Hi! Great enhancement, have been waiting for this feature! How can we use it?

@jamezp
Copy link
Member Author

jamezp commented May 23, 2016

You just need to override the <filename/> and <name/> configuration properties.

<filename>${project.build.finalName}</filename>
<name>${project.build.finalName}.war</name>

Note this is just a path to where the deployment content is located. With the given example above the content from the maven target directory would be deployed.

"content" => [{
    "path" => "/home/jperkins/projects/jboss/examples/javaee/simple-servlet/target/simple-servlet",
    "archive" => false
}],
"enabled" => true,
"enabled-time" => 1464017178837L,
"enabled-timestamp" => "2016-05-23 08:26:18,837 PDT",
"name" => "simple-servlet.war",
"owner" => undefined,
"persistent" => true,
"runtime-name" => "simple-servlet.war",
"subdeployment" => undefined,
"subsystem" => {"undertow" => undefined}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants