My vote: create a new project for every m2 plugin.
That said, I think it would be great to have a separate machine for that.
Stéphane
On 11/15/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> I think we should vote to solve this asap, I believe these are the
> options:
>
> [ ] create a new proje
My vote
> [x] create a new project for new m2 plugins, reuse m1 projects adding
> a new version
> [ ] create a new project for every m2 plugin
> [ ] keep it as it's now
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: mercredi 16 novembre 2005 01:04
> To: Maven Developers List
> Subject: Re: JIRA projects for m2 plugins?
>
> On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote:
> > I think we should vote to solve this asap
Brett,
There was a bug in the deploy code that has been fixed by John. The
${version} expression in deps wasn't getting resolved at deploy time.
Thanks
-Vincent
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 16 novembre 2005 01:08
> To: Maven Develop
Thanks John for the feedback.
I still have trouble understanding what's the difference between a deploy
and a release and I would think we'd need to merge both concept into one in
the future.
If you think about it, the result of both actions is the same from a user
point of view. The only differe
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051116.06.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051116.06.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1560?page=all ]
Edwin Punzalan updated MNG-1560:
Fix Version: (was: 2.0)
2.0.1
> Guide to accessing repository with https client authentication
> -
ons Chain pom
> --
>
> Key: MEV-197
> URL: http://jira.codehaus.org/browse/MEV-197
> Project: Maven Evangelism
> Type: Improvement
> Components: Dependencies
> Reporter: Wendy Smoak
> Assignee: Edwin Punzalan
Evangelism
> Type: Improvement
> Components: Dependencies
> Reporter: Wendy Smoak
> Assignee: Edwin Punzalan
> Attachments: chain-1.0-20051115.diff
>
>
> Making some dependencies optional, changing to standard groupId for Sun jars
--
This message is automatic
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051116.041500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051116.041500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051116.034500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051116.034500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051116.033000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051116.033000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1585?page=comments#action_51078 ]
John Casey commented on MNG-1585:
-
is this related to MNG-1501?
> debug logging from wagon not shown in debug mode
>
>
> Key: MN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think Emmanuel was able to get around this issue using
READ_UNCOMMITTED in the jpox config properties, but it definitely needs
some testing.
- -j
Brett Porter wrote:
| Hi,
|
| I found that adding plexus' root pom.xml on a clean continuum install
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You're right, as usual. I've rolled back this change for the assembly
plugin, and avoided using the 2.0.1 API in the assembly plugin patches I
applied today, in order to release the new version of the assembly
plugin ahead of the 2.0.1 release.
Brett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
deployment doesn't guarantee reproducibility. I already discussed this
with you on IRC, but I'm replicating my answer here to keep the list up
to date.
The only time you have strong requirements for reproducibility in builds
is at release time, when
On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote:
> I think we should vote to solve this asap, I believe these are the options:
>
> [ ] create a new project for new m2 plugins, reuse m1 projects adding
> a new version
> [ ] create a new project for every m2 plugin
+1
> [ ] keep it as it's
[ http://jira.codehaus.org/browse/MEV-3?page=all ]
Edwin Punzalan closed MEV-3:
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours to reach central repo.
> Broken dependencies for nanocontainer
> -
>
> K
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/15-Nov-2005_08.33.44/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
[ http://jira.codehaus.org/browse/MEV-126?page=all ]
Edwin Punzalan closed MEV-126:
--
Resolution: Fixed
I'm closing this issue as the poms from ibiblio are already updated.
> poms for som emissing sun xml API + javamail 1.3.3
>
jabber doesn't work with talk.google.com
Key: CONTINUUM-451
URL: http://jira.codehaus.org/browse/CONTINUUM-451
Project: Continuum
Type: Task
Reporter: Brett Porter
Fix For: 1.1
from what I can tell, talk.google.com
debug logging from wagon not shown in debug mode
Key: MNG-1585
URL: http://jira.codehaus.org/browse/MNG-1585
Project: Maven 2
Type: Bug
Components: maven-artifact
Reporter: Brett Porter
Fix For: 2.0.1
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051116.001500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051116.001500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051116.00.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051116.00.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
It need sto be fixed but is a low priority as it only affects biuld the
plugin plugin after having built the plugin plugin with the bootstrap
which is very specific to our environment.
- Brett
Vincent Massol wrote:
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
You have to have that locally, I presume it was a failed deploy attempt
in which case we need to improve the point at which the data is written.
Look in your local repository for where the value comes from.
- Brett
Vincent Massol wrote:
Hi,
I have uploaded the cargo m2 plugin to a private re
[ http://jira.codehaus.org/browse/MEV-190?page=comments#action_51053 ]
Mark Hobson commented on MEV-190:
-
You mean on ibiblio? It's here:
http://www.ibiblio.org/maven2/slide/slide-webdavlib/2.1/
Or if you mean the project, 2.1 is here:
http://jakarta.apac
[ http://jira.codehaus.org/browse/MEV-190?page=comments#action_51052 ]
Edwin Punzalan commented on MEV-190:
Can't seem to find 2.1 version. Are you referring to 2.1M1 ?
> Missing dependencies for slide-webdavlib
> ---
[ http://jira.codehaus.org/browse/MEV-194?page=all ]
Edwin Punzalan closed MEV-194:
--
Resolution: Fixed
Patch applied. Thanks.
NOTE: May take up to 4hours for the fix to reach central repo.
> cactus missing dependencies
> ---
>
[ http://jira.codehaus.org/browse/MEV-195?page=all ]
Edwin Punzalan closed MEV-195:
--
Resolution: Fixed
Applied. Thanks.
NOTE: May take up to 4hours for the fix to reach central repo.
> securityfilter missing dependencies
> ---
add google analytics code to website
Key: MNG-1584
URL: http://jira.codehaus.org/browse/MNG-1584
Project: Maven 2
Type: Task
Components: documentation - general
Reporter: Brett Porter
Assigned to: Brett Porter
I've cre
Give pointers to integration tests in the docs
--
Key: MNG-1583
URL: http://jira.codehaus.org/browse/MNG-1583
Project: Maven 2
Type: Improvement
Components: documentation - guides
Versions: 2.0
Reporter: Car
Add how to convert pregoals and postgoals to lifecycle to the m1-m2 guide
-
Key: MNG-1582
URL: http://jira.codehaus.org/browse/MNG-1582
Project: Maven 2
Type: Improvement
Components: documentat
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.224501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Allow to configure to which files should use CRLF line endings in Zip archives
--
Key: MPDIST-28
URL: http://jira.codehaus.org/browse/MPDIST-28
Project: maven-dist-plugin
Type: Improvement
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.223001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Publish the build results to a different machine
Key: CONTINUUM-450
URL: http://jira.codehaus.org/browse/CONTINUUM-450
Project: Continuum
Type: New Feature
Versions: 1.0
Reporter: Carlos Sanchez
The build
Make sure that there aren't two jars with the same artifactId and version
-
Key: MNG-1581
URL: http://jira.codehaus.org/browse/MNG-1581
Project: Maven 2
Type: Improvement
Components: maven-war-
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.221500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MEV-207?page=all ]
Carlos Sanchez closed MEV-207:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Hibernate 3.1rc2 missing jar
>
>
> Key: MEV-207
> URL: http://jira.co
title bar says "Jabber" when creating an MSN notifier
-
Key: CONTINUUM-449
URL: http://jira.codehaus.org/browse/CONTINUUM-449
Project: Continuum
Type: Bug
Reporter: Brett Porter
Priority: Trivial
Fix Fo
Unable to enable http-wagon instead of http-wagon-lightweight using
---
Key: MNG-1580
URL: http://jira.codehaus.org/browse/MNG-1580
Project: Maven 2
Type: Bug
Versions: 2.0
Environm
imrpvoe performance of "show projects" page
---
Key: CONTINUUM-448
URL: http://jira.codehaus.org/browse/CONTINUUM-448
Project: Continuum
Type: Improvement
Reporter: Brett Porter
Fix For: 1.1
this seems to reload all
[ http://jira.codehaus.org/browse/MEV-28?page=all ]
Carlos Sanchez closed MEV-28:
-
Assign To: Carlos Sanchez
Resolution: Fixed
Fixed in svn repo
> bogus dependencies in commons-configuration
> ---
>
>
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.214500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.213000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.211501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.210001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hibernate 3.1rc2 missing jar
Key: MEV-207
URL: http://jira.codehaus.org/browse/MEV-207
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: mike perham
It looks like the jar didn't make the move with the POM wh
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.204500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.203001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I think we should vote to solve this asap, I believe these are the options:
[ ] create a new project for new m2 plugins, reuse m1 projects adding
a new version
[ ] create a new project for every m2 plugin
[ ] keep it as it's now
On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
> So what's t
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.20.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNG-1462?page=all ]
John Casey closed MNG-1462:
---
Resolution: Fixed
applied. Thanks, Jerome.
> assembly:assembly forks a lifecycle and cannot be used in a reactor
> environment. Need a new mojo suitable for this environm
URL: http://jira.codehaus.org/browse/MEV-197
> Project: Maven Evangelism
> Type: Improvement
> Components: Dependencies
> Reporter: Wendy Smoak
> Attachments: chain-1.0-20051115.diff
>
>
> Making some dependencies optional, changing to standard groupId for Sun
URL: http://jira.codehaus.org/browse/MEV-197
> Project: Maven Evangelism
> Type: Improvement
> Components: Dependencies
> Reporter: Wendy Smoak
> Attachments: chain-1.0-20051115.diff
>
>
> Making some dependencies optional, changing to standard groupId for Sun
[ http://jira.codehaus.org/browse/MEV-157?page=comments#action_51036 ]
Carlos Sanchez commented on MEV-157:
Ok, I see, I thought these were relocated.
Let's create reloaction poms for these two
> Invalid deps in the dumbster pom
> -
[ http://jira.codehaus.org/browse/MNG-1311?page=all ]
John Casey updated MNG-1311:
Assign To: John Casey
Component: (was: maven-assembly-plugin)
maven-core
Complexity: Expert (was: Intermediate)
[ http://jira.codehaus.org/browse/MNG-1274?page=all ]
John Casey updated MNG-1274:
Description:
Trying to use the assembly plugin to repackage a war, I got the exception
below. The functionality was needed to implemented multi-webstart application
d
[ http://jira.codehaus.org/browse/MNG-1274?page=all ]
John Casey closed MNG-1274:
---
Resolution: Fixed
Applied. Thanks, Jerome.
> maven-assembly doesn't support war format
> -
>
> Key: MNG-1274
> UR
Damn I just found my answer in the readme file. I had forgotten to read it.
Sorry!
On 11/15/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
>
> Hi, I know how to define my proxy settings when maven is already built,
> but how can I define them before building maven from the source so all the
> pl
Hi, I know how to define my proxy settings when maven is already built, but
how can I define them before building maven from the source so all the
plugins it needs can be downloaded?
Thank!
--
Alexandre Poitras
Québec, Canada
[ http://jira.codehaus.org/browse/MNG-1509?page=comments#action_51028 ]
Bernd Bohmann commented on MNG-1509:
patch included
> Profile activation by os doesn't work
> -
>
> Key: MNG-1509
> URL: http://
[ http://jira.codehaus.org/browse/MNG-1469?page=comments#action_51027 ]
Bernd Bohmann commented on MNG-1469:
patch included
> pmd has problems with package-info.java.
>
>
> Key: MNG-1469
> URL: h
[ http://jira.codehaus.org/browse/MNG-1455?page=comments#action_51026 ]
Bernd Bohmann commented on MNG-1455:
patch included
> Possible NPE in DefaultArtifactResolver
> ---
>
> Key: MNG-1455
> URL: htt
[ http://jira.codehaus.org/browse/MPXDOC-30?page=all ]
Lukas Theussl closed MPXDOC-30:
---
Resolution: Won't Fix
Fix Version: 1.10
> Not very informative error message on xdoc template error
>
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051115.183000.txt
[ http://jira.codehaus.org/browse/MPXDOC-21?page=all ]
Lukas Theussl closed MPXDOC-21:
---
Resolution: Duplicate
Superceded by MPXDOC-183
> Customization template
> --
>
> Key: MPXDOC-21
> URL: http://jira.codehaus.
[ http://jira.codehaus.org/browse/MPXDOC-15?page=all ]
Lukas Theussl closed MPXDOC-15:
---
Resolution: Won't Fix
Fix Version: 1.10
These errors are reported by the xdoc:validate goal.
> misplaced text in xdocs should be reported
> -
release:perform could update the date attribute in the changes.xml
---
Key: MPRELEASE-14
URL: http://jira.codehaus.org/browse/MPRELEASE-14
Project: maven-release-plugin
Type: New Feature
Reporter: O
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051115.173000.txt
[ http://jira.codehaus.org/browse/MNG-1579?page=all ]
Lukas Theussl updated MNG-1579:
---
Component: maven-checkstyle-plugin
> Exception: Can't find resource bundle for current bundle
>
>
> Key
[ http://jira.codehaus.org/browse/MNG-1579?page=all ]
Lukas Theussl moved MPCHECKSTYLE-44 to MNG-1579:
Version: (was: 2.0)
2.0
Complexity: Intermediate
Workflow: Maven (was: jira)
Key: MNG-1579
[ http://jira.codehaus.org/browse/MPXDOC-183?page=all ]
Lukas Theussl moved MAVEN-1725 to MPXDOC-183:
-
Workflow: jira (was: Maven)
Key: MPXDOC-183 (was: MAVEN-1725)
Project: maven-xdoc-plugin (was: Maven)
> Enable User Templa
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051115.171501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.171501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051115.17.txt
Thanks John,
When I deploy now the resolved version is 0.7-SNASPHOT and not the
timestamped version.
It may work but that means that builds will not be reproducible, because the
correct dependency version will be chosen at runtime according to the
available snapshots, right?
Thanks
-Vincent
>
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051115.163000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.163000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Remove Project Exception
Key: CONTINUUM-447
URL: http://jira.codehaus.org/browse/CONTINUUM-447
Project: Continuum
Type: Bug
Versions: 1.0.1
Environment: Windows 2000 sp4 OS, 1GB of RAM, 1.70 GHz CPU
Reporter: Michael Fiedler
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: mardi 15 novembre 2005 17:31
> To: dev@maven.apache.org
> Subject: Re: svn commit: r344377 - /maven/components/trunk/m2-bootstrap-
> all.bat
>
> It will be better to find and fix the pb in maven instead of th
[ http://jira.codehaus.org/browse/MAVEN-1725?page=all ]
Niall Pemberton updated MAVEN-1725:
---
Attachment: xdoc-user-template2.patch
Woops, sorry missed a bit of the change when cut & pasting - attaching new
patch version
> Enable User Templates in XDO
Enable User Templates in XDOC plugin
Key: MAVEN-1725
URL: http://jira.codehaus.org/browse/MAVEN-1725
Project: Maven
Type: New Feature
Reporter: Niall Pemberton
Priority: Minor
Attachments: xdoc-user-template.patch
It wou
Exception: Can't find resource bundle for current bundle
Key: MPCHECKSTYLE-44
URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-44
Project: maven-checkstyle-plugin
Type: Bug
Versions: 2.0
Environment:
It will be better to find and fix the pb in maven instead of this bootstrap
script
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: vmassol
Date: Tue Nov 15 07:37:46 2005
New Revision: 344377
URL: http://svn.apache.org/viewcvs?rev=344377&view=rev
Log:
Fixed bootstrap on windows. For some reason t
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051115.154501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.154501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MNG-1574?page=all ]
Olivier Lamy closed MNG-1574:
-
Resolution: Fixed
Move to MEV.
> trouble with invalid pom (failed cli site:site)
> ---
>
> Key: MNG-1574
>
mvn assembly:assembly fails if there is no target directory already present
---
Key: MNG-1578
URL: http://jira.codehaus.org/browse/MNG-1578
Project: Maven 2
Type: Bug
Reporter: Matthew Pocock
I needed to do a bit of compiling after the process-classes phase for a
couple of custom plugins...so I pulled out the interesting parts of the
compiler mojo and used that...not sure if there is a better way, but this
certainly works..
jesse
private Compiler compiler = new JavacCompiler();
p
[ http://jira.codehaus.org/browse/MNG-1353?page=comments#action_51007 ]
Vincent Massol commented on MNG-1353:
-
Brett,this would be needed for any parameter.
The goal is to move the config POJO out of the directory where the mojos are so
that they can be
Hi,
I have uploaded the cargo m2 plugin to a private repo and I'm trying to use
it from a m2 project. All the cargo artifacts that I have uploaded are
snapshots. They all have a different resolved timestamp.
However when I run the cargo m2 plugin on my m2 project m2 looks for a an
artifact (cargo
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051115.134500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.134500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
dependencyManagent does not work for transient dependencies
---
Key: MNG-1577
URL: http://jira.codehaus.org/browse/MNG-1577
Project: Maven 2
Type: Bug
Components: maven-core
Versions: 2.0
Reporte
PMD does not work on dutch locale
-
Key: MNG-1576
URL: http://jira.codehaus.org/browse/MNG-1576
Project: Maven 2
Type: Bug
Components: maven-pmd-plugin
Reporter: Wim Deblauwe
I get the following error when running mvn site wi
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.132737.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I am ready to check in the Weblogic Plugin. I think it makes sense to
create new projects for these plugins since the structure will be quite
different. This also allows us to keep maintaining the version 1.0 plugins
as well.
I woiuld prefer that we start with 2.0 for a number of reasons since I
[ http://jira.codehaus.org/browse/MEV-197?page=all ]
Wendy Smoak updated MEV-197:
Attachment: chain-1.0-20051115.diff
Apparently you can't reuse filenames, trying again. :)
> Improvements for Commons C
[ http://jira.codehaus.org/browse/MEV-197?page=all ]
Wendy Smoak updated MEV-197:
Attachment: chain-1.0.diff
Replacement diff -- this one also marks JUnit as test scope.
> Improvements for Commons Chain pom
> --
>
>
[ http://jira.codehaus.org/browse/MEV-197?page=comments#action_50987 ]
Wendy Smoak commented on MEV-197:
-
Quotes from the Commons Chain docs [0]:
"The "context" abstraction is designed to isolate command implementations from
the environment in which they ar
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051115.131500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Provide a way for a maven1 build to upload to an m2 repository
--
Key: MAVEN-1724
URL: http://jira.codehaus.org/browse/MAVEN-1724
Project: Maven
Type: New Feature
Versions: 1.1-beta-1
Reporter: S
1 - 100 of 125 matches
Mail list logo
