Hi,
Welcome Java 1.5 and Maven 2.0.9 in trunk, please! :-)
I think that I've checked everything when it comes to our infrastructure for compliance with Java
1.5 and Maven 2.0.9.
To sum things up:
1. I've switched us to Java 1.5, Maven 2.0.9 profile in Continuum (seems to
work correctly)
2
Hi,
I just wanted to inform you that Continuum will be failing because I'm trying different settings on
Continuum to enforce building with Java 1.5.
Stay patient, please.
--
Grzegorz Kossakowski
Grzegorz Kossakowski pisze:
Hi,
I just wanted to inform you that Continuum will be failing because I'm
trying different settings on Continuum to enforce building with Java 1.5.
Build statistics:
State: Ok
[...]
Java Home version : java version 1.5.0_12
Java(TM) 2 Runtime
Grzegorz Kossakowski pisze:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1] there
are more and more problems with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility
Grzegorz Kossakowski wrote:
Grzegorz Kossakowski pisze:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4
Grzegorz Kossakowski pisze:
During the voting period there were 14 +1 votes and no negative ones.
This means that the proposal was accepted.
I'll take care of updating pom, Java at our zone and Continuum
configuration but this will take some time, though.
I forgot about tag in subject, so
On Tue, 2008-08-05 at 15:40 +0200, Grzegorz Kossakowski wrote:
But of course I meant:
The vote will stay open until 12:00 UTC, 08.08.2008.
Too late, but still +1.
Cheers, Alfred.
On Aug 5, 2008, at 9:07 AM, Grzegorz Kossakowski wrote:
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4
Grzegorz Kossakowski wrote:
Please cast your votes:
+1
-David
-Original Message-
From: Grzegorz Kossakowski [mailto:[EMAIL PROTECTED]
Sent: dinsdag 5 augustus 2008 15:08
To: Cocoon's dev mailing list
Subject: [vote] Java 1.5 as minimal requirement for trunk
Hello,
As discussed in thread Cocoon-jms-sample requires Java =
1.5[1
Grzegorz Kossakowski grek at tuffmail.com writes:
switching to Java 1.5 as minimal required version
+1
Joerg
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1] there are more and more problems
with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need for dropping Java 1.4 compatibility
and in that case, switching to Java 1.5
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1] there
are more and more problems with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in that case, switching to Java
1.5 as minimal required version seems to be the best solution.
+1
Felix
Grzegorz Kossakowski skrev:
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in that case, switching to Java
1.5 as minimal required version seems to be the best solution.
+1
/Daniel
Grzegorz Kossakowski wrote
Please cast your votes:
+1
Jeroen
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1] there
are more and more problems with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility
Reinhard Pötz pisze:
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4
+1
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility
Hi,
2008/8/5 Grzegorz Kossakowski [EMAIL PROTECTED]:
After a while it turned out that everybody agrees on the need for dropping
Java 1.4 compatibility and in that case, switching to Java 1.5 as minimal
required version seems to be the best solution.
+1
Andrew.
--
[EMAIL PROTECTED] / [EMAIL
Grzegorz Kossakowski escribió:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility
On Tue, Aug 5, 2008 at 8:07 AM, Grzegorz Kossakowski [EMAIL PROTECTED] wrote:
Hello,
As discussed in thread Cocoon-jms-sample requires Java = 1.5[1] there are
more and more problems with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need
, switching to new Java version is not that hard, things that you
need to do are:
1. Change required Java version in our parent pom.
2. Change profile in Continuum so it uses Java 1.5
3. Upgrade Java used on cocoon.zones.apache.org.
4· Announce this fact to our users.
In the past, it proven to be more
Now we have the problem that the ActiveMQ version that we use was built
with Java 5:
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
Hi,
2008/7/30 Reinhard Pötz [EMAIL PROTECTED]:
Now we have the problem that the ActiveMQ version that we use was built with
Java 5:
[ERROR] BUILD FAILURE
According to
http://activemq.apache.org/can-i-use-activemq-5x-or-later-on-java-14.html
there is no version built for 1.4.
What shall
Hey,
this came out of my head. Currently, I'm using three different Java versions on
my PC.
I'm sorry for that. As Reinhard already stated,
there won't be a solution in the near future, except using the Retrotranslator.
I could suggest to introduce a profile, activated when using Java 5 or
Reinhard Pötz schrieb:
According to
http://activemq.apache.org/can-i-use-activemq-5x-or-later-on-java-14.html
there is no version built for 1.4.
What shall we do?
Can't we use the enforcer plugin that the jms block is only build and
added when using 1.5 or higher and make a note in the
Felix Knecht wrote:
Reinhard Pötz schrieb:
According to
http://activemq.apache.org/can-i-use-activemq-5x-or-later-on-java-14.html
there is no version built for 1.4.
What shall we do?
Can't we use the enforcer plugin that the jms block is only build and
added when using 1.5 or higher and
Reinhard Pötz pisze:
Now we have the problem that the ActiveMQ version that we use was built
with Java 5:
snip/
According to
http://activemq.apache.org/can-i-use-activemq-5x-or-later-on-java-14.html
there is no version built for 1.4.
What shall we do?
Actually, this is a part of bigger
Then I think the solution is rather clear: we need to migrate to 1.5.
If Sun is not supporting Java 1.4 then I don't want to support it as
well in our _trunk_.
People that need to stick to Java 1.4 still have a choice: We have
released 2.2 that works with Java 1.4.
Therefore I propose to
On Wed, Jul 30, 2008 at 8:47 AM, Felix Knecht [EMAIL PROTECTED] wrote:
Then I think the solution is rather clear: we need to migrate to 1.5. If
Sun is not supporting Java 1.4 then I don't want to support it as well in
our _trunk_.
People that need to stick to Java 1.4 still have a choice:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alfred Nathaniel wrote:
| On Mon, 2008-05-05 at 00:08 -0700, Ralph Goers wrote:
| I sure am glad we decided to go with Java 1.4 for 2.2. See the nice
| bulletin at http://java.sun.com/j2se/1.4.2/download.html. At least now
| I'm certain we won't be
On Mon, 2008-05-05 at 00:08 -0700, Ralph Goers wrote:
I sure am glad we decided to go with Java 1.4 for 2.2. See the nice
bulletin at http://java.sun.com/j2se/1.4.2/download.html. At least now
I'm certain we won't be supporting 1.4 until 2010.
No hope to get rid of 1.4 anytime soon. Java
I sure am glad we decided to go with Java 1.4 for 2.2. See the nice
bulletin at http://java.sun.com/j2se/1.4.2/download.html. At least now
I'm certain we won't be supporting 1.4 until 2010.
Ralph Goers wrote:
Carsten Ziegeler said:
Although I guess everyone understood what I meant above,
then
the
voting rules state that a single -1 vetoes the proposal, and we got
that
before. Unless the -1 is rescinded I fear we will be stuck at 1.4
until
2010.
We can bump version number to 2.3 and require Java 1.5 for it. In fact
I'd proposed this already sometime before. 2.2 can be branched off
Nathaniel in:
http://svn.apache.org/viewvc?view=revrevision=555089
XSP compile failure when using Java 1.5 features
Key: COCOON-1251
URL: https://issues.apache.org/jira/browse/COCOON-1251
Project: Cocoon
Reinhard Poetz wrote:
I think for 2.2 it is fine to stick with Java 1.4 and go for Java 5 with
2.3. This should also give the Websphere 6 users enough time and is for
all the Java 5 fans motivation to make 2.3 happen soon ;-)
Exactly.
Vadim
Hi,
On 28 Sep 2007, at 05:38, Joerg Heinicke wrote:
And what's the use of it? I just don't get it why a framework
should set restrictions on its user base.
Well, by that argument we should make cocoon work with Ruby, C++,
Lisp, Erlang, etc etc ... don't want to restrict our users to just
and
over again.
So if you really think it's worth it go ahead. Otherwise I'm with
Vadim's plan:
I'm completely expecting Cocoon 2.3 to be at Java 1.5 level, and 2.4 may be at
Java 1.6 level.
Joerg
On 28.09.2007 0:46 Uhr, Ralph Goers wrote:
I'm sure we could find a way to take advantage of NIO if we
really thought about it. But we can't do any of that
because we are stuck at 1.4.
NIO is 1.4.
Joerg
Joerg Heinicke wrote:
On 25.09.2007 16:20 Uhr, Felix Knecht wrote:
May I ask why can't just make a jump and goto java 1.6?
What's the benefit of using not the latest version - do any contracts
exists that we can't jump over a java version?
And what's the use of it? I just don't get it why a
On 25.09.2007 16:20 Uhr, Felix Knecht wrote:
May I ask why can't just make a jump and goto java 1.6?
What's the benefit of using not the latest version - do any contracts
exists that we can't jump over a java version?
And what's the use of it? I just don't get it why a framework should set
On 28.09.2007 0:46 Uhr, Ralph Goers wrote:
However, the language features of 1.5 are worth it.
For example, I would love to replace some pieces of
code that require synchronized blocks with java.util.concurent. I would
love to be able to specify the object types on Maps and Lists. It just
Joerg Heinicke wrote:
On 25.09.2007 15:45 Uhr, Vadim Gritsenko wrote:
Our problem is not minimum Java requirement for Cocoon 2.2. The
problem is release time lines. [..] Java requirements? Nah, that's
peanuts...
Thanks, you hit the nail. When was the vote? 1 year ago?
Despite being still
Vadim Gritsenko wrote:
Our problem is not minimum Java requirement for Cocoon 2.2. The problem
is release time lines. Cocoon 2.2 was supposed to be Cocoon 2.1 +
ECM+. Now we don't have ECM+, it went through Spring migration, there
seems to be second wave of OSGi activity - and 2.2 ain't
. Killing 2.1.x should enable us to maintain 2.2.x and focus on trunk
introducing Java 1.5
as minimal requirement and some other incompatibilities.
What happened to item 2?
Good question. I was having bad night.
If I recall what it was I'll post it :)
3. Let's release 2.2 final just few weeks
Grzegorz Kossakowski skrev:
Ralph Goers pisze:
...
Version 2.3 should only be created if we have some new feature for it ..
like OSGi (and it might even be possible to do that on 2.2 since it is
leveraging Spring - but you'd have to ask the guys working on it). I am
not in favor of creating a
Daniel Fagerstrom wrote:
The current plan is that Spring-OSGi will be released in december, so we
should most definitively not let Cocoon 2.2 wait for it. Right now,
I'm the only one working on Cocoon-OSGi so it must be more of a
community effort before we include it in any release.
OSGi
[EMAIL PROTECTED] wrote:
Author: reinhard
Date: Tue Sep 25 01:55:55 2007
New Revision: 579132
URL: http://svn.apache.org/viewvc?rev=579132view=rev
Log:
disable this testcase since it doesn't run through with Java 1.4. The
problem is that the included
Spring configuration files can't be
.
+1 to switch to java 1.5. :)
Best Regards,
Antonio Gallardo.
2.2 is a critical mass.
+1 to switch to java 1.5. :)
+1 as well.
J2SE 1.4.2 began its end of life process Dec 11 2006 and is expected to
complete it for the summer of 2008 http://java.sun.com/j2se/1.4.2/.
/Daniel
Carsten Ziegeler said:
Although I guess everyone understood what I meant above, just a
clarification: of course I meant that it only makes sense to stick with
1.4 if the people working on and using 2.2 *with jdk 1.4* is a critical
mass. There is no doubt that currently there are many people
I agree. I am optimistic adn believe people opinions changes with time.
I would like to start a new vote since we have now a new jave version
scenario in front of us. :)
wdyt?
Best Regards,
Antonio Gallardo.
Ralph Goers escribió:
Carsten Ziegeler said:
Although I guess everyone
Date: Tue, 25 Sep 2007 17:08:52 +0200
From: [EMAIL PROTECTED]
J2SE 1.4.2 began its end of life process Dec 11 2006 and is expected to
complete it for the summer of 2008 http://java.sun.com/j2se/1.4.2/.
Sun's isn't the only JVM, you know...
According to
expecting Cocoon 2.3 to be at Java 1.5 level, and 2.4 may be at Java
1.6 level.
Our problem is not minimum Java requirement for Cocoon 2.2. The problem is
release time lines. Cocoon 2.2 was supposed to be Cocoon 2.1 + ECM+. Now we
don't have ECM+, it went through Spring migration, there seems
an idea. I'm completely expecting Cocoon 2.3 to be at Java 1.5 level,
and 2.4 may be at Java 1.6 level.
Our problem is not minimum Java requirement for Cocoon 2.2. The problem
is release time lines. Cocoon 2.2 was supposed to be Cocoon 2.1 +
ECM+. Now we don't have ECM+, it went through Spring
, we could
set Java 1.5 for trunk.
May I ask why can't just make a jump and goto java 1.6?
What's the benefit of using not the latest version - do any contracts
exists that we can't jump over a java version?
Felix
2010.
Here, fixed it for you :)
You are saying it like a bad thing. Cocoon 2.1 will be stuck at Java 1.3
until cows come home. And Cocoon 1.8.2 will be stuck at... Well, you get
an idea. I'm completely expecting Cocoon 2.3 to be at Java 1.5 level,
and 2.4 may be at Java 1.6 level.
Our
. At the
same time, we could
set Java 1.5 for trunk.
May I ask why can't just make a jump and goto java 1.6?
What's the benefit of using not the latest version - do any contracts
exists that we can't jump over a java version?
Some (most?) platforms are lagging 1.6 support.
For example, Java 1.6
)
2.1.9
Javaflow runtime error when cocoon is built and ran using java 1.5
--
Key: COCOON-1865
URL: https://issues.apache.org/jira/browse/COCOON-1865
Project: Cocoon
On 10/9/06, Antonio Gallardo [EMAIL PROTECTED] wrote:
...Because we claim 2.1 is java 1.3 when it
fact few of us care about this compatibility and some blocks does not
compile at all
I think we voted on this a while ago: the 2.1 core and most blocks
must work with 1.3, but some blocks
Hi Simone,
I agree with you, basically, it is a chicken egg problem, if we don't
set java 1.5 as the minimal jvm, we will never start using typed
collections, for-each etc. The fact is that most of us is using this new
cool features and will be fine to use them in our cocoon code too.
Best
Bertrand Delacretaz wrote:
On 10/9/06, Antonio Gallardo [EMAIL PROTECTED] wrote:
...Because we claim 2.1 is java 1.3 when it
fact few of us care about this compatibility and some blocks does not
compile at all
I think we voted on this a while ago: the 2.1 core and most blocks
must work
Reinhard Poetz wrote:
For 2.2, it would be cool to have this info in the blocks themselves -
do the Maven POMs allow for some JDK requirements metadata?
not that i know of. There is the prerequisites element but that's only
used for the maven version. Nothing prevents us though from just
On 09.10.2006 06:01, Antonio Gallardo wrote:
Should we call for a new votation about the
minimal java version for cocoon 2.2?
No, please don't.
Jörg
] version 1.6 was
released in August 2006 (we are using now qdox 1.5) and it is
distributed only for java 1.5! I know qdox is not the most used block,
but it rings a bell!
Cocoon 2.2 is not released and we will start to find such cases more
often than what we would like to believe. I mean we
On 10/9/06, Antonio Gallardo [EMAIL PROTECTED] wrote:
...I was updating some jars for cocoon 2.1.0. Qdox[1] version 1.6 was
released in August 2006 (we are using now qdox 1.5) and it is
distributed only for java 1.5! I know qdox is not the most used block,
but it rings a bell!...
Does
Bertrand Delacretaz wrote:
I think the only way to handle this is to decide on a JVM version for
the core, and accept that some non-core blocks might have different
requirements.
+1
Vadim
Antonio Gallardo wrote:
Ralph Goers escribió:
1. I don't see the point. There was a -1 that is unlikely to be changed.
I am providing more reasons as brain food. I think people can change
his mind over the time when more facts arises.
2. Since we will be distributing binaries with Maven -
Bertrand Delacretaz escribió:
I think the only way to handle this is to decide on a JVM version for
the core, and accept that some non-core blocks might have different
requirements.
+1.
Just some question: it is the same for 2.1, right? What is 2 different
blocks with different jvm
On 10/9/06, Antonio Gallardo [EMAIL PROTECTED] wrote:
...Just some question: it is the same for 2.1, right? What is 2 different
blocks with different jvm requirement needs the same jar?...
I was mainly thinking about 2.2, but in your case, if a jar is
compiled for 1.4 it will work with 1.5,
to see if Retrotranslator works
correctly, and if it works agree on a plan on moving blocks to 1.5
progressively, moving core as the last part, taking enough time to be
realistic on our efforts and grant a smooth change.
Maybe this could be a way to gain consensus?
Simone
P.S. Java 1.5 also
Bertrand Delacretaz escribió:
On 10/9/06, Antonio Gallardo [EMAIL PROTECTED] wrote:
...Just some question: it is the same for 2.1, right? What is 2
different
blocks with different jvm requirement needs the same jar?...
I was mainly thinking about 2.2, but in your case, if a jar is
compiled
On 09.10.2006 23:03, Antonio Gallardo wrote:
I am thinking in 2.2 too. The above reference to 2.1 is just a sample of
what we are repeating for 2.2. Because we claim 2.1 is java 1.3 when it
fact few of us care about this compatibility and some blocks does not
compile at all. This somehow
Hi:
I was updating some jars for cocoon 2.1.0. Qdox[1] version 1.6 was
released in August 2006 (we are using now qdox 1.5) and it is
distributed only for java 1.5! I know qdox is not the most used block,
but it rings a bell!
Cocoon 2.2 is not released and we will start to find such cases
Javaflow runtime error when cocoon is built and ran using java 1.5
--
Key: COCOON-1865
URL: http://issues.apache.org/jira/browse/COCOON-1865
Project: Cocoon
Type: Bug
Components: Blocks: Java Flow
and ran using java 1.5
--
Key: COCOON-1865
URL: http://issues.apache.org/jira/browse/COCOON-1865
Project: Cocoon
Type: Bug
Components: Blocks: Java Flow
Versions: 2.1.10-dev (current SVN
.
for (Map entry: entries)
{
Cocoon is running under Tomcat 5.0.28 on j2sdk-1.5.0-beta2-b51.
XSP compile failure when using Java 1.5 features
Key: COCOON-1251
URL: http://issues.apache.org/jira/browse/COCOON
For those of you who might not have noticed it (and who are using Mac
OS/X), the ADC http://developer.apple.com/ just posted to everyone
the J2SE 5.0 Release 3 Developer Preview 2...
I don't think you need any special privilege to download it, just an
ADC account.
It's a 110 Mb download!
Le 12 oct. 05, à 16:15, Pier Fumagalli a écrit :
For those of you who might not have noticed it (and who are using Mac
OS/X), the ADC http://developer.apple.com/ just posted to everyone
the J2SE 5.0 Release 3 Developer Preview 2...
Thanks for the info - I hope the install does not wipe out
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 16:15, Pier Fumagalli a écrit :
For those of you who might not have noticed it (and who are using Mac
OS/X), the ADC http://developer.apple.com/ just posted to everyone
the J2SE 5.0 Release 3 Developer Preview 2...
Thanks for the info - I hope
On 12 Oct 2005, at 15:30, Bertrand Delacretaz wrote:
Le 12 oct. 05, à 16:15, Pier Fumagalli a écrit :
For those of you who might not have noticed it (and who are using
Mac OS/X), the ADC http://developer.apple.com/ just posted to
everyone the J2SE 5.0 Release 3 Developer Preview 2...
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33189.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33394.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33394.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33189.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=33394
Summary: Does not compile under Java 1.5 - TransformerException
if writing cocoon.roles
Product: Cocoon 2
Version: 2.1.6
Platform: PC
OS/Version: Windows XP
Status: NEW
Keywords: JDK1.5
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33394.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=33189
Summary: Does not compile under Java 1.5 because enum is a
keyword
Product: Cocoon 2
Version: 2.1.6
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: JDK1.5
Severity: normal
/show_bug.cgi?id=33189
--- Additional Comments From [EMAIL PROTECTED] 2005-01-21 06:39 ---
Created an attachment (id=14062)
-- (http://issues.apache.org/bugzilla/attachment.cgi?id=14062action=view)
Single diff that fixes Cocoon 2.1.6 so that it compiles with Java 1.5
Run the following:
cd
/show_bug.cgi?id=30971
XSP compile failure when using Java 1.5 features
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED
/show_bug.cgi?id=30971
XSP compile failure when using Java 1.5 features
--- Additional Comments From [EMAIL PROTECTED] 2004-10-24 22:20 ---
The eclipse compiler is currently working on java 1.5 features:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36938
I will try to run cocoon with javac
JD Daniels wrote:
I am about to start building a new server for my new cocoon projects.
I have a few questions:
1.) I have started using SVN in my own projects and I really like it.
but I am a little confused about about what version of cocoon supports
java 1.5, and if that suport
what version of cocoon
supports java 1.5, and if that suport is available. Where is the main
development going on? I see as my choices:
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X
https://svn.apache.org/repos/asf/cocoon/tags/RELEASE_2_1_RC_1
https://svn.apache.org/repos/asf
On 16.10.2004 07:31, JD Daniels wrote:
1.) I have started using SVN in my own projects and I really like it.
but I am a little confused about about what version of cocoon supports
java 1.5, and if that suport is available. Where is the main development
going on? I see as my choices:
https
I am about to start building a new server for my new cocoon projects. I
have a few questions:
1.) I have started using SVN in my own projects and I really like it.
but I am a little confused about about what version of cocoon supports
java 1.5, and if that suport is available. Where
/show_bug.cgi?id=30971
XSP compile failure when using Java 1.5 features
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
Hi:
Now, the current 2.1.x branch compiles and run using java 1.5.
I also checked the back compatibility:
Compile and run with java 1.4 OK
Compile and run with java 1.3 OK (as before).
In the case of the java 1.3 we cannot compile the Deli and scratchpad
block. Both issues are quite old
Hi:
I am trying to compile Cocoon with jdk1.5.0. I already committed some
changes until I meet this one:
/cocoon-2.1/src/blocks/forms/java/org/apache/cocoon/forms/event/ProcessingPhase.java:22:
as of release 1.5, 'enum' is a keyword, and may not be used as an
identifier
(try -source 1.4 or lower
Antonio Gallardo wrote:
Hi:
I am trying to compile Cocoon with jdk1.5.0. I already committed some
changes until I meet this one:
/cocoon-2.1/src/blocks/forms/java/org/apache/cocoon/forms/event/ProcessingPhase.java:22:
as of release 1.5, 'enum' is a keyword, and may not be used as an
identifier
1 - 100 of 105 matches
Mail list logo
