[ANN] Maven Project Info Reports Plugin 3.7.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.7.0.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.7.0



Release Notes - Maven Project Info Reports Plugin - Version 3.7.0

** Dependency upgrade
* [MPIR-454] - Upgrade to Doxia 2.0.0 Milestone Stack
* [MPIR-467] - Upgrade to Parent 43


NOTE: Read the details on this release here: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.6.2 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.6.2.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.6.2



Release Notes - Maven Project Info Reports Plugin - Version 3.6.2

** Bug
* [MPIR-466] - ModulesReport/IndexReport do not pass a complete 
building request to renderer



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.6.1 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.6.1.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.6.1



Release Notes - Maven Project Info Reports Plugin - Version 3.6.1

** Bug
* [MPIR-462] - [REGRESSION] NFEx: For input string: "1.8" in 
project w/ MR dependency


** Task
* [MPIR-463] - Remove workaround to count the number of root 
content entries in JAR files


** Dependency upgrade
* [MPIR-464] - Upgrade to Maven Shared JAR 3.1.1


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.6.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.6.0.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.6.0



Release Notes - Maven Project Info Reports Plugin - Version 3.6.0

** New Feature
* [MPIR-455] - dependencies goal: add support for multi-release JARs

** Improvement
* [MPIR-451] - Rename "Dependency Information" to "Maven Coordinates"
* [MPIR-460] - Dependency Information for maven-plugin

** Task
* [MPIR-459] - Refresh download page

** Dependency upgrade
* [MPIR-457] - Upgrade to Parent 42 and Maven 3.6.3
* [MPIR-461] - Upgrade plugins and components (in ITs)


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Excluding artifact from project-info-reports dependency report

[Mark Eggers]

I'll have to think about how this works and the ramifications. Off the 
top of my head, I'm not sure how packaging the artifact as a JAR would help.


We make use of overlays, and then override the content in the project 
that depends on the WAR by utilizing Maven's WAR overlays. Basically, 
the first WAR component wins. The downstream project may override the 
dependency simply by having a file with the same name in the same web 
application location.


I might be able to use the dependency plugin and unpack the JAR contents 
in the correct place (and order). I'll think about that.


What I was hoping for is something like the following:



 dependencies
 dependencies
  
   
  
   arifactId


    
. . . . other reports . . . .


However, that doesn't seem to be available.

Of course, then you wouldn't be able to tell of that WAR dependency had 
updates. Hmm.


Thanks for replying.

Mark
/mde/

On 12/19/2023 3:32 AM, Nils Breunese wrote:

Can’t these resources be packaged in plain JARs and added as a regular 
dependency to the applications that require them, instead of using WAR overlays?

Nils.


Op 19 dec 2023, om 06:53 heeft Mark Eggers  het 
volgende geschreven:

I have several artifacts that consist of WAR archives with no server component.

In other words, there are only HTML, CSS, JS, JSP, images, fonts, etc.files in 
these artifacts. There are no servlets, listeners, POJOs, resources, etc. in 
these artifacts.

These artifacts are used as overlays in other projects to keep common 
components managed.

When a dependency report is run using these artifacts, there is an error along 
the lines of:

[ERROR] Artifact groupId:artifactId:war:version caused IOException:

[FILE_LOCATION]/classes  (The system cannot find the file specified)

-- stack trace --

Well this is obvious, since the WAR artifacts used as an overlay have no 
WEB-INF/classes directories.

Is there a way to exclude these artifacts  from dependency checking for 
projects that consume them? Or do I just live with the error messages in 
site:site (the site builds correctly).

I'm using maven-project-info-reports-plugin 3.5.0 with a variety of Maven 
versions (3.6.3, 3.9.6), and a variety of JDKs (8, 11, 17).

Any ideas would be greatly appreciated.

Thanks in advance,

Mark
/mde/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Excluding artifact from project-info-reports dependency report

[Nils Breunese]

Can’t these resources be packaged in plain JARs and added as a regular 
dependency to the applications that require them, instead of using WAR overlays?

Nils.

> Op 19 dec 2023, om 06:53 heeft Mark Eggers  
> het volgende geschreven:
> 
> I have several artifacts that consist of WAR archives with no server 
> component.
> 
> In other words, there are only HTML, CSS, JS, JSP, images, fonts, etc.files 
> in these artifacts. There are no servlets, listeners, POJOs, resources, etc. 
> in these artifacts.
> 
> These artifacts are used as overlays in other projects to keep common 
> components managed.
> 
> When a dependency report is run using these artifacts, there is an error 
> along the lines of:
> 
> [ERROR] Artifact groupId:artifactId:war:version caused IOException:
> 
> [FILE_LOCATION]/classes  (The system cannot find the file specified)
> 
> -- stack trace --
> 
> Well this is obvious, since the WAR artifacts used as an overlay have no 
> WEB-INF/classes directories.
> 
> Is there a way to exclude these artifacts  from dependency checking for 
> projects that consume them? Or do I just live with the error messages in 
> site:site (the site builds correctly).
> 
> I'm using maven-project-info-reports-plugin 3.5.0 with a variety of Maven 
> versions (3.6.3, 3.9.6), and a variety of JDKs (8, 11, 17).
> 
> Any ideas would be greatly appreciated.
> 
> Thanks in advance,
> 
> Mark
> /mde/
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Excluding artifact from project-info-reports dependency report

[Mark Eggers]

I have several artifacts that consist of WAR archives with no server 
component.


In other words, there are only HTML, CSS, JS, JSP, images, fonts, 
etc.files in these artifacts. There are no servlets, listeners, POJOs, 
resources, etc. in these artifacts.


These artifacts are used as overlays in other projects to keep common 
components managed.


When a dependency report is run using these artifacts, there is an error 
along the lines of:


[ERROR] Artifact groupId:artifactId:war:version caused IOException:

[FILE_LOCATION]/classes  (The system cannot find the file specified)

-- stack trace --

Well this is obvious, since the WAR artifacts used as an overlay have no 
WEB-INF/classes directories.


Is there a way to exclude these artifacts  from dependency checking for 
projects that consume them? Or do I just live with the error messages in 
site:site (the site builds correctly).


I'm using maven-project-info-reports-plugin 3.5.0 with a variety of 
Maven versions (3.6.3, 3.9.6), and a variety of JDKs (8, 11, 17).


Any ideas would be greatly appreciated.

Thanks in advance,

Mark
/mde/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.5.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.5.0.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.5.0



Release Notes - Maven Project Info Reports Plugin - Version 3.5.0

** Task
* [MPIR-453] - Replace Commons IO in favor of standard APIs

** Dependency upgrade
* [MPIR-446] - Update to Maven SCM 2.0.1
* [MPIR-452] - Upgrade to Parent 41


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.4.5 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.4.5.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.4.5



Release Notes - Maven Project Info Reports Plugin - Version 3.4.5

** Bug
* [MPIR-441] - Fix DependenciesReportTest
* [MPIR-448] - [REGRESSION] DependenciesRenderer chokes on invalid 
scope with a NPE


** Improvement
* [MPIR-447] - Gradle deprecates compile in favor of implementation
* [MPIR-449] - Don't count and display debug information if 
dependency does not contain class files



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.4.3 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.4.3.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.4.3



Release Notes - Maven Project Info Reports Plugin - Version 3.4.3

** Bug
* [MPIR-429] - avoid warning on "Unknown packaging: bundle"

** Dependency upgrade
* [MPIR-432] - Upgrade parent pom to 39
* [MPIR-433] - Bump bcel from 6.5.0 to 6.6.0


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.4.2 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.4.2.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.4.2



Release Notes - Maven Project Info Reports Plugin - Version 3.4.2

** Bug
* [MPIR-425] - Verbatim content should be rendered as plain text

** Task
* [MPIR-426] - Remove Apache Buildr from Dependency Information Report
* [MPIR-427] - Explicitly start and end tables with Doxia Sinks in 
report renderers



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Surefire plain text reports

[Elliotte Rusty Harold]

Please don't. I totally use that and expect them to be there without
any extra markup or systems. Plain text, FTW.

On Fri, Nov 18, 2022 at 8:23 AM Slawomir Jaranowski
 wrote:
>
> Hi,
>
> By default Surefire generate plain text reports which is stored in
> target/surefire-reports/yourTestName.txt
>
> It can be disabled by using the "useFile" parameter.
>
> Question - Does somebody use such reports?
> I'm thinking about removing those at all and saving some CO2 :-)
>
> What do you think?
>
> --
> Sławomir Jaranowski



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Surefire plain text reports

[Romain Manni-Bucau]

Le ven. 18 nov. 2022 à 09:39, Slawomir Jaranowski 
a écrit :

> pt., 18 lis 2022 o 09:24 Romain Manni-Bucau 
> napisał(a):
>
> > +1 to switch it off by default (but keep the feature since it can help
> > investigations on CI)
> >
>
>
> Text reports contain exactly the same information that is displayed during
> build on console, so you should have it in logs from CI.
> Additionally xml reports also have it.
>
> Do you really use it on your CI?
>

Yes the stdxxx output is disabled and text file enabled when a failure is
hard to analyse.


>
>
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le ven. 18 nov. 2022 à 09:23, Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> > a écrit :
> >
> > > Hi,
> > >
> > > By default Surefire generate plain text reports which is stored in
> > > target/surefire-reports/yourTestName.txt
> > >
> > > It can be disabled by using the "useFile" parameter.
> > >
> > > Question - Does somebody use such reports?
> > > I'm thinking about removing those at all and saving some CO2 :-)
> > >
> > > What do you think?
> > >
> > > --
> > > Sławomir Jaranowski
> > >
> >
>
>
> --
> Sławomir Jaranowski
>

Re: Surefire plain text reports

[Slawomir Jaranowski]

pt., 18 lis 2022 o 09:24 Romain Manni-Bucau 
napisał(a):

> +1 to switch it off by default (but keep the feature since it can help
> investigations on CI)
>


Text reports contain exactly the same information that is displayed during
build on console, so you should have it in logs from CI.
Additionally xml reports also have it.

Do you really use it on your CI?


>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le ven. 18 nov. 2022 à 09:23, Slawomir Jaranowski 
> a écrit :
>
> > Hi,
> >
> > By default Surefire generate plain text reports which is stored in
> > target/surefire-reports/yourTestName.txt
> >
> > It can be disabled by using the "useFile" parameter.
> >
> > Question - Does somebody use such reports?
> > I'm thinking about removing those at all and saving some CO2 :-)
> >
> > What do you think?
> >
> > --
> > Sławomir Jaranowski
> >
>


-- 
Sławomir Jaranowski

Re: Surefire plain text reports

[Mantas Gridinas]

I doubt anyone will update the surefire plugin in their existing projects
regardless.

On Fri, Nov 18, 2022, 10:23 Slawomir Jaranowski 
wrote:

> Hi,
>
> By default Surefire generate plain text reports which is stored in
> target/surefire-reports/yourTestName.txt
>
> It can be disabled by using the "useFile" parameter.
>
> Question - Does somebody use such reports?
> I'm thinking about removing those at all and saving some CO2 :-)
>
> What do you think?
>
> --
> Sławomir Jaranowski
>

Re: Surefire plain text reports

[Romain Manni-Bucau]

+1 to switch it off by default (but keep the feature since it can help
investigations on CI)

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le ven. 18 nov. 2022 à 09:23, Slawomir Jaranowski 
a écrit :

> Hi,
>
> By default Surefire generate plain text reports which is stored in
> target/surefire-reports/yourTestName.txt
>
> It can be disabled by using the "useFile" parameter.
>
> Question - Does somebody use such reports?
> I'm thinking about removing those at all and saving some CO2 :-)
>
> What do you think?
>
> --
> Sławomir Jaranowski
>

Surefire plain text reports

[Slawomir Jaranowski]

Hi,

By default Surefire generate plain text reports which is stored in
target/surefire-reports/yourTestName.txt

It can be disabled by using the "useFile" parameter.

Question - Does somebody use such reports?
I'm thinking about removing those at all and saving some CO2 :-)

What do you think?

-- 
Sławomir Jaranowski

[ANN] Maven Project Info Reports Plugin 3.4.1 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.4.1.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.4.1



Release Notes - Maven Project Info Reports Plugin - Version 3.4.1

** Bug
* [MPIR-423] - dependencies goal doesn't create required resources

** Dependency upgrade
* [MPIR-424] - Upgrade Maven Reporting API to 3.1.1/Maven Reporting 
Impl to 3.2.0



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.3.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.3.0.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.3.0



Release Notes - Maven Project Info Reports Plugin - Version 3.3.0

** Bug
* [MPIR-415] - Wrong old goal name in "Incompatibility Notice" 
table in website


** Dependency upgrade
* [MPIR-399] - Upgrade to Maven 3.2.5
* [MPIR-416] - Upgrade maven-dependency-tree to 3.1.0
* [MPIR-417] - Upgrade Parent to 36


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.2.2 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.2.2.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.2.2



Release Notes - Maven Project Info Reports Plugin - Version 3.2.2

** Bug
* [MPIR-413] - Plugin repositories defined in project are not used 
by plugin-management report


** Dependency upgrade
* [MPIR-414] - Upgrade Maven Reporting API/Impl to 3.1.0


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.2.1 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.2.1.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.2.1



Release Notes - Maven Project Info Reports Plugin - Version 3.2.1

** Bug
* [MPIR-403] - Travis link should point to travis-ci.com instead of 
travis-ci.org

* [MPIR-404] - Warn and accept invalid mailing list links
* [MPIR-405] - Regression in Maven site rendering due to Doxia 
change to HTML5
* [MPIR-412] - Dependency report generates non-well-formed output 
if the POM of a depdendency cannot be parsed


** Improvement
* [MPIR-408] - Add some i18n properties for zh_CH

** Dependency upgrade
* [MPIR-409] - Upgrade Maven Site Plugin to 3.10.0
* [MPIR-410] - Upgrade Maven SCM to 1.12.2
* [MPIR-411] - Upgrade Doxia to 1.11.1 and Doxia Sitetools to 1.11.1


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.1.2 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.1.2.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.1.2



Release Notes - Maven Project Info Reports Plugin - Version 3.1.2

** New Feature
* [MPIR-395] - Add TeamCity as a possibility for ciManagement entry

** Improvement
* [MPIR-391] - Continuous Integration support for GitHub Actions
* [MPIR-401] - Mailing list subscribe and unsubscribe links


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 3.1.1 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.1.1.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.1.1



Release Notes - Maven Project Info Reports Plugin - Version 3.1.1

** Bug
* [MPIR-374] - Unknown packaging: bundle when creating report
* [MPIR-398] - Nonsense links created for mailing lists when mailto 
is empty


** Improvement
* [MPIR-393] - MailiingListReport.getArchiveServer is weird
* [MPIR-394] - Link for Jenkins introduction should be updated to 
jenkins.io



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Maven Project Info Reports Plugin 3.1.0 released

[Michael Osipov]

Am 2020-05-27 um 10:44 schrieb Michael Osipov:

Am 2020-05-27 um 03:44 schrieb Maxim Solodovnik:

Hello,

for whatever reason this plugin is missing in central
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/ 


Waiting for https://jira.apache.org/jira/browse/INFRA-20332

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Maven Project Info Reports Plugin 3.1.0 released

[Maxim Solodovnik]

Thanks :))

On Wed, 27 May 2020 at 15:44, Michael Osipov  wrote:

> Am 2020-05-27 um 03:44 schrieb Maxim Solodovnik:
> > Hello,
> >
> > for whatever reason this plugin is missing in central
> >
> https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/
> > Can you please check?
>
> Good question, I have released the staging repo 10 hours ago. I will get
> in touch with INFRA and MVNCENTRAL.
>
> > On Wed, 27 May 2020 at 04:24, Michael Osipov 
> wrote:
> >
> >> The Apache Maven team is pleased to announce the release of the Maven
> >> Project Info Reports Plugin version 3.1.0.
> >>
> >> https://maven.apache.org/plugins/maven-project-info-reports-plugin/
> >>
> >> You should specify the version in your project's plugin configuration:
> >>
> >> 
> >>     org.apache.maven.plugins
> >> maven-project-info-reports-plugin
> >> 3.1.0
> >> 
> >>
> >>
> >> Release Notes - Maven Project Info Reports Plugin - Version 3.1.0
> >>
> >> ** Bug
> >>   * [MPIR-373] - Upgrade from 2.9 to 3.0.0 introduces additional
> warning
> >>   * [MPIR-374] - Unknown packaging: bundle when creating report
> >>   * [MPIR-376] - LightweightHttpsWagon is always used
> >>   * [MPIR-380] - Emails in developers section of pom are improperly
> >> handled
> >>   * [MPIR-385] - Emails in mailing list section of pom are
> improperly
> >> handled
> >>   * [MPIR-386] - Project building errors with plugins and central
> >> repository override
> >>
> >> ** New Feature
> >>   * [MPIR-375] - add plugin excludes feature for plugin-management
> >> report
> >>
> >> ** Improvement
> >>   * [MPIR-381] - Improve russian localization
> >>   * [MPIR-384] - Use PatternExcludesArtifactFilter to exclude
> >> artifacts in PluginManagement
> >>   * [MPIR-387] - make build Reproducible
> >>   * [MPIR-390] - Verify build by Github action
> >>
> >> ** Dependency upgrade
> >>   * [MPIR-388] - upgrade Doxia Sitetools to 1.9.2 to remove
> >> dependency on Struts
> >>   * [MPIR-389] - Upgrade Doxia to 1.9.1
> >>
> >>
> >> Enjoy,
> >>
> >> -The Apache Maven team
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
>

-- 
Best regards,
Maxim

Re: [ANN] Maven Project Info Reports Plugin 3.1.0 released

