Re: [josm-dev] Java 1.5 versus 1.6
On Sat, Feb 13, 2010 at 4:55 PM, Henry Loenwind wrote: > On 13.02.2010 14:24, Dirk Stöcker wrote: > > > I would not care about that any more. Java 1.5 support will be dropped > > with next release and we have< 4% Java 5 users (actually I only see > > "page impressions", not "users"). Suggestion for these is to update. > > Update like in "buy a new pc"? Yeah, people will just love you ;) > > Java 1.6 still is not available for all platforms that run 1.5. And it > seems that won't change---so with going to 1.6 you'd lock out all Mac > users but those with a 64-bit Intel processor. In my opinion its still > too early to lock out all those 32bit Intel processor (e.g. Core Duo) > users without any real reason. > > this is wrong all intel based macs support snow leopard which includes java 1.6 leopard 1.6 support is 64bit only if someone doesn't upgrade the OS why upgrade josm? old josm versions will still work only G* based macs have no official 1.6 support. there is also soylatte which may work. but have never tested josm only osmosis, or mkgmap > > BTW, those with a 64bit Mac and OSX 10.5 will need some advice on how to > use Java 1.6. Point them to: > > http://superuser.com/questions/100078/java-1-6-on-mac-os-x-10-5 > > cu > Henry > > ___ > josm-dev mailing list > josm-dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/josm-dev > ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Java 1.5 versus 1.6
Henry, Henry Loenwind wrote: > Java 1.6 still is not available for all platforms that run 1.5. And it > seems that won't change---so with going to 1.6 you'd lock out all Mac > users but those with a 64-bit Intel processor. In my opinion its still > too early to lock out all those 32bit Intel processor (e.g. Core Duo) > users without any real reason. I have no sympathy for Mac users. It is fine for them to voluntarily chain themselves to one supplier. It is fine for them to keep their old hardware for which said supplier refuses to release new software. All their decision. But I don't see why we should hold back with sensible advancements just because these people have got a bad deal from their one and only beloved vendor. We should not allow Apple's product strategy to have an influence on JOSM development. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Java 1.5 versus 1.6
On 13.02.2010 14:24, Dirk Stöcker wrote: > I would not care about that any more. Java 1.5 support will be dropped > with next release and we have< 4% Java 5 users (actually I only see > "page impressions", not "users"). Suggestion for these is to update. Update like in "buy a new pc"? Yeah, people will just love you ;) Java 1.6 still is not available for all platforms that run 1.5. And it seems that won't change---so with going to 1.6 you'd lock out all Mac users but those with a 64-bit Intel processor. In my opinion its still too early to lock out all those 32bit Intel processor (e.g. Core Duo) users without any real reason. BTW, those with a 64bit Mac and OSX 10.5 will need some advice on how to use Java 1.6. Point them to: http://superuser.com/questions/100078/java-1-6-on-mac-os-x-10-5 cu Henry ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Java 1.5 versus 1.6 for plugins
On Fri, 12 Feb 2010, Roland Olbricht wrote: > I've just developed a plugin (Public Transport) for JOSM which should be as > portable as possible. Now I've received a request of a Mac OS user using Java > 1.5 that the plugin doesn't work. > > I've set > > in > http://svn.openstreetmap.org/applications/editors/josm/plugins/public_transport/build.xml > > and I don't use any special features of Java 1.6. So has anybody an idea why > the plugin doesn't work with Java 1.5? I would not care about that any more. Java 1.5 support will be dropped with next release and we have < 4% Java 5 users (actually I only see "page impressions", not "users"). Suggestion for these is to update. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] deleting relations fails due to not fullfiled prerequirements
Karl Guggisberg wrote: > Hi Werner > > I'd say it's a JOSM *feature*, not a defect. JOSM correctly detects > that the server wasn't able to delete a relation because it was still > in use by some other relation. > >> Simple workaround: Remove 73724 first and 73723 with a second >> changeset. > That's how to do it. It isn't a workaround. There is nothing wrong about deleting these two relations, why should it result in an error? We have already the rule to upload first all nodes, then all ways and then all relations. In a similar manner, JOSM should sort the relations in a way that keeps the server happy. __ Basti ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] deleting relations fails due to not fullfiled prerequirements
Hi Werner I'd say it's a JOSM *feature*, not a defect. JOSM correctly detects that the server wasn't able to delete a relation because it was still in use by some other relation. > Simple workaround: > Remove 73724 first and 73723 with a second changeset. That's how to do it. It isn't a workaround. Regards Karl Am 13.02.2010 10:04, schrieb Werner Hoch: > Hi there, > > I'm not sure if this is a JOSM problem. > > I've tried to delete the relations 73723 and 73724. > 73723 is the only element of 73724. > http://www.openstreetmap.org/browse/relation/73724 > > When I try to upload the change, I get an error message > that 73723 cannot be deleted because it is an element of > 73724. > The complete message is (German): > - > Vorbedingung nicht erfüllt > Die Relation 73723 konnte nicht gelöscht werden. Sie wird immer > noch von Relation 73724 referenziert. Bitte laden Sie die Relation > 73724, entfernen Sie die Referenz auf Relation 73723 und laden Sie > erneut hoch. > -- > > I think that the prerequirements are fullfiled if relation 73724 > is removed, too. > > Simple workaround: > Remove 73724 first and 73723 with a second changeset. > > I'm using JOSM version 2561. > > Regards > Werner > > ___ > josm-dev mailing list > josm-dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/josm-dev > > ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] deleting relations fails due to not fullfiled prerequirements
Hi there, I'm not sure if this is a JOSM problem. I've tried to delete the relations 73723 and 73724. 73723 is the only element of 73724. http://www.openstreetmap.org/browse/relation/73724 When I try to upload the change, I get an error message that 73723 cannot be deleted because it is an element of 73724. The complete message is (German): - Vorbedingung nicht erfüllt Die Relation 73723 konnte nicht gelöscht werden. Sie wird immer noch von Relation 73724 referenziert. Bitte laden Sie die Relation 73724, entfernen Sie die Referenz auf Relation 73723 und laden Sie erneut hoch. -- I think that the prerequirements are fullfiled if relation 73724 is removed, too. Simple workaround: Remove 73724 first and 73723 with a second changeset. I'm using JOSM version 2561. Regards Werner ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
