Re: Using the new maven assembly goals

Hi, Thanks for the reply. -- Rui On Mon, Mar 14, 2011 at 10:01 AM, Marc Rohlfs wrote: > Hi Rui, > > I guess You were formally using the 'assembly:assembly' (or > 'assembly:directory') goal, right? Those goals where "not inherited by > default in multi-project builds" [1], but they "forced Maven

Re: Using the new maven assembly goals

Hi, Thanks for the quick response. My comments are in-line. Have a nice weekend too ;) -- Rui On Fri, Mar 11, 2011 at 6:29 PM, Marc Rohlfs wrote: > Hi Rui, > > normally false should work for You. It is a Maven > core parameter and it doesn't depend on the plugin goal You are using. > > I can o

Using the new maven assembly goals

Hi all, I've been using the maven-assembly-plugin for long time and I noticed that some goals changed and are now deprecated. I've a multi-module project and I only want to run the assembly plugin on the parent. But if I run assembly:single (according to the plugin's page is the only one that is

Re: Executing ant run after a plugin

typically used inside other parts of the > pom. > What are you trying to do? > > BTW, if you run this goal from CLI, why don't you just add the next goal to > be run on the same command line? > Le 24 févr. 2011 16:23, "Rui Vilão" a écrit : > > Hi, > > &

Executing ant run after a plugin

Hi, I'm using the buildnumber plugin and I want to execute a given antrun goal ONLY when I explicitly call that plugin from the console. So, imagine that I execute mvn buildnumber:create and in the pom I do something like: maven-antrun-plugin WHAT DO I PUT HERE

Re: Disabling lifecycle with assembly plugin

goal instead > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 16 Feb 2011 12:40, "Rui Vilão" wrote: > > Hi all, > >

Disabling lifecycle with assembly plugin

Hi all, I'm having a problem with maven assembly plugin. It happens that I have a child pom with relative paths and when I hit assembly:assembly the environment becomes corrupted (that doesn't happen if I hit mvn install, package whatever in both project's pom directory or in the root of the major

Re: License collection

of a build > (including searching in parent poms) with the ability to assign > custom license information + generate a report with selective dependency > scopes. It is part of Artifactory Pro. > > http://wiki.jfrog.org/confluence/display/RTF/License+Control > > On Sat, Jan 22, 2

Re: License collection

nstead? The dependencies report of the mpir plugin has had a > license section for quite some time, I use it all the time. See e.g. > the dependency report of the mpir plugin itself: > > http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies.html > . > > Kal

Re: Some questions about the assembly plugin

package > > single > > > > release.xml > > > > > > > HTH, > Justin > > > Rui Vilão wrote: > >> Hi there, >> >> I'm trying to do the following: >>

Some questions about the assembly plugin

Does anyone had this problem? Thanks in advance, Rui Vilão

Final release of a project

Hi, My company is developing a product and we're using Maven as project management tool. My question is: how can I achieve a final release of the project? More detailed below. What I am looking for is to have at the end a structure similar to the one JBoss uses: *bin startup shutdown lib dep