Menu
▾
▴
xml11-devel — XML11 Developer List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(35) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Wolfgang K. <wol...@gm...> - 2006-08-02 06:24:46
|
Guys, as Arno already mentioned, we are close to releasing a new version of XML1= 1. Arno asked for tests, tests, tests =A7;-) If you find any bug during your tests, please use XML11's bug tracker host= ed at SourceForge to report these bugs (https://sourceforge.net/tracker/=3Fa= tid=3D785991&group=5Fid=3D152977&func=3Dbrowse). -- Frusty =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/=3Fmc=3D100071&distributionid=3D000000000071 |
|
From: Sascha H. <ma...@sa...> - 2006-08-01 22:38:32
|
Guys, I just updated the homepage-files and added the desired little arrow beneath the main menu. It indicates, which page the user is currently looking at ( in addition to the heading ). I also restored the lost information from the CVS for the overview and contact page. I made everything XHTML1.1 and CSS error-free but it might happen, that something doesn't look right in your browsers so please test it and report any errors you find. I know that opera displays the arrow 1 pixel to high, but it still looks okay. I will look after that. Also on IE here in wine the calculator looks not at the right position. I will take a look at this! Sascha |
|
From: Wolfgang K. <wol...@gm...> - 2006-08-01 19:51:52
|
Guys, as you maybe know, the XML11 build files support having user specific build.properties files. To use this feature just set an environment variable XML11_USER and create a build.properties.$XML11_USER in XML11's project root folder. I just committed a few changes to make life easier with these specific files. Before this change it was necessary to duplicate the whole build.properties and customize some of the settings to meet your specfic environment. After the changes I committed, it is only necessary to specify those properties, which are different from those specified in the common build.properties file. -- Frusty |
|
From: Wolfgang K. <wol...@gm...> - 2006-08-01 19:19:37
|
Besides our scripts, Ant is using JAVA_HOME as well to determine which JDK to use (I'm not quite sure about this, but that would be an explanation of the behaviour you've seen. The message regarding the unsupported Java version comes from our Ant script. That is the little Java version check I mentioned in my first mail. -- Frusty Christopher Kriese wrote: > Something is dependent on JAVA_HOME. > > I had my PATH set to include JDK 1.5.07, but (when I did *not* have JAVA_HOME > set) the build was using a 1.4 JDK on my Linux box. This caused serveral > compile errors. I believe that Wolfgang's changes are addressing this issue. > > cjk > > --- Sascha Haeberling <ma...@sa...> wrote: > > >> Hey, >> >> I just tested the Linux-Shellscript. In the past, when the JAVA_HOME >> variable wasn't set, it returned an error. When testing it now, it >> doesn't fail but instead shows: >> "Java version 1.4.2 not supported. Supported versions are 1.5" When I >> set JAVA_HOME, everything is fine. Do we really need JAVA_HOME? Because >> usually, all the java tools are known through PATH, I think? >> >> >> Sascha >> >> >> >> >> Wolfgang Korn wrote: >> >>> Guys, >>> >>> I just committed some changes. >>> >>> * The shell scripts should work now >>> * The Ant script performs a basic check on the Java version being >>> used. Currently all JDKs other than 1.5 should cause a failure >>> * Fixed the problem with the log4j warning. The reason for this >>> warnig was a missing log4j.xml in classes/core. Eclipse already >>> copied this file from core/src to classes/core but the Ant >>> script did not. >>> >>> @Arno: The problem concerning LayoutDemo you reported today is not >>> caused by the log4j problem mentioned above. The log4j problem only >>> caused missing log output. Besides that I can not reproduce that >>> problem with LayoutDemo on my box. >>> >>> -- Frusty >>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------- >>> Take Surveys. Earn Cash. Influence the Future of IT >>> Join SourceForge.net's Techsay panel and you'll get the chance to share >>> >> your >> >>> opinions on IT & business topics through brief surveys -- and earn cash >>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> XML11-devel mailing list >>> XML...@li... >>> https://lists.sourceforge.net/lists/listinfo/xml11-devel >>> >>> >>> ------------------------------------------------------------------------- >>> >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV> >> > _______________________________________________ > >> XML11-devel mailing list >> XML...@li... >> https://lists.sourceforge.net/lists/listinfo/xml11-devel >> >> > > > Christopher J. Kriese > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > XML11-devel mailing list > XML...@li... > https://lists.sourceforge.net/lists/listinfo/xml11-devel > > |
|
From: Wolfgang K. <wol...@gm...> - 2006-08-01 19:16:35
|
Yes - we really need JAVA_HOME since we have to rebuild the boot classpath. JAVA_HOME is neede to determine where to get rt.jar and all the other Java runtime jars. -- Frusty Sascha Haeberling wrote: > Hey, > > I just tested the Linux-Shellscript. In the past, when the JAVA_HOME > variable wasn't set, it returned an error. When testing it now, it > doesn't fail but instead shows: > "Java version 1.4.2 not supported. Supported versions are 1.5" When I > set JAVA_HOME, everything is fine. Do we really need JAVA_HOME? > Because usually, all the java tools are known through PATH, I think? > > > Sascha > > > > > Wolfgang Korn wrote: >> Guys, >> >> I just committed some changes. >> >> * The shell scripts should work now >> * The Ant script performs a basic check on the Java version being >> used. Currently all JDKs other than 1.5 should cause a failure >> * Fixed the problem with the log4j warning. The reason for this >> warnig was a missing log4j.xml in classes/core. Eclipse already >> copied this file from core/src to classes/core but the Ant >> script did not. >> >> @Arno: The problem concerning LayoutDemo you reported today is not >> caused by the log4j problem mentioned above. The log4j problem only >> caused missing log output. Besides that I can not reproduce that >> problem with LayoutDemo on my box. >> >> -- Frusty >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> XML11-devel mailing list >> XML...@li... >> https://lists.sourceforge.net/lists/listinfo/xml11-devel >> > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > > _______________________________________________ > XML11-devel mailing list > XML...@li... > https://lists.sourceforge.net/lists/listinfo/xml11-devel > |
|
From: Christopher K. <ch...@ya...> - 2006-08-01 19:04:06
|
Something is dependent on JAVA_HOME. I had my PATH set to include JDK 1.5.07, but (when I did *not* have JAVA_HOME set) the build was using a 1.4 JDK on my Linux box. This caused serveral compile errors. I believe that Wolfgang's changes are addressing this issue. cjk --- Sascha Haeberling <ma...@sa...> wrote: > Hey, > > I just tested the Linux-Shellscript. In the past, when the JAVA_HOME > variable wasn't set, it returned an error. When testing it now, it > doesn't fail but instead shows: > "Java version 1.4.2 not supported. Supported versions are 1.5" When I > set JAVA_HOME, everything is fine. Do we really need JAVA_HOME? Because > usually, all the java tools are known through PATH, I think? > > > Sascha > > > > > Wolfgang Korn wrote: > > Guys, > > > > I just committed some changes. > > > > * The shell scripts should work now > > * The Ant script performs a basic check on the Java version being > > used. Currently all JDKs other than 1.5 should cause a failure > > * Fixed the problem with the log4j warning. The reason for this > > warnig was a missing log4j.xml in classes/core. Eclipse already > > copied this file from core/src to classes/core but the Ant > > script did not. > > > > @Arno: The problem concerning LayoutDemo you reported today is not > > caused by the log4j problem mentioned above. The log4j problem only > > caused missing log output. Besides that I can not reproduce that > > problem with LayoutDemo on my box. > > > > -- Frusty > > > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys -- and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > XML11-devel mailing list > > XML...@li... > > https://lists.sourceforge.net/lists/listinfo/xml11-devel > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV> _______________________________________________ > XML11-devel mailing list > XML...@li... > https://lists.sourceforge.net/lists/listinfo/xml11-devel > Christopher J. Kriese |
|
From: Sascha H. <ma...@sa...> - 2006-08-01 18:45:15
|
Hey, I just tested the Linux-Shellscript. In the past, when the JAVA_HOME variable wasn't set, it returned an error. When testing it now, it doesn't fail but instead shows: "Java version 1.4.2 not supported. Supported versions are 1.5" When I set JAVA_HOME, everything is fine. Do we really need JAVA_HOME? Because usually, all the java tools are known through PATH, I think? Sascha Wolfgang Korn wrote: > Guys, > > I just committed some changes. > > * The shell scripts should work now > * The Ant script performs a basic check on the Java version being > used. Currently all JDKs other than 1.5 should cause a failure > * Fixed the problem with the log4j warning. The reason for this > warnig was a missing log4j.xml in classes/core. Eclipse already > copied this file from core/src to classes/core but the Ant > script did not. > > @Arno: The problem concerning LayoutDemo you reported today is not > caused by the log4j problem mentioned above. The log4j problem only > caused missing log output. Besides that I can not reproduce that > problem with LayoutDemo on my box. > > -- Frusty > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > > _______________________________________________ > XML11-devel mailing list > XML...@li... > https://lists.sourceforge.net/lists/listinfo/xml11-devel > |
|
From: Wolfgang K. <wol...@gm...> - 2006-08-01 17:32:58
|
Guys,
I just committed some changes.
* The shell scripts should work now
* The Ant script performs a basic check on the Java version being
used. Currently all JDKs other than 1.5 should cause a failure
* Fixed the problem with the log4j warning. The reason for this
warnig was a missing log4j.xml in classes/core. Eclipse already
copied this file from core/src to classes/core but the Ant script
did not.
@Arno: The problem concerning LayoutDemo you reported today is not
caused by the log4j problem mentioned above. The log4j problem only
caused missing log output. Besides that I can not reproduce that problem
with LayoutDemo on my box.
-- Frusty
|
|
From: Arno P. <ar...@pu...> - 2006-08-01 11:40:08
|
Guys, we plan to make a new release of XML11 (version 0.3), hopefully this week. Everybody: please test, test, test and give feedback on this list. Thx, Arno |
|
From: Arno P. <ar...@pu...> - 2006-08-01 11:09:17
|
I can't run LayoutDemo with code migration anymore. I get the error below. Frusty: I suspect it has something to do with your changes. Can you please investigate? Arno log4j:WARN No appenders could be found for logger (org.xml11.util.JarFileHandler). log4j:WARN Please initialize the log4j system properly. java.lang.ClassNotFoundException: org.xml11.demo.step4.LayoutDemo at org.xml11.util.XML11ClassLoader.findClass(XML11ClassLoader.java:421) at org.xml11.util.XML11ClassLoader.loadClass(XML11ClassLoader.java:241) at java.lang.ClassLoader.loadClass(Unknown Source) at org.xml11.util.XML11ClassLoader.loadApplication(XML11ClassLoader.java:204) at org.xml11.gw.RunApplication.run(RunApplication.java:78) |
|
From: Wolfgang K. <wol...@gm...> - 2006-07-31 19:30:51
|
I guess there is a way. But I have to check this. I think, additionally the Ant-scripts should make sure that JAVA_HOME is set. -- Frusty Arno Puder wrote: > > ok, Frusty and Chris have already subscribed. Lets continue this > discussion on the XML11-devel mailing list. > > Frusty: is there any way that the ant-scripts can make sure that Java > 5 is used? It seems that Java 1.4 no longer works because of some > minor changes in the AWT. > > Arno > > ------------------------------------------------------------------------ > > Subject: > Re: ant scripts > From: > Christopher Kriese <ch...@ya...> > Date: > Mon, 31 Jul 2006 11:50:45 -0700 (PDT) > To: > Christopher Kriese <ch...@ya...>, Arno Puder <ar...@pu...>, > Wolfgang Korn <wol...@gm...> > > To: > Christopher Kriese <ch...@ya...>, Arno Puder <ar...@pu...>, > Wolfgang Korn <wol...@gm...> > CC: > Christopher Kriese <ch...@ya...> > > > OK...I now have the same output as Arno. My JAVA_HOME env var was not set. > > cjk > > --- Christopher Kriese <ch...@ya...> wrote: > > >> My errors are a bit different. Some Java interfaces are not fully >> implemented. >> >> init-core: >> [mkdir] Created dir: /home/chris/xml11/XML11/classes/core >> >> compile-core: >> [javac] Compiling 27 source files to /home/chris/xml11/XML11/classes/core >> [javac] ---------- >> [javac] 1. ERROR in >> /home/chris/xml11/XML11/core/src/org/xml11/awt/XML11ButtonPeer.java >> [javac] (at line 45) >> [javac] public class XML11ButtonPeer >> [javac] ^^^^^^^^^^^^^^^ >> [javac] The type XML11ButtonPeer must implement the inherited abstract >> method ComponentPeer.requestFocus() >> [javac] ---------- >> [javac] 2. ERROR in >> /home/chris/xml11/XML11/core/src/org/xml11/awt/XML11ButtonPeer.java >> [javac] (at line 45) >> [javac] public class XML11ButtonPeer >> [javac] ^^^^^^^^^^^^^^^ >> [javac] The type XML11ButtonPeer must implement the inherited abstract >> method ComponentPeer.isFocusTraversable() >> [javac] ---------- >> >> >> [...ETC....ETC...] >> >> cjk >> >> --- Arno Puder <ar...@pu...> wrote: >> >> >>> here is the error I get with the current CVS head: >>> >>> init-simplewebgw: >>> [mkdir] Created dir: C:\workspace\XML11\classes\simplewebgw >>> >>> compile-simplewebgw: >>> >>> BUILD FAILED >>> C:\workspace\XML11\targets\simplewebgw-targets.xml:51: srcdir >>> "C:\workspace\XML1 >>> 1\simplewebgw\src" does not exist! >>> >>> Total time: 3 seconds >>> >>> >>> Wolfgang Korn wrote: >>> >>>> Arno, >>>> >>>> what troubles do you have? I just updated to have the latest changes on >>>> my box and I do not have any problems. The project compiles (excpet some >>>> Java5 warnings). The XML11Server can be started and demos are running >>>> perfectly. >>>> >>>> -- Frusty >>>> >>>> >>>> >>>> Arno Puder wrote: >>>> >>>>> Frusty, >>>>> >>>>> a student of mine (Chris, CCed) and I are having troubles with the ant >>>>> scripts. Could you please check and let us both know what is going on? >>>>> >>>>> Thx, >>>>> Arno >>>>> >>>>> >> Christopher J. Kriese >> >> > > > Christopher J. Kriese > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > > _______________________________________________ > XML11-devel mailing list > XML...@li... > https://lists.sourceforge.net/lists/listinfo/xml11-devel > |
|
From: Arno P. <ar...@pu...> - 2006-07-31 19:04:33
|
ok, Frusty and Chris have already subscribed. Lets continue this discussion on the XML11-devel mailing list. Frusty: is there any way that the ant-scripts can make sure that Java 5 is used? It seems that Java 1.4 no longer works because of some minor changes in the AWT. Arno |
|
From: Arno P. <ar...@pu...> - 2006-07-31 18:28:04
|
;-) |
