Re[2]: [mojo-dev] flatten-maven-plugin last steps towards release

2014-04-08 Thread Sergei Ivanov 
JDK for running maven is not the same as JDK for building the project. You can 
control the latter through toolchains, which allows you to run maven (and 
plugins) under Java 8, but still build your project sources under Java 1.4 if 
needed. As a concrete example, our maven build requires java 7 (dictated by 
nbm-maven-plugin), but the projects are built for both java 6 and 7.
+1 for ditching java5 support
--
Sergei Ivanov

Tuesday, 8 April 2014 07:20 +0100 from Anders Hammar  :
I'd say it's up to you as the developer to decide on java requirement. 
Personally I would ditch java 5 support and go for a Java 6+ requirement. But 
as Robert says, it could make the plugin impossible to use for some people.
/Anders (mobile)
Den 7 apr 2014 23:46 skrev "Robert Scholte" < codeh...@sourcegrounds.com >:
>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
 :
>>>
>>>    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  MATHUS -  http://batmat.net
>>>Sauvez un arbre,
>>>Mangez un castor !
>
>-- -- -
>To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/ manage_email
>
>

[mojo-dev] [jira] (MOJO-2011) A way of executing filelist-upgrade goal without an explicit file list

2014-04-08 Thread Dipanjan Laha (JIRA) 
Title: Message Title










 

 Dipanjan Laha commented on an issue











 






  Re: A way of executing filelist-upgrade goal without an explicit file list 










I tested both the file list and recursive upgrade method from the staging repository. It works quite well and I haven't faced any issue yet.












   

 Add Comment











 













 Mojo /  MOJO-2011



  A way of executing filelist-upgrade goal without an explicit file list 







 The filelist-upgrade goal requires an explicit file list to be present from which the SQL script files names/locations are picked and executed.   I would like to suggest an optional way of executing these SQL files without having the explicit file list. The plugin can pick up the files in a lexicographical order and execute them. If the files are nested...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MVERSIONS-255) add versions:lock-snapshots also for parents

2014-04-08 Thread Renate Achter (JIRA) 
Title: Message Title










 

 Renate Achter created an issue











 






 Mojo's Versions Maven Plugin /  MVERSIONS-255



  add versions:lock-snapshots also for parents 










Issue Type:

  New Feature




Affects Versions:


 3.0




Assignee:


 Unassigned




Created:


 08/Apr/14 4:01 AM




Priority:

  Major




Reporter:

 Renate Achter










In the same manner as working for dependencies, there should be a possibility to lock snapshot-versions in parents.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)

Re: Re[2]: [mojo-dev] flatten-maven-plugin last steps towards release

2014-04-08 Thread Anders Hammar 
> JDK for running maven is not the same as JDK for building the project. You
> can control the latter through toolchains, which allows you to run maven
> (and plugins) under Java 8, but still build your project sources under Java
> 1.4 if needed. As a concrete example, our maven build requires java 7
> (dictated by nbm-maven-plugin), but the projects are built for both java 6
> and 7.
>

In this case the plugin has a dependency which requires Java 6+, so there
is no point in building the plugin's code for Java 5 or lower.

/Anders


> +1 for ditching java5 support
> --
> Sergei Ivanov
>
> Tuesday, 8 April 2014 07:20 +0100 from Anders Hammar  :
> I'd say it's up to you as the developer to decide on java requirement.
> Personally I would ditch java 5 support and go for a Java 6+ requirement.
> But as Robert says, it could make the plugin impossible to use for some
> people.
> /Anders (mobile)
> Den 7 apr 2014 23:46 skrev "Robert Scholte" < codeh...@sourcegrounds.com>:
> >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
>  :
> >>>
> >>>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  MATHUS -  htt

[mojo-dev] [jira] (MSONAR-61) New properties sonar.maven.skipModules and sonar.maven.includeModules

2014-04-08 Thread Fabrice Bellingard (JIRA) 
Title: Message Title










 

 Fabrice Bellingard updated an issue











 






 Mojo's Sonar Maven Plugin /  MSONAR-61



  New properties sonar.maven.skipModules and sonar.maven.includeModules 










Change By:

 Fabrice Bellingard




Assignee:

 Fabrice Bellingard Julien HENRY












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MSONAR-61) New properties sonar.maven.skipModules and sonar.maven.includeModules

2014-04-08 Thread Fabrice Bellingard (JIRA) 
Title: Message Title










 

 Fabrice Bellingard assigned an issue to Fabrice Bellingard











 






 Mojo's Sonar Maven Plugin /  MSONAR-61



  New properties sonar.maven.skipModules and sonar.maven.includeModules 