[Michael Osipov]

Am 2020-05-27 um 03:44 schrieb Maxim Solodovnik:

Hello,

for whatever reason this plugin is missing in central
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/
Can you please check?


Good question, I have released the staging repo 10 hours ago. I will get 
in touch with INFRA and MVNCENTRAL.



On Wed, 27 May 2020 at 04:24, Michael Osipov  wrote:


The Apache Maven team is pleased to announce the release of the Maven
Project Info Reports Plugin version 3.1.0.

https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


org.apache.maven.plugins
maven-project-info-reports-plugin
3.1.0



Release Notes - Maven Project Info Reports Plugin - Version 3.1.0

** Bug
  * [MPIR-373] - Upgrade from 2.9 to 3.0.0 introduces additional warning
  * [MPIR-374] - Unknown packaging: bundle when creating report
  * [MPIR-376] - LightweightHttpsWagon is always used
  * [MPIR-380] - Emails in developers section of pom are improperly
handled
  * [MPIR-385] - Emails in mailing list section of pom are improperly
handled
  * [MPIR-386] - Project building errors with plugins and central
repository override

** New Feature
  * [MPIR-375] - add plugin excludes feature for plugin-management
report

** Improvement
  * [MPIR-381] - Improve russian localization
  * [MPIR-384] - Use PatternExcludesArtifactFilter to exclude
artifacts in PluginManagement
  * [MPIR-387] - make build Reproducible
  * [MPIR-390] - Verify build by Github action

** Dependency upgrade
  * [MPIR-388] - upgrade Doxia Sitetools to 1.9.2 to remove
dependency on Struts
  * [MPIR-389] - Upgrade Doxia to 1.9.1


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Maven Project Info Reports Plugin 3.1.0 released

[Maxim Solodovnik]

Hello,

for whatever reason this plugin is missing in central
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/
Can you please check?

On Wed, 27 May 2020 at 04:24, Michael Osipov  wrote:

> The Apache Maven team is pleased to announce the release of the Maven
> Project Info Reports Plugin version 3.1.0.
>
> https://maven.apache.org/plugins/maven-project-info-reports-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>org.apache.maven.plugins
>maven-project-info-reports-plugin
>3.1.0
> 
>
>
> Release Notes - Maven Project Info Reports Plugin - Version 3.1.0
>
> ** Bug
>  * [MPIR-373] - Upgrade from 2.9 to 3.0.0 introduces additional warning
>  * [MPIR-374] - Unknown packaging: bundle when creating report
>  * [MPIR-376] - LightweightHttpsWagon is always used
>  * [MPIR-380] - Emails in developers section of pom are improperly
> handled
>  * [MPIR-385] - Emails in mailing list section of pom are improperly
> handled
>  * [MPIR-386] - Project building errors with plugins and central
> repository override
>
> ** New Feature
>  * [MPIR-375] - add plugin excludes feature for plugin-management
> report
>
> ** Improvement
>  * [MPIR-381] - Improve russian localization
>  * [MPIR-384] - Use PatternExcludesArtifactFilter to exclude
> artifacts in PluginManagement
>  * [MPIR-387] - make build Reproducible
>  * [MPIR-390] - Verify build by Github action
>
> ** Dependency upgrade
>  * [MPIR-388] - upgrade Doxia Sitetools to 1.9.2 to remove
> dependency on Struts
>  * [MPIR-389] - Upgrade Doxia to 1.9.1
>
>
> Enjoy,
>
> -The Apache Maven team
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Best regards,
Maxim

[ANN] Maven Project Info Reports Plugin 3.1.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.1.0.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.1.0



Release Notes - Maven Project Info Reports Plugin - Version 3.1.0

** Bug
* [MPIR-373] - Upgrade from 2.9 to 3.0.0 introduces additional warning
* [MPIR-374] - Unknown packaging: bundle when creating report
* [MPIR-376] - LightweightHttpsWagon is always used
* [MPIR-380] - Emails in developers section of pom are improperly 
handled
* [MPIR-385] - Emails in mailing list section of pom are improperly 
handled
* [MPIR-386] - Project building errors with plugins and central 
repository override


** New Feature
* [MPIR-375] - add plugin excludes feature for plugin-management report

** Improvement
* [MPIR-381] - Improve russian localization
* [MPIR-384] - Use PatternExcludesArtifactFilter to exclude 
artifacts in PluginManagement

* [MPIR-387] - make build Reproducible
* [MPIR-390] - Verify build by Github action

** Dependency upgrade
* [MPIR-388] - upgrade Doxia Sitetools to 1.9.2 to remove 
dependency on Struts

* [MPIR-389] - Upgrade Doxia to 1.9.1


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

GPG plugin reports "No secret key": version 1.5/1.6 - Windows 10 64-bit - gpg (GnuPG) 2.2.20-unknown

[Qingtian Wang]

Hi,

I am very new to gpg and the maven plugin for it. I followed the
instructions here:

https://maven.apache.org/plugins/maven-gpg-plugin/usage.html

and numerous other places online. I always get the following error when
running "mvn deploy" or "mvn verify". I googled and found the version 2.2
of GPG changed how "secring.gpg" is stored. They now combined both
public and secret key rings into the one file called "pubring.kbx". As a
matter of fact, if I type "gpg --list-secret-keys" in CLI, I got
nothing/blank in return. Is the 1.5/1.6 version of the maven-gpg-plugin not
working with 2.2 version of the GPG executable because of the change?

Again I have tried all kinds of instructions in addition to the official
maven plugin doc (e.g. Sonatype.org), and always get the same error below.
Can you please help?

Thanks!

===

[INFO] --- maven-gpg-plugin:1.6:sign (sign-artifacts) @ mavenproject1 ---
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  1.390 s
[INFO] Finished at: 2020-04-21T22:16:39-05:00
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-gpg-plugin:1.6:sign (sign-artifacts) on
project mavenproject1: Exit code: 2 -> [Help 1]

Maven Project Info Reports Plugin 3.0.2

[Konrad Windszus]

Hi, 
Unfortunately release 3.0.1 never got published due to a failed vote in August 
last year: 
https://lists.apache.org/list.html?d...@maven.apache.org:lte=12M:%5BVOTE%5D%20Release%20Maven%20Project%20Info%20Reports%20Plugin%20version%203.0.1
 


Still a lot of fixes are resolved in this version: 
https://issues.apache.org/jira/projects/MPIR/versions/12344828 

Any chance to get a 3.0.2 soon?

To me it is not really clear what is missing, because the issue reported in 
https://lists.apache.org/thread.html/c695a357db250df6d4f574661df8efd8cf16f8839f2213cfdc74%40%3Cdev.maven.apache.org%3E
 

 never made it to a JIRA ticket.
Only there is https://issues.apache.org/jira/browse/MPIR-384 
 but it is tagged for 3.1.0, so 
what is missing for a 3.0.2?

Thanks in advance,
Konrad

[ANN] Maven Project Info Reports Plugin 3.0.0 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 3.0.0.


https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.0.0



Release Notes - Maven Project Info Reports Plugin - Version 3.0.0

** Bug
* [MPIR-348] - Usage of HTTP in web site for git-scm.com resources 
cause redirects to HTTPS
* [MPIR-349] - Bad modules links in 'index/modules' reports when 
'distributionManagement.site.url' comes from settings.xml

* [MPIR-359] - Generated links for Mercurial SCM are broken
* [MPIR-362] - Dependency Management report doesn't exclude system 
scoped dependencies
* [MPIR-365] - Failed tests on Java 9 due to error with keytool 
plugin "keytool: not found"
* [MPIR-370] - Upgrade transitive BCEL to 6.2 to avoid 
org.apache.bcel.classfile.ClassFormatException


** Improvement
* [MPIR-352] - Use protocol-agnostic URL for Gravatar
* [MPIR-358] - Add GitHub for issue management
* [MPIR-366] - Drop Maven 2 support

** Task
* [MPIR-323] - Align Mojo class names, goals and output names
* [MPIR-345] - Upgrade to Doxia 1.8
* [MPIR-346] - Upgrade to Doxia Sitetools 1.8.1
* [MPIR-347] - Upgrade to Java 6
* [MPIR-350] - Upgrade of plexus-interpolation to 1.24.
* [MPIR-353] - Upgrade parent to version 30
* [MPIR-354] - Upgrade Maven Site Plugin to version 3.5.1 for ITs
* [MPIR-355] - Upgrade dependencies which are code- and testsafe
* [MPIR-356] - Deprecate not used methods in ProjectInfoReportUtils
* [MPIR-367] - Remove Dependency Repository Locations from 
dependency report

* [MPIR-368] - Upgrade to Java 7
* [MPIR-369] - Drop Commons Lang for System builtins
* [MPIR-372] - Remove fields duplicating parent class members

** Dependency upgrade
* [MPIR-361] - Upgrade parent to 31
* [MPIR-363] - Upgrade dependencies to latest versions


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 2.9 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin version 2.9.


This module generates browsable HTML pages from Java source code.

https://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  2.9



Release Notes - Maven Project Info Reports Plugin - Version 2.9

** Sub-task
* [MPIR-341] - Align mojo class names to element names in pom.xml
* [MPIR-342] - Document upcoming mojo and file names change in 3.0

** Bug
* [MPIR-251] - Artifact ## has no file error regression
* [MPIR-268] - Add Gradle dependency information
* [MPIR-308] - Plugin fails with Java 8 (caused by BCEL)

** Improvement
* [MPIR-340] - Omit legend and dependency details in Dependency 
Convergence if there is 100 % convergence


** Task
* [MPIR-336] - Upgrade to Maven Shared JAR 1.2
* [MPIR-337] - Localize sealed information on JARs
* [MPIR-338] - Localize alternative text for used icons
* [MPIR-339] - Align/pluralize name of 
project-info-report.properties and all of its usages



Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Upcoming Maven Project Info Reports release

[Michael Osipov]

Hi folks,

I intend to roll 2.9 this week. There are still a few long-standing 
issues. If anyone wants to make some progress, feel free to do so. If I 
don't hear anything, I'll start on Wed/Thu.


Michael

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Combining surefire reports?

[Jeff]

I'm using maven w/ TestNG to build integration tests.  I have a few tests
that must be run alone because they muck with the service settings and
database.

However, I'd like to combine the results of all the tests run together
after they have been completed.

Is this possible?

Thanks!!

-- 
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

[ANN] Apache Maven Project Info Reports Plugin 2.8.1 Released

[Hervé Boutemy]

The Maven team is pleased to announce the release of the Apache Maven Project 
Info Reports Plugin, version 2.8.1

The Maven Project Info Reports Plugin is a plugin that generates standard 
reports
for the specified project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  2.8.1



Release Notes - Apache Maven Project Info Reports Plugin - Version 2.8.1

Bug
* [MPIR-300] Reporting plugins are reported with wrong version if version 
specified via pluginManagement

Improvement
* [MPIR-329] French translation in project-info-report_fr.properties

Task
* [MPIR-333] switch to Fluido
* [MPIR-332] don't warn when removing path from git scm url


Enjoy,

-The Maven team


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven site : maven-project-info-reports-plugin version warnings and deps behind a proxy

[Brice Vandeputte]

Hi Hervé,
 You right, pluginManagement/plugins solve my warnings.
 And for proxy settings, I'm sorry ; my settings was correctly configured.
So these warnings are expected : repositories listed into the logs as
warnings are moved/closed/deprecated.

thanks ; that's ok now.
regards

2015-08-03 10:31 GMT+02:00 :

> 1. MPIR version
> MPIR is a plugin, with its own version independant from any other plugin,
> even from m-site-p
> Then you need to choose the plugin version like any other version (the
> fact that it is not only a classical plugin but also a reporting plugin
> does not change anything)
> then see pluginManagement/plugins sections
>
> 2. proxy
> see http://maven.apache.org/guides/mini/guide-proxies.html
>
> Regards,
>
> Hervé
>
> - Mail original -
> De: "Brice Vandeputte" 
> À: "Maven Users List" 
> Envoyé: Lundi 3 Août 2015 09:59:26
> Objet: maven site : maven-project-info-reports-plugin version warnings and
> deps behind a proxy
>
> Hi all,
>
>  I would like to generate a site using mvn site
>  I'm behind a proxy at generation time and got the following output from
> the maven site command:
>
>
> *Output 1: MPIR version*
> [INFO] --- maven-site-plugin:3.4:site (default-site) @ myProject ---
> [WARNING] Report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin has an empty
> version.
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> (...)
>
> *Output 2: **MPIR** dependencies*
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:2.8:dependencies
> [WARNING] The repository url 'http://download.oracle.com/maven' is invalid
> - Repository 'oracle.releases' will be blacklisted.
> [WARNING] The repository url 'http://snapshots.repository.codehaus.org' is
> invalid - Repository 'codehaus-snapshots' will be black
> listed.
> [WARNING] The repository url 'http://repository.codehaus.org' is invalid -
> Repository 'codehaus' will be blacklisted.
> [WARNING] The repository url 'http://download.java.net/maven/glassfish' is
> invalid - Repository 'glassfish-repository' will be bla
> cklisted.
> (...)
>
> I've got 2 questions:
> 
> - Output1 *MPIR version*: if "maven-project-info-reports-plugin" is now
> embedded by maven site why should we set explicitely a version for this
> plugin ? how to do that ?
>I tryed to add 2.8 version as maven site sub dependencies, as project
> dependencies directly, and as dependencyManagement/dependencies but that
> doesn't remove these warnings..? maybe maven site pom himself refers to
> this plugin without version ?
>
> - Output 2 *MPIR** dependencies*: I think this warnings is due to a network
> issue. So if this is the case, how to set a proxy for the
> "maven-project-info-reports-plugin" plugin ?
>I send a question on SO for these :
>
> http://stackoverflow.com/questions/31748832/maven-site-plugin-is-not-working-well-behind-a-proxy
>
> Regards
> NB/// thanks @KarlHM for your answer to my previous question (release
> plugin doc)
>
>  Brice
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: maven site : maven-project-info-reports-plugin version warnings and deps behind a proxy

[herve . boutemy]

1. MPIR version
MPIR is a plugin, with its own version independant from any other plugin, even 
from m-site-p
Then you need to choose the plugin version like any other version (the fact 
that it is not only a classical plugin but also a reporting plugin does not 
change anything)
then see pluginManagement/plugins sections

2. proxy
see http://maven.apache.org/guides/mini/guide-proxies.html

Regards,

Hervé

- Mail original -
De: "Brice Vandeputte" 
À: "Maven Users List" 
Envoyé: Lundi 3 Août 2015 09:59:26
Objet: maven site : maven-project-info-reports-plugin version warnings and deps 
behind a proxy

Hi all,

 I would like to generate a site using mvn site
 I'm behind a proxy at generation time and got the following output from
the maven site command:


*Output 1: MPIR version*
[INFO] --- maven-site-plugin:3.4:site (default-site) @ myProject ---
[WARNING] Report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin has an empty
version.
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
(...)

*Output 2: **MPIR** dependencies*
[INFO] Generating "Dependencies" report ---
maven-project-info-reports-plugin:2.8:dependencies
[WARNING] The repository url 'http://download.oracle.com/maven' is invalid
- Repository 'oracle.releases' will be blacklisted.
[WARNING] The repository url 'http://snapshots.repository.codehaus.org' is
invalid - Repository 'codehaus-snapshots' will be black
listed.
[WARNING] The repository url 'http://repository.codehaus.org' is invalid -
Repository 'codehaus' will be blacklisted.
[WARNING] The repository url 'http://download.java.net/maven/glassfish' is
invalid - Repository 'glassfish-repository' will be bla
cklisted.
(...)

I've got 2 questions:

- Output1 *MPIR version*: if "maven-project-info-reports-plugin" is now
embedded by maven site why should we set explicitely a version for this
plugin ? how to do that ?
   I tryed to add 2.8 version as maven site sub dependencies, as project
dependencies directly, and as dependencyManagement/dependencies but that
doesn't remove these warnings..? maybe maven site pom himself refers to
this plugin without version ?

- Output 2 *MPIR** dependencies*: I think this warnings is due to a network
issue. So if this is the case, how to set a proxy for the
"maven-project-info-reports-plugin" plugin ?
   I send a question on SO for these :
http://stackoverflow.com/questions/31748832/maven-site-plugin-is-not-working-well-behind-a-proxy

Regards
NB/// thanks @KarlHM for your answer to my previous question (release
plugin doc)

 Brice

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven site : maven-project-info-reports-plugin version warnings and deps behind a proxy

[Brice Vandeputte]

Hi all,

 I would like to generate a site using mvn site
 I'm behind a proxy at generation time and got the following output from
the maven site command:


*Output 1: MPIR version*
[INFO] --- maven-site-plugin:3.4:site (default-site) @ myProject ---
[WARNING] Report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin has an empty
version.
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
(...)

*Output 2: **MPIR** dependencies*
[INFO] Generating "Dependencies" report ---
maven-project-info-reports-plugin:2.8:dependencies
[WARNING] The repository url 'http://download.oracle.com/maven' is invalid
- Repository 'oracle.releases' will be blacklisted.
[WARNING] The repository url 'http://snapshots.repository.codehaus.org' is
invalid - Repository 'codehaus-snapshots' will be black
listed.
[WARNING] The repository url 'http://repository.codehaus.org' is invalid -
Repository 'codehaus' will be blacklisted.
[WARNING] The repository url 'http://download.java.net/maven/glassfish' is
invalid - Repository 'glassfish-repository' will be bla
cklisted.
(...)

I've got 2 questions:

- Output1 *MPIR version*: if "maven-project-info-reports-plugin" is now
embedded by maven site why should we set explicitely a version for this
plugin ? how to do that ?
   I tryed to add 2.8 version as maven site sub dependencies, as project
