(as sent to users@)
In the lead up to the 2.0.2 release, I'd like anyone experiencing:
[WAGONSSH-28] session is down
[WAGONSSH-30] hangs during deployment
to test the following wagon snapshots:
http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0-alpha-6-SNAPSHOT/wagon
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060105.071501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060105.071501.txt
-
To unsubscribe, e-mai
thanks! Fixed.
- Brett
Lukas Theussl wrote:
> You have the wrong JIRA issue in the log, it should be MNG-1907.
>
> -Lukas
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
You have the wrong JIRA issue in the log, it should be MNG-1907.
-Lukas
[EMAIL PROTECTED] wrote:
Author: brett
Date: Wed Jan 4 23:02:46 2006
New Revision: 366101
URL: http://svn.apache.org/viewcvs?rev=366101&view=rev
Log:
[MAVEN-1907] Include scpexe wagon by default, and upgrade to alpha-6 S
[ http://jira.codehaus.org/browse/MNG-1907?page=all ]
Brett Porter closed MNG-1907:
-
Resolution: Fixed
> Bundle wagon-ssh-external with maven dist
> -
>
> Key: MNG-1907
> URL: http://jira.codehau
[ http://jira.codehaus.org/browse/MNG-1419?page=all ]
Brett Porter updated MNG-1419:
--
Assign To: Brett Porter
Fix Version: (was: 2.0.3)
2.0.2
> resolve outstanding wagon issues
>
>
> Key:
[ http://jira.codehaus.org/browse/MASSEMBLY-51?page=all ]
Dan Tran updated MASSEMBLY-51:
--
Attachment: pom.xml
> assembly:attached fails
> ---
>
> Key: MASSEMBLY-51
> URL: http://jira.codehaus.org/browse/MASSEMBLY-51
>
[ http://jira.codehaus.org/browse/MRM-44?page=all ]
Maria Odea Ching updated MRM-44:
Attachment: MRM-44-maven-repository-indexer.patch
> search by group, artifact and version
> -
>
> Key: MRM-44
> URL
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (8 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-664jlmenu 1.0
http://jira.codehaus.org/browse/MAVENUPLOAD-664
MAVENUPLOAD-663please upload jtds (bundle provided)
http://jira.codehaus
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (14 issues)
Subscriber: mavendevlist
Key Summary
MEV-278 Invalid POM for jcoverage 1.0.5 at iBiblio
http://jira.codehaus.org/browse/MEV-278
MEV-277 More Spring Dependencies Should be Optional
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060105.011501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060105.011501.txt
-
To unsubscribe, e-mai
Brett Porter wrote:
Jason van Zyl wrote:
That's not a problem, and we can try to get everything useful in a
single line for things like Mylar.
I didn't know it needed a single line? That might make it harder to
read, but we can look into it.
It will take more, it's just the one line summary
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060105.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
assembly:attached fails
---
Key: MASSEMBLY-51
URL: http://jira.codehaus.org/browse/MASSEMBLY-51
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp, jdk 1.5, maven-2.0|2.0.1|2.0.2-SNAPHOT
Reporter: Dan Tran
[ http://jira.codehaus.org/browse/MSITE-6?page=comments#action_54958 ]
Valerio Schiavoni commented on MSITE-6:
---
marked as fixed, but still faced here.
the stacktrace is the following:
[DEBUG] Found 0 components to load on start
[DEBUG] Building Maven u
+1
Vincent
2006/1/2, Arnaud HERITIER <[EMAIL PROTECTED]>:
> Hi all,
>
> It seems useful for some users to have a maven-sources-plugin for m1.
> http://jira.codehaus.org/browse/MAVEN-1736
> Are you agree if we add it in the m1 plugins ?
>
> [ ] +1 - It seems to be a good idea.
> [ ] +0 - Don'
+1
Vincent
2006/1/4, Brett Porter <[EMAIL PROTECTED]>:
> All issues in JIRA have been completed. Please test the published snapshot.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Release will proceed in 72 hours if vote carries.
>
> - Brett
>
> -
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060105.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060105.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Thoughts on logging:-
I would like to see logging messages use relevant and meaningful identifiers
that are correlatable to provide users with a means of knowing what is going
on and what sequence of events has brought about the output. Currently huge
amounts of work goes on 'behind the scenes
+1
Vincent
2006/1/4, Brett Porter <[EMAIL PROTECTED]>:
> All scheduled issues in JIRA have been completed. Please test the
> published snapshot.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Release will proceed in 72 hours if vote carries.
>
> NB: The only change is the inclusion of the deploy:deploy-file mo
Lukas Theussl wrote:
Hi all,
The following m1 plugins all have zero issues open:
[] faq
[] multichanges
[] clean
[] genapp
+1
and I would like to release them for inclusion in m1.1-beta-3. The
future documentation is here:
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/ref
+1
Lukas Theussl wrote:
>
> Hi all,
>
> The following m1 plugins all have zero issues open:
>
> [] faq
> [] multichanges
> [] clean
> [] genapp
>
> and I would like to release them for inclusion in m1.1-beta-3. The
> future documentation is here:
>
> http://people.apache.org/~ltheussl/maven-s
Hi all,
The following m1 plugins all have zero issues open:
[] faq
[] multichanges
[] clean
[] genapp
and I would like to release them for inclusion in m1.1-beta-3. The
future documentation is here:
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/faq/
http://
Jason van Zyl wrote:
> That's not a problem, and we can try to get everything useful in a
> single line for things like Mylar.
I didn't know it needed a single line? That might make it harder to
read, but we can look into it.
> If you actually look at the way Mylar works it pulls everything in fr
[ http://jira.codehaus.org/browse/MNG-1867?page=comments#action_54953 ]
Brett Porter commented on MNG-1867:
---
Mike - we are currently resorting to custom resolvers for such cases. You
basically use the repository, or you don't - it can't be mixed and matche
I'm using Maven Proxy to cache not only ibiblio, but some of our
internal repos as well (remote offices, etc). The problem is that MP
will look at all sites for snapshots before returning the result. This
means that queries for internal snapshots hit ibiblio. This is at best a
slowdown, at worst ca
[ http://jira.codehaus.org/browse/MPGENAPP-21?page=all ]
Lukas Theussl closed MPGENAPP-21:
-
Resolution: Fixed
> generated structure does not conform to maven standards
> ---
>
> Key: MPGEN
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54948 ]
Brett Porter commented on MNG-1323:
---
workaround is to include the dependency in the first antrun plugin instance
encountered. one way to guarantee would be to include this in the root
Create XML documents containing report data.
Key: MPIR-17
URL: http://jira.codehaus.org/browse/MPIR-17
Project: Maven 2.x Project Info Reports Plugin
Type: Improvement
Versions: 2.0-beta-3
Reporter: Chris Hagm
[ http://jira.codehaus.org/browse/MNG-1921?page=comments#action_54946 ]
Brett Porter commented on MNG-1921:
---
I don't think this is a bug.
Let me understand:
child inherits parent, but peer does not?
dependency management is not transitive, however the ea
[ http://jira.codehaus.org/browse/MNG-1908?page=comments#action_54945 ]
Brett Porter commented on MNG-1908:
---
look into the unique version = false problem which is probably the same too
> M1 snapshots on legacy repos can not be used with m2
> --
I really like
project/
|_ src
|_ main
|_ test
|_ unit
|_ java
|_ resources
|_ integration
|_ java
|_ resources
|_ functional
|_ java
|_ resources
perhaps we could make it backwards compatible and support the old way of
d
[ http://jira.codehaus.org/browse/MNG-1915?page=comments#action_54944 ]
Brett Porter commented on MNG-1915:
---
so, this is an aggregating artifact?
> Top level project have to have a packaging of "pom". What about plug-ins
> wanting to make a different top
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_54943 ]
Brett Porter commented on MSUREFIRE-23:
---
You can use profiles to have the selected version based on the executing JDK,
but that may not be what you desire. The selection mechan
jlmenu 1.0
--
Key: MAVENUPLOAD-664
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-664
Project: maven-upload-requests
Type: Task
Reporter: Ofir Reichenberg
Attachments: jlmenu-1.0-bundle.jar
http://jlmenu.sourceforge.net/jlmenu-1.0-bundle.jar
JavaLay
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060104.210001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060104.210001.txt
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54941 ]
ruel loehr commented on MNG-1323:
-
Are there any suggested work arounds for this issue?Hence, if I wish to use
a custom ant task in a child module (which would require a dependency u
Brett Porter wrote:
I still have a problem with this template. Sorry to keep bringing this
up, but I'd really like consistency in this area.
Eugene made a good point about why the summary should go first, and why
we should be consistent:
http://www.jroller.com/page/eu?entry=cvs_comment_templates
Jason van Zyl wrote:
>> For design, I believe it should go with the project itself, targetted at
>> the same release as it is aimed for.
>
> Not sure if all of them would align with a release, but more importantly
> it's not easy to see the priorities in design vs scheduled work given
> the way JI
Brett Porter wrote:
Initial thoughts are -1.
To me, the Maven dev process is a function of the whole project and can
easily be dealt with in MPA.
The dev process will be applied to all the projects in the Maven TLP
yes, but I'm specifically talking about a JIRA project for scheduled
work li
[ http://jira.codehaus.org/browse/MDEPLOY-18?page=comments#action_54940 ]
Brett Porter commented on MDEPLOY-18:
-
I've never seen anything like that.
Do you have a second distributionManagement section by accident?
Is it possible to attach your full POM
Hi,
I've started a document at
http://docs.codehaus.org/display/MAVEN/best+practices+-+testing+strategies
where I've listed the known issues/questions I had in mind WRT Maven 2 and
testing.
If you're interested in testing could you please have a look and add/comment
if you have other questions/th
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060104.203000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060104.203000.txt
reminder to moderators not to moderate through anything from this address.
I tried emailing it, but didn't get a response. Who knows what they've done.
- Brett
[EMAIL PROTECTED] wrote:
> test scope in dependencyManagement does not appear to be transitive to
> dependent subProjects
> ---
[ http://jira.codehaus.org/browse/MNG-1922?page=all ]
Vincent Massol updated MNG-1922:
Summary: Rename maven-it-plugin plugin as its name implies it is for
performing integration tests in general (was: Renamed maven-it-plugin plugin
as its name implies
Renamed maven-it-plugin plugin as its name implies it is for performing
integration tests in general
Key: MNG-1922
URL: http://jira.codehaus.org/browse/MNG-1922
Project: Mav
test scope in dependencyManagement does not appear to be transitive to
dependent subProjects
Key: MNG-1921
URL: http://jira.codehaus.org/browse/MNG-1921
Project: Maven 2
Ty
Check the project lead: http://jira.codehaus.org/browse/MASSEMBLY
It should be you, Brett, right? :)
Cheers,
Stéphane
On 1/4/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> There isn't anything documented on the naming of variables, but would
> suggest following the surrounding code. I was referrin
Initial thoughts are -1.
To me, the Maven dev process is a function of the whole project and can
easily be dealt with in MPA. I don't think there'll be a lot of "issues"
to raise there, especially nothing requiring scheduling.
For design, I believe it should go with the project itself, targetted
There isn't anything documented on the naming of variables, but would
suggest following the surrounding code. I was referring to things like
"pAssembly", where we usually stick to just "assembly".
Thanks,
Brett
Jochen Wiedmann wrote:
>
> Brett,
>
> I was aware of a certain code style, when it c
Thanks! I was planning to do it as part of another issue, but appreciate
the help.
I believe that -DdescriptorRefs=... should work, but will check it out.
- Brett
Jochen Wiedmann wrote:
>
> Hi,
>
> I am quite glad about the changes in MASSEMBLY-25. However, the docs
> haven't been updated. Con
[ http://jira.codehaus.org/browse/MNG-1867?page=comments#action_54937 ]
Mike Whittemore commented on MNG-1867:
--
I would like to be able to specify a system path for any dependency regardless
of the scope. For example, I would like to mark junit-3.8.1 as
[ http://jira.codehaus.org/browse/MNG-1921?page=comments#action_54936 ]
Brian Bonner commented on MNG-1921:
---
I made an error.
The peer pom only looks like this:
child
and has no reference to easymock, however it should pick it up transitively,
or so
Hi,
I was just looking over our discussion and without a separate project
for the dev process and design JIRA doesn't make it very easy to look at
the popular issues. So it would definitely be easier for reporting to
have a separate project but it might also be good to separate
design/process
test scope in dependencyManagement does not appear to be transitive to
dependent subProjects
Key: MNG-1921
URL: http://jira.codehaus.org/browse/MNG-1921
Project: Maven 2
Typ
[ http://jira.codehaus.org/browse/MCHECKSTYLE-29?page=comments#action_54935
]
darren hartford commented on MCHECKSTYLE-29:
+1
> Checkstyle violations should link to Xref if available
> --
>
>
[ http://jira.codehaus.org/browse/MPMD-9?page=comments#action_54934 ]
darren hartford commented on MPMD-9:
+1
> Link violations to Xref
> ---
>
> Key: MPMD-9
> URL: http://jira.codehaus.org/browse/MPMD-9
> Proje
[ http://jira.codehaus.org/browse/MCHECKSTYLE-24?page=comments#action_54933
]
darren hartford commented on MCHECKSTYLE-24:
Confirmed my problem went away with the 2.0-beta-2-20051230.164525-2 version of
maven-checkstyle-plugin (tested exact same
I added mine as a warning in the appropriate section...remove if you aren't
concerned about it :)
jesse
On 1/4/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I see one comment in the dev process doco and I'm about to incorporate
> yesterday's discussion so if you want to add any notes o
Hi,
I see one comment in the dev process doco and I'm about to incorporate
yesterday's discussion so if you want to add any notes or comments into
the doco feel free. Also, it might be good to put your name with your
comments so I can track you down if I have any questions.
--
jvz.
Jason v
Do you do IBM WCS ??
Best Regards
Global Identity A/S,
Jens Fournais
CEO
Bygstubben 3 | DK-2950 Vedbaek | Denmark
Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED]
Please visit our website at: http://www.elibitum.com
[ http://jira.codehaus.org/browse/ARCHETYPE-21?page=comments#action_54925 ]
Eric Redmond commented on ARCHETYPE-21:
---
It's possible I am using old code. Let me check. I'll cancel this issue if that
is the case.
> Unecessary java directory creation
> --
[ http://jira.codehaus.org/browse/ARCHETYPE-22?page=comments#action_54924 ]
Eric Redmond commented on ARCHETYPE-22:
---
Whichever. What I was getting at is that a groupId directory structure is
inserted by default. have ${package} would make more sense wi
[ http://jira.codehaus.org/browse/MNGECLIPSE-23?page=comments#action_54923
]
Eugene Kuleshov commented on MNGECLIPSE-23:
---
Console should show the output of the maven-embedder used to fetch pom
dependencies as well as any other internal tasks, not
With planetmirror set up as the repository, and using the 2.0.0 version
of the m2 ant tasks, trying to get back
the 2.6.0 file
http://public.planetmirror.com/pub/maven/xerces/xercesImpl/2.6.0/xercesImpl-2.6.0.pom
This is not valid, because it should be pub/maven2. I think things have
been chan
[ http://jira.codehaus.org/browse/MECLIPSE-51?page=all ]
David Rice updated MECLIPSE-51:
---
Attachment: MECLIPSE-51-maven-eclipse-plugin.patch
> Issue Tracking on website points to generic MNG instead of MECLIPSE
> ---
Issue Tracking on website points to generic MNG instead of MECLIPSE
---
Key: MECLIPSE-51
URL: http://jira.codehaus.org/browse/MECLIPSE-51
Project: Maven 2.x Eclipse Plugin
Type: Bug
Versions: 2.0
SimpleSourceIncludeScanner is created with incorrect include set.
-
Key: MCOMPILER-24
URL: http://jira.codehaus.org/browse/MCOMPILER-24
Project: Maven 2.x Compiler Plugin
Type: Bug
Reporter: Brent W
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060104.163000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060104.163000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060104.161501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060104.161501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNG-1920?page=all ]
David Rice updated MNG-1920:
Attachment: MNG-1920-maven-eclipse-plugin.patch
> Allow custom project name for eclipse projects
> --
>
> Key: MNG-1920
>
Allow custom project name for eclipse projects
--
Key: MNG-1920
URL: http://jira.codehaus.org/browse/MNG-1920
Project: Maven 2
Type: New Feature
Versions: 2.0.1
Reporter: David Rice
If you download 2 versions
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060104.160001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060104.160001.txt
If deploy with uniqueVersion=false (only generate file ended SNAPSHOT), this is
not downloaded
--
Key: MNG-1919
URL: http://jira.codehaus.org/browse/MNG-1919
Project: Maven 2
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_54913 ]
Jesse Kuhnert commented on MSUREFIRE-23:
Yay! This is turning out to be a lot easier than I thought.
Question: Does anything in the maven dependency runtime have the ability
Hello,
I have a problem with running surefire tests when I have commons-logging
in my classpath. I get java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory.
I am subscriber of this list and I think I saw a solution here (adding
something to the
commons-logging...???)
but
please upload jtds (bundle provided)
Key: MAVENUPLOAD-663
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-663
Project: maven-upload-requests
Type: Task
Reporter: Miguel Griffa
Attachments: jtds-1.2-bundle.jar
--
This me
Brett Porter wrote:
All issues in JIRA have been completed. Please test the published snapshot.
[ ] +1
[ ] +0
[ ] -1
+1
Release will proceed in 72 hours if vote carries.
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Brett Porter wrote:
All scheduled issues in JIRA have been completed. Please test the
published snapshot.
[ ] +1
[ ] +0
[ ] -1
+1
Release will proceed in 72 hours if vote carries.
NB: The only change is the inclusion of the deploy:deploy-file mojo.
Most of the issues filed actually must be
[ http://jira.codehaus.org/browse/SCM-116?page=comments#action_54899 ]
David Boden commented on SCM-116:
-
>I think it is assumed that when you update the root of a multi-project, the
>SCM updates everything underneath that directory, including all subproject
[ http://jira.codehaus.org/browse/MCHECKSTYLE-29?page=all ]
Nick Giles updated MCHECKSTYLE-29:
--
Attachment: MCHECKSTYLE-29.patch
> Checkstyle violations should link to Xref if available
> --
>
>
Checkstyle violations should link to Xref if available
--
Key: MCHECKSTYLE-29
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-29
Project: Maven 2.x Checkstyle Plugin
Type: New Feature
Reporter: Nick Giles
[ http://jira.codehaus.org/browse/MNG-1784?page=all ]
David Boden closed MNG-1784:
Resolution: Fixed
Fix Version: 2.0.1
Aggregator poms must now be of type pom. You get an error message if this is
not the case.
> mvn install - multiple modules us
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060104.133000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060104.133000.txt
Vincent Massol wrote:
-Original Message-
From: Jesse McConnell [mailto:[EMAIL PROTECTED]
Sent: mercredi 28 décembre 2005 20:44
To: Maven Developers List
Subject: Re: [discussion] Integration testing location
I worry a bit about mixing unit and integration tests generally...
maybe we h
you can make an issue for each plugin you want to contribute here:
http://jira.codehaus.org/browse/MOJO
for plugin discussion the [EMAIL PROTECTED] is probably the more appropriate
address
cheers!
jesse
On 1/4/06, Jurgen De Landsheer <[EMAIL PROTECTED]> wrote:
>
> hello,
>
> I've developed som
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060104.13.txt
[ http://jira.codehaus.org/browse/MEV-275?page=all ]
Carlos Sanchez closed MEV-275:
--
Resolution: Fixed
AFAIK there's nothing to do with the jar artifact
> Castor dependencies
> ---
>
> Key: MEV-275
> URL: http://jira
hello,
I've developed some plugins (lint4j, linguine maps, spring beandocs)
that I want
to submit to the sandbox on codehaus. I've seen that I need to create an
issue,
but in wich project - "Maven 2" or some other - and issue type "new
feature"
or "improvement". And then what? Can I submit i
[ http://jira.codehaus.org/browse/MEV-278?page=comments#action_54890 ]
Carlos Sanchez commented on MEV-278:
attached pom is missing log4j and includes itself
> Invalid POM for jcoverage 1.0.5 at iBiblio
> --
>
>
+1
On 1/4/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> +1
>
> Arnaud
>
>
> On 1/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> >
> > +1
> >
> > Emmanuel
> >
> > Brett Porter a écrit :
> > > All scheduled issues in JIRA have been completed. Please test the
> > > published snapshot.
> > >
>
[ http://jira.codehaus.org/browse/MDEPLOY-18?page=all ]
Morten Kristiansen reopened MDEPLOY-18:
---
But why is it trying to create tracetracker at /? And it's not using morten as
user, but maven:
>From pom.xml:
marplerepo
[ http://jira.codehaus.org/browse/MNG-1916?page=comments#action_54888 ]
Nils Fredrik Gjerull commented on MNG-1916:
---
Wildcarded {{}} would certainly help. As commented in issue MNG-1915 I
am working on making a maven2 plug-in for JPF. This is the r
Hi,
I am quite glad about the changes in MASSEMBLY-25. However, the docs
haven't been updated. Consequently, the docs are now reflecting
deprecated features.
I am ready to submit a patch for the docs. However, before I work these
out, I have a couple of questions:
- What is the policy
Brett,
I was aware of a certain code style, when it comes to indentation, and
the like. I did my best to follow that code style. However, I am
completely lost, when it comes to a code style in terms of variable
names. Any additional hints on that?
Regards,
Jochen
--- Begin Message ---
[ http://jira.codehaus.org/browse/MNG-1915?page=comments#action_54880 ]
Nils Fredrik Gjerull commented on MNG-1915:
---
I am working on creating a maven2 plug-in for Java Plug-in Framework
([http://jpf.sourceforge.net/]). This framework is inspired by
[ http://jira.codehaus.org/browse/CONTINUUM-532?page=all ]
Emmanuel Venisse closed CONTINUUM-532:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Fixed.
> Add ability to move from a particular build to the build list for a project.
> -
[ http://jira.codehaus.org/browse/CONTINUUM-531?page=comments#action_54861
]
Emmanuel Venisse commented on CONTINUUM-531:
It isn't in template page
(http://people.apache.org/~brett/white-site/viewProject.html). Where do you
want it?
> Add back
+1
Arnaud
On 1/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>
> +1
>
> Emmanuel
>
> Brett Porter a écrit :
> > All scheduled issues in JIRA have been completed. Please test the
> > published snapshot.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Release will proceed in 72 hours if vote carr
+1
Arnaud
On 1/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>
> +1
>
> Emmanuel
>
> Brett Porter a écrit :
> > All issues in JIRA have been completed. Please test the published
> snapshot.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Release will proceed in 72 hours if vote carries.
> >
> >
1 - 100 of 104 matches
Mail list logo
