In the past, we've seen it happen that some patch releases would work
but others wouldn't. For example, 1.8.2 would work, but 1.8.3 might not.
drew
On 03/21/2014 09:03 AM, Andrew Petro wrote:
Emmett,
Thanks for working on this. Shaking that Ant 1.8.2 dependency and
moving on to a later Ant would be great.
On what the antversion task supports
--------------------------------
Yes, the `<antversion/>` task supports an `atleast` attribute in place
of `exactly`.
https://ant.apache.org/manual/Tasks/antversion.html
On where to find Ant documentation
-------------------------------
https://ant.apache.org/
On defining successful ant build
---------------------------
If `ant clean initportal` successfully goes from zero to deployed to
Tomcat, with the database appropriately loaded, that sounds like success.
Kind regards,
Andrew
On 3/21/14, 10:50 AM, Emmett Culley wrote:
I am successfully building uPortal using ant 1.9.2. To do that I
needed to modify the bootstrap/build_includes.xml file to allow
building with that version. I have three questions
1)
Is it possible to have the antversion tag specify a "greater than or
equal" attribute, instead of "exactly"?
<antversion exactly="1.9.2"/>
to something like:
<antversion atleast="1.9.2"/>
2)
I suppose there is some documentation on build_includes.xml tags and
their attributes. None of the XSD files in the project refer to
antversion. Where can I find either generic ant build XML file
documentation or uPortal specific ant build XML file documentation, or
both?
3)
How can I verify that using ant 1.9.2 actually builds correctly? Is it
enough that the build is successful and uPortal loads and functions.
Emmett
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
