Hi,
I am writing a custom maven plugin and I want to do some integration
testing. I use maven-invoker-plugin run the tests, and my configuration for
it looks
pretty much like this.
maven-invoker-plugin
true
src/it
${project.build.directory}/it
${project.build.directory}/local-repo
src/it/setti
> My guess is that while dots are in general perhaps ill-advised,
> 'maven.' is what really causes the problem here. In my experience,
> dots in pom props are as common as dirt, and it's very much news to me
> that they are a bad idea. There are a lot of poms at Apache that will
> need to be edited
> Well, at this point all I'm mainly after is the ability to copy an
> artifact from snapshot to release repo (removing -SNAPSHOT from the
> version) without having to go through the rebuild process. If that
As Vincent already stated, this is harder than it initially appears
for most builds as th
My guess is that while dots are in general perhaps ill-advised,
'maven.' is what really causes the problem here. In my experience,
dots in pom props are as common as dirt, and it's very much news to me
that they are a bad idea. There are a lot of poms at Apache that will
need to be edited if all do
On Wed, Oct 6, 2010 at 4:19 PM, Thiessen, Todd (Todd)
wrote:
> What you are asking for definitely is not recommended. The release plugin
> already has a "staging" feature but it is not the recommended way to do.
Good to know, thanks.
> Putting a "staging" build into the release repo is not reco
On 2010-10-06 00:13, Andrew Robinson wrote:
> I am trying to get our build system moved over from maven 2.0.8 to
> 2.2.1, but we have been having problems with the site plugin. While
> converting over, I am supporting a profile that changes the plugin
> version. Here is the setup:
>
>
>
> ..
On 5 October 2010 09:48, Hilco Wijbenga wrote:
> On 5 October 2010 04:09, Benjamin Bentmann wrote:
>> Hilco Wijbenga wrote:
>>>
>>>
>>> central
>>> http://central
>>>
>>> true
>>>
>>>
>>> true
>>>
What you are asking for definitely is not recommended. The release plugin
already has a "staging" feature but it is not the recommended way to do.
Putting a "staging" build into the release repo is not recommended from my
perspective either. That isn't what a snapshot is for. They are meant to
In Maven/Nexus terminology, you deploy a release candidate to a staging area
(#2) in your example. This artifact (or group of artifacts) is then made
available to a group of people for validation (it can be automated or
manual). Once it's validated it is promoted and copied to the release
repositor
On Wed, Oct 6, 2010 at 3:50 PM, Phillip Hellewell wrote:
>
> No, there are basically there types of builds I want to do. Most
> people don't have a stage between snapshot and release, so I'm
> guessing that is why I am not getting any clear direction about the
> best way to do this.
> 1. A snapsh
On Wed, Oct 6, 2010 at 2:04 PM, Ron Wheeler
wrote:
> On 06/10/2010 3:42 PM, Phillip Hellewell wrote:
>>
>> If I deploy non-snapshot builds to the snapshot repository first
>
> How. I do not think that this can be done.
I asked earlier if non-snapshot builds can be deployed to a snapshot
reposito
On Wed, Oct 6, 2010 at 3:34 PM, Thiessen, Todd (Todd)
wrote:
> Err mean to say "Write a plugin for Nexus". Bah sorry. Hate it when I make
> typos like that. Reply too fast. ;-)
The file structure of a repository seems to make it look like copying
artifacts is almost trivial.
Phillip
--
Err mean to say "Write a plugin for Nexus". Bah sorry. Hate it when I make
typos like that. Reply too fast. ;-)
> -Original Message-
> From: Thiessen, Todd (Todd) [mailto:tthies...@avaya.com]
> Sent: Wednesday, October 06, 2010 5:33 PM
> To: Maven Users List
> Subject: RE: Can't specify d
Why a plugin for the open source version of nexus. I'd bet it isn't quite as
straight forward as you might think ;-)
> -Original Message-
> From: Phillip Hellewell [mailto:ssh...@gmail.com]
> Sent: Wednesday, October 06, 2010 5:31 PM
> To: Maven Users List
> Subject: Re: Can't specify dis
On Wed, Oct 6, 2010 at 2:00 PM, Thiessen, Todd (Todd)
wrote:
> Phil. I think you just need to try it and read the Nexus docs. Sounds like
> you are really making things complicated for yourself.
Yeah, you are probably right.
Phillip
On Wed, Oct 6, 2010 at 1:57 PM, Anders Hammar wrote:
> Philip, have a look at the staging feature of Nexus Pro. That's what you
> want. I believe I already said this...
Thanks. I wonder if there are any free alternatives that provide this
functionality. You'd think you wouldn't have to pay for
anyone know how to reach cargo admin ?
requests to both
u...@cargo.codehaus.org
and d...@cargo.codehaus.org
do not respond
thanks,
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich
> into Nexus anyway. The build process builds two jars one with and one
> without dependencies. I uploaded the myjar without dependencies into Nexus.
> That is the one that is included in project B's web-inf/lib (but not its
> dependencies) which I have verified. Sorry for the confusion.
So, di
On 06/10/2010 3:42 PM, Phillip Hellewell wrote:
On Wed, Oct 6, 2010 at 1:37 PM, Ron Wheeler
wrote:
No worries. I've already got Nexus installed (just dropped the WAR
into Tomcat; almost too easy). I just haven't played with it enough
yet to make sure it can do everything I need it to (like
Phil. I think you just need to try it and read the Nexus docs. Sounds like you
are really making things complicated for yourself.
> -Original Message-
> From: Phillip Hellewell [mailto:ssh...@gmail.com]
> Sent: Wednesday, October 06, 2010 3:43 PM
> To: Maven Users List
> Subject: Re: Can
On Wed, Oct 6, 2010 at 1:35 PM, Anders Hammar wrote:
> http://maven.40175.n5.nabble.com/how-to-centralize-configuration-accross-multiple-modules-td3199398.html#a3199398
>
> Searched Nabble for "separate configuration".
Thanks Anders. I read that thread.
I think I should be ok with my idea of al
Philip, have a look at the staging feature of Nexus Pro. That's what you
want. I believe I already said this...
/Anders
On Wed, Oct 6, 2010 at 21:42, Phillip Hellewell wrote:
> On Wed, Oct 6, 2010 at 1:37 PM, Ron Wheeler
> wrote:
> >>
> >> No worries. I've already got Nexus installed (just dr
Yes I'm aware it builds a jar with dependencies..that is because I couldn't
figure out how to solve this the right way which is why I'm asking you guys.
Pay no attention to that plugin part..I didn't check in that particular jar
into Nexus anyway. The build process builds two jars one with and o
The POMs look good to me.
I would move the to a parent POM with the compile
plug-in just to reduce the size of the project POMs but that is not what
is affecting your build.
Log from the build of B ?
Ron
On 06/10/2010 3:37 PM, thisguy wrote:
ok I've pruned out the rest of the dependencie
> maven-assembly-plugin
> 2.2-beta-5
>
>
> jar-with-dependencies
You do realize what this plugin with that configuration does, right...?
Wayne
On Wed, Oct 6, 2010 at 1:37 PM, Ron Wheeler
wrote:
>>
>> No worries. I've already got Nexus installed (just dropped the WAR
>> into Tomcat; almost too easy). I just haven't played with it enough
>> yet to make sure it can do everything I need it to (like copy
>> artifacts between repositories).
On 06/10/2010 3:14 PM, Phillip Hellewell wrote:
On Wed, Oct 6, 2010 at 12:42 PM, Siegmann Daniel, NY
wrote:
Phillip,
Nexus supports deployment via HTTP. Probably other repo managers do too.
Yeah, I just figured that out. But I'm still getting a 401 error
because I haven't set my credential
ok I've pruned out the rest of the dependencies but left everything else in
here:
Project A:
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/xsd/maven-4.0.0.xsd";>
4.0.0
m
On Wed, Oct 6, 2010 at 1:17 PM, Ron Wheeler
wrote:
> On 06/10/2010 2:42 PM, Siegmann Daniel, NY wrote:
>>
>> Using Maven in a corporate setting without having a repository manager
>> is like working in a team without a version control system. You could do
>> it but you're going to suffer.
>
> +1
http://maven.40175.n5.nabble.com/how-to-centralize-configuration-accross-multiple-modules-td3199398.html#a3199398
Searched Nabble for "separate configuration".
Anders
On Wed, Oct 6, 2010 at 19:33, Phillip Hellewell wrote:
> On Wed, Oct 6, 2010 at 9:37 AM, Phillip Hellewell
> wrote:
> >
> > I
On 06/10/2010 2:54 PM, thisguy wrote:
ok this is from project B's pom.xml
hello
myjar
1.0.0.0
jar
compile
this jar does get put into web-inf/lib but the jar
On 06/10/2010 2:42 PM, Siegmann Daniel, NY wrote:
Phillip,
Nexus supports deployment via HTTP. Probably other repo managers do too.
Using Maven in a corporate setting without having a repository manager
is like working in a team without a version control system. You could do
it but you're goin
On Wed, Oct 6, 2010 at 12:42 PM, Siegmann Daniel, NY
wrote:
> Phillip,
>
> Nexus supports deployment via HTTP. Probably other repo managers do too.
Yeah, I just figured that out. But I'm still getting a 401 error
because I haven't set my credentials yet. I haven't figured out yet
if it is Tomc
ok this is from project B's pom.xml
hello
myjar
1.0.0.0
jar
compile
this jar does get put into web-inf/lib but the jars that myjar depends on do
not. Here is
Phillip,
Nexus supports deployment via HTTP. Probably other repo managers do too.
Using Maven in a corporate setting without having a repository manager
is like working in a team without a version control system. You could do
it but you're going to suffer.
~Daniel
-Original Message-
Fro
On Wed, Oct 6, 2010 at 11:33 AM, Phillip Hellewell wrote:
>
> I probably should play it safe because I really don't want any
> artifacts to be incomplete in the repository, even if it is only the
> snapshot repository where this could happen.
Ok, I had another idea that could make developers happ
On 06/10/2010 1:09 PM, thisguy wrote:
Hi, I have project A which is a jar. Then I have project B which is a war.
In B's pom.xml I have a dependency on jar A. However when the war is built
I am not getting A's dependency jars put into my WEB-INF/lib directory.
I don't want to setup B as a chi
On Wed, Oct 6, 2010 at 9:37 AM, Phillip Hellewell wrote:
>
> I could set up the poms so they always build for all
> platforms/configs, but that won't change anything because developers
> will simply stop using Maven to do the build step. They just open the
> .sln and use Visual Studio so they onl
Hi, I have project A which is a jar. Then I have project B which is a war.
In B's pom.xml I have a dependency on jar A. However when the war is built
I am not getting A's dependency jars put into my WEB-INF/lib directory.
I don't want to setup B as a child project of A because they aren't real
smime.p7m
Description: S/MIME encrypted message
On Wed, Oct 6, 2010 at 9:28 AM, Anders Hammar wrote:
> Please, please, please have a look at a repo manager. It has these type of
> features. That's why it's called a manager.
I'm sure a repo manager can do fancy things with multiple repositories
for downloading, and I am already working on getti
On Wed, Oct 6, 2010 at 8:22 AM, Anders Hammar wrote:
> No, never to a build for a specific environment! It's "One build fits all"!
> There was a recent thread about that; you might want to have a look to get
> the details.
Point me to that thread if you could, but I don't see how it will be a
pro
On Wed, Oct 6, 2010 at 11:19 AM, Phillip Hellewell wrote:
> Speaking of snapshots, is there an easy way to delete all snapshots
> older than a given date to free up disk space? Since snapshots are
> temporary, yet plentiful, deleting old ones seems like it would be a
> common need.
Some of the r
Please, please, please have a look at a repo manager. It has these type of
features. That's why it's called a manager.
/Anders (mobile)
Den 2010 10 6 17:19 skrev "Phillip Hellewell" :
> On Mon, Oct 4, 2010 at 11:26 PM, Ron Wheeler
> wrote:
>>
>> Maven will do this automatically for you. Just set
On Tue, Oct 5, 2010 at 12:29 AM, Anders Hammar wrote:
> Have a look at this parent:
> http://repo2.maven.org/maven2/org/sonatype/forge/forge-parent/6/forge-parent-6.pom
>
> There you see that properties are used for both the repo name and url. This
> makes it possible to override these values from
On Mon, Oct 4, 2010 at 11:26 PM, Ron Wheeler
wrote:
>
> Maven will do this automatically for you. Just set the version to
> X.Y-SNAPSHOT and Maven will deploy it to your SNAPSHOT repository as defined
> in your parent POM.
Thanks Ron. I was thinking about snapshots, but wasn't quite sure if
I wa
you need to add -DoldVersion=1.0
On 6 October 2010 15:24, Jo Support wrote:
> I'm a bit puzzled by versions plugin. According to versions:set goal's
> documentation, reading the description it "sets the current project
> version, updating the details of any child modules as necessary", and
> it d
I'm a bit puzzled by versions plugin. According to versions:set goal's
documentation, reading the description it "sets the current project
version, updating the details of any child modules as necessary", and
it does.
But in optional parameters, we can see the "artifactId" parameter,
that specify
No, never to a build for a specific environment! It's "One build fits all"!
There was a recent thread about that; you might want to have a look to get
the details.
/Anders
On Wed, Oct 6, 2010 at 15:39, Phillip Hellewell wrote:
> On Tue, Oct 5, 2010 at 2:56 AM, Vincent Latombe
> wrote:
> > To h
On Wed, Oct 6, 2010 at 7:33 AM, Anders Hammar wrote:
> The LDAP realm you're referring too (mine, actually) so not the way to go.
> Nexus now includes its own LDAP support, both in OSS and Pro (the Pro one is
> more enterprise oriented).
Ok.
> Regarding your kerberos issue, I would talk to Sonat
On Tue, Oct 5, 2010 at 2:56 AM, Vincent Latombe
wrote:
> To handle distributionManagement, I define the url as a property that is
> defined in settings.xml.
> This allow me to define the whole connectivity from settings.xml. If ever my
> repository changed, I just need to update settings.xml on my
The LDAP realm you're referring too (mine, actually) so not the way to go.
Nexus now includes its own LDAP support, both in OSS and Pro (the Pro one is
more enterprise oriented).
Regarding your kerberos issue, I would talk to Sonatype.
/Anders
On Wed, Oct 6, 2010 at 15:22, Phillip Hellewell wro
On Mon, Oct 4, 2010 at 12:34 PM, Thiessen, Todd (Todd)
wrote:
> Nexus is free Phil. We use the free version for some pretty complicated
> builds and works very well. You would of have it setup by now. Very easy.
I think I just found a problem. Based on my reading, Nexus supports
LDAP (http://co
The archetype:create generates an archetype once you have defined all
the necessary properties for the archetype, while the
archetype:generate gives you user interactive options for a number of
template-archetypes.
But they both generate/creates an archetype but in quite a different manner...
Che
create doesn't do any prompting for missing arguments or utilise newer features
like the catalog. It's deprecated, and I think actually delegates to generate
internally.
On 06/10/2010, at 11:28 PM, benxs wrote:
>
> What is the difference between these two goals?
>
> From my point of view both
2010/10/6 benxs :
>
> What is the difference between these two goals?
archetype:create is deprecated.
Antonio
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.
What is the difference between these two goals?
>From my point of view both generate a project (directory structure).
Ben
--
View this message in context:
http://maven.40175.n5.nabble.com/Difference-between-archetype-create-and-archetype-generate-tp3201300p3201300.html
Sent from the Maven - Us
Hi Wayne
For app deployment we use anthill in such a way that we use the same build
for all environments and the resources are processed during the deployment.
that said, this is a special case, as this project and its modules are all
jbehave and selenium projects, which won't generate artifacts
As I somewhat expected. As you have the issue at hands, could you please
file a jira for the mave-deploy-plugin about this description being wrong?
/Anders
On Wed, Oct 6, 2010 at 11:48, NickDeGraeve wrote:
>
>
> Anders Hammar wrote:
> >
> > You might be able to solve this by setting generatePom
Doubt that. I've run into exactly the same thing when trying to script
deployments which use the deploy-file goal and includes sources/javadocs. My
solution was to just ignore any error for the javadoc and sources
deployment, as the jar was actually uploaded.
You could enable redeployments, but yo
Did you have a look at nexus logs to see what is wrong on its side ??
This is perhaps a problem of repository target settings
On Oct 6, 2010, at 11:23 AM, NickDeGraeve wrote:
>
> I'm trying to get a legacy project to build with Maven. I'm not allowed to do
> a complete makeover because of time c
So the problem is that I need to do 3 seperate deploys for the client and the
POM is added at the first invocation
It's unfortunate that the 'depoy-file' goal doesn't provide the
functionality to add the sources and Javadocs in one go like the
'install-file' goal does.
Nick
--
View this messag
For awhile I've been thinking of dusting off my polyglot maven wings and
doing a JSON based builder, but since I've never been able to resolve how
plugins such as the release plugin work with non-XML poms ( version number
rewriting etc. ) I've given up on polyglot maven for awhile.
Assuming you ca
Anders Hammar wrote:
>
> You might be able to solve this by setting generatePom to false:
> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#generatePom
> I haven't tried this personally, but the text indicates this should work.
> However, the name of the param kind of i
This is expected as a release repo is set to not allow redeploys by default.
What happens is that first the primary artifact (the jar) and the pom gets
uploaded. The you try to uploaded sources jar and the pom again, which isn't
allowed.
A snapshot repo doesn't have this restriction normally and th
I'm trying to get a legacy project to build with Maven. I'm not allowed to do
a complete makeover because of time constraints so for the time being I just
call the necessary Ant target.
The Ant build produces an EAR, a client JAR (with the interfaces for the
Swing client) and its Javadoc and sour
2010/10/6 Andrew Robinson :
> When I execute "mvn site" from the top level pom directory in maven
> 2.0.8, it builds the site for the top directory and all of the
> modules. If I execute "mvn -PsiteFix site" from maven 2.2.1, it does
> not build the modules and only builds the site for the current
67 matches
Mail list logo
