maven jetty plugin - running two jetty's with different ports
Hi List, is it possible to run two jetty instances one on port 8080 and one on port 8090? Both jetty's should start several webApps. Running Multiple Webapps is decribed in http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin I hope this works. Thanks Fredy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: maven jetty plugin - running two jetty's with different ports
Thanks for the hint! Fredy -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Montag, 28. Februar 2011 11:14 An: Maven Users List Betreff: Re: maven jetty plugin - running two jetty's with different ports As that's a specific question for that plugin, you should probably ask on a mailing list specific for that plugin. I believe these are the appropriate ones: http://jetty.codehaus.org/jetty/maven-plugin/mail-lists.html /Anders On Mon, Feb 28, 2011 at 10:59, Hauschel Fred Robert fredrobert.hausc...@cirquent.de wrote: Hi List, is it possible to run two jetty instances one on port 8080 and one on port 8090? Both jetty's should start several webApps. Running Multiple Webapps is decribed in http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin I hope this works. Thanks Fredy - 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
maven3 - maven-checkstyle-plugin:2.5 - Property ${basedir} has not been set
Hi all,
I've configured checkstyle for a project.
1. If I use the default check style, all works.
2. If I use a absolute path in file system
configLocation//xxx\yyy\Checkstyle\ISPA_checkstyle.xml/configLocation
The same error as with 3. Happens!
3. If I use:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version${version_maven-checkstyle-plugin}/version
configuration
configLocation/preferences/XXX_checkstyle.xml/configLocation
/configuration
/plugin
The following happens:
[INFO] Generating Checkstyle report--- maven-checkstyle-plugin:2.5
[DEBUG] executeCheckstyle start headerLocation : LICENSE.txt
[DEBUG] Adding the outputDirectory
file:/D:/IDE/workspaces/current/score_common/target/classes/ to the
Checkstyle class path
[DEBUG] request.getConfigLocation() /preferences/XXX_checkstyle.xml
[DEBUG] The resource '/preferences/XXX_checkstyle.xml' was found as
jar:file:/D:/Documents%20and%20Settings/XHAUSF/.m2/repository/com/xxx/sc
ore/buildExtension/0.0.1-SNAPSHOT/buildExtension-0.0.1-SNAPSHOT.jar!/pre
ferences/XXX_checkstyle.xml.
[DEBUG] headerLocation LICENSE.txt
[DEBUG] The resource 'LICENSE.txt' was found as
jar:file:/D:/Documents%20and%20Settings/XHAUSF/.m2/repository/org/apache
/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.j
ar!/LICENSE.txt.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 17.625s
[INFO] Finished at: Wed Feb 16 12:03:40 CET 2011
[INFO] Final Memory: 22M/58M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site
(default-site) on project score_common: Error during page generation:
Error rendering Maven report: Failed during checkstyle execution: Failed
during checkstyle configuration: unable to read
D:\IDE\workspaces\current\score_common\target\checkstyle-checker.xml -
unable to parse configuration stream - Property ${basedir} has not been
set - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site
(default-site) on project score_common: Error during page generation
It's great to know, that it find my settings on the classpath in the
buildextension ;-) But wtf is the problem with the basedir?
Any idea ??
Fredy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-assembly-plugin and .folder
Hi all,
I will zip a folder with the name '.metadata' but assembly plugin is ignoring
me ;-)
This is ignored:
include.metadata/version.ini/include
Does anybody have an idea, why assembly is ignoring '.metadata'?
Or is it a feature of the fileset ??
fileSets
fileSet
directory${project.basedir}/src/ide/xxx/directory
outputDirectory//outputDirectory
includes
includeworkspaces/defaultWorkspace/.metadata/version.ini/include
/includes
/fileSet
Thanks Fredy
--- searching a bit
And here is the answer ;-)) useDefaultExcludes is the feature, that devil me.
fileSet
useDefaultExcludesfalse/useDefaultExcludes
directory${project.basedir}/src/ide/xxx/directory
outputDirectory//outputDirectory
includes
include**/*/include
/includes
/fileSet
AW: adding a jar as resource to a webapp
Hi Marc, that is exactly what I need! Thank you very much!! @Antonio, Martin: Because of classpath manipulation (switching 3rdParty libraries) while runtime! The library should not be loaded from the webapp classloader. Fredy -Ursprüngliche Nachricht- Von: Marc Rohlfs [mailto:pomar...@googlemail.com] Gesendet: Mittwoch, 2. Februar 2011 17:44 An: Maven Users List Betreff: Re: adding a jar as resource to a webapp I'd suggest it could be a JAR containing an Applet. The maven-dependency-plugin might help You out. Use on of the following approaches: http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-project-dependencies.html On 02/02/11 17:06, Antonio Petrelli wrote: The jar should not be added to the classpath at build, runtime! And it should not be included in WEB-INF/lib. Not at build, not at runtime and not in WEB-INF/lib? What do you need it for? - 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: Inermediatte surefire reports
Hi sridharl, divide and conquer ;-) I can't imagine a artifact, which needs 2 hours for unit-test. Maybe you should rethink the modularization. To you question, I don't think, that it is possible to see the reports immediately in one artifact. But it is sure possible if you divide your code (or simple the testcases) in some separate artifacts. Maybe a multi module project which have 12 test modules, so each of your module takes 10 minutes ,-). Do not search a technical solution for big things, search for responsibilities to separate. Hope this helps a little bit. Fredy -Ursprüngliche Nachricht- Von: Sridhar Laxmipuram Srinivasan [mailto:sridh...@yahoo-inc.com] Gesendet: Mittwoch, 22. Dezember 2010 04:46 An: Maven Users List Betreff: Inermediatte surefire reports Hi, I have a profile which has around 75 tests and runs for 2 hrs, by default I will be able to see surefire rport only after 2 hrs, is there a way I can make maven write surefire report as and when tests gets completed, I mean can I see surefire report right immediately after 1st testcase gets executed? thnkx sridharl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: AW: AW: releas:perform with profiles fails
Hi Ron,
so we are now speaking about a m2Eclipse problem, and that is the wrong list!
Example: You have a webApp packagingwar/packaging and in it a dependency to
(for example) commons-logging with scope provided.
If you now use commons-logging in a servlet, and run your webapp in eclipse
(WTP - run on srever), so the classpath will not contain
commons-logging.
Can you conform that ??
Fredy
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Mittwoch, 22. Dezember 2010 09:35
An: users@maven.apache.org
Betreff: Re: AW: AW: AW: releas:perform with profiles fails
On 22/12/2010 2:56 AM, Hauschel Fred Robert wrote:
See inline...
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Dienstag, 21. Dezember 2010 17:17
An: users@maven.apache.org
Betreff: Re: AW: AW: releas:perform with profiles fails
On 21/12/2010 4:28 AM, Hauschel Fred Robert wrote:
Ok, maybe packagingExcludesWEB-INF/lib/*.jar/packagingExcludes
Explained in
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
is a better way ;-)
Sounds like too much work to copy a bunch of libraries into each project
and then exclude them when maven already has a transitive dependency
mechanism that supports scope provided.
[HF:] Maybe! But m2Eclipse plugin does not use provided libraries in it's
classpath for wtp projects.
Are you sure?
It seems to work for us with no problems but perhaps I don't understand
where you ran into the problems.
With Eclipse/STS we are also insulated from plug-ins since they all come
pre-installed.
And our goal is to make it as simple as possible for the developers. Maybe
this is the problem ,-)
That is what we did as well. Simple parent POM, small set of
dependencies. 3rd party dependencies all neatly packaged up when a new
release is planned.
Modules are easy to construct and the Maven tasks are just a click on a
menu.
No profiles, no custom plug-ins only 3 or 4 standard Maven plug-in are
used to build a portal that has over 60 Web services, JSF, portlets,
servlets and batch jobs.
Libraries are very stable and we know exactly what versions of 3rd party
software are included in any version of the application.
Thanks for your help, we will see, how to solve the thing.
You are quite welcome.
Good luck with getting this setup.
Ron
Fredy
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Dienstag, 21. Dezember 2010 10:06
An: Maven Users List
Betreff: AW: AW: releas:perform with profiles fails
Hi Ron,
thank you very much for your hint!
We are actual converting a historical ant builded project to maven.
Profiles are really a bad way to solve our problems, but in the moment it is
a way to get the whole stuff running and be able to provide a release.
Providing configuration is just one problem, that we actually solve with
profiles!
The major problem is to provide separate different dependencies for
m2Eclipse and tomcat in the webapps.
We solve this with profiles and properties:
parentPom:
profiles
profile
idcontainer/id
properties
scopeprovided/scope
/properties
/profile
profile
ideclipse/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
scopecompile/scope
/properties
/profile
/profiles
ModulePom:
profiles
profile
iddependencies/id
activation
activeByDefaulttrue/activeByDefault
/activation
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
scope${scope}/scope
/dependency
dependency
groupIdxyzgroupId
artifactIdxyz_common/artifactId
scope${scope}/scope
/dependency
/dependencies
/profile
/profiles
That works for now, but we are not really happy yet!
We will provide all dependencies in tomcat/lib so we actual have all
dependencies provided in our libraries.
So each webApp have to define it's dependencies (again), transitive
dependencies are switched off.
The other way would be to use the default (compile) dependencies in the
libraries and exclude all transitive dependencies
AW: AW: releas:perform with profiles fails
Hi Ron,
thank you very much for your hint!
We are actual converting a historical ant builded project to maven.
Profiles are really a bad way to solve our problems, but in the moment it is a
way to get the whole stuff running and be able to provide a release.
Providing configuration is just one problem, that we actually solve with
profiles!
The major problem is to provide separate different dependencies for m2Eclipse
and tomcat in the webapps.
We solve this with profiles and properties:
parentPom:
profiles
profile
idcontainer/id
properties
scopeprovided/scope
/properties
/profile
profile
ideclipse/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
scopecompile/scope
/properties
/profile
/profiles
ModulePom:
profiles
profile
iddependencies/id
activation
activeByDefaulttrue/activeByDefault
/activation
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
scope${scope}/scope
/dependency
dependency
groupIdxyzgroupId
artifactIdxyz_common/artifactId
scope${scope}/scope
/dependency
/dependencies
/profile
/profiles
That works for now, but we are not really happy yet!
We will provide all dependencies in tomcat/lib so we actual have all
dependencies provided in our libraries.
So each webApp have to define it's dependencies (again), transitive
dependencies are switched off.
The other way would be to use the default (compile) dependencies in the
libraries and exclude all transitive dependencies for production build.
Any better idea ?
Fredy
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Montag, 20. Dezember 2010 16:33
An: users@maven.apache.org
Betreff: Re: AW: releas:perform with profiles fails
On 20/12/2010 10:20 AM, Hauschel Fred Robert wrote:
Found a workarround:
http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html
Fredy
You will be back.
Search this forum for discussions of profiles and environments.
The road to Maven hell is paved with profiles.
Just as good intentions are wonderful on their own, profiles can lead
you to do things that will get you into bad situations.
Not to say that they are evil in themselves and do not have good uses.
This is not one of them.
Ron
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Montag, 20. Dezember 2010 15:23
An: Maven Users List
Betreff: releas:perform with profiles fails
Hi list,
I've a multi module with differences between the prod and dev
environment. Threfor I've defined some profiles.
mvn clean install -P devContainerSettings,dependencies,!eclipse works
fine!
but mvn --batch-mode release:prepare -P
devContainerSettings,dependencies,!eclipse fails with compilations
errors!
Any idea??
Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.6.0_21
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
Fredy
-
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
AW: AW: releas:perform with profiles fails
Ok, maybe packagingExcludesWEB-INF/lib/*.jar/packagingExcludes
Explained in
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html is a
better way ;-)
Fredy
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Dienstag, 21. Dezember 2010 10:06
An: Maven Users List
Betreff: AW: AW: releas:perform with profiles fails
Hi Ron,
thank you very much for your hint!
We are actual converting a historical ant builded project to maven.
Profiles are really a bad way to solve our problems, but in the moment it is a
way to get the whole stuff running and be able to provide a release.
Providing configuration is just one problem, that we actually solve with
profiles!
The major problem is to provide separate different dependencies for m2Eclipse
and tomcat in the webapps.
We solve this with profiles and properties:
parentPom:
profiles
profile
idcontainer/id
properties
scopeprovided/scope
/properties
/profile
profile
ideclipse/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
scopecompile/scope
/properties
/profile
/profiles
ModulePom:
profiles
profile
iddependencies/id
activation
activeByDefaulttrue/activeByDefault
/activation
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
scope${scope}/scope
/dependency
dependency
groupIdxyzgroupId
artifactIdxyz_common/artifactId
scope${scope}/scope
/dependency
/dependencies
/profile
/profiles
That works for now, but we are not really happy yet!
We will provide all dependencies in tomcat/lib so we actual have all
dependencies provided in our libraries.
So each webApp have to define it's dependencies (again), transitive
dependencies are switched off.
The other way would be to use the default (compile) dependencies in the
libraries and exclude all transitive dependencies for production build.
Any better idea ?
Fredy
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Montag, 20. Dezember 2010 16:33
An: users@maven.apache.org
Betreff: Re: AW: releas:perform with profiles fails
On 20/12/2010 10:20 AM, Hauschel Fred Robert wrote:
Found a workarround:
http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html
Fredy
You will be back.
Search this forum for discussions of profiles and environments.
The road to Maven hell is paved with profiles.
Just as good intentions are wonderful on their own, profiles can lead
you to do things that will get you into bad situations.
Not to say that they are evil in themselves and do not have good uses.
This is not one of them.
Ron
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Montag, 20. Dezember 2010 15:23
An: Maven Users List
Betreff: releas:perform with profiles fails
Hi list,
I've a multi module with differences between the prod and dev
environment. Threfor I've defined some profiles.
mvn clean install -P devContainerSettings,dependencies,!eclipse works
fine!
but mvn --batch-mode release:prepare -P
devContainerSettings,dependencies,!eclipse fails with compilations
errors!
Any idea??
Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.6.0_21
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
Fredy
-
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
AW: AW: AW: releas:perform with profiles fails
See inline...
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Dienstag, 21. Dezember 2010 17:17
An: users@maven.apache.org
Betreff: Re: AW: AW: releas:perform with profiles fails
On 21/12/2010 4:28 AM, Hauschel Fred Robert wrote:
Ok, maybe packagingExcludesWEB-INF/lib/*.jar/packagingExcludes
Explained in
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html is
a better way ;-)
Sounds like too much work to copy a bunch of libraries into each project
and then exclude them when maven already has a transitive dependency
mechanism that supports scope provided.
[HF:] Maybe! But m2Eclipse plugin does not use provided libraries in it's
classpath for wtp projects. And our goal is to make it as simple as possible
for the developers. Maybe this is the problem ,-) Thanks for your help, we will
see, how to solve the thing.
Fredy
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Dienstag, 21. Dezember 2010 10:06
An: Maven Users List
Betreff: AW: AW: releas:perform with profiles fails
Hi Ron,
thank you very much for your hint!
We are actual converting a historical ant builded project to maven.
Profiles are really a bad way to solve our problems, but in the moment it is
a way to get the whole stuff running and be able to provide a release.
Providing configuration is just one problem, that we actually solve with
profiles!
The major problem is to provide separate different dependencies for m2Eclipse
and tomcat in the webapps.
We solve this with profiles and properties:
parentPom:
profiles
profile
idcontainer/id
properties
scopeprovided/scope
/properties
/profile
profile
ideclipse/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
scopecompile/scope
/properties
/profile
/profiles
ModulePom:
profiles
profile
iddependencies/id
activation
activeByDefaulttrue/activeByDefault
/activation
dependencies
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
scope${scope}/scope
/dependency
dependency
groupIdxyzgroupId
artifactIdxyz_common/artifactId
scope${scope}/scope
/dependency
/dependencies
/profile
/profiles
That works for now, but we are not really happy yet!
We will provide all dependencies in tomcat/lib so we actual have all
dependencies provided in our libraries.
So each webApp have to define it's dependencies (again), transitive
dependencies are switched off.
The other way would be to use the default (compile) dependencies in the
libraries and exclude all transitive dependencies for production build.
Any better idea ?
Fredy
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Montag, 20. Dezember 2010 16:33
An: users@maven.apache.org
Betreff: Re: AW: releas:perform with profiles fails
On 20/12/2010 10:20 AM, Hauschel Fred Robert wrote:
Found a workarround:
http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html
Fredy
You will be back.
Search this forum for discussions of profiles and environments.
The road to Maven hell is paved with profiles.
Just as good intentions are wonderful on their own, profiles can lead
you to do things that will get you into bad situations.
Not to say that they are evil in themselves and do not have good uses.
This is not one of them.
Ron
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Montag, 20. Dezember 2010 15:23
An: Maven Users List
Betreff: releas:perform with profiles fails
Hi list,
I've a multi module with differences between the prod and dev
environment. Threfor I've defined some profiles.
mvn clean install -P devContainerSettings,dependencies,!eclipse works
fine!
but mvn --batch-mode release:prepare -P
devContainerSettings,dependencies,!eclipse fails with compilations
errors!
Any idea??
Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.6.0_21
Java home: C:\Program
AW: AW: Dependency on pom-project not resolved in reactor on multi-module build
) @ parent ---
[INFO]
[INFO]
[INFO] Building A 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ A ---
[INFO]
[INFO]
[INFO] Building B 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ B ---
[INFO] Deleting C:\temp\pom-dep-problem\B\target
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ B ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
C:\temp\pom-dep-problem\B\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ B ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @
B ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
C:\temp\pom-dep-problem\B\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ B ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.5:test (default-test) @ B ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ B ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: C:\temp\pom-dep-problem\B\target\B-1.0-SNAPSHOT.jar
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] parent SUCCESS [0.157s]
[INFO] A . SUCCESS [0.000s]
[INFO] B . SUCCESS [1.297s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.609s
[INFO] Finished at: Mon Dec 20 09:20:05 CET 2010
[INFO] Final Memory: 3M/15M
[INFO]
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 14:37
An: Maven Users List
Betreff: AW: AW: Dependency on pom-project not resolved in reactor on
multi-module build
I am using Maven version 2.2.1. That is also a thing that I should have
mentioned.
mvn --version:
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20
Java home: /usr/lib/jvm/java-6-openjdk/jre Default locale: en_US, platform
encoding: UTF-8 OS name: linux version: 2.6.32-27-generic arch: amd64
Family: unix
Attached you find a ZIP file containing the basic setup.
Maybe this helps to reproduce the error.
We have a Nexus set up here, that is configured in the settings.xml. But this
should not make any big difference. Beyond that, there are not Maven profiles
configured.
Thanks a lot,
Florian
--
Florian Rampp, Software Architect
Phone: +49.89.45 23 47-64
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@xxx.de]
Gesendet: Freitag, 17. Dezember 2010 13:39
An: Maven Users List
Betreff: AW: AW: Dependency on pom-project not resolved in reactor on
multi-module build
So I can't see a difference to my test, expecting
version${project.version}/version
I've used
version${parent.version}/version
Can't imagine, that that is a difference, but who knows!
Fredy
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
artifactIdparent/artifactId
groupIdmygroup/groupId
version1.0-SNAPSHOT/version
/parent
artifactIdB/artifactId
packagingjar/packaging
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdA/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
/project
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 13:31
An: Maven Users List
Betreff: AW: AW: Dependency on pom-project not resolved in reactor on
multi-module build
Yes, I have. See my first mail for the content of A/pom.xml and B/pom.xml
Florian
--
Florian Rampp, Software Architect
Phone: +49.89.45 23 47-64
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@xxx.de]
Gesendet
releas:perform with profiles fails
Hi list, I've a multi module with differences between the prod and dev environment. Threfor I've defined some profiles. mvn clean install -P devContainerSettings,dependencies,!eclipse works fine! but mvn --batch-mode release:prepare -P devContainerSettings,dependencies,!eclipse fails with compilations errors! Any idea?? Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) Java version: 1.6.0_21 Java home: C:\Program Files\Java\jdk1.6.0_21\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Fredy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: releas:perform with profiles fails
Found a workarround: http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html Fredy -Ursprüngliche Nachricht- Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de] Gesendet: Montag, 20. Dezember 2010 15:23 An: Maven Users List Betreff: releas:perform with profiles fails Hi list, I've a multi module with differences between the prod and dev environment. Threfor I've defined some profiles. mvn clean install -P devContainerSettings,dependencies,!eclipse works fine! but mvn --batch-mode release:prepare -P devContainerSettings,dependencies,!eclipse fails with compilations errors! Any idea?? Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) Java version: 1.6.0_21 Java home: C:\Program Files\Java\jdk1.6.0_21\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Fredy - 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
Maven and environment Properties - Feature or bug ??
In windows:
set test=dev and using ${env.test} in the pom for example in name
myArtifact _${env.test}/name
Results in: Building myArtifact_${env.test} 00.01-SNAPSHOT
set TEST=dev and using ${env.TEST} in the pom for example in name
myArtifact _${env.TEST}/name
Results in: Building myArtifact_dev 00.01-SNAPSHOT
How cool is that?
For me that was a very expensive Feature!
Or did I have problems understanding the environment variables? Is there
a case sensitivity in general ??
Fredy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: Dependency on pom-project not resolved in reactor on multi-module build
What happens, if you use mvn install?
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 10:51
An: users@maven.apache.org
Betreff: Dependency on pom-project not resolved in reactor on multi-module build
Hello,
I am having the following issue with artifact resolution in the Maven reactor.
My project layout resembles the following:
-- Parent POM
-- POM A (packaging: pom)
-- POM B (packaging: jar)
POM A and POM B have Parent POM as parent. Parent POM has POM A and
POM B as submodules. All projects inherit their version from the parent POM.
POM B has a dependency on POM A, which has dependencies on several other
artifacts and is used according to section 3.6.1. Grouping dependencies in
http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html.
When I execute mvn package on the parent POM, the build results in the
following error:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) mygroup:A:pom:1.0-SNAPSHOT
Path to dependency:
1) mygroup:B:jar:1.0-SNAPSHOT
2) mygroup:A:pom:1.0-SNAPSHOT
Debug output reveals the following error:
[DEBUG] WARNING: A dependency of the current project (or of one the plugins
used in its build) was found in the reactor,
but had not been built at the time it was requested. It will be resolved from
the repository instead.
Current Project: Unnamed - mygroup:B:jar:1.0-SNAPSHOT
Requested Dependency: mygroup:A:pom:1.0-SNAPSHOT
NOTE: You may need to run this build to the 'compile' lifecycle phase, or
farther, in order to build the dependency artifact.
So I am wondering if this is a bug. Dependencies on POM projects in the reactor
should not be handled different than dependencies on JAR-projects.
The content of POM file for project A is:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
artifactIdparent/artifactId
groupIdmygroup/groupId
version1.0-SNAPSHOT/version
/parent
artifactIdA/artifactId
packagingpom/packaging
/project
The content of POM file for project B is:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
artifactIdparent/artifactId
groupIdmygroup/groupId
version1.0-SNAPSHOT/version
/parent
artifactIdB/artifactId
packagingjar/packaging
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdA/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
/project
Thanks a lot,
Florian
--
Florian Rampp, Software Architect
Phone: +49.89.45 23 47-64
--
jambit Software Development Management GmbH
Nymphenburger Straße 13-15, D-80335 München
Phone: +49.89.45 23 47-0 Fax: +49.89.45 23 47-70
http://www.jambit.comwhere innovation works
Geschäftsführer: Peter F. Fellinger, Markus Hartinger
Sitz: München; Registergericht: München, HRB 129139
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: Dependency on pom-project not resolved in reactor on multi-module build
How is the reactor solving the order of your modules?
How is the order in your parent pom?
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 10:51
An: users@maven.apache.org
Betreff: Dependency on pom-project not resolved in reactor on multi-module build
Hello,
I am having the following issue with artifact resolution in the Maven reactor.
My project layout resembles the following:
-- Parent POM
-- POM A (packaging: pom)
-- POM B (packaging: jar)
POM A and POM B have Parent POM as parent. Parent POM has POM A and
POM B as submodules. All projects inherit their version from the parent POM.
POM B has a dependency on POM A, which has dependencies on several other
artifacts and is used according to section 3.6.1. Grouping dependencies in
http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html.
When I execute mvn package on the parent POM, the build results in the
following error:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) mygroup:A:pom:1.0-SNAPSHOT
Path to dependency:
1) mygroup:B:jar:1.0-SNAPSHOT
2) mygroup:A:pom:1.0-SNAPSHOT
Debug output reveals the following error:
[DEBUG] WARNING: A dependency of the current project (or of one the plugins
used in its build) was found in the reactor,
but had not been built at the time it was requested. It will be resolved from
the repository instead.
Current Project: Unnamed - mygroup:B:jar:1.0-SNAPSHOT
Requested Dependency: mygroup:A:pom:1.0-SNAPSHOT
NOTE: You may need to run this build to the 'compile' lifecycle phase, or
farther, in order to build the dependency artifact.
So I am wondering if this is a bug. Dependencies on POM projects in the reactor
should not be handled different than dependencies on JAR-projects.
The content of POM file for project A is:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
artifactIdparent/artifactId
groupIdmygroup/groupId
version1.0-SNAPSHOT/version
/parent
artifactIdA/artifactId
packagingpom/packaging
/project
The content of POM file for project B is:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
artifactIdparent/artifactId
groupIdmygroup/groupId
version1.0-SNAPSHOT/version
/parent
artifactIdB/artifactId
packagingjar/packaging
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdA/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
/project
Thanks a lot,
Florian
--
Florian Rampp, Software Architect
Phone: +49.89.45 23 47-64
--
jambit Software Development Management GmbH
Nymphenburger Straße 13-15, D-80335 München
Phone: +49.89.45 23 47-0 Fax: +49.89.45 23 47-70
http://www.jambit.comwhere innovation works
Geschäftsführer: Peter F. Fellinger, Markus Hartinger
Sitz: München; Registergericht: München, HRB 129139
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
activating a profile by two environment variables/values
Hi, I have four profiles prodDeps, prodResources, devDeps, devResources. If I set ENVIRONMENT=devContainer - prodDeps and devResources should be activated If I set ENVIRONMENT=prodContainer - prodDeps and prodResources should be activated If I set ENVIRONMENT=eclipse - devDeps and devResources should be activated So I need something like this: activation property nameenv.ENVIRONMENT/name valueprodContainer,devContainer/value /property /activation Is there any possibility to do something like this? The activation and the property cardinality in the xsd is 0..1 ;-( Thanks Fredy
AW: Maven and environment Properties - Feature or bug ??
Rtfm ;-) Thanks!!! Fredy -Ursprüngliche Nachricht- Von: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu] Gesendet: Freitag, 17. Dezember 2010 12:18 An: Maven Users List Betreff: Re: Maven and environment Properties - Feature or bug ?? Hauschel Fred Robert wrote: Or did I have problems understanding the environment variables? Is there a case sensitivity in general ?? http://maven.apache.org/pom.html#Properties Benjamin - 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: AW: Dependency on pom-project not resolved in reactor on multi-module build
Hello Florian,
have you defined the typepom/type ??
dependencies
dependency
groupIdmygroup/groupId
artifactIdA/artifactId
version${parent.version}/version
typepom/type
/dependency
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 12:42
An: users@maven.apache.org
Betreff: Re: AW: Dependency on pom-project not resolved in reactor on
multi-module build
Hello Freddy,
Thanks for your quick reply. I should have mentioned that mvn installs solves
the problem. So Maven resolves the dependency from the local repository. But
this is just a workaround since I expect the dependency to be resolved from the
reactor.
I think the order in which the modules are listed in the parent POM is not
important. If I change the order this does not affect the behavior. Here is the
parent POM:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdmygroup/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
modules
moduleA/module
moduleB/module
/modules
/project
The reactor build order is correct:
[INFO] Reactor build order:
[INFO] Unnamed - mygroup:parent:pom:1.0-SNAPSHOT
[INFO] Unnamed - mygroup:A:pom:1.0-SNAPSHOT
[INFO] Unnamed - mygroup:B:jar:1.0-SNAPSHOT
It seems to be a bug or at least unexpected behavior in Maven.
Thanks a lot,
Florian
P.S: If this mail does not appear as response on the first thread, I am sorry.
My mistake.
--
jambit Software Development Management GmbH
Nymphenburger Straße 13-15, D-80335 München
Phone: +49.89.45 23 47-0 Fax: +49.89.45 23 47-70
http://www.jambit.comwhere innovation works
Geschäftsführer: Peter F. Fellinger, Markus Hartinger
Sitz: München; Registergericht: München, HRB 129139
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: Dependency on pom-project not resolved in reactor on multi-module build
So I can't see a difference to my test, expecting
version${project.version}/version
I've used
version${parent.version}/version
Can't imagine, that that is a difference, but who knows!
Fredy
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
artifactIdparent/artifactId
groupIdmygroup/groupId
version1.0-SNAPSHOT/version
/parent
artifactIdB/artifactId
packagingjar/packaging
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdA/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
/project
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 13:31
An: Maven Users List
Betreff: AW: AW: Dependency on pom-project not resolved in reactor on
multi-module build
Yes, I have. See my first mail for the content of A/pom.xml and B/pom.xml
Florian
--
Florian Rampp, Software Architect
Phone: +49.89.45 23 47-64
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Freitag, 17. Dezember 2010 13:12
An: Maven Users List
Betreff: AW: AW: Dependency on pom-project not resolved in reactor on
multi-module build
Hello Florian,
have you defined the typepom/type ??
dependencies
dependency
groupIdmygroup/groupId
artifactIdA/artifactId
version${parent.version}/version
typepom/type
/dependency
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 12:42
An: users@maven.apache.org
Betreff: Re: AW: Dependency on pom-project not resolved in reactor on
multi-module build
Hello Freddy,
Thanks for your quick reply. I should have mentioned that mvn installs solves
the problem. So Maven resolves the dependency from the local repository. But
this is just a workaround since I expect the dependency to be resolved from the
reactor.
I think the order in which the modules are listed in the parent POM is not
important. If I change the order this does not affect the behavior. Here is the
parent POM:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdmygroup/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
modules
moduleA/module
moduleB/module
/modules
/project
The reactor build order is correct:
[INFO] Reactor build order:
[INFO] Unnamed - mygroup:parent:pom:1.0-SNAPSHOT
[INFO] Unnamed - mygroup:A:pom:1.0-SNAPSHOT
[INFO] Unnamed - mygroup:B:jar:1.0-SNAPSHOT
It seems to be a bug or at least unexpected behavior in Maven.
Thanks a lot,
Florian
P.S: If this mail does not appear as response on the first thread, I am sorry.
My mistake.
--
jambit Software Development Management GmbH
Nymphenburger Straße 13-15, D-80335 München
Phone: +49.89.45 23 47-0 Fax: +49.89.45 23 47-70
http://www.jambit.comwhere innovation works
Geschäftsführer: Peter F. Fellinger, Markus Hartinger
Sitz: München; Registergericht: München, HRB 129139
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Missing M2Eclipse extensions: Checking out a Maven project from several SCM repositories
Hi list, A few weeks ago I think I've installed this feature from: m2eclipse Extras - http://m2eclipse.sonatype.org/sites/m2e-extras But now the feature is not available any more ?!?! Any Idea ?? Thanks Fredy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[M3] release plugin
Hey all, i've some problems with releasing my artifacts with m3: [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-source-plugin:2.2-SNAPSHOT or one of its dependencies could not be resolved: Failure to find org.apache.maven.plugins:maven-source-plugin:jar:2.2-2 0100510.060623-403 in http://xxx/vvv/repository/public was cached in the local repository, resolution will not be reattempted until the update interval of ccc_public has elaps ed or updates are forced - [Help 1] Does anybody knows this problem? Does anybody knows where I can find the repo for maven-source-plugin:2.2-SNAPSHOT ?? I've started the plugin with the -U option ! Thanks Fredy
[m3] maven-site-plugin - out of memory
Hey all, I'm running site:site on a windows cmd line: C:\temp\scoreset maven_opts MAVEN_OPTS=-Xmx1536m Configuration in my parent pom: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version3.0-beta-3/version configuration reportPlugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version configuration dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration reports reportindex/report reportsummary/report reportdependencies/report reportproject-team/report reportcim/report reportissue-tracking/report reportlicense/report reportscm/report reportplugins/report /reports /plugin plugin artifactIdmaven-javadoc-plugin/artifactId configuration showprivate/show maxmemory1600m/maxmemory additionalJOption-J-XX:MaxPermSize=512/additionalJOption javadocVersion1.6/javadocVersion aggregatefalse/aggregate /configuration version2.7/version /plugin /reportPlugins /configuration /plugin /plugins Any idea what to configure else ??? Thanks Fredy Error: [INFO] --- maven-site-plugin:3.0-beta-3:site (default-cli) @ test_common --- [INFO] configuring report plugin org.apache.maven.plugins:maven-project-info-reports-plugin:2.2 [INFO] configuring report plugin org.apache.maven.plugins:maven-javadoc-plugin:2.7 [INFO] [INFO] maven-javadoc-plugin:2.7:aggregate (report:aggregate) @ test_common [ERROR] Java heap space - [Help 1] java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2760) at java.util.Arrays.copyOf(Arrays.java:2734) at java.util.ArrayList.ensureCapacity(ArrayList.java:167) at java.util.ArrayList.addAll(ArrayList.java:474) at org.apache.maven.project.MavenProject.setActiveProfiles(MavenProject.jav a:1408) at org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1941) at org.apache.maven.project.MavenProject.clone(MavenProject.java:1815) at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions (MojoExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeForkedExecuti ons(DefaultLifecycleExecutor.java:165) at org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenRepor ts(DefaultMavenReportExecutor.java:284) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(Abstr actSiteRenderingMojo.java:208) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBui ldPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja va:195) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja va:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja va:140) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject( LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject( LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild (LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleSt arter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at
[m3] maven documentation - maven-site-plugin
Hey all, what is happening with the maven-site-plugin in future? Will it be supported for maven 3? I heard from any other plans keyword: idiom: access wiki. Does anybody have some information? Actually my sit generation crashes ;-( Fredy
