[ 
http://jira.codehaus.org/browse/MOJO-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike R. Haller updated MOJO-961:
--------------------------------

    Attachment: pde-ConsoleLog-withTests.patch

Same patch but with unit tests extended to use consoleLog parameter

> Provide config option to enable Equinox Console Logging
> -------------------------------------------------------
>
>                 Key: MOJO-961
>                 URL: http://jira.codehaus.org/browse/MOJO-961
>             Project: Mojo
>          Issue Type: Improvement
>          Components: pde
>            Reporter: Mike R. Haller
>            Priority: Trivial
>         Attachments: pde-ConsoleLog-ConfigProperty.patch, 
> pde-ConsoleLog-withTests.patch
>
>
> For debugging purposes, it would be nice to have a way to enable the Equinox 
> Console Logging by adding the -consoleLog command line argument to the launch 
> of PDE build. This way, errors of the PDE Build itself (like missing bundles, 
> compile errors) are displayed right in the shell and the builder does not 
> need to go search for the log files.
> Configuration example:
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0";
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/maven-v4_0_0.xsd";>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>com.example.ch.jdf</groupId>
>   <artifactId>com.example.ch.jdf.application</artifactId>
>   <packaging>zip</packaging>
>   <name>com.example.ch.jdf.application Plugin</name>
>   <version>1.4.0-SNAPSHOT</version>
>   <description>Main Application Plugin</description>
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>pde-maven-plugin</artifactId>
>         <version>1.0-alpha-2-SNAPSHOT</version>
>         <extensions>true</extensions>
>         <configuration>
>           
>           <!-- Path to a full-blown Eclipse installation with all required 
> plugins
>                such as BIRT, EMF, GMF, Draw2d etc. -->
>           <eclipseInstall>C:/target/eclipse</eclipseInstall>
>           
>           <!-- Enable console log to show Eclipse errors in the terminal -->
>           <consoleLog>true</consoleLog>
>           
>           <!-- This is very verbose, prints out which properties are being 
> set -->
>           <antDebug>false</antDebug>
>           <antVerbose>false</antVerbose>
>                 
>         <pdeProductFilename>example.product</pdeProductFilename>
>           
>           <!-- From filename of 
> C:\java\eclipse-3.3\eclipse\plugins\org.eclipse.pde.build_3.3.0.v20070612\scripts\productBuild
>  -->
>           <pdeBuildVersion>3.3.0.v20070612</pdeBuildVersion>
>           
>           <!-- A temp folder for compiling classes -->
>         <pdeBuildTempFolder>c:/pdebuild/</pdeBuildTempFolder>
>          </configuration>
>       </plugin>
>     </plugins>
>   </build>
> </project>
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to