dependencies directly, and as dependencyManagement/dependencies but that
doesn't remove these warnings..? maybe maven site pom himself refers to
this plugin without version ?

- Output 2 *MPIR** dependencies*: I think this warnings is due to a network
issue. So if this is the case, how to set a proxy for the
"maven-project-info-reports-plugin" plugin ?
   I send a question on SO for these :
http://stackoverflow.com/questions/31748832/maven-site-plugin-is-not-working-well-behind-a-proxy

Regards
NB/// thanks @KarlHM for your answer to my previous question (release
plugin doc)

 Brice

[ANN] Maven Project Info Reports Plugin 2.8 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Project Info Reports Plugin, version 2.8.


This module generates browsable HTML pages from Java source code.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  >maven-project-info-reports-plugin
  2.8


RRelease Notes - Maven Project Info Reports Plugin - Version 2.8

** Sub-task
* [MPIR-321] - Disable/remove dev/contrib current time generation 
because it is broken



** Bug
* [MPIR-242] - Incorrect translations list for GPL v3 (illegible 
letters for Catalan and Arabic)
* [MPIR-247] - "Comparison method violates its general contract!" 
while generating site
* [MPIR-273] - links to modules broken in modules.html of flat 
multimodule parent project

* [MPIR-279] - Wrong hyperlinks on index and modules page
* [MPIR-280] - Clarify that Web Access SCM link is not suitable for 
SCM checkout

* [MPIR-281] - Misleading SCM report title
* [MPIR-289] - DependenciesRenderer's FileDecimalFormat claims to 
use SI prefixes but calculated numbers do not match
* [MPIR-293] - On the team list report the "picUrl" property 
appears in the table, although no other properties are set for that team 
member
* [MPIR-301] - Update plexus-interpolation to 1.21 to avoid thread 
safety issues

* [MPIR-303] - Backslash in multi-module project
* [MPIR-309] - The Integration test mpir-229 breaks on Apache Jenkins
* [MPIR-311] - Specific SCM intro is missing if dev connection is 
given but not anonymous connection

* [MPIR-313] - License name is mandatory but it is not validated
* [MPIR-319] - Apache Ant has no dependency management but Apache 
Ivy has

* [MPIR-325] - JIRA report is not generated



** Improvement
* [MPIR-263] - improve minimum java requirement when m-compiler-p 
not explicitely configured: use default properties

* [MPIR-265] - Improve debug information in Dependencies report
* [MPIR-287] - Misleading report titles in Project Information overview
* [MPIR-290] - improve git support: remove directory info (after 
'.git') for "git clone"
* [MPIR-291] - if scm tag is present, propose "git clone --branch 
"

* [MPIR-295] - Enhancements on dependency convergence report
* [MPIR-296] - SBT Output not correct for dependencies
* [MPIR-298] - Continuous Integration support for Travis CI
* [MPIR-299] - Update to SCM 1.9.1
* [MPIR-304] - Update dependencies to the most recent usable versions
* [MPIR-305] - Upgrade Doxia + Site Tools to 1.6
* [MPIR-306] - Upgrade to maven-plugins version 25 to 26
* [MPIR-310] - Improve 'JDK Rev' label in dependencies report
* [MPIR-314] - Upgrade to maven-plugins version 26 to 27
* [MPIR-315] - Replace org.apache.maven.shared:maven-doxia-tools 
with org.apache.maven.doxia:doxia-integration-tools
* [MPIR-316] - Removed dependency 
org.codehaus.plexus:plexus-container-default:1.0-alpha-9
* [MPIR-322] - Dependencies Files Details should reuse installed 
jars instead of target/classes
* [MPIR-326] - Remove notes to ancient version of this plugin or 
the Site Plugin in the apt files


** New Feature
* [MPIR-288] - Add a skipEmptyReport option
* [MPIR-297] - add a skip parameter


** Task
* [MPIR-317] - Remove FAQ entry for Recaptcha Mailhide
* [MPIR-318] - Link time zone FAQ entry to the POM reference 
documentation

* [MPIR-324] - Clean up unused and used undeclared dependencies


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

excluding module from project reports

[McCormick, Jeremy I.]

Hello,

I have a question regarding the site generation. 

I see that 'project-info-reports:modules' generates the list of modules that 
goes on the front page of my site.  This works mostly fine.

However, it is including in the list of modules one in which the execution of 
the site plugin was skipped (intentionally because I don't want it included on 
the site).

But the module in question still shows up in the list of modules as a dead link.

How can I make it so that this module without a site is not included in the 
list of modules generated by the modules goal?

Thanks.

--Jeremy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

What is the minimum required config for the Maven Cobertura plugin to instrument, run, and generate xml and html reports?

[KARR, DAVID]

I have a working configuration that runs unit tests with Cobertura using Maven. 
 I've always been a little mystified by Maven phases and how various plugins 
integrate with it (and I've read the user guide).

I'd like to understand the minimum required configuration to get Cobertura 
automatically running along with my unit tests, and generating both the XML and 
HTML outputs.  Answering this might require understanding what the Cobertura 
plugin goals do, but perhaps this is more of a Maven question.  I don't know.

For a long time, I had the following in the "executions" section:
---


prepare
prepare-package

clean
check



package
package

cobertura



---

This works, but I've always been unclear on exactly what is "required" and what 
is just fluff.  By "works", I mean that I see it instrument code, then run 
tests, and apparently generating output, because I find new versions of the XML 
and HTML reports after it completes.

Today I tried simplifying this to just the following:
-



clean
check
cobertura



-

This also seems to work perfectly fine.  I just don't know if there's really 
any difference, or not.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: javadoc:aggregate reports missing packages

[Christian.Pontesegger]

> From: Martin Gainty
> [ERROR] ^MG>Wild guess you are using eclipse 3.7.0 for your IDE in which
> case you want
> to

>MG>http://mirrors.ibiblio.org/pub/mirrors/maven/eclipse/jars/eclipse-
> workbench-2.1.0.jar
> MG>onto your classpath

I am using eclipse kepler. One of my poms on the aggregator contains a
target platform containing the needed kepler packages. Build works fine, I
guess due to tycho resolving all the classpaths correctly. Now I am looking
for something similar for Javadoc creation.

-- 
Christian


smime.p7s
Description: S/MIME cryptographic signature

RE: javadoc:aggregate reports missing packages

[Martin Gainty]

 
From: christian.ponteseg...@infineon.com
To: users@maven.apache.org
Subject: javadoc:aggregate reports missing packages
Date: Mon, 26 May 2014 09:50:05 +






javadoc:aggregate reports missing packages




Hi,

I am trying to build an API documentation for some eclipse plugins. Therefore 
I’d like to run the Javadoc:aggregate goal

My configuration therefore is trivial:









maven-javadoc-plugin

2.9.1




help/api

api











Now maven fails as it cannot resolve lots of eclipse dependencies like:



[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:aggregate (default-cli) on 
project com.infineon.commontools.releng.jenkins: An error has occurred in 
JavaDocs report generation:

[ERROR] Exit code: 1 - 
C:\Userdata\Workspaces\SysBox\ebt_common\bundles\com.infineon.tools\src\com\infineon\tools\AbstractActivator.java:24:
 error: package org.eclipse.ui does not exist

[ERROR] import org.eclipse.ui.IMemento;

[ERROR] ^MG>Wild guess you are using eclipse 3.7.0 for your IDE in which case 
you want 
toMG>http://mirrors.ibiblio.org/pub/mirrors/maven/eclipse/jars/eclipse-workbench-2.1.0.jar
MG>onto your classpath



I get other errors for libs, where I only have a binary OSGI bundle available 
(which is part of the aggregator pom)

[ERROR] symbol:   class CoreException

[ERROR] location: class StringTools

[ERROR] 
C:\Userdata\Workspaces\SysBox\ebt_common\bundles\com.infineon.tools\src\com\infineon\tools\hexparser\antlr\HexStringBaseListener.java:4:
 error: package org.antlr.v4.runtime does not exist

[ERROR] import org.antlr.v4.runtime.ParserRuleContext;

[ERROR] ^MG>put one of the antlr4-runtime jars on your 
classpathMG>http://mvnrepository.com/artifact/org.antlr/antlr4-runtime



Generally I am happy with the created JavaDoc files. Is there a way to tell 
Javadoc to ignore missing dependencies or to tell maven not to fail here?

I know there are lots of similar questions asked out there, but I could not 
find a solution to my problem

Thanks

Christian

MG>You're welcome
MG>Martin

  

javadoc:aggregate reports missing packages

[Christian.Pontesegger]

Hi,

I am trying to build an API documentation for some eclipse plugins.
Therefore I'd like to run the Javadoc:aggregate goal

My configuration therefore is trivial:





maven-javadoc-plugin
2.9.1


help/api
api





Now maven fails as it cannot resolve lots of eclipse dependencies like:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:aggregate (default-cli)
on project com.infineon.commontools.releng.jenkins: An error has occurred in
JavaDocs report generation:
[ERROR] Exit code: 1 -
C:\Userdata\Workspaces\SysBox\ebt_common\bundles\com.infineon.tools\src\com\
infineon\tools\AbstractActivator.java:24: error: package org.eclipse.ui does
not exist
[ERROR] import org.eclipse.ui.IMemento;
[ERROR] ^

I get other errors for libs, where I only have a binary OSGI bundle
available (which is part of the aggregator pom)

[ERROR] symbol:   class CoreException
[ERROR] location: class StringTools
[ERROR]
C:\Userdata\Workspaces\SysBox\ebt_common\bundles\com.infineon.tools\src\com\
infineon\tools\hexparser\antlr\HexStringBaseListener.java:4: error: package
org.antlr.v4.runtime does not exist
[ERROR] import org.antlr.v4.runtime.ParserRuleContext;
[ERROR] ^


Generally I am happy with the created JavaDoc files. Is there a way to tell
Javadoc to ignore missing dependencies or to tell maven not to fail here?
I know there are lots of similar questions asked out there, but I could not
find a solution to my problem

Thanks
Christian




smime.p7s
Description: S/MIME cryptographic signature

Re: What packaging for Jira excel reports with maven?

[Steinar Bang]

> Anders Hammar :

> I categorize different usage of Maven into two categories:
> A) As a build tool
> B) As a utility tool
[snip!]
> My point here is that if you're in category A then Maven is absolutely
> appropriate. At least if you're building everything else with
> Maven. But if you're in category B, then Maven is just one of many
> options you have. I would even go as far as saying that there are
> simpler solutions, one being a shell script (or Windows batch file)
> where you just have you Java command with the jar on the classpath and
> the options to have the excel file generated.

A solution like this, is what I would like to replace, actually. :-)

> Using Maven here would just add an additional dependency (to Maven)
> which could just complicate things.

What we have, is:
 - A jar that is built with maven, and installed in the local plexus
   archive, this Jar file creates an excel file from a template
 - Many jenkins projects that uses the jar together with two python
   scrips
 - The python scripts, are:
  - A script to delete existing XLS files in the working directory
  - A script to download the jar from plexus

What I would like to have, are maven projects that would:
 1. Have the jar project as a dependency
 2. Run the jar to create the XLS spreadsheet in the target directory
 3. Offer the the XLS spreadsheet in the target directory as a Jenkins
build artifact

Ie. since the python scripts does things that maven does by default
(clean the working directory, and download jar files from plexus),
replacing them with a maven project seemed like a good idea.
 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: What packaging for Jira excel reports with maven?

[Sebastian Otaegui]

Or ivy if you want dependency resolution
On Apr 2, 2014 7:59 AM, "Ron Wheeler" 
wrote:

> Looks like something that ANT might be good at.
>
> Ron
> On 02/04/2014 6:58 AM, Anders Hammar wrote:
>
>> I categorize different usage of Maven into two categories:
>> A) As a build tool
>> B) As a utility tool
>>
>> A) would be for example building a Java web application, i.e. using the
>> full build lifecycle of Maven. B) on the other hand is where you just want
>> to do one specific "thing", for example generate Java classes from an xml
>> schema or creating a jar of existing Java classes.
>>
>> So the first question is if your usage would fit into A or B? To narrow
>> things down a little bit, do you want this excel file to be generated as
>> part of the build of your software and then deployed together with that to
>> the repository? If so, it would be A. If you're just trying to find a tool
>> to generate this excel file on demand, we would be in B.
>>
>> My point here is that if you're in category A then Maven is absolutely
>> appropriate. At least if you're building everything else with Maven. But
>> if
>> you're in category B, then Maven is just one of many options you have. I
>> would even go as far as saying that there are simpler solutions, one being
>> a shell script (or Windows batch file) where you just have you Java
>> command
>> with the jar on the classpath and the options to have the excel file
>> generated. Using Maven here would just add an additional dependency (to
>> Maven) which could just complicate things.
>>
>> My two cents,
>> /Anders
>>
>>
>> On Tue, Apr 1, 2014 at 2:05 PM, Steinar Bang  wrote:
>>
>>  I have access to a Jar-file that contains code that:
>>>   - Reads an excel file containing a JQL query, the names of the fields
>>> from the JQL results to include in excel, as well as the sheets that
>>> are to be populated
>>>   - Talks to Jira, using the Jira REST API, to do the query and extract
>>> the results
>>>   - Exports a new excel file populated with the query results
>>>
>>> The Jar-file resides in a plexus archive, so I thought that having a
>>> small maven project, containing a pom.xml and the template excel
>>> spreadshet in src/main/resources/ would be a good match.
>>>
>>> The idea was that I could:
>>>   - set the Jar-file containing the excel export code as a dependency
>>>   - use exec-maven-plugin to run the Jar
>>>   - have the output of exec-maven-plugin (an excel file) as the build
>>> artifact
>>>
>>> But the idea stopped on that I don't know what packaging should be used
>>> for the pom: "jar" didn't seem appropriate, so I tried "pom", but that
>>> doesn't do anything (no target directory created).
>>>
>>> Is maven appropriate for what I'm trying to do? Is there an appropriate
>>> packaging to use?
>>>
>>> Thanks!
>>>
>>>
>>> - Steinar
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: What packaging for Jira excel reports with maven?

[Ron Wheeler]

Looks like something that ANT might be good at.

Ron
On 02/04/2014 6:58 AM, Anders Hammar wrote:

I categorize different usage of Maven into two categories:
A) As a build tool
B) As a utility tool

A) would be for example building a Java web application, i.e. using the
full build lifecycle of Maven. B) on the other hand is where you just want
to do one specific "thing", for example generate Java classes from an xml
schema or creating a jar of existing Java classes.

So the first question is if your usage would fit into A or B? To narrow
things down a little bit, do you want this excel file to be generated as
part of the build of your software and then deployed together with that to
the repository? If so, it would be A. If you're just trying to find a tool
to generate this excel file on demand, we would be in B.

My point here is that if you're in category A then Maven is absolutely
appropriate. At least if you're building everything else with Maven. But if
you're in category B, then Maven is just one of many options you have. I
would even go as far as saying that there are simpler solutions, one being
a shell script (or Windows batch file) where you just have you Java command
with the jar on the classpath and the options to have the excel file
generated. Using Maven here would just add an additional dependency (to
Maven) which could just complicate things.

My two cents,
/Anders


On Tue, Apr 1, 2014 at 2:05 PM, Steinar Bang  wrote:


I have access to a Jar-file that contains code that:
  - Reads an excel file containing a JQL query, the names of the fields
from the JQL results to include in excel, as well as the sheets that
are to be populated
  - Talks to Jira, using the Jira REST API, to do the query and extract
the results
  - Exports a new excel file populated with the query results

The Jar-file resides in a plexus archive, so I thought that having a
small maven project, containing a pom.xml and the template excel
spreadshet in src/main/resources/ would be a good match.

The idea was that I could:
  - set the Jar-file containing the excel export code as a dependency
  - use exec-maven-plugin to run the Jar
  - have the output of exec-maven-plugin (an excel file) as the build
artifact

But the idea stopped on that I don't know what packaging should be used
for the pom: "jar" didn't seem appropriate, so I tried "pom", but that
doesn't do anything (no target directory created).

Is maven appropriate for what I'm trying to do? Is there an appropriate
packaging to use?

Thanks!


- Steinar


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: What packaging for Jira excel reports with maven?

[Anders Hammar]

I categorize different usage of Maven into two categories:
A) As a build tool
B) As a utility tool

A) would be for example building a Java web application, i.e. using the
full build lifecycle of Maven. B) on the other hand is where you just want
to do one specific "thing", for example generate Java classes from an xml
schema or creating a jar of existing Java classes.

So the first question is if your usage would fit into A or B? To narrow
things down a little bit, do you want this excel file to be generated as
part of the build of your software and then deployed together with that to
the repository? If so, it would be A. If you're just trying to find a tool
to generate this excel file on demand, we would be in B.

My point here is that if you're in category A then Maven is absolutely
appropriate. At least if you're building everything else with Maven. But if
you're in category B, then Maven is just one of many options you have. I
would even go as far as saying that there are simpler solutions, one being
a shell script (or Windows batch file) where you just have you Java command
with the jar on the classpath and the options to have the excel file
generated. Using Maven here would just add an additional dependency (to
Maven) which could just complicate things.

My two cents,
/Anders


On Tue, Apr 1, 2014 at 2:05 PM, Steinar Bang  wrote:

