[JBoss JIRA] (FORGE-137) Add explode and deploy goals to pom.xml during scaffold generation
by Kevin Sapper (Issue Comment Edited) (JIRA)
[ https://issues.jboss.org/browse/FORGE-137?page=com.atlassian.jira.plugin.... ]
Kevin Sapper edited comment on FORGE-137 at 11/14/11 3:12 PM:
--------------------------------------------------------------
Hey Lincoln,
no problem this gave me some time to think of a solution ;)
Here is an example on how I thought to implement this issue for *mvn compile -Pexplode*
{code:xml}
<profile>
<id>explode</id>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${exploded.dir}</webappDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
<executions>
<!-- execute goal war:explode with compile phase -->
<execution>
<id>explode</id>
<phase>compile</phase>
<goals>
<goal>exploded</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>copy-as-deployment-descriptors</id>
<phase>compile</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<touch file="${exploded.dir}.dodeploy" />
</target>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
{code}
Though this works it gets really ant like messy if you plan to implement this for all deploy and explode goals.
Another approach I thought of is to use the the jboss as7 maven plugin. But as they only support deploying this isn't really a complete solution. This also leave the question open on how the implementation for Glassfish will look like?
What do you think?
//Kevin
was (Author: sappo):
Hey Lincoln,
no problem this gave me some time to think of a solution ;)
Here is an example on how I thought to implement this issue for *mvn compile -Pexplode*
{code:xml}
<profile>
<id>explode</id>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${exploded.dir}</webappDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
<executions>
<!-- execute goal war:explode with compile phase -->
<execution>
<id>explode</id>
<phase>compile</phase>
<goals>
<goal>exploded</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>copy-as-deployment-descriptors</id>
<phase>compile</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<touch file="${exploded.dir}.dodeploy" />
</target>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
{code}
Though this works it gets really ant like messy if you plan to implement this for all deploy and explode goals.
Another approach I thought of is to use the the jboss as7 maven plugin. But as they only support deploying this isn't really a complete solution. This also leave the question open on how he implementation for Glassfish will look like?
What do you think?
//Kevin
> Add explode and deploy goals to pom.xml during scaffold generation
> ------------------------------------------------------------------
>
> Key: FORGE-137
> URL: https://issues.jboss.org/browse/FORGE-137
> Project: Forge
> Issue Type: Enhancement
> Components: Forge Build, Maven Integration
> Environment: JBoss 7, JBoss 6, Glassfish 3.1
> Reporter: Kevin Sapper
>
> Hi Guys,
> One of the most compelling features about seam-gen is that after you've build the projects scaffold deploying and exploding to an application server just goes by calling an ant target. It really would be nice to have such a goal in the projects pom.xml after creating the scaffold and boilerplate code. Adding that functionality yourself really takes an awful lot of time. Especially with glassfish 3.1 I failed to accomplish that task.
> Best regards//Kevin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] (FORGE-137) Add explode and deploy goals to pom.xml during scaffold generation
by Kevin Sapper (Issue Comment Edited) (JIRA)
[ https://issues.jboss.org/browse/FORGE-137?page=com.atlassian.jira.plugin.... ]
Kevin Sapper edited comment on FORGE-137 at 11/14/11 3:11 PM:
--------------------------------------------------------------
Hey Lincoln,
no problem this gave me some time to think of a solution ;)
Here is an example on how I thought to implement this issue for *mvn compile -Pexplode*
{code:xml}
<profile>
<id>explode</id>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${exploded.dir}</webappDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
<executions>
<!-- execute goal war:explode with compile phase -->
<execution>
<id>explode</id>
<phase>compile</phase>
<goals>
<goal>exploded</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>copy-as-deployment-descriptors</id>
<phase>compile</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<touch file="${exploded.dir}.dodeploy" />
</target>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
{code}
Though this works it gets really ant like messy if you plan to implement this for all deploy and explode goals.
Another approach I thought of is to use the the jboss as7 maven plugin. But as they only support deploying this isn't really a complete solution. This also leave the question open on how he implementation for Glassfish will look like?
What do you think?
//Kevin
was (Author: sappo):
Hey Lincoln,
no problem this gave me some time to think of a solution ;)
Here is an example on how I thought to implement this issue for *mvn compile -Pexplode*
{code:xml}
<profile>
<id>explode</id>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${exploded.dir}</webappDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
<executions>
<!-- execute goal war:explode with prepare-package phase -->
<execution>
<id>explode</id>
<phase>compile</phase>
<goals>
<goal>exploded</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Manual mode -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>copy-as-deployment-descriptors</id>
<phase>compile</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<touch file="${exploded.dir}.dodeploy" />
</target>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
{code}
Though this works it gets really ant like messy if you plan to implement this for all deploy and explode goals.
Another approach I thought of is to use the the jboss as7 maven plugin. But as they only support deploying this isn't really a complete solution. This also leave the question open on how he implementation for Glassfish will look like?
What do you think?
//Kevin
> Add explode and deploy goals to pom.xml during scaffold generation
> ------------------------------------------------------------------
>
> Key: FORGE-137
> URL: https://issues.jboss.org/browse/FORGE-137
> Project: Forge
> Issue Type: Enhancement
> Components: Forge Build, Maven Integration
> Environment: JBoss 7, JBoss 6, Glassfish 3.1
> Reporter: Kevin Sapper
>
> Hi Guys,
> One of the most compelling features about seam-gen is that after you've build the projects scaffold deploying and exploding to an application server just goes by calling an ant target. It really would be nice to have such a goal in the projects pom.xml after creating the scaffold and boilerplate code. Adding that functionality yourself really takes an awful lot of time. Especially with glassfish 3.1 I failed to accomplish that task.
> Best regards//Kevin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] (FORGE-137) Add explode and deploy goals to pom.xml during scaffold generation
by Kevin Sapper (Issue Comment Edited) (JIRA)
[ https://issues.jboss.org/browse/FORGE-137?page=com.atlassian.jira.plugin.... ]
Kevin Sapper edited comment on FORGE-137 at 11/14/11 4:49 AM:
--------------------------------------------------------------
Hey Lincoln,
no problem this gave me some time to think of a solution ;)
Here is an example on how I thought to implement this issue for *mvn compile -Pexplode*
{code:xml}
<profile>
<id>explode</id>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${exploded.dir}</webappDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
<executions>
<!-- execute goal war:explode with prepare-package phase -->
<execution>
<id>explode</id>
<phase>compile</phase>
<goals>
<goal>exploded</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Manual mode -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>copy-as-deployment-descriptors</id>
<phase>compile</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<touch file="${exploded.dir}.dodeploy" />
</target>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
{code}
Though this works it gets really ant like messy if you plan to implement this for all deploy and explode goals.
Another approach I thought of is to use the the jboss as7 maven plugin. But as they only support deploying this isn't really a complete solution. This also leave the question open on how he implementation for Glassfish will look like?
What do you think?
//Kevin
was (Author: sappo):
Hey Lincoln,
here is an example on how I thought to implement this issue for *mvn compile -Pexplode*
{code:xml}
<profile>
<id>explode</id>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${exploded.dir}</webappDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
<executions>
<!-- execute goal war:explode with prepare-package phase -->
<execution>
<id>explode</id>
<phase>compile</phase>
<goals>
<goal>exploded</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Manual mode -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>copy-as-deployment-descriptors</id>
<phase>compile</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<touch file="${exploded.dir}.dodeploy" />
</target>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
{code}
Though this works it gets really ant like messy if you plan to implement this for all deploy and explode goals.
Another approach I thought of is to use the the jboss as7 maven plugin. But as they only support deploying this isn't really a complete solution. This also leave the question open on how he implementation for Glassfish will look like?
What do you think?
//Kevin
> Add explode and deploy goals to pom.xml during scaffold generation
> ------------------------------------------------------------------
>
> Key: FORGE-137
> URL: https://issues.jboss.org/browse/FORGE-137
> Project: Forge
> Issue Type: Enhancement
> Components: Forge Build, Maven Integration
> Environment: JBoss 7, JBoss 6, Glassfish 3.1
> Reporter: Kevin Sapper
>
> Hi Guys,
> One of the most compelling features about seam-gen is that after you've build the projects scaffold deploying and exploding to an application server just goes by calling an ant target. It really would be nice to have such a goal in the projects pom.xml after creating the scaffold and boilerplate code. Adding that functionality yourself really takes an awful lot of time. Especially with glassfish 3.1 I failed to accomplish that task.
> Best regards//Kevin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] (FORGE-137) Add explode and deploy goals to pom.xml during scaffold generation
by Kevin Sapper (Commented) (JIRA)
[ https://issues.jboss.org/browse/FORGE-137?page=com.atlassian.jira.plugin.... ]
Kevin Sapper commented on FORGE-137:
------------------------------------
Hey Lincoln,
here is an example on how I thought to implement this issue for *mvn compile -Pexplode*
{code:xml}
<profile>
<id>explode</id>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${exploded.dir}</webappDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
<executions>
<!-- execute goal war:explode with prepare-package phase -->
<execution>
<id>explode</id>
<phase>compile</phase>
<goals>
<goal>exploded</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Manual mode -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>copy-as-deployment-descriptors</id>
<phase>compile</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<touch file="${exploded.dir}.dodeploy" />
</target>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
{code}
Though this works it gets really ant like messy if you plan to implement this for all deploy and explode goals.
Another approach I thought of is to use the the jboss as7 maven plugin. But as they only support deploying this isn't really a complete solution. This also leave the question open on how he implementation for Glassfish will look like?
What do you think?
//Kevin
> Add explode and deploy goals to pom.xml during scaffold generation
> ------------------------------------------------------------------
>
> Key: FORGE-137
> URL: https://issues.jboss.org/browse/FORGE-137
> Project: Forge
> Issue Type: Enhancement
> Components: Forge Build, Maven Integration
> Environment: JBoss 7, JBoss 6, Glassfish 3.1
> Reporter: Kevin Sapper
>
> Hi Guys,
> One of the most compelling features about seam-gen is that after you've build the projects scaffold deploying and exploding to an application server just goes by calling an ant target. It really would be nice to have such a goal in the projects pom.xml after creating the scaffold and boilerplate code. Adding that functionality yourself really takes an awful lot of time. Especially with glassfish 3.1 I failed to accomplish that task.
> Best regards//Kevin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] (FORGE-137) Add explode and deploy goals to pom.xml during scaffold generation
by Lincoln Baxter III (Commented) (JIRA)
[ https://issues.jboss.org/browse/FORGE-137?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on FORGE-137:
------------------------------------------
Hey Kevin,
Sorry for the late reply. I've been on the road at conferences.
These command breakdowns look good, but does this actually make this functionality available when using maven standalone? It looks like these are just Forge commands. Is that what you want?
I'm not really clear how you plan to implement this approach (but that doesn't mean I'm against it, just that I want to know more.) Thoughts?
~Lincoln
> Add explode and deploy goals to pom.xml during scaffold generation
> ------------------------------------------------------------------
>
> Key: FORGE-137
> URL: https://issues.jboss.org/browse/FORGE-137
> Project: Forge
> Issue Type: Enhancement
> Components: Forge Build, Maven Integration
> Environment: JBoss 7, JBoss 6, Glassfish 3.1
> Reporter: Kevin Sapper
>
> Hi Guys,
> One of the most compelling features about seam-gen is that after you've build the projects scaffold deploying and exploding to an application server just goes by calling an ant target. It really would be nice to have such a goal in the projects pom.xml after creating the scaffold and boilerplate code. Adding that functionality yourself really takes an awful lot of time. Especially with glassfish 3.1 I failed to accomplish that task.
> Best regards//Kevin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months