[ http://jira.codehaus.org/browse/MAVENUPLOAD-855?page=comments#action_63946 ]
John Casey commented on MAVENUPLOAD-855: ---------------------------------------- Alright, after updates (both to the bundles and the script used to deploy them), I have uploaded stringtemplate and jdtcore. HOWEVER, I'm not sure about the antlr bundle. Mark is using the artifactId 'antlr3' internally, to differentiate between antlr 2.x and antlr 3.x in the same project. String template requires 2.x, which means they both have to be present. Also, Terrence has changed the package name for antlr 3.x, so they are viable siblings in the same classloader. In light of the changes to the package name, would it be appropriate to change the artifactId to something more in line with Mark's (i.e. 'antlr3'). This would allow the two to exist side-by-side... I'm not deploying the antlr bundle until we reach some conclusion on this. > stringtemplate-2.3b6-bundle.jar antlr3-3.0ea8-bundle.jar > jdtcore-3.2.0.v_658-bundle.jar > ----------------------------------------------------------------------------------------- > > Key: MAVENUPLOAD-855 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-855 > Project: maven-upload-requests > Type: Task > Reporter: Mark Proctor > > > I was told its better to have a single jira for all the bundles, which are > listed below: > http://www.codehaus.org/~mproctor/stringtemplate-2.3b6-bundle.jar > http://www.codehaus.org/~mproctor/antlr3-3.0ea8-bundle.jar > http://www.codehaus.org/~mproctor/jdtcore-3.2.0.v_658-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
