- This topic has 8 replies, 3 voices, and was last updated 19 years, 4 months ago by
.
-
Posts
-
I’m using ME and I like it quite a bit. I have a local instance of a jboss server for testing and I check my code into subversion. Then I want to use anthill to pull from the repository, build and place that code on a QA-environment jboss server. When I do that I have dependencies on some local files,
C:\eclipse\plugins\com.genuitec.jboss.ide.eclipse.xdoclet.core_3.8.1
that aren’t in my build and deploy environment. How do I get around this? The xdoclet-build.xml file that ME generates from includes all of these paths. Thanks for any help.
Please navigate to your Project Properties > MyEclipse-XDoclet, then change to the Build tab and change the build policy to “dynamic” and check the “remove existing” if its enabled. This will change the MyEclispe XDoclet generation to an internally controlled/dynamically generated part of ME, instead of making it a hard-coded file in your project. Many people prefer this approach.
Perhaps I’m not seeing things correctly but when I go to the Project Porpoerties>MyEclipse-XDoclet screen there are no Tabs. There is just a single pop-up with three panes. I have a Standard EJB XDoclet checked in the top one and that gives me a ejbdoclet structure in the bottom left. There is no way to go to a Build tab. I think I’m on 3.8.2 of ME if I’m reading the screen right.
I think I’m on 3.8.2 of ME if I’m reading the screen right.
Ahh, please upgrade to 3.8.3, its a new feature that might help you out (with almost 200 more enhancements/bug fixes over 3.8.2)
Well I did and this works mostly but now I don’t understand what to use as the build file within anthill. There is no xdoclet-build.xml file created now. What is the generated file that I point at now?
I didn’t realize you wanted the XML file… I thought the dependency was stopping you from building… now I know you need/want it. If that’s the case turn the Build behavior back to the old style, let it create the file, and the dependency you need are just the XDoclet libs… you can grab them from xdoclet.sf.net most likely.
Once you take the xdoclet-build.xml file, you will have to modify the paths to work in your environment and you can place the modified copy in a place where anthill can use it.
Okay thanks for the help. I believe that what I am doing here is a common thing. Developing on one machine and deploying on another (or a couple) and you guys might want to look at handling this a little more elegantly. Having to change the build files and maintain two copies after I create them locally and check them in to source code is kind of clunky. I’d love to hear if other have the same issue though. Maybe I’m doing something wrong?
We looked at making the xdoclet build file more dynamic but in order to access the xdoclet libs from a MyEclipse installation you still have to use at least one hardcoded path. The only way to create an xdoclet build file that would work in both environments is to use relative paths for the xdoclet libs. That means that all of the xdoclet libraries would have to be included in your EJB project in MyEclipse as well as included in your QA build environment path. The latter isn’t too bad and I’m assuming you are doing that anyway if you are running xdoclet outside of MyEclipse. The former would be the problem because your EJB project would have a couple of megs of xdoclet libraries laying around and cluttering up the project.
Thank you for your input and I will add your comments to our internal PR tracking this issue.
