[jira] [Created] (MRELEASE-973) Please keep the property performRelease or provide an alternativ for it

2016-12-27 Thread Oliver B. Fischer (JIRA) 
Oliver B. Fischer created MRELEASE-973:
--

 Summary: Please keep the property performRelease or provide an 
alternativ for it
 Key: MRELEASE-973
 URL: https://issues.apache.org/jira/browse/MRELEASE-973
 Project: Maven Release Plugin
  Issue Type: Wish
  Components: perform
Affects Versions: 3.0.0
Reporter: Oliver B. Fischer
Priority: Critical
 Fix For: 3.0.0


MRELEASE-896 deprecates the {{useReleaseProfile}} and changed its default value 
from {{true}} to {{false}}. 

Unfortunately this disabled also the setting of the property {{performRelease}} 
which we use to enable multiple profiles during the release process.

At least we need a possibility to enable multiple, sometimes different, 
profiles during a release and its preparation.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] Commented: (MCHECKSTYLE-164) Multimodule Configuration example does not show how to configure build-tools pom

2011-09-22 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MCHECKSTYLE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279647#comment-279647
 ] 

Oliver B. Fischer commented on MCHECKSTYLE-164:
---

Hi sebbaz,

simply take a minimal {{pom.xml}} like this:

{noformat}

http://maven.apache.org/POM/4.0.0";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0


com.company
parent
5.4.5
..


com.company
checkstyle
5.4.5
Checkstyle Configuration

{noformat}

I will create a jar file containing your checkstyle configuration. But you are 
right, it would be helpfull to have such an example.

> Multimodule Configuration example does not show how to configure build-tools 
> pom
> 
>
> Key: MCHECKSTYLE-164
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-164
> Project: Maven 2.x Checkstyle Plugin
>  Issue Type: Bug
> Environment: 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
>Reporter: sebbaz+ch
>
> It would be helpful if the page documented how to configure the build-tools 
> pom.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Issue Comment Edited: (MCHECKSTYLE-164) Multimodule Configuration example does not show how to configure build-tools pom

2011-09-22 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MCHECKSTYLE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279647#comment-279647
 ] 

Oliver B. Fischer edited comment on MCHECKSTYLE-164 at 9/22/11 9:46 AM:


Hi sebbaz,

simply take a minimal {{pom.xml}} like this:

{noformat}

http://maven.apache.org/POM/4.0.0";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0


com.company
parent
5.4.5
..


com.company
checkstyle
5.4.5
Checkstyle Configuration

{noformat}

I will create a jar file containing your checkstyle configuration. But you are 
right, it would be helpfull to have such an example.

  was (Author: oliver.b.fischer):
Hi sebbaz,

simply take a minimal {{pom.xml}} like this:

{noformat}

http://maven.apache.org/POM/4.0.0";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0


com.company
parent
5.4.5
..


com.company
checkstyle
5.4.5
Checkstyle Configuration

{noformat}

I will create a jar file containing your checkstyle configuration. But you are 
right, it would be helpfull to have such an example.
  
> Multimodule Configuration example does not show how to configure build-tools 
> pom
> 
>
> Key: MCHECKSTYLE-164
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-164
> Project: Maven 2.x Checkstyle Plugin
>  Issue Type: Bug
> Environment: 
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
>Reporter: sebbaz+ch
>
> It would be helpful if the page documented how to configure the build-tools 
> pom.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MNG-5178) Substitute environment variable M2_HOME by M3_HOME

2011-09-27 Thread Oliver B. Fischer (JIRA) 
Substitute environment variable M2_HOME by M3_HOME
--

 Key: MNG-5178
 URL: https://jira.codehaus.org/browse/MNG-5178
 Project: Maven 2 & 3
  Issue Type: Wish
  Components: Command Line
Reporter: Oliver B. Fischer
Priority: Minor


Maven 3 uses the environment variable {{M2_HOME}} to point to it's installation 
directory. This variable should be replaced by {{M3_HOME}} to allow users to 
have parallel installations of Maven 2 and Maven 3 without any special handling 
of the environment variable {{M2_HOME}}.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MNG-5179) Unable to checkout https://svn.codehaus.org/mojo/trunk because of non-portable filenames

2011-09-29 Thread Oliver B. Fischer (JIRA) 
Unable to  checkout https://svn.codehaus.org/mojo/trunk because of non-portable 
filenames
-

 Key: MNG-5179
 URL: https://jira.codehaus.org/browse/MNG-5179
 Project: Maven 2 & 3
  Issue Type: Bug
 Environment: Windows 7
