[jira] Created: (MEJB-28) outputDirectory is not created before packaging

outputDirectory is not created before packaging
-----------------------------------------------

                 Key: MEJB-28
                 URL: http://jira.codehaus.org/browse/MEJB-28
             Project: Maven 2.x Ejb Plugin
          Issue Type: Bug
    Affects Versions: 2.0
            Reporter: Ron Piterman
            Priority: Minor


When using the jar plugin, outputDirectory is being cerated prior to creating the jar.

The ejb plugin however fails if specifying an outputDirectory which does not exist -

So, specifying something like ${project.build.directory}/jar will always fail after a clean.


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

       

    [ http://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140922#action_140922 ]

Dennis Lundberg commented on MEJB-28:
-------------------------------------

Can you give us a complete pom.xml that we can use to test this?

> outputDirectory is not created before packaging
> -----------------------------------------------
>
>                 Key: MEJB-28
>                 URL: http://jira.codehaus.org/browse/MEJB-28
>             Project: Maven 2.x Ejb Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Ron Piterman
>            Priority: Minor
>
> When using the jar plugin, outputDirectory is being cerated prior to creating the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not exist -
> So, specifying something like ${project.build.directory}/jar will always fail after a clean.

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

       

    [ http://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165468#action_165468 ]

Dennis Lundberg commented on MEJB-28:
-------------------------------------

I had a look at this and I get the following error message:
{noformat}
Error assembling EJB: META-INF/ejb-jar.xml is required for ejbVersion 2.x
{noformat}

Here's the configuration snippet I used:
{code:xml}
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ejb-plugin</artifactId>
        <version>2.1</version>
        <configuration>
          <outputDirectory>${project.build.directory}/jar</outputDirectory>
        </configuration>
      </plugin>
    </plugins>
  </build>
{code}

The reason for the error is that the EJB Plugin searches for resources (in this case the exb-jar.xml) in <outputDirectory>. But the file is not there. It is in the outputDirectory specified for the Resources Plugin. This needs to be rewritten in order to fix this issue.

> outputDirectory is not created before packaging
> -----------------------------------------------
>
>                 Key: MEJB-28
>                 URL: http://jira.codehaus.org/browse/MEJB-28
>             Project: Maven 2.x Ejb Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Ron Piterman
>            Priority: Minor
>
> When using the jar plugin, outputDirectory is being cerated prior to creating the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not exist -
> So, specifying something like ${project.build.directory}/jar will always fail after a clean.

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

       

    [ http://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197542#action_197542 ]

Adam Barry commented on MEJB-28:
--------------------------------

The reason I am voting for this issue is to be able to use the outputDirectory of an ejb module much like an exploded war where JBoss for instance requires the exploded directory to have an appropriate extension ie:
ejbmodule/target/ejbmodule-exploded.jar/

> outputDirectory is not created before packaging
> -----------------------------------------------
>
>                 Key: MEJB-28
>                 URL: http://jira.codehaus.org/browse/MEJB-28
>             Project: Maven 2.x EJB Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Ron Piterman
>            Priority: Minor
>
> When using the jar plugin, outputDirectory is being cerated prior to creating the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not exist -
> So, specifying something like ${project.build.directory}/jar will always fail after a clean.

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

       

    [ http://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197545#action_197545 ]

Adam Barry commented on MEJB-28:
--------------------------------

As a workaround I used the following antrun plugin task:
{code:xml}
<plugin>
  <artifactId>maven-antrun-plugin</artifactId>
  <executions>
    <execution>
      <phase>process-classes</phase>
      <configuration>
        <tasks>
          <copydir src="${project.build.outputDirectory}"
                   dest="${project.build.directory}/${project.build.finalName}-exploded.jar"/>
        </tasks>
      </configuration>
      <goals>
        <goal>run</goal>
      </goals>
    </execution>
  </executions>
</plugin>
{code:xml}

> outputDirectory is not created before packaging
> -----------------------------------------------
>
>                 Key: MEJB-28
>                 URL: http://jira.codehaus.org/browse/MEJB-28
>             Project: Maven 2.x EJB Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Ron Piterman
>            Priority: Minor
>
> When using the jar plugin, outputDirectory is being cerated prior to creating the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not exist -
> So, specifying something like ${project.build.directory}/jar will always fail after a clean.

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

       

    [ http://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197545#action_197545 ]

Adam Barry edited comment on MEJB-28 at 11/7/09 2:44 AM:
---------------------------------------------------------

As a workaround I used the following antrun plugin task:
{code:xml}
<plugin>
  <artifactId>maven-antrun-plugin</artifactId>
  <executions>
    <execution>
      <phase>process-classes</phase>
      <configuration>
        <tasks>
          <copydir src="${project.build.outputDirectory}"
                   dest="${project.build.directory}/${project.build.finalName}-exploded.jar"/>
        </tasks>
      </configuration>
      <goals>
        <goal>run</goal>
      </goals>
    </execution>
  </executions>
</plugin>
{code}


      was (Author: ajbarry):
    As a workaround I used the following antrun plugin task:
{code:xml}
<plugin>
  <artifactId>maven-antrun-plugin</artifactId>
  <executions>
    <execution>
      <phase>process-classes</phase>
      <configuration>
        <tasks>
          <copydir src="${project.build.outputDirectory}"
                   dest="${project.build.directory}/${project.build.finalName}-exploded.jar"/>
        </tasks>
      </configuration>
      <goals>
        <goal>run</goal>
      </goals>
    </execution>
  </executions>
</plugin>
{code:xml}

 

> outputDirectory is not created before packaging
> -----------------------------------------------
>
>                 Key: MEJB-28
>                 URL: http://jira.codehaus.org/browse/MEJB-28
>             Project: Maven 2.x EJB Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Ron Piterman
>            Priority: Minor
>
> When using the jar plugin, outputDirectory is being cerated prior to creating the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not exist -
> So, specifying something like ${project.build.directory}/jar will always fail after a clean.

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