Jim Idle schrieb: > Terence Parr wrote: >> So maven seems to work and has lots of capabilities. we've got it >> working but it sort of expects a code tree like this: >> >> >> >> >> So our src/org/antlr/... would become src/main/java/org/antlr/... >> >> the effect is for all your XTarget.java and template files to move >> down 2 levels or so on disk. can mess up your IDE and such. >> >> is it reasonable to go whole hog and drink the maven koolaid completely? > Just so that everyone realizes (I know that some of you already know > this), Maven can generate projects for use in Idea and Eclipse and > Netbeans does not even need that, it just recognizes Maven projects > directly. While most of us are not using Java, it is still really good > to be able to make a change in your template or XTarget.java and test it > in-situ with the jar format that will eventually be shipped. > > I see that a number of us have our template files checked out. If I move > the templates before you have had a chance to check in, don't worry, > perforce knows what to do about it and if anyone has any trouble > following what to do then feel free to just lob your changes over the > wall to me and I will take care of it. If you can't work out how to > follow the integration, all you need do is copy the file you changed to > a temporary folder, then revert the ones you have checked out; check out > the template in the new location and move your temporary copy on top of > it, then submit. Easy enough as we all only have one or two files > checked out. > > In fact the changes are subtle in that there is an extra directory or so > for Java files, but your templates (not your java target file) will > actually be under src/main/resources/org/antlr/... Otherwise everything > is the same. This is because Maven then knows how to parse resources if > needed without any configuration settings (for instance to update > licenses). Basically it simplifies things at the expense of conforming > to a pre-built idea of how a project should be organized. > > In the main though, apart from the location of your template, everything > is pretty much as is. If you can't be bothered to build the Tool jar > yourself, Hudson checks for changes and emails anyone concerned about > builds. Make sure that you have set the email address in your perforce > user so that you get notifications if you break/fix anything: > > p4 user (or use the Windows/X gui - p4v) > > If there is no email address, add: > > email: jimi@/dev/null > > Also, with the automated builds, if you include a JIRA bug name in your > change list description, then Hudson will automatically annotate the > JIRA entry with your change description. As in: > > p4 submit > > .... > Description: > ANTLR-666 Eradicate beast. > > The good thing about this is that you can type in a nice long perforce > changelist description (we all do that anyway right? ;-), and it will > update JIRA (and will be included in the release notes eventually), so > when you close a bug, you can just say "See perforce change description". > > Anyway, the organizational changes will be obvious as soon as you sync > and use ls -lR or a GUI directory browser: > > src/main/java - java code > src/main/antlr - antlr v3 gramamars > src/main/resources - String templates, code gen string templates, > anything else that isn't a Java source or ANTLR grammar. > src/test/java/.... - jUnit tests > src/test/resources/... - Stuff like string templates used for tests > > All pretty sensible, just a little bit different from what we had before. > > Jim
Nice in theory, but I've got no permission on my string templates and on my XTarget.java files anymore. :( Probably everyone else doesn't, too. Johannes _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
