- By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common.
- Make the ejb creation work even if there are not sources. git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@233477 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
1 parent
f09520091f
commit
4f6bd83501
4 files changed
+27
-7
No files matched your search
+16
-4
@@ -38,9 +38,22 @@
|
||||
<!--==================================================================-->
|
||||
<goal name="ejb:init">
|
||||
|
||||
<j:if test="${sourcesPresent == 'true'}">
|
||||
<attainGoal name="test:test"/>
|
||||
</j:if>
|
||||
<!-- This is required in the case of building an ejb jar where all
|
||||
the sources are taken from a dependent jar. When this is the case
|
||||
the source files have not been compiled and the classes dir thus
|
||||
not created automatically -->
|
||||
<ant:mkdir dir="${maven.build.dest}"/>
|
||||
|
||||
<j:choose>
|
||||
<j:when test="${sourcesPresent == 'true'}">
|
||||
<attainGoal name="test:test"/>
|
||||
</j:when>
|
||||
<j:otherwise>
|
||||
<!-- Make sure we always copy the resources whether there are sources or
|
||||
not -->
|
||||
<attainGoal name="java:jar-resources"/>
|
||||
</j:otherwise>
|
||||
</j:choose>
|
||||
|
||||
</goal>
|
||||
|
||||
@@ -103,7 +116,6 @@
|
||||
<!-- END OF TO BE REMOVED -->
|
||||
</j:forEach>
|
||||
|
||||
|
||||
<j:if test="${maven.ejb.manifest.available}">
|
||||
<ant:setProperty name="manifest" value="${maven.ejb.manifest}" />
|
||||
</j:if>
|
||||
|
||||
@@ -53,4 +53,4 @@ maven.ejb.includes = **
|
||||
maven.ejb.excludes = **/package.html
|
||||
|
||||
# Decide whether a client jar is generated or not.
|
||||
maven.ejb.client.generate = true
|
||||
maven.ejb.client.generate = false
|
||||
@@ -25,6 +25,14 @@
|
||||
</properties>
|
||||
<body>
|
||||
<release version="1.7-SNAPSHOT" date="in SVN trunk">
|
||||
<action dev="vmassol" type="update">
|
||||
By default do not generate client EJB. I believe this is a more common
|
||||
default that generating as generation of client EJBs is only required
|
||||
for distributed apps which are not so common.
|
||||
</action>
|
||||
<action dev="vmassol" type="fix">
|
||||
Make the ejb creation work even if there are not sources.
|
||||
</action>
|
||||
<action dev="vmassol" type="fix" issue="MPEJB-12">
|
||||
Fixed default property values in the web site documentation.
|
||||
</action>
|
||||
@@ -36,7 +44,7 @@
|
||||
property <code>maven.ejb.client.generate</code> which decides whether or
|
||||
not to generate the ejb client jar. It defaults to true.
|
||||
</action>
|
||||
<action dev="vmassol" type="fix" issue="MPEJB-16" due-to="Håvard Bjåstad">
|
||||
<action dev="vmassol" type="fix" issue="MPEJB-16" due-to="H�vard Bj�stad">
|
||||
Added new EJB type handler that supports <code>ejb</code> and
|
||||
<code>ejb-client</code> types. This fixes the bug with
|
||||
<code>ejb:install/deploy-client</code> not uploading the client
|
||||
|
||||
@@ -148,7 +148,7 @@
|
||||
Decide wether to generate an ejb client jar or not.
|
||||
</td>
|
||||
<td>
|
||||
true
|
||||
false
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
Reference in new issue
Block a user