Google is your friend. See
http://en.m.wikipedia.org/wiki/Java_backporting_tools
Matt
On Aug 24, 2013 12:34 AM, "Matt Benson" wrote:
> Thinking more on this, you'd at least have to remove generics signature
> information from the bytecode. Those are the main differences between these
> levels of
Thinking more on this, you'd at least have to remove generics signature
information from the bytecode. Those are the main differences between these
levels of bytecode I can think of, although there certainly could be more
to it. I feel like there once was a utility out there to do this job
though.
Interesting. There is a project in the Apache Commons sandbox, the [weaver]
component, which provides a general infrastructure for performing bytecode
transformations. An Ant task is provided. It might be fairly trivial to
rewrite 1.5 bytecode to v1.3; I'm not sure.
Matt
On Aug 23, 2013 10:11 PM,
Hi,
Is there any ant task, which allows manupulation of annotations with
in java source code..
The need I have is, I want to either strip all the annotations
within the java source code as java 1.3 (used for javame) does not
support annotations or use Simpl
Mssr Kerry
regarding use of .properties or .xml configuration
place ant configuration files such as .properties or .xml files into 1st item
in classpath e.g.
assume resolver.jar is located in $ANT_HOME/lib
set $CLASSPATH=$ANT_HOME%/lib;$TOMCAT_HOME%/lib
export $CLASSPATH
if you place a
PATH is for shell scripts to locate binaries (C++ programs)
CLASSPATH is for java classes (.jar)
My location is ant-apache-resolver.jar $APACHE_HOME/lib/ant-apache-resolver.jar
CLASSPATH=$APACHE_HOME/lib/ant-apache-resolver.jar;%CLASSPATH%
lets get this working before moving onto step 2
Marti
Thanks.
Regarding the first issue - Saxon's built-in catalog handling - I already know
how to do this. When I call Saxon from a Java task I pass all of -x, -y, -r,
-u.
Regarding the second - Saxon from within Ant's xslt task - I have been advised
that it isn't really possible with Saxo
I've changed my build file to pass the xslt task the location of the xsl style
file.
I can now see it reading that in the build log.
However, it isn't using my resolver to look up imports.
Please can someone answer the following questions.
1. I have xml-commons-resolver-1.2, including r
I'm walking in late here, so I may be missing the point.
Have you seen
http://stackoverflow.com/questions/14165765/how-to-use-saxon-built-in-catalog-feature
and http://www.saxonica.com/documentation/using-xsl/xsltfromant.html
The first is about Saxon and catalogs, the second is about the problem
On 2013-08-23, Kerry, Richard wrote:
> Can I add this as a feature request ?
Sure:
https://issues.apache.org/bugzilla/enter_bug.cgi?product=Ant&bug_severity=enhancement
> Saxon is able to do this, but it is run as a Java application so is
> able to do anything a Java app can do, in whatever way
Good Morning Mr Kerry
add this as a feature request
https://issues.apache.org/bugzilla/createaccount.cgi
Martin Gainty
__
Please do not alter or disrupt this communication...Thank You
> From: richard.ke...@atos.net
> To: user@ant.apache.org
>
"you wont need to write anything...Im just showing you the parameters you would
need to create a working test harness"
Ok, missed that.
"if you could approach the situation as if someone gave you a C++ program to
write
step1...is to start simple.."
Except that for C++, step 0 would be the
"The point is that Saxon loads a Java classpath defined
CatalogManager.properties file, so it's possible that it has read this before
ANT gets started."
Actually I think the point is that Saxon, run from a Java task, can load its
own files so it can do what it likes.
"So, you might be bett
"you want the catalog to resolve the stylesheet itself - I'm afraid this is not
supported."
"it does not use the catalog when locating the documents to transform or the
stylesheet itself."
Thank you, that's what I wanted to know. I couldn't see it stated
categorically in the docs.
I shal
14 matches
Mail list logo
