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

Bjorn Smette closed MWAS-24.
----------------------------

       Resolution: Not A Bug
    Fix Version/s: 1.0

> Fails to get buildnumber variable
> ---------------------------------
>
>                 Key: MWAS-24
>                 URL: http://jira.codehaus.org/browse/MWAS-24
>             Project: Maven 2.x WebSphere 6 Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-2
>         Environment: Maven version: 2.0.9
> Java version: 1.6.0_07
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: Bjorn Smette
>            Assignee: David J. M. Karlsen
>            Priority: Minor
>             Fix For: 1.0
>
>
> It seems like the was6-maven-plugin and the buildnumber-maven-plugin doesn't 
> operate well together. 
> The ejb module of my project builds in this order, xdoclet-maven-plugin -> 
> maven-ejb-plugin -> was6-maven-plugin. The two first is ok, and then the 
> ejbdeploy of the was6-maven-plugin starts.
> The errormessage is: "Embedded error: Source 
> 'C:\workspace\myp-2.1.0\myp-ejb\target\was6-maven-plugin\a9944721\myp-ejb-2.1.0-r${buildNumber}\ejbModule'
>  does not exist"
> It seems like the variable ${buildNumber} is not resolved even though the 
> C:\workspace\myp-2.1.0\myp-ejb\target\was6-maven-plugin\a9944721\myp-ejb-2.1.0-r64215\ejbModule\
>  folder is created and contains the build (classes and META-INF)
> The buildnumber is run during the validate phase and should be available(?)
> From the parent pom:
>     <build>
>         <plugins>
>             <plugin>
>                 <groupId>org.codehaus.mojo</groupId>
>                 <artifactId>buildnumber-maven-plugin</artifactId>
>                 <executions>
>                     <execution>
>                         <phase>validate</phase>
>                         <goals>
>                             <goal>create</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>                 <configuration>
>                     <doCheck>false</doCheck>
>                     <doUpdate>true</doUpdate>
>                 </configuration>
>             </plugin>
>         </plugins>
>         
> <finalName>${project.artifactId}-${project.version}-r${buildNumber}</finalName>
>     </build>
> From the ejb module pom:
>             <plugin>
>                 <groupId>org.codehaus.mojo</groupId>
>                 <artifactId>was6-maven-plugin</artifactId>
>                 <executions>
>                     <execution>
>                         <phase>generate-sources</phase>
>                         <goals>
>                             <goal>clean</goal>
>                             <goal>ejbdeploy</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>                 <configuration>
>                     <wasHome>${was6home}</wasHome>
>                     
> <wsAntClasspath>${was6home}/plugins/com.ibm.ws.runtime_6.1.0.jar</wsAntClasspath>
>                     <legacyMode>true</legacyMode>                  
>                 </configuration>
>             </plugin>

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