Change By:

 Fabrice Bellingard




Assignee:

 Fabrice Bellingard












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MSONAR-61) Improve support of advanced reactor options

2014-04-08 Thread Julien HENRY (JIRA) 
Title: Message Title










 

 Julien HENRY updated an issue











 






 Mojo's Sonar Maven Plugin /  MSONAR-61



  Improve support of advanced reactor options 










Change By:

 Julien HENRY




Summary:

 New properties sonar.maven.skipModules and sonar.maven.includeModules Improve support of advanced reactor options












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MSONAR-61) Improve support of advanced reactor options

2014-04-08 Thread Julien HENRY (JIRA) 
Title: Message Title










 

 Julien HENRY updated an issue











 






 Mojo's Sonar Maven Plugin /  MSONAR-61



  Improve support of advanced reactor options 










Change By:

 Julien HENRY









 Selection of the modules to analyze is the responsibility of the Maven plugin but not of SonarQube internals. That's why the properties sonar. maven.skipModules and sonar.maven.includeModules must replace sonar. skippedModules and sonar.includedModules , which  are going to be deprecated. Instead people should be able to use standard reactor options (or profiles) to exclude some modules from SQ analysis.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MSONAR-61) Improve support of advanced reactor options

2014-04-08 Thread Julien HENRY (JIRA) 
Title: Message Title










 

 Julien HENRY assigned an issue to Fabrice Bellingard











 







You can now use advanced reactor options to list the modules you want in the analysis. The only constraint is that the reactor is a consistent tree (single root, no orphans branches).









 Mojo's Sonar Maven Plugin /  MSONAR-61



  Improve support of advanced reactor options 










Change By:

 Julien HENRY




Assignee:

 Julien HENRY Fabrice Bellingard












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MSONAR-65) PMD BeanMembersShouldSerialize and BooleanGetMethodName cause IllegalDataException

2014-04-08 Thread Simon Brandhof (JIRA) 
Title: Message Title










 

 Simon Brandhof updated an issue











 






 Mojo's Sonar Maven Plugin /  MSONAR-65



  PMD BeanMembersShouldSerialize and BooleanGetMethodName cause IllegalDataException 










Change By:

 Simon Brandhof




Assignee:

 Simon Brandhof












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MSONAR-60) Embed sonar-runner

2014-04-08 Thread Fabrice Bellingard (JIRA) 
Title: Message Title










 

 Fabrice Bellingard assigned an issue to Julien HENRY











 







Tested!









 Mojo's Sonar Maven Plugin /  MSONAR-60



  Embed sonar-runner 










Change By:

 Fabrice Bellingard




Assignee:

 Fabrice Bellingard Julien HENRY












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MSONAR-60) Embed sonar-runner

2014-04-08 Thread Julien HENRY (JIRA) 
Title: Message Title










 

 Julien HENRY closed an issue as Fixed











 






 Mojo's Sonar Maven Plugin /  MSONAR-60



  Embed sonar-runner 










Change By:

 Julien HENRY




Resolution:

 Fixed




Status:

 Open Closed












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [mojo-dev] flatten-maven-plugin last steps towards release

2014-04-08 Thread Jörg Hohwiller 

Hi there,

I would not mind in making the code compatible with Java 1.5 but there 
really seems to be no real point:
Java 1.5 and Java 1.6 are both far beyond end-of-life and not even 
getting public updates anymore so they are a security threat except you 
have a premium support contract with Oracle:

http://www.oracle.com/technetwork/java/javase/eol-135779.html

Cheers
  Jörg

Am 08.04.2014 11:51, schrieb Anders Hammar:


JDK for running maven is not the same as JDK for building the
project. You can control the latter through toolchains, which
allows you to run maven (and plugins) under Java 8, but still
build your project sources under Java 1.4 if needed. As a concrete
example, our maven build requires java 7 (dictated by
nbm-maven-plugin), but the projects are built for both java 6 and 7.


In this case the plugin has a dependency which requires Java 6+, so 
there is no point in building the plugin's code for Java 5 or lower.


/Anders

+1 for ditching java5 support
--
Sergei Ivanov

Tuesday, 8 April 2014 07:20 +0100 from Anders Hammar
 mailto:and...@hammar.net>>:
I'd say it's up to you as the developer to decide on java
requirement. Personally I would ditch java 5 support and go for a
Java 6+ requirement. But as Robert says, it could make the plugin
impossible to use for some people.
/Anders (mobile)
Den 7 apr 2014 23:46 skrev "Robert Scholte" <
codeh...@sourcegrounds.com  >:
>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-