Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.091502.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.091502.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Annotation proccessing tool plugin introduction
Key: MNG-1197
URL: http://jira.codehaus.org/browse/MNG-1197
Project: Maven 2
Type: New Feature
Versions: 2.0-beta-4
Reporter: Juraj Burian
Priority: Minor
group artifact not found exceptions
---
Key: MNG-1198
URL: http://jira.codehaus.org/browse/MNG-1198
Project: Maven 2
Type: Improvement
Components: maven-artifact
Reporter: Brett Porter
Fix For: 2.0.1
the artifact resolver s
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.10.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MEV-109?page=comments#action_48498 ]
Trygve Laugstol commented on MEV-109:
-
xml-apis and xerces should probably still be there as they're needed if you're
using a older JVM. You can easily exclude them in your build.
>
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.101500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48501 ]
Jerome Lacoste commented on MNG-1130:
-
taking
> Support jar signing.
>
>
> Key: MNG-1130
> URL: http://jira.codehaus.org/browse/MNG-1130
>
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.103000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.103000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1185?page=comments#action_48502 ]
Martin Desruisseaux commented on MNG-1185:
--
Thanks for taking care of this issue :) (actually, I wonder if the priority
should have been something higher than "major", since any
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.11.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.11.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.111500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.111500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1192?page=comments#action_48503 ]
spencer portee commented on MNG-1192:
-
Yes, it ran to completion. There is a maven-metadata.xml at
http://sporty.org/java/repository/org/sporty/qdox/maven-metadata.xml, but maybe
t
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48505 ]
Jerome Lacoste commented on MNG-1130:
-
In your 1st example pom (for the jar packaging), you specify the following
config:
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.121501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.121501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Support jar signing.
Key: MNG-1130
URL: http://jira.codehaus.org/browse/MNG-1130
Project: Maven 2
Type: New Feature
Components: maven-jar-plugin
Versions: 2.0-beta-3
Environment: gentoo linux, jdk 1.4.2_06
Reporter: Corridor Software Develo
To Dan:
We're using Base ClearCase (#1) with Snapshot views (#4). We don't use
any of the "advanced" features of ClearCase. We're only using the
basics: just the copy-modify-merge features.
To Brett:
I pulled the source from the URL you gave me below. I'll just start
rummaging through it. An
[ http://jira.codehaus.org/browse/MNG-1150?page=all ]
Brett Porter updated MNG-1150:
--
Component: maven-artifact
> be able to configure custom wagon's properties
> --
>
> Key: MNG-1150
> URL: http
[ http://jira.codehaus.org/browse/MNG-1120?page=comments#action_48509 ]
fabrizio giustina commented on MNG-1120:
I had a look at this, but the first step is making the POM readers/writers xsd
aware... at the moment when a project is rewritten the xsd
goal variable not cleaned after multiproject:clean
--
Key: MPMULTIPROJECT-62
URL: http://jira.codehaus.org/browse/MPMULTIPROJECT-62
Project: maven-multiproject-plugin
Type: Bug
Versions: 1.3
Environment: Maven
Javadoc plugin puts "docletPath" on commandline instead of "docletpath"
---
Key: MNG-1199
URL: http://jira.codehaus.org/browse/MNG-1199
Project: Maven 2
Type: Bug
Components: maven-javadoc-plugin
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48513 ]
Corridor Software Developer commented on MNG-1130:
--
Brought them over from the keystore settings properties of the maven 1 jnlp
plugin. I thought it was a little stran
m2 poms using pom.currentVersion
Key: MEV-110
URL: http://jira.codehaus.org/browse/MEV-110
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Reporter: Dave Brondsema
directory-naming/naming-config/0.8 uses ${pom.curre
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48529 ]
Jerome Lacoste commented on MNG-1130:
-
I have a working mojo. I need some feedback on how to improve/clean it up it
before submitting it. Want to answer the following questions?
- u
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48541 ]
Corridor Software Developer commented on MNG-1130:
--
Suggested Answers:
1) JarSignMojo is a good name.
2) Putting the signed jar at
${project.build.directory}/signed/${
Wasn't real sure where to send this but figured the dev list was the best place
to start.
While working on converting the build process of some of the applications I
work on I found that I needed to be able to add sections to the manifest.
Currently the maven-jar-plugin doesn't support this ex
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48544 ]
Jerome Lacoste commented on MNG-1130:
-
ok I updated my code based on your comments. The only bad point is that I don't
have proper unit tests.
The only thing I could test if the Com
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48547 ]
Corridor Software Developer commented on MNG-1130:
--
The jpox plugin on the mojo site has an example of an automated unit test.
Check it out of svn:
https://svn.codeha
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48549 ]
Corridor Software Developer commented on MNG-1130:
--
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/netbeans-freeform-maven-plugin/
is a better example. Demonstra
[ http://jira.codehaus.org/browse/MNG-1150?page=all ]
John Casey updated MNG-1150:
Complexity: Expert (was: Intermediate)
Remaining Estimate: 1 hour
Original Estimate: 3600
patch is a little stale, and uses a new exception in maven-wagon (?
[ http://jira.codehaus.org/browse/MNG-1150?page=comments#action_48552 ]
John Casey commented on MNG-1150:
-
once the bootstrap finishes (to ensure I haven't messed anything up), I'll
commit and close this.
> be able to configure custom wagon's properties
> -
I wish the documentation for the plugin goals (specifically the descriptions)
were completed and included examples
--
Key: MNG-1200
URL: http://jira.codehaus.org/brows
[ http://jira.codehaus.org/browse/MPMULTIPROJECT-62?page=all ]
Lukas Theussl closed MPMULTIPROJECT-62:
---
Resolution: Fixed
Fix Version: 1.5
It's fixed in SVN (see MPMULTIPROJECT-49 ).
> goal variable not cleaned after multiproject:clean
>
[ http://jira.codehaus.org/browse/MNG-1130?page=all ]
Jerome Lacoste updated MNG-1130:
Attachment: MNG-1130-jar-sign.diff
This is my current state of the implementation.
Things lacking:
- documentation
- unit tests. I've wondered what to implement. I be
[ http://jira.codehaus.org/browse/MNG-1078?page=all ]
Brett Porter closed MNG-1078:
-
Assign To: Brett Porter
Resolution: Duplicate
> Exclude pom-type dependencies in eclipse projects
> -
>
>
[ http://jira.codehaus.org/browse/MNG-578?page=all ]
Brett Porter closed MNG-578:
Assign To: Brett Porter (was: Allan Ramirez)
Resolution: Fixed
> dependencies otherthan of type jar are added to the .classpath
> ---
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter closed MNG-122:
Resolution: Fixed
> clean up of exception handling, error reporting and logging
> ---
>
> Key: MNG-122
>
[ http://jira.codehaus.org/browse/MNG-1192?page=comments#action_48563 ]
Brett Porter commented on MNG-1192:
---
I see your repo is public - everything looks in order.
It may be requesting SNAPSHOT instead of the build number because you have
set to false?
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.163000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.163000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.164500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNG-1150?page=comments#action_48566 ]
Juan F. Codagnone commented on MNG-1150:
ohh! i forgot to diff the wagon tree!
> be able to configure custom wagon's properties
> --
[ http://jira.codehaus.org/browse/MNG-1192?page=comments#action_48567 ]
spencer portee commented on MNG-1192:
-
I just retried to recompile and now it downloaded the module fine. Serverside
seems fine, confirmed, well and dandy.
Here's my access log on
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.17.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.171501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.171501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1192?page=all ]
Brett Porter closed MNG-1192:
-
Assign To: Brett Porter
Resolution: Cannot Reproduce
I can download it using
qdox-huh
1.6-SNAPSHOT
from your repo. You had the "huh" in the wrong place.
> snaps
[ http://jira.codehaus.org/browse/MNG-1143?page=all ]
Brett Porter closed MNG-1143:
-
Assign To: Brett Porter
Resolution: Fixed
> fail-at-end swallows exceptions in subprojects
> --
>
> Key: MNG-1
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051013.173000.txt
[
http://jira.codehaus.org/browse/MAVENUPLOAD-547?page=comments#action_48570 ]
Carlos Sanchez commented on MAVENUPLOAD-547:
js-1.6R2.jar': No such file or directory inside bundle
> Upload Mozilla Rhino js 1.6R2
> -
>
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.173000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.173000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1150?page=comments#action_48571 ]
John Casey commented on MNG-1150:
-
Since the configuration method doesn't exist in maven-wagon, it's more
appropriate that the exception live outside of maven-wagon too. Plus, we've
alr
[ http://jira.codehaus.org/browse/MNG-1150?page=all ]
John Casey closed MNG-1150:
---
Resolution: Fixed
applied. Thanks, Juan.
> be able to configure custom wagon's properties
> --
>
> Key: MNG-1150
>
[ http://jira.codehaus.org/browse/MEV-35?page=comments#action_48573 ]
Brian Bonner commented on MEV-35:
-
tagsoup 1.0 rc3 is located here:
http://mercury.ccil.org/~cowan/XML/tagsoup/tagsoup-1.0rc3.jar
I also found tagsoup 0.9.7 here:
http://mercury.ccil.or
[ http://jira.codehaus.org/browse/MEV-35?page=all ]
Brian Bonner updated MEV-35:
Attachment: tagsoup-0.9.7.jar
previously mentioned file
> XOM POM references tagsoup which is not in the repo
> ---
>
>
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.18.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
dom4j 1.5.2 references stax incorrectly
---
Key: MEV-111
URL: http://jira.codehaus.org/browse/MEV-111
Project: Maven Evangelism
Type: Bug
Reporter: Brian Bonner
referenced as:
stax
stax
1.0
should be:
[ http://jira.codehaus.org/browse/MEV-34?page=all ]
Brian Bonner updated MEV-34:
Attachment: normalizer-2.6.1.jar
I'm attaching normalizer.jar which comes from the xom distribution. I think
this is the customized icu4j judging from the packages.
Hopefully
[ http://jira.codehaus.org/browse/MEV-34?page=all ]
Brian Bonner updated MEV-34:
Attachment: normalizer_license.html
license for normalizer
> XOM POM references icu4j which is not in the repo
> -
>
>
[ http://jira.codehaus.org/browse/MNG-1058?page=all ]
Brett Porter closed MNG-1058:
-
Assign To: Brett Porter
Resolution: Fixed
> errors deploying artifacts are not shown.
> -
>
> Key: MNG-1058
>
[ http://jira.codehaus.org/browse/MEV-111?page=all ]
Carlos Sanchez closed MEV-111:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> dom4j 1.5.2 references stax incorrectly
> ---
>
> Key: MEV-111
>
Bad POM for commons-codec:commons-codec-1.3
---
Key: MEV-112
URL: http://jira.codehaus.org/browse/MEV-112
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Reporter: fabrizio giustina
http://www.ibiblio.org/mav
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051013.183002.txt
Hi,
Well, we've finally closed off all the core distributable issues for
Maven 2.0.
This was a bit delayed, but with everything squared away, I'd now like
to tag the codebase as 2.0 and release the libraries. Based on those,
the plugins can be updated and all released also (those with outstanding
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.181501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.181501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+100
:)
- -john
Brett Porter wrote:
| Hi,
|
| Well, we've finally closed off all the core distributable issues for
| Maven 2.0.
|
| This was a bit delayed, but with everything squared away, I'd now like
| to tag the codebase as 2.0 and rele
[ http://jira.codehaus.org/browse/MNG-1079?page=all ]
Brett Porter closed MNG-1079:
-
Resolution: Fixed
> error reporting for a plugin not found needs improvement
>
>
> Key: MNG-1079
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why on earth would you remove the root causes from all of these
diagnosers?? Particularly the PuntDiagnoser?
Often, the root cause is the only thing that makes any sense...the rest
is just heaps of string-literal shoulder-shrugs that are too digested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm going to revise this, to -0, based on the latest diagnoser commit.
We have to provide a way to at least expression the root cause of
unknown errors in a user-friendly way. Many developers cannot read stack
traces properly, so this will enhance our
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.184825.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051013.19.txt
[ http://jira.codehaus.org/browse/MNG-968?page=all ]
John Casey closed MNG-968:
--
Resolution: Fixed
patch applied. Thanks, Lester.
> linkoffline tag is not parsed properly
> --
>
> Key: MNG-968
> URL: h
maven2 archetype plugin's maven-archetype-mojo points to snapshot
-
Key: MNG-1201
URL: http://jira.codehaus.org/browse/MNG-1201
Project: Maven 2
Type: Bug
Reporter: Brian Bonner
maven2 archetype plugi
I'd planned to summarise what I did here tomorrow as its late...
I very carefully audited every exception in the codebase and ensured
that the message of each exception always captured any appropriate
message from the cause. There are no more "shoulder shrugs".
The root simply duplicated all of t
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.19.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.19.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1201?page=comments#action_48578 ]
Brian Bonner commented on MNG-1201:
---
Disregard this, I guess. It looks like it's fixed in svn. as 2.0-beta-2.
I'm running 2.0 beta 3. I wonder why I didn't get the new code?
> mave
... of course, I only did m2, not wagon.
I'd suggest restoring the root cause for the
ArtifactResolutionException, but make sure it grabs the IOException (I
saw the 503 on the clean checkout), and don't display it if the main
message contains that message.
- Brett
Brett Porter wrote:
>I'd plann
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.191500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.191500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Missing support for adding sections to the manifest at build time
-
Key: MNG-1202
URL: http://jira.codehaus.org/browse/MNG-1202
Project: Maven 2
Type: Improvement
Components: maven-jar-plugin, maven-ar
Note I have created a bug to track this so that it doesn't get lost. The bug
is MNG-1202
Mark Russell
-Original Message-
From: Russell, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 13, 2005 9:31 AM
To: dev@maven.apache.org
Subject: [m2] maven-jar-plugin support for manifest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I only have 2 real problems here:
1. MojoExecutionException, which is meant to be a wrapper for some
unknown exception. This could be anything, and we REALLY cannot
guarantee that it's root cause is expressed in the top-level exception's
message, unl
[ http://jira.codehaus.org/browse/MNG-1164?page=all ]
John Casey updated MNG-1164:
Remaining Estimate: 10 minutes
Original Estimate: 600
> parameter should not put an "-additional" on the javadoc
> command line.
> -
[ http://jira.codehaus.org/browse/MNG-704?page=all ]
John Casey updated MNG-704:
---
Complexity: Intermediate
Remaining Estimate: 30 minutes
Original Estimate: 1800
will convert to list format.
> javadoc plugin doesn't honor multiple custom tags
[ http://jira.codehaus.org/browse/MNG-1164?page=all ]
John Casey closed MNG-1164:
---
Resolution: Fixed
> parameter should not put an "-additional" on the javadoc
> command line.
> ---
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051013.193000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051013.193000.txt
[ http://jira.codehaus.org/browse/MNG-1136?page=comments#action_48581 ]
Matthew Beermann commented on MNG-1136:
---
...but I can try to make it easy if someone's got a build environment and knows
how the POM works: it's at line 156 of CloverInstrumentMojo
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.194500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.194500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-704?page=all ]
John Casey closed MNG-704:
--
Resolution: Fixed
the javadoc plugin now supports both the old config option of:
one, two, three
AND the new list-oriented syntax:
one
two
three
> javadoc plugin
Hi Adrian,
What you can do is to use the exec task from ant in your goal.
http://ant.apache.org/manual/CoreTasks/exec.html
In the NSIS plugin we called the nsis.exe with :
The NSIS executable '${maven.nsis.exe}' could not be found
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.201500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.201500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What about component config errors in the plugin handling? I'll put it
back for artifact resolution too. I've done the MojoExecutionException
and the default diagnoser, and I'm checking that the main error message
doesn't include the root's message.
+1
Emmanuel
Brett Porter a écrit :
Hi,
Well, we've finally closed off all the core distributable issues for
Maven 2.0.
This was a bit delayed, but with everything squared away, I'd now like
to tag the codebase as 2.0 and release the libraries. Based on those,
the plugins can be updated and al
[ http://jira.codehaus.org/browse/CONTINUUM-353?page=comments#action_48586
]
Dan Tran commented on CONTINUUM-353:
It turns out, the is a bug in StarteamCheckoutConsumer (around line 106) which
throws IlegalStateException but ignored by contiuum.
So t
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051013.210001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051013.210001.txt
As I haven't been getting much of a response on the users list I thought
I'd ask here. For whatever reason I can't get m2 to use repositories
defined in a profile (see the thread below)
Any ideas? If I was going to debug this in the maven code where would I
start?
MAR
-Original Message---
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051013.211501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051013.211501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051013.213002.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051013.213002.txt
+1
On Fri, 2005-10-14 at 04:40 +1000, Brett Porter wrote:
> Hi,
>
> Well, we've finally closed off all the core distributable issues for
> Maven 2.0.
>
> This was a bit delayed, but with everything squared away, I'd now like
> to tag the codebase as 2.0 and release the libraries. Based on those,
On Thu, 2005-10-13 at 09:31 -0600, Russell, Mark wrote:
> Wasn't real sure where to send this but figured the dev list was the best
> place to start.
Have you seen this:
http://people.apache.org/~jvanzyl/maven2/guides/mini/guide-manifest.html
--
jvz.
Jason van Zyl
jason at maven.org
http://ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll withdraw this. Sorry if I was a bit harsh on this point. I just
want to make sure maven is as user friendly as we can reasonably make it.
+1
- -j
John Casey wrote:
| I'm going to revise this, to -0, based on the latest diagnoser commit.
| We h
Yep, and if you look closely the guide doesn't talk about adding
sections, only additional entries which end up in the "main" section
MAR
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, October 14, 2005 5:35 AM
To: Maven Developers List
Subject: Re: [m2] m
[ http://jira.codehaus.org/browse/MNG-1130?page=all ]
Jerome Lacoste updated MNG-1130:
Attachment: MNG-1130-jar-sign.diff
2nd version of the patch.
This adds:
- make sure we don't hang if jarsigner asks for some input
- add documentation
- fix unit test
[ http://jira.codehaus.org/browse/MAVEN-1712?page=comments#action_48589 ]
Arnaud Heritier commented on MAVEN-1712:
Finally I'm using these releases :
maven.jar.commons-beanutils=1.6.1
maven.jar.plexus-utils=1.0.3
maven.jar.wagon-file=1.0-alpha-4
> U
1 - 100 of 151 matches
Mail list logo
