You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Serge Knystautas <se...@lokitech.com> on 2002/04/17 22:03:55 UTC
JDK 1.4 compilation working
In looking at how DBCP has JDBC3 support (ergo JDK 1.4) support, I took
the same approach, reworked it a bit for the James build and class in
question, and presto, James is compiling in 1.4.
One question if anybody knows why it was done this way... the current
build.xml creates a build\classes and build\src directory. However, it
only copies the Constants file into build\src and during a compile
references the java source from the CVS directory. I had to change this
to copy all java code to build\src since I need to possibly replace a
token, based on whether we need JDBC3 support. Aside from having to
delete and recreate the Constants file each time, does anybody see a
downside with doing it this way?
I'm going to commit it this way since it seems to be working. We'll
have to figure out how to make a release though... I'm hoping that if we
compile in JDK 1.4, we can still run it in JDK 1.3. All the JDBC3
methods just throw exceptions, so there's no real support for them anyway.
--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JDK 1.4 compilation working
Posted by Serge Knystautas <se...@lokitech.com>.
There's an IDE that does that? Cool!
--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
Danny Angus wrote:
> the downside of build\src is that IDE's capturing ant->javac messages can't
> take you to the line of code where an error is marked, 'cos they take you to
> build\src
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JDK 1.4 compilation working
Posted by Serge Knystautas <se...@lokitech.com>.
Ok, I've redone the build file back so it leaves the code in java.dir,
but treats the PoolConnEntry file like the Constants file, copying it to
build.src and replacing tokens as appropriate. Seems to be more or less
working.
--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
Danny Angus wrote:
> the downside of build\src is that IDE's capturing ant->javac messages can't
> take you to the line of code where an error is marked, 'cos they take you to
> build\src
>
>
>>-----Original Message-----
>>From: Serge Knystautas [mailto:sergek@lokitech.com]
>>Sent: 17 April 2002 21:04
>>To: james-dev@jakarta.apache.org
>>Subject: JDK 1.4 compilation working
>>
>>
>>In looking at how DBCP has JDBC3 support (ergo JDK 1.4) support, I took
>>the same approach, reworked it a bit for the James build and class in
>>question, and presto, James is compiling in 1.4.
>>
>>One question if anybody knows why it was done this way... the current
>>build.xml creates a build\classes and build\src directory. However, it
>>only copies the Constants file into build\src and during a compile
>>references the java source from the CVS directory. I had to change this
>>to copy all java code to build\src since I need to possibly replace a
>>token, based on whether we need JDBC3 support. Aside from having to
>>delete and recreate the Constants file each time, does anybody see a
>>downside with doing it this way?
>>
>>I'm going to commit it this way since it seems to be working. We'll
>>have to figure out how to make a release though... I'm hoping that if we
>>compile in JDK 1.4, we can still run it in JDK 1.3. All the JDBC3
>>methods just throw exceptions, so there's no real support for them anyway.
>>--
>>Serge Knystautas
>>Loki Technologies - Unstoppable Websites
>>http://www.lokitech.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: JDK 1.4 compilation working
Posted by Danny Angus <da...@thought.co.uk>.
the downside of build\src is that IDE's capturing ant->javac messages can't
take you to the line of code where an error is marked, 'cos they take you to
build\src
> -----Original Message-----
> From: Serge Knystautas [mailto:sergek@lokitech.com]
> Sent: 17 April 2002 21:04
> To: james-dev@jakarta.apache.org
> Subject: JDK 1.4 compilation working
>
>
> In looking at how DBCP has JDBC3 support (ergo JDK 1.4) support, I took
> the same approach, reworked it a bit for the James build and class in
> question, and presto, James is compiling in 1.4.
>
> One question if anybody knows why it was done this way... the current
> build.xml creates a build\classes and build\src directory. However, it
> only copies the Constants file into build\src and during a compile
> references the java source from the CVS directory. I had to change this
> to copy all java code to build\src since I need to possibly replace a
> token, based on whether we need JDBC3 support. Aside from having to
> delete and recreate the Constants file each time, does anybody see a
> downside with doing it this way?
>
> I'm going to commit it this way since it seems to be working. We'll
> have to figure out how to make a release though... I'm hoping that if we
> compile in JDK 1.4, we can still run it in JDK 1.3. All the JDBC3
> methods just throw exceptions, so there's no real support for them anyway.
> --
> Serge Knystautas
> Loki Technologies - Unstoppable Websites
> http://www.lokitech.com/
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>