facebook

Proper Level of XDoclet Automation

  1. MyEclipse IDE
  2.  > 
  3. Feature Requests
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #209779 Reply

    Release notes for 3.8b2 say you want comments, so here they are.

    I’d like to see an option in the MyEclipse preferences that, if set, would do an XDoclet build of a project whenever it’s deployed, either directly or as part of an EAR build. I always want to be able to build the dependent files manually, but it’d be nice if I could be sure that the dependent files were always updated whenever I deploy. I want to be able to turn off the function, though, just in case I have a big project that takes awhile to build the files or for whatever other reason that I haven’t thought of yet.

    #210090 Reply

    Greg
    Member

    We agree that making sure all deployment descriptors and supplemental files are synced before deploying is a crucial requirement. We have opend a PR to capture all user input so we can make the best plan for xdoclet automation in 3.8 GA. Thanks for your input on the subject.

    Any other users that want to comment on xdoclet automation feel free to continue to use this topic since it is appropriately named.

    #210396 Reply

    siderean
    Member

    I really wish that the MyEclipse-XDoclent dialog would pick up manual changes to the xdoclet-build.xml file so that those manual changes were not lost when using the dialog to edit things. It’s powerful to have both a text and graphical interface to changing the xdoclet-build.xml file, but only if they are able to work together.

    #210398 Reply

    Greg
    Member

    siderean,

    Do you mean manual changes in the xdoclet-build file that are attribute/value pairs in the subdoc tasks? Or do you mean adding your own things in the xdoclet-build file like extra <property file/> tags or other ant build stuff?

    The current MyEclipse-Xdoclet configuration page picks up settings from the .xdoclet file in your project. So changes to the xdoclet-build file for attribute/value pairs like destDir=”…” for any subdoclet task will get overwritten. However, if there are other changes you want to be always in xdoclet-build files, like extra ant tags, this is doable but it takes manual reconfiguration of some XSD files.

    #210412 Reply

    siderean
    Member

    I am speaking about attributes like pattern that I always configure for all four types of interfaces for each project. It’s easier to copy/paste four lines of XML than the find and change the pattern attribute for each type of interface. If I make that change in the xml file, though, it dissapears the next time I view the XDoclet dialog 🙁 In my case, it makes we’ve had to ‘ban’ the dialog in favour of text only changes.

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Proper Level of XDoclet Automation

You must be logged in to post in the forum log in