Re: What is a good alternative for maven-itblast-plugin ?
Hi Wayne.
Thx for your quick reply. I tried Maven 2.2.1 as well, but resulted in the
same error.
Normally when using 2.0.9 it is possible to run all the Junit tests, but
when switching to 2.1.0 or 2.2.1 I always get the same exception:
NoSuchBeanDefinitionException.
And I do have to switch to 2.2.1 because I need to transform the junit (XML)
test results into a HTML page which has to be delivered as part of the
build. This is done by JUnitReport which relies on maven 2.1.0 or
higher.. So I'm in a deadlock right now.
Hopefully somebody knows a trick to solve this
NoSuchBeanDefinitionException..
[INFO] [talledLocalContainer] 08:53:54,758 INFO [AjpProtocol] Starting
Coyote AJP/1.3 on ajp-127.0.0.1-48009
[INFO] [talledLocalContainer] 08:53:54,773 INFO [Server] JBoss (MX
MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)]
Started in 31s:625ms
[INFO] [talledLocalContainer] JBoss 4.2.3 started on port [48080]
[INFO] [surefire:test {execution: virtual-execution}]
[INFO] Surefire report directory:
c:\_composer\_build\war\jboss42x\surefire-reports
---
T E S T S
---
Running nl.allshare.unittests.util.TestSuiteSingleClass
log4j:WARN No appenders could be found for logger
(nl.allshare.pvcomposer.EHCacheManager).
log4j:WARN Please initialize the log4j system properly.
Something went wrong
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
named 'environmentManager' is defined
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:504)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1041)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:273)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)
Wayne Fay wrote:
This was all perfectly running using maven 2.0.9, but since moving to
maven
2.1.0 the maven-itblast-plugin has stopped working.
Have you tried with Maven 2.2.1? There were serveral things wrong with
2.1.0, as I recall.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/What-is-a-good-alternative-for-maven-itblast-plugin---tp28772452p28776383.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: What is a good alternative for maven-itblast-plugin ?
have you tried changing the forkMode?
Additionally the version of surefire that is locked down is AFAIK different
between 2.0.9 and 2.2.1.
I think, but I am not sure, that 2.0.9 uses 2.4.2 unless you have locked
down the plugin version
whereas 2.1.0 and 2.2.1 use 2.4.3 unless you have locked down the plugin
version.
One of the changes between 2.4.2 and 2.4.3 is
http://jira.codehaus.org/browse/SUREFIRE-491 (see
http://jira.codehaus.org/browse/SUREFIRE/fixforversion/14255)
I am going to make a wild stab in the dark and guess that it is SUREFIRE-491
that is causing your test failures, i.e. your tests were relying on a bug in
surefire
The solution is to define for the surefire plugin exactly what system
properties you want to pass through to the forked JVM (or else use forkMode
= none (not recommended)
-Stephen
On 4 June 2010 08:00, Nafter hdo...@allshare.nl wrote:
Hi Wayne.
Thx for your quick reply. I tried Maven 2.2.1 as well, but resulted in the
same error.
Normally when using 2.0.9 it is possible to run all the Junit tests, but
when switching to 2.1.0 or 2.2.1 I always get the same exception:
NoSuchBeanDefinitionException.
And I do have to switch to 2.2.1 because I need to transform the junit
(XML)
test results into a HTML page which has to be delivered as part of the
build. This is done by JUnitReport which relies on maven 2.1.0 or
higher.. So I'm in a deadlock right now.
Hopefully somebody knows a trick to solve this
NoSuchBeanDefinitionException..
[INFO] [talledLocalContainer] 08:53:54,758 INFO [AjpProtocol] Starting
Coyote AJP/1.3 on ajp-127.0.0.1-48009
[INFO] [talledLocalContainer] 08:53:54,773 INFO [Server] JBoss (MX
MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)]
Started in 31s:625ms
[INFO] [talledLocalContainer] JBoss 4.2.3 started on port [48080]
[INFO] [surefire:test {execution: virtual-execution}]
[INFO] Surefire report directory:
c:\_composer\_build\war\jboss42x\surefire-reports
---
T E S T S
---
Running nl.allshare.unittests.util.TestSuiteSingleClass
log4j:WARN No appenders could be found for logger
(nl.allshare.pvcomposer.EHCacheManager).
log4j:WARN Please initialize the log4j system properly.
Something went wrong
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
named 'environmentManager' is defined
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:504)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1041)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:273)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)
Wayne Fay wrote:
This was all perfectly running using maven 2.0.9, but since moving to
maven
2.1.0 the maven-itblast-plugin has stopped working.
Have you tried with Maven 2.2.1? There were serveral things wrong with
2.1.0, as I recall.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/What-is-a-good-alternative-for-maven-itblast-plugin---tp28772452p28776383.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
Activate differernt profiles in Multimodule projects
Hi, I have a multimodule project in which some modules need an additional sourcefolder, whereas other modules dont. To avoid redefining this in each of the relevant modules I want to add this to the parent pom and activate the project if this folder X is present. Unfortunately this seems not working as the activation section seems to be interpreted during the parent pom, where no folder X exists. Ergo the profile is deactivated and the relevant modules are failing. How can I activate profiles, defined in the parent pom, for some modules ? Is there another way which avoids redefining this in every module ? Thanks PS: Using maven 2.2.1 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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: Activate differernt profiles in Multimodule projects
On 4 June 2010 09:18, MartyMcFly martymc...@smart-mail.de wrote: Hi, I have a multimodule project in which some modules need an additional sourcefolder, whereas other modules dont. To avoid redefining this in each of the relevant modules I want to add this to the parent pom and activate the project if this folder X is present. Unfortunately this seems not working as the activation section seems to be interpreted during the parent pom, where no folder X exists. Ergo the profile is deactivated and the relevant modules are failing. How can I activate profiles, defined in the parent pom, for some modules ? Is there another way which avoids redefining this in every module ? don't go against the maven way... apart from generated source code, you should only have one source folder per module... and if you are generating source code, best practice is to keep that in its own module (but obviously generate the source code into target/generated-source/plugin-name/. and have the plugin add the generated directory as a source root... only as a last resource should you use build-helper) Thanks PS: Using maven 2.2.1 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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: Activate differernt profiles in Multimodule projects
thanks for the answer. Sorry I probably should have add more information. It is generated source code. We have IDL files for Corba which are in project folder 'idl' - but not all modules have this idl folder. The idea is: in case of a 'idl' folder, the system to generate the java files from idl files is running and the /target/generated-sources (in which the java files are generated) is added as source folder. if no idl folder is given, the normal way to should proceed. But the problem remains that this system for the idls should only be active when this idl folder is present - is this possible to define in the parent pom ? (especially as the idl2java system requires addtional dependencies etc - I dont want to redefine that in every pom of a module which requires it). As we are bound to visibroker and there is no maven plugin available, we are required to find another solution :( Stephen Connolly-2 wrote: On 4 June 2010 09:18, MartyMcFly martymc...@smart-mail.de wrote: Hi, I have a multimodule project in which some modules need an additional sourcefolder, whereas other modules dont. To avoid redefining this in each of the relevant modules I want to add this to the parent pom and activate the project if this folder X is present. Unfortunately this seems not working as the activation section seems to be interpreted during the parent pom, where no folder X exists. Ergo the profile is deactivated and the relevant modules are failing. How can I activate profiles, defined in the parent pom, for some modules ? Is there another way which avoids redefining this in every module ? don't go against the maven way... apart from generated source code, you should only have one source folder per module... and if you are generating source code, best practice is to keep that in its own module (but obviously generate the source code into target/generated-source/plugin-name/. and have the plugin add the generated directory as a source root... only as a last resource should you use build-helper) Thanks PS: Using maven 2.2.1 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28777178.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: Activate differernt profiles in Multimodule projects
Hi, wouldn't adding a specialized parent pom for modules containing idl files to your project work? -Tim On 04.06.2010 10:33, MartyMcFly wrote: thanks for the answer. Sorry I probably should have add more information. It is generated source code. We have IDL files for Corba which are in project folder 'idl' - but not all modules have this idl folder. The idea is: in case of a 'idl' folder, the system to generate the java files from idl files is running and the /target/generated-sources (in which the java files are generated) is added as source folder. if no idl folder is given, the normal way to should proceed. But the problem remains that this system for the idls should only be active when this idl folder is present - is this possible to define in the parent pom ? (especially as the idl2java system requires addtional dependencies etc - I dont want to redefine that in every pom of a module which requires it). As we are bound to visibroker and there is no maven plugin available, we are required to find another solution :( Stephen Connolly-2 wrote: On 4 June 2010 09:18, MartyMcFlymartymc...@smart-mail.de wrote: Hi, I have a multimodule project in which some modules need an additional sourcefolder, whereas other modules dont. To avoid redefining this in each of the relevant modules I want to add this to the parent pom and activate the project if this folder X is present. Unfortunately this seems not working as the activation section seems to be interpreted during the parent pom, where no folder X exists. Ergo the profile is deactivated and the relevant modules are failing. How can I activate profiles, defined in the parent pom, for some modules ? Is there another way which avoids redefining this in every module ? don't go against the maven way... apart from generated source code, you should only have one source folder per module... and if you are generating source code, best practice is to keep that in its own module (but obviously generate the source code into target/generated-source/plugin-name/. and have the plugin add the generated directory as a source root... only as a last resource should you use build-helper) Thanks PS: Using maven 2.2.1 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Activate differernt profiles in Multimodule projects
write your own maven plugin it's not that hard it would just check if the idk folder is present and then generate the source code and attach the generated source code to the current module. then just add the maven plugin to your pom and away you go On 4 June 2010 09:33, MartyMcFly martymc...@smart-mail.de wrote: thanks for the answer. Sorry I probably should have add more information. It is generated source code. We have IDL files for Corba which are in project folder 'idl' - but not all modules have this idl folder. The idea is: in case of a 'idl' folder, the system to generate the java files from idl files is running and the /target/generated-sources (in which the java files are generated) is added as source folder. if no idl folder is given, the normal way to should proceed. But the problem remains that this system for the idls should only be active when this idl folder is present - is this possible to define in the parent pom ? (especially as the idl2java system requires addtional dependencies etc - I dont want to redefine that in every pom of a module which requires it). As we are bound to visibroker and there is no maven plugin available, we are required to find another solution :( Stephen Connolly-2 wrote: On 4 June 2010 09:18, MartyMcFly martymc...@smart-mail.de wrote: Hi, I have a multimodule project in which some modules need an additional sourcefolder, whereas other modules dont. To avoid redefining this in each of the relevant modules I want to add this to the parent pom and activate the project if this folder X is present. Unfortunately this seems not working as the activation section seems to be interpreted during the parent pom, where no folder X exists. Ergo the profile is deactivated and the relevant modules are failing. How can I activate profiles, defined in the parent pom, for some modules ? Is there another way which avoids redefining this in every module ? don't go against the maven way... apart from generated source code, you should only have one source folder per module... and if you are generating source code, best practice is to keep that in its own module (but obviously generate the source code into target/generated-source/plugin-name/. and have the plugin add the generated directory as a source root... only as a last resource should you use build-helper) Thanks PS: Using maven 2.2.1 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28777178.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: Activate differernt profiles in Multimodule projects
This is actually a nice idea... thanks - going for this Tim Kettler wrote: Hi, wouldn't adding a specialized parent pom for modules containing idl files to your project work? -Tim On 04.06.2010 10:33, MartyMcFly wrote: thanks for the answer. Sorry I probably should have add more information. It is generated source code. We have IDL files for Corba which are in project folder 'idl' - but not all modules have this idl folder. The idea is: in case of a 'idl' folder, the system to generate the java files from idl files is running and the /target/generated-sources (in which the java files are generated) is added as source folder. if no idl folder is given, the normal way to should proceed. But the problem remains that this system for the idls should only be active when this idl folder is present - is this possible to define in the parent pom ? (especially as the idl2java system requires addtional dependencies etc - I dont want to redefine that in every pom of a module which requires it). As we are bound to visibroker and there is no maven plugin available, we are required to find another solution :( Stephen Connolly-2 wrote: On 4 June 2010 09:18, MartyMcFlymartymc...@smart-mail.de wrote: Hi, I have a multimodule project in which some modules need an additional sourcefolder, whereas other modules dont. To avoid redefining this in each of the relevant modules I want to add this to the parent pom and activate the project if this folder X is present. Unfortunately this seems not working as the activation section seems to be interpreted during the parent pom, where no folder X exists. Ergo the profile is deactivated and the relevant modules are failing. How can I activate profiles, defined in the parent pom, for some modules ? Is there another way which avoids redefining this in every module ? don't go against the maven way... apart from generated source code, you should only have one source folder per module... and if you are generating source code, best practice is to keep that in its own module (but obviously generate the source code into target/generated-source/plugin-name/. and have the plugin add the generated directory as a source root... only as a last resource should you use build-helper) Thanks PS: Using maven 2.2.1 -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28777874.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
scm:checkout ignores tag element
Hello. I have a peculiar problem with cvs/M2 - it ignores tag element during checkout and always goes for the head. I modeled my settings after pom reference found here http://maven.apache.org/pom.html#SCM Someone else had similar problem 2 years back and Wayne tried to help however the thread was left unfinished. Here is my pom snippet: scm connectionscm:cvs:pserver:u...@server :/my/path:ProjectName/connection tagProjectNameTag/tag /scm I tried using mvn 'scm:checkout' - I get the HEAD revision. Using 'mvn -Dscm.tag=ProjectNameTag scm:checkout didn't help either. Your help will be greatly appreciated. Thanks, Dave
Re: scm:checkout ignores tag element
To answer my own question: scmVersionbranch_name/scmVersion scmVersionTypebranch/scmVersionType Could we add that to example documentation on maven.apache.org? Thanks, Dave On Fri, Jun 4, 2010 at 9:32 AM, D D dawi...@gmail.com wrote: Hello. I have a peculiar problem with cvs/M2 - it ignores tag element during checkout and always goes for the head. I modeled my settings after pom reference found here http://maven.apache.org/pom.html#SCM Someone else had similar problem 2 years back and Wayne tried to help however the thread was left unfinished. Here is my pom snippet: scm connectionscm:cvs:pserver:u...@server :/my/path:ProjectName/connection tagProjectNameTag/tag /scm I tried using mvn 'scm:checkout' - I get the HEAD revision. Using 'mvn -Dscm.tag=ProjectNameTag scm:checkout didn't help either. Your help will be greatly appreciated. Thanks, Dave
Re: Copying jar in multi module project with assembly
Thanks Ron, But the abc.jar I want to refer to is created in mod2 using assembly plug-in as an executable jar mod2/target/abc.jar It is not a direct dependency of mod1 . When I use dependency-with-war or dependencyset in my assembly for mod1.1, it is able to refer all other jar in Mod2 except abc.jar ... My issue is when creating a distribution in Mod1.1 , I want to include the abc.jar (created in mod2 target). Thanks ronatartifact wrote: On 03/06/2010 12:00 PM, maven-user wrote: Hi, I have multi module project structure as shown below . In mod2 target directory I have created executable jar, say abc.jar . Now I want to include this jar in the archive of mod1.1 that I'm creating using assembly.xml. My question is how can I refer to this abc.jar which is a runtime artifact of mod2..? myproject |__mod1 | |_mod1.1 |_mod2 Thanks. It is a dependency of mod1 and if your use jar-with-dependency it will be picked up. Google maven jar with dependency. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Copying-jar-in-multi-module-project-with-assembly-tp28769514p28781379.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: What is a good alternative for maven-itblast-plugin ?
Something went wrong org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'environmentManager' is defined at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:504) Seems like a reasonable question for a Spring forum, or perhaps ask the people behind itblast? Is environmentManager a common Spring bean and you're just missing some configuration? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Copying jar in multi module project with assembly
If you want it in, it is a dependency. Being a dependency does not have any religious significance, it just means that you think that mod1 will not run without that abc.jar being there. Maven makes no value judgments about why you want it included. If you say you need it Maven will include it. Ron On 04/06/2010 11:18 AM, maven-user wrote: Thanks Ron, But the abc.jar I want to refer to is created in mod2 using assembly plug-in as an executable jar mod2/target/abc.jar It is not a direct dependency of mod1 . When I use dependency-with-war or dependencyset in my assembly for mod1.1, it is able to refer all other jar in Mod2 except abc.jar ... My issue is when creating a distribution in Mod1.1 , I want to include the abc.jar (created in mod2 target). Thanks ronatartifact wrote: On 03/06/2010 12:00 PM, maven-user wrote: Hi, I have multi module project structure as shown below . In mod2 target directory I have created executable jar, say abc.jar . Now I want to include this jar in the archive of mod1.1 that I'm creating using assembly.xml. My question is how can I refer to this abc.jar which is a runtime artifact of mod2..? myproject |__mod1 | |_mod1.1 |_mod2 Thanks. It is a dependency of mod1 and if your use jar-with-dependency it will be picked up. Google maven jar with dependency. Ron - 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: Copying jar in multi module project with assembly
But the abc.jar I want to refer to is created in mod2 using assembly plug-in as an executable jar mod2/target/abc.jar I don't recall if the assembly plugin automatically (or can be configured to) adds its output to the project as a secondary artifact or if you have to use build-helper to do it, but either way, you need to simply install that artifact from mod2 and then depend on it in mod1. You may not think of it as a dependency, but if you need it inside mod1 for mod1 to work properly, then Maven calls it a dependency. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : m2Eclipse
On Thu, Jun 03, 2010 at 02:10:51PM -0400, Greg Akins wrote: Turns out I missed the requirement for the m2Eclipse extras .. those contain the SCM integration plugins. Looks like Subversive is supported by the SCM Integration.. Subclipse requires an additional provider. Aha! I've been sticking with Eclipse 3.4 for months because, when trying to check out a Maven project set from SCM, I would get a dialog demanding to know which SCM using a disabled droplist control. The list was empty, because no providers were installed. Ugh. It works now, though I had to AltaVista for m2Eclipse extras to find the separate site on which they live. How did we miss this? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ pgpn2NTCsb7af.pgp Description: PGP signature
[ANN] Maven Site Plugin 2.1.1 Released
The Maven team is pleased to announce the release of the Maven Site Plugin, version 2.1.1 The Site Plugin is used to generate a site for the project. The generated site also includes the project's reports that were configured in the reporting section of the POM. http://maven.apache.org/plugins/maven-site-plugin/ You should specify the version in your project's plugin configuration in the build section: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.1.1/version /plugin Release Notes - Maven 2.x Site Plugin - Version 2.1.1 ** Bug * [MSITE-440] - Site generation fails if unable to retrieve schema (in offline mode) * [MSITE-456] - [regression] Site navigation not generated * [MSITE-464] - Site generation fails on !DOCTYPE in xdoc documentation * [MSITE-477] - menu ref=modules/ href's drop the leading character in the href when staging a site ** New Feature * [MSITE-463] - Lithuanian translation * [MSITE-474] - Make validation configurable ** Task * [MSITE-478] - Attach site descriptor as an artifact, not metadata, to the project * [MSITE-482] - Update to Doxia 1.1.3 Enjoy, -The Maven team -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: scm:checkout ignores tag element
Creating a jira ticket at http://jira.codehaus.org/browse/SCM for this doc enhancement is the best approach. /Anders On Fri, Jun 4, 2010 at 17:14, D D dawi...@gmail.com wrote: To answer my own question: scmVersionbranch_name/scmVersion scmVersionTypebranch/scmVersionType Could we add that to example documentation on maven.apache.org? Thanks, Dave On Fri, Jun 4, 2010 at 9:32 AM, D D dawi...@gmail.com wrote: Hello. I have a peculiar problem with cvs/M2 - it ignores tag element during checkout and always goes for the head. I modeled my settings after pom reference found here http://maven.apache.org/pom.html#SCM Someone else had similar problem 2 years back and Wayne tried to help however the thread was left unfinished. Here is my pom snippet: scm connectionscm:cvs:pserver:u...@server :/my/path:ProjectName/connection tagProjectNameTag/tag /scm I tried using mvn 'scm:checkout' - I get the HEAD revision. Using 'mvn -Dscm.tag=ProjectNameTag scm:checkout didn't help either. Your help will be greatly appreciated. Thanks, Dave
Re: Copying jar in multi module project with assembly
m-assembly-p attaches it by default ( http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#attach), for the single goal. At least if you bind it to the package phase. /Anders On Fri, Jun 4, 2010 at 18:24, Wayne Fay wayne...@gmail.com wrote: But the abc.jar I want to refer to is created in mod2 using assembly plug-in as an executable jar mod2/target/abc.jar I don't recall if the assembly plugin automatically (or can be configured to) adds its output to the project as a secondary artifact or if you have to use build-helper to do it, but either way, you need to simply install that artifact from mod2 and then depend on it in mod1. You may not think of it as a dependency, but if you need it inside mod1 for mod1 to work properly, then Maven calls it a dependency. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Custom metadata in a POM?
Is this possible? So, in addition to stuff like developers, is it possible to add additional metadata? I'm asking because the Grails development team is exploring the possibility of using a Maven repository (e.g. Nexus) to host Grails plugins. A Grails plugin is a .zip file, but the Grails environment (and the global Grails Plugin Portal http://www.grails.org/plugin/home) need to read Grails-specific metadata about that .zip without having to download the .zip first. I'm proposing that the POM could serve that purpose *if* POMs can hold additional metadata somehow. Any ideas? Thanks, Les - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Custom metadata in a POM?
On Fri, Jun 4, 2010 at 1:28 PM, Les Hazlewood l...@katasoft.com wrote: Is this possible? So, in addition to stuff like developers, is it possible to add additional metadata? plugins. A Grails plugin is a .zip file, but the Grails environment http://www.grails.org/plugin/home) need to read Grails-specific metadata about that .zip without having to download the .zip first. I'm proposing that the POM could serve that purpose *if* POMs can hold additional metadata somehow. Seems like a potential misuse of the pom.xml. The power of the project object model is that it's standardized and contains the metadata common to all projects (as much as possible). Even if you could do it, why would this custom metadata need to sit in the pom file if it's specific to a particular environment or technology only? Wouldn't be cleaner and simpler to to create a .gpm (Grails Plugin Metadata) with its own schema and whip up a plugin that reads it in from a pre-defined source location, possibly also adding it both to the zip and attaching it as a secondary artifact to the module? If you wanted to specify this metadata as part of the pom, you'd probably still want to create a custom plugin for it. The configuration section for a plugin can carry arbitrary xml data. For example, see jar plugin's manifest customization at http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html. You could follow the same approach for your custom plugin. Kalle - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Custom metadata in a POM?
Hi Kalle, It definitely doesn't have to sit in the POM file if that's considered bad practice. The key is that the Plugin Portal would need to download something lightweight to discover the metadata and not the actual plugin. There is already a Grails plugin.xml file that they use for this purpose, but it currently is bundled inside the plugin .zip - not ideal. I'm sure that can be re-used. The main goal though was to have that plugin.xml somewhere external to the plugin .zip so the Plugin Portal can 'know' about the plugin and not need to download it directly. I'll bring up your suggestions - I think they're great! Thanks! Les On Fri, Jun 4, 2010 at 2:10 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Fri, Jun 4, 2010 at 1:28 PM, Les Hazlewood l...@katasoft.com wrote: Is this possible? So, in addition to stuff like developers, is it possible to add additional metadata? plugins. Seems like a potential misuse of the pom.xml. The power of the project object model is that it's standardized and contains the metadata common to all projects (as much as possible). Even if you could do it, why would this custom metadata need to sit in the pom file if it's specific to a particular environment or technology only? Wouldn't be cleaner and simpler to to create a .gpm (Grails Plugin Metadata) with its own schema and whip up a plugin that reads it in from a pre-defined source location, possibly also adding it both to the zip and attaching it as a secondary artifact to the module? If you wanted to specify this metadata as part of the pom, you'd probably still want to create a custom plugin for it. The configuration section for a plugin can carry arbitrary xml data. For example, see jar plugin's manifest customization at http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html. You could follow the same approach for your custom plugin. Kalle - 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: Custom metadata in a POM?
On Fri, Jun 4, 2010 at 3:07 PM, Les Hazlewood l...@katasoft.com wrote: It definitely doesn't have to sit in the POM file if that's considered bad practice. The key is that the Plugin Portal would need to download something lightweight to discover the metadata and not the actual plugin. There is already a Grails plugin.xml file that they use for this purpose, but it currently is bundled inside the plugin .zip - not ideal. I'm sure that can be re-used. The main goal though was to have that plugin.xml somewhere external to the plugin .zip so the Plugin Portal can 'know' about the plugin and not need to download it directly. I'll bring up your suggestions - I Sounds like publishing the plugin.xml might be the right path since such a thing exists already. Jar plugin additionally packages the pom file by default into the jar, in this case you'd just need to do the opposite. You could very simply create a prototype configuration with the buildhelper plugin, see Attach additional artifacts to your project section at http://mojo.codehaus.org/build-helper-maven-plugin/usage.html. I'd designate a custom type, such as .gpm for that xml file though to make it easily identifiable. Kalle On Fri, Jun 4, 2010 at 2:10 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Fri, Jun 4, 2010 at 1:28 PM, Les Hazlewood l...@katasoft.com wrote: Is this possible? So, in addition to stuff like developers, is it possible to add additional metadata? plugins. Seems like a potential misuse of the pom.xml. The power of the project object model is that it's standardized and contains the metadata common to all projects (as much as possible). Even if you could do it, why would this custom metadata need to sit in the pom file if it's specific to a particular environment or technology only? Wouldn't be cleaner and simpler to to create a .gpm (Grails Plugin Metadata) with its own schema and whip up a plugin that reads it in from a pre-defined source location, possibly also adding it both to the zip and attaching it as a secondary artifact to the module? If you wanted to specify this metadata as part of the pom, you'd probably still want to create a custom plugin for it. The configuration section for a plugin can carry arbitrary xml data. For example, see jar plugin's manifest customization at http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html. You could follow the same approach for your custom plugin. Kalle - 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: Custom metadata in a POM?
Very cool - thanks for the pointer! I'll have to check it out. - Les On Fri, Jun 4, 2010 at 3:27 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Fri, Jun 4, 2010 at 3:07 PM, Les Hazlewood l...@katasoft.com wrote: It definitely doesn't have to sit in the POM file if that's considered bad practice. The key is that the Plugin Portal would need to download something lightweight to discover the metadata and not the actual plugin. There is already a Grails plugin.xml file that they use for this purpose, but it currently is bundled inside the plugin .zip - not ideal. I'm sure that can be re-used. The main goal though was to have that plugin.xml somewhere external to the plugin .zip so the Plugin Portal can 'know' about the plugin and not need to download it directly. I'll bring up your suggestions - I Sounds like publishing the plugin.xml might be the right path since such a thing exists already. Jar plugin additionally packages the pom file by default into the jar, in this case you'd just need to do the opposite. You could very simply create a prototype configuration with the buildhelper plugin, see Attach additional artifacts to your project section at http://mojo.codehaus.org/build-helper-maven-plugin/usage.html. I'd designate a custom type, such as .gpm for that xml file though to make it easily identifiable. Kalle On Fri, Jun 4, 2010 at 2:10 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Fri, Jun 4, 2010 at 1:28 PM, Les Hazlewood l...@katasoft.com wrote: Is this possible? So, in addition to stuff like developers, is it possible to add additional metadata? plugins. Seems like a potential misuse of the pom.xml. The power of the project object model is that it's standardized and contains the metadata common to all projects (as much as possible). Even if you could do it, why would this custom metadata need to sit in the pom file if it's specific to a particular environment or technology only? Wouldn't be cleaner and simpler to to create a .gpm (Grails Plugin Metadata) with its own schema and whip up a plugin that reads it in from a pre-defined source location, possibly also adding it both to the zip and attaching it as a secondary artifact to the module? If you wanted to specify this metadata as part of the pom, you'd probably still want to create a custom plugin for it. The configuration section for a plugin can carry arbitrary xml data. For example, see jar plugin's manifest customization at http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html. You could follow the same approach for your custom plugin. Kalle - 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
Command line output when running JUnit 4 test suite
Is there a way to get better command line output when running a JUnit 4 test suite with Surefire? I'd like to get the same output as when running test classes directly, but I only get the Running ... and Tests run: ... output once for the whole suite, and failure output only appears after the whole suite (comprised of more than hundred test classes) has finished. This means I have to wait much longer until I get feedback. Cheers, Peter -- View this message in context: http://old.nabble.com/Command-line-output-when-running-JUnit-4-test-suite-tp28786362p28786362.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
