Opened 13 years ago

Closed 13 years ago

#972 closed enhancement (wontfix)

clean up ant build.xml scripting fun

Reported by: jkuhnert@… Owned by: jkuhnert
Priority: high Milestone: 0.9
Component: General Version: 0.3
Keywords: Cc:
Blocked By: Blocking:

Description

In light of the recent calamities involving CLASSPATHS / generated bytcode classformat errros / small quircks in whatever is supposedly wrong with the compression ant task it may be desirable to move some of these scripted steps into one easy-to-contain mess that no one can see.

The basic overall solution would be taking out all python/javascript build steps (in their current form) and placing them into a more tightly controlled "dojo" ant task. The rest documentation is theoretically deprecated already anyways(or not? ), so the only areas that would need to be figured out are all of the javascript portions.

I've already created an ant task that invokes and bundles the rhino api into one single jar that replaces all of the testing items you currently see in build.xml for dojo with one single line xml statement.

There are drawbacks/benefits...going with benefits first:

-) No more having to install optional jar files - easier build. -) Less clutter in the core build.xml means it will be easier for all to understand / maintain. -) Using rhino directly such as I've already done with my own dojo task will eliminate the need for a custom_rhino jar completely as this logic will be self contained and make it easier for dojo to be more globally rhino friendly. -) Potentially creates more easy to use "tools" based around dojo, furthering plans for world domination.. =p -) Will be very easy to go ahead and make it possible to build custom packages / test runs for people using dojo within the confines of their ~own~ project. This is already being done with the ant test part, won't be very hard to do for packaging either.

Drawbacks:

-) It's all java. Wtf wants to maintain that? -) The current items are in javascript / python, which a lot of dojo devs are already very familiar with(snicker..) ...Moving to java might be bad for moral AND maintainability in general.

If this is something that will actually get used I'll write the code, maybe there are better solutions as well..

Change History (4)

comment:1 Changed 13 years ago by dylan

Owner: changed from anonymous to jkuhnert

comment:2 Changed 13 years ago by jkuhnert

Owner: changed from jkuhnert to alex

Another yay/nay re-assignment question.

It looks like you would be my module "buddy" according to this http://dojo.jot.com/WikiHome/ModuleExperts.

The code is clean and unobtrusive. Solves classpath issues with installation of js.jar / etc..Would probably stick it under tools/ like all of the other new things coming in.

comment:3 Changed 13 years ago by jkuhnert

Milestone: 0.40.5
Owner: changed from alex to jkuhnert
Status: newassigned

comment:4 Changed 13 years ago by jkuhnert

Resolution: wontfix
Status: assignedclosed

For now it looks like some portions of the build system won't be going away.

Note: See TracTickets for help on using tickets.