> I have access to a Jar-file that contains code that:
>  - Reads an excel file containing a JQL query, the names of the fields
>from the JQL results to include in excel, as well as the sheets that
>are to be populated
>  - Talks to Jira, using the Jira REST API, to do the query and extract
>the results
>  - Exports a new excel file populated with the query results
>
> The Jar-file resides in a plexus archive, so I thought that having a
> small maven project, containing a pom.xml and the template excel
> spreadshet in src/main/resources/ would be a good match.
>
> The idea was that I could:
>  - set the Jar-file containing the excel export code as a dependency
>  - use exec-maven-plugin to run the Jar
>  - have the output of exec-maven-plugin (an excel file) as the build
>artifact
>
> But the idea stopped on that I don't know what packaging should be used
> for the pom: "jar" didn't seem appropriate, so I tried "pom", but that
> doesn't do anything (no target directory created).
>
> Is maven appropriate for what I'm trying to do? Is there an appropriate
> packaging to use?
>
> Thanks!
>
>
> - Steinar
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

What packaging for Jira excel reports with maven?

[Steinar Bang]

I have access to a Jar-file that contains code that:
 - Reads an excel file containing a JQL query, the names of the fields
   from the JQL results to include in excel, as well as the sheets that
   are to be populated
 - Talks to Jira, using the Jira REST API, to do the query and extract
   the results
 - Exports a new excel file populated with the query results

The Jar-file resides in a plexus archive, so I thought that having a
small maven project, containing a pom.xml and the template excel
spreadshet in src/main/resources/ would be a good match.

The idea was that I could:
 - set the Jar-file containing the excel export code as a dependency
 - use exec-maven-plugin to run the Jar
 - have the output of exec-maven-plugin (an excel file) as the build
   artifact 

But the idea stopped on that I don't know what packaging should be used
for the pom: "jar" didn't seem appropriate, so I tried "pom", but that
doesn't do anything (no target directory created).

Is maven appropriate for what I'm trying to do? Is there an appropriate
packaging to use?

Thanks!


- Steinar


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

pmd:check has trouble loading reports from target/pmd.txt

[Andrew Pennebaker]

If I configure maven-pmd-plugin to use txt for the report,
then `mvn clean && mvn pmd:check` messes up, attempting to load the report
from `target/pmd.xml` instead of `target/pmd.txt`.

I tried specifying txt in both  and 
plugin sections, but mvn:check still doesn't know about the txt file.

I'm not sure if maven-pmd-plugin is able to parse back the violations from
the text format. If not, then maybe a good compromise is to always generate
both formats.

Using maven-pmd-plugin v3.0.1.

http://search.maven.org/#artifactdetails%7Corg.apache.maven.plugins%7Cmaven-pmd-plugin%7C3.0.1%7Cmaven-plugin

-- 
Cheers,

Andrew Pennebaker
apenneba...@42six.com

Help needed on Crystal reports in Maven!

[Mumtaz Ahmad]

Hello everybody,

 

We have reports in Jasper and CR (contains sub reports, Group controls) and
it displays and runs fine in Spring and JSF. We then tried to build into an
.ear file using Maven; a few of our CR reports are not working.

The CR generates the following errors:

. Unexpected query Engine.

. Can't create component controller.

We would appreciate your help, solution and suggestions. If you need more
information, please send me an email and I will send more details.

Thank you

 

 

Mumtaz Ahmad
Lonestar Technologies,
Lahore (Pakistan)

 

[ANN] Maven Project Info Reports Plugin version 2.7 Released

[Hervé Boutemy]

The Apache Maven team is pleased to announce the release of the Maven *Project 
Info Reports Plugin, version 2.7*

The Maven Project Info Reports plugin is used to generate reports information 
about the project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  2.7


Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.7

** Bug
* [MPIR-229] - The 'modules' report does not support 'url' elements using 
properties.
* [MPIR-257] - English localization properties misplaced (i18n)
* [MPIR-261] - Wrong URL for some CI home pages in resource bundles
* [MPIR-264] - JDK Rev not determined when Maven 2 is building the site
* [MPIR-266] - Subsequent runs of the dependencies report should always 
produce the same output if the input hasn't changed
* [MPIR-272] - add support for Maven 3.1-A1/Eclipse Aether 0.9-M2 to 
dependencies report
* [MPIR-275] - NPE in DependenciesReport

** Improvement
    * [MPIR-182] - Make order of reports shown in "Project Reports" configurable
* [MPIR-232] - when packaging is pom, index report (About) should contain 
modules report content
* [MPIR-258] - Missing english localization property for dependency-info 
(i18n)
* [MPIR-259] - Add french localization for dependency-info
* [MPIR-262] - Add support for 'report.cim.bamboo.intro' resource property
* [MPIR-271] - GIT support in project-info-reports:scm
* [MPIR-274] - Added translations and corrections to spanish resource 
boundle

** Task
* [MPIR-276] - Upgrade to Doxia 1.4

Enjoy,

-The Apache Maven team

RE: Maven build not populating with arabic characters in jasper reports

[sarmahdi]

Thanks Amir,

sorry for the late reply. I saw that I had missed out one of the fonts jars
which solved the issue when i added it back. 

Thanks for the help.

Syed...



--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-build-not-populating-with-arabic-characters-in-jasper-reports-tp5754151p5755831.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven 3.0.5 eclipse:eclipse reports a BULD SUCCES while dependency does not exist.

[Wayne Fay]

> I have the following dependency in my pom but this version does not exist
> in our repository. Maven then tries to download it from
> http://repo1.maven.org/ where of course this package also does not exists.
> But Maven reports BUILD SUCCESS while there are unresolved packages. Is
> this normal behavior or is this a bug?
>
> I spent some time to figure out that I was using a wrong version. If Maven
> had given any sort of warning it would have saved me some time.
> So if this is by design then it would be a nice feature to have a warning
> of some sort.

There are two things going on here...

First, the purpose of the eclipse:eclipse goal is to simply take your
pom and produce Eclipse-compatible project files. So the
maven-eclipse-plugin does not really care (nor does it see other
functionality as part of its job) if the dependency artifacts exist in
your repo(s). If you want this to happen, you'd need to submit a patch
against the plugin to add the functionality.

Second, when you call a plugin goal directly like "mvn
eclipse:eclipse" then Maven does not run the full lifecycle, instead
it just invokes that goal directly. So Maven never has the opportunity
to complain about a missing artifact during an earlier lifecycle phase
as it would otherwise.

So, if you want to see these kinds of warnings or errors, I'd suggest
using "mvn validate eclipse:eclipse" instead. Revert the pom to
provide a "bad" version for a dependency and see if Maven complains as
you'd expect when you run it like this.

But ultimately, I think you shouldn't be using eclipse:eclipse at all.
Instead you should use M2E which is what "everyone" else is using.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven 3.0.5 eclipse:eclipse reports a BULD SUCCES while dependency does not exist.

[Chris de Vries]

I have the following dependency in my pom but this version does not exist
in our repository. Maven then tries to download it from
http://repo1.maven.org/ where of course this package also does not exists.
But Maven reports BUILD SUCCESS while there are unresolved packages. Is
this normal behavior or is this a bug?

I spent some time to figure out that I was using a wrong version. If Maven
had given any sort of warning it would have saved me some time.
So if this is by design then it would be a nice feature to have a warning
of some sort.




   nl.cjib.clients
   zakenregister-client
   8.3.0.0


[INFO] [INFO]

[INFO] Building dwangproforma-service-war 6.0.0.1-SNAPSHOT [INFO]

[INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @
dwangproforma-service-war >>> [INFO] [INFO] <<<
maven-eclipse-plugin:2.8:eclipse (default-cli) @ dwangproforma-service-war
<<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @
dwangproforma-service-war --- [WARNING] The POM for
org.apache.maven:maven-repository-metadata:jar:2.0 is missing, no
dependency information available [INFO] Adding support for WTP version R7.
[INFO] Using Eclipse Workspace: null [INFO] Adding default classpath
container: org.eclipse.jdt.launching.JRE_CONTAINER Downloading:
http://repo1.maven.org/maven2/nl/cjib/clients/zakenregister-client/8.3.0.0/zakenregister-client-8.3.0.0.pom[INFO]
File
D:\work\java\dwangproforma-service-accelerate\dwangproforma-service-war\.project
already exists. Additional settings will be preserved, run mvn
eclipse:clean if you want old settings to be removed. [INFO] Wrote Eclipse
project for "dwangproforma-service-war" to
D:\work\java\dwangproforma-service-accelerate\dwangproforma-service-war.
[INFO] [INFO]

[INFO] BUILD SUCCESS [INFO]

[INFO] Total time: 24.156s [INFO] Finished at: Mon Apr 29 10:53:35 CEST
2013 [INFO] Final Memory: 6M/18M [INFO]


Settings look like this   (I placed some xxx's ;this is not the original
file but it should not matter for this post)


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

D:\work\.m2\repository



nexus



false

cjibcentral
libs-release
http://xxx:8080/nexus/content/repositories/releases




snapshots
libs-snapshot
http://xxx:8080/nexus/content/repositories/snapshots






false

central
plugins-release
http://xx:8080/nexus/content/repositories/releases



snapshots
plugins-snapshot
http://xxx:8080/nexus/content/repositories/snapshots






jbos


jboss-public-repository-group
JBoss Public Maven Repository Group
https://repository.jboss.org/nexus/content/groups/public/
default

true
never


true
never



 

jboss-public-repository-group
JBoss Public Maven Repository Group
https://repository.jboss.org/nexus/content/groups/public/
default

true
never


true
never







nexus





true
http
xx.xxx.nl
8080
xx
xx
*.cjib.minjus.nl

RE: Maven build not populating with arabic characters in jasper reports

[Amir Gheibi]

It seems that when your reports are built from within eclipse your Arabic font 
is in your classpath and when built with Maven, it isn't.

Use iReport to export the font as an extension, manually install the generated 
jar file onto your repository (or upload it to your repository manager if you 
are using one such as Nexus), and use it as a dependency.

Let us know if this helped.

From: sarmahdi [sarma...@hotmail.com]
Sent: Saturday, April 20, 2013 2:11 AM
To: users@maven.apache.org
Subject: Maven build not populating with arabic characters in jasper reports

Hello All,I tried searching for this issue and i couldn't find anything. When
i build my application with eclipse my jasper reports are coming correctly
in English and Arabic. When i build it through maven, my English reports are
coming correctly but my Arabic reports are generated but with no Arabic.
Some of the labels are coming as in English but some are not even there they
are just empty. The data that is supposed to come in numbers is also not
showing. I cant say that  don't have fonts or something as the same reports
work when i build it through eclipse and generate an ear file through that.
but when maven does the ear file they don't work in Arabic.What am I missing
here. Hows is maven related to this anyways.Any help will be
appreciate.ThanksSyed.



--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-build-not-populating-with-arabic-characters-in-jasper-reports-tp5754151.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven build not populating with arabic characters in jasper reports

[sarmahdi]

Hello All,I tried searching for this issue and i couldn't find anything. When
i build my application with eclipse my jasper reports are coming correctly
in English and Arabic. When i build it through maven, my English reports are
coming correctly but my Arabic reports are generated but with no Arabic.
Some of the labels are coming as in English but some are not even there they
are just empty. The data that is supposed to come in numbers is also not
showing. I cant say that  don't have fonts or something as the same reports
work when i build it through eclipse and generate an ear file through that.
but when maven does the ear file they don't work in Arabic.What am I missing
here. Hows is maven related to this anyways.Any help will be
appreciate.ThanksSyed.



--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-build-not-populating-with-arabic-characters-in-jasper-reports-tp5754151.html
Sent from the Maven - Users mailing list archive at Nabble.com.

[ANN] Maven Maven Project Info Reports Plugin 2.6 Released

[Kristian Rosenvold]

The Maven team is pleased to announce the release of the Maven Project Info
Reports Plugin, version 2.6

This version fixed an annoying bug in the 2.5.x range, where the
plugin was actually
downloading a noticeable part of the internet. It also adds
image/gravatar.com avatar support to
the team list

The Maven Project Info Reports Plugin is a plugin that generates standard
reports  for the specified project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  2.6



Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.6



** Bug
* [MPIR-233] - dependency-management is checking for SNAPSHOT updates
* [MPIR-255] - DependencyManagement report reads every artifact
from repository



** Improvement
* [MPIR-176] - Support picture URLs in team report



Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Project Info Reports Plugin 2.5.1 Released

[Hervé Boutemy]

The Maven team is pleased to announce the release of the Maven Project Info 
Reports Plugin, version 2.5.1

The Maven Project Info Reports Plugin is a plugin that generates standard 
reports for the specified project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  2.5.1



Release Notes - Maven Project Info Reports Plugin - Version 2.5.1

Bug
* [MPIR-250] dependency-info packaging information broken: displays 
"${project.packaging"
* [MPIR-249] new dependency-info report not added to goals index page
* [MPIR-248] NPE while DependenciesReport
* [MPIR-187] Usage of other(internal) TLD

Improvement
* [MPIR-239] Brazillian Portuguese translation


Enjoy,

-The Maven team


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven compiler plugin reports warnings as error

[Sascha Vogt]

Hi Wayne,

Am 29.08.2012 16:13, schrieb Wayne Fay:
>> I did a few more tests, see the output below. Should I open a ticket for
>> that?
> 
> What JDK are you using in each example?
I tried with 1.6.0_32 and 1.7.0_04, both 64-bit Version on Windows7 64-bit

> And yes, in general, if you think you have found a bug, you should
> open a ticket. It is especially nice if you can provide a patch to fix
> it as well. ;)
The question I had was more, if this is considered a bug, or if this
was/is intended behavior

Anyway, I created a Jira (http://jira.codehaus.org/browse/MCOMPILER-179)

Thx for the help
Greetings
-Sascha-

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven compiler plugin reports warnings as error

[Wayne Fay]

> I did a few more tests, see the output below. Should I open a ticket for
> that?

What JDK are you using in each example?

And yes, in general, if you think you have found a bug, you should
open a ticket. It is especially nice if you can provide a patch to fix
it as well. ;)

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven compiler plugin reports warnings as error

[Sascha Vogt]

Hi again,

I did a few more tests, see the output below. Should I open a ticket for
that?

The output of 2.3.2 is
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[WARNING]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
[unchecked] unchecked conversion
found   : java.util.List
required: java.util.List
[INFO] 3 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
getList() in de.maybebuggy.sample.Main cannot be applied to (int)
[INFO] 1 error
[INFO] -


As of 2.4 (and 2.5, 2.5.1) the output is:
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] bad path element "": no such file or directory
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18]
[unchecked] unchecked call to add(E) as a member of the raw type
java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15]
[unchecked] unchecked conversion
found   : java.util.List
required: java.util.List
[ERROR]
C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29]
getList() in de.maybebuggy.sample.Main cannot be applied to (int)
[INFO] 4 errors

Am 28.08.2012 11:47, schrieb Sascha Vogt:
> Hi all,
> 
> with the maven compiler plugin (version 2.5.1) and Maven 3.0.3 / 3.0.4 I
> have the the strange effect, that if I have one real build error all
> warnings are reported as errors as well.
> 
> Settings for the compiler plugin are (copied from the effective pom):
>-Xlint:all
>true
>true
>1.6
>1.6
>1.6
> 
> This makes it very hard to spot the real error. Is this the intended
> behavior? I didn't find an issue regarding that.
> 
> Greetings
> -Sascha-
> 
> PS: I did a quick check, and using the compiler plugin 2.3.1 only shows
> the real error as error and the rest still as warning, though the output
> seems to have changed quite a bit


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven compiler plugin reports warnings as error

[Sascha Vogt]

Hi all,

with the maven compiler plugin (version 2.5.1) and Maven 3.0.3 / 3.0.4 I
have the the strange effect, that if I have one real build error all
warnings are reported as errors as well.

Settings for the compiler plugin are (copied from the effective pom):
   -Xlint:all
   true
   true
   1.6
   1.6
   1.6

This makes it very hard to spot the real error. Is this the intended
behavior? I didn't find an issue regarding that.

Greetings
-Sascha-

PS: I did a quick check, and using the compiler plugin 2.3.1 only shows
the real error as error and the rest still as warning, though the output
seems to have changed quite a bit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Maven Project Info Reports Plugin 2.5 Released

[Hervé Boutemy]

The Maven team is pleased to announce the release of the Maven Project Info 
Reports Plugin, version 2.5

The Maven Project Info Reports Plugin is a plugin that generates standard 
reports  for the specified project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  2.5



Release Notes - Maven Project Info Reports Plugin - Version 2.5

Bug
* [MPIR-245] blacklisted column in dependencies location is rendered without 
header
* [MPIR-244] With Maven 3, "Dependency Repository Locations" in dependencies 
report shows my local repository manager id and url instead of public 
repository info
* [MPIR-237] Unexpected download
* [MPIR-228] HTML code detection in license content too precise: doesn't 
detect EPL at http://www.eclipse.org/legal/epl-v10.html is HTML

Improvement
* [MPIR-236] Create a new report to show how to include the module in different 
build systems

New Feature
* [MPIR-227] add an index listing all licenses at page start

Task
* [MPIR-246] use maven-plugin-tools' java 5 annotations


Enjoy,

-The Maven team


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

AW: [mvn-3.0.5] troubles with Generating "Plugin Management" report --- maven-project-info-reports-plugin:2.4

[Stadelmann Josef]

Wayne

I have done that very carefully yesterday. For me all was Ok but as you can see 
it failed.
I deleted me repo several times and was unable to build error free.

This morning I moved my project to a different directiory tree but on the same 
disk.
Then I've rerun maven from the same account to build the project ... all was 
excellent working.

So now, I don’t have explanation why the POM's should have an issue, but maybe 
there is a protection 
or left rubbish problem somewhere, i.e. maven attempting to build into a local 
place or the like. 

I am confused, but it runs OK now.

Thank you very much for your help and don’t bother with me when I send in such 
stack traces.

