commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BCEL-49) Build problems against jdk1.5
Date Thu, 24 Apr 2014 09:55:15 GMT

     [ https://issues.apache.org/jira/browse/BCEL-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Bourg updated BCEL-49:
-------------------------------

      Description: 
There are two apparent problems. The first is that BCEL's "Deprecated" class has a name clash
with the new "Deprecated" interface in java.lang, which first appeared in jdk1.5. Two obvious
solutions to this are to (1) rename BCEL's class to something like "DeprecatedAttr" (which
would break source that used this class) or (2) change all internal references to "Deprecated"
to the fully qualified class name "org.apache.bcel.classfile.Deprecated".

The second is much more minor. In "build.xml" the "jar" target depends on the "examples" target.
Shouldn't it depend on "compile" (or perhaps "test"). In the "jar" target build instructions,
there is also a mandatory dependency on the file "manifest.txt" it seems like this should
be optional. If not present, let "jar" itself generate a Manifest.

  was:
There are two apparent problems. The first is that BCEL's "Deprecated" class
has a name clash with the new "Deprecated" interface in java.lang, which first
appeared in jdk1.5. Two obvious solutions to this are to (1) rename BCEL's
class to something like "DeprecatedAttr" (which would break source that used
this class) or (2) change all internal references to "Deprecated" to the
fully qualified class name "org.apache.bcel.classfile.Deprecated".

The second is much more minor. In "build.xml" the "jar" target depends on
the "examples" target. Shouldn't it depend on "compile" (or perhaps "test").
In the "jar" target build instructions, there is also a mandatory dependency
on the file "manifest.txt" it seems like this should be optional. If not
present, let "jar" itself generate a Manifest.

         Priority: Major
      Environment:     (was: Operating System: other
Platform: PC)
    Fix Version/s: 5.2
         Priority:   (was: P3)
         Severity:   (was: normal)

> Build problems against jdk1.5
> -----------------------------
>
>                 Key: BCEL-49
>                 URL: https://issues.apache.org/jira/browse/BCEL-49
>             Project: Commons BCEL
>          Issue Type: Bug
>          Components: Main
>    Affects Versions: 5.1
>            Reporter: mreynold
>            Assignee: Apache Commons Developers
>             Fix For: 5.2
>
>
> There are two apparent problems. The first is that BCEL's "Deprecated" class has a name
clash with the new "Deprecated" interface in java.lang, which first appeared in jdk1.5. Two
obvious solutions to this are to (1) rename BCEL's class to something like "DeprecatedAttr"
(which would break source that used this class) or (2) change all internal references to "Deprecated"
to the fully qualified class name "org.apache.bcel.classfile.Deprecated".
> The second is much more minor. In "build.xml" the "jar" target depends on the "examples"
target. Shouldn't it depend on "compile" (or perhaps "test"). In the "jar" target build instructions,
there is also a mandatory dependency on the file "manifest.txt" it seems like this should
be optional. If not present, let "jar" itself generate a Manifest.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message