Hi,
I've added 2 plugins which verify the sources and dependencies. So it's
not required to use an old JDK anymore(unless you want to be 100% sure).
So now you need to find an older version of plexus-utils ;)
You will be surprised how often JDK5 is still used. Especially the bigger
companies can struggle with moving forwards to a more recent JDK,
sometimes caused by the version of the webcontainer.
I don't mind the watermark being aggressive. Users should be aware of the
status of the plugin, developers should be motivated to move it faster to
a final version.
regards,
Robert
Op Mon, 07 Apr 2014 23:22:24 +0200 schreef Jörg Hohwiller
<jo...@j-hohwiller.de>:
Hi,
I changed the skin. Please note that the watermarks are very aggressive.
For the sandbox skin I got feedback from others that they could not read
the information properly.
I was able to get some JDK1.5 from a museum. However, I doubt that
anybody still requires 1.5 compatibility today.
Finally I can not build with JDK 1.5:
[INFO] BUILD FAILURE
[INFO]
---------------------------------------------------------------------
---
[INFO] Total time: 5.629s
[INFO] Finished at: Mon Apr 07 23:17:58 CEST 2014
[INFO] Final Memory: 13M/26M
[INFO]
---------------------------------------------------------------------
---
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugi
n:2.5.1:compile (default-compile) on project flatten-maven-plugin:
Compilation f
ailure
[ERROR]
C:\Users\hohwille\projects\OSS\flatten-maven-plugin\src\main\java\or
g\codehaus\mojo\flatten\FlattenMojo.java:[61,-1] cannot access
org.codehaus.plex
us.util.IOUtil
[ERROR] bad class file:
C:\Users\hohwille\.m2\repository\org\codehaus\plexus
\plexus-utils\3.0.17\plexus-utils-3.0.17.jar(org/codehaus/plexus/util/IOUtil.cla
ss)
[ERROR] class file has wrong version 50.0, should be 49.0
[ERROR] -> [Help 1]
What should I do now?
To me it seems as this information is not consistent as IOUtil from
plexus is not even JDK 1.5 compliant.
Or do I missunderstand the error message?
Regards
Jörg
Am 04.04.2014 09:04, schrieb Baptiste Mathus:
Hi,
Should be OK. Also replace the skin with the pre-release one, as I
suppose you're not releasing a non qualified (alpha, beta) version
directly?
As for adding the plugin already in plugins.apt, I guess it's
generally better to do it afterwards. Because if someone in the team
ini the meantime fixes something and redeploys the website, there wll
be a reference to flatten-maven-plugin not yet existing.
Also beware using a JDK5 locally for releasing to prevent any unwanted
usage creeping in (as we didn't set up animal-sniffer IIRC).
Have fun.
Cheers
2014-04-04 0:31 GMT+02:00 Jörg Hohwiller <jo...@j-hohwiller.de
<mailto:jo...@j-hohwiller.de>>:
Hi there,
I have moved flattend-maven-plugin out of sandbox:
* moved folder in svn
* change pom (updated parent)
* removed sandbox skin in site.xml
* moved plugin link in plugins.apt (already with upcoming
version that is not yet released).
For the actual release I would follow
http://mojo.codehaus.org/development/performing-a-release.html
and do these steps:
* stage the release (remove SNAPSHOT from version, create SVN
tag, all via release plugin)
* start a vote
Anything I might be missing?
Sorry for all the double checking but the previous mojo I wrote
had been released by others.
Cheers
Jörg
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