Josef

-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:wayne...@gmail.com] 
Gesendet: Montag, 9. Juli 2012 18:52
An: Maven Users List
Betreff: Re: [mvn-3.0.5] troubles with Generating "Plugin Management" report 
--- maven-project-info-reports-plugin:2.4

> Downloaded:
> http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
> ral/org/codehaus/mojo/clirr-maven-plugin/2.3/clirr-maven-plugin-2.3.pom
> (8 KB at 41.1 KB/sec)
> Downloaded:
> http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
> ral/org/codehaus/mojo/mojo-parent/27/mojo-parent-27.pom (27 KB at 175.4
> KB/sec)
> [INFO] Could not build project for: clirr-maven-plugin:1 problem was
> encountered while building the effective model for
> org.codehaus.mojo:clirr-maven-plugin:2.3
> [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27:
> Could not find artifact org.codehaus:codehaus-parent:pom:3 @
> org.codehaus.mojo:mojo-parent:27
>  for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project
> org.codehaus.mojo:clirr-maven-plugin:2.3
> org.apache.maven.project.InvalidProjectModelException: 1 problem was
> encountered while building the effective model for
> org.codehaus.mojo:clirr-maven-plugin:2.3
> [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27:
> Could not find artifact org.codehaus:codehaus-parent:pom:3 @
> org.codehaus.mojo:mojo-parent:27
>  for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project
> org.codehaus.mojo:clirr-maven-plugin:2.3

This error suggests the pom files for clirr-maven-plugin:2.3 and maybe
mojo-parent:27 and codehaus-parent in your repo might have issues.
Look at those poms in particular.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [mvn-3.0.5] troubles with Generating "Plugin Management" report --- maven-project-info-reports-plugin:2.4

[Wayne Fay]

> Downloaded:
> http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
> ral/org/codehaus/mojo/clirr-maven-plugin/2.3/clirr-maven-plugin-2.3.pom
> (8 KB at 41.1 KB/sec)
> Downloaded:
> http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
> ral/org/codehaus/mojo/mojo-parent/27/mojo-parent-27.pom (27 KB at 175.4
> KB/sec)
> [INFO] Could not build project for: clirr-maven-plugin:1 problem was
> encountered while building the effective model for
> org.codehaus.mojo:clirr-maven-plugin:2.3
> [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27:
> Could not find artifact org.codehaus:codehaus-parent:pom:3 @
> org.codehaus.mojo:mojo-parent:27
>  for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project
> org.codehaus.mojo:clirr-maven-plugin:2.3
> org.apache.maven.project.InvalidProjectModelException: 1 problem was
> encountered while building the effective model for
> org.codehaus.mojo:clirr-maven-plugin:2.3
> [FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27:
> Could not find artifact org.codehaus:codehaus-parent:pom:3 @
> org.codehaus.mojo:mojo-parent:27
>  for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project
> org.codehaus.mojo:clirr-maven-plugin:2.3

This error suggests the pom files for clirr-maven-plugin:2.3 and maybe
mojo-parent:27 and codehaus-parent in your repo might have issues.
Look at those poms in particular.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[mvn-3.0.5] troubles with Generating "Plugin Management" report --- maven-project-info-reports-plugin:2.4

[Stadelmann Josef]

How can I make it work?

1.  The Warning bothers me ...
2.  deleted in my repository all in subdirectory mojo from
org.codehaus (so all org.codehaus.mojo artifacts need to be refreshed
from external repo or maven central or 
3.  However that does not work
4.  But I have checked the various pom's and cant find the gulty
one.
5.  So what could be the reason for the FATAL errors below, because
as you can see artifacs are downloaded if missing
6.  what else can I cleanup in my local repo?
7.  what does this mean: "[INFO] Could not build project for:
clirr-maven-plugin:1"
8.  is there a relation to "
org.apache.maven.project.InvalidProjectModelException: 1"
9.  can it be that bandRepositories now strikes back?

Josef



[INFO]
[INFO] --- maven-site-plugin:3.0:site (default) @ SpezplaService ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.4
[INFO] Parent project loaded from repository:
com.axa.ch.spezpla:Spezpla-Parent:pom:1.0
[WARNING] Unable to find a URL to the parent project. The parent menu
will NOT be added.
[INFO] Relativizing decoration links with respect to project URL:
http://integ2.ch.winterthur.com/Wiki/index.php/SpezplaService
[INFO] Rendering site with
org.apache.maven.skins:maven-default-skin:jar:1.0 skin.
[INFO] Generating "About" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Project Summary" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Project License" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Source Repository" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Issue Tracking" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Continuous Integration" report    ---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:2.4
Downloading:
http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
ral/org/codehaus/mojo/clirr-maven-plugin/2.3/clirr-maven-plugin-2.3.pom
Downloaded:
http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
ral/org/codehaus/mojo/clirr-maven-plugin/2.3/clirr-maven-plugin-2.3.pom
(8 KB at 41.1 KB/sec)
Downloading:
http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
ral/org/codehaus/mojo/mojo-parent/27/mojo-parent-27.pom
Downloaded:
http://mavenrepo.ch.winterthur.com:12697/nexus/content/repositories/cent
ral/org/codehaus/mojo/mojo-parent/27/mojo-parent-27.pom (27 KB at 175.4
KB/sec)
[INFO] Could not build project for: clirr-maven-plugin:1 problem was
encountered while building the effective model for
org.codehaus.mojo:clirr-maven-plugin:2.3
[FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27:
Could not find artifact org.codehaus:codehaus-parent:pom:3 @
org.codehaus.mojo:mojo-parent:27
 for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project
org.codehaus.mojo:clirr-maven-plugin:2.3
org.apache.maven.project.InvalidProjectModelException: 1 problem was
encountered while building the effective model for
org.codehaus.mojo:clirr-maven-plugin:2.3
[FATAL] Non-resolvable parent POM for org.codehaus.mojo:mojo-parent:27:
Could not find artifact org.codehaus:codehaus-parent:pom:3 @
org.codehaus.mojo:mojo-parent:27
 for project org.codehaus.mojo:clirr-maven-plugin:2.3 for project
org.codehaus.mojo:clirr-maven-plugin:2.3
at
org.apache.maven.project.DefaultMavenProjectBuilder.transformError(Defau
ltMavenProjectBuilder.java:174)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:221)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:232)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:239)
at
org.apache.maven.report.projectinfo.PluginManagementReport$PluginManagem
entRenderer.renderSectionPluginManagement(PluginManagementReport.java:20
3)
at
org.apache.maven.report.projectinfo.PluginManagementReport$PluginManagem
entRenderer.renderBody(PluginManagementReport.java:166)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMa
venReportRenderer.java:79)
at
org.apache.maven.report.projectinfo.PluginManagementReport.executeReport
(PluginManagementReport.java:80)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRep
ort.java:190

Re: Code coverage report for multi module maven project reports zero in some modules

[kfmohamm]

Thanks Thomas,

I tried what you suggested and now we have the code coverage report for
all our modules.

Thanks
Khurram

> On 1 July 2012 03:51,   wrote:
>> Yes, I have moduleA, moduleB, moduleC, moduleD, moduleE and module F. I
>> run JUnit tests from module F.
>
> This is not the way the Cobertura plugin expects you to do stuff. I
> have solved this scenario with a mix if Maven and And. If you are
> interested, take a look at
> http://thomassundberg.wordpress.com/2012/02/18/test-coverage-in-a-multi-module-maven-project/
>
> HTH
> Thomas
>
>
>
>>
>> The report in the moduleF/target... directory has the required coverage
>> information. However, the coverage report in the other modules reports
>> line and code coverage as zero.
>>
>> I did try to use the aggregate option with setting it to true, to see an
>> aggregate coverage report for all modules, it gives the aggregate
>> report,
>> but again only for packages in moduleF(from where we run JUnit tests)
>> and
>> reports as zero for all other modules.
>>
>> I am trying what was suggested in the first response to this question.
>>
>> Is there a way that we generate the code coverage report for all
>> modules,
>> with out using ant and only with use of cobertura ?
>>
>> Thanks
>>
>>> Aggregated cobertura report will execute cobertura on each module and
>>> then
>>> merge the single reports. It will not help if, for example, you have
>>> tests
>>> in module A and want to have coverage of module B.
>>>
>>>
>>> On Sat, Jun 30, 2012 at 10:46 AM, Patrick Mohr 
>>> wrote:
>>>
>>>> On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
>>>> aliaksei.lahac...@gmail.com> wrote:
>>>>
>>>> > Hi!
>>>> >
>>>> > cobertura:cobertura executes it's own lifecycle: instruments the
>>>> classes,
>>>> > instrumented classes are saved to
>>>> target/generated-classes/cobertura,
>>>> and
>>>> > executes unit tests. Instrumented classes dump coverage data to
>>>> > target/conbertura/cobertura.ser. There are two things to understand:
>>>> >
>>>> > 1. When cobertura:cobertura is executed, dependencies are not
>>>> instrumented.
>>>> > You have to have enabled instrumentation, see cobertura:instrument
>>>> goal.
>>>> > This will produce jars with instrumented classes, so be careful not
>>>> to
>>>> > distribute them.
>>>> > 2. Each module will write coverage data to it's own
>>>> > target/conbertura/cobertura.ser file. I think it's possible to
>>>> configure
>>>> > instrumentation so that all jars write to the same cobertura.ser
>>>> file,
>>>> but
>>>> > I don't know whether it's normal, and I never tried that.
>>>> >
>>>> >
>>>> I want to say that there's a cobertura target.  Something like
>>>> cobertura:aggregate that will combine the results off all the unit
>>>> tests,
>>>> for the module that's being tested.  That probably won't be what you
>>>> want,
>>>> but I think it would be a lot closer.  This is all from memory though,
>>>> so
>>>> make sure to check it's actually what you want.
>>>>
>>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>
>
>
> --
> Thomas Sundberg
> M. Sc. in Computer Science
>
> Mobile: +46 70 767 33 15
> Blog: http://thomassundberg.wordpress.com/
> Twitter: @thomassundberg
>
> Better software through faster feedback
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Code coverage report for multi module maven project reports zero in some modules

[Thomas Sundberg]

On 1 July 2012 03:51,   wrote:
> Yes, I have moduleA, moduleB, moduleC, moduleD, moduleE and module F. I
> run JUnit tests from module F.

This is not the way the Cobertura plugin expects you to do stuff. I
have solved this scenario with a mix if Maven and And. If you are
interested, take a look at
http://thomassundberg.wordpress.com/2012/02/18/test-coverage-in-a-multi-module-maven-project/

HTH
Thomas



>
> The report in the moduleF/target... directory has the required coverage
> information. However, the coverage report in the other modules reports
> line and code coverage as zero.
>
> I did try to use the aggregate option with setting it to true, to see an
> aggregate coverage report for all modules, it gives the aggregate report,
> but again only for packages in moduleF(from where we run JUnit tests) and
> reports as zero for all other modules.
>
> I am trying what was suggested in the first response to this question.
>
> Is there a way that we generate the code coverage report for all modules,
> with out using ant and only with use of cobertura ?
>
> Thanks
>
>> Aggregated cobertura report will execute cobertura on each module and then
>> merge the single reports. It will not help if, for example, you have tests
>> in module A and want to have coverage of module B.
>>
>>
>> On Sat, Jun 30, 2012 at 10:46 AM, Patrick Mohr  wrote:
>>
>>> On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
>>> aliaksei.lahac...@gmail.com> wrote:
>>>
>>> > Hi!
>>> >
>>> > cobertura:cobertura executes it's own lifecycle: instruments the
>>> classes,
>>> > instrumented classes are saved to target/generated-classes/cobertura,
>>> and
>>> > executes unit tests. Instrumented classes dump coverage data to
>>> > target/conbertura/cobertura.ser. There are two things to understand:
>>> >
>>> > 1. When cobertura:cobertura is executed, dependencies are not
>>> instrumented.
>>> > You have to have enabled instrumentation, see cobertura:instrument
>>> goal.
>>> > This will produce jars with instrumented classes, so be careful not to
>>> > distribute them.
>>> > 2. Each module will write coverage data to it's own
>>> > target/conbertura/cobertura.ser file. I think it's possible to
>>> configure
>>> > instrumentation so that all jars write to the same cobertura.ser file,
>>> but
>>> > I don't know whether it's normal, and I never tried that.
>>> >
>>> >
>>> I want to say that there's a cobertura target.  Something like
>>> cobertura:aggregate that will combine the results off all the unit
>>> tests,
>>> for the module that's being tested.  That probably won't be what you
>>> want,
>>> but I think it would be a lot closer.  This is all from memory though,
>>> so
>>> make sure to check it's actually what you want.
>>>
>>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



-- 
Thomas Sundberg
M. Sc. in Computer Science

Mobile: +46 70 767 33 15
Blog: http://thomassundberg.wordpress.com/
Twitter: @thomassundberg

Better software through faster feedback

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Code coverage report for multi module maven project reports zero in some modules

[Aliaksei Lahachou]

I also use jenkins cobertura plugin and it does nothing special. It is
invoked after the build and only generates aggregated report from single
coverage.xml files.


On Sun, Jul 1, 2012 at 9:00 AM, Tim Wu T  wrote:

> Hi,
>
> I met the same problem with you, now, I use jenkins cobuertural plugin,
> which will help me generate a whole report, not only include some packages
> :)
>
> Br,
> Tim
>
> -Original Message-
> From: kfmoh...@uci.edu [mailto:kfmoh...@uci.edu]
> Sent: Sunday, July 01, 2012 9:51 AM
> To: Maven Users List
> Subject: Re: Code coverage report for multi module maven project reports
> zero in some modules
>
> Yes, I have moduleA, moduleB, moduleC, moduleD, moduleE and module F. I
> run JUnit tests from module F.
>
> The report in the moduleF/target... directory has the required coverage
> information. However, the coverage report in the other modules reports
> line and code coverage as zero.
>
> I did try to use the aggregate option with setting it to true, to see an
> aggregate coverage report for all modules, it gives the aggregate report,
> but again only for packages in moduleF(from where we run JUnit tests) and
> reports as zero for all other modules.
>
> I am trying what was suggested in the first response to this question.
>
> Is there a way that we generate the code coverage report for all modules,
> with out using ant and only with use of cobertura ?
>
> Thanks
>
> > Aggregated cobertura report will execute cobertura on each module and
> then
> > merge the single reports. It will not help if, for example, you have
> tests
> > in module A and want to have coverage of module B.
> >
> >
> > On Sat, Jun 30, 2012 at 10:46 AM, Patrick Mohr  wrote:
> >
> >> On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
> >> aliaksei.lahac...@gmail.com> wrote:
> >>
> >> > Hi!
> >> >
> >> > cobertura:cobertura executes it's own lifecycle: instruments the
> >> classes,
> >> > instrumented classes are saved to target/generated-classes/cobertura,
> >> and
> >> > executes unit tests. Instrumented classes dump coverage data to
> >> > target/conbertura/cobertura.ser. There are two things to understand:
> >> >
> >> > 1. When cobertura:cobertura is executed, dependencies are not
> >> instrumented.
> >> > You have to have enabled instrumentation, see cobertura:instrument
> >> goal.
> >> > This will produce jars with instrumented classes, so be careful not to
> >> > distribute them.
> >> > 2. Each module will write coverage data to it's own
> >> > target/conbertura/cobertura.ser file. I think it's possible to
> >> configure
> >> > instrumentation so that all jars write to the same cobertura.ser file,
> >> but
> >> > I don't know whether it's normal, and I never tried that.
> >> >
> >> >
> >> I want to say that there's a cobertura target.  Something like
> >> cobertura:aggregate that will combine the results off all the unit
> >> tests,
> >> for the module that's being tested.  That probably won't be what you
> >> want,
> >> but I think it would be a lot closer.  This is all from memory though,
> >> so
> >> make sure to check it's actually what you want.
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

RE: Code coverage report for multi module maven project reports zero in some modules

[Tim Wu T]

Hi,

I met the same problem with you, now, I use jenkins cobuertural plugin, which 
will help me generate a whole report, not only include some packages :)

Br,
Tim

-Original Message-
From: kfmoh...@uci.edu [mailto:kfmoh...@uci.edu] 
Sent: Sunday, July 01, 2012 9:51 AM
To: Maven Users List
Subject: Re: Code coverage report for multi module maven project reports zero 
in some modules

Yes, I have moduleA, moduleB, moduleC, moduleD, moduleE and module F. I
run JUnit tests from module F.

The report in the moduleF/target... directory has the required coverage
information. However, the coverage report in the other modules reports
line and code coverage as zero.

I did try to use the aggregate option with setting it to true, to see an
aggregate coverage report for all modules, it gives the aggregate report,
but again only for packages in moduleF(from where we run JUnit tests) and
reports as zero for all other modules.

I am trying what was suggested in the first response to this question.

Is there a way that we generate the code coverage report for all modules,
with out using ant and only with use of cobertura ?

Thanks

