Re: Versioning builds
On Thu, Nov 20, 2008 at 5:03 PM, Costin Caraivan [EMAIL PROTECTED] wrote:
Hello.
I'm trying to build a lot of Eclipse plugins with Maven. I've finished the
hardest part (I hope :) ), and now I'm trying to version the builds. That
is, I want the output of the build process to be a zip named something like
this:
com.whatever.me_2.2.2.MMDDHHmm.zip, where 2.2.2 is a relatively static
version, but MMDDHHmm is obviously the timestamp of the build (and it's
not static at all :) ).
Thing is, I can't figure out how to do this. Any ideas? (Can I give Maven
project.version numbers as command line parameters?)
Later on I have to automate this with Continuum, so if anyone knows how to
pass the timestamp from Continuum, be my guest :)
Continuum is not passing timestamp to projects during build but you may use
${continuum.project.nextBuild.number} - this will be a number.
Or, for timestamp, as Mick pointed out - buildnumber plugin.
Regards,
Tomek
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mojo and Spring
Hello spyder71, I think this is more a question for the spring dev list... However, try checking the following: 1) Is the resource *really* in the jar? open the jar and look for the resource and check its location. 2) Try to load the resource yourself as a test: this.getClass().getClassLoader().getResourceAsStream(spring/applicationContext.xml) will throw an exception if the resource is not found. If this works, then consider using the constructor signature that takes a Class as parameter, pass it 'this' PS: Consider posting your question to the spring forum board instead [1], you'll get a better chance of reply. HTH, --w [1] http://forum.springsource.org/index.php On Thu, Nov 20, 2008 at 5:13 PM, spyder71 [EMAIL PROTECTED] wrote: Hi, I am writting a Mojo that should use Spring fwk. But when i a run the Mojo, it cannot find the spring beans config file (which is packaged into the mojo jar). I use ClassPathXmlApplicationContext to resolve the config file, but no success Error is the following : Embedded error: IOException parsing XML document from class path resource [spring/applicationContext.xml]; nested exception is java.io.FileNotFoundException: class path resource [spring/applicationContext.xml] cannot be opened because it does not exist Has any one any hints ? tx ! -- View this message in context: http://www.nabble.com/Mojo-and-Spring-tp20604693p20604693.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Versioning builds
If I go one step further and want to install/deploy the build with this build
number as a version... What do I do? :)
Right now, when I install, the artifact is uploaded with the version, not
the finalName.
So artifact-1.0.0-MMDDHHmm.zip becomes artifact-1.0.0.zip :)
Any ideas? (basically I want to change the version from the build launcher
(Continuum). Should I launch some sort of ant script which runs the Maven
project with a changed version? (sounds ok? :) ).
Thanks,
Costin.
Tomasz Pik wrote:
Continuum is not passing timestamp to projects during build but you may
use
${continuum.project.nextBuild.number} - this will be a number.
Or, for timestamp, as Mick pointed out - buildnumber plugin.
Regards,
Tomek
--
View this message in context:
http://www.nabble.com/Versioning-builds-tp20604494p20618244.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Versioning builds
On Friday 21 November 2008 Costin Caraivan wrote: If I go one step further and want to install/deploy the build with this build number as a version... What do I do? :) You read this thread from last week: http://www.nabble.com/buildnumber-value-not-making-it-to-local--repo-to20492362.html#a20492410 hth, - martin signature.asc Description: This is a digitally signed message part.
compiler's FATAL ERROR
Hello. I have this error due making the project: mvn package [INFO] Scanning for projects... [INFO] [INFO] Building helloWorld App [INFO]task-segment: [package] [INFO] [INFO] [resources:resources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [compiler:compile] [INFO] Compiling 2 source files to /usr/share/tomcat5.5/server/webapps/helloWorld/target/classes [INFO] [resources:testResources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /usr/share/tomcat5.5/server/webapps/helloWorld/src/test/resources [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Could not instatiate converter : com.thoughtworks.xstream.converters.enums.EnumMapConverter : null Could not access java.util.EnumMap.keyType field [INFO] [INFO] Trace com.thoughtworks.xstream.XStream$InitializationException: Could not instatiate converter : com.thoughtworks.xstream.converters.enums.EnumMapConverter : null at com.thoughtworks.xstream.XStream.dynamicallyRegisterConverter(XStream.java:668) at com.thoughtworks.xstream.XStream.setupConverters(XStream.java:640) at com.thoughtworks.xstream.XStream.init(XStream.java:375) at com.thoughtworks.xstream.XStream.init(XStream.java:301) at org.apache.maven.plugin.war.util.WebappStructureSerializer.init(WebappStructureSerializer.java:49) at org.apache.maven.plugin.war.AbstractWarMojo.init(AbstractWarMojo.java:295) at org.apache.maven.plugin.war.WarMojo.init(WarMojo.java:47) at java.lang.Class.newInstance(libgcj.so.81) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:425) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at java.lang.reflect.Method.invoke(libgcj.so.81) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.reflect.InvocationTargetException at java.lang.reflect.Constructor.newInstance(libgcj.so.81) at com.thoughtworks.xstream.XStream.dynamicallyRegisterConverter(XStream.java:661) ...29 more Caused by: java.lang.RuntimeException: Could not access java.util.EnumMap.keyType field at com.thoughtworks.xstream.core.util.Fields.find(Fields.java:18) at com.thoughtworks.xstream.converters.enums.EnumMapConverter.init(EnumMapConverter.java:29) at java.lang.reflect.Constructor.newInstance(libgcj.so.81) ...30 more [INFO] [INFO] Total time: 50 seconds [INFO] Finished at: Fri Nov 21 14:58:40 GMT+03:00 2008 [INFO] Final Memory: 31M/50M [INFO] I use: 1)kubuntu 7 2)Maven version: 2.0.8 Java version: 1.5.0 OS name: linux version:
Webstart plugin: How to set Velocity variables?
Hi
I'm using the JNLP Velocity template within the Webstart plugin.
However, I don't know how to set my own variables. Clearly, Maven
properties can't be used, but there must be some way to transfer ${foo}
(Maven) to $foo (Velocity).
I didn't find any information in the documentation, can someone help me
out?
Also, is there a list of the predefined Velocity variables that the
plugin sets?
Third: I need to change the jar nodes that $dependencies generates. Is
there a way to do this (specifically, I'd like to set download=eager).
Thanks for any help,
Eric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Webstart plugin: Resources copied to wrong folder
Hi I'm using the Webstart plugin to copy resources to the final artefact, as described by http://mojo.codehaus.org/webstart/webstart-maven-plugin/jnlp-mojos-overv iew.html The section Input/Output states that anything in src/main/jnlp/resources/ will be copied to the work directory target/jnlp/ When building, however, the files are not copied into the work directory's root, but into target/jnlp/lib/ Is this a known bug? Best regards, Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Webstart plugin: How to set Velocity variables?
Sorry, seems like I didn't find the right page. See below...
Best regards,
Eric
Hi
I'm using the JNLP Velocity template within the Webstart plugin.
However, I don't know how to set my own variables. Clearly, Maven
properties can't be used, but there must be some way to
transfer ${foo}
(Maven) to $foo (Velocity).
I didn't find any information in the documentation, can
someone help me
out?
http://mojo.codehaus.org/webstart/webstart-maven-plugin/jnlp-mojos-overv
iew.html
- JNLP file generation
The key of the property is taken
Perhaps the documentation isn't clear enough about $property, because at
first I thought I had to use something like $property.foo
Also, is there a list of the predefined Velocity variables that the
plugin sets?
See above
Third: I need to change the jar nodes that $dependencies
generates. Is
there a way to do this (specifically, I'd like to set
download=eager).
From looking at the source (getDependenciesText()), this seems to be
hard-coded, which is a pity.
Should I write an RFE?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: compiler's FATAL ERROR
[EMAIL PROTECTED] wrote: Hello. I have this error due making the project: mvn package [INFO] Scanning for projects... [INFO] -- -- [INFO] Building helloWorld App [INFO]task-segment: [package] [INFO] -- -- [INFO] [resources:resources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [compiler:compile] [INFO] Compiling 2 source files to /usr/share/tomcat5.5/server/webapps/helloWorld/target/classes [INFO] [resources:testResources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /usr/share/tomcat5.5/server/webapps/helloWorld/src/test/resources [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] -- -- [ERROR] FATAL ERROR [INFO] -- -- [INFO] Could not instatiate converter : com.thoughtworks.xstream.converters.enums.EnumMapConverter : null Could not access java.util.EnumMap.keyType field [INFO] -- -- [INFO] Trace com.thoughtworks.xstream.XStream$InitializationException: Could not instatiate converter : com.thoughtworks.xstream.converters.enums.EnumMapConverter : null at com.thoughtworks.xstream.XStream.dynamicallyRegisterConverter( XStream.java:668) at com.thoughtworks.xstream.XStream.setupConverters(XStream.java:640) at com.thoughtworks.xstream.XStream.init(XStream.java:375) at com.thoughtworks.xstream.XStream.init(XStream.java:301)at org.apache.maven.plugin.war.util.WebappStructureSerializer.in it(WebappStructureSerializer.java:49) at org.apache.maven.plugin.war.AbstractWarMojo.init(AbstractWar Mojo.java:295) at org.apache.maven.plugin.war.WarMojo.init(WarMojo.java:47) at java.lang.Class.newInstance(libgcj.so.81) at org.codehaus.plexus.component.factory.java.JavaComponentFactor y.newInstance(JavaComponentFactory.java:44) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInst ance(DefaultPlexusContainer.java:1464) at org.codehaus.plexus.component.manager.AbstractComponentManager .createComponentInstance(AbstractComponentManager.java:93)at org.codehaus.plexus.component.manager.PerLookupComponentManage r.getComponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexu sContainer.java:331) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexu sContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo (DefaultPluginManager.java:566) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(Defau ltPluginManager.java:425) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa ls(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa lWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa l(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa lAndHandleFailures(DefaultLifecycleExecutor.java:311)at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTas kSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De faultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at java.lang.reflect.Method.invoke(libgcj.so.81)at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.reflect.InvocationTargetException at java.lang.reflect.Constructor.newInstance(libgcj.so.81)at com.thoughtworks.xstream.XStream.dynamicallyRegisterConverter( XStream.java:661) ...29 more Caused by: java.lang.RuntimeException: Could not access java.util.EnumMap.keyType field at com.thoughtworks.xstream.core.util.Fields.find(Fields.java:18) at com.thoughtworks.xstream.converters.enums.EnumMapConverter.in it(EnumMapConverter.java:29) at java.lang.reflect.Constructor.newInstance(libgcj.so.81)...30 more [INFO] -- -- [INFO] Total time: 50 seconds [INFO] Finished at: Fri Nov 21 14:58:40 GMT+03:00 2008 [INFO] Final Memory: 31M/50M [INFO]
Re: Project versioning
Hi Stephen,
thanks to advice to use buildnumber plugin, I didn't know it before...
Now, please be patient, can you explain me better the meaning of and filter
in the project version *and* the
build number ?
Thanks again
regards
Raffaele
Stephen Connolly-2 wrote:
use the buildnumber plugin and filter in the project version *and* the
build number
Sent from my iPod
On 20 Nov 2008, at 17:13, Raffaele [EMAIL PROTECTED] wrote:
Hi,
unfortunately I'm here againmy boss is not satisfied with this
solution:
- Due to old consuetudes he would like the following scenario:
1) In the pom version tag, he wants specify only Major.Minor, ex: 1.5
2) In the file (version.cfg) that will be read by java code to show
a label
informing user about product build number, he wants that an automatic
process append to Major.Minor (taken from pom during build phase)
another
version, example 1.5.562
3) He wants that, each time I run mvn package, maven updates that
file
incrementing by one that number
Do you believe is it possible doing it with maven?
Thanks in advance and scuse me again (I'm agree with your
vision, my
boss not :-) )
Best regards
Raffaele
Stephen Connolly-2 wrote:
I always rejig my resources folders so that I have
src/main/resources/filtered
src/main/resources/verbatim
src/test/resources/filtered
src/test/resources/verbatim
If only I could come up with a good version for webapps
2008/11/20 Brian E. Fox [EMAIL PROTECTED]
No you can't filter only one file that I recall, but you can make
something like src/main/filtered-resources and enable filtering on
that
folder only.
-Original Message-
From: Raffaele [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 10:00 AM
To: users@maven.apache.org
Subject: Re: Project versioning
Ok guys thank you all,
There is only one thing that I'm continuing to not understand
In my src/main/resources I have many many files.
I would like to filter only one of those files
but putting this in my pom
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
has effect to try to filter all the files
How could I say maven to filter only one specific file and not a
full
folder?
Best regards
Raffaele
Stephen Connolly-2 wrote:
Alternatively, you could pull the version info from the pom.xml
that
gets
stashed in a sub-folder of META-INF by default but this might
require
a
bit of work since the version could have been inherited from the
parent
version...
Safest way is as Brian suggests... and it has the added advantage
of
not
tieing you to maven for your build.
What we do is we have a properties file with
version=${project.version}
as the only entry. We then turn on filtering for that properties
file,
and
to access it from code we just use getClass().getResource(/path to
versions.properties)
2008/11/20 Brian E. Fox [EMAIL PROTECTED]
Normally you just have a properties file that is filtered during
the
build and at runtime your code reads the value.
-Original Message-
From: Raffaele [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 8:53 AM
To: users@maven.apache.org
Subject: Project versioning
Hi all,
I would like some advices about how automatically update a
properties
file
inserting into an incremental value representing the build
number
My scenario:
- I have a web application and I would like to insert in some
page,
the
build version
- I would like to know if is there a way to obtain the project
version
from
the java code in a way that I'm able to insert a label showing
that
version...
- If there wasn't such a way, I was thinking to write project
version
in
a
file, then from java code I would read that file and would
update my
label...
Have you got any idea? Obviously I would like to take advantage of
Maven
and
I would prefer to avoid another file
Thanks in advance,
Raffaele Gambelli
--
View this message in context:
http://www.nabble.com/Project-versioning-tp20601486p20601486.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Project-versioning-tp20601486p20603012.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Re: Versioning builds
Thank you for the information. I will try to get more information about the current versioning system, to see why it needs to be this way, maybe I can adjust the project instead of Maven's versioning :) matinh wrote: On Friday 21 November 2008 Costin Caraivan wrote: If I go one step further and want to install/deploy the build with this build number as a version... What do I do? :) You read this thread from last week: http://www.nabble.com/buildnumber-value-not-making-it-to-local--repo-to20492362.html#a20492410 hth, - martin -- View this message in context: http://www.nabble.com/Versioning-builds-tp20604494p20626087.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Project versioning
version=${project.version}.${someotherproperty}
2008/11/21 Raffaele [EMAIL PROTECTED]
Hi Stephen,
thanks to advice to use buildnumber plugin, I didn't know it before...
Now, please be patient, can you explain me better the meaning of and
filter
in the project version *and* the
build number ?
Thanks again
regards
Raffaele
Stephen Connolly-2 wrote:
use the buildnumber plugin and filter in the project version *and* the
build number
Sent from my iPod
On 20 Nov 2008, at 17:13, Raffaele [EMAIL PROTECTED] wrote:
Hi,
unfortunately I'm here againmy boss is not satisfied with this
solution:
- Due to old consuetudes he would like the following scenario:
1) In the pom version tag, he wants specify only Major.Minor, ex: 1.5
2) In the file (version.cfg) that will be read by java code to show
a label
informing user about product build number, he wants that an automatic
process append to Major.Minor (taken from pom during build phase)
another
version, example 1.5.562
3) He wants that, each time I run mvn package, maven updates that
file
incrementing by one that number
Do you believe is it possible doing it with maven?
Thanks in advance and scuse me again (I'm agree with your
vision, my
boss not :-) )
Best regards
Raffaele
Stephen Connolly-2 wrote:
I always rejig my resources folders so that I have
src/main/resources/filtered
src/main/resources/verbatim
src/test/resources/filtered
src/test/resources/verbatim
If only I could come up with a good version for webapps
2008/11/20 Brian E. Fox [EMAIL PROTECTED]
No you can't filter only one file that I recall, but you can make
something like src/main/filtered-resources and enable filtering on
that
folder only.
-Original Message-
From: Raffaele [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 10:00 AM
To: users@maven.apache.org
Subject: Re: Project versioning
Ok guys thank you all,
There is only one thing that I'm continuing to not understand
In my src/main/resources I have many many files.
I would like to filter only one of those files
but putting this in my pom
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
has effect to try to filter all the files
How could I say maven to filter only one specific file and not a
full
folder?
Best regards
Raffaele
Stephen Connolly-2 wrote:
Alternatively, you could pull the version info from the pom.xml
that
gets
stashed in a sub-folder of META-INF by default but this might
require
a
bit of work since the version could have been inherited from the
parent
version...
Safest way is as Brian suggests... and it has the added advantage
of
not
tieing you to maven for your build.
What we do is we have a properties file with
version=${project.version}
as the only entry. We then turn on filtering for that properties
file,
and
to access it from code we just use getClass().getResource(/path to
versions.properties)
2008/11/20 Brian E. Fox [EMAIL PROTECTED]
Normally you just have a properties file that is filtered during
the
build and at runtime your code reads the value.
-Original Message-
From: Raffaele [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 8:53 AM
To: users@maven.apache.org
Subject: Project versioning
Hi all,
I would like some advices about how automatically update a
properties
file
inserting into an incremental value representing the build
number
My scenario:
- I have a web application and I would like to insert in some
page,
the
build version
- I would like to know if is there a way to obtain the project
version
from
the java code in a way that I'm able to insert a label showing
that
version...
- If there wasn't such a way, I was thinking to write project
version
in
a
file, then from java code I would read that file and would
update my
label...
Have you got any idea? Obviously I would like to take advantage of
Maven
and
I would prefer to avoid another file
Thanks in advance,
Raffaele Gambelli
--
View this message in context:
http://www.nabble.com/Project-versioning-tp20601486p20601486.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Project-versioning-tp20601486p20603012.html
Sent from the Maven - Users
providing the provided dependencies using Maven
Before I look into writing a custom plugin: is there any way to get Maven to produce an artifact (zip?) containing the dependencies with scope provided? Most of the jar files required by our web app will be provided by Tomcat outside of the war file. But since I also need to be the one to provide these jars, it would be ideal if I could have Maven produce them based on declared scope in the POM files. Without this, we are sure to see mismatches in compile vs runtime library versions over time. -Andrew
Maven multi-module setup hierarchical or flat folder hierarchy
Hi Maven gurus, I would like to know what is the best recommended way of definining maven multi-module projects? Is it the hierarchical ? parent/pom.xml parent/childA/pom.xml parent/childB/pom.xml or flat-structure ? parent/pom.xml childA/pom.xml childB/pom.xml I'm using eclipseIDE with m2eclipse and hierarchical multi-module structure and the maven release plugin to manage my release cycle. My setup works reasonably well but I have seen others using the flat-structure. Can someone tell me what are the pros and cons of both approaches? I'm not sure which one is best. Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
Transitive dependencies for dependency of type pom
I have pom A of type pom which lists a bunch of dependencies and defines a repository (call it repo1) for the dependency. I have a project with pom B of type jar which has dependency on pom A. When building pom B it downloads all dependencies in pom A from repo1. However it fails to bring in all transitive dependencies for the dependencies listed in pom A. This happens since none of the poms for dependencies in pom a are downloaded. Do I have to define repo1 in pom B? -- View this message in context: http://www.nabble.com/Transitive-dependencies-for-dependency-of-type-pom-tp20628873p20628873.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: providing the provided dependencies using Maven
have a look at the copyDependencies goal of the maven-dependency- plugin (or it might be the copy-dependencies goal) Sent from my iPod On 21 Nov 2008, at 19:23, Andrew Goktepe [EMAIL PROTECTED] wrote: Before I look into writing a custom plugin: is there any way to get Maven to produce an artifact (zip?) containing the dependencies with scope provided? Most of the jar files required by our web app will be provided by Tomcat outside of the war file. But since I also need to be the one to provide these jars, it would be ideal if I could have Maven produce them based on declared scope in the POM files. Without this, we are sure to see mismatches in compile vs runtime library versions over time. -Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
LATEST and RELEASE
I thought I these two keywords LATEST and RELEASE were supported versions that could be used in a pom.xml. Does anyone know more about them, an I mistaken?
Is the dependency for doxia-core missing the version tag in the doxia-book pom?
Is the dependency for doxia-core missing the version tag in the
doxia-book pom [1]?
dependency
groupIdorg.apache.maven.doxia/groupId
artifactIddoxia-core/artifactId
/dependency
dependency
groupIdorg.apache.maven.doxia/groupId
artifactIddoxia-module-xdoc/artifactId
version${projectVersion}/version
/dependency
Paul Spencer
[1]http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/doxia/doxia-book/1.0-beta-1-SNAPSHOT/doxia-book-1.0-beta-1-20081119.231737-2.pom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-release-plugin svn branch command failed
I've run into the same problem, but somehow I managed to figure it out!! I found that if I simply run an svn up right before executing the mvn release:branch command it works! Note that there are NO changes downloaded from the scm, but for whatever reason it worked for me. Peter Nedonosko wrote: Hi guys! I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java 1.5.0_15 and svn 1.5.4. I cannot run release:branch goal from trunk successful. Branch commit failed on command svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit . http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC I have tried this command manually svn copy . http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC it fails too. But if I replace '.' on full path of the trunk it will works svn copy http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC I feel it's a bug, but may be I do smth wrong here? Anybody can help or comment the usecase? -- View this message in context: http://www.nabble.com/maven-release-plugin-svn-branch-command-failed-tp20321804p20629606.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LATEST and RELEASE
I thought I these two keywords LATEST and RELEASE were supported versions that could be used in a pom.xml. 9.3.1.3. LATEST and RELEASE Versions http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0e9801 Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is the dependency for doxia-core missing the version tag in the doxia-book pom?
Is the dependency for doxia-core missing the version tag in the doxia-book pom [1]? Is it perhaps mentioned in a dependencyManagement section in the pom, or a parent? Otherwise, it does seem odd. Try running mvn help:effective-pom on it and see what that shows. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LATEST and RELEASE
From my experience, using RELEASE as a version identifier works for any kinds of artifacts given the fact that you should have install or deployed the artifact using the parameter updateReleaseInfo to true. Using the LATEST version identifier is available only for Maven plugins, not for standards artifacts, because the artifact metadata needs to store this information and this is only possible through the maven plugin plugin. Regards Jeff MAURY On Fri, Nov 21, 2008 at 10:04 PM, Timothy Reilly [EMAIL PROTECTED]wrote: I thought I these two keywords LATEST and RELEASE were supported versions that could be used in a pom.xml. Does anyone know more about them, an I mistaken? -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal Mes CDs à récupérer: http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTAhl=en
usage of maven-release-plugin's branch feature
I am trying to create an automated branching mechanism, and am trying to understand the branch goal of the release plugin. According to the Specify versions on the command line. section on the plugin's page I should be able to specify the next development version's number right on the command line. There's an example there, but I can't for the life of my figure it out... It talks about using something like -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT on the plugin's page, but it doesn't seem to work. The problem I am having is that ALL of our version numbers are 3 digits (e.g. X.Y.Z-SNAPSHOT), and the next dev version needs to have the minor version upped (e.g. Y+1). There is absolutely no way we can use just two as suggested elsewhere in the list. I want to be able to pass parameters to the plugin to specify that my next development version should be X.Y+1.0-SNAPSHOT -- I can pass the value in... I just can't seem to figure out how. Any thoughts, especially examples, would be welcome. Thanks, Trevor -- View this message in context: http://www.nabble.com/usage-of-maven-release-plugin%27s-branch-feature-tp20629883p20629883.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LATEST and RELEASE
In my opinion, this chapter is bogus Jeff MAURY On Fri, Nov 21, 2008 at 10:18 PM, Wayne Fay [EMAIL PROTECTED] wrote: I thought I these two keywords LATEST and RELEASE were supported versions that could be used in a pom.xml. 9.3.1.3. LATEST and RELEASE Versions http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0e9801 Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal Mes CDs à récupérer: http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTAhl=en
Re: Is the dependency for doxia-core missing the version tag in the doxia-book pom?
Wayne Fay wrote: Is the dependency for doxia-core missing the version tag in the doxia-book pom [1]? Is it perhaps mentioned in a dependencyManagement section in the pom, or a parent? Otherwise, it does seem odd. Try running mvn help:effective-pom on it and see what that shows. Yes, the version is correctly displayed by help:effective-pom. I guess the version comes from dependencyManagement. Curious, the dependency on doxia-core is mentioned twice, once with the default scope and then with test scope. dependencies dependency groupIdorg.apache.maven.doxia/groupId artifactIddoxia-core/artifactId version1.0-beta-1-SNAPSHOT/version /dependency ... dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-cli/artifactId version1.0/version /dependency dependency groupIdorg.apache.maven.doxia/groupId artifactIddoxia-core/artifactId version1.0-beta-1-SNAPSHOT/version classifiertests/classifier scopetest/scope /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.2/version scopetest/scope /dependency /dependencies Wayne Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is the dependency for doxia-core missing the version tag in the doxia-book pom?
Wayne Fay wrote: Is the dependency for doxia-core missing the version tag in the doxia-book pom [1]? Is it perhaps mentioned in a dependencyManagement section in the pom, or a parent? Otherwise, it does seem odd. Try running mvn help:effective-pom on it and see what that shows. Yes, the version is correctly displayed by help:effective-pom. I guess the version comes from dependencyManagement. Curious, the dependency on doxia-core is mentioned twice, once with the default scope and then with test scope. dependencies dependency groupIdorg.apache.maven.doxia/groupId artifactIddoxia-core/artifactId version1.0-beta-1-SNAPSHOT/version /dependency ... dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-cli/artifactId version1.0/version /dependency dependency groupIdorg.apache.maven.doxia/groupId artifactIddoxia-core/artifactId version1.0-beta-1-SNAPSHOT/version classifiertests/classifier scopetest/scope /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.2/version scopetest/scope /dependency /dependencies Wayne Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: LATEST and RELEASE
Jeff, From my experience, using RELEASE as a version identifier works for any kinds of artifacts given the fact that you should have install or deployed the artifact using the parameter updateReleaseInfo to true. Thanks. That's very helpful! I was about to complain it does not work - but first I need to fix somethings it seems. You also made me go look in the metadata.xml and it turns out our qualifiers or our build process might be messing things up. I have to check if we're using deploy or install too (if install what we use for -DupdateReleaseInfo= I'm guess it's not set). The metadata version hasn't changed in 5 releases. By chance have you used it for parent version? We're planning to put a real version in as late (late binding) as possible using a custom release plugin to save the dev's from the hassle updating a couple of hundered projects everytime we do something to the corporate build pom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
what filtering does assembly plugin provide?
I'm trying to inject some properties from my pom.xml into a shell script using
the assembly plugin. Is that possible? Is there some special syntax that I
should be using? In my pom.xml I have
profile
iddev/id
properties
layerdev/layer
etc.
For my assembly descriptor I have
assembly
iddeploy-script/id
formats
formatdir/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
baseDirectory//baseDirectory
files
file
sourcesrc/main/scripts/deploy.sh/source
destNamedeploy-${pom.layer}.sh/destName
filteredtrue/filtered
lineEndingunix/lineEnding
/file
/files
/assembly
And the deploy.sh script has at the top
export REL=${project.version}
export LAYER=${pom.layer}
export SVNURL=${pom.developerConnection}
The created script in the target directory is correctly named deploy-dev.sh,
and in it the ${project.version} is replaced by the project version, but the 2
${pom properties aren't.
Am I not using them or specifying them correctly?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: LATEST and RELEASE
If you intent to use it for you corporate parent pom, I think this should work assumed you deploy or install it using the updateReleaseInfo to true and refer the corporate parent pom using the RELEASE version. Regards Jeff MAURY On Fri, Nov 21, 2008 at 10:55 PM, Timothy Reilly [EMAIL PROTECTED]wrote: Jeff, From my experience, using RELEASE as a version identifier works for any kinds of artifacts given the fact that you should have install or deployed the artifact using the parameter updateReleaseInfo to true. Thanks. That's very helpful! I was about to complain it does not work - but first I need to fix somethings it seems. You also made me go look in the metadata.xml and it turns out our qualifiers or our build process might be messing things up. I have to check if we're using deploy or install too (if install what we use for -DupdateReleaseInfo= I'm guess it's not set). The metadata version hasn't changed in 5 releases. By chance have you used it for parent version? We're planning to put a real version in as late (late binding) as possible using a custom release plugin to save the dev's from the hassle updating a couple of hundered projects everytime we do something to the corporate build pom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal Mes CDs à récupérer: http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTAhl=en
[doxia-maven-plugin] How to get images from book's apt directory into site?
I am working with doxia-maven-plugin 1.0-alpha-11. One of my apt files contains a figure, as defined by [myImage.png]. Per the documentation[1], the image file for the figure is in the same directory as the apt file, src/books/user-guide/apt. mvn site generated the pages for the book, including the img src=myImage.png / tag to include the image. Although I have followed the Configuring Maven Doxia Plug-in example [2] with the exception if setting the plugin version to 1.0-alpha-11 and using only the xdoc format, the image file is not in the same directory as the generated html. Suggestions? Paul Spencer [1] http://maven.apache.org/doxia/references/apt-format.html [2] http://maven.apache.org/doxia/book/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to deploy images onto internal maven repositories.
Hi, I need to have some image files on the maven repositories and so I have to deploy images onto internal maven repositories. I'm more concerned on what would be the packaging mode to deploy images onto maven repositories. Can any one please advise what would be the exact maven command to deploy images onto the maven repositories. Thanks Regards, Logu Rajamanickam - This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.
Re: How to deploy images onto internal maven repositories.
On Fri, Nov 21, 2008 at 3:43 PM, [EMAIL PROTECTED] wrote: I need to have some image files on the maven repositories and so I have to deploy images onto internal maven repositories. I'm more concerned on what would be the packaging mode to deploy images onto maven repositories. It depends on how you want to use the images later. Without knowing any more, I would suggest packaging them in a jar and using the normal deploy/release mechanism. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to deploy images onto internal maven repositories.
try ant:copy example: ant:copy todir=targetFolder filtering=false overwrite=true ant:fileset dir=SourceFolder includes=*.jpg /ant:fileset /ant:copy HTH Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. To: users@maven.apache.org Subject: How to deploy images onto internal maven repositories. From: [EMAIL PROTECTED] Date: Fri, 21 Nov 2008 17:43:59 -0500 Hi, I need to have some image files on the maven repositories and so I have to deploy images onto internal maven repositories. I'm more concerned on what would be the packaging mode to deploy images onto maven repositories. Can any one please advise what would be the exact maven command to deploy images onto the maven repositories. Thanks Regards, Logu Rajamanickam - This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. _ Access your email online and on the go with Windows Live Hotmail. http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_access_112008
Re: what filtering does assembly plugin provide?
On Fri, 2008-11-21 at 14:07 -0800, Rusty Wright wrote:
I'm trying to inject some properties from my pom.xml into a shell script
using the assembly plugin. Is that possible? Is there some special syntax
that I should be using? In my pom.xml I have
[snip]
And the deploy.sh script has at the top
export REL=${project.version}
export LAYER=${pom.layer}
export SVNURL=${pom.developerConnection}
I believe you want:
export LAYER=${layer}
export SVNURL=${scm.developerConnection}
(untested)
-Olivier
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven multi-module setup hierarchical or flat folder hierarchy
Hello Guillaume, I must say I've tried both with almost equal success, the one positive advantage of the hierarchical option is that it allows the option of having multiple depths of hierarchy without the quick growth of the number of folders on a level. It also helps organize the structure when there's a large number of sub-projects. My 2 cents :-D w On Fri, Nov 21, 2008 at 8:44 PM, Jeudy, Guillaume [EMAIL PROTECTED]wrote: Hi Maven gurus, I would like to know what is the best recommended way of definining maven multi-module projects? Is it the hierarchical ? parent/pom.xml parent/childA/pom.xml parent/childB/pom.xml or flat-structure ? parent/pom.xml childA/pom.xml childB/pom.xml I'm using eclipseIDE with m2eclipse and hierarchical multi-module structure and the maven release plugin to manage my release cycle. My setup works reasonably well but I have seen others using the flat-structure. Can someone tell me what are the pros and cons of both approaches? I'm not sure which one is best. Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
Re: [doxia-maven-plugin] How to get images from book's apt directory into site?
Hello Paul, I had the same situation a while ago, I found that including the full name (with extension) works better. HTH, w On Fri, Nov 21, 2008 at 11:28 PM, Paul Spencer [EMAIL PROTECTED] wrote: I am working with doxia-maven-plugin 1.0-alpha-11. One of my apt files contains a figure, as defined by [myImage.png]. Per the documentation[1], the image file for the figure is in the same directory as the apt file, src/books/user-guide/apt. mvn site generated the pages for the book, including the img src=myImage.png / tag to include the image. Although I have followed the Configuring Maven Doxia Plug-in example [2] with the exception if setting the plugin version to 1.0-alpha-11 and using only the xdoc format, the image file is not in the same directory as the generated html. Suggestions? Paul Spencer [1] http://maven.apache.org/doxia/references/apt-format.html [2] http://maven.apache.org/doxia/book/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: what filtering does assembly plugin provide?
Thanks; I started seeing through the fog as well. I don't know where I came up
with that ${pom naming scheme. The scm variable needs project. prepended, so
what works is
export REL=${project.version}
export LAYER=${layer}
export SVNURL=${project.scm.developerConnection}
Thanks again!
Olivier Dehon wrote:
On Fri, 2008-11-21 at 14:07 -0800, Rusty Wright wrote:
I'm trying to inject some properties from my pom.xml into a shell script using
the assembly plugin. Is that possible? Is there some special syntax that I
should be using? In my pom.xml I have
[snip]
And the deploy.sh script has at the top
export REL=${project.version}
export LAYER=${pom.layer}
export SVNURL=${pom.developerConnection}
I believe you want:
export LAYER=${layer}
export SVNURL=${scm.developerConnection}
(untested)
-Olivier
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [doxia-maven-plugin] How to get images from book's apt directory into site?
Hi Paul,
# try placing images relative to {basedir}/src/site/resources
# maven-antrun-plugin phasepre-site/phase
# is good time to render other formats like docbook
# and copy images from your source tree to appropriate resources folder.
# for example;
# in {basedir}/src/site/apt/index.apt using the following image reference.
[ 1.doc/images/labbenchmap.jpg ] Lab Office 65 layout
# and the corresponding image located here.
{basedir}/src/site/resources/1.doc/images/labbenchmap.jpg
# after call to mvn -X -e site -o mvn_site.log
# results are found {basedir}/target/site/1.doc/images/
given your {basedir}/src/books/user-guide/apt
I would think {basedir}/src/resources/books/user-guide/myImage.png likely place.
Regards,
Sean
-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 2:29 PM
To: Maven Users List
Subject: [doxia-maven-plugin] How to get images from book's apt directory into
site?
I am working with doxia-maven-plugin 1.0-alpha-11. One of my apt files
contains a figure, as defined by [myImage.png]. Per the
documentation[1], the image file for the figure is in the same directory
as the apt file, src/books/user-guide/apt. mvn site generated the
pages for the book, including the img src=myImage.png / tag to
include the image. Although I have followed the Configuring Maven
Doxia Plug-in example [2] with the exception if setting the plugin
version to 1.0-alpha-11 and using only the xdoc format, the image file
is not in the same directory as the generated html. Suggestions?
Paul Spencer
[1] http://maven.apache.org/doxia/references/apt-format.html
[2] http://maven.apache.org/doxia/book/index.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-release-plugin svn branch command failed
tespackman wrote: I've run into the same problem, but somehow I managed to figure it out!! I found that if I simply run an svn up right before executing the mvn release:branch command it works! Note that there are NO changes downloaded from the scm, but for whatever reason it worked for me. This is a known issue with the release plugin and Subversion 1.5.1+. You'll run into the same issue on a release:prepare. The problem has to do with the fact that the release plugin checks into a new branch (or tag) directly from the working copy, rather than committing and copying first. (Reason has to do with making sure nothing committed on the trunk while the preparation goals are running gets into the tag.) This worked fine up through SVN 1.5.0. Googling on the error message you get (something about xyz already exists) should get you some additional details. Best known workaround I have for now is to downgrade to SVN 1.5.0; last I heard this is still an issue with maven-release-plugin 2.0-beta-8 and SVN 1.5.4. - John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: usage of maven-release-plugin's branch feature
I want to be able to pass parameters to the plugin to specify that my next development version should be X.Y+1.0-SNAPSHOT -- I can pass the value in... I just can't seem to figure out how. I'm not familiar with the command-line options to specify the next-version parameters. But as I remember, the default suggested version is the latest version with the most specific number specified. That is, if you are releasing 3.4, it will suggest 3.5. but if you are releasing 3.4.0, it will suggest 3.4.1. Perhaps that tidbit will be useful? - John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: contents in webapp/META-INF are not packaged in the war
Hi all, Please ignore my question. It is my neglect to cause this problem. Thanks, Rice On Thu, Nov 20, 2008 at 8:07 PM, Samuli Saarinen [EMAIL PROTECTED] wrote: Rice Yeh wrote: Hi, I have a web project with some files under webapp/META-INF, like tomcat's context.xml. I find they are not included in the result war file. I cannot find any configuration parameter in war:war plugin. Hello, Is this what you are looking for? http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html Although with a quick test using maven 2.0.9 and war-plugin 2.1-alpha-1 a file under webapp/META-INF ends up in the war under META-INF -Samuli - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
