Junking paths when unpacking or overlaying
I have a project where I get a dependency from a vendor in an archive, and I need to copy a jar file from a subfolder within the archive to WEB-INF/lib. When I try to unpack it with dependency:unpack or use the overlay element in war:war, it retains the folder in the jar name. Is there a way to strip the folder name so that the jar file goes into WEB-INF/lib instead of WEB-INF/lib/folder? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Do I need to write a plugin for this?
However, if I want my pom to have packaging of cba, it's my impression that I need to write a plugin. It's the only artifact I want to upload to Nexus. On 03/01/15 20:42, Benson Margulies wrote: > I don't understand your question at all. In Maven, you can just use the > build-helper-maven-plugin to attach any file to the project, causing it to > upload. So, you can certainly use antrun to run the ant build, and the > helper to attach the result as an artifact. > > On Sun, Mar 1, 2015 at 4:18 PM, Bruce Albrecht > wrote: > >> I am working on a project that creates OSGI bundles with an extension of >> .cba and today uses ant to invoke a workbench to build the .cba file. I >> want to upload the .cba file to my Nexus repository. My initial take on >> this is that if IBM didn't use its own extension for this, I would be >> able to just use the antrun plugin. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Do I need to write a plugin for this?
I am working on a project that creates OSGI bundles with an extension of .cba and today uses ant to invoke a workbench to build the .cba file. I want to upload the .cba file to my Nexus repository. My initial take on this is that if IBM didn't use its own extension for this, I would be able to just use the antrun plugin. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Apache Maven Toolchains Plugin 1.1 Released
Can the toolchain.xml file contain Maven properties including references
to system environment variables using ${env.VARIABLE}? My company is
using several versions of Websphere and I was wondering if I could have
something like:
jdk
1.5
ibm
${env.WAS_HOME}/java
jdk
1.6
IBM
${env.WAS_HOME}
jdk
1.7
IBM
${env.WAS_HOME}
Also, does it fail if the toolchain plugin is specified but the
toolchain.xml file is missing?
I think that the toolchain plugin documentation should specify that the
toolchain.xml file belongs in the$user.home/.m2 directory, as it only
mentions this in the guide to using toolchains.
On 11/14/14 18:55, Hervé Boutemy wrote:
> The Maven team is pleased to announce the release of the Apache Maven
> Toolchains Plugin, version 1.1
>
> The Toolchains Plugins allows to share configuration across plugins. For
> example to make sure the plugins like compiler, surefire, javadoc, webstart
> etc. all use the same JDK for execution.
>
> http://maven.apache.org/plugins/maven-toolchains-plugin/
>
> You should specify the version in your project's plugin configuration:
>
>
> org.apache.maven.plugins
> maven-toolchains-plugin
> 1.1
>
>
>
> Release Notes - Apache Maven Toolchains Plugin - Version 1.1
>
> Bug
> * [MTOOLCHAINS-6] Cannot create custom toolchain type
>
> Improvement
> * [MTOOLCHAINS-11] Double check toolchain type to protect against core bug
> MNG-5716
> * [MTOOLCHAINS-10] Improve plugin output
> * [MTOOLCHAINS-1] Document how to create new toolchains
>
> Task
> * [MTOOLCHAINS-9] Upgrade to Maven 2.2.1 compatiblity
> * [MTOOLCHAINS-8] improve code and javadoc
> * [MTOOLCHAINS-7] add an IT to check that the plugin works as expected
> * [MTOOLCHAINS-4] use maven-plugin-tools' java 5 annotations
>
>
> Enjoy,
>
> -The Maven team
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Overriding artifact to be installed/deployed
One of my teams is trying to build a bundled application that first builds a jar file using the jar plugin and then uses maven-exec plugin to run something that bundles the jar file into a specialized osgi bundle. When we run the mvn install or deploy, it will deploy the jar file created by the jar plugin. Is there some way to override the artifact location so that it will upload the bundled jar? Currently this is all done in a single project, and I'm beginning to wonder if the way to go is to change it to a multi-module project, with one module to create the jar file, and a second module to create the bundled jar, and use build-helper:attach-artifact to attach the bundled jar. They don't need the unbundled jar to be uploaded to the repository. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Creating a bundled jar file with an external bundler
Some of my developers is trying to create a OSGI bundled jar file by creating a jar project which the jar plugin and then calling the external bundler in the packaging phase. They change the output directory in the jar configuration to be a subfolder used by the external bundler. When it performs an install or deploy, it uploads the jar created by the jar plugin. Is there some way for me to tell the install and deploy plugins to use the jar file created by the external bundler? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to build war with dependencies in a different location
I have an application with OSGI bundles, and the Felix loader is looking for the jars to be in WEB-INF/bundles/3 instead of the usual WEB-INF/lib. Is there a configuration for the war plugin, or a different plugin I can use to place these dependencies in a different location? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven versioning
On 5/24/2012 7:39 AM, DK wrote: Hi, New to Maven and have a couple of questions around versioning. Should all projects within a multi-module project have the same version? Should all projects related to each other keep the same version number? Any best practices on changing version numbers? Perhaps this it not considered best practice, but we've got a lot of web applications which are multi-module, usually a few jars/ejbs + 1-2 wars + ear, and I've been telling my users to let the child projects inherit the parent project's groupId and version (i.e., the child pom specifies the parent's groupId, artifactId and version, but only its artifactId). A release still needs to update all the poms to update the children's parent version, though. IMHO, if you have a large multi-module project with a large number subprojects that almost never change and are not build dependent on subprojects which change frequently, it makes sense to take them out of the multi-module project and only build them when necessary. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using maven to modify a vendor supplied war/ear
Our company has several projects where we have received a war or ear from a vendor, and we need to insert jars or configuration files into the vendor artifact before deploying them. Is there an existing maven plugin that can handle this? If there is such a plugin, can it manage inserting/updating files in embedded jars/wars also? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven and ClearCase UCM
Unfortunately, the SCM plugin documentation says that it doesn't work with ClearCase dynamic views, which we use almost exclusively. Since the release plugin relies on the SCM plugin, we can't use it. We normally have developers create new baselines through a script, so we're considering modifying the script to update the POMs with a version based on the ClearCase baseline created by the script. One catch is that if we automatically update POMs after creating baseline they're not available for rebasing until we create a second baseline. Mark Struberg wrote: do you guys use mvn release:prepare and mvn release:perform? This should increment the versions automatically! Please also read through the section covering in the 'definitive maven guide'. LieGrue, strub --- On Thu, 9/10/09, Andrew Close wrote: From: Andrew Close Subject: Re: Maven and ClearCase UCM To: "Maven Users List" Date: Thursday, September 10, 2009, 4:29 PM On Thu, Sep 10, 2009 at 8:59 AM, Bruce Albrecht wrote: Is anyone using Maven with ClearCase UCM with developers using children streams with dynamic views? If so, how do you manage bumping the POM versions? Do you rely on the developers doing it manually, or use an automatic process? If we automate it, it looks like we potentially need to strip the -SNAPSHOT in the POMs' version before creating a baseline, create a baseline, update the POMs to new -SNAPSHOT versions, and then create a second baseline so that the developers can rebase against it. Is there a better way that we're overlooking? Thanks! hi Bruce, we recently converted our SCM from MS VSS to CC UCM and our build system from a very poor ANT implementation (not that ANT is poor, our implementation was) to Maven. we're still struggling with growing pains/conversion pains and have yet to automate versioning. i'm hoping that others speak up cause we'd like some ideas as well. :) our setup/process is pretty poor at the moment mainly due to the amount of baggage our systems carry. we currently rely on the developers to set their versions to SNAPSHOT during development. everything on the dev stream is SNAPSHOT. when we move to Integration testing we create a new stream that everyone delivers to and the versions are set to hard versions. everything is built and tested and if ok delivered to the Prod stream by SCM. i can give you more details, but i'm hoping others step up with better solutions cause i'll be the first to tell you ours isn't the way to go. :) -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven and ClearCase UCM
Is anyone using Maven with ClearCase UCM with developers using children streams with dynamic views? If so, how do you manage bumping the POM versions? Do you rely on the developers doing it manually, or use an automatic process? If we automate it, it looks like we potentially need to strip the -SNAPSHOT in the POMs' version before creating a baseline, create a baseline, update the POMs to new -SNAPSHOT versions, and then create a second baseline so that the developers can rebase against it. Is there a better way that we're overlooking? Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
