On 27-Aug-08, at 11:22 PM, Milos Kleint wrote:
On Thu, Aug 28, 2008 at 8:02 AM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
James,
I am not exactly sure what is the problem for Archiva or any other
project
to use nexus indexer API. For instance, Archiva is already using
number of
dependen
On Thu, Aug 28, 2008 at 8:02 AM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
>
> James,
>
> I am not exactly sure what is the problem for Archiva or any other project
> to use nexus indexer API. For instance, Archiva is already using number of
> dependencies from outside of Maven project and even f
James,
I am not exactly sure what is the problem for Archiva or any other project
to use nexus indexer API. For instance, Archiva is already using number of
dependencies from outside of Maven project and even from outside Apache
umbrella and it doesn't seem to be an issue.
As Jason already m
Eugene Kuleshov wrote:
I am running on windows and got the same errors with b4 release. See
details below.
Sounds familar to me ;-)
http://jira.codehaus.org/browse/WAGON-233
Benjamin
-
To unsubscribe, e-mail: [EMAIL PRO
brettporter wrote:
>
>> I took wagon 1.0-beta3 released code from the tag and run unit
>> tests on it > and got failures.
>> Do you have a theory how is that possible for a release?
>
> Not without more information on went wrong, no. Probably one of the
> tests has some environmental requ
On 28/08/2008, at 12:39 PM, Eugene Kuleshov wrote:
Brett,
I took wagon 1.0-beta3 released code from the tag and run unit
tests on it
and got failures.
Do you have a theory how is that possible for a release?
Not without more information on went wrong, no. Probably one of the
tests ha
Brett,
I took wagon 1.0-beta3 released code from the tag and run unit tests on it
and got failures.
Do you have a theory how is that possible for a release?
regards,
Eugene
brettporter wrote:
>
> Sorry, but I still don't really get why you think a line of
> development that is som
Should this be moved to MPLUGIN, or was it a core fix? It's currently
set as fixed in 2.0.11 :)
- Brett
On 28/08/2008, at 12:10 PM, John Casey (JIRA) wrote:
[ http://jira.codehaus.org/browse/MNG-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey clos
Jason,
I'm cool sticking with the Nexus index format - it works and there has
been a successful uptake with different tool vendors - so it seems to
be the defacto standard. We will certainly be using it in a future
version of Archiva.
What I would like to see would be that the index code
On 27-Aug-08, at 4:58 PM, Wendy Smoak wrote:
[moved from [EMAIL PROTECTED]
On Wed, Aug 27, 2008 at 2:39 PM, Jason van Zyl <[EMAIL PROTECTED]>
wrote:
For any tool you see saying they support Nexus indexes make sure
they are
using our APIs. We guarantee nothing in the way of the format, but
[moved from [EMAIL PROTECTED]
On Wed, Aug 27, 2008 at 2:39 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> For any tool you see saying they support Nexus indexes make sure they are
> using our APIs. We guarantee nothing in the way of the format, but we have
> gone to excruciating lengths to make sur
I just want to throw out some thoughts on versioning.
1) I noticed that the transformation of 2.0.10 -> 2.1 has not (yet)
also brought the renaming of SVN tags. I think this is an eventual
must-do so the future 2.0.10 -- the one designed for critical bug
fixes -- can go forward.
2) There was agre
Benjamin Bentmann wrote:
Hypermedia like the web is all about hyperlinks
In this spirit, Wendy has just suggested to add a link for the "mail
archive", too, which I happily adopted:
General instructions on how to use the Plugin Name can be found on the
{{{usage.html}usage page}}. Some m
The only benefit of the profile is that the plugin is downloaded and
installed as Maven does normally. Updating metadata accordingly and
all that jazz.
On 27-Aug-08, at 1:14 PM, Dan Fabulich wrote:
Jason van Zyl wrote:
The method that we've pushed in a couple releases is a simple
profile
Wendy Smoak wrote:
Each plugin has an associated wiki page... what do you think about
adding a link to it?
Hypermedia like the web is all about hyperlinks so I am +1 on your
suggestion. As a prerequisite, I made sure all our plugins have a
corresponding wiki page by adding a stub page where
Hi,
Can you explain in a issue what will be this changes ?
Thanks,
--
Olivier
2008/8/27 Alexey Kakunin <[EMAIL PROTECTED]>:
> +1 (even I have no voice for voiting)
> We have couple of changes, related to allow maven-scm better work with
> remote repositories (as example of using such extensions -
Wendy Smoak wrote:
Each plugin has an associated wiki page... what do you think about
adding a link to it?
Hypermedia like the web is all about hyperlinks so I am +1 on your
suggestion. As a prerequisite, I made sure all our plugins have a
corresponding wiki page by adding a stub page where
On Wed, Aug 27, 2008 at 12:02 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> I thought it would be cool to have a downloader plugin that let you do this:
>
> mvn downloader:get
>-Dartifact=org.apache.maven.plugins:maven-scm-plugin:1.1
>-DrepoUrl=http://people.apache.org/~olamy/staging-repo
Jason van Zyl wrote:
The method that we've pushed in a couple releases is a simple profile which
lists the staging repository where a test plugin has been deployed. The
profile can be generated with the release and it's a separate file, so you
just erase it when you're done with it. Think the
The method that we've pushed in a couple releases is a simple profile
which lists the staging repository where a test plugin has been
deployed. The profile can be generated with the release and it's a
separate file, so you just erase it when you're done with it. Think
the profile might be a
Some people are using the maven-reactor-plugin and they seem to like it.
http://maven.apache.org/plugins/maven-reactor-plugin/
It's at a point where I think it's basically ready to release, but I
assume it shouldn't be released from sandbox.
One weird thing about it is that three of its goal
The Maven team is pleased to announce the release of the Maven Invoker,
version 2.0.10
This shared component fires up a Maven build in a new JVM.
http://maven.apache.org/shared/maven-invoker/
Release Notes - Maven Shared Components - Version maven-invoker 2.0.10
** New Feature
* [MSHARED
I think I've found the issue. Once I've tested this theory out a little
more, I'll file a JIRA issue, and get this fixed with an integration
test in place.
Henrique Prange wrote:
Hi John,
I compared the contents of the artifacts generated by 2.0.9 and
2.0.10-RC11 and they are different. The
The vote passed: dfabulich, olamy, jvanzyl, jdcasey
I'll run the stage command now...
-- Forwarded message --
Date: Tue, 19 Aug 2008 13:00:19 -0700 (PDT)
From: Dan Fabulich <[EMAIL PROTECTED]>
Reply-To: Maven Developers List
To: Maven Developers List
Subject: [VOTE] Release Ma
I've always found it to be a hassle to test plugins that don't need to be
wired up in POM files, e.g. the archetype, dependency, scm plugins. I
find that to test them I have to create a dummy POM file with a
section, as described in our guide to testing staged
releases.
http://maven.apach
AFAICT the merge from the RC branch is done now. I'll have to look into
why the user-agent header stuff isn't working in the 2.1.x branch.
Brett Porter wrote:
I think John is still working on merging things around from the last I
saw him post... is that right John?
(2.0.9 didn't have that fea
Hi John,
I compared the contents of the artifacts generated by 2.0.9 and
2.0.10-RC11 and they are different. The latter doesn't have the Ant
build file and has a different plug-in descriptor.
Another difference is the version of maven-plugin-plugin. Maven 2.0.9
uses 2.4.1 and Maven 2.0.10-RC
Hi John,
I found something, but I can't ensure it is caused by 2.0.10-RC11. I
have a Maven plug-in that extends the lifecycle and adds a new kind of
package. It also uses some Ant tasks. When I build the plug-in with
2.0.10-RC* (I tried with RC1, RC2 and RC11) the build works. But when I
try
Hi,
Can anyone help me on this?.
I want to add my own JUnit 4.0 listener to maven-surefire-plugin in my
pom.xml. But i'm not supposed to use TestNG there, Only JUnit 4.0.
So can I register a non-TestNG listener to maven-surefire-plugin ? Please
tell me how.
Regards
Sudarshen
Hi,
The Maven team is pleased to announce the release of the Maven SCM , version
1.1.
http://maven.apache.org/scm
This version includes two new scm providers : AccuRev and Git.
Release Notes - Maven SCM - Version 1.1
** Sub-task
* [SCM-401] - Fix parseHostAndPort() for Bazaar too
** Bug
2008/8/26 Olivier Lamy <[EMAIL PROTECTED]>:
> +1 (in the future could you provide a link to the jira issues ?)
I've now tidied up JIRA:
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14530
(Note that there were other fixes in this relea
2008/8/27 Mark Hobson <[EMAIL PROTECTED]>:
> 2008/8/27 Olivier Lamy <[EMAIL PROTECTED]>:
>> Hi,
>> As I remember we dediced 2 ?
>
> Ah right, thanks, I must have missed that conversation. Have you got
> a link to the thread?
No :-)
>
> Cheers,
>
> Mark
>
> -
2008/8/27 Olivier Lamy <[EMAIL PROTECTED]>:
> Hi,
> As I remember we dediced 2 ?
Ah right, thanks, I must have missed that conversation. Have you got
a link to the thread?
Cheers,
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTE
Hi,
As I remember we dediced 2 ?
--
Olivier
2008/8/27 Mark Hobson <[EMAIL PROTECTED]>:
> 2008/8/26 Olivier Lamy <[EMAIL PROTECTED]>:
>> +1 (in the future could you provide a link to the jira issues ?)
>
> I would have liked to although the shared components all share the
> single MSHARED JIRA pro
2008/8/26 Olivier Lamy <[EMAIL PROTECTED]>:
> +1 (in the future could you provide a link to the jira issues ?)
I would have liked to although the shared components all share the
single MSHARED JIRA project, and thus the issues have no version
fields set. I could send a link for the remaining iss
35 matches
Mail list logo