Reporter: Oliver B. Fischer


Today I tried to checkout the public Subversion repository available at 
[https://svn.codehaus.org/mojo/trunk]. The command {{svn checkout}} failed to 
checkout all mojos because a non-portable filename used in the solaris mojo.

Here is the error message of {{svn checkout}}:

{code}
svn: Kann Datei 
¯solaris\solaris-maven-plugin\src\test\projects\project-relocation\target\root\server\repo\org\apache\geronimo\specs\geronimo-j2ee-management_1.0_spec\1.0.1\.svn\tmp\text-base\geronimo-j2ee-management_1.0_spec-1.0.1.jar.svn-base®
 nicht "ffnen: Das System kann den angegebenen Pfad nicht finden.  
{code}

If would be great if this problem could be solved.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-5179) Unable to checkout https://svn.codehaus.org/mojo/trunk because of non-portable filenames

2011-09-29 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280239#comment-280239
 ] 

Oliver B. Fischer commented on MNG-5179:


I tried to file this issue in the MPA project, but I can't open an issue in 
this project.

> Unable to  checkout https://svn.codehaus.org/mojo/trunk because of 
> non-portable filenames
> -
>
> Key: MNG-5179
> URL: https://jira.codehaus.org/browse/MNG-5179
> Project: Maven 2 & 3
>  Issue Type: Bug
> Environment: Windows 7
>Reporter: Oliver B. Fischer
>
> Today I tried to checkout the public Subversion repository available at 
> [https://svn.codehaus.org/mojo/trunk]. The command {{svn checkout}} failed to 
> checkout all mojos because a non-portable filename used in the solaris mojo.
> Here is the error message of {{svn checkout}}:
> {code}
> svn: Kann Datei 
> ¯solaris\solaris-maven-plugin\src\test\projects\project-relocation\target\root\server\repo\org\apache\geronimo\specs\geronimo-j2ee-management_1.0_spec\1.0.1\.svn\tmp\text-base\geronimo-j2ee-management_1.0_spec-1.0.1.jar.svn-base®
>  nicht "ffnen: Das System kann den angegebenen Pfad nicht finden.  
> {code}
> If would be great if this problem could be solved.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (SUREFIRE-600) Surefire + TestNG executes tests annotated as disabled, if superclasses are enabled.

2012-01-17 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/SUREFIRE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288576#comment-288576
 ] 

Oliver B. Fischer commented on SUREFIRE-600:


I have a similar problem with disabled test classes inheriting from 
{{org.jboss.arquillian.testng.Arquillian}}.

It is not possible to disable this tests in our setup.

> Surefire + TestNG executes tests annotated as disabled, if superclasses are 
> enabled.
> 
>
> Key: SUREFIRE-600
> URL: https://jira.codehaus.org/browse/SUREFIRE-600
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: TestNG support
>Affects Versions: 2.4.3, 2.5
> Environment: TestNG 5.11, Maven 2.2.1, Apple & Sun JDK 6
>Reporter: Manik Surtani
>
> This has to do with a test class extending a base test class, and both 
> classes are annotated with {{@Test}}.  The parent class would have {{@Test 
> (enabled = true)}} and the child {{@Test (enabled = false)}}.  The child test 
> is still run, and this is contradictory to the behaviour of TestNG run in 
> other forms (command line, via IDEs, etc).
> I suspect this has to do with the way @Test annotations are parsed by 
> Surefire when deciding which classes to pass to TestNG.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MCHECKSTYLE-171) Wrong Link Generation for Checkstyle report

2012-02-09 Thread Oliver B. Fischer (JIRA) 
Oliver B. Fischer created MCHECKSTYLE-171:
-

 Summary: Wrong Link Generation for Checkstyle report
 Key: MCHECKSTYLE-171
 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-171
 Project: Maven 2.x Checkstyle Plugin
  Issue Type: Bug
Affects Versions: 2.8
Reporter: Oliver B. Fischer


The Checkstyle report for the Checkstyle report generates in our project wrong 
anchors.

The link for the file {{ServiceServicejava.java}}

{code}
/com/company/provisioning/model/client/ServiceServicejava.java
{code}

and the corresponding anchor as

{code}

{code}

It would be nice to see this issue fixed in the next version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MCHECKSTYLE-171) Wrong Link Generation for Checkstyle report

