Brett,
i talked with Wayne (Fay) on the issue.
for the way i want to imlpement it (an INternal repository) it is NOT a
maven problem
proxy will be configured in Artifactory... so it's there where i should
focus my attention..
thanks a lot for reply and regards
marco
On 11/2/07, Brett Porter
Ah, I misunderstood - I thought you were going to configure your
username and password for your repo manager/proxy :)
Good luck,
Brett
On 03/11/2007, Marco Mistroni [EMAIL PROTECTED] wrote:
Brett,
i talked with Wayne (Fay) on the issue.
for the way i want to imlpement it (an INternal
Hi,
I already did it in the past :)
http://jira.codehaus.org/browse/MASSEMBLY-32
Cheers,
Vincent
2007/10/29, Arnaud HERITIER [EMAIL PROTECTED]:
it should be something provided within the assembly plugin or an extension
of it.
I never had the time to rewrite it for maven 2 but it shouldn't
Hi maveneers. I have an interesting problem which I'm not sure how to
solve, and I wonder if anyone else has met this before or has some
good ideas..
We have 2 products; Alpha and Beta, a CommonCode project, and a
SuperPom project (it's actually more complex than that, but this is
just to
Is there a reason to always have common code in snapshot as a
dependency? Could it not be set to the latest release and only updated
when a change from the new one is needed?
- Brett
On 03/11/2007, Nigel Magnay [EMAIL PROTECTED] wrote:
Hi maveneers. I have an interesting problem which I'm not
Hi all,
as described in dashboard documentation :
http://mojo.codehaus.org/dashboard-maven-plugin/
you must add this in your pom.xml or settings.xml to use properly the
dashboard plugin:
pluginRepositories
pluginRepository
idCodehaus Snapshots/id
url
Hi
i do that all the time when i have developed the dashboard plugin :
you must add this in your pom.xml :
build
plugins
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddashboard-maven-plugin/artifactId
version1.0-SNAPSHOT/version
configuration
The problem is that the projects always end up changing quite often -
perhaps the example of 'commoncode' is a bad one - in reality we have
about 3 'shared' projects that both teams might commit changes to.
It's desirable that they move to using a 'release' (and remove the
project from their
Hi,
I currently use Archiva 1.0 beta 2 in my project and I plan to replace
it by Archiva 1.0 beta 3 because it solves an annoying problem during
artifact deployment.
Do I need to delete my install of Archiva 1.0 beta 2 and reconfigure all
my users and repositories in my new Archiva 1.0
2007/11/1, Jason van Zyl [EMAIL PROTECTED]:
On 1 Nov 07, at 5:25 AM 1 Nov 07, Brett Porter wrote:
The archetype plugin is released independently of Maven - so it won't
change the state. The revised architecture of archetype is available
on the archetypeng branch if you'd like to test it
Yea, we talked it out a bit and he realized that actually only his
Artifactory instance will be going outside the firewall (through the
proxy), so he needs to focus his attention on giving that box
permission to get out to the Internet. I suggested a few approaches
I've used/seen and he's going to
I have a situation where I need many instances of the same plugin within
my pom. Each instance would typically require quite a long configuration.
However, all such plugin instances are basically very similar with a few
minor differences. Is it somehow possible to minimize the content of the
Yep, will certainly do
On 11/3/07, Wayne Fay [EMAIL PROTECTED] wrote:
Yea, we talked it out a bit and he realized that actually only his
Artifactory instance will be going outside the firewall (through the
proxy), so he needs to focus his attention on giving that box
permission to get
Tell us more about what you're trying to do, what plugin(s) you're
using, and why you're doing this. There may be a smarter, more
Maven-ish way to do it.
Wayne
On 11/3/07, Farrukh Najmi [EMAIL PROTECTED] wrote:
I have a situation where I need many instances of the same plugin within
my pom.
Hi,
Does anyone know how to upload an artifact created by the assembly
pluing to a remote file system? The install and deploy plugins have to
be used in conjunction with a maven repository whereas i was just
looking to upload the files directly so they can be served through a
normal web
I am trying to compile a fairly complex set of XMl Schemas using JAXB RI
and the maven-jaxb-plugin.
This plugin does not provide a simple way to map schema directories to
java packages (only maps on a per schema file basis).
So I need to run the plugin for each directory in my schema tree and
Hello
I have faced with maven warning, and I cant find explanation nor fix for it,
maybe you can help me.
My project is single module application with war packaging.
A while ago we migrated from ant to maven and to map our project structure
into maven I had to do a lot of configuration in
This is cool!
Is there a release date for an official release?
What should I do to use your modified version? Is the assembly plug-in
enough or shall I apply all the other diffs too?
Ste
On 11/3/07, Vincent Siveton [EMAIL PROTECTED] wrote:
Hi,
I already did it in the past :)
Right - at the very least, even if you still need to use the proxy
from there, you only have to configure the u/p in one place and it can
be locked down to system administrators.
- Brett
On 04/11/2007, Marco Mistroni [EMAIL PROTECTED] wrote:
Yep, will certainly do
On 11/3/07, Wayne Fay
Cam wrote:
Hi,
Does anyone know how to upload an artifact created by the assembly
pluing to a remote file system? The install and deploy plugins have to
be used in conjunction with a maven repository whereas i was just
looking to upload the files directly so they can be served through a
You can use jelly's forEach tag [1], eg here is a snippet used in the m1
xdoc plugin:
fileScanner var=xmlFiles
fileset dir=${maven.docs.src}
patternset
include name=**/*.xml/
exclude name=**/${maven.xdoc.navigation.file} /
/patternset
21 matches
Mail list logo
