[boffies]

Hi,

We have a team of six developers working on the same project using xdoclet for ejb creation. We are finding that because we have different filesystem configurations, ie: one developer does not have a D drive and the developers have installed their java libraries using different paths, that when one developer sets up the xdoclet properties, another developer cannot run xdoclet without opening the properties and closing them so that the ant script gets regenerated. Also what often happens is that the new interfaces and deployment descriptors cannot be written because the files were marked read-only previously by CVS.

Is there any workaround for these issues?

Regards,
Andreas

[Scott Anderson]

Andreas,

We’re aware of this issue and have an open enhancement request to take care of it. Right now, it looks like it will be within the scope of the 3.9 release schedule. The current workaround is as you found, that is to open the XDoclet config and hit OK to regenerate the script. Sorry for the inconvenience in the interim before a fix is available.

Also what often happens is that the new interfaces and deployment descriptors cannot be written because the files were marked read-only previously by CVS.

That’s very odd. I don’t think CVS uses pessimistic locking by marking files read-only. Are you sure you’re not using some other version control software, like Clearcase or VSS, instead of CVS? To ease this issue, the 3.8 GA build decouples XDoclet generation from the build loop so you’ll have to explicitly request it to run and regenerate. Given this new level of control you should be able to then checkout the files that will be affected before you kick off the run to work around the read-only issue of your team source control tool.

[fust]

Hi,

I’m using MyEclipse 4.0.1 and it seems that the problem still exists.
Is there a way now for solving the problem?

Regards,
Patrick Fust

[Greg]

Patrick,

My advice is to not check in the xdoclet-build.xml file at all, but rather just check in the .xdoclet file. In MyEclipse 4.x if you select dynamic build setting for xdoclet, it doesn’t even keep the xdoclet-build.xml file around. Each time you run XDoclet it generates a new temporary build file from your .xdoclet file and then deletes it after its finished. This way the correct paths are generated on each development machine separatly from the .xdoclet file that everyone uses since it doesn’t contain any absolute references.

[fust]

Greg,

The problem is that we’re using Cruise Control to make continuos builds, so there’s no user to start Eclipse and press the button.

Is it possible to trigger MyEclipse’s XDoclet generation from Ant?
(or other ways?)

Right now I have made a “hack” where I copy the xdoclet-build.xml and substitutes through Ant all the paths, so the build-server have the rigth paths.

– Patrick

[Greg]

Patrick,

You should be able to copy the xdoclet-build.xml file and change all the absolute paths and then you should be able to call that ant file from another ant file. I’m dont’ quite remember how this works but i=I’m sure it is possible.

[Author]

Posts