This content has been marked as final. Show 6 replies
I am experiencing the same issue with the ojdeploy ant task in 11g. ojdeploy builds all JDeveloper deployment profiles from the command line. The ant task on the other hand doesn't seem to find the application-level profiles.
I have worked around this issue by following your wonderful "Oracle ADF Development Essentials: Building Projects Using ANT" article. This solution works but is not ideal for enterprise organizations that are embracing the Fusion Middleware Platform stack. It won't take long before the build will be out of line with deployment profiles created and deployed with JDeveloper. Headless execution of ojdeploy against JDeveloper jws and jpr project files ensures alignment between builds. It would be different if all configuration files were present at the start of compilation. JDeveloper renders some configuration/deployment items on the fly during the build process. I feel like long term having a "from scratch build" for each project is asking for trouble and doesn't leverage JDeveloper and all the wonderful work the JDeveloper team is doing taking the busy work out of building enterprise applications.
The ojdeploy ant task can not find application-level deployment profiles. This is an issue for automating releases. How do you build ear files at oracle? Do you use the same Ant Task?
Thanks for thinking about this,
any chance you can file a bug on this matter and provide a testcase for support to verify ?
I think the following bug tracks the same issue.
In the latest builds the error message has changed slightly from the one mentioned in the bug.
yes, this appears to be the same issue. Seems that this has been a regression in JDeveloper 11g R1 that has been reported as a defect for the upcoming PatchSet. So chances are good that this gets solved in the next upcoming Pacth Set
Test with JDev 184.108.40.206.0 still results in
build.xml:311: Missing <workspace>, <project> or <profile> parameter in <deploy> element
Using ojdeploy directly from command line and same parameters as in the Ant script everything works fine.
This is a bug that will be resolved in the next patch set.