I had been using a tempdir variable to deploy the ejb, which has to end up
copied into a modules directory.  This worked once, but on the next ejb
project it failed on an error like the one given.  I assumed this was an
issue of variable redeclaration, but I don't know how to get around it.


JerodLass wrote:
> 
> I am defining tasks for certain specific subprojects through my top-level
> gradlefiles.  I am trying to make a generic, useful top-level gradlefile
> so nobody else gets to use groovy, and one thing it does is detect if the
> project it an EJB project.  If so, it declares the necessary source and
> resource variables as well as an ejbdeploy task.  I have shortened it as
> follows:
> 
> subprojects.each{project->
>   if(project.isEJB){
>     project.srcRootName = ejbModule
>     project.createTask('ejbdeploy', dependsOn: 'libs'){    
>       ant {
>         taskdef(name: "wsejbdeploy", classname:
> "com.ibm.websphere.ant.tasks.WsEjbDeploy", classpath:
> project.dependencies.antpath("wsanttasks"))
>         wsejbdeploy(inputJar:
> project.buildDir.path+'/'+project.archivesBaseName+'-'+project.version+'.jar',
>         classpath: path{
>             fileset(dir: rootDir.path+"/$modulesDirPath"){include:
> name="**/*.jar"}
>             fileset(dir: globalWasDir+'/lib'){include: name="**/*.jar"}
>             fileset(dir: globalWasDir+'/java'){include: name="**/*.jar"}
>             fileset(dir: earLib.path){include: name="**/*.jar"}
>             },
>           wasHome: globalWasDir,
>           outputJar:
> ${project.projectDir.path}/$ejbTemp/${project.name}-${project.version}.jar",
>           quiet:'false',
>           trace:'true',
>           failonerror:'true')
>         }
> 
>   }
> }
> 
> It's a bit sloppy, but when I run it on windows it's fine.  On unix, I end
> up with:
> 
> [wsejbdeploy] com.ibm.etools.ejbdeploy.IllegalFilenameException: Can not
> create file
> /builds/build/**/*.jar/EJBproject/ejbTemp/codesbenchEJB-g.1.0.jar.
> 
> I'm wondering if this is a context problem, but obviously that's not a
> valid location.  It should be coming from the outputjar attribute, but I
> don't know where it gets that front nonsense.
> 
> Any thoughts?
> 
> -Jerod
> 

-- 
View this message in context: 
http://www.nabble.com/task-execution-context-tp18496103p18496166.html
Sent from the gradle-user mailing list archive at Nabble.com.


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

    http://xircles.codehaus.org/manage_email


Reply via email to