Hi,
I've updated my local copy of Archiva this morning and built it, and it
seems that Archiva has problems to load its configuration as I get a There
are no remote repositories configured yet when I go to Administration -
Repositories (whereas remote repositories do exist in archiva.xml).
This
I would like to get alpha-2 released to the community now.
Highlights are:
revamped xml-rpc support
converted to use rebranded plexus-security, aka redback
continuum maven plugin
many bug fixes and ui improvements.
I have it staged at:
+1
On 5/30/07, Jesse McConnell [EMAIL PROTECTED] wrote:
I would like to get alpha-2 released to the community now.
Highlights are:
revamped xml-rpc support
converted to use rebranded plexus-security, aka redback
continuum maven plugin
many bug fixes and ui improvements.
I have it staged at:
Sorry for the delay, here is my +1
Review the license header in the archetype-resources for the next release.
Vincent
2007/5/25, Brett Porter [EMAIL PROTECTED]:
Hi,
The 1.0 release of the portlet archetype doesn't work at all, but
Franz has patched it up and it's useful now. There are no open
Yep - I just filed a bug before it earlier.
On 30/05/2007, at 8:24 PM, Fabrice Bellingard wrote:
Hi,
I've updated my local copy of Archiva this morning and built it,
and it
seems that Archiva has problems to load its configuration as I get
a There
are no remote repositories configured yet
Hi,
That kind of metadata is not handled by packaging, but by the artifact manager.
What do you need this for?
If it's to automatically list all available archetypes, that would be great.
We should generalize that by having a special kind of metadata in special
groups,
like
Hi
We get some JIRA issues for the M1 plugins that really belongs to the M2
plugins. To help get these issues into the correct JIRA project from the
start, I propose that we change the names of the JIRA projects for M1
plugins. From maven-idea-plugin to Maven 1.x IDEA Plugin.
Note: for the
+1
On 30 May 07, at 11:27 AM 30 May 07, Dennis Lundberg wrote:
Hi
We get some JIRA issues for the M1 plugins that really belongs to
the M2 plugins. To help get these issues into the correct JIRA
project from the start, I propose that we change the names of the
JIRA projects for M1
See http://jira.codehaus.org/browse/MPA-43
You have my +1 if you want to go for it... :)
-Lukas
Dennis Lundberg wrote:
Hi
We get some JIRA issues for the M1 plugins that really belongs to the M2
plugins. To help get these issues into the correct JIRA project from the
start, I propose that
On 29/05/07, Brett Porter [EMAIL PROTECTED] wrote:
Heh. Nice catch! Can you get that into JIRA?
Done: http://jira.codehaus.org/browse/MNG-3015
Sure, I was envisaging that it could be fixed in 2.0.7 after which the
release plugin could have 2.0.7 as a prerequisite.
Still an unreleased
+1
On May 30, 2007, at 11:27 AM, Dennis Lundberg wrote:
Hi
We get some JIRA issues for the M1 plugins that really belongs to
the M2 plugins. To help get these issues into the correct JIRA
project from the start, I propose that we change the names of the
JIRA projects for M1 plugins.
+1
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 30, 2007 1:01 PM
To: Maven Developers List
Subject: Re: [proposal] Change project names for M1 plugins in JIRA
+1
On May 30, 2007, at 11:27 AM, Dennis Lundberg wrote:
Hi
We get some JIRA issues
+1
On 5/30/07, Brian E. Fox [EMAIL PROTECTED] wrote:
+1
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 30, 2007 1:01 PM
To: Maven Developers List
Subject: Re: [proposal] Change project names for M1 plugins in JIRA
+1
On May 30, 2007, at 11:27 AM,
+1
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 30, 2007 10:27 AM
To: dev@maven.apache.org
Subject: [proposal] Change project names for M1 plugins in JIRA
Hi
We get some JIRA issues for the M1 plugins that really belongs to the M2
plugins.
+1
- Joakim
John Casey wrote:
+1
On May 30, 2007, at 11:27 AM, Dennis Lundberg wrote:
Hi
We get some JIRA issues for the M1 plugins that really belongs to the
M2 plugins. To help get these issues into the correct JIRA project
from the start, I propose that we change the names of the JIRA
Hi,
2007/5/30, Kenney Westerhof [EMAIL PROTECTED]:
Hi,
That kind of metadata is not handled by packaging, but by the artifact
manager.
What do you need this for?
If it's to automatically list all available archetypes, that would be
great.
You guessed \o/
Currently, the selection mojo
Done!
Dennis Lundberg wrote:
Hi
We get some JIRA issues for the M1 plugins that really belongs to the M2
plugins. To help get these issues into the correct JIRA project from the
start, I propose that we change the names of the JIRA projects for M1
plugins. From maven-idea-plugin to Maven
Binding +1 votes: brett, snicoll, vsiveton
Non-binding +1 votes: oching
I'll do the release.
On 25/05/2007, at 3:40 PM, Brett Porter wrote:
Hi,
The 1.0 release of the portlet archetype doesn't work at all, but
Franz has patched it up and it's useful now. There are no open
issues for this
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (8 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1483Please synchronize the jDTAUS repository
http://jira.codehaus.org/browse/MAVENUPLOAD-1483
MAVENUPLOAD-1576Xanot (XML to Object mapper).
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (40 issues)
Subscriber: mavendevlist
Key Summary
MEV-523 prefuse -sources.jar is missing
http://jira.codehaus.org/browse/MEV-523
MEV-520 retroweaver 1.2.4 jar is corrupt
20 matches
Mail list logo