2012-02-10 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MCHECKSTYLE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291331#comment-291331
 ] 

Oliver B. Fischer commented on MCHECKSTYLE-171:
---

Yes, I will prepare something to show the problem within the next days.

> Wrong Link Generation for Checkstyle report
> ---
>
> Key: MCHECKSTYLE-171
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-171
> Project: Maven 2.x Checkstyle Plugin
>  Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Oliver B. Fischer
>
> The Checkstyle report for the Checkstyle report generates in our project 
> wrong anchors.
> The link for the file {{ServiceServicejava.java}}
> {code}
>   >/com/company/provisioning/model/client/ServiceServicejava.java
> {code}
> and the corresponding anchor as
> {code}
> 
> {code}
> It would be nice to see this issue fixed in the next version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5178) Substitute environment variable M2_HOME by M3_HOME

2012-03-07 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293620#comment-293620
 ] 

Oliver B. Fischer commented on MNG-5178:


This is exactly that I thought how it should be handled.

> Substitute environment variable M2_HOME by M3_HOME
> --
>
> Key: MNG-5178
> URL: https://jira.codehaus.org/browse/MNG-5178
> Project: Maven 2 & 3
>  Issue Type: Wish
>  Components: Command Line
>Reporter: Oliver B. Fischer
>Priority: Minor
>
> Maven 3 uses the environment variable {{M2_HOME}} to point to it's 
> installation directory. This variable should be replaced by {{M3_HOME}} to 
> allow users to have parallel installations of Maven 2 and Maven 3 without any 
> special handling of the environment variable {{M2_HOME}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MSITE-726) Document who report sets are selected

2014-07-24 Thread Oliver B. Fischer (JIRA) 
Oliver B. Fischer created MSITE-726:
---

 Summary: Document who report sets are selected
 Key: MSITE-726
 URL: https://jira.codehaus.org/browse/MSITE-726
 Project: Maven Site Plugin
  Issue Type: Wish
  Components: documentation
Affects Versions: 3.4
Reporter: Oliver B. Fischer
Priority: Minor


Set section [Configuring 
Reports|http://maven.apache.org/plugins/maven-site-plugin/examples/configuring-reports.html]
 of the Maven Site plugin describes who to configure multiple report sets. 

After reading this section I got the impression that I can define as many 
report sets as I would like to have. But the {{aggregate}} report set seems to 
be choosen for packing type {{pom}}.

Hence it would be very helpfull to have very simple and clear explanation how 
many reports are possible and which report set is choosen under which 
condition. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-3525) Settings.xml allowing mirror definitions inside profiles

2014-08-01 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350819#comment-350819
 ] 

Oliver B. Fischer commented on MNG-3525:


Same problem here.

> Settings.xml allowing mirror definitions inside profiles
> 
>
> Key: MNG-3525
> URL: https://jira.codehaus.org/browse/MNG-3525
> Project: Maven
>  Issue Type: Improvement
>  Components: Profiles
>Affects Versions: 2.0.9
> Environment: N/A
>Reporter: Paul Grove
> Fix For: Issues to be reviewed for 3.x
>
>
> I currently use Maven in 2 places 
> 1. At work 
> 2. Not at work
> At work we have a repository manager thus we have mirror properties in the 
> settings.xml for the whole teams global settings. We also have a defined a 
> number of repositories in our work profile so we can mirror these to 
> different repo's managed by Archiva. Now when I work from home I have to 
> comment out the mirror definitions and activate a home profile which does not 
> define any repos so Maven just goes out to the WWW as normal. So the pain is 
> having to comment out and un-comment the mirror settings every time I go from 
> work to home and visa-versa.
> Can we not have the option to add mirrors inside profiles?  



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] [Created] (MJAVADOC-468) Please provide an example for the userproperty groups

2016-07-13 Thread Oliver B. Fischer (JIRA) 
Oliver B. Fischer created MJAVADOC-468:
--

 Summary: Please provide an example for the userproperty groups
 Key: MJAVADOC-468
 URL: https://issues.apache.org/jira/browse/MJAVADOC-468
 Project: Maven Javadoc Plugin
  Issue Type: Documentation
  Components: javadoc
Affects Versions: 2.10.3
Reporter: Oliver B. Fischer
Priority: Minor


Groups can by configured via the {{group}} element of the configuration and via 
the userproperty {{groups}}.

