search

rehamaltamimi / gwtwiki

Automatically exported from code.google.com/p/gwtwiki
0 stars 0 forks source link

All release versions in the Maven are broken #61

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Every single class file has been compiled for Java 6 which makes it completely 
unusable with Java 5.
Altough the POM is configured for 1.5 the files are still 1.6.

See example:
C:\Dokumente und Einstellungen\mosipov>C:\Programme\Java\jdk1.6.0_23\bin\javap.e
xe -classpath E:\Downloads\bliki-core-3.0.14.jar -verbose info.bliki.htmlcleaner
.TagNode | more
Compiled from "TagNode.java"
public class info.bliki.htmlcleaner.TagNode extends info.bliki.htmlcleaner.TagTo
ken
  SourceFile: "TagNode.java"
  minor version: 0
  major version: 50
  Constant pool:
...

I tried from 3.0.12 thru 3.0.15 all unusable.

Immediate action must be taken!

Original issue reported on code.google.com by 1983-01...@gmx.net on 17 Dec 2010 at 3:07

GoogleCodeExporter commented 8 years ago 
The subject should read: All release versions in the Maven repo are broken

Original comment by 1983-01...@gmx.net on 17 Dec 2010 at 3:08

GoogleCodeExporter commented 8 years ago 
I changed compiler settings.
Could you please try the latest 3.0.16-SNAPSHOT?

http://code.google.com/p/gwtwiki/wiki/MavenSupport

Original comment by axelclk@gmail.com on 18 Dec 2010 at 9:57

GoogleCodeExporter commented 8 years ago 
This snapshot works as desired. Altough I need a release version, I cannot rely 
on a snapshot version. Please do fork 3.0.15, fix it and deploy as 3.0.16 and 
bump the current 3.0.16-SNAPSHOT to 3.0.17-SNAPSHOT.

A few other related things I'd like to comment for you to have some lessons 
learned:

1. http://code.google.com/p/gwtwiki/source/detail?r=2890 You *never* ever check 
in config files of an IDE or anything else autogenerated.
2. It is a break of principle to use 2 build tools at the same time. Stick to 
one. If you use Eclipse, do not use Maven at all (to build your software) and 
vice versa.
3. If you want to use both, rely on m2eclipse and let it configure Eclipse for 
you or Maven from the shell only.

Grüße aus Berlin

Original comment by 1983-01...@gmx.net on 18 Dec 2010 at 11:28

GoogleCodeExporter commented 8 years ago 
My comment would be to stick with maven, some of us don't use Eclipse.

Original comment by dfisla@gmail.com on 18 Dec 2010 at 1:29

GoogleCodeExporter commented 8 years ago 
I think 3.0.16 is stable enough.

So I created 3.0.16 release in Maven repo as a first step.

Original comment by axelclk@gmail.com on 18 Dec 2010 at 4:09

GoogleCodeExporter commented 8 years ago

Original comment by axelclk@gmail.com on 21 Apr 2011 at 5:41