Yes,
when we'll upgrade the bsh.jar we will need to upgrade the JPublish
version as well... but this is not an easy task and I don't know if
there will be enough interest for this since JPublish is almost no more
used for developing OFBiz ui.
This raises some general issues that we should discuss:
a) how to track the version of the jar files distributed with OFBiz? (I
think it is a good idea to append the revision number to the name of the
jar file)
b) how to manage jar interdependencies? For example, the new JPublish
distribution depends on several jar files (included in the JPublish
distribution), and some of them (such as the bsh.jar file) are already
included in OFBiz but could be of a different release (older or
newer)... how should be handle situation like this one?
c) this last point is a philosophical issue: it is nice to keep the
older tools in the framework (such as the integration with JPublish),
even if in the OFBiz distribution they are no more used (but this is
still not the case of JPublish, used by the Shark and Content
components), however what should we do when the older tools make more
difficult the upgrade to newer tools (new jars etc...)? I think that
this could slow down the growth of OFBiz because it is difficult to find
people willing to help to keep updated with the rest of the system
things that are not really used. (should we think of a framework-lite
distribution of the OFBiz framework that contains just the things that
the svn version of OFBiz uses?)
Jacopo
Jacques Le Roux (JIRA) wrote:
[ http://issues.apache.org/jira/browse/OFBIZ-401?page=comments#action_12445373 ]
Jacques Le Roux commented on OFBIZ-401:
---------------------------------------
Reviewing more seriously this issue I realised that the problem Jacopo
encoutered is related to JPublish.
I checked source
(http://jpublish.cvs.sourceforge.net/jpublish/jpublish/src/org/jpublish/action/ScriptAction.java?view=log)
: Jpublish does not use IBM no more for 2 years and a half now. So it seems
that updating JPublish to last stable should do the trick...
In Revision 1.34 you may see David's work :o)
upgrade bsf to something a bit more modern
------------------------------------------
Key: OFBIZ-401
URL: http://issues.apache.org/jira/browse/OFBIZ-401
Project: OFBiz (The Open for Business Project)
Issue Type: Bug
Components: framework
Affects Versions: SVN trunk
Reporter: Adam Heath
Assigned To: Jacques Le Roux
Priority: Trivial
Fix For: SVN trunk
Attachments: bsf.diff
OfBiz still uses a bsf version from when it was hosted/maintained by ibm. The
attached patch fixes this(does a search/replace), changing the package names.
