You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by mick <mg...@redhat.com> on 2011/08/17 18:07:13 UTC
[JAVA] build breakage with older ant/java
I'm not a Java developer, although I do know how to break the build.
Problem is -- when trying to fix my problem, I ran into a pre-existing
problem:
(with a new code tree as of this morning)
[mick@mrg35 java]$ ant clean build
Buildfile: build.xml
[mkdir] Created dir: /home/mick/trunk/qpid/java/tasks/classes
[javac] Compiling 5 source files
to /home/mick/trunk/qpid/java/tasks/classes
[javac]
Note: /home/mick/trunk/qpid/java/tasks/src/org/apache/qpid/tasks/BaseTask.java uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
BUILD FAILED
/home/mick/trunk/qpid/java/build.xml:25: The following error occurred
while executing this line:
/home/mick/trunk/qpid/java/common.xml:122: The <dirset> type doesn't
support the "erroronmissingdir" attribute.
- - - - - - - - -
I am using java java-1.6.0-openjdk-1.6.0.0-1.22.1.9.8.el5_6
and ant ant-1.6.5-2jpp.2
( and I do not have the choice of updating thses.)
Does anyone know an easy way to work around this problem for these older
versions?
Re: [JAVA] build breakage with older ant/java
Posted by Gordon Sim <gs...@redhat.com>.
On 08/22/2011 11:16 AM, Keith Wall wrote:
> On 18 August 2011 16:14, Gordon Sim<gs...@redhat.com> wrote:
>
>> On 08/18/2011 04:09 PM, Robbie Gemmell wrote:
>>
>>> The rationale for the change was to add an extension point to the
>>> build system to enable client modules, such as transports and
>>> authentication/authorisation add-ons. The easiest way of doing this
>>> was the property used which has happened to involve requiring a 3 year
>>> old version of Ant.
>>>
>>> Should it be a policy to support things that are over 6 years old at
>>> this point? RHEL4? I've been seeing RHEL5 based builds getting broken
>>> with increasing regularity recently...
>>>
>>
>> I'm not suggesting it should be policy. All I was asking was for
>> clarification and context on the change in question to help inform any
>> possible proposals on alternatives.
>>
>> While we shouldn't have to contort ourselves to workaround the lack of well
>> established features, if there are simple alternatives that are less
>> exclusive that is surely a reasonable thing to consider.
>
>
> I commited a change under QPID-3365 to avoid the dependency on Ant 1.7.1.
> The build should now be working under Ant 1.6.x once again.
Thanks!
(I'll stress again that I am not by any means suggesting there should be
a policy to support older versions. However I very much appreciate the
gesture here).
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [JAVA] build breakage with older ant/java
Posted by Keith Wall <ke...@gmail.com>.
On 18 August 2011 16:14, Gordon Sim <gs...@redhat.com> wrote:
> On 08/18/2011 04:09 PM, Robbie Gemmell wrote:
>
>> The rationale for the change was to add an extension point to the
>> build system to enable client modules, such as transports and
>> authentication/authorisation add-ons. The easiest way of doing this
>> was the property used which has happened to involve requiring a 3 year
>> old version of Ant.
>>
>> Should it be a policy to support things that are over 6 years old at
>> this point? RHEL4? I've been seeing RHEL5 based builds getting broken
>> with increasing regularity recently...
>>
>
> I'm not suggesting it should be policy. All I was asking was for
> clarification and context on the change in question to help inform any
> possible proposals on alternatives.
>
> While we shouldn't have to contort ourselves to workaround the lack of well
> established features, if there are simple alternatives that are less
> exclusive that is surely a reasonable thing to consider.
I commited a change under QPID-3365 to avoid the dependency on Ant 1.7.1.
The build should now be working under Ant 1.6.x once again.
>
>
> ------------------------------**------------------------------**---------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.**apache.org<de...@qpid.apache.org>
>
>
Re: [JAVA] build breakage with older ant/java
Posted by Gordon Sim <gs...@redhat.com>.
On 08/18/2011 04:09 PM, Robbie Gemmell wrote:
> The rationale for the change was to add an extension point to the
> build system to enable client modules, such as transports and
> authentication/authorisation add-ons. The easiest way of doing this
> was the property used which has happened to involve requiring a 3 year
> old version of Ant.
>
> Should it be a policy to support things that are over 6 years old at
> this point? RHEL4? I've been seeing RHEL5 based builds getting broken
> with increasing regularity recently...
I'm not suggesting it should be policy. All I was asking was for
clarification and context on the change in question to help inform any
possible proposals on alternatives.
While we shouldn't have to contort ourselves to workaround the lack of
well established features, if there are simple alternatives that are
less exclusive that is surely a reasonable thing to consider.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [JAVA] build breakage with older ant/java
Posted by Robbie Gemmell <ro...@gmail.com>.
The rationale for the change was to add an extension point to the
build system to enable client modules, such as transports and
authentication/authorisation add-ons. The easiest way of doing this
was the property used which has happened to involve requiring a 3 year
old version of Ant.
Should it be a policy to support things that are over 6 years old at
this point? RHEL4? I've been seeing RHEL5 based builds getting broken
with increasing regularity recently...
Robbie
On 18 August 2011 14:07, Gordon Sim <gs...@redhat.com> wrote:
> On 08/17/2011 08:21 PM, Robbie Gemmell wrote:
>>
>> You say you cant update, but is that really the case? All that is
>> required to update Ant would be to unpack the ~6+ MB binary (e.g.
>> from http://www.apache.org/dist/ant/binaries/ ) and add the bin
>> directory to your path, job done.
>
> In more controlled build environments this is not always so simple.
>
>> The alternative would be to rework the additions to support 1.6.5,
>> but at over 6 years old I think its time we gave up on that and take
>> advantage of the bug fixes and newer features in later releases
>> (theres a few I've spotted in 1.8.X that I look forward to using at
>> some point down the line, once its suitably aged).
>
> Looking at the change in question,
> http://svn.apache.org/viewvc?view=revision&revision=1149163, would I be
> right in saying the use of the newer attribute is to make the existence of
> the client-plugins dir optional?
>
> A bit of context on the thinking there would be useful in considering what
> the options would be for those stuck on earlier versions.
>
> --Gordon
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [JAVA] build breakage with older ant/java
Posted by Gordon Sim <gs...@redhat.com>.
On 08/17/2011 08:21 PM, Robbie Gemmell wrote:
> You say you cant update, but is that really the case? All that is
> required to update Ant would be to unpack the ~6+ MB binary (e.g.
> from http://www.apache.org/dist/ant/binaries/ ) and add the bin
> directory to your path, job done.
In more controlled build environments this is not always so simple.
> The alternative would be to rework the additions to support 1.6.5,
> but at over 6 years old I think its time we gave up on that and take
> advantage of the bug fixes and newer features in later releases
> (theres a few I've spotted in 1.8.X that I look forward to using at
> some point down the line, once its suitably aged).
Looking at the change in question,
http://svn.apache.org/viewvc?view=revision&revision=1149163, would I be
right in saying the use of the newer attribute is to make the existence
of the client-plugins dir optional?
A bit of context on the thinking there would be useful in considering
what the options would be for those stuck on earlier versions.
--Gordon
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [JAVA] build breakage with older ant/java
Posted by Robbie Gemmell <ro...@gmail.com>.
I fixed the build breakage on Saturday when committing something else,
so you dont need to worry about that now.
The issue below is due to the somewhat ancient version of Ant you are
using; a commit some weeks ago has used an attribute not supported
until Ant 1.7.1, released in June 2008.
You say you cant update, but is that really the case? All that is
required to update Ant would be to unpack the ~6+ MB binary (e.g. from
http://www.apache.org/dist/ant/binaries/ ) and add the bin directory
to your path, job done. The alternative would be to rework the
additions to support 1.6.5, but at over 6 years old I think its time
we gave up on that and take advantage of the bug fixes and newer
features in later releases (theres a few I've spotted in 1.8.X that I
look forward to using at some point down the line, once its suitably
aged).
Robbie
On 17 August 2011 17:07, mick <mg...@redhat.com> wrote:
> I'm not a Java developer, although I do know how to break the build.
>
> Problem is -- when trying to fix my problem, I ran into a pre-existing
> problem:
> (with a new code tree as of this morning)
>
>
> [mick@mrg35 java]$ ant clean build
> Buildfile: build.xml
> [mkdir] Created dir: /home/mick/trunk/qpid/java/tasks/classes
> [javac] Compiling 5 source files
> to /home/mick/trunk/qpid/java/tasks/classes
> [javac]
> Note: /home/mick/trunk/qpid/java/tasks/src/org/apache/qpid/tasks/BaseTask.java uses unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
>
> BUILD FAILED
> /home/mick/trunk/qpid/java/build.xml:25: The following error occurred
> while executing this line:
> /home/mick/trunk/qpid/java/common.xml:122: The <dirset> type doesn't
> support the "erroronmissingdir" attribute.
>
> - - - - - - - - -
>
> I am using java java-1.6.0-openjdk-1.6.0.0-1.22.1.9.8.el5_6
> and ant ant-1.6.5-2jpp.2
> ( and I do not have the choice of updating thses.)
>
>
> Does anyone know an easy way to work around this problem for these older
> versions?
>
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org