Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051230.11.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051230.11.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051230.153000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051230.153000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051230.16.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051231.013000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051231.02.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051231.023000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051231.03.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051231.033000.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051231.04.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051231.04.txt
mvn clean tries to download dependencies
--
Key: MCLEAN-3
URL: http://jira.codehaus.org/browse/MCLEAN-3
Project: Maven 2.x Clean Plugin
Type: Bug
Environment: 2.1-SNAPSHOT
Reporter: Vincent Massol
[ http://jira.codehaus.org/browse/MCLEAN-3?page=comments#action_54513 ]
Vincent Massol commented on MCLEAN-3:
-
Actually i have the same problem with mvn install and it's definitely due to
the extension (removing it makes the build work).
mvn clean
[ http://jira.codehaus.org/browse/MCLEAN-3?page=all ]
Vincent Massol updated MCLEAN-3:
Description:
C:\dev\cargo\branches\0.7mvn clean
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Cargo
[INFO] Cargo Build Tools
[INFO] Cargo
[ http://jira.codehaus.org/browse/MNG-1904?page=all ]
Vincent Massol moved MCLEAN-3 to MNG-1904:
--
Complexity: Intermediate
Key: MNG-1904 (was: MCLEAN-3)
Project: Maven 2 (was: Maven 2.x Clean Plugin)
cannot build and use a
[ http://jira.codehaus.org/browse/MCHECKSTYLE-10?page=comments#action_54515
]
fabrizio giustina commented on MCHECKSTYLE-10:
--
The plugin has been fixed by manually switching the context classloader (note:
checkstyle will always use the context
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051230.11.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051230.11.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051230.111501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051230.111501.txt
-
To unsubscribe,
Resource patterns should be configurable and have a better default (+patch)
---
Key: MIDEA-18
URL: http://jira.codehaus.org/browse/MIDEA-18
Project: Maven 2.x Idea Plugin
Type: Improvement
[ http://jira.codehaus.org/browse/MIDEA-18?page=all ]
Geoffrey updated MIDEA-18:
--
Attachment: MIDEA-18-maven-idea-plugin.patch
Resource patterns should be configurable and have a better default (+patch)
[
http://jira.codehaus.org/browse/MAVENUPLOAD-649?page=comments#action_54519 ]
Carlos Sanchez commented on MAVENUPLOAD-649:
Just post the pom in a MEV issue
fixed group-jfreechart-1.0.0
Key:
[ http://jira.codehaus.org/browse/MIDEA-15?page=comments#action_54520 ]
Geoffrey commented on MIDEA-15:
---
This issue is important to allow to FAST hot deployment of the exploded
directory, without making artifacts, in IntelliJ (not using maven).
To allow
On Dec 28, 2005, at 10:00 PM, Jason van Zyl wrote:
Brett Porter wrote:
-1 to generic pre/post phases. For one, there's no difference between
pre-process-classes and post-compile.
Maybe that indicates that the process-classes is really a decoration
for the compile phase. We have several
[ http://jira.codehaus.org/browse/MNG-1895?page=all ]
Carlos Sanchez updated MNG-1895:
Attachment: MNG-1895.patch
Scopes are not correctly calculated for dependencies in two dependency paths
This may sound like a bit of a stupid question
I need to use several external jar files in my app, where should I put
them in my maven project so that maven will detect them for me at
compile and run ?
Any help would be greatly appreciated, if only to point me to the
correct documentation.
[ http://jira.codehaus.org/browse/MNG-1895?page=all ]
Carlos Sanchez updated MNG-1895:
Testcase included: yes
Fix Version: (was: 2.0.3)
2.0.2
Scopes are not correctly calculated for dependencies in two dependency
Project scoped code style
-
Key: MIDEA-19
URL: http://jira.codehaus.org/browse/MIDEA-19
Project: Maven 2.x Idea Plugin
Type: New Feature
Reporter: Geoffrey
Priority: Trivial
When working on different projects with different code
[ http://jira.codehaus.org/browse/MDEPLOY-6?page=all ]
Carlos Sanchez closed MDEPLOY-6:
Assign To: Carlos Sanchez
Resolution: Duplicate
wagon-ssh or deploy plugin sometimes uses scp instead of configured pscp
sorry, but m1 or m2?
On 12/30/05, Abbs, David A [EMAIL PROTECTED] wrote:
This may sound like a bit of a stupid question
I need to use several external jar files in my app, where should I put
them in my maven project so that maven will detect them for me at
compile and run ?
Any help would
Configurable excluded directories for less synchronizing
Key: MIDEA-20
URL: http://jira.codehaus.org/browse/MIDEA-20
Project: Maven 2.x Idea Plugin
Type: Improvement
Reporter: Geoffrey
When you switch
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051230.153000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051230.153000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MCHECKSTYLE-17?page=all ]
fabrizio giustina closed MCHECKSTYLE-17:
Assign To: fabrizio giustina
Resolution: Cannot Reproduce
Fix Version: 2.0-beta-2
Skipping the report generation if a src
[ http://jira.codehaus.org/browse/MCHECKSTYLE-10?page=all ]
fabrizio giustina closed MCHECKSTYLE-10:
Assign To: fabrizio giustina
Resolution: Fixed
Tested on different projects and it seems to work properly with the latests
patches.
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051230.154500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051230.154500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MCHECKSTYLE-24?page=comments#action_54540
]
fabrizio giustina commented on MCHECKSTYLE-24:
--
This could be fixed by the classloader change for MCHECKSTYLE-10
Could you give it a try (using the version in svn)? I
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051230.16.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051230.16.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
${parentProject}\ in default site descriptor doesn't resolve
Key: MSITE-65
URL: http://jira.codehaus.org/browse/MSITE-65
Project: Maven 2.x Site Plugin
Type: Bug
Versions: 2.0-beta-5
Reporter:
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051230.163000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051230.163000.txt
[ http://jira.codehaus.org/browse/MNG-1900?page=all ]
Carlos Sanchez closed MNG-1900:
---
Assign To: Carlos Sanchez
Resolution: Fixed
Error while deploying when using scpexe protocol with non-default scp/ssh
executables
Delete remote files before uploading them to avoid permission problems
--
Key: MNG-1905
URL: http://jira.codehaus.org/browse/MNG-1905
Project: Maven 2
Type: Bug
Components: Artifacts and
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051230.164500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051230.164500.txt
-
To unsubscribe,
Please direct your question to [EMAIL PROTECTED] This list is for
development of Maven itself.
Thanks,
Brett
Abbs, David A wrote:
This may sound like a bit of a stupid question
I need to use several external jar files in my app, where should I put
them in my maven project so that maven will
[ http://jira.codehaus.org/browse/MNG-1904?page=comments#action_54546 ]
Brett Porter commented on MNG-1904:
---
yes, extensions need to be loaded up front. The problem is that you are
inheriting the extension, so the parent, and the build tools themselves,
[ http://jira.codehaus.org/browse/MCHECKSTYLE-24?page=comments#action_54547
]
Brett Porter commented on MCHECKSTYLE-24:
-
I was unable to reproduce in the first place, so I'm not sure whether being
unable to reproduce makes a difference. Try
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051230.173000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051230.173000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MNG-1904?page=all ]
Brett Porter closed MNG-1904:
-
Assign To: Brett Porter
Resolution: Won't Fix
cannot build and use a build extension in the same build run
[ http://jira.codehaus.org/browse/MNG-1545?page=comments#action_54548 ]
Arik Kfir commented on MNG-1545:
I'm not sure that would be wise - when runningin another application (e.g. an
IDE) I wouldn't want Maven to fiddle with external resources such as
We don't need to manually apply fixes to both the trunk and branch.
I know its been a bit slow due to the break, but we will do regular
branch - trunk merges.
(Unless there is some other plan - I haven't read through that dev
process doc that is being formulated yet).
- Brett
[EMAIL PROTECTED]
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: vendredi 30 décembre 2005 19:00
To: dev@maven.apache.org
Subject: Re: svn commit: r360120 - /maven/components/trunk/maven-artifact-
manager/src/main/java/org/apache/maven/artifact/manager/DefaultWagonManage
[ http://jira.codehaus.org/browse/MIDEA-15?page=all ]
Geoffrey updated MIDEA-15:
--
Attachment: MIDEA-15-maven-idea-plugin.patch
add support for war module configuration in iml
---
Key: MIDEA-15
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051230.18.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051230.18.txt
[ http://jira.codehaus.org/browse/MNG-1905?page=comments#action_54551 ]
Brett Porter commented on MNG-1905:
---
I'm not sure about this, let's discuss a little first.
Delete remote files before uploading them to avoid permission problems
[ http://jira.codehaus.org/browse/MANTRUN-33?page=all ]
Carlos Sanchez closed MANTRUN-33:
-
Resolution: Fixed
Fix Version: 1.1
Add ant property referencing plugin classpath to antrun plugin
[ http://jira.codehaus.org/browse/MSUREFIRE-20?page=all ]
Brett Porter updated MSUREFIRE-20:
--
Version: 2.1.1
Fix Version: 2.1.2
forkMode=pertest fails to call setUp
Key: MSUREFIRE-20
[ http://jira.codehaus.org/browse/MSUREFIRE-20?page=comments#action_54553 ]
Jason van Zyl commented on MSUREFIRE-20:
Matt, do you think you could integrate this into a test in the main source
tree? I've tested using your sample and it's fine now.
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051230.181500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051230.181500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MSUREFIRE-35?page=all ]
Jason van Zyl updated MSUREFIRE-35:
---
Fix Version: 2.1.2
Improved errors in console
--
Key: MSUREFIRE-35
URL:
[ http://jira.codehaus.org/browse/MSUREFIRE-37?page=all ]
Jason van Zyl updated MSUREFIRE-37:
---
Fix Version: 2.1.2
Remove or fix strange battery = null messages displayed on the console
[ http://jira.codehaus.org/browse/MSUREFIRE-36?page=all ]
Jason van Zyl updated MSUREFIRE-36:
---
Fix Version: 2.1.2
surefire property droppings in fork mode
Key: MSUREFIRE-36
URL:
[ http://jira.codehaus.org/browse/MSUREFIRE-34?page=all ]
Brett Porter updated MSUREFIRE-34:
--
Fix Version: 2.1.2
seems this is a bug in surefire, not the report
surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5 xml file
[ http://jira.codehaus.org/browse/MSUREFIRE-12?page=all ]
Brett Porter closed MSUREFIRE-12:
-
Assign To: Brett Porter
Resolution: Cannot Reproduce
we won't be able to reproduce this. I'm pretty sure a seg fault has to be a bug
in the JDK -
[ http://jira.codehaus.org/browse/MNG-1906?page=all ]
Brett Porter moved MSUREFIRE-1 to MNG-1906:
---
Key: MNG-1906 (was: MSUREFIRE-1)
Project: Maven 2 (was: Maven 2.x Surefire Plugin)
properties not being replaced before being passed
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051230.183000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051230.183000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Do not execute checkstyle when the project has no sources
-
Key: MCHECKSTYLE-25
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-25
Project: Maven 2.x Checkstyle Plugin
Type: Improvement
Versions:
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051230.184500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051230.184500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54556
]
fabrizio giustina commented on MCHECKSTYLE-25:
--
Hi Vincent
are you using the latest version from svn? This should already be fixed, see
MCHECKSTYLE-17
Do not
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54557
]
Vincent Massol commented on MCHECKSTYLE-25:
---
Hi Fabrizio,
I'm using what's in svn trunk which is *supposed* to be the latets. I've just
learnt from Brett that trunk is
[ http://jira.codehaus.org/browse/MANTRUN-28?page=all ]
Carlos Sanchez closed MANTRUN-28:
-
Assign To: Carlos Sanchez
Resolution: Fixed
Fix Version: 1.1
maven.test.classpath doesn't contain test scope dependancies
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=all ]
Brett Porter closed MCHECKSTYLE-25:
---
Assign To: Brett Porter (was: fabrizio giustina)
Resolution: Duplicate
Do not execute checkstyle when the project has no sources
Bundle wagon-ssh-external with maven dist
-
Key: MNG-1907
URL: http://jira.codehaus.org/browse/MNG-1907
Project: Maven 2
Type: Improvement
Versions: 2.0.2, 2.0.1
Environment: All
Reporter: Arik Kfir
Priority:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051230.190001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051230.190001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MANTRUN-31?page=all ]
Carlos Sanchez closed MANTRUN-31:
-
Assign To: Carlos Sanchez
Resolution: Fixed
Fix Version: 1.1
Will be fixed in next deployment
Incorrect svn url in the documentation
[ http://jira.codehaus.org/browse/MANTRUN-30?page=all ]
Carlos Sanchez closed MANTRUN-30:
-
Assign To: Carlos Sanchez
Resolution: Duplicate
Subversion links point to wrong location.
-
Key:
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54561
]
fabrizio giustina commented on MCHECKSTYLE-25:
--
I am committing changes to trunk, AFAIK there are no branches for plugins
actually.
The current version of
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051230.191500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051230.191500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=all ]
Vincent Massol reopened MCHECKSTYLE-25:
---
Assign To: fabrizio giustina (was: Brett Porter)
Reopening as Fabrizio has confirmed it's not a dupliate and a real issue. i'll
edit the
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=all ]
Vincent Massol updated MCHECKSTYLE-25:
--
Summary: Do not execute checkstyle when the project has no sources and when
checkstyle is triggered through checkstyle:check (was: Do not execute
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54565
]
Vincent Massol commented on MCHECKSTYLE-25:
---
Hi Fabrizio,
Thanks for fixing this! It's better but there's still an issue:
C:\dev\cargo\trunk\coremvn clean install
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051230.193000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051230.193000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=all ]
fabrizio giustina closed MCHECKSTYLE-25:
Resolution: Fixed
Fix Version: 2.0-beta-2
Closing this issue since Vincent confirmed it's fixed.
Vincent, can you open a new issue
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051230.194500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051230.194500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MCHECKSTYLE-24?page=comments#action_54574
]
Joakim Erdfelt commented on MCHECKSTYLE-24:
---
The specific exception message related to commons-logging 1.0.3 (and earlier).
We've had this exception occur on our own
checkstyle:check fails when the project has no sources
---
Key: MCHECKSTYLE-26
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-26
Project: Maven 2.x Checkstyle Plugin
Type: Bug
Reporter: Vincent Massol
See
[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54577
]
Vincent Massol commented on MCHECKSTYLE-25:
---
I've opened a new (but related) issue: MCHECKSTYLE-26
Do not execute checkstyle when the project has no sources and when
[ http://jira.codehaus.org/browse/MRM-41?page=comments#action_54578 ]
Brett Porter commented on MRM-41:
-
I'll wait for the tests to apply this.
discover standalone POMs
Key: MRM-41
URL:
[ http://jira.codehaus.org/browse/MCHECKSTYLE-26?page=all ]
fabrizio giustina closed MCHECKSTYLE-26:
Assign To: fabrizio giustina
Resolution: Fixed
Fix Version: 2.0-beta-2
give it a try now
checkstyle:check fails when the
[ http://jira.codehaus.org/browse/MSUREFIRE-20?page=comments#action_54583 ]
Jason van Zyl commented on MSUREFIRE-20:
I will integrate this test into an integration test for the plugin.
forkMode=pertest fails to call setUp
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051231.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051231.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051231.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051231.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051231.011500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.011500.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MEV-273?page=all ]
Brian Fox updated MEV-273:
--
Attachment: pom.xml
jfreechart is located in jfree/jfreechart (pom attached)
Key: MEV-273
URL:
jfreechart is located in jfree/jfreechart (pom attached)
Key: MEV-273
URL: http://jira.codehaus.org/browse/MEV-273
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Reporter: Brian Fox
[ http://jira.codehaus.org/browse/MPMD-1?page=comments#action_54599 ]
domi commented on MPMD-1:
-
I have the same and also found out there are more plugins having the same
problem e.g. checkstyle (http://jira.codehaus.org/browse/MCHECKSTYLE-15?rc=1)
PMD does not
[ http://jira.codehaus.org/browse/MCHECKSTYLE-15?page=comments#action_54600
]
domi commented on MCHECKSTYLE-15:
-
I have the same problem - the fix seems not yet to be published...
Exception: Can't find resource bundle for current bundle
93 matches
Mail list logo