Definitely deserves +1
However, I'm still torn between using apt and a wiki site but whichever
wins I think the obvious casualty will be the site-plugin.
If we continue on using the pages generated by the site plugin, and
based from John Casey's "Core Documentation" point #2, it will be a
m
Issue Subscription
Filter: Design & Best Practices (34 issues)
Subscriber: mavendevlist
Key Summary
MNG-612 implement conflict resolution techniques
http://jira.codehaus.org/browse/MNG-612
MNG-1508Need a process-test-classes phase
http://jira.codehaus.org/b
Thx Brett :o)
On 6/16/06, Brett Porter <[EMAIL PROTECTED]> wrote:
done
Fabrice Bellingard wrote:
> Hi guys,
>
> I've just figured out that I can't edit JIRA issues for Maven projects
> (only
> for the MOJO project). Can someone give me the rights to edit JIRA
issues
> please?
>
> Thx in advanc
done
Fabrice Bellingard wrote:
Hi guys,
I've just figured out that I can't edit JIRA issues for Maven projects
(only
for the MOJO project). Can someone give me the rights to edit JIRA issues
please?
Thx in advance!
Cheers,
Fabrice.
--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http:
Hi guys,
I've just figured out that I can't edit JIRA issues for Maven projects (only
for the MOJO project). Can someone give me the rights to edit JIRA issues
please?
Thx in advance!
Cheers,
Fabrice.
+1
Carlos Sanchez wrote:
I'd like to release the 2.0.1 with only one bug fix,
http://jira.codehaus.org/browse/MPIR-2
I know there are some pending issues but until somebody has time to go
for them releasing 2.0.1 will help avoid the innumerable times people
had reported this bug.
--
Brett P
+1
Emmanuel Venisse wrote:
I'd prefer to release all wagons.
We have actually three open issues that will be fixed in beta-2
Emmanuel
Emmanuel Venisse a écrit :
hi,
wagon-webdav providers works fine and it is required for some release
of mojo and plexus projects.
here my +1
Emmanuel
-
+1
On 6/15/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I'd prefer to release all wagons.
We have actually three open issues that will be fixed in beta-2
Emmanuel
Emmanuel Venisse a écrit :
> hi,
>
> wagon-webdav providers works fine and it is required for some release of
> mojo and plexus
+1
Vincent
2006/6/15, Emmanuel Venisse <[EMAIL PROTECTED]>:
I'd prefer to release all wagons.
We have actually three open issues that will be fixed in beta-2
Emmanuel
Emmanuel Venisse a écrit :
> hi,
>
> wagon-webdav providers works fine and it is required for some release of
> mojo and plex
+1
Vincent
2006/6/15, Carlos Sanchez <[EMAIL PROTECTED]>:
I'd like to release the 2.0.1 with only one bug fix,
http://jira.codehaus.org/browse/MPIR-2
I know there are some pending issues but until somebody has time to go
for them releasing 2.0.1 will help avoid the innumerable times people
had
+1 Sounds reasonable.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Carlos Sanchez
> Sent: Thursday, June 15, 2006 3:42 PM
> To: Maven Developers List
> Subject: [VOTE] Release maven-project-info-reports-plugin 2.0.1
>
> I'd like to release the
+1
Emmanuel
Carlos Sanchez a écrit :
I'd like to release the 2.0.1 with only one bug fix,
http://jira.codehaus.org/browse/MPIR-2
I know there are some pending issues but until somebody has time to go
for them releasing 2.0.1 will help avoid the innumerable times people
had reported this bug.
I'd like to release the 2.0.1 with only one bug fix,
http://jira.codehaus.org/browse/MPIR-2
I know there are some pending issues but until somebody has time to go
for them releasing 2.0.1 will help avoid the innumerable times people
had reported this bug.
--
I could give you my word as a Spaniar
+1
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 15, 2006 2:51 PM
> To: Maven Developers List
> Subject: Re: [vote] Release all wagons (was Re: [vote]
> Release wagon-webdav 1.0-beta-1)
>
> we want to keep them all in the same version (a
we want to keep them all in the same version (at least for now) so it's more easy to update them in
projects that use them.
Emmanuel
Mike Perham a écrit :
Can you summarize why? Do they all have outstanding fixes deserving of
a release? Or are you just keeping them all versioned with the sa
Hi,
is there a snapshot of the maven-changes-plugin available somewhere? I would
like to do a release Apache XML-RPC, where I am using this snapshot to
generate the site. Obviously, this only makes sense, if someone else is able
to rebuild the site without too many hazzle.
If not: Could someone
+1
In the m1 artifact plugin we are using beta 6 or 7 versions.
If there are some interesting fixes in wagon since theses releases it could
be useful for use to release a new version of the artifact plugin to bundle
it in m1 beta 3.
Arnaud
On 6/15/06, Mike Perham <[EMAIL PROTECTED]> wrote:
Can
Can you summarize why? Do they all have outstanding fixes deserving of
a release? Or are you just keeping them all versioned with the same
version (1.0-beta-1)?
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 15, 2006 9:22 AM
> To: Maven D
On 6/15/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I'd prefer to release all wagons.
We have actually three open issues that will be fixed in beta-2
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
I'd prefer to release all wagons.
We have actually three open issues that will be fixed in beta-2
Emmanuel
Emmanuel Venisse a écrit :
hi,
wagon-webdav providers works fine and it is required for some release of
mojo and plexus projects.
here my +1
Emmanuel
--
+1
Been using it internally since it appeared.
Mark
On 15/06/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
+1
On 6/15/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> hi,
>
> wagon-webdav providers works fine and it is required for some release of mojo
and plexus projects.
>
> here my +1
>
On 6/15/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> hi,
>
> wagon-webdav providers works fine and it is required for some release of mojo
and plexus projects.
>
> here my +1
+1
Won't you release the full wagon-providers module?
Jerome
---
+1
On 6/15/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
hi,
wagon-webdav providers works fine and it is required for some release of mojo
and plexus projects.
here my +1
Emmanuel
-
To unsubscribe, e-mail: [EMAIL PROTECT
+1
managed to deploy the site for mevenide2 easily.
Milos
On 6/15/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
hi,
wagon-webdav providers works fine and it is required for some release of mojo
and plexus projects.
here my +1
Emmanuel
hi,
wagon-webdav providers works fine and it is required for some release of mojo
and plexus projects.
here my +1
Emmanuel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 6/15/06, John Casey <[EMAIL PROTECTED]> wrote:
Hi everyone,
I know we've talked about this quite a bit already. Actually, I'm having
trouble finding the past threads on this topic in my email...can someone who
knows please link them in?
Basically, I've talked to Brett, Jason, and a few other
[SNIP]
It will come as no surprise that I think you should encourage more
user-contributed documentation. (Aside from submitting patches for
the apt source-- that's too high a barrier if you just want to share a
plugin configuration example that works for you.)
Agreed. I'd like to see if we
On 6/14/06, John Casey <[EMAIL PROTECTED]> wrote:
Basically, I've talked to Brett, Jason, and a few other Maven developers,
and I think it's time we started making website documentation a top priority
for Maven.
General thoughts -- I never navigate the Maven site, I go straight to
Google. (So
Hi John,
Here are inlined some propositions.
2006/6/15, John Casey <[EMAIL PROTECTED]>:
Hi everyone,
[SNIP]
I've put my ideas here:
http://www.commonjava.org/~jdcasey/maven-documentation-proposal.html
I apologize if it looks like I ripped off someone else's ideas...I
honestly
cannot fin
Jason van Zyl
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
a few days ago I have posted a request on the Maven user list for some
way to create a source bundle for an artifact which not only includes
the artifact's source (as produced by source:jar) but also the sources
of its transitive dependencies. I was told that the closest approach
to this is u
Hi,
When I run maven 1.0.2 under USS and I'm encountering a character set
conversion issue. It outputs some gibberish which when you convert
from ISO8859-1 to IBM-1047 appears to be environment variables. From
what I gather, this happens when you use in
maven.xml. It seems that maven expects the
Hi Dan,
dan tran wrote:
Hi Richard,
The native-maven-plugin JNI example shows that you can have your native
project depends on a java jar project that has
java jni interfaces. This way you can use native plugin to generate jni
native include files before building the native artifacts.
This is
Yep, I am on that task to get them organized and published.
Cheers,
Rahul
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Thursday, June 15, 2006 6:09 PM
Subject: Re: Fw: [plexus-dev] Plexus Website
That's a good idea too :)
I was ac
34 matches
Mail list logo