> Aggregated cobertura report will execute cobertura on each module and then
> merge the single reports. It will not help if, for example, you have tests
> in module A and want to have coverage of module B.
>
>
> On Sat, Jun 30, 2012 at 10:46 AM, Patrick Mohr  wrote:
>
>> On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
>> aliaksei.lahac...@gmail.com> wrote:
>>
>> > Hi!
>> >
>> > cobertura:cobertura executes it's own lifecycle: instruments the
>> classes,
>> > instrumented classes are saved to target/generated-classes/cobertura,
>> and
>> > executes unit tests. Instrumented classes dump coverage data to
>> > target/conbertura/cobertura.ser. There are two things to understand:
>> >
>> > 1. When cobertura:cobertura is executed, dependencies are not
>> instrumented.
>> > You have to have enabled instrumentation, see cobertura:instrument
>> goal.
>> > This will produce jars with instrumented classes, so be careful not to
>> > distribute them.
>> > 2. Each module will write coverage data to it's own
>> > target/conbertura/cobertura.ser file. I think it's possible to
>> configure
>> > instrumentation so that all jars write to the same cobertura.ser file,
>> but
>> > I don't know whether it's normal, and I never tried that.
>> >
>> >
>> I want to say that there's a cobertura target.  Something like
>> cobertura:aggregate that will combine the results off all the unit
>> tests,
>> for the module that's being tested.  That probably won't be what you
>> want,
>> but I think it would be a lot closer.  This is all from memory though,
>> so
>> make sure to check it's actually what you want.
>>
>



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Code coverage report for multi module maven project reports zero in some modules

[kfmohamm]

Yes, I have moduleA, moduleB, moduleC, moduleD, moduleE and module F. I
run JUnit tests from module F.

The report in the moduleF/target... directory has the required coverage
information. However, the coverage report in the other modules reports
line and code coverage as zero.

I did try to use the aggregate option with setting it to true, to see an
aggregate coverage report for all modules, it gives the aggregate report,
but again only for packages in moduleF(from where we run JUnit tests) and
reports as zero for all other modules.

I am trying what was suggested in the first response to this question.

Is there a way that we generate the code coverage report for all modules,
with out using ant and only with use of cobertura ?

Thanks

> Aggregated cobertura report will execute cobertura on each module and then
> merge the single reports. It will not help if, for example, you have tests
> in module A and want to have coverage of module B.
>
>
> On Sat, Jun 30, 2012 at 10:46 AM, Patrick Mohr  wrote:
>
>> On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
>> aliaksei.lahac...@gmail.com> wrote:
>>
>> > Hi!
>> >
>> > cobertura:cobertura executes it's own lifecycle: instruments the
>> classes,
>> > instrumented classes are saved to target/generated-classes/cobertura,
>> and
>> > executes unit tests. Instrumented classes dump coverage data to
>> > target/conbertura/cobertura.ser. There are two things to understand:
>> >
>> > 1. When cobertura:cobertura is executed, dependencies are not
>> instrumented.
>> > You have to have enabled instrumentation, see cobertura:instrument
>> goal.
>> > This will produce jars with instrumented classes, so be careful not to
>> > distribute them.
>> > 2. Each module will write coverage data to it's own
>> > target/conbertura/cobertura.ser file. I think it's possible to
>> configure
>> > instrumentation so that all jars write to the same cobertura.ser file,
>> but
>> > I don't know whether it's normal, and I never tried that.
>> >
>> >
>> I want to say that there's a cobertura target.  Something like
>> cobertura:aggregate that will combine the results off all the unit
>> tests,
>> for the module that's being tested.  That probably won't be what you
>> want,
>> but I think it would be a lot closer.  This is all from memory though,
>> so
>> make sure to check it's actually what you want.
>>
>



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Code coverage report for multi module maven project reports zero in some modules

[Aliaksei Lahachou]

Aggregated cobertura report will execute cobertura on each module and then
merge the single reports. It will not help if, for example, you have tests
in module A and want to have coverage of module B.


On Sat, Jun 30, 2012 at 10:46 AM, Patrick Mohr  wrote:

> On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
> aliaksei.lahac...@gmail.com> wrote:
>
> > Hi!
> >
> > cobertura:cobertura executes it's own lifecycle: instruments the classes,
> > instrumented classes are saved to target/generated-classes/cobertura, and
> > executes unit tests. Instrumented classes dump coverage data to
> > target/conbertura/cobertura.ser. There are two things to understand:
> >
> > 1. When cobertura:cobertura is executed, dependencies are not
> instrumented.
> > You have to have enabled instrumentation, see cobertura:instrument goal.
> > This will produce jars with instrumented classes, so be careful not to
> > distribute them.
> > 2. Each module will write coverage data to it's own
> > target/conbertura/cobertura.ser file. I think it's possible to configure
> > instrumentation so that all jars write to the same cobertura.ser file,
> but
> > I don't know whether it's normal, and I never tried that.
> >
> >
> I want to say that there's a cobertura target.  Something like
> cobertura:aggregate that will combine the results off all the unit tests,
> for the module that's being tested.  That probably won't be what you want,
> but I think it would be a lot closer.  This is all from memory though, so
> make sure to check it's actually what you want.
>

Re: Code coverage report for multi module maven project reports zero in some modules

[Patrick Mohr]

On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
aliaksei.lahac...@gmail.com> wrote:

> Hi!
>
> cobertura:cobertura executes it's own lifecycle: instruments the classes,
> instrumented classes are saved to target/generated-classes/cobertura, and
> executes unit tests. Instrumented classes dump coverage data to
> target/conbertura/cobertura.ser. There are two things to understand:
>
> 1. When cobertura:cobertura is executed, dependencies are not instrumented.
> You have to have enabled instrumentation, see cobertura:instrument goal.
> This will produce jars with instrumented classes, so be careful not to
> distribute them.
> 2. Each module will write coverage data to it's own
> target/conbertura/cobertura.ser file. I think it's possible to configure
> instrumentation so that all jars write to the same cobertura.ser file, but
> I don't know whether it's normal, and I never tried that.
>
>
I want to say that there's a cobertura target.  Something like
cobertura:aggregate that will combine the results off all the unit tests,
for the module that's being tested.  That probably won't be what you want,
but I think it would be a lot closer.  This is all from memory though, so
make sure to check it's actually what you want.

Re: Code coverage report for multi module maven project reports zero in some modules

[Aliaksei Lahachou]

Hi!

cobertura:cobertura executes it's own lifecycle: instruments the classes,
instrumented classes are saved to target/generated-classes/cobertura, and
executes unit tests. Instrumented classes dump coverage data to
target/conbertura/cobertura.ser. There are two things to understand:

1. When cobertura:cobertura is executed, dependencies are not instrumented.
You have to have enabled instrumentation, see cobertura:instrument goal.
This will produce jars with instrumented classes, so be careful not to
distribute them.
2. Each module will write coverage data to it's own
target/conbertura/cobertura.ser file. I think it's possible to configure
instrumentation so that all jars write to the same cobertura.ser file, but
I don't know whether it's normal, and I never tried that. When you have
multiple cobertura.ser files, you can merge them with ant script and
generate report from the merged file.

Check build-configurator project [1], it does what you need. I used
instructions from cobertura-maven-plugin to configure the build [2].

[1] https://github.com/htfv/build-configurator
[2]
http://mojo.codehaus.org/cobertura-maven-plugin/instrumentingDeploymentArtifact.html


Regards,
htfv (Aliaksei Lahachou)


On Sat, Jun 30, 2012 at 4:07 AM,  wrote:

> Hi,
>
> I am trying to generate code coverage report for our multi-module maven
> project using cobertura. After I run mvn package, in one of the modules
> from where we run JUnit tests, the coverage report is correct as expected.
>
> However, coverage report generated in the other
> /target/site/cobertura directories is reported as zero for
> both line and branch coverage.
>
> Am I missing something, in my parent POM, I have not made any changes to
> any of the child POMs in the  directories. Please let me know
> how to generate the code coverage report for a multi module maven project
> using cobertura.
>
> Here is how my parent POM looks like.
>
> 
> org.codehaus.mojo
> cobertura-maven-plugin
> 2.5.1
>  
> 
> html
> xml
> 
>  
>  true
>  
>  
>  package
>  
>  cobertura
>  
>  
>  
> 
>
> ...
> 
> 
> org.codehaus.mojo
> cobertura-maven-plugin
> 2.5.1
> plugin
> package
> 
> 
>
> Thanks!
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Code coverage report for multi module maven project reports zero in some modules

[kfmohamm]

Hi,

I am trying to generate code coverage report for our multi-module maven
project using cobertura. After I run mvn package, in one of the modules
from where we run JUnit tests, the coverage report is correct as expected.

However, coverage report generated in the other
/target/site/cobertura directories is reported as zero for
both line and branch coverage.

Am I missing something, in my parent POM, I have not made any changes to
any of the child POMs in the  directories. Please let me know
how to generate the code coverage report for a multi module maven project
using cobertura.

Here is how my parent POM looks like.


org.codehaus.mojo
cobertura-maven-plugin
2.5.1
 

html
xml

 
 true
 
 
 package
 
 cobertura
 
 
 


...


org.codehaus.mojo
cobertura-maven-plugin
2.5.1
plugin
package



Thanks!


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problem with Maven Project Info Reports Plugin in maven 3

[Subash Chaturanga]

This is the log I see when maven reports info plugin runs at second time in
single build command

Building index for all the packages and classes...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/overview-tree.html...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/index-all.html...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/deprecated-list.html...
Building index for all classes...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/allclasses-frame.html...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/allclasses-noframe.html...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/index.html...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/overview-summary.html...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/help-doc.html...
Generating
/home/subash/development/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/target/site/testapidocs/stylesheet.css...
[INFO] Generating "Distribution Management" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "About" report---
maven-project-info-reports-plugin:2.4
[INFO] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.4
[WARNING] The repository url 'https://repository.jboss.org/maven2/' is
invalid - Repository 'jboss-deprecated-repository' will be blacklisted.


...*and buid hangs*.

Can we stop this running second time ?

On Wed, Mar 21, 2012 at 9:47 PM, Subash Chaturanga wrote:

> Hi Likas,
>
> Thank you very much for the quick response.
>
> Your first link is the way I implemented the pom in maven 2. So I followed
> one of the methods in the link you provided.  According to following
> configuration I must get only the specified reports in the site. But maven
> tries to generate all reports including dependencies .
>
> NOTE: I found this log : [INFO] plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin will be executed
> more than one time
> I think this is what causing. Any idea ?
>
>
> *My pom config*
> *
> *
> 
> org.apache.maven.plugins
> maven-site-plugin
> 3.0
> 
> 
> package
> 
> site
> 
>     
> 
> 
> org.apache.maven.plugins
>
> maven-project-info-reports-plugin
> 2.4
> 
> 
> 
> project-team
> mailing-list
> issue-tracking
> license
> 
> 
> 
> 
> 
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.8
> 
> 
> 
> 
> 
> 
>
>
> Thanks
> /subash
>



-- 
Subash Chaturanga
Department of Computer Science & Engineering
University of Moratuwa
Sri Lanka

Blog -  http://subashsdm.blogspot.com/
Twitter - http://twitter.com/subash89

Re: Problem with Maven Project Info Reports Plugin in maven 3

[Lukas Theussl]

http://maven.apache.org/plugins/maven-project-info-reports-plugin/examples/selective-project-info-reports.html

Note the different reporting configuration in maven 3:

http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Configuration_formats

HTH,
-Lukas


Subash Chaturanga wrote:

Hi all,

NOTE : In other words, in my maven-project-info-reports-plugin, it
generates following.(as logs indicates). I want to remove generating  two
of them.
Which are *"Dependency Management*" report  and *"Dependencies"* report .
  It will be great if anybody can provide me a solution.

[INFO] Generating "About" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Source Repository" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Issue Tracking" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project Plugins" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project Summary" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "*Dependency Management*" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating *"Dependencies"* report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project License" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Continuous Integration" report---
maven-project-info-reports-plugin:2.2

On Wed, Mar 21, 2012 at 2:49 PM, Subash Chaturangawrote:


Hi all,
I am using maven 3.

In Maven Project Info Reports Plugin (version 2.4), I am having problems
in report generating. I found out that, the reason cause of report
generation related to dependency management .

Because in maven-project-info-reports-plugin they have several goals
running and one of them, which is unnecessary for me is
  "project-info-reports:dependency-management"  which
causing me trouble (hangs the build for 4-5 mins saying "[WARNING] The
repository url 'https://repository.jboss.org/maven2/' is invalid -
Repository 'jboss-deprecated-repository' will be blacklisted.").

Is there a way to exclude an goal from the project-info-reports plugin to
get rid from this issue.
(i.e project-info-reports:dependency-management)

Thanks
/Subash







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problem with Maven Project Info Reports Plugin in maven 3

[Subash Chaturanga]

Hi all,

NOTE : In other words, in my maven-project-info-reports-plugin, it
generates following.(as logs indicates). I want to remove generating  two
of them.
Which are *"Dependency Management*" report  and *"Dependencies"* report .
 It will be great if anybody can provide me a solution.

[INFO] Generating "About" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Source Repository" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Issue Tracking" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project Plugins" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project Summary" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "*Dependency Management*" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating *"Dependencies"* report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project License" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.2
[INFO] Generating "Continuous Integration" report---
maven-project-info-reports-plugin:2.2

On Wed, Mar 21, 2012 at 2:49 PM, Subash Chaturanga wrote:

> Hi all,
> I am using maven 3.
>
> In Maven Project Info Reports Plugin (version 2.4), I am having problems
> in report generating. I found out that, the reason cause of report
> generation related to dependency management .
>
> Because in maven-project-info-reports-plugin they have several goals
> running and one of them, which is unnecessary for me is
>  "project-info-reports:dependency-management"  which
> causing me trouble (hangs the build for 4-5 mins saying "[WARNING] The
> repository url 'https://repository.jboss.org/maven2/' is invalid -
> Repository 'jboss-deprecated-repository' will be blacklisted.").
>
> Is there a way to exclude an goal from the project-info-reports plugin to
> get rid from this issue.
> (i.e project-info-reports:dependency-management)
>
> Thanks
> /Subash




-- 
Subash Chaturanga
Department of Computer Science & Engineering
University of Moratuwa
Sri Lanka

Blog -  http://subashsdm.blogspot.com/
Twitter - http://twitter.com/subash89

Problem with Maven Project Info Reports Plugin in maven 3

[Subash Chaturanga]

Hi all,
I am using maven 3.

In Maven Project Info Reports Plugin (version 2.4), I am having problems in
report generating. I found out that, the reason cause of report generation
related to dependency management .

Because in maven-project-info-reports-plugin they have several goals
running and one of them, which is unnecessary for me is
 "project-info-reports:dependency-management"  which
causing me trouble (hangs the build for 4-5 mins saying "[WARNING] The
repository url 'https://repository.jboss.org/maven2/' is invalid -
Repository 'jboss-deprecated-repository' will be blacklisted.").

Is there a way to exclude an goal from the project-info-reports plugin to
get rid from this issue.
(i.e project-info-reports:dependency-management)

Thanks
/Subash

Surefire + failsafe plugins - how to generate reports?

[Miguel Almeida]

Dear all,

I was using surefire-report to test my multi-module Maven project, by
running the goal "clean surefire-report:report" on the parent project.

However, some Cucumber BDD tests were slowing the tests down (4+ minutes),
which is not good if we want devs to run them frequently. Ideally, what I
want is:
- quick set of tests run locally
- full set of tests run in CI (Jenkins)

I decided to try the failsafe plugin, so I changed one test from
Acceptance_Test to Acceptance_IT and added the following in the parent pom.


> org.apache.maven.plugins
> maven-failsafe-plugin
> 2.12
> 
> 
> integration-test
> 
> integration-test
> verify
> 
> 
> 
> 
>

Sure enough, mvn verify runs the IT test and surefire-report:report (or mvn
site) runs the other ones.

I added the following [1] to the reportPlugins section of the
maven-site-plugin, but if I run "mvn site" I don't see my integration tests
in the [each_module]/target/site/surefire-report.html document, nor in
[each_module]/target/surefire-reports

[1] - section of the maven-site-plugin configuration

> 
> org.apache.maven.plugins
>
> maven-surefire-report-plugin
> 2.12
> 
> 
> unit
> 
> report
> 
> 
> 
> integration-tests
> 
>
> failsafe-report-only
> 
> 
> 
> 
>


My questions are:
1) *which goal(s) do I have to run to have an html report for both sets of
tests?*
2) *Will it be one report with all tests, or two separate reports?*

I also have a couple of questions regarding the different goals run in CI
(I take it I should run all the goals in CI and only surefire:report on
developer's machines) and how Cobertura is affected by this (I read that
code coverage won't take into consideration the failsafe tests, even though
it should in the CI server), but I'll tackle one problem at a time.

I appreciate your help,

Miguel Almeida

Re: maven-failsafe-plugin incorrect reports when running parallel tests

[Kristian Rosenvold]

http://jira.codehaus.org/browse/SUREFIRE

2012/2/23 Christian Schlichtherle :
> Because this issue persists, where should I file a bug report?
>
> Regards,
> Christian
>
>> -Ursprüngliche Nachricht-
>> Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no]
>> Im Auftrag von Kristian Rosenvold
>> Gesendet: Dienstag, 7. Februar 2012 21:15
>> An: Maven Users List; christ...@schlichtherle.de
>> Betreff: Re: maven-failsafe-plugin incorrect reports when running
>> parallel tests
>>
>> I have looked through all our current integration tests regarding
>> failing of build with failsafe, and they all seem to be ok.
>>
>> You have probably uncovered some unknown problem, and I request that
>> you do the following:
>>
>> svn co https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-
>> integration-tests/src/test/resources/failsafe-buildfail/
>> cd failsafe-buildfail
>> mvn -Dsurefire.version=2.12 verify
>>
>> Form that point on I'd be really happy if you could try to modify this
>> project to reproduce the failure, and in that case please submit the
>> modified project attached to a jira.
>>
>> I also just updated the developer guides on how to attach a debugger to
>> the fork, which may be just as simple:
>> http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-
>> plugin/src/site/apt/developing.apt.vm?view=markup
>>
>> Kristian
>>
>> 2012/2/7 Christian Schlichtherle :
>> > Hi,
>> >
>> > I have now run the integration test suite with plugin version 2.10
>> and
>> > it always fails. So the results are:
>> >
>> > V2.10: Always fails => correct behavior.
>> > V2.11: Always fails => correct behavior.
>> > V2.12: Always passes => wrong behavior.
>> >
>> > The configuration is the same as before.
>> >
>> > Enclosed is a unified diff of the output from the following command
>> line:
>> >
>> >        mvn install -Pintegration-test --debug
>> >
>> > between plugin version 2.11 and 2.12. I could find nothing unexpected
>> in it.
>> >
>> > Regards,
>> > Christian
>> >
>> >> -Ursprüngliche Nachricht-
>> >> Von: kristian.rosenv...@zenior.no
>> >> [mailto:kristian.rosenv...@zenior.no]
>> >> Im Auftrag von Kristian Rosenvold
>> >> Gesendet: Dienstag, 7. Februar 2012 18:30
>> >> An: Maven Users List; christ...@schlichtherle.de
>> >> Betreff: Re: maven-failsafe-plugin incorrect reports when running
>> >> parallel tests
>> >>
>> >> The thing is, you might be hitting two different problems, which is
>> >> where I'd really like for you to test 2.10. 2.11 had a *known*
>> >> problem with certain classloading combinations, which could cause
>> all
>> >> tests to fail (basically all or nothing, but it would only be
>> hitting
>> >> users with specific libs/deps).
>> >>
>> >> Now this was fixed in 2.12, but SUREFIRE-803 (2.12) does some
>> changes
>> >> to the failure detection algorithm in failsafe, which may be the
>> >> cause of some other problem. We have decent test coverage of these
>> >> things but there's always the chance of some uncovered corner-case.
>> >>
>> >> AFIK 2.10 could be used to benchmark the behaviour of your current
>> >> tests.
>> >>
>> >>
>> >> Kristian
>> >>
>> >> 2012/2/7 Christian Schlichtherle :
>> >> > Hi Kristian,
>> >> >
>> >> > I've investigated the subject a little more. For both plugin
>> >> versions,
>> >> > I use the same configuration (confirmed by both help:effective-pom
>> >> xor
>> >> > the --debug
>> >> > option):
>> >> >
>> >> > forkMode=once
>> >> > parallel=both
>> >> > useSystemClassLoader=true
>> >> >
>> >> > I also wrote a little test class with two test methods which both
>> >> > simply log the System.identityHashCode() for the test class and
>> its
>> >> > class loader. With both plugin versions, both test method
>> >> > executions report the same class and classloader instance.
>> >> >
>> >> > Yet, with version 2.11 my integration test suite always fails and
>> >> with
>> >> > 

