deploying war automatically to tomcat
hi i want to deploy war file to webapps folder under tomcat automatically after running mvn install like in ant .can u please help -- View this message in context: http://www.nabble.com/deploying-war-automatically-to--tomcat-tf4191146s177.html#a11918830 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: Excluding build .jars from .war
On 7/30/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote: > I was building off of the struts2-portlet-2.0.x.war example. So I guess > that means I need to travel up the pom parents tree and merge all the > dependencies and other elements into my own pom? No, you should just declare dependencies on the jars you need. Maven will include transitive dependencies for you. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding build .jars from .war
I'd assume this is happening because some parent (or grandparent, or grand-grandparent, etc) of your pom is including those jars as a dependency. And so your own project is bringing them in as a dependency, so they are included in your war. You could try "mvn -X package" and then search the text-tree dependency output to find out what specific artifact is bringing those dependencies in, but I think this is a wasted effort, and agree with Wendy that you need to remove that extraneous tag and fix up your own dependencies. If you're lucky, the problem will resolve itself with these changes. Wayne On 7/30/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote: > I was building off of the struts2-portlet-2.0.x.war example. So I guess > that means I need to travel up the pom parents tree and merge all the > dependencies and other elements into my own pom? I will try and attempt > not to break anything. Thank you. Do you happen to know why all those > .jars are being included in my .war? > > Fred > > Wendy Smoak wrote: > > On 7/30/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote: > > > >> > >> org.apache.struts > >> struts2-apps > >> 2.0.9 > >> > >> > > > > Using a pom from some else's project as your parent is unusual. I'd > > remove that and leave the dependencies on the struts jars. You may > > want to establish a 'struts.version' property so you don't have to > > repeat it. > > > > Having this as a parent means you're following all the way up to the > > ASF top-level parent pom, which is unlikely to be what you really want > > -- your project web site will list all the Struts developers, for one > > thing. :) > > > > > > > - > 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: Excluding build .jars from .war
I was building off of the struts2-portlet-2.0.x.war example. So I guess that means I need to travel up the pom parents tree and merge all the dependencies and other elements into my own pom? I will try and attempt not to break anything. Thank you. Do you happen to know why all those .jars are being included in my .war? Fred Wendy Smoak wrote: On 7/30/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote: org.apache.struts struts2-apps 2.0.9 Using a pom from some else's project as your parent is unusual. I'd remove that and leave the dependencies on the struts jars. You may want to establish a 'struts.version' property so you don't have to repeat it. Having this as a parent means you're following all the way up to the ASF top-level parent pom, which is unlikely to be what you really want -- your project web site will list all the Struts developers, for one thing. :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven coherent dependencies build
What "didn't work"? What happened vs what did you expect to happen? We need more details to be able to help. And what is a "coherent dependency"? Wayne On 7/30/07, Dmitry <[EMAIL PROTECTED]> wrote: > > we changed configuration using Coherent Dependency - Maven conf but it did > not work. Any advices about how to use coherent dependecies? > > > > 4.0.0 > > com.mycompany.app > > AdvertiseFreeModule > > jar > > 1.1-SNAPSHOT > > > > > > junit > > junit > > 3.8.1 > > test > > > > > > > > thanks, > > DT > > www.ejinz.com Search Shopping Engine > > > > > - > 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 standard directory layout question
On 7/30/07, Dmitry <[EMAIL PROTECTED]> wrote: > This means that by adopting Maven's standard conventions, we can package > resources within JARs, simply by placing those resources in a standard > directory structure. But when we put resources in standard directory we get > nothing -what we did wrong? You really haven't given us enough info to help. Where did you put them, exactly? Did you add any additional resources config to your pom? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding build .jars from .war
On 7/30/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote: > > org.apache.struts > struts2-apps > 2.0.9 > Using a pom from some else's project as your parent is unusual. I'd remove that and leave the dependencies on the struts jars. You may want to establish a 'struts.version' property so you don't have to repeat it. Having this as a parent means you're following all the way up to the ASF top-level parent pom, which is unlikely to be what you really want -- your project web site will list all the Struts developers, for one thing. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven standard directory layout question
We are suing common case which requires no changes to the POM project - the packaging of resources into a JAR file. Maven again uses for this task the standard directory layout. This means that by adopting Maven's standard conventions, we can package resources within JARs, simply by placing those resources in a standard directory structure. But when we put resources in standard directory we get nothing -what we did wrong? thanks, DT www.ejinz.com EjinZ Search Shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding build .jars from .war
Here it is:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.apache.struts
struts2-apps
2.0.9
com.mycompany.portlet
myportlet
war
Portlet
http://www.mycompany.com
1
Frederick N. Brier
fbrier at multideck.com
EDT5
src/main/resources
true
src/main/java
true
**/*.properties
**/*.xml
package
maven-idea-plugin
2.1
true
true
true
false
Generated XMLBeans Source
target/xmlbeans-source
org.codehaus.mojo
xmlbeans-maven-plugin
xmlbeans
xmlbeans
xbean
2.2.0
true
src/main/xsd
target/xmlbeans-source
portlet-api
portlet-api
1.0
provided
org.apache.struts
struts2-spring-plugin
${pom.version}
org.apache.struts
struts2-core
${pom.version}
velocity
velocity
1.4
velocity-tools
velocity-tools
1.1
commons-digester
commons-digester
1.8
commons-dbcp
commons-dbcp
1.1
javax.servlet
servlet-api
2.4
provided
commons-lang
commons-lang
2.0
xmlbeans
xbean
2.2.0
com.googlecode.tabletags
tabletags
1.0.1-SNAPSHOT
javax.persistence
persistence-api
1.0
2007
org.hibernate.dialect.MySQLInnoDBDialect
mysql
mysql-connector-java
5.0.5
com.mysql.jdbc.Driver
root
Wayne Fay wrote:
Show us your pom. You must be doing something wrong -- I've never seen
any of those jars including in any wars I've ever constructed.
Wayne
On 7/30/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote:
I am relatively new to Maven and my project is including a number of
.jars which I believe are only needed by Maven at build time into my
.war. How do I stop them from being included?
maven-artifact-20.0.jar
maven-artifact-manager-2.0.jar
maven-model-2.0.jar
maven-plugin-api-2.0.jar
maven-profile-2.0.jar
maven-project-2.0.jar
maven-repository-metadata-2.0.jar
plexus-container-default-1.0-alpha-8.jar
plexus-utils-1.0.0.jar
plexus-utils-1.0.4.jar
wagon-provider-api-1.0-alpha-5.jar
It is also including the junit-2.8.1.jar and two copies of the
xbean-*.jar, specifically xbean-2.0.0.jar and xbean-2.2.0.jar. Also
note that two versions of the plexus-utils-*.jar are included above.
Now I am using the xmlbeans-maven-plugin mojo plugin. Could this be
causing some of the jar issues? Thank you.
Fred
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven coherent dependencies build
we changed configuration using Coherent Dependency - Maven conf but it did not work. Any advices about how to use coherent dependecies? 4.0.0 com.mycompany.app AdvertiseFreeModule jar 1.1-SNAPSHOT junit junit 3.8.1 test thanks, DT www.ejinz.com Search Shopping Engine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven local process artifacts
First off, I think you probably should avoid doing this. I think you will run into troubles down the line if/when changes in Spring cause your older projects to break, so suddenly you can't use the latest Spring in all your projects, etc. Having said that, you could create a single Super Parent POM (with the Spring framework as a dependency) and tell all your other projects and modules to utilize that pom as their parent. Wayne On 7/30/07, Dmitry <[EMAIL PROTECTED]> wrote: > By default Maven attempts to locate a dependecies artifact using the > follloing process: 1-st generate path to the artifact in local repositiory. > etc > How we can change Maven configuration that instead having to add the Spring > framework jar to every project - change just from one common configuration? > > Thanks, > DT, > www.ejinz.com > Search Engine News Shop > > > - > 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: How to use ${project.build.directory}?
On 7/20/07, Tawfik, Sameh E <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm using the following code:
>
>
> connector
> connector 1_0
> system
>
> ${Build_base}/ma-jdm-tck/lib/connector_1_0.jar
>
>
> This code is working fine, but it requires everyone to define the
> "Build_base" system variable, so is there is another way, where I can
> reference the folder where this jar is located without using a system
> variable?
I would have the developers use 'mvn install:install-file' to add the
jar to their local repository, and then you can declare it as a normal
dependency.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to use ${project.build.directory}?
When we run maven JUnits - and ensure that testing is successful. - run mvn test but its through out exception and looks like it did not run properly JUnit in project. How the first step to check where is error in configuration / setting sof maven and fix this error thanks, DT www.ejinz.com Search Shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding build .jars from .war
Show us your pom. You must be doing something wrong -- I've never seen any of those jars including in any wars I've ever constructed. Wayne On 7/30/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote: > I am relatively new to Maven and my project is including a number of > .jars which I believe are only needed by Maven at build time into my > .war. How do I stop them from being included? > > maven-artifact-20.0.jar > maven-artifact-manager-2.0.jar > maven-model-2.0.jar > maven-plugin-api-2.0.jar > maven-profile-2.0.jar > maven-project-2.0.jar > maven-repository-metadata-2.0.jar > plexus-container-default-1.0-alpha-8.jar > plexus-utils-1.0.0.jar > plexus-utils-1.0.4.jar > wagon-provider-api-1.0-alpha-5.jar > > It is also including the junit-2.8.1.jar and two copies of the > xbean-*.jar, specifically xbean-2.0.0.jar and xbean-2.2.0.jar. Also > note that two versions of the plexus-utils-*.jar are included above. > Now I am using the xmlbeans-maven-plugin mojo plugin. Could this be > causing some of the jar issues? Thank you. > > Fred > > - > 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]
Maven local process artifacts
By default Maven attempts to locate a dependecies artifact using the follloing process: 1-st generate path to the artifact in local repositiory. etc How we can change Maven configuration that instead having to add the Spring framework jar to every project - change just from one common configuration? Thanks, DT, www.ejinz.com Search Engine News Shop - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
I have also noticed the same behavior with the project url, the sit url and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> In the parent POM I have the following:
> [...]
>
> http://localhost/repos/repo/${groupId}/${artifactId}/trunk
>
>
>
>
>
>
> ${scmConnection}
> ${scmConnection}
>
> [...]
>
> The child POM has nothing expect mandatory elements and the reference to
> the parent POM. Both the child and the parent are snapshots. The parent POM
> has been deployed to the remote repository.
>
> When I run mvn help:effective-pom on the child project, I get:
> [...]
>
> http://localhost/repos/repo/com.opicasso/Child/trunk/Child
>
>
> http://localhost/repos/repo/com.opicasso/Child/trunk/Child
>
>
> [..]
>
> I would have expected:
> [...]
>
> http://localhost/repos/repo/com.opicasso/Child/trunk
>
>
> http://localhost/repos/repo/com.opicasso/Child/trunk
>
> [..]
>
> Why does maven happen the child artifactId to the connections? Does maven
> merge the parent scm connections with the children ones ? But in the current
> case the child has no scm connections defined in its pom.
>
> How to get rid of this extra artifactId?
>
> Thanks
>
> Oscar
>
>
>
Re: Eclipse 3.3 plugin based war build with Maven?
Assuming the servletbridge jar is in your repo and dependency list, try
something like this:
maven-dependency-plugin
process-resources
copy-dependencies
servletbridge
${project.build.directory}/${
project.build.finalName}/WEB-INF/eclipse
maven-war-plugin
WEB-INF/lib/servletbridge*.jar
You can find the details of these plugins, but above is one way to do it:
http://maven.apache.org/plugins/
Please, let me know how it works out!
Eric
On 7/30/07, George Stragand <[EMAIL PROTECTED]> wrote:
>
> With Eclipse 3.3, the temptation to use the osgi plugin framework is huge,
> and we would really like to utilize the osgi framework within our web app.
> Differences exist between the classic layout of a web app and where the
> osgi
> bundles exist (the Eclipse plugin jars existing under WEB-INF/eclipse
> instead of WEB-INF/lib, etc.). The only jar in the WEB-INF/lib is
> servletbridge.jar (OK, that makes me twitch that there isn't a version on
> that jar out of Eclipse; guess I am too used to the logical approach of
> Maven).
>
> Main question is how to create the same war from an automated Maven build
> as
> Eclipse does. The PDE Maven plugin doesn't appear to do this. Anyone
> else
> attempting to create an osgi war from Eclipse and Maven at the same time?
>
> I'd rather not leave the "build" in Eclipse (IDE's doing builds also makes
> me twitch!). The ability for the build machine to have unexpected
> versions
> of plugins is a risk, and we would really like the ability to recreate a
> build from source control and Maven as we do with other war deliverables.
>
> Thanks.
>
--
Eric Redmond
http://blog.propellors.net
Excluding build .jars from .war
I am relatively new to Maven and my project is including a number of .jars which I believe are only needed by Maven at build time into my .war. How do I stop them from being included? maven-artifact-20.0.jar maven-artifact-manager-2.0.jar maven-model-2.0.jar maven-plugin-api-2.0.jar maven-profile-2.0.jar maven-project-2.0.jar maven-repository-metadata-2.0.jar plexus-container-default-1.0-alpha-8.jar plexus-utils-1.0.0.jar plexus-utils-1.0.4.jar wagon-provider-api-1.0-alpha-5.jar It is also including the junit-2.8.1.jar and two copies of the xbean-*.jar, specifically xbean-2.0.0.jar and xbean-2.2.0.jar. Also note that two versions of the plexus-utils-*.jar are included above. Now I am using the xmlbeans-maven-plugin mojo plugin. Could this be causing some of the jar issues? Thank you. Fred - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Parent POM, properties and scm problem
Hi,
In the parent POM I have the following:
[...]
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
${scmConnection}
${scmConnection}
[...]
The child POM has nothing expect mandatory elements and the reference to the
parent POM. Both the child and the parent are snapshots. The parent POM has
been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
[..]
I would have expected:
[...]
http://localhost/repos/repo/com.opicasso/Child/trunk
http://localhost/repos/repo/com.opicasso/Child/trunk
[..]
Why does maven happen the child artifactId to the connections? Does maven
merge the parent scm connections with the children ones ? But in the current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
Re: Passing System Variables to Maven
I would stick to -D options. "env" variables are going away in Maven soon.
Eric
On 7/30/07, Graham Leggett <[EMAIL PROTECTED]> wrote:
>
> David Williams wrote:
>
> > How do you pass system environment variables like system date or system
> time
> > to maven. I'm running maven on a windows machine.
>
> You can access environment variables by using maven variables of the
> form ${env.VARIABLE}.
>
> So ${env.PATH} would be your path, for example.
>
> As far as I am aware, will only work on JDK v1.5 and above, as it wasn't
> possible to read environment variables in Java before then.
>
> Regards,
> Graham
> --
>
>
--
Eric Redmond
http://blog.propellors.net
Julia Vilke/Moscow/Canon/FI is out of the office.
I will be out of the office starting 16.05.2007 and will not return until 08.01.2008. I'm on maternity leave till January 2008. In case of Canon Consumable business, please contact Mikhail Popov, in case of Paper business - Maria Bondarenko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse 3.3 plugin based war build with Maven?
With Eclipse 3.3, the temptation to use the osgi plugin framework is huge, and we would really like to utilize the osgi framework within our web app. Differences exist between the classic layout of a web app and where the osgi bundles exist (the Eclipse plugin jars existing under WEB-INF/eclipse instead of WEB-INF/lib, etc.). The only jar in the WEB-INF/lib is servletbridge.jar (OK, that makes me twitch that there isn't a version on that jar out of Eclipse; guess I am too used to the logical approach of Maven). Main question is how to create the same war from an automated Maven build as Eclipse does. The PDE Maven plugin doesn't appear to do this. Anyone else attempting to create an osgi war from Eclipse and Maven at the same time? I'd rather not leave the "build" in Eclipse (IDE's doing builds also makes me twitch!). The ability for the build machine to have unexpected versions of plugins is a risk, and we would really like the ability to recreate a build from source control and Maven as we do with other war deliverables. Thanks.
RE: [maven-dependency-plugin] v 2.0-alpha-4 : include/exclude scopes
The dependency plugin uses the same code as core to determine the scope. Specifically, it calls a method (going by memory here) isScope(scope). The test scope includes everything, so if used to exclude, you would get nothing. You can use the copy goal to name specific dependencies if you need to, or you could use other combinations of include/exclude groups,artifacts,types etc to get what you need. I think it's important that the dependency plugin continue to use the same code to determine scope so that it matches the classpath provided for a given scope. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 10:10 AM To: users@maven.apache.org Subject: [maven-dependency-plugin] v 2.0-alpha-4 : include/exclude scopes Hello ! I'd like to talk about the behaviour of the dependency:copy-depedencies plugin, when I add some include/exclude scopes parameters. I noticed that these parameters' types were just Strings, which means you can set only one include scope and one exclude scope in the config tag. After a few tests, I could establish a link between the parameter value and the dependencies selected. The array below describes these links : --- param value -> dependencies scope --- compile -> compile + provided runtime -> compile + runtime provided -> provided test -> compile + provided + runtime + test --- Fortunately, I need to get only compile and runtime, which corresponds to a "runtime" value in the includeScope parameter. But imagine you need "compile + provided + runtime", which is an equivalent of "all but test". How can you configure the plugin to do that ? If I set excludeScope to "test", the build fails because I've excluded * all * the dependencies. If I set 2 include scopes (compile and runtime), it only takes the last one, and doesn't work much better... Perhaps you could change the mojo's parameters to give the user more possibilities ? Thanks ! Isabelle Guimiot - 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: Assembly plugin includes directories
Andrew hi, and thank you for the swift response. As I have listed I have set false so I don't think this is the problem. The A:B and A:C artifacts doesn't have the B.jar and C.jar directories in their archives. Any other ideas? 2007/7/31, Andrew Boyer <[EMAIL PROTECTED]>: > > Check your assembly descriptor for A:B and A:C, make sure you've set the > includeBaseDirectory property for them to false. > > Andrew > > > -Original Message- > > From: Petar Tahchiev [mailto:[EMAIL PROTECTED] > > Sent: Monday, July 30, 2007 5:43 PM > > To: Maven Users List > > Subject: Assembly plugin includes directories > > > > Hi guys, > > > > I have the following situation: I have configured the assembl plugin > so > > that > > it produces an archive that contains > > the content of another two archives. My assembly descriptor is this > one: > > > > > > jar > > > > false > > > > > > / > > false > > > > A:B:jar > > A:C:jar > > > > > > true > > test > > > > > > > > > > The problem is that the new archive that is created contains the > original > > folders, like: > > Archive > > | > > | B.jar-/contentsOfB > > | C.jar-/contentsOfC > > > > So basicaly in the example above I don't want the B.jar and > > C.jardirectories in my archive. > > > > Have anyone seen this problem? > > > > Thank you. > > > > > > -- > > Regards, Petar! > > Karlovo, Bulgaria. > > > > Bulgarian medics in Libya are innocent! > > http://www.nestesami.bg/main/index.php > > > > Public PGP Key at: > > > https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C311061 > 1 > > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Petar! Karlovo, Bulgaria. Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: Jdev project error using Maven to build .jpr
Hi Wayne, I'm not familiar to JDev and Maven integration too, so then I'm using both separetly. Well, I fixed my issue putting my project folder in the same volume as maven folder. I was completly unwarned of it. I think this is some kind of problem in the engine of Jdev plugin. However I do not have my project in way with maven, i'm using maven to generate my .jpr to easy the way how I import libs to my project. It takes to much time ,in a project that has a .war file with 70Mb, to import all the .jar that I need. Then maven dooes it for me... I'm sorry of not being so advanced... thanks anyway.. Scott -- View this message in context: http://www.nabble.com/Jdev-project-error-using-Maven-to-build-.jpr-tf4159624s177.html#a11884999 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: Assembly plugin includes directories
Check your assembly descriptor for A:B and A:C, make sure you've set the includeBaseDirectory property for them to false. Andrew > -Original Message- > From: Petar Tahchiev [mailto:[EMAIL PROTECTED] > Sent: Monday, July 30, 2007 5:43 PM > To: Maven Users List > Subject: Assembly plugin includes directories > > Hi guys, > > I have the following situation: I have configured the assembl plugin so > that > it produces an archive that contains > the content of another two archives. My assembly descriptor is this one: > > > jar > > false > > > / > false > > A:B:jar > A:C:jar > > > true > test > > > > > The problem is that the new archive that is created contains the original > folders, like: > Archive > | > | B.jar-/contentsOfB > | C.jar-/contentsOfC > > So basicaly in the example above I don't want the B.jar and > C.jardirectories in my archive. > > Have anyone seen this problem? > > Thank you. > > > -- > Regards, Petar! > Karlovo, Bulgaria. > > Bulgarian medics in Libya are innocent! > http://www.nestesami.bg/main/index.php > > Public PGP Key at: > https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C311061 1 > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Assembly plugin includes directories
Hi guys, I have the following situation: I have configured the assembl plugin so that it produces an archive that contains the content of another two archives. My assembly descriptor is this one: jar false / false A:B:jar A:C:jar true test The problem is that the new archive that is created contains the original folders, like: Archive | | B.jar-/contentsOfB | C.jar-/contentsOfC So basicaly in the example above I don't want the B.jar and C.jardirectories in my archive. Have anyone seen this problem? Thank you. -- Regards, Petar! Karlovo, Bulgaria. Bulgarian medics in Libya are innocent! http://www.nestesami.bg/main/index.php Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: Running a single JUnit test
Thanks Ben that was it. I got screwed up because the docs say the following: "The value for the test parameter is the name of the test class (without the extension)." so I assumed the extension was Test and so I kept leaving it off. Thanks, Mondays. On 7/30/07, ben short <[EMAIL PROTECTED]> wrote: > Your missing test from the end of your class name, see [1] > > mvn -Dtest=com.xxx..InternalDAOtest test > > > [1] > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > > > > On 7/30/07, Scott Purcell <[EMAIL PROTECTED]> wrote: > > Hello, > > Maven 2.0.7 > > > > I have a project that encompases different projects, so I have a > > parent pom with children. I created a JUnit test called > > InternalDAOTest.java. In my pom, I have the following: > > > > > > > > org.apache.maven.plugins > > maven-surefire-plugin > > > > > > **/*Test.java > > > > > > > > > > So I would think I should be able to run my file like so: > > mvn -Dtest=com.xxx..InternalDAO > > but it does not run, it scans for projects and reports back > > BUILD FAILURE. You must specify at least one goal. > > > > So then I try > > mvn -Dtest=com.xxx..InternalDAO test and it runs a bunch of > > other testSuites etc but not my one test. > > > > How should it run a single JUnit test with 16 tests? Anyone? > > Kind of stuck here. > > > > Thanks, > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running a single JUnit test
*mvn -Dtest=com.xxx..InternalDAOTest test On 7/30/07, ben short <[EMAIL PROTECTED]> wrote: > Your missing test from the end of your class name, see [1] > > mvn -Dtest=com.xxx..InternalDAOtest test > > > [1] > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > > > > On 7/30/07, Scott Purcell <[EMAIL PROTECTED]> wrote: > > Hello, > > Maven 2.0.7 > > > > I have a project that encompases different projects, so I have a > > parent pom with children. I created a JUnit test called > > InternalDAOTest.java. In my pom, I have the following: > > > > > > > > org.apache.maven.plugins > > maven-surefire-plugin > > > > > > **/*Test.java > > > > > > > > > > So I would think I should be able to run my file like so: > > mvn -Dtest=com.xxx..InternalDAO > > but it does not run, it scans for projects and reports back > > BUILD FAILURE. You must specify at least one goal. > > > > So then I try > > mvn -Dtest=com.xxx..InternalDAO test and it runs a bunch of > > other testSuites etc but not my one test. > > > > How should it run a single JUnit test with 16 tests? Anyone? > > Kind of stuck here. > > > > Thanks, > > > > - > > 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: Running a single JUnit test
Your missing test from the end of your class name, see [1] mvn -Dtest=com.xxx..InternalDAOtest test [1] http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html On 7/30/07, Scott Purcell <[EMAIL PROTECTED]> wrote: > Hello, > Maven 2.0.7 > > I have a project that encompases different projects, so I have a > parent pom with children. I created a JUnit test called > InternalDAOTest.java. In my pom, I have the following: > > > > org.apache.maven.plugins > maven-surefire-plugin > > > **/*Test.java > > > > > So I would think I should be able to run my file like so: > mvn -Dtest=com.xxx..InternalDAO > but it does not run, it scans for projects and reports back > BUILD FAILURE. You must specify at least one goal. > > So then I try > mvn -Dtest=com.xxx..InternalDAO test and it runs a bunch of > other testSuites etc but not my one test. > > How should it run a single JUnit test with 16 tests? Anyone? > Kind of stuck here. > > Thanks, > > - > 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]
Running a single JUnit test
Hello, Maven 2.0.7 I have a project that encompases different projects, so I have a parent pom with children. I created a JUnit test called InternalDAOTest.java. In my pom, I have the following: org.apache.maven.plugins maven-surefire-plugin **/*Test.java So I would think I should be able to run my file like so: mvn -Dtest=com.xxx..InternalDAO but it does not run, it scans for projects and reports back BUILD FAILURE. You must specify at least one goal. So then I try mvn -Dtest=com.xxx..InternalDAO test and it runs a bunch of other testSuites etc but not my one test. How should it run a single JUnit test with 16 tests? Anyone? Kind of stuck here. Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exit codes on Windows
Seems I posted a bit prematurely. It works in a standard command prompt just not in powershell. It seems it's not picking up the environmental variable MAVEN_TERMINATE_CMD. If you define it again in your powershell script in the env namespace ($ENV:MAVEN_TERMINATE_CMD="on") it starts working. - Original message - From: "Martin Gilday" <[EMAIL PROTECTED]> To: users@maven.apache.org Date: Mon, 30 Jul 2007 21:15:15 +0100 Subject: Exit codes on Windows I am currently writing a Windows Powershell script which calls the maven bat file to trigger a build as part of its functionality. It seems that regardless of sucess or failure an exit code of 0 is returned. I have found this closed JIRA issue (http://jira.codehaus.org/browse/MNG-2127) which offers some suggestions, including setting MAVEN_TERMINATE_CMD=on. I have tried these but have not had any luck. Is this an ongoing issue with Maven on Windows? Should this be working with 2.0.7. Thanks for any advice. Martin. - 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]
Exit codes on Windows
I am currently writing a Windows Powershell script which calls the maven bat file to trigger a build as part of its functionality. It seems that regardless of sucess or failure an exit code of 0 is returned. I have found this closed JIRA issue (http://jira.codehaus.org/browse/MNG-2127) which offers some suggestions, including setting MAVEN_TERMINATE_CMD=on. I have tried these but have not had any luck. Is this an ongoing issue with Maven on Windows? Should this be working with 2.0.7. Thanks for any advice. Martin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with ear packaging and existing jboss-app.xml
src/main/resources is not the correct (default) directory to use for EARs resources. As stated on [1], the correct directory is src/main/application. Try that and report back! [1] http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html Wayne On 7/30/07, Todd Nine <[EMAIL PROTECTED]> wrote: > Hi all, > I'm running into a pretty big issue with the ear plugin. I'm creating an > ear for JBoss with an existing jboss-app.xml file. I need to have special > classloading directives, and they're not available in the file that's > generated by the plugin. Whenever the plugin runs, it never packages my > file src/main/resources/META-INF/jboss-app.xml. Any idea on how to get > around this? I'm using a different version of Hibernate than JBoss 4.02 and > my app blows up unless I deploy with scoped classloaders. > > Thanks, > Todd > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can i build a specific version without changing the pom.xml?
In that case, you will need to change pom.xml everytime right? As long as you're using snapshots: No. You only have to change your pom.xml if you decide that the code is stable enough to be called a new release. Or, we can have profile defined in profiles.xml or settings.xml to avoid pom.xml changes? I absolutely recommend to not omit the project version number in your pom (don't know if that ever work, btw). I'd be afraid to be unable to verify that some piece of code I have in my IDE really belongs to a certain deployed release that is in use somewhere... HTH Thorsten PGP.sig Description: Signierter Teil der Nachricht
Problems with ear packaging and existing jboss-app.xml
Hi all, I'm running into a pretty big issue with the ear plugin. I'm creating an ear for JBoss with an existing jboss-app.xml file. I need to have special classloading directives, and they're not available in the file that's generated by the plugin. Whenever the plugin runs, it never packages my file src/main/resources/META-INF/jboss-app.xml. Any idea on how to get around this? I'm using a different version of Hibernate than JBoss 4.02 and my app blows up unless I deploy with scoped classloaders. Thanks, Todd
Re: Deployment of runtime configurations? / Deployment of assemblies?
I don't believe you should put environment specific, such as TEST-db connection params vs PROD-db connection params in the binary. Put that information in a file which can be edited outside your artifact (jar, war, ear). As long as this config file is in your classpath, then you can access it from your java application. You want to be able to TEST a binary and move that exact binary to production without ANY modification. On 7/30/07, Georg Öttl <[EMAIL PROTECTED]> wrote: > > Hi > > I have a different configurations (spring, Text files and so on). I really > tried hard to figure out how I should handle those runtime configurations > with maven. Has anybody done such a thing so far? > > My problem is: If I put the configuration into the src/main/resources > directory and therefore directly into the distributed jar it will be hard > (but possible) to override the default configuration. If I put the > resources > outside the resources directory I couldn't figure out how deploy it. > Depended projects won't get the configuration if I can't deploy it to a > remote repo :-(. > > The remote-resources plug-in looks somehow like what I need - but the > documentation is not that good. Couldn't really use it by now. If I'm > right > this plug-in should allow to deploy "remote-resources". > > I'd find it cool to be able to specify > > "Project-X.jar depends on Project-A-resources-1.0.SNAPSHOT.jar" > "Project-X1.jar depends on Project-B-resources-1.0.SNAPSHOT.jar" > "Project-X2.jar depends on Project-A-resources-1.0.SNAPSHOT.jar" > > Is this a feature I have to wait for or did I overlook a really simple > solution? > > > PS: Does anybody know how to deploy an assembly with the deploy plug-in? > Or > is this a thing "not to do". > > Best regards, > Georg > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Passing System Variables to Maven
David Williams wrote:
How do you pass system environment variables like system date or system time
to maven. I'm running maven on a windows machine.
You can access environment variables by using maven variables of the
form ${env.VARIABLE}.
So ${env.PATH} would be your path, for example.
As far as I am aware, will only work on JDK v1.5 and above, as it wasn't
possible to read environment variables in Java before then.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signature
Re : Passing System Variables to Maven
Hi DavidThose are all already available in the Java environment running Maven. If the property your are looking for is not in the system default, you pass them in the command line using the -D option.Hope it helps.Eric.- Message d'origine -De: David Williams <[EMAIL PROTECTED]>Date: Lundi, Juillet 30, 2007 1:04 pmObjet: Passing System Variables to MavenÀ: Maven Users List > Hi Everyone,> > How do you pass system environment variables like system date or > system time> to maven. I'm running maven on a windows machine.> > Thanks,> > David>
Re: deploying to two repositories and two snapshots repositories in m2
Correct me if I'm wrong Maarten, but you'd still need to call deploy twice, once for -P repo1 and again for -P repo2. The original question was asking if it was possible to do 2 deploys with a single call of mvn deploy -- my general response would be no. But I've never needed to do this, so there's a chance its possible and I've just never done it. Wayne On 7/30/07, maarten roosendaal <[EMAIL PROTECTED]> wrote: > Use profiles to define 2 profiles, each having it's own repository. You can > then say mvn deploy:deploy -P repo1 > > - Original Message > From: Piotr Oktaba <[EMAIL PROTECTED]> > To: Maven Users List > Sent: Monday, July 30, 2007 8:31:30 AM > Subject: deploying to two repositories and two snapshots repositories in m2 > > Hi. > > I have to deploy artifacts to two repositories (if snapshots, to two > snapshots repositories). I cannot define two repositories (and two > snapshots repositories) in section distributionManagement. Is any way to > do it without double calling goal deploy:deploy with argument > altDeploymentRepisitory? > > Thanks in advance, > Peter > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > Ready > for the edge of your seat? > Check out tonight's top picks on Yahoo! TV. > http://tv.yahoo.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]
Re: [maven-dependency-plugin] v 2.0-alpha-4 : include/exclude scopes
I don't believe "all but test" as a possible scope makes much sense when you're thinking about valid use/business cases. Can you think of such a real-life situation? Also, it might be helpful to review the Maven Dependency Scope section on this page: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html Wayne On 7/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello ! > > I'd like to talk about the behaviour of the dependency:copy-depedencies > plugin, when I add some include/exclude scopes parameters. > I noticed that these parameters' types were just Strings, which means you > can set only one include scope and one exclude scope in the config tag. > > After a few tests, I could establish a link between the parameter value and > the dependencies selected. The array below describes these links : > > --- > param value -> dependencies scope > --- > compile -> compile + provided > runtime -> compile + runtime > provided -> provided > test -> compile + provided + runtime + test > --- > > Fortunately, I need to get only compile and runtime, which corresponds to a > "runtime" value in the includeScope parameter. > > But imagine you need "compile + provided + runtime", which is an equivalent > of "all but test". > How can you configure the plugin to do that ? > If I set excludeScope to "test", the build fails because I've excluded * > all * the dependencies. > If I set 2 include scopes (compile and runtime), it only takes the last > one, and doesn't work much better... > > Perhaps you could change the mojo's parameters to give the user more > possibilities ? > > Thanks ! > > Isabelle Guimiot > > > - > 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]
Passing System Variables to Maven
Hi Everyone, How do you pass system environment variables like system date or system time to maven. I'm running maven on a windows machine. Thanks, David
Re: latest non-snapshot dependency
On 31/07/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > As far as I understand it, this works fine so long as you are only > connecting to non-snapshot repos. > > As Rodrigo mentioned, he has snapshot repos configured in his pom, and > as such the RELEASE tag will not work as desired. ah, ok - good to know > > Wayne > > On 7/30/07, Stuart McCulloch <[EMAIL PROTECTED]> wrote: > > On 30/07/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > To answer your original question, it is not currently possible to tell > > > Maven to use the latest non-snapshot of a dependency. Something along > > > these lines has been under discussion on the Dev list in the last > > > month, though. > > > > that's weird, we've been happily using RELEASE to track the latest > > version of our helper plugins for a while and it appears to pick the > > right version each time (luck? chance?) > > > > > > > > Your best bet is to simply specify the exact version you want, or > > > remove the snapshot repos from your pom. > > > > > > Wayne > > > > > > On 7/30/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > > > Hi Stuart ! > > > > > > > > Thx for your response... > > > > > > > > I've tried to use your suggestion but it does not work for every > > > > artifacts. For example: > > > > when I use: > > > > > > > > > > > >org.apache.maven.plugins > > > >maven-release-plugin > > > >RELEASE > > > > > > > > ... > > > > > > > > > > > > > > > > Maven tries to download version 2.0-beta-5-SNAPSHOT > > > > "org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-5-20070426.100207-13" > > > > > > > > I don't know if it's relevant but I'm using a Maven 2 enterprise > > > > repository (artifactory). > > > > > > > > Regards, > > > > Rodrigo. > > > > > > > > > > > > Stuart McCulloch wrote: > > > > > On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > > > > > > > > >> Hi... > > > > >> > > > > >> In my poms I have some plugins configured without the version in > > > > >> order > > > > >> to use the latest one, but in my settings.xml file I need to have > > > > >> some > > > > >> snapshot-repositories. > > > > >> So in the builds maven will use the latest version available witch > > > > >> is a > > > > >> snapshot version, and that is not my intension. > > > > >> Is there any way to specify maven to use the latest non-snapshot > > > > >> version > > > > >> of a dependency? > > > > >> > > > > > > > > > > have you tried using a meta-version, such as: > > > > > > > > > > RELEASE > > > > > > > > > > that shouldn't match against any snapshots. > > > > > > > > > > > > > > >> Thx in advance... > > > > >> Rodrigo. > > > > >> > > > > >> - > > > > >> 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] > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Cheers, Stuart > > > > - > > 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] > > -- Cheers, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] release process - maven-release-plugin usage
On 30/07/07, Tom Huybrechts <[EMAIL PROTECTED]> wrote: > You can use the release plugin on a multi-module project, and it will > it walk the module graph for you. That's what I doing currently. Nearly all of our SVN modules are Maven2 multi-module projects; there's an unfortunate overloading of the term. My apologies for not being more precise. > You can also run release:prepare > with -B (batch mode) so that all defaults will be used automatically. Thanks, I can't see in the documentation[1], and missed it in the source. That covers automating the prepare step. Any suggestions on the branch / remove snapshot / increment to development versions and merge aspects? Cheers, James [1] http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html > > On 7/30/07, James Abley <[EMAIL PROTECTED]> wrote: > > Hi, > > > > We currently have the following process for our releases: > > > > Walk the DAG of our modules in a breadth-first traversal [1] and for > > each module being released: > > > > 1) Create a branch in Subversion. > > 2) Check out the branch > > 3) Update the POMs so that no SNAPSHOT dependencies are stil in the > > POMs and commit these updates in the branch. > > 4) mvn release:prepare -D... > > 5) mvn release:perform > > 6) Update the POMs to reference the new SNAPSHOT dependency versions > > and commit these updates in the branch. > > 7) Merge the updated POMs back into main trunk. > > > > We have some Python scripts to do steps 1-3 and 6,7. > > > > Unfortunately step 4 doesn't seem to be possible to fully script due > > to prompting for release numbers and next development numbers. We > > could do more work with the reading and writing of child stdin / > > stdout, but I think it would be preferable for the release plugin to > > support being invoked in an enabling manner which assumes that we know > > what we are doing and just to use the defaults. > > > > I also noticed that the maven-release-plugin has had some changes in > > the last few months, with a new release:branch goal. And from a brief > > look at the plugin code, the logic is in place to do steps 3 and 6 > > within the plugin, but it doesn't appear to be exposed. > > > > I would like to be able to move to an all Maven solution. > > > > 1. Does this look possible, given the process that we have? And is it > > possible using the current release plugin, if invoked correctly, or > > would it require changes to expose the desired functionality? Please > > provide any examples of how you think this should work. > > 2. If I'm correct and the prepare step can't be automated, does anyone > > think this is a reasonable idea? If so, I'll raise a JIRA issue and > > look at whether I can provide a patch. > > > > Regards, > > > > James > > > > [1] http://en.wikipedia.org/wiki/Breadth-first_search > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: latest non-snapshot dependency
As far as I understand it, this works fine so long as you are only connecting to non-snapshot repos. As Rodrigo mentioned, he has snapshot repos configured in his pom, and as such the RELEASE tag will not work as desired. Wayne On 7/30/07, Stuart McCulloch <[EMAIL PROTECTED]> wrote: > On 30/07/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > To answer your original question, it is not currently possible to tell > > Maven to use the latest non-snapshot of a dependency. Something along > > these lines has been under discussion on the Dev list in the last > > month, though. > > that's weird, we've been happily using RELEASE to track the latest > version of our helper plugins for a while and it appears to pick the > right version each time (luck? chance?) > > > > > Your best bet is to simply specify the exact version you want, or > > remove the snapshot repos from your pom. > > > > Wayne > > > > On 7/30/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > > Hi Stuart ! > > > > > > Thx for your response... > > > > > > I've tried to use your suggestion but it does not work for every > > > artifacts. For example: > > > when I use: > > > > > > > > >org.apache.maven.plugins > > >maven-release-plugin > > >RELEASE > > > > > > ... > > > > > > > > > > > > Maven tries to download version 2.0-beta-5-SNAPSHOT > > > "org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-5-20070426.100207-13" > > > > > > I don't know if it's relevant but I'm using a Maven 2 enterprise > > > repository (artifactory). > > > > > > Regards, > > > Rodrigo. > > > > > > > > > Stuart McCulloch wrote: > > > > On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > > > > > > >> Hi... > > > >> > > > >> In my poms I have some plugins configured without the version in order > > > >> to use the latest one, but in my settings.xml file I need to have some > > > >> snapshot-repositories. > > > >> So in the builds maven will use the latest version available witch is a > > > >> snapshot version, and that is not my intension. > > > >> Is there any way to specify maven to use the latest non-snapshot > > > >> version > > > >> of a dependency? > > > >> > > > > > > > > have you tried using a meta-version, such as: > > > > > > > > RELEASE > > > > > > > > that shouldn't match against any snapshots. > > > > > > > > > > > >> Thx in advance... > > > >> Rodrigo. > > > >> > > > >> - > > > >> 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] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Cheers, Stuart > > - > 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]
[maven-dependency-plugin] v 2.0-alpha-4 : include/exclude scopes
Hello ! I'd like to talk about the behaviour of the dependency:copy-depedencies plugin, when I add some include/exclude scopes parameters. I noticed that these parameters' types were just Strings, which means you can set only one include scope and one exclude scope in the config tag. After a few tests, I could establish a link between the parameter value and the dependencies selected. The array below describes these links : --- param value -> dependencies scope --- compile -> compile + provided runtime -> compile + runtime provided -> provided test -> compile + provided + runtime + test --- Fortunately, I need to get only compile and runtime, which corresponds to a "runtime" value in the includeScope parameter. But imagine you need "compile + provided + runtime", which is an equivalent of "all but test". How can you configure the plugin to do that ? If I set excludeScope to "test", the build fails because I've excluded * all * the dependencies. If I set 2 include scopes (compile and runtime), it only takes the last one, and doesn't work much better... Perhaps you could change the mojo's parameters to give the user more possibilities ? Thanks ! Isabelle Guimiot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: latest non-snapshot dependency
On 30/07/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > To answer your original question, it is not currently possible to tell > Maven to use the latest non-snapshot of a dependency. Something along > these lines has been under discussion on the Dev list in the last > month, though. that's weird, we've been happily using RELEASE to track the latest version of our helper plugins for a while and it appears to pick the right version each time (luck? chance?) > > Your best bet is to simply specify the exact version you want, or > remove the snapshot repos from your pom. > > Wayne > > On 7/30/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > Hi Stuart ! > > > > Thx for your response... > > > > I've tried to use your suggestion but it does not work for every > > artifacts. For example: > > when I use: > > > > > >org.apache.maven.plugins > >maven-release-plugin > >RELEASE > > > > ... > > > > > > > > Maven tries to download version 2.0-beta-5-SNAPSHOT > > "org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-5-20070426.100207-13" > > > > I don't know if it's relevant but I'm using a Maven 2 enterprise > > repository (artifactory). > > > > Regards, > > Rodrigo. > > > > > > Stuart McCulloch wrote: > > > On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > > > > >> Hi... > > >> > > >> In my poms I have some plugins configured without the version in order > > >> to use the latest one, but in my settings.xml file I need to have some > > >> snapshot-repositories. > > >> So in the builds maven will use the latest version available witch is a > > >> snapshot version, and that is not my intension. > > >> Is there any way to specify maven to use the latest non-snapshot version > > >> of a dependency? > > >> > > > > > > have you tried using a meta-version, such as: > > > > > > RELEASE > > > > > > that shouldn't match against any snapshots. > > > > > > > > >> Thx in advance... > > >> Rodrigo. > > >> > > >> - > > >> 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] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] release process - maven-release-plugin usage
You can use the release plugin on a multi-module project, and it will it walk the module graph for you. You can also run release:prepare with -B (batch mode) so that all defaults will be used automatically. On 7/30/07, James Abley <[EMAIL PROTECTED]> wrote: > Hi, > > We currently have the following process for our releases: > > Walk the DAG of our modules in a breadth-first traversal [1] and for > each module being released: > > 1) Create a branch in Subversion. > 2) Check out the branch > 3) Update the POMs so that no SNAPSHOT dependencies are stil in the > POMs and commit these updates in the branch. > 4) mvn release:prepare -D... > 5) mvn release:perform > 6) Update the POMs to reference the new SNAPSHOT dependency versions > and commit these updates in the branch. > 7) Merge the updated POMs back into main trunk. > > We have some Python scripts to do steps 1-3 and 6,7. > > Unfortunately step 4 doesn't seem to be possible to fully script due > to prompting for release numbers and next development numbers. We > could do more work with the reading and writing of child stdin / > stdout, but I think it would be preferable for the release plugin to > support being invoked in an enabling manner which assumes that we know > what we are doing and just to use the defaults. > > I also noticed that the maven-release-plugin has had some changes in > the last few months, with a new release:branch goal. And from a brief > look at the plugin code, the logic is in place to do steps 3 and 6 > within the plugin, but it doesn't appear to be exposed. > > I would like to be able to move to an all Maven solution. > > 1. Does this look possible, given the process that we have? And is it > possible using the current release plugin, if invoked correctly, or > would it require changes to expose the desired functionality? Please > provide any examples of how you think this should work. > 2. If I'm correct and the prepare step can't be automated, does anyone > think this is a reasonable idea? If so, I'll raise a JIRA issue and > look at whether I can provide a patch. > > Regards, > > James > > [1] http://en.wikipedia.org/wiki/Breadth-first_search > > - > 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: merge 2 web applications into 1
Maven2 supports this already. It is called WAR overlaying. http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html Wayne On 7/30/07, Eugeny N Dzhurinsky <[EMAIL PROTECTED]> wrote: > Hello there! > > I have some (strange?) requirement: > > there is a web application, let's say projectA. This application contains some > classes, required libraries, images, javascript/jsp files etc. > > now I have application (projectB), which depends on projectA. To resolve such > dependency, I need to have projectA be "merged" into the directory structure > of WEB application of projectB, and then pack projectB as a WAR file. > > How can I do this? I assume I need to prepare a package of application > projectA in some way (as a WAR file probably?) and then unpack this war file > into target directory for projectB, and then create WAR package? > > Another thing is how can I compile classes for projectA, package them as JAR > file, and then include into WAR file (WEB-INF/lib)? > > -- > Eugene N Dzhurinsky > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: latest non-snapshot dependency
To answer your original question, it is not currently possible to tell Maven to use the latest non-snapshot of a dependency. Something along these lines has been under discussion on the Dev list in the last month, though. Your best bet is to simply specify the exact version you want, or remove the snapshot repos from your pom. Wayne On 7/30/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > Hi Stuart ! > > Thx for your response... > > I've tried to use your suggestion but it does not work for every > artifacts. For example: > when I use: > > >org.apache.maven.plugins >maven-release-plugin >RELEASE > > ... > > > > Maven tries to download version 2.0-beta-5-SNAPSHOT > "org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-5-20070426.100207-13" > > I don't know if it's relevant but I'm using a Maven 2 enterprise > repository (artifactory). > > Regards, > Rodrigo. > > > Stuart McCulloch wrote: > > On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > > >> Hi... > >> > >> In my poms I have some plugins configured without the version in order > >> to use the latest one, but in my settings.xml file I need to have some > >> snapshot-repositories. > >> So in the builds maven will use the latest version available witch is a > >> snapshot version, and that is not my intension. > >> Is there any way to specify maven to use the latest non-snapshot version > >> of a dependency? > >> > > > > have you tried using a meta-version, such as: > > > > RELEASE > > > > that shouldn't match against any snapshots. > > > > > >> Thx in advance... > >> Rodrigo. > >> > >> - > >> 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: latest non-snapshot dependency
On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > Hi Stuart ! > > Thx for your response... > > I've tried to use your suggestion but it does not work for every > artifacts. For example: > when I use: > > > org.apache.maven.plugins > maven-release-plugin > RELEASE > >... > > > > Maven tries to download version 2.0-beta-5-SNAPSHOT > "org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-5-20070426.100207-13" > > I don't know if it's relevant but I'm using a Maven 2 enterprise > repository (artifactory). could be another pom is using the plugin without a version to find out you can use "mvn -X ..." to trace where the snapshot dependency comes from during the build. FYI, the best way to pass plugin versions to child projects is by using a ... section, as explained at: http://maven.apache.org/pom.html#plugin_management lastly, check the maven-metadata.xml file on the server just in case the release stanza has the wrong version > Regards, > Rodrigo. > > > Stuart McCulloch wrote: > > On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > > > >> Hi... > >> > >> In my poms I have some plugins configured without the version in order > >> to use the latest one, but in my settings.xml file I need to have some > >> snapshot-repositories. > >> So in the builds maven will use the latest version available witch is a > >> snapshot version, and that is not my intension. > >> Is there any way to specify maven to use the latest non-snapshot version > >> of a dependency? > >> > > > > have you tried using a meta-version, such as: > > > > RELEASE > > > > that shouldn't match against any snapshots. > > > > > >> Thx in advance... > >> Rodrigo. > >> > >> - > >> 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] > > -- Cheers, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
merge 2 web applications into 1
Hello there! I have some (strange?) requirement: there is a web application, let's say projectA. This application contains some classes, required libraries, images, javascript/jsp files etc. now I have application (projectB), which depends on projectA. To resolve such dependency, I need to have projectA be "merged" into the directory structure of WEB application of projectB, and then pack projectB as a WAR file. How can I do this? I assume I need to prepare a package of application projectA in some way (as a WAR file probably?) and then unpack this war file into target directory for projectB, and then create WAR package? Another thing is how can I compile classes for projectA, package them as JAR file, and then include into WAR file (WEB-INF/lib)? -- Eugene N Dzhurinsky pgptJovo9MuOV.pgp Description: PGP signature
Re: latest non-snapshot dependency
Hi Stuart ! Thx for your response... I've tried to use your suggestion but it does not work for every artifacts. For example: when I use: org.apache.maven.plugins maven-release-plugin RELEASE ... Maven tries to download version 2.0-beta-5-SNAPSHOT "org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-5-20070426.100207-13" I don't know if it's relevant but I'm using a Maven 2 enterprise repository (artifactory). Regards, Rodrigo. Stuart McCulloch wrote: On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: Hi... In my poms I have some plugins configured without the version in order to use the latest one, but in my settings.xml file I need to have some snapshot-repositories. So in the builds maven will use the latest version available witch is a snapshot version, and that is not my intension. Is there any way to specify maven to use the latest non-snapshot version of a dependency? have you tried using a meta-version, such as: RELEASE that shouldn't match against any snapshots. Thx in advance... Rodrigo. - 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: latest non-snapshot dependency
On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote: > Hi... > > In my poms I have some plugins configured without the version in order > to use the latest one, but in my settings.xml file I need to have some > snapshot-repositories. > So in the builds maven will use the latest version available witch is a > snapshot version, and that is not my intension. > Is there any way to specify maven to use the latest non-snapshot version > of a dependency? have you tried using a meta-version, such as: RELEASE that shouldn't match against any snapshots. > > > Thx in advance... > Rodrigo. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
latest non-snapshot dependency
Hi... In my poms I have some plugins configured without the version in order to use the latest one, but in my settings.xml file I need to have some snapshot-repositories. So in the builds maven will use the latest version available witch is a snapshot version, and that is not my intension. Is there any way to specify maven to use the latest non-snapshot version of a dependency? Thx in advance... Rodrigo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deployment of runtime configurations? / Deployment of assemblies?
Hi I have a different configurations (spring, Text files and so on). I really tried hard to figure out how I should handle those runtime configurations with maven. Has anybody done such a thing so far? My problem is: If I put the configuration into the src/main/resources directory and therefore directly into the distributed jar it will be hard (but possible) to override the default configuration. If I put the resources outside the resources directory I couldn't figure out how deploy it. Depended projects won't get the configuration if I can't deploy it to a remote repo :-(. The remote-resources plug-in looks somehow like what I need - but the documentation is not that good. Couldn't really use it by now. If I'm right this plug-in should allow to deploy "remote-resources". I'd find it cool to be able to specify "Project-X.jar depends on Project-A-resources-1.0.SNAPSHOT.jar" "Project-X1.jar depends on Project-B-resources-1.0.SNAPSHOT.jar" "Project-X2.jar depends on Project-A-resources-1.0.SNAPSHOT.jar" Is this a feature I have to wait for or did I overlook a really simple solution? PS: Does anybody know how to deploy an assembly with the deploy plug-in? Or is this a thing "not to do". Best regards, Georg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JAXP DocumentBuilderFactory not found by maven-antrun-plugin initiated Ant
(I have not subscribed to users alias, so please copy a reply directly
to my email)
Hi,
I get /javax.xml.parsers.FactoryConfigurationError: Provider
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl could
not be instantiated: java.lang.NullPointerException/ when I call an Ant
script from maven using maven-antrun-plugin. I have tried using fork =
true as well as false, but same result. Maven version is 2.0.7 and JDK
version is 1.5.0_06. I don't understand why Ant is not finding this
class, which is actually present in jre/lib/rt.jar. I get the following
output while running with -X option:
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
[DEBUG] getProperty(ns=null, name=ant.executor.class, user=false)
[DEBUG] getProperty(ns=null, name=ant.file, user=false)
test:
[echo] Generating Java classes from SDO Types
5 INFO [main] openjpa.MetaData - Parsing XML Schema "META-INF/po.xsd"
[java] javax.xml.parsers.FactoryConfigurationError: Provider
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl could
not be instantiated: java.lang.NullPointerException
[java] at
javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
[java] at
org.eclipse.xsd.util.DefaultJAXPConfiguration.createDocumentBuilder(DefaultJAXPConfiguration.java:94)
[java] at
org.eclipse.xsd.util.XSDResourceImpl.getDocument(XSDResourceImpl.java:334)
[java] at
org.eclipse.xsd.util.XSDResourceImpl.getDocument(XSDResourceImpl.java:372)
[java] at
org.eclipse.xsd.util.XSDResourceImpl.doLoad(XSDResourceImpl.java:680)
[java] at
org.eclipse.xsd.util.XSDResourceImpl.load(XSDResourceImpl.java:617)
[java] at
org.apache.tuscany.sdo.helper.XSDHelperImpl.define(XSDHelperImpl.java:197)
[java] at
org.apache.tuscany.sdo.helper.XSDHelperImpl.define(XSDHelperImpl.java:188)
[java] at
org.apache.openjpa.sdo.SDO2POJOGenerator.findTypes(SDO2POJOGenerator.java:126)
[java] at
org.apache.openjpa.sdo.SDO2POJOGenerator.run(SDO2POJOGenerator.java:246)
[java] at
org.apache.openjpa.sdo.SDO2POJOGenerator.main(SDO2POJOGenerator.java:282)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:202)
[java] at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:134)
[java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
[java] at
org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
[java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[java] at org.apache.tools.ant.Task.perform(Task.java:364)
[java] at org.apache.tools.ant.Target.execute(Target.java:341)
[java] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[java] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[java] at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[java] at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[java] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[java] at org.apache.tools.ant.Task.perform(Task.java:364)
[java] at org.apache.tools.ant.Target.execute(Target.java:341)
[java] at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
[java] at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
[java] at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
[java] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
[java] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
[java] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
[java] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
[java] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
[java] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
[java] at
org.apache.maven.DefaultMaven.doExe
Re: deploying to two repositories and two snapshots repositories in m2
Use profiles to define 2 profiles, each having it's own repository. You can then say mvn deploy:deploy -P repo1 - Original Message From: Piotr Oktaba <[EMAIL PROTECTED]> To: Maven Users List Sent: Monday, July 30, 2007 8:31:30 AM Subject: deploying to two repositories and two snapshots repositories in m2 Hi. I have to deploy artifacts to two repositories (if snapshots, to two snapshots repositories). I cannot define two repositories (and two snapshots repositories) in section distributionManagement. Is any way to do it without double calling goal deploy:deploy with argument altDeploymentRepisitory? Thanks in advance, Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deployment of runtime configurations? Deployment of assemblies?
Hi I have a different configurations (spring, Text files and so on). I really tried hard to figure out how I should handle those runtime configurations with maven. Has anybody done such a thing so far? My problem is: If I put the configuration into the src/main/resources directory and therefore directly into the distributed jar it will be hard (but possible) to override the default configuration. If I put the resources outside the resources directory I couldn't figure out how deploy it. Depended projects won't get the configuration if I can't deploy it to a remote repo :-(. The remote-resources plug-in looks somehow like what I need - but the documentation is not that good. Couldn't really use it by now. If I'm right this plug-in should allow to deploy "remote-resources". I'd find it cool to be able to specify "Project-X.jar depends on Project-A-resources-1.0.SNAPSHOT.jar" "Project-X1.jar depends on Project-B-resources-1.0.SNAPSHOT.jar" "Project-X2.jar depends on Project-A-resources-1.0.SNAPSHOT.jar" Is this a feature I have to wait for or did I overlook a really simple solution? PS: Does anybody know how to deploy an assembly with the deploy plug-in? Or is this a thing "not to do". Best regards, Georg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] release process - maven-release-plugin usage
Hi, We currently have the following process for our releases: Walk the DAG of our modules in a breadth-first traversal [1] and for each module being released: 1) Create a branch in Subversion. 2) Check out the branch 3) Update the POMs so that no SNAPSHOT dependencies are stil in the POMs and commit these updates in the branch. 4) mvn release:prepare -D... 5) mvn release:perform 6) Update the POMs to reference the new SNAPSHOT dependency versions and commit these updates in the branch. 7) Merge the updated POMs back into main trunk. We have some Python scripts to do steps 1-3 and 6,7. Unfortunately step 4 doesn't seem to be possible to fully script due to prompting for release numbers and next development numbers. We could do more work with the reading and writing of child stdin / stdout, but I think it would be preferable for the release plugin to support being invoked in an enabling manner which assumes that we know what we are doing and just to use the defaults. I also noticed that the maven-release-plugin has had some changes in the last few months, with a new release:branch goal. And from a brief look at the plugin code, the logic is in place to do steps 3 and 6 within the plugin, but it doesn't appear to be exposed. I would like to be able to move to an all Maven solution. 1. Does this look possible, given the process that we have? And is it possible using the current release plugin, if invoked correctly, or would it require changes to expose the desired functionality? Please provide any examples of how you think this should work. 2. If I'm correct and the prepare step can't be automated, does anyone think this is a reasonable idea? If so, I'll raise a JIRA issue and look at whether I can provide a patch. Regards, James [1] http://en.wikipedia.org/wiki/Breadth-first_search - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hibernate and 2.0.7
Using those versions together with no problems. - Original message - From: "jallen" <[EMAIL PROTECTED]> To: users@maven.apache.org Date: Sun, 29 Jul 2007 13:00:27 -0700 (PDT) Subject: Hibernate and 2.0.7 Has anyone else experienced issues with 2.0.7 and hibernate 3.2.4.ga? It's not my project code but I've upgraded the common build system and some unit tests for a hibernate project now fail? Searched the web and not come up with a lot. -- View this message in context: http://www.nabble.com/Hibernate-and-2.0.7-tf4166646s177.html#a11854518 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]
Re: Looking for IZPack mater in the repo
I'd recommend contacting the izpack mailing list with this issue. Maybe someone already has a decent pom of an up to date version, which can be pushed to the central maven repo. PS: there is also an issue of an izpack maven2 plugin in mojo.codehaus.org's JIRA. Also for maven1 I wrote one at maven-plugins.sf.net which could be ported (though not by me). With kind regards, Geoffrey De Smet Aron Sogor schreef: The izpack poms has some issues: 1. the causes mvn 2.0.6 to call the pom invalid. 2. 3.8.0 is old 3. The biggest pain is none of the packages contains the classes from the izpack-events.jar so if you write plugins there is no way to compile them Whoever is the boss I am happy to help! Aron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
