[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-109) Wrapper for calling project's classes using mvn exec:java

[Lincoln Baxter III (JIRA)]

    [ https://issues.jboss.org/browse/SEAMFORGE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597841#comment-12597841 ] 

Lincoln Baxter III commented on SEAMFORGE-109:
----------------------------------------------

JavaExecutionFacet perhaps? Not all projects would necessarily execute using Java. Wondering if this should be in the core API. Dev-plugins isn't a place for feature addition, so for now I'd say let's put it in the Shell-API itself (implemented by the Maven Project Impl)

> Wrapper for calling project's classes using mvn exec:java
> ---------------------------------------------------------
>
>                 Key: SEAMFORGE-109
>                 URL: https://issues.jboss.org/browse/SEAMFORGE-109
>             Project: Seam Forge
>          Issue Type: Feature Request
>          Components: Brainstorming
>            Reporter: Paul Bakker
>            Assignee: Paul Bakker
>
> The Arquillian plugin uses mvn exec:java to invoke @Deployment methods within tests that are part of the user's code. We discussed this on the mailinglist. This is a way to invoke code within the project without having to build a classloader that loads the whole user's classpath.
> This is how I described it on he mailinglist:
> "For the plugin I now just generate a new class with a main method to the project's test-source folder. After that I use an mvn exec:java to run the class. It's less ideal because the plugin now adds a user visible utility class to the project, but it's not really a problem I believe. The exporter class is also runnable outside of Forge, so that's good too."
> I'm still polishing the code, but I'll add a link to github when it's checked in.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira