Multiple output paths.
Hi all,
I'm evaluating Ariadna - build 629, and I find it a very impressive tool!
....but I have the following problem:
I have a J2EE project which contains an EJB sub-project and a Web
sub-project. I want to compile my EJB files directly in the directory where
the EJB classes are deployed:
%application_home%\ejb-module\
and my Web files directly in the directory where the Web classes are
deployed:
%application_home%\web-module\web-inf\classes\
To achieve this, I created 2 source paths and I chose Output type = Multiple
output paths in Project Properties. One source path contains my EJB files
and has Output path = %application_home%\ejb-module\, the other contains my
Web files and has Output path =
%application_home%\web-module\web-inf\classes\.
My problem is, Ariadna compiles the source files not in the directories I
mentioned above, but in
%ariadna_installation_home%\system\output\498d6120 ! Then I have to manually
copy the files in my two output directories.
I mention that I have enabled Web application support and EJB integration in
Project Properties.
What could cause my problem and how can I avoid it?
Thanks,
Radu Zaharia
请先登录再写评论。
Hello,
Steps to Resolve
Check Project Properties:
Go to Project Properties and double-check the configuration for both the EJB and Web source paths.
Confirm that the Output type is set to Multiple output paths.
Ensure that the paths you entered for the Output path are correctly specified, without typos or missing placeholders.
Verify Variable Substitution:
Ensure that %application_home% is correctly defined within Ariadna or the system environment. If this variable isn't resolved, Ariadna might default to its internal directory.
Replace %application_home% with an absolute path temporarily to see if the issue persists.
Inspect Build Settings:
Look into the Build and Deployment settings in Ariadna. There might be an override or default directory setting for output paths.
Ensure that these settings align with the paths you’ve specified.
Check Compilation Behavior:
Some IDEs or build tools generate intermediate files in an internal directory before moving them to the final output directory. Check if there's an option like "Copy to Output Directory" or a similar setting that you need to enable.
Modify Deployment Settings:
If Ariadna uses deployment descriptors or build scripts (e.g., Ant or Maven), ensure they are configured to output files directly into the specified directories.
For example, in Ant, ensure the <javac> task specifies the desired output directory.
Enable Debug Logging:
Enable verbose or debug logging in Ariadna (if available) to trace the exact steps during compilation and see why it outputs to %ariadna_installation_home%\system\output\498d6120.
Manual Adjustment:
If none of the above works, consider using a post-build script to automate the copying of files from %ariadna_installation_home%\system\output\498d6120 to your desired directories.
Possible Causes
Incorrect Path Substitution: %application_home% might not be resolved correctly by Ariadna.
Default Output Behavior: Ariadna could be defaulting to an internal directory regardless of your settings, which might be a bug or an intentional design.
Build Settings Conflict: There might be a conflict between the Web application support and EJB integration settings, causing Ariadna to disregard your paths.
Best Regards