-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It uses anakia to transform, but in true Maven spirit it should be able
to be done - with a plugin. ;-) And maybe maven-site is suited to it
just fine (not a maven-site expert for user sites AT ALL - I'm with
Jesse here that so much more 'whiz-bang' is
Hi Stephane and other devs announcing plugin releases,
just a recommendation for the next plugin announcement:
Report the Maven version the plugin is designed for. Only the link to the
documentation below indicates, that this is an update for a Maven 1 plugin.
Also it does not really help users
On 3/9/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jesse Kuhnert wrote:
> > I think what everyone is saying sounds more or less correct, but what is
> the
> > solution then?
> >
> > If they can't rely on a runtime container to host the site
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse Kuhnert wrote:
> I think what everyone is saying sounds more or less correct, but what is the
> solution then?
>
> If they can't rely on a runtime container to host the site, options become
> MUCH more limited.
>
> Complaints about the UI are f
I think what everyone is saying sounds more or less correct, but what is the
solution then?
If they can't rely on a runtime container to host the site, options become
MUCH more limited.
Complaints about the UI are fine and I'm sure everyone welcomes them, but
possible solutions that fit into the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All in all, I'd have to agree with the sentiments of this. I don't think
anything should be taken personally although I know some personalities
might be inclined to react emotionally at the words used, but if you
look at the sentiment I believe it's ri
On 3/8/06, John Casey <[EMAIL PROTECTED]> wrote:
>
>
> Something to think about is maybe not having the initial Maven page be a
> > Maven site. ASF sites in general seems to be more Developer focused
> than
> > user focused. What if the initial Maven site were more like the front
> pages
> >
That separates the core site, but there is still a two issues, and,
unfortunately, I'm not sure if there is an easy way to address it.
First, it is easy to publish specific versions of projects to different
directories. But, the Maven documentation consists of a bunch of related
sites. I think t
sorry, just got to read this now... will change it now. Thanks.
Emmanuel Venisse wrote:
I think it will be better to use a logger instead of
System.out.println in DiscoverJob.
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: epunzalan
Date: Thu Mar 2 01:53:40 2006
New Revision: 382337
URL: h
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (6 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-771Upload request for SLF4J 1.0 (final) and NLOG4J 1.2.23
http://jira.codehaus.org/browse/MAVENUPLOAD-771
MAVENUPLOAD-770jalopy-console-0.1-1.5rc2
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (25 issues)
Subscriber: mavendevlist
Key Summary
MEV-352 Relocate cvslib in netbeans groupId to cvsclient in org.netbeans.lib
http://jira.codehaus.org/browse/MEV-352
MEV-356 Missing dep on jboss-
On 3/9/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> Hi guys,
>
> I would like to inform you and have your feedback about some changes I'm
> preparing to apply on the m1 web site.
>
> I added a homepage for the plugins in /maven-1.x/plugins/
> http://people.apache.org/~aheritier/maven-st
Good to see discussion on this. I'll choose more controversial topics
next time, because I've already discussed this with myself at length on
this list.
As I've said recently, I'm just waiting for 2.0.3 to my plan into action.
- Brett
Tim O'Brien wrote:
> Having to choose between publishing the
Sonuds good.
Lukas Theussl wrote:
> +1
>
> -Lukas
>
>
> Arnaud HERITIER wrote:
>> Hi guys,
>>
>> I would like to inform you and have your feedback about some changes
>> I'm
>> preparing to apply on the m1 web site.
>>
>> I added a homepage for the plugins in /maven-1.x/plugins/
>> http://
I will work since FireFox knows that you invoke the file directory on your
local directory
On 3/8/06, Mang Lau (JIRA) <[EMAIL PROTECTED]> wrote:
>
>[
> http://jira.codehaus.org/browse/CONTINUUM-621?page=comments#action_60498 ]
>
> Mang Lau commented on CONTINUUM-621:
> -
[ http://jira.codehaus.org/browse/SUREFIRE-30?page=comments#action_60502 ]
Walco van Loon commented on SUREFIRE-30:
Why not use
java.io.File.pathSeparator
for this purpose?
> Wrong classpath separator
> -
>
> Key: S
We already have that in place for the core, the site url is
maven.apache.org/ref/${project.version}/
see
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382904&view=markup
We're missing the continuous integration part to auto deploy site
everytime it's changed
On 3/8/06, Tim
Comments inline.
-john
Tim O'Brien wrote:
Sorry, gmail confused me and I sent that last one by mistake John.
I don't think you'll be trading look and feel here. I think you'd just be
doing something like making the site.xml for trunk point to a logo or banner
GIF that just added a "trunk", "d
The maven team is pleased to announce the Maven EJB Plugin 1.7.2 release!
http://maven.apache.org/maven-1.x/plugins/ejb/
To automatically install the plugin, type the following on a single line:
maven plugin:download
-DgroupId=maven
-DartifactId=maven-ejb-plugin
-Dversion=1.7.2
For a man
[ http://jira.codehaus.org/browse/SUREFIRE-33?page=all ]
Jerome Lacoste updated SUREFIRE-33:
---
Attachment: m2_2.log
> java.lang.ExceptionInInitializerError in TestCase constructor kills surefire
> without letting any log
> -
[ http://jira.codehaus.org/browse/SUREFIRE-33?page=all ]
Jerome Lacoste updated SUREFIRE-33:
---
Attachment: m2.log
> java.lang.ExceptionInInitializerError in TestCase constructor kills surefire
> without letting any log
> ---
[ http://jira.codehaus.org/browse/SUREFIRE-33?page=all ]
Jerome Lacoste updated SUREFIRE-33:
---
Attachment: SUREFIRE-33.tar
> java.lang.ExceptionInInitializerError in TestCase constructor kills surefire
> without letting any log
> --
2006/3/8, Arnaud HERITIER <[EMAIL PROTECTED]>:
>
> The problem will be also with reports.
> Do we need all reports for all releases ?
> Documentation reports like javadoc, jxr, are needed for each release.
> But is it useful for quality reports (pmd, simian, linkcheck, ...) ? These
> reports are us
The problem will be also with reports.
Do we need all reports for all releases ?
Documentation reports like javadoc, jxr, are needed for each release.
But is it useful for quality reports (pmd, simian, linkcheck, ...) ? These
reports are useful for the development team to improve their code. But fo
Sorry, gmail confused me and I sent that last one by mistake John.
I don't think you'll be trading look and feel here. I think you'd just be
doing something like making the site.xml for trunk point to a logo or banner
GIF that just added a "trunk", "draft", or "development" stamp. If this was
do
Right, I think confusion is a good word. I approach Maven as an end-user
most often, and if I need to dive into a plugin source to finally figure out
how it works I do. But, I've had the displeasure of
On 3/8/06, John Casey <[EMAIL PROTECTED]> wrote:
>
> +1
>
> Maybe we can put a banner at the t
+1
-Lukas
Arnaud HERITIER wrote:
Hi guys,
I would like to inform you and have your feedback about some changes I'm
preparing to apply on the m1 web site.
I added a homepage for the plugins in /maven-1.x/plugins/
http://people.apache.org/~aheritier/maven-stage-site/maven-1.x/plugins/
+1
Maybe we can put a banner at the top of each page that marks the version
it refers to or something. If we styled the reference doco as a manual,
it could be part of the page layout that ties it together. I'd be
willing to trade a bit of the look&feel for that sort of information, as
it see
I think this is all pretty good in principle, but I have some concerns
about specific points, which I'll summarize below. I agree that we need
to raise our minimum quality at the release level, and even at the
individual commit level. However, I'm hesitant to add too much burden to
patch contri
+1 for everything and I hope this will be enforced (by all of us)
-Lukas
Brett Porter wrote:
This is not too long, and important. Please read.
I've just spent some time discussing this on users@, and felt it was
time to bring it here to look at the practical steps going forward.
Basically, I
I think that's a good idea. In m1 we are already using the
maven.site.stage.address property to publish sites more frequently to
our personal pages (eg [1]) and I refer people to this site
occasionally. This has the obvious drawback that the
'latest-and-greatest' docs for different plugins are
Hi guys,
I would like to inform you and have your feedback about some changes I'm
preparing to apply on the m1 web site.
I added a homepage for the plugins in /maven-1.x/plugins/
http://people.apache.org/~aheritier/maven-stage-site/maven-1.x/plugins/
And I created a subdirectory for each
Having to choose between publishing the latest and greatest docs and only
the released version is a problem that Maven seems to have created for
itself. Same issue comes up in other projects frequently - Commons has a
problem because some of the sites only publish on a release. Latest and
greates
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 8 mars 2006 14:29
> To: Maven Developers List
> Subject: Re: Filtering web.xml?
>
> MWAR-12
Thanks Brett... I didn't realized it was such a hot topic! (and apparently I
missed the discussion about it).
It still works, but before it was wrong.
Before, say you ran:
mvn insllat
mvn install
the second one would fail because ERROR_CODE is still 1 from the first time.
See my comments on MNG-2127. You're assessment was right in the first
place, but I think if we change plexus-utils to always run:
"C
MWAR-12
Vincent Massol wrote:
> Hi,
>
> Is there a way in m2 to filter any file (not just resources)? For example in
> my web.xml there are references to artifact names with version in it. I'd
> like to replace the version with ${version} or something like that.
>
> Any idea how I could achieve
Why do you do this? it worked well without this change.
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: brett
Date: Wed Mar 8 05:05:43 2006
New Revision: 384207
URL: http://svn.apache.org/viewcvs?rev=384207&view=rev
Log:
fix location of original setter
Modified:
maven/components/branches/ma
Hi,
Is there a way in m2 to filter any file (not just resources)? For example in
my web.xml there are references to artifact names with version in it. I'd
like to replace the version with ${version} or something like that.
Any idea how I could achieve this? I was thinking about filters but I don'
+1
On 3/7/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> I agree. Just one comment about javadocs, they are not important just
> for public apis, they should be there for almost all methods so we
> won't have to go into the details of the code when bug fixing or
> writing new code.
>
> On 3/7/06,
Hello,
I've written a few pages with thoughts on howto map Netbeans IDE
actions, like Build/Run/Debug, to a sequence of maven goals with
custom configurations.
http://docs.codehaus.org/display/MEVENIDE/Mevenide2Design
Any comments most welcome. Either to the mailing list or edit the wiki pages.
I'm not sure how a fix in war solves anything? There are a couple
related issues that are apparently caused by the same problem unrelated
to war:
http://jira.codehaus.org/browse/MDEP-2
http://jira.codehaus.org/browse/MNG-2045
I looked into the dependency problem and project.getArtifacts() doesn't
It won't be ignored, and it needs to be fixed in the war plugin (ie
MWAR). Moving it will delay its release.
- Brett
Brian E. Fox wrote:
> Ok, I'm glad this is really a bug because I was pulling my hair out
> trying to understand what the logic was. Should the issue be moved to a
> reactor group
It would be great if maven had the ability to specify a snapshot site
url similar to how the repositories work. Then a snapshot rev gets its
site deployed some where different than the release version.
-Original Message-
From: Brian K. Wallace [mailto:[EMAIL PROTECTED]
Sent: Tuesday, Ma
Ok, I'm glad this is really a bug because I was pulling my hair out
trying to understand what the logic was. Should the issue be moved to a
reactor group so it gets considered for 2.0.4? I'm just afraid that
having it out in WAR, it might get neglected.
-Original Message-
From: Brett Port
I think that m1 commits don't pollute a lot of people ;-)
Our activity is very minor compared to the m2 one !
Arnaud
On 3/8/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> Brett Porter wrote:
> > I have some bandwidth so I'm doing this a bit earlier today.
> >
> > Going once, going twice
>
that becomes an epic adventure, close to none of the methods/classes
have a usable javadoc (most have none). the same applies to plugin
parameters, I always go to the plugin doc first, but then realize it's
useless and try finding stuff in the other site documentation. Also
please consider removing
46 matches
Mail list logo