AW: maven-failsafe-plugin incorrect reports when running parallel tests

[Christian Schlichtherle]

Because this issue persists, where should I file a bug report?

Regards,
Christian

> -Ursprüngliche Nachricht-
> Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no]
> Im Auftrag von Kristian Rosenvold
> Gesendet: Dienstag, 7. Februar 2012 21:15
> An: Maven Users List; christ...@schlichtherle.de
> Betreff: Re: maven-failsafe-plugin incorrect reports when running
> parallel tests
> 
> I have looked through all our current integration tests regarding
> failing of build with failsafe, and they all seem to be ok.
> 
> You have probably uncovered some unknown problem, and I request that
> you do the following:
> 
> svn co https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-
> integration-tests/src/test/resources/failsafe-buildfail/
> cd failsafe-buildfail
> mvn -Dsurefire.version=2.12 verify
> 
> Form that point on I'd be really happy if you could try to modify this
> project to reproduce the failure, and in that case please submit the
> modified project attached to a jira.
> 
> I also just updated the developer guides on how to attach a debugger to
> the fork, which may be just as simple:
> http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-
> plugin/src/site/apt/developing.apt.vm?view=markup
> 
> Kristian
> 
> 2012/2/7 Christian Schlichtherle :
> > Hi,
> >
> > I have now run the integration test suite with plugin version 2.10
> and
> > it always fails. So the results are:
> >
> > V2.10: Always fails => correct behavior.
> > V2.11: Always fails => correct behavior.
> > V2.12: Always passes => wrong behavior.
> >
> > The configuration is the same as before.
> >
> > Enclosed is a unified diff of the output from the following command
> line:
> >
> >        mvn install -Pintegration-test --debug
> >
> > between plugin version 2.11 and 2.12. I could find nothing unexpected
> in it.
> >
> > Regards,
> > Christian
> >
> >> -Ursprüngliche Nachricht-
> >> Von: kristian.rosenv...@zenior.no
> >> [mailto:kristian.rosenv...@zenior.no]
> >> Im Auftrag von Kristian Rosenvold
> >> Gesendet: Dienstag, 7. Februar 2012 18:30
> >> An: Maven Users List; christ...@schlichtherle.de
> >> Betreff: Re: maven-failsafe-plugin incorrect reports when running
> >> parallel tests
> >>
> >> The thing is, you might be hitting two different problems, which is
> >> where I'd really like for you to test 2.10. 2.11 had a *known*
> >> problem with certain classloading combinations, which could cause
> all
> >> tests to fail (basically all or nothing, but it would only be
> hitting
> >> users with specific libs/deps).
> >>
> >> Now this was fixed in 2.12, but SUREFIRE-803 (2.12) does some
> changes
> >> to the failure detection algorithm in failsafe, which may be the
> >> cause of some other problem. We have decent test coverage of these
> >> things but there's always the chance of some uncovered corner-case.
> >>
> >> AFIK 2.10 could be used to benchmark the behaviour of your current
> >> tests.
> >>
> >>
> >> Kristian
> >>
> >> 2012/2/7 Christian Schlichtherle :
> >> > Hi Kristian,
> >> >
> >> > I've investigated the subject a little more. For both plugin
> >> versions,
> >> > I use the same configuration (confirmed by both help:effective-pom
> >> xor
> >> > the --debug
> >> > option):
> >> >
> >> > forkMode=once
> >> > parallel=both
> >> > useSystemClassLoader=true
> >> >
> >> > I also wrote a little test class with two test methods which both
> >> > simply log the System.identityHashCode() for the test class and
> its
> >> > class loader. With both plugin versions, both test method
> >> > executions report the same class and classloader instance.
> >> >
> >> > Yet, with version 2.11 my integration test suite always fails and
> >> with
> >> > version 2.12 it always passes.
> >> >
> >> > Now what concerns me is that I wouldn't have noticed that there
> are
> >> > issues in my code under test if I had started to use
> >> > maven-failsafe-plugin with version 2.12.
> >> >
> >> > My integration test suite is large and long running, so I can be
> >> > fairly sure it always fails as long as the multithreading issue(s)
> >> > exist(s) in my code under te

Re: maven-failsafe-plugin incorrect reports when running parallel tests

[Kristian Rosenvold]

I have looked through all our current integration tests regarding
failing of build with failsafe, and they all seem to be ok.

You have probably uncovered some unknown problem, and I request that
you do the following:

svn co 
https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources/failsafe-buildfail/
cd failsafe-buildfail
mvn -Dsurefire.version=2.12 verify

Form that point on I'd be really happy if you could try to modify this
project to reproduce the failure, and in that case please submit the
modified project attached to a jira.

I also just updated the developer guides on how to attach a debugger
to the fork, which may be just as simple:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-plugin/src/site/apt/developing.apt.vm?view=markup

Kristian

2012/2/7 Christian Schlichtherle :
> Hi,
>
> I have now run the integration test suite with plugin version 2.10 and it
> always fails. So the results are:
>
> V2.10: Always fails => correct behavior.
> V2.11: Always fails => correct behavior.
> V2.12: Always passes => wrong behavior.
>
> The configuration is the same as before.
>
> Enclosed is a unified diff of the output from the following command line:
>
>        mvn install -Pintegration-test --debug
>
> between plugin version 2.11 and 2.12. I could find nothing unexpected in it.
>
> Regards,
> Christian
>
>> -Ursprüngliche Nachricht-
>> Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no]
>> Im Auftrag von Kristian Rosenvold
>> Gesendet: Dienstag, 7. Februar 2012 18:30
>> An: Maven Users List; christ...@schlichtherle.de
>> Betreff: Re: maven-failsafe-plugin incorrect reports when running
>> parallel tests
>>
>> The thing is, you might be hitting two different problems, which is
>> where I'd really like for you to test 2.10. 2.11 had a *known* problem
>> with certain classloading combinations, which could cause all tests to
>> fail (basically all or nothing, but it would only be hitting users with
>> specific libs/deps).
>>
>> Now this was fixed in 2.12, but SUREFIRE-803 (2.12) does some changes
>> to the failure detection algorithm in failsafe, which may be the cause
>> of some other problem. We have decent test coverage of these things but
>> there's always the chance of some uncovered corner-case.
>>
>> AFIK 2.10 could be used to benchmark the behaviour of your current
>> tests.
>>
>>
>> Kristian
>>
>> 2012/2/7 Christian Schlichtherle :
>> > Hi Kristian,
>> >
>> > I've investigated the subject a little more. For both plugin
>> versions,
>> > I use the same configuration (confirmed by both help:effective-pom
>> xor
>> > the --debug
>> > option):
>> >
>> > forkMode=once
>> > parallel=both
>> > useSystemClassLoader=true
>> >
>> > I also wrote a little test class with two test methods which both
>> > simply log the System.identityHashCode() for the test class and its
>> > class loader. With both plugin versions, both test method executions
>> > report the same class and classloader instance.
>> >
>> > Yet, with version 2.11 my integration test suite always fails and
>> with
>> > version 2.12 it always passes.
>> >
>> > Now what concerns me is that I wouldn't have noticed that there are
>> > issues in my code under test if I had started to use
>> > maven-failsafe-plugin with version 2.12.
>> >
>> > My integration test suite is large and long running, so I can be
>> > fairly sure it always fails as long as the multithreading issue(s)
>> > exist(s) in my code under test. I also know that the issue(s) in my
>> > code under test are not classic racing conditions for objects on the
>> > heap, but a failure to properly deal with some IOExceptions when
>> > concurrently accessing shared file system resources.
>> >
>> > Regards,
>> > Christian
>> >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: users-h...@maven.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-failsafe-plugin incorrect reports when running parallel tests

[Kristian Rosenvold]

The thing is, you might be hitting two different problems, which is
where I'd really like for you to test 2.10. 2.11 had a *known* problem
with certain classloading combinations, which could cause all tests to
fail (basically all or nothing, but it would only be hitting users
with specific libs/deps).

Now this was fixed in 2.12, but SUREFIRE-803 (2.12) does some changes to
the failure detection algorithm in failsafe, which may be the cause of
some other problem. We have decent test coverage of these things but
there's always the
chance of some uncovered corner-case.

AFIK 2.10 could be used to benchmark the behaviour of your current tests.


Kristian

2012/2/7 Christian Schlichtherle :
> Hi Kristian,
>
> I've investigated the subject a little more. For both plugin versions, I use
> the same configuration (confirmed by both help:effective-pom xor the --debug
> option):
>
> forkMode=once
> parallel=both
> useSystemClassLoader=true
>
> I also wrote a little test class with two test methods which both simply log
> the System.identityHashCode() for the test class and its class loader. With
> both plugin versions, both test method executions report the same class and
> classloader instance.
>
> Yet, with version 2.11 my integration test suite always fails and with
> version 2.12 it always passes.
>
> Now what concerns me is that I wouldn't have noticed that there are issues
> in my code under test if I had started to use maven-failsafe-plugin with
> version 2.12.
>
> My integration test suite is large and long running, so I can be fairly sure
> it always fails as long as the multithreading issue(s) exist(s) in my code
> under test. I also know that the issue(s) in my code under test are not
> classic racing conditions for objects on the heap, but a failure to properly
> deal with some IOExceptions when concurrently accessing shared file system
> resources.
>
> Regards,
> Christian
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

AW: maven-failsafe-plugin incorrect reports when running parallel tests

[Christian Schlichtherle]

Hi Kristian,

I've investigated the subject a little more. For both plugin versions, I use
the same configuration (confirmed by both help:effective-pom xor the --debug
option):

forkMode=once
parallel=both
useSystemClassLoader=true

I also wrote a little test class with two test methods which both simply log
the System.identityHashCode() for the test class and its class loader. With
both plugin versions, both test method executions report the same class and
classloader instance.

Yet, with version 2.11 my integration test suite always fails and with
version 2.12 it always passes.

Now what concerns me is that I wouldn't have noticed that there are issues
in my code under test if I had started to use maven-failsafe-plugin with
version 2.12.

My integration test suite is large and long running, so I can be fairly sure
it always fails as long as the multithreading issue(s) exist(s) in my code
under test. I also know that the issue(s) in my code under test are not
classic racing conditions for objects on the heap, but a failure to properly
deal with some IOExceptions when concurrently accessing shared file system
resources.

Regards,
Christian



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-failsafe-plugin incorrect reports when running parallel tests

[Kristian Rosenvold]

Depending on your forkMode, there was a classloading issue in 2.11
that caused tests to fail (works in all other versions).

(That was SUREFIRE-804, there may have been other permutations of
forkMode/useSystemClassLoader that were affected, I tested/closed a
few duplicates on this one)

As for threading issues, most of them are of intermittent characters,
so I will assume any consistent failures would be due to something
like 804.

Kristian


2012/2/7 Christian Schlichtherle :
> Hi everyone,
>
>
>
> I recently added maven-failsafe-plugin version 2.11 to my build. When
> running the integration tests in parallel it always reports test failures.
>
>
>
> Now I have changed to version 2.12 and all of a sudden my test suite passes
> without failures although I know that there are some multithreading issues
> in my code.
>
>
>
> When changing back to version 2.11 I get the test failures again as before.
>
>
>
> So I wonder if there have been changes to the class loading between 2.11 and
> 2.12? I suspect that a separate class instance is used for each test with
> 2.12. This would explain why it passes the test suite all of a sudden.
>
>
>
> Looking up the plugin site and JIRA change log has revealed no evidence of
> this, however.
>
>
>
> Regards,
>
> Christian Schlichtherle
>
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven-failsafe-plugin incorrect reports when running parallel tests

[Christian Schlichtherle]

Hi everyone,

 

I recently added maven-failsafe-plugin version 2.11 to my build. When
running the integration tests in parallel it always reports test failures.

 

Now I have changed to version 2.12 and all of a sudden my test suite passes
without failures although I know that there are some multithreading issues
in my code.

 

When changing back to version 2.11 I get the test failures again as before.

 

So I wonder if there have been changes to the class loading between 2.11 and
2.12? I suspect that a separate class instance is used for each test with
2.12. This would explain why it passes the test suite all of a sudden.

 

Looking up the plugin site and JIRA change log has revealed no evidence of
this, however.

 

Regards,

Christian Schlichtherle

 

Enhancing testcase elements in surefire xml reports with custom attributes specified by annotations?

[Mirko Friedenhagen]

Hello,

we use Testlink for describing testcases, some of which are run as
automatic tests using junit. Now to easily match junit tests to
Testlink IDs I thought about adding an annotation like:
@TestlinkID(12345)
to tests run, which should result in something like:



Right now we use an approach of suffixing out method names with the
testlink ID and afterwards parse the results, which feels kind of
clumsy.
Looking into org.apache.maven.surefire.report.XMLReporter there seems
no easy way to extend the reporter to include additional information
like this.

Any suggestions?

Regards Mirko
-- 
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: reports inheritance - parent can disinherit, can child refuse to inherit?

[sebb]

On 10 September 2011 15:39, Hervé BOUTEMY  wrote:
> no, the child can override, that's all

Don't understand what you mean by that.

> see MNG-2807 for the same about CI management, or MNG-3124 for mailing lists
>
> there is an inheritance configuration pattern to find then apply on many
> elements of the pom.
> If you have an idea about something easyto understand from a user
> perspective...

The parent can currently do the following to prevent all inheritance

  


   org.apache.maven.plugins
   maven-project-info-reports-plugin
   false
   

However, that does not allow some reports to apply to the parent only;
it is all or nothing.

Although the  element is also allowed within a reportSet,
that does not seem to prevent the reports from being generated in
Maven 2.2.1.
[seems to work in M303, provided that the  is omiitted or has the
value "default" (which is the default) ]

There ought to be a way for the parent to specify its own private
reports separately from the reports that should be inherited.

If the reportSet/ element worked properly, that would solve
the issue for the parent.

Being able to configure the parent to pass on some reports but not
others would be helpful in many cases, but equally, its children
should be able to refuse reports specified by the parent.

Perhaps the combine.children/combine.self configuration attribute
could be extended to reportSet?

S
P.S.
Unfortunately, the word "inherited" is ambiguous; in this case it
means "will it be inherited", rather than the usual spoken meaning as
in "the child inherited from its parent".  It would perhaps have been
clearer if the element was called "inheritable"; the child version
could then be called "inherit".
But I think that would be too confusing now.

> Regards,
>
> Hervé
>
> Le samedi 10 septembre 2011, sebb a écrit :
>> [This mainly applies to the project-info-reports plugin]
>>
>> The reporting/plugins/plugin entries support the  element;
>> if set to false, child projects don't inherit the plugin settings,
>> i.e. the parent can disinherit the child.
>>
>> Is the reverse also possible, i.e. given a parent pom, can a child
>> reporting plugin refuse to inherit from its parent?
>>
>> For example, if the parent and most children need the same set of
>> reports, but one child does not need some of the reports.
>>
>> This does not appear to be possible except by defining the required
>> set of reports in each project, parent included.
>> The parent config has to disinherit the children, otherwise they will
>> all get the full set of reports.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: reports inheritance - parent can disinherit, can child refuse to inherit?

[Hervé BOUTEMY]

no, the child can override, that's all

