This is old, and you may have figured out your issue, but this is what worked
for us.
We had our artifactory configured to use both apache's official maven
release and snaphot repositories. We also had our settings.xml set to be a
mirrorOf "*" so that everything would go to our artifactory repo.
done..
On 10/1/07, Gisbert Amm <[EMAIL PROTECTED]> wrote:
>
> Vote for it ...
>
> -Gisbert
>
> Vanja Petreski wrote:
> > Yes!
> >
> > V
> >
> > On 10/1/07, Gisbert Amm <[EMAIL PROTECTED]> wrote:
> >
> >>This one?
> >>
> >>http://jira.codehaus.org/browse/ARCHETYPE-81
> >>
> >>-Gisbert
> >>
> >>Vanj
Vote for it ...
-Gisbert
Vanja Petreski wrote:
Yes!
V
On 10/1/07, Gisbert Amm <[EMAIL PROTECTED]> wrote:
This one?
http://jira.codehaus.org/browse/ARCHETYPE-81
-Gisbert
Vanja Petreski wrote:
Hello,
I have Maven 2.0.7 installation on the SVN with configured settings.xml,
so
every d
Yes!
V
On 10/1/07, Gisbert Amm <[EMAIL PROTECTED]> wrote:
>
> This one?
>
> http://jira.codehaus.org/browse/ARCHETYPE-81
>
> -Gisbert
>
> Vanja Petreski wrote:
> > Hello,
> >
> > I have Maven 2.0.7 installation on the SVN with configured settings.xml,
> so
> > every developer can update changes (
This one?
http://jira.codehaus.org/browse/ARCHETYPE-81
-Gisbert
Vanja Petreski wrote:
Hello,
I have Maven 2.0.7 installation on the SVN with configured settings.xml, so
every developer can update changes (for example, about repo, etc..).
I am using Artifactory for repository management and e
Hello,
I have Maven 2.0.7 installation on the SVN with configured settings.xml, so
every developer can update changes (for example, about repo, etc..).
I am using Artifactory for repository management and everything work
perfectly until now.
If I use, for example, mvn archetype:create
-DgroupId=