Hi all,
I'm running into a bit of an odd issue here with using the release plugin. I
have a multi-module project I'm trying to release that has two submodules. One
defines a parent subproject with a header like so:
project ...
...
groupIdmy.group/groupId
You could always put it in a separate Maven project and declare a dependency
to that artifact for the exec plugin. But then it might be better to create
a Maven plugin instead...
If it's something simple, why not just write a Groovy script and use the
gmaven-plugin to execute it? You'll then keep
Have you tried specifying ${project.version}?
/Anders
On Fri, Apr 1, 2011 at 03:25, Brinker, Don-NONEMP dbrin...@collegeboard.org
wrote:
Hi all,
I'm running into a bit of an odd issue here with using the release plugin.
I have a multi-module project I'm trying to release that has two
Our project uses Eviware's maven-soapui-plugin. The plugin depends on
xmlbeans:xmlpublic:2.4.0, which is hosted in the eviware repository, but
seems to be corrupt. I think this jar is also available from apache, but has
a different definition - xmlbeans:xmlbeans-xmlpublic:2.4.0 so I would like
to
I wonder if my mail was sent on the mailing list so I send it again, sorry if
you already receive this mail.
Hi all,
I'd like to make my own artifact/archetype and I'm facing an issue when trying
to install it, precisely when it tries to make the jar file.
Here is the output :
I've had similar issues with the soopui plugin, it (and their repo) really
needs to be shaped up I've even had a meeting with Eviware about this,
but very little has happened.
What you can do, and that we've done, is to create a patched version of the
plugin where you correct/change the pom.
Thanks Anders, that was my guess too. For the benefit of others it's not
just the eviware repo that's broken but also the l2fprod one they reference
too. If maven attempts to download log4j-1.2.14 from it you get redirected
to the l2fprod home page, meaning the log4j-1.2.14.pom is just an HTML web
Yes, it's just a mess. To alter a famous quote here on the list:
Friends don't let friends use the Eviware repo.
It's a shame as soapUI is such an excellent tool.
/Anders
On Fri, Apr 1, 2011 at 11:53, Stephen Cresswell em...@stephen-cresswell.net
wrote:
Thanks Anders, that was my guess too.
So how about this:
I have Hudson CI build run the release to automatically update the version each
time. Would that work?
-Original Message-
From: Manfred Moser [mailto:manf...@mosabuam.com]
Sent: Thursday, March 31, 2011 11:02 PM
To: Maven Users List
Cc: Bryan Keech
Subject: Re: One
AFAIK it's not possible.
/Anders
On Thu, Mar 31, 2011 at 15:35, Stefan Schulze algr...@gmx.de wrote:
Hi,
I'd like to write a custom packaging to add some javascript-tooling. As
part of this, it should be packaged with maven-assembly-plugin.
I wrote the components.xml and lifecycle.xml
Hi,
I have a build/resources stanza that is inherited. In a sub-pom, I'd like
to override it to be empty. Simply specifyingresources / does not work.
What's the best way to accomplish this?
may i misunderstand your explanation but what exactly is inherited the
definition in the pom ?
If
Actually, ${project.version} just gets passed along in the archetype files. To
my mind this is a good thing, since I need that token in the generated POM, but
it still leaves me with the question of how to designate the version of the
archetype.
Thanks
- Don
-Original Message-
From:
Yes, that's the idea.
Bryan Keech bryan.keech.h...@statefarm.com wrote:
So how about this: I have Hudson CI build run the release to automatically
update the version each time. Would that work? -Original Message- From:
Manfred Moser [mailto:manf...@mosabuam.com] Sent: Thursday, March
Hi,
I'm using Grails 1.2.1 and just recently downloaded Maven 2.2. I have found
the maven-grails plugin and figured out how to mavenize an existing grails
project. What are the advantages of doing this? It seems like some of the
advantages of using Maven (dependency management,
Well, if your grails app is just one part of a larger project, you get your
grails build integrated as part of the larger maven lifecycle.
On Fri, Apr 1, 2011 at 7:23 AM, laredotornado-3 laredotorn...@gmail.comwrote:
Hi,
I'm using Grails 1.2.1 and just recently downloaded Maven 2.2. I have
I'm using Grails 1.2.1 and just recently downloaded Maven 2.2. I have found
the maven-grails plugin and figured out how to mavenize an existing grails
project. What are the advantages of doing this? It seems like some of the
advantages of using Maven (dependency management, standardization)
Can some one confirm that my understanding of lifecycles, phases, and
goals is correct?
Maven has three lifecycles: clean, default (build), and site. These are
defined by Maven core and can not be changed by plugins.
Each lifecycle is made up of a fixed, ordered list, of phases. The
phases in
Can some one confirm that my understanding of lifecycles, phases, and
goals is correct?
Maven has three lifecycles: clean, default (build), and site. These are
defined by Maven core and can not be changed by plugins.
the stock maven does..
Each lifecycle is made up of a fixed, ordered
Only addition I'd suggest is that new lifecycles and packaging types can be
defined in plugins.
Justin
On Apr 1, 2011, at 6:37 PM, Chad La Joie laj...@itumi.biz wrote:
Can some one confirm that my understanding of lifecycles, phases, and
goals is correct?
Maven has three lifecycles:
I lloked at the sources: it seems you're including non-existent source
directory files.
Please open a Jira issue [1] with a sample project as attachement, and I'll fix
the plugin to give a better error message on such case.
Note in your pom.xml that specifying a version for archetype plugin and
20 matches
Mail list logo
