Are you saying this worked with Maven 3.0?
If not, it could be a problem with either Maven or Artifactory. However, I
do vaguely recall seeing a ticket regarding something similar to this.
Couldn't find it in jira when I searched though.
/Anders
On Tue, Nov 30, 2010 at 08:25, Moser, Christian
Thanks for your response. Just tested it with maven 2.2.1 and maven 3.0, I
doesn't work neither.
Do you think it's a problem with the dependency-plugin? I wonder what's the
criteria is to skip files when using the goal :sources. How does the plugin
know, if it should skip or not?
The structure of my project id very simple, I have only a 'model' folder in my
existing project:
tree
.
└───model
-Message d'origine-
De : El Arbi ABOUSSOROR [mailto:el-arbi.abousso...@sogeti.com]
Envoyé : lundi 29 novembre 2010 17:11
À : users@maven.apache.org
Objet : Build failure
Just found it out by myself..
The dependency plugin creates in target a folder called
dependency-maven-plugin-markers which acts like a cache. To make sure all
available sources will be checked downloaded again you have to clean the
cache with the maven clean.
mvn -U clean dependency:sources
Hi Gérald,
just a quick update: I arranged stuff working moving the filters/
section inside the assembly plugin configuration, so instead of having
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
Sorry, just realized you suggested the same workaround in the issue! :D
Thanks,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Nov 30, 2010 at 11:10 AM, Simone Tripodi
simone.trip...@gmail.com wrote:
Hi Gérald,
just a quick update: I arranged stuff working
The main problem isn't about allowing overlapping packages, but a way
for the reports to show grouped by module.
On 26 November 2010 22:18, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
There are good reasons for not having overlapping packages in separate jars.
Namely when alves
If your packages don't overlap then packages should give the per-module
stats.
On 30 November 2010 11:40, emerson echofloripa.y...@gmail.com wrote:
The main problem isn't about allowing overlapping packages, but a way
for the reports to show grouped by module.
On 26 November 2010 22:18,
Yes, we treat POMs as projects and they are in our CI system so any
changes committed to SVN trigger a build which deploys the POM.
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time, 600 times a day
Thanks for your reply.
I re-checked and the problem was because the pom version was a release
but the parent pom defined a snapshot repository.
-Original Message-
From: Anders Hammar and...@hammar.net
To: iapazm...@sri.gob.ec, Maven Users List users@maven.apache.org
Subject: Re:
Hi,
I am trying to avoid using -Dusername= -Dpassword= in a command
line.
I would like to store this information (and password preferably
encrypted) in some svn-settings.xml or other config file.
Unfortunately as I use encrypted password (created by mvn
--encrypt-master-password password)
Subversion has its own password store which AFAIK is now encrypted on
all major platforms. Why not use that?
On 11/30/10 9:55 AM, ilya.may...@ubs.com wrote:
Hi,
I am trying to avoid using -Dusername= -Dpassword= in a command
line.
I would like to store this information (and password
Justin,
Can you please elaborate on how to use it with maven?
Thanks
Ilya Mayzel
Distributed Change Management
UBS Financial Services Inc.
1000 Harbor Boulevard, 4th Floor
Weehawken, NJ-07086
Phone: 201-352-7976
Email : ilya.may...@ubs.com
-Original Message-
From: Justin Edelson
I find the easiest thing to is to pre-populate the cache by using the
svn command directly (i.e. svn ls --username username URL).
On the Maven side, you don't have to do anything.
Justin
On 11/30/10 10:02 AM, ilya.may...@ubs.com wrote:
Justin,
Can you please elaborate on how to use it with
What are common practices in terms of where to deploy maven sites to?
I'm specifically asking for projects built internally within a company
(i.e. only available to internal users). Initially I thought that our
artifact repository itself would be a logical place but that doesn't
seem to be a
Our artifacts go In our internal Nexus repo.
Ron
On 30/11/2010 11:42 AM, Mike Lenner wrote:
What are common practices in terms of where to deploy maven sites to?
I'm specifically asking for projects built internally within a company
(i.e. only available to internal users). Initially I thought
Yes, using the maven site feature of Nexus Pro makes it one place less to
manage authorization (compared to having a separate web server).
/Anders
On Tue, Nov 30, 2010 at 18:03, Ron Wheeler
rwhee...@artifact-software.comwrote:
Our artifacts go In our internal Nexus repo.
Ron
On 30/11/2010
After much searching and talking with colleagues we've decided that we will
stick with un-jaring the parent xsds from the parent project within the maven
repository using the maven-dependency-plugin.
There seems to be no better way of keeping the XSD in sync with the Pojos that
are generated
Is there a checklist in the Maven documentation somewhere that definitively
lists the conditions under which Maven 2.2.1 (or 3.0) will resolve pom
inheritance from the filesystem rather than from the (local) repository?
We have a situation where A is the root pom, and B and C are two of its
jochen-2 wrote:
This is a good example of my belief, that it should be possible to
invoke other plugins dynamically by supplying an own configuration
section from your own plugin.
In my example, users still have to be able to configure all aspects of the
(Surefire) plugin themselves.
It *always* looks up a level for a pom. This is why I would only use
that *up-a-level* pom for aggregation and not inheritance stuff. For
that we make the parentpom project at the module level and *build* it
(install or deploy) like any other project.
Curt Yanko
Hell,
You have added a dependency to wagon-scm in your project ?
So you have to add a dependency to your scm provider too.
In your case, it should be
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-hg/artifactId
!-- not sure about the version --
*Thanks, I already figured that part out and have since updated it :)
*
On Tue, Nov 30, 2010 at 12:22 PM, Dennis Lundberg denn...@apache.orgwrote:
Hi
Although I don't think that it's related to your problems described
here, if you are running Maven 3 you need to use Maven Site Plugin 3.
The
Back in March, there was a thread involving Kathryn Huxtable and
deploying to git via the scm provider. I have a vague sense that she
subsequently reported success here. Kathryn, are you reading this? Did
you get it to work?
-
To
Yes, it's available on central at
org.kathrynhuxtable.maven.wagon.wagon-gitsite:0.2, and the docs are at
http://khuxtable.github.com/wagon-gitsite/
There are a few minor improvements I'd like to make, the main one being to
create the gh-pages branch if it doesn't exist, but it works, at least
I should point out that this was intended to deploy site documentation, not
artifacts. Did you want artifacts? That should be doable, but probably not with
the existing code. I rather think that the ssh wagon would be sufficient.
-K
On Nov 30, 2010, at 5:48 PM, Kathryn Huxtable wrote:
Yes,
I have a particularly nefarious plot. I want to use this to push an
eclipse update site to github via the sonatype maven-update-plugin.
Can I add more pathname to the end of the urls?
Your reference to ssh leads me to believe that I'm confused. How does
one use ssh to push files to github? I
Maybe I'm confused. I meant using the git protocol over ssh using the standard
git wagon.
My wagon allows you to specify a branch, but that's it.
-K
On Nov 30, 2010, at 7:04 PM, Benson Margulies wrote:
I have a particularly nefarious plot. I want to use this to push an
eclipse update site
On Tue, Nov 30, 2010 at 10:01 PM, Kathryn Huxtable
kath...@kathrynhuxtable.org wrote:
Maybe I'm confused. I meant using the git protocol over ssh using the
standard git wagon.
Now I get it. It looks like the sonatypists don't allow for arbitrary
wagons in their uploader, so it's manual file
29 matches
Mail list logo