Please provide an example how to use this property with one and multiple groups.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] (MNG-4505) use slf4j to control various logging frameworks

2012-04-03 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=295657#comment-295657
 ] 

Oliver B. Fischer commented on MNG-4505:


Would be really nice to be able to control the logging messages of third party 
components used in Maven plugins.

> use slf4j to control various logging frameworks
> ---
>
> Key: MNG-4505
> URL: https://jira.codehaus.org/browse/MNG-4505
> Project: Maven 2 & 3
>  Issue Type: Improvement
>  Components: Logging
>Reporter: Brett Porter
> Fix For: Issues to be reviewed for 3.x
>
>
> In MNG-1725, Jason indicated this was the plan for Maven 3.x. I didn't see an 
> existing issue and from what I can tell it hasn't been implemented yet, so 
> creating an issue to track it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MNG-5743) Add support for splitted POMs

2014-12-25 Thread Oliver B. Fischer (JIRA) 
Oliver B. Fischer created MNG-5743:
--

 Summary: Add support for splitted POMs
 Key: MNG-5743
 URL: https://jira.codehaus.org/browse/MNG-5743
 Project: Maven
  Issue Type: Improvement
  Components: Design, Patterns & Best Practices
Affects Versions: Issues to be reviewed for 4.x
Reporter: Oliver B. Fischer


Please add the possibility to split a POM into multiple files. A huge POM is 
difficult to maintain and it is also difficult to navigate through a huge POM. 

So it would be nice to have the possibility to split a POM into multiple files.

This could be achived by adding an {{include}} directive or by supporting 
configuration directory as suggested in [Optional support for splitting up 
pom.xml in multiple files|http://docs.codehaus.org/x/BgSV].

Adding this feature would be help to promoted Maven in new projects. Futhermore 
it would be helpful for all maintaining large Maven based projects.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5743) Add support for splitted POMs

2014-12-26 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359721#comment-359721
 ] 

Oliver B. Fischer commented on MNG-5743:


I am not agains mixins but for 95% of the problems huge POMs causes it would be 
enough to store dependency problems in one file, profiles in different files 
and so one. This is a simple, easy to understand and to implement way to help 
us. I agree with you if you refuse to add the ability to spread the same 
section across multiple files.

> Add support for splitted POMs
> -
>
> Key: MNG-5743
> URL: https://jira.codehaus.org/browse/MNG-5743
> Project: Maven
>  Issue Type: Improvement
>  Components: Design, Patterns & Best Practices
>Affects Versions: Issues to be reviewed for 4.x
>Reporter: Oliver B. Fischer
>
> Please add the possibility to split a POM into multiple files. A huge POM is 
> difficult to maintain and it is also difficult to navigate through a huge 
> POM. 
> So it would be nice to have the possibility to split a POM into multiple 
> files.
> This could be achived by adding an {{include}} directive or by supporting 
> configuration directory as suggested in [Optional support for splitting up 
> pom.xml in multiple files|http://docs.codehaus.org/x/BgSV].
> Adding this feature would be help to promoted Maven in new projects. 
> Futhermore it would be helpful for all maintaining large Maven based projects.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5743) Add support for splitted POMs

2015-01-01 Thread Oliver B. Fischer (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360511#comment-360511
 ] 

Oliver B. Fischer commented on MNG-5743:


My request is very similar to MNG-5102. MNG-5102 addresses a more advanced use 
cases but for 95% of all projects dealing with huge POMs the possibility to 
split a POM in multiple disjunct subparts.

Can you give me some arguments why this wouldn't be helpfull?

> Add support for splitted POMs
> -
>
> Key: MNG-5743
> URL: https://jira.codehaus.org/browse/MNG-5743
> Project: Maven
>  Issue Type: Improvement
>  Components: Design, Patterns & Best Practices
>Affects Versions: Issues to be reviewed for 4.x
>Reporter: Oliver B. Fischer
>
> Please add the possibility to split a POM into multiple files. A huge POM is 
> difficult to maintain and it is also difficult to navigate through a huge 
> POM. 
> So it would be nice to have the possibility to split a POM into multiple 
> files.
> This could be achived by adding an {{include}} directive or by supporting 
> configuration directory as suggested in [Optional support for splitting up 
> pom.xml in multiple files|http://docs.codehaus.org/x/BgSV].
> Adding this feature would be help to promoted Maven in new projects. 
> Futhermore it would be helpful for all maintaining large Maven based projects.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)