+1.
Emmanuel
John Casey a écrit :
Hi,
I think it's time to release Maven 2.0.3. This release will incorporate
21 resolved JIRA issues, including some critical fixes for Continuum and
users of the embedder. The full listing of fixes can be found here:
[ http://jira.codehaus.org/browse/MNG-2097?page=comments#action_59193 ]
Thomas Will commented on MNG-2097:
--
I've got a similar situation. Need to perform some work prior to 'package', but
only when 'package' is to be executed after.
A prepare-package phase
[ http://jira.codehaus.org/browse/MDEPLOY-19?page=all ]
Allan Ramirez closed MDEPLOY-19:
Resolution: Fixed
Fixed in SVN. Thanks Jerome
Ability to deploy-file as classifier
Key: MDEPLOY-19
[ http://jira.codehaus.org/browse/MRM-13?page=all ]
Edwin Punzalan closed MRM-13:
-
Resolution: Fixed
utilise repository relocation information during conversion of an artifact
--
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060222.081501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060222.081501.txt
-
To unsubscribe,
[
http://jira.codehaus.org/browse/MAVENUPLOAD-751?page=comments#action_59198 ]
Michael Böckling commented on MAVENUPLOAD-751:
--
Doh!
At least I know now where to look... ;-)
EasyMock 1.2 for Java 1.3 and 1.5
Sorry emmanuel, I was talking about maven 1.1 beta 3 ;-)
Arnaud
On 2/22/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
beta3 won't exist, it will be 1.0 final next week
Emmanuel
Arnaud HERITIER a écrit :
+3
But we'll make a new scm release before the beta3
Arnaud
On 2/21/06,
[ http://jira.codehaus.org/browse/MRM-14?page=comments#action_59199 ]
Edwin Punzalan commented on MRM-14:
---
I think the original should be retained because there are so many possibilities
on how this can be happening.
Then probably add a user triggered
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060222.083000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060222.083000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
+ 1 for me
John Casey wrote:
Hi,
I think it's time to release Maven 2.0.3. This release will
incorporate 21 resolved JIRA issues, including some critical fixes for
Continuum and users of the embedder. The full listing of fixes can be
found here:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060222.090002.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060222.090002.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I just used my first debug breakpoint in maven 2 to fix the
jasperreports plugin:
export MAVEN_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
mvn phase-on-my-project
Still, this is a bit unhandy and it took me quite a while to find
+1
On 2/22/06, John Casey [EMAIL PROTECTED] wrote:
Hi,
I think it's time to release Maven 2.0.3. This release will incorporate
21 resolved JIRA issues, including some critical fixes for Continuum and
users of the embedder. The full listing of fixes can be found here:
On Wed, 22 Feb 2006, Brett Porter wrote:
I personally think a separate jira list allows for the most flexibility.
The same for continuum builds, which sometimes really spam the dev
list.
I think the dev list should be exclusively used by human posters
writing real email, discussing development.
[ http://jira.codehaus.org/browse/MNG-2089?page=comments#action_59207 ]
Juraj Burian commented on MNG-2089:
---
Thank you for hint mr. Trygve.
I didn't know about this plugin.
differences:
Our plugin uses different phases namely:
in compile goal we use
+1 for a jira specific list
For consistency's sake :) A list for each topic. You choose the information
you need.
+0 for subscribing to filters from JIRA
Why not, but we still need a way to get the issues as soon as they arrive,
and not only once a day.
+0 for RSS from JIRA filters
There again,
On Wed, 22 Feb 2006, Stephane Nicoll wrote:
+1,
with 2 comments:
1) no earth shaking fixes.. why not wait a bit longer?
2) it might be nice if 2.0.3 included these:
http://jira.codehaus.org/browse/MNG-1317 (mvn.bat doesn't work on win2k/xp)
(and possibly this one:
+1
Arnaud
On 2/22/06, Kenney Westerhof [EMAIL PROTECTED] wrote:
On Wed, 22 Feb 2006, Stephane Nicoll wrote:
+1,
with 2 comments:
1) no earth shaking fixes.. why not wait a bit longer?
2) it might be nice if 2.0.3 included these:
http://jira.codehaus.org/browse/MNG-1317 (mvn.bat
Maven2 Eclipse plugin does not use setings.xml
--
Key: MNGECLIPSE-82
URL: http://jira.codehaus.org/browse/MNGECLIPSE-82
Project: Maven 2.x Extension for Eclipse
Type: Bug
Components: Maven Launcher
Versions: 0.0.5
Invalid Link in the build emails
Key: CONTINUUM-599
URL: http://jira.codehaus.org/browse/CONTINUUM-599
Project: Continuum
Type: Bug
Reporter: clojinted
Hello,
I changed Continuum to run on port instead of port 8080. The
+1
Vincent
2006/2/21, John Casey [EMAIL PROTECTED]:
Hi,
I think it's time to release Maven 2.0.3. This release will incorporate
21 resolved JIRA issues, including some critical fixes for Continuum and
users of the embedder. The full listing of fixes can be found here:
I think that the next release should be in March (according plugin statuses).
Cheers,
Vincent
2006/2/21, Prasad Kashyap [EMAIL PROTECTED]:
Sorry Brett. Will keep that in mind in the future.
Issue 2 is not actually a issue. It was a user-error.
Vincent, as for the site:stage goal, do you
Geoffrey,
I like it! I prefer more --jdpa rather than --jpwd (Think about
geronimo or tomcat)
What do others think?
Vincent
2006/2/22, Geoffrey De Smet [EMAIL PROTECTED]:
I just used my first debug breakpoint in maven 2 to fix the
jasperreports plugin:
export MAVEN_OPTS=-Xdebug -Xnoagent
Agreed with Yann and John
Cheers,
Vincent
2006/2/22, Yann Le Du [EMAIL PROTECTED]:
+1 for a jira specific list
For consistency's sake :) A list for each topic. You choose the information
you need.
+0 for subscribing to filters from JIRA
Why not, but we still need a way to get the issues
[ http://jira.codehaus.org/browse/MECLIPSE-3?page=comments#action_59217 ]
Olivier Lamy commented on MECLIPSE-3:
-
I have a probably related trouble.
My root pom contains modules :
- accommons-tools (version 2.4-SNAPSHOT)
- accommons-prefs (version
I usually don't add my 2 cents to this, but I do hope that maven-2.0.3
includes the fix for WAGONSSH-36 (not MNG, I know, but since it comes
bundled...). For CI, this is certainly a blocker!
Regards,
Michael
On Wed, 22 Feb 2006, Stephane Nicoll wrote:
+1,
with 2 comments:
1) no earth
+1!
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 22, 2006 7:49 AM
To: Maven Developers List
Subject: Re: Debugging maven with breakpoints feed-back: --jdwp + docs
Geoffrey,
I like it! I prefer more --jdpa rather than --jpwd (Think about
+1 for a separate list for flexibility.
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 22, 2006 7:51 AM
To: Maven Developers List
Subject: Re: sending JIRA mail to commits@maven.apache.org
Agreed with Yann and John
Cheers,
Vincent
Hello everyone
I tried to use JarSignMojo from maven-jar-plugin trunk but with no success.
Out of the box it's not useable.
1) If I set verify to true the following code is done:
if ( verify )
{
JarSignVerifyMojo verify = new JarSignVerifyMojo();
[ http://jira.codehaus.org/browse/MJAR-31?page=all ]
Jerome Lacoste moved MOJO-295 to MJAR-31:
-
Component: (was: sandbox)
Complexity: (was: Intermediate)
Key: MJAR-31 (was: MOJO-295)
Project: Maven 2.x Jar Plugin
transitive dependency: test stronger than provided
--
Key: MNG-2101
URL: http://jira.codehaus.org/browse/MNG-2101
Project: Maven 2
Type: Bug
Versions: 2.0.2
Environment: Maven 2.0.2
Reporter: Frank
For now how do I specify in my pom to pick up the 2.0-SNAPSHOT ?
I have explicitly specified the 2.0-SNAPSHOT as the version in the
dependecyManagement/ and in
plugin
artifactIdmaven-site-plugin/artifactId
version2.0-SNAPSHOT/version
..
...
dependencies
parent with multi-type mojo children does not build ant mojo
Key: MNG-2102
URL: http://jira.codehaus.org/browse/MNG-2102
Project: Maven 2
Type: Bug
Components: Plugin Creation Tools
Versions:
Inheritance of plugin overrides that of execution
-
Key: MNG-2103
URL: http://jira.codehaus.org/browse/MNG-2103
Project: Maven 2
Type: Bug
Reporter: Prasad Kashyap
Attachments: test-inheritance.zip
The
[ http://jira.codehaus.org/browse/CONTINUUM-599?page=all ]
Emmanuel Venisse closed CONTINUUM-599:
--
Resolution: Won't Fix
You must configure it in configuration page
Invalid Link in the build emails
[ http://jira.codehaus.org/browse/MNG-2103?page=comments#action_59235 ]
Yann Le Du commented on MNG-2103:
-
Hmm... In this case, I would understand the plugininheritedfalse as
don't inherit whatever is in plugin . So, in modules, executions is not
[ http://jira.codehaus.org/browse/CONTINUUM-599?page=comments#action_59236
]
clojinted commented on CONTINUUM-599:
-
Thank you very much.
Invalid Link in the build emails
Key: CONTINUUM-599
URL:
[ http://jira.codehaus.org/browse/MNGECLIPSE-82?page=all ]
Eugene Kuleshov closed MNGECLIPSE-82:
-
Resolution: Duplicate
Maven2 Eclipse plugin does not use setings.xml
--
Key:
[ http://jira.codehaus.org/browse/MNGECLIPSE-82?page=comments#action_59237
]
Emmanuel Venisse commented on MNGECLIPSE-82:
It will be fix when eclipse plugin will use the new maven embedder (2.0.3)
Maven2 Eclipse plugin does not use setings.xml
What is your version? If it's a snapshot, specify the build number.
Emmanuel
Stramel, Jay a écrit :
I get the following error when I attempt to add a goal to any project. I
can get to the Add Build Definition screen and enter the values I want,
but the following error occurs every time I hit
[ http://jira.codehaus.org/browse/WAGONSSH-36?page=all ]
John Casey reassigned WAGONSSH-36:
--
Assign To: John Casey
SSH transport hangs on large transfers
--
Key: WAGONSSH-36
URL:
[ http://jira.codehaus.org/browse/MNGECLIPSE-82?page=comments#action_59239
]
Eugene Kuleshov commented on MNGECLIPSE-82:
---
Emmanuel, is 2.0.3 embedder already released?
Maven2 Eclipse plugin does not use setings.xml
I don't have a windows box on which to test #1, but I'll give #2 a run
and see what I can do.
-john
Kenney Westerhof wrote:
On Wed, 22 Feb 2006, Stephane Nicoll wrote:
+1,
with 2 comments:
1) no earth shaking fixes.. why not wait a bit longer?
2) it might be nice if 2.0.3 included these:
+1
On 2/21/06, John Casey [EMAIL PROTECTED] wrote:
Hi,
I think it's time to release Maven 2.0.3. This release will incorporate
21 resolved JIRA issues, including some critical fixes for Continuum and
users of the embedder. The full listing of fixes can be found here:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060222.173001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060222.173001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Arnaud HERITIER wrote:
+1 for another list [EMAIL PROTECTED]
+0 to keep the existing configuration
-1 to receive the issues on commits@maven.apache.org
Arnaud
I agree with Arnaud.
--
Dennis Lundberg
On 2/22/06, Geoffrey De Smet [EMAIL PROTECTED] wrote:
+1 (if I am allowed to vote :)
To
[ http://jira.codehaus.org/browse/MNGECLIPSE-82?page=comments#action_59240
]
Emmanuel Venisse commented on MNGECLIPSE-82:
Eugene, not yet.
I think Jason will release it just after the release of maven 2.0.3 that will
be release shortly.
Add Configure Mojo to maven-jboss-plugin
Key: MPJBOSS-25
URL: http://jira.codehaus.org/browse/MPJBOSS-25
Project: maven-jboss-plugin
Type: Improvement
Reporter: Jeff Smith
Attachments: patch.txt
Add the ability to
I can test it on windows XP,but actual mvn.bat works fine on it. I don't know
for Win2000
Emmanuel
John Casey a écrit :
I don't have a windows box on which to test #1, but I'll give #2 a run
and see what I can do.
-john
Kenney Westerhof wrote:
On Wed, 22 Feb 2006, Stephane Nicoll wrote:
[ http://jira.codehaus.org/browse/MNG-553?page=comments#action_59243 ]
Thomas Van de Velde commented on MNG-553:
-
Same here. This a major security issue and blocks wide adoption of Maven in
our organization. A minor priority seems completely
[ http://jira.codehaus.org/browse/MPXDOC-91?page=all ]
Lukas Theussl closed MPXDOC-91:
---
Resolution: Won't Fix
It is now possible to use your own custom themes, see the maven.xdoc.theme.file
and maven.xdoc.theme.url properties.
bundled css files
Hi,
I worte an article about Maven for Dr. Dobbs. I would like to get some
feedback. The article is a text file with several code listings and tables.
Please let me know if I should just attach an archive of everything or
separate files or just mail it directly to interested parties.
Thanks, Gigi
Kenney Westerhof wrote:
On Wed, 22 Feb 2006, Brett Porter wrote:
I personally think a separate jira list allows for the most flexibility.
The same for continuum builds, which sometimes really spam the dev
list.
I think the dev list should be exclusively used by human posters
writing real email,
I am interested. Everything here is archived and made public so I
guess you can just publish it somewhere and communicate the URL to
this list.
Thanks,
Stéphane
On 2/22/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,
I worte an article about Maven for Dr. Dobbs. I would like to get some
[ http://jira.codehaus.org/browse/MNG-2103?page=comments#action_59250 ]
Prasad Kashyap commented on MNG-2103:
-
I see what you mean. That makes sense only if the plugininherited is set to
false.
Now flip the inheritance boolean at the plugin level to
I have a very simple pom with the reporting section set to
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-project-info-reports-plugin/artifactId
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
Remove one of these txo index file
Emmanuel
Prasad Kashyap a écrit :
I have a very simple pom with the reporting section set to
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-project-info-reports-plugin/artifactId
/plugin
Add a servlet for downloading files project as text (without html decoration)
-
Key: CONTINUUM-601
URL: http://jira.codehaus.org/browse/CONTINUUM-601
Project: Continuum
Type: New Feature
I had tried that. It throws a NPE.
[INFO] Generate Plugin documentation report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[EMAIL PROTECTED] wrote:
Hi,
I worte an article about Maven for Dr. Dobbs. I would like to get some
feedback. The article is a text file with several code listings and tables.
Please let me know if I should just attach an archive of everything or
separate files or just mail it directly to
Distribution:
http://maven.zones.apache.org/~continuum/builds/branches/continuum-1.0.x/continuum-20060222.203001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060222.203001.txt
FileSet type should be available to all user created plugins
Key: MNG-2104
URL: http://jira.codehaus.org/browse/MNG-2104
Project: Maven 2
Type: New Feature
Components: Plugins and Lifecycle
Stéphane, it seems that there was a problem of encoding when you tagged the
source plugin
Which maven release did you use ? With which plugins ?
I never had this problem even when I worked on a french OS :-(
Arnaud
On 2/22/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: snicoll
Date:
What is the character in the tag name after MAVEN ?
- Brett
[EMAIL PROTECTED] wrote:
Author: snicoll
Date: Sun Feb 19 00:53:42 2006
New Revision: 378861
URL: http://svn.apache.org/viewcvs?rev=378861view=rev
Log:
[maven-scm] copy for tag MAVEN�_SOURCE_1_0
Added:
The dependencies section isn't needed.
If you've set 2.0-SNAPSHOT, it will download and use that version.
http://maven.apache.org/guides/development/guide-testing-development-plugins.html
- Brett
Prasad Kashyap wrote:
For now how do I specify in my pom to pick up the 2.0-SNAPSHOT ?
I have
I've thought about this in the past, but have always opted to go for
setting MAVEN_OPTS (which I have in a separate little script).
I'd be fine with adding this argument, but parsing the command line
arguments (especially in the .bat file) can be a bit of a pain.
Would someone like to put it in
This just means you got further.
A nulle pointer exception is a bug any way you look at it - normally you
should file it in JIRA. However, I think this was just fixed yesterday -
its because you have no mojos to document yet.
- Brett
Prasad Kashyap wrote:
I had tried that. It throws a NPE.
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060222.211501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060222.211501.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MNG-2104?page=all ]
Brett Porter closed MNG-2104:
-
Assign To: Brett Porter
Resolution: Won't Fix
this isn't necessary. If you declare:
org.apache.maven.model.FileSet fileSet;
You can use it in your plugin. It
[ http://jira.codehaus.org/browse/MNG-553?page=comments#action_59253 ]
Brett Porter commented on MNG-553:
--
how do you work around this in the build systems of those areas that have not
adopted Maven?
Secure Storage of Server Passwords
[ http://jira.codehaus.org/browse/WAGON-37?page=all ]
Brett Porter closed WAGON-37:
-
Assign To: Brett Porter
Resolution: Duplicate
wagon based site deploy hangs on large files
Key: WAGON-37
[ http://jira.codehaus.org/browse/MNG-2101?page=all ]
Brett Porter closed MNG-2101:
-
Assign To: Brett Porter
Resolution: Duplicate
transitive dependency: test stronger than provided
--
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060222.220001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060222.220001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
+1
I tested it with our full product build and it appears to work well. I
would like to see WAGONSSH-36 fixed if possible - the fix is so trivial
I don't know why it hasn't been integrated already.
I'm also looking forward to the upcoming site and cobertura releases!
-Original Message-
[ http://jira.codehaus.org/browse/MNG-553?page=comments#action_59255 ]
J. Michael McGarr commented on MNG-553:
---
Currently, our oganization's work around involves the use of public/private key
authentication. This requires, however, that the maven
[ http://jira.codehaus.org/browse/MNG-553?page=comments#action_59256 ]
Emmanuel Venisse commented on MNG-553:
--
If it's an internal repository, why do you need login/password?
Secure Storage of Server Passwords
--
[ http://jira.codehaus.org/browse/MNG-553?page=comments#action_59258 ]
Brett Porter commented on MNG-553:
--
Thanks. Specifically I was addressing Thomas' comment blocks wide adoption of
Maven. Presumably the solution they already have in place handles this
[ http://jira.codehaus.org/browse/MPJAR-47?page=all ]
Lukas Theussl closed MPJAR-47:
--
Resolution: Fixed
Fix Version: 1.8
Documentation mentions nonexistent properties
-
Key: MPJAR-47
[ http://jira.codehaus.org/browse/MPJAR-32?page=all ]
Lukas Theussl closed MPJAR-32:
--
Resolution: Won't Fix
This functionality is now provided by the maven-source-plugin.
Add the ability to include the source code in the jar
Images used by the changes report aren't copied.
Key: MPCHANGES-29
URL: http://jira.codehaus.org/browse/MPCHANGES-29
Project: maven-changes-plugin
Type: Bug
Versions: 1.6
Reporter: Arnaud Heritier
+1 from me, but I also would like to see that WAGONSSH-36 fixed in this release
fabrizio
On 2/21/06, John Casey [EMAIL PROTECTED] wrote:
Hi,
I think it's time to release Maven 2.0.3. This release will incorporate
21 resolved JIRA issues, including some critical fixes for Continuum and
[ http://jira.codehaus.org/browse/MPCHANGES-29?page=all ]
Arnaud Heritier closed MPCHANGES-29:
Resolution: Fixed
Fixed.
Images used by the changes report aren't copied.
Key:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060223.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060223.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MPJAR-3?page=all ]
Lukas Theussl closed MPJAR-3:
-
Resolution: Fixed
Patch was apparently applied a long time ago, only the docs were forgotten ...
Add ability to include user specified Manifest entries.
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060223.003001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060223.003001.txt
-
To unsubscribe,
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060223.010001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060223.010001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060223.011501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060223.011501.txt
-
To unsubscribe,
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (21 issues)
Subscriber: mavendevlist
Key Summary
MEV-296 Activemq-core (and other activemq projects) 3.2.1 have unexpanded
variables
http://jira.codehaus.org/browse/MEV-296
MEV-340 junit-addons
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (7 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-742Please upload maven-qalab-plugin
http://jira.codehaus.org/browse/MAVENUPLOAD-742
MAVENUPLOAD-749Please upload DWR-1.1-rc1 to the global Maven
[ http://jira.codehaus.org/browse/MRM-38?page=all ]
Edwin Punzalan closed MRM-38:
-
Resolution: Fixed
Patch Applied. Thanks.
add a background task scheduler
---
Key: MRM-38
URL:
[ http://jira.codehaus.org/browse/MRM-38?page=all ]
Edwin Punzalan reopened MRM-38:
---
Sorry, patched the wrong file.
add a background task scheduler
---
Key: MRM-38
URL:
[ http://jira.codehaus.org/browse/MRM-38?page=all ]
Edwin Punzalan closed MRM-38:
-
Resolution: Fixed
Correct patch applied this time. ^_^
add a background task scheduler
---
Key: MRM-38
URL:
Distribution:
http://maven.zones.apache.org/~continuum/builds/branches/continuum-1.0.x/continuum-20060223.020001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060223.020001.txt
[ http://jira.codehaus.org/browse/MEV-301?page=comments#action_59279 ]
Drew Farris commented on MEV-301:
-
Can someone set up a relocation from xerces 2.2.1 to xercesImpl 2.2.1? The
current pom for xerces-2.2.1 does not relocate to xercesImpl-2.2.1 and thus
PerforceChangeLogCommand needs to use the same clientspec as the update command
---
Key: SCM-165
URL: http://jira.codehaus.org/browse/SCM-165
Project: Maven SCM
Type: Bug
Components:
[ http://jira.codehaus.org/browse/MEV-301?page=comments#action_59281 ]
Drew Farris commented on MEV-301:
-
For what's it's worth, the pom I'm using locally for xerces-2.2.1 in
repository/xerces/xerces/2.2.1/ is
project
modelVersion4.0.0/modelVersion
assembly goal is executed twice
---
Key: MASSEMBLY-72
URL: http://jira.codehaus.org/browse/MASSEMBLY-72
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.0
Reporter: Dan Diephouse
Fix For: 2.0.1
My assembly goal
[ http://jira.codehaus.org/browse/MASSEMBLY-72?page=comments#action_59283 ]
Dan Tran commented on MASSEMBLY-72:
---
this is a duplicate of MASSEMBLY-37.
The work around is to use attached goal instead ( in svn)
assembly goal is executed twice
[ http://jira.codehaus.org/browse/MRM-70?page=all ]
John Tolentino closed MRM-70:
-
Resolution: Duplicate
Code already exists (see MRM-74).
Browse by Group/Artifact/Version
Key: MRM-70
URL:
[ http://jira.codehaus.org/browse/MRM-74?page=all ]
Edwin Punzalan closed MRM-74:
-
Resolution: Fixed
Patch applied. Thanks.
Browse web user interface
-
Key: MRM-74
URL:
1 - 100 of 115 matches
Mail list logo