see MNG-2807 for the same about CI management, or MNG-3124 for mailing lists

there is an inheritance configuration pattern to find then apply on many 
elements of the pom.
If you have an idea about something easyto understand from a user 
perspective...

Regards,

Hervé

Le samedi 10 septembre 2011, sebb a écrit :
> [This mainly applies to the project-info-reports plugin]
> 
> The reporting/plugins/plugin entries support the  element;
> if set to false, child projects don't inherit the plugin settings,
> i.e. the parent can disinherit the child.
> 
> Is the reverse also possible, i.e. given a parent pom, can a child
> reporting plugin refuse to inherit from its parent?
> 
> For example, if the parent and most children need the same set of
> reports, but one child does not need some of the reports.
> 
> This does not appear to be possible except by defining the required
> set of reports in each project, parent included.
> The parent config has to disinherit the children, otherwise they will
> all get the full set of reports.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

reports inheritance - parent can disinherit, can child refuse to inherit?

[sebb]

[This mainly applies to the project-info-reports plugin]

The reporting/plugins/plugin entries support the  element;
if set to false, child projects don't inherit the plugin settings,
i.e. the parent can disinherit the child.

Is the reverse also possible, i.e. given a parent pom, can a child
reporting plugin refuse to inherit from its parent?

For example, if the parent and most children need the same set of
reports, but one child does not need some of the reports.

This does not appear to be possible except by defining the required
set of reports in each project, parent included.
The parent config has to disinherit the children, otherwise they will
all get the full set of reports.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Project reports customBundle - how to share across multiple modules

[sebb]

On 31 August 2011 13:25, Olivier Lamy  wrote:
> 2011/8/31 sebb :
>> On 31 August 2011 11:27, Olivier Lamy  wrote:
>>> 2011/8/31 sebb :
>>>> On 31 August 2011 08:29, Olivier Lamy  wrote:
>>>>> Hello,
>>>>> The solution I see is to have an artifact (call it build-resources or
>>>>> something like that) which contains those .properties
>>>>
>>>> The modules all have a common parent pom - is it possible to use that
>>>> to contain the resources, rather than creating another module?
>>>>
>>>>> And use it tru remote-resources or dependency plugin.
>>>>
>>>> The remote-resources sharing example shows that the resources will be
>>>> made available under
>>>>
>>>> ${project.build.directory}/maven-shared-archive-resources
>>>>
>>>> but the reports customBundle expects to find the file under
>>>>
>>>> ${project.basedir}/src/site/custom/project-info-report.properties
>>>>
>>>> Looks like I would also have to configure the reports to pick up the
>>>> custom bundle from elsewhere, or change the outputDirectory (but that
>>>> would probably mess up the packaging/assembly phases).
>>>>
>>>> Seems simpler to just create copies of the bundle in each module in
>>>> the first place.
>>>>
>>>> I'm not sure how to use the dependency plugin - how do I configure the
>>>> reports to pick up the properties from a jar?
>>>
>>> use the dependency to unpack you properties file from your
>>> artifact/jar to a dedicated path in your project.
>>
>> I see - much the same as using remote-resources to unpack the file.
>>
>>> Then configure the mojo.
>>>
>>>      
>>>        org.apache.maven.plugins
>>>        maven-project-info-reports-plugin
>>>        
>>>          path to unpacked properties file
>>>        
>>>      
>>>
>>> IMHO a little complicated and a lot of xml to write but should work
>>> (not tested).
>>
>> I assume that the report mojo can be configured once in the parent?``
> Yup as other plugins configured it's inherited
>> Otherwise it's a lot more work.
>>
>> And each module has to unpack the file locally.
>>
>>> I would prefer add a feature for the maven-project-info-reports-plugin
>>> (and maybe others) to be able to load properties file from
>>> artifact/jar with adding this artifact/jar in the plugin
>>> configuration.
>>>
>>>      
>>>        org.apache.maven.plugins
>>>        maven-project-info-reports-plugin
>>>        
>>>          
>>>            org.foo:my-properties:1.0
>>>            path in the jar
>>>          
>>>        
>>>      
>>>
>>> Makes sense ? (less xml than using dependency unpack)
>>
>> This is a generic solution and would simplify the process somewhat,
>> but one would still have to create and deploy the properties artifact.
>>
>> I would expect the reports plugin to be able to inherit properties
>> directly from the parent pom.
>>
>> Rather like the site.xml can be inherited.
>
> AFAIK site descriptor is an "artifact" which is deployed too.
> So the site plugin use the parent if found in the path tree if not one
> the needed one is downloaded.

Somehow the site.xml file is copied to the Maven repo alongside the POM.
This is presumably how it is found by depending projects.

Something similar needs to happen with the custom properties.

> In our case, I see an issue with the case of a classic svn tree.
>
> parent
>         /src/main/resources/mybundle.properties
>         child1
>
> With using ${project.basedir}/src/site/custom/project-info-report.properties
> a hack is possible to look at
> ${parent.baseDir}/src/site/custom/project-info-report.properties.
>
> This hack exists in the checkstyle plugin
> (http://jira.codehaus.org/browse/MCHECKSTYLE-131) but personnally I
> don't want to reproduce it.
> Because it doesn't work as maven does for everything else and cause
> some confusions.
>
> And what happend when checkout only the submodule child1 and not all
> the tree (your files won't be found).

Yes, that is a problem.

> See the case of the release plugin : only the submodule subtree is
> retrieve from svn this means your release will fail.
>
> And using a "build-tools-configuration" is IMHO a better way to do
> thi

Re: Project reports customBundle - how to share across multiple modules

[Olivier Lamy]

2011/8/31 sebb :
> On 31 August 2011 11:27, Olivier Lamy  wrote:
>> 2011/8/31 sebb :
>>> On 31 August 2011 08:29, Olivier Lamy  wrote:
>>>> Hello,
>>>> The solution I see is to have an artifact (call it build-resources or
>>>> something like that) which contains those .properties
>>>
>>> The modules all have a common parent pom - is it possible to use that
>>> to contain the resources, rather than creating another module?
>>>
>>>> And use it tru remote-resources or dependency plugin.
>>>
>>> The remote-resources sharing example shows that the resources will be
>>> made available under
>>>
>>> ${project.build.directory}/maven-shared-archive-resources
>>>
>>> but the reports customBundle expects to find the file under
>>>
>>> ${project.basedir}/src/site/custom/project-info-report.properties
>>>
>>> Looks like I would also have to configure the reports to pick up the
>>> custom bundle from elsewhere, or change the outputDirectory (but that
>>> would probably mess up the packaging/assembly phases).
>>>
>>> Seems simpler to just create copies of the bundle in each module in
>>> the first place.
>>>
>>> I'm not sure how to use the dependency plugin - how do I configure the
>>> reports to pick up the properties from a jar?
>>
>> use the dependency to unpack you properties file from your
>> artifact/jar to a dedicated path in your project.
>
> I see - much the same as using remote-resources to unpack the file.
>
>> Then configure the mojo.
>>
>>      
>>        org.apache.maven.plugins
>>        maven-project-info-reports-plugin
>>        
>>          path to unpacked properties file
>>        
>>      
>>
>> IMHO a little complicated and a lot of xml to write but should work
>> (not tested).
>
> I assume that the report mojo can be configured once in the parent?``
Yup as other plugins configured it's inherited
> Otherwise it's a lot more work.
>
> And each module has to unpack the file locally.
>
>> I would prefer add a feature for the maven-project-info-reports-plugin
>> (and maybe others) to be able to load properties file from
>> artifact/jar with adding this artifact/jar in the plugin
>> configuration.
>>
>>      
>>        org.apache.maven.plugins
>>        maven-project-info-reports-plugin
>>        
>>          
>>            org.foo:my-properties:1.0
>>            path in the jar
>>          
>>        
>>      
>>
>> Makes sense ? (less xml than using dependency unpack)
>
> This is a generic solution and would simplify the process somewhat,
> but one would still have to create and deploy the properties artifact.
>
> I would expect the reports plugin to be able to inherit properties
> directly from the parent pom.
>
> Rather like the site.xml can be inherited.

AFAIK site descriptor is an "artifact" which is deployed too.
So the site plugin use the parent if found in the path tree if not one
the needed one is downloaded.

In our case, I see an issue with the case of a classic svn tree.

parent
 /src/main/resources/mybundle.properties
 child1

With using ${project.basedir}/src/site/custom/project-info-report.properties
a hack is possible to look at
${parent.baseDir}/src/site/custom/project-info-report.properties.

This hack exists in the checkstyle plugin
(http://jira.codehaus.org/browse/MCHECKSTYLE-131) but personnally I
don't want to reproduce it.
Because it doesn't work as maven does for everything else and cause
some confusions.

And what happend when checkout only the submodule child1 and not all
the tree (your files won't be found).
See the case of the release plugin : only the submodule subtree is
retrieve from svn this means your release will fail.

And using a "build-tools-configuration" is IMHO a better way to do
this. As your configuration files will be reusable everywhere even
outside of the sources tree where they are located.
See sample here :
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html

If you have time to load a jira entry for the feature, I will work on.

>
>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend : http://talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> 2011/8/31 sebb :
>>>>> On 23 August 2011 14:43, sebb  wrote:
>>>>>> The default customBundle is located at
>>>>>>
>&

Re: Project reports customBundle - how to share across multiple modules

[sebb]

On 31 August 2011 11:27, Olivier Lamy  wrote:
> 2011/8/31 sebb :
>> On 31 August 2011 08:29, Olivier Lamy  wrote:
>>> Hello,
>>> The solution I see is to have an artifact (call it build-resources or
>>> something like that) which contains those .properties
>>
>> The modules all have a common parent pom - is it possible to use that
>> to contain the resources, rather than creating another module?
>>
>>> And use it tru remote-resources or dependency plugin.
>>
>> The remote-resources sharing example shows that the resources will be
>> made available under
>>
>> ${project.build.directory}/maven-shared-archive-resources
>>
>> but the reports customBundle expects to find the file under
>>
>> ${project.basedir}/src/site/custom/project-info-report.properties
>>
>> Looks like I would also have to configure the reports to pick up the
>> custom bundle from elsewhere, or change the outputDirectory (but that
>> would probably mess up the packaging/assembly phases).
>>
>> Seems simpler to just create copies of the bundle in each module in
>> the first place.
>>
>> I'm not sure how to use the dependency plugin - how do I configure the
>> reports to pick up the properties from a jar?
>
> use the dependency to unpack you properties file from your
> artifact/jar to a dedicated path in your project.

I see - much the same as using remote-resources to unpack the file.

> Then configure the mojo.
>
>      
>        org.apache.maven.plugins
>        maven-project-info-reports-plugin
>        
>          path to unpacked properties file
>        
>      
>
> IMHO a little complicated and a lot of xml to write but should work
> (not tested).

I assume that the report mojo can be configured once in the parent?
Otherwise it's a lot more work.

And each module has to unpack the file locally.

> I would prefer add a feature for the maven-project-info-reports-plugin
> (and maybe others) to be able to load properties file from
> artifact/jar with adding this artifact/jar in the plugin
> configuration.
>
>      
>        org.apache.maven.plugins
>        maven-project-info-reports-plugin
>        
>          
>            org.foo:my-properties:1.0
>            path in the jar
>          
>        
>      
>
> Makes sense ? (less xml than using dependency unpack)

This is a generic solution and would simplify the process somewhat,
but one would still have to create and deploy the properties artifact.

I would expect the reports plugin to be able to inherit properties
directly from the parent pom.

Rather like the site.xml can be inherited.

>>
>>> --
>>> Olivier Lamy
>>> Talend : http://talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> 2011/8/31 sebb :
>>>> On 23 August 2011 14:43, sebb  wrote:
>>>>> The default customBundle is located at
>>>>>
>>>>> ${project.basedir}/src/site/custom/project-info-report.properties
>>>>>
>>>>> which works fine for single module projects.
>>>>>
>>>>> However, it does not seem to work for multi-module projects.
>>>>>
>>>>> How can one share the same bundle between multiple modules?
>>>>>
>>>>> The modules all share a common parent, but do not seem to pick up the
>>>>> bundle from the parent.
>>>>
>>>> Anyone?
>>>>
>>>> Or is the only solution to duplicate the bundle in all projects?
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>
>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
>
>
> --
> Olivier Lamy
> Talend : http://talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Project reports customBundle - how to share across multiple modules

[Olivier Lamy]

2011/8/31 sebb :
> On 31 August 2011 08:29, Olivier Lamy  wrote:
>> Hello,
>> The solution I see is to have an artifact (call it build-resources or
>> something like that) which contains those .properties
>
> The modules all have a common parent pom - is it possible to use that
> to contain the resources, rather than creating another module?
>
>> And use it tru remote-resources or dependency plugin.
>
> The remote-resources sharing example shows that the resources will be
> made available under
>
> ${project.build.directory}/maven-shared-archive-resources
>
> but the reports customBundle expects to find the file under
>
> ${project.basedir}/src/site/custom/project-info-report.properties
>
> Looks like I would also have to configure the reports to pick up the
> custom bundle from elsewhere, or change the outputDirectory (but that
> would probably mess up the packaging/assembly phases).
>
> Seems simpler to just create copies of the bundle in each module in
> the first place.
>
> I'm not sure how to use the dependency plugin - how do I configure the
> reports to pick up the properties from a jar?

use the dependency to unpack you properties file from your
artifact/jar to a dedicated path in your project.
Then configure the mojo.

  
org.apache.maven.plugins
maven-project-info-reports-plugin

  path to unpacked properties file

  

IMHO a little complicated and a lot of xml to write but should work
(not tested).
I would prefer add a feature for the maven-project-info-reports-plugin
(and maybe others) to be able to load properties file from
artifact/jar with adding this artifact/jar in the plugin
configuration.

  
org.apache.maven.plugins
maven-project-info-reports-plugin

  
org.foo:my-properties:1.0
path in the jar
  

  

Makes sense ? (less xml than using dependency unpack)

>
>> --
>> Olivier Lamy
>> Talend : http://talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> 2011/8/31 sebb :
>>> On 23 August 2011 14:43, sebb  wrote:
>>>> The default customBundle is located at
>>>>
>>>> ${project.basedir}/src/site/custom/project-info-report.properties
>>>>
>>>> which works fine for single module projects.
>>>>
>>>> However, it does not seem to work for multi-module projects.
>>>>
>>>> How can one share the same bundle between multiple modules?
>>>>
>>>> The modules all share a common parent, but do not seem to pick up the
>>>> bundle from the parent.
>>>
>>> Anyone?
>>>
>>> Or is the only solution to duplicate the bundle in all projects?
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Project reports customBundle - how to share across multiple modules

[sebb]

On 31 August 2011 08:29, Olivier Lamy  wrote:
> Hello,
> The solution I see is to have an artifact (call it build-resources or
> something like that) which contains those .properties

The modules all have a common parent pom - is it possible to use that
to contain the resources, rather than creating another module?

> And use it tru remote-resources or dependency plugin.

The remote-resources sharing example shows that the resources will be
made available under

${project.build.directory}/maven-shared-archive-resources

but the reports customBundle expects to find the file under

${project.basedir}/src/site/custom/project-info-report.properties

Looks like I would also have to configure the reports to pick up the
custom bundle from elsewhere, or change the outputDirectory (but that
would probably mess up the packaging/assembly phases).

Seems simpler to just create copies of the bundle in each module in
the first place.

I'm not sure how to use the dependency plugin - how do I configure the
reports to pick up the properties from a jar?

> --
> Olivier Lamy
> Talend : http://talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> 2011/8/31 sebb :
>> On 23 August 2011 14:43, sebb  wrote:
>>> The default customBundle is located at
>>>
>>> ${project.basedir}/src/site/custom/project-info-report.properties
>>>
>>> which works fine for single module projects.
>>>
>>> However, it does not seem to work for multi-module projects.
>>>
>>> How can one share the same bundle between multiple modules?
>>>
>>> The modules all share a common parent, but do not seem to pick up the
>>> bundle from the parent.
>>
>> Anyone?
>>
>> Or is the only solution to duplicate the bundle in all projects?
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Project reports customBundle - how to share across multiple modules

[Olivier Lamy]

Hello,
The solution I see is to have an artifact (call it build-resources or
something like that) which contains those .properties

And use it tru remote-resources or dependency plugin.

-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

2011/8/31 sebb :
> On 23 August 2011 14:43, sebb  wrote:
>> The default customBundle is located at
>>
>> ${project.basedir}/src/site/custom/project-info-report.properties
>>
>> which works fine for single module projects.
>>
>> However, it does not seem to work for multi-module projects.
>>
>> How can one share the same bundle between multiple modules?
>>
>> The modules all share a common parent, but do not seem to pick up the
>> bundle from the parent.
>
> Anyone?
>
> Or is the only solution to duplicate the bundle in all projects?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Project reports customBundle - how to share across multiple modules

[sebb]

On 23 August 2011 14:43, sebb  wrote:
> The default customBundle is located at
>
> ${project.basedir}/src/site/custom/project-info-report.properties
>
> which works fine for single module projects.
>
> However, it does not seem to work for multi-module projects.
>
> How can one share the same bundle between multiple modules?
>
> The modules all share a common parent, but do not seem to pick up the
> bundle from the parent.

Anyone?

Or is the only solution to duplicate the bundle in all projects?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Project reports customBundle - how to share across multiple modules

[sebb]

The default customBundle is located at

${project.basedir}/src/site/custom/project-info-report.properties

which works fine for single module projects.

However, it does not seem to work for multi-module projects.

How can one share the same bundle between multiple modules?

The modules all share a common parent, but do not seem to pick up the
bundle from the parent.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org