[forge-issues] [JBoss JIRA] (FORGE-625) Remove Maven exec plugin configuration from dist module

George Gastaldi (JIRA) jira-events at lists.jboss.org
Tue Aug 21 17:15:15 EDT 2012


     [ https://issues.jboss.org/browse/FORGE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Gastaldi closed FORGE-625.
---------------------------------

         Assignee: George Gastaldi
    Fix Version/s: 1.0.7.Final
       Resolution: Done

    
> Remove Maven exec plugin configuration from dist module
> -------------------------------------------------------
>
>                 Key: FORGE-625
>                 URL: https://issues.jboss.org/browse/FORGE-625
>             Project: Forge
>          Issue Type: Enhancement
>          Components: Documentation, Init Scripts
>    Affects Versions: 1.0.5.Final
>            Reporter: George Gastaldi
>            Assignee: George Gastaldi
>            Priority: Trivial
>              Labels: starter
>             Fix For: 1.0.7.Final
>
>
> As for now, the best way to start forge is to get into dist/target/forge-distribution-1.0.6-SNAPSHOT/bin and run ./forge.
> However, some time ago it used to be run using mvn exec:exec, which should no longer be used, since it has some issues with JBoss modules itself.
> The following should be removed from pom.xml in dist module and documentation should be properly updated:
> {code:xml}
>       <profile>
>          <id>runForge</id>
>          <build>
>             <plugins>
>                <plugin>
>                   <groupId>org.codehaus.mojo</groupId>
>                   <artifactId>exec-maven-plugin</artifactId>
>                   <version>1.2.1</version>
>                   <configuration>
>                      <executable>java</executable>
>                      <workingDirectory>${java.io.tmpdir}</workingDirectory>
>                      <arguments>
>                         <argument>-cp</argument>
>                         <classpath />
>                         <argument>org.jboss.modules.Main</argument>
>                         <argument>-modulepath</argument>
>                         <argument>${project.build.directory}/${project.artifactId}-${forge.release.version}/modules:${user.home}/.forge/plugins</argument>
>                         <argument>org.jboss.forge</argument>
>                      </arguments>
>                   </configuration>
>                </plugin>
>             </plugins>
>          </build>
>       </profile>
>       <profile>
>          <id>debugForge</id>
>          <build>
>             <plugins>
>                <plugin>
>                   <groupId>org.codehaus.mojo</groupId>
>                   <artifactId>exec-maven-plugin</artifactId>
>                   <version>1.2.1</version>
>                   <configuration>
>                      <executable>java</executable>
>                      <workingDirectory>${java.io.tmpdir}</workingDirectory>
>                      <arguments>
>                         <argument>-Xdebug</argument>
>                         <argument>${debug.props}</argument>
>                         <argument>-cp</argument>
>                         <classpath />
>                         <argument>org.jboss.modules.Main</argument>
>                         <argument>-modulepath</argument>
>                         <argument>${project.build.directory}/${project.artifactId}-${forge.release.version}/modules:${user.home}/.forge/plugins</argument>
>                         <argument>org.jboss.forge</argument>
>                      </arguments>
>                   </configuration>
>                </plugin>
>             </plugins>
>          </build>
>       </profile>
> {code}

--
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

        


More information about the forge-issues mailing list