should be the same but for modules. I don't think it matters as long as
the rest of the elements are ok. Obviously we need to improve how Maven
deals with this (another thing related to my earlier mail on POM
inheritance).
In future, this should be posted to [EMAIL PROTECTED], it's not
really rele
http://www.ibiblio.org/maven2/org/codehaus/mojo/mojo/5/
vs
http://svn.codehaus.org/trunk/mojo/pom.xml?rev=1036&root=mojo&view=auto
the one at central repo uses scpexe for deployment
is it intended?
-D
Vincent Massol wrote:
> Ok, I didn't know we were following that rule...
>
> If we want to enforce this then we could have a config property in the site
> plugin to only deploy sites if the version is not snapshot and we should
> activate this feature for the maven plugins.
>
We can put this in
Vincent Massol wrote:
> No. It was because there was a bug and I had implemented the correct
> algorithm only for the clover:check goal. I have fixed that yesterday or
> today (can't remember).
>
Yep, I hadn't caught the commit there yet. It's working now.
-Brett
-
+1
Brett Porter wrote:
> I'd like to see the other thread on the clover default resolved first
> and am withholding my vote until then.
>
> - Brett
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051224.003000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051224.003000.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051224.00.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051224.00.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/ARCHETYPE-20?page=comments#action_54154 ]
Jason van Zyl commented on ARCHETYPE-20:
I'll stat with one for the geronimo site as I'm trying to incorporate some work
by volunteers who have made some skins.
> create a s
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: vendredi 23 décembre 2005 22:28
> To: Maven Developers List
> Subject: Re: maven ear release 2.1 - web site not up to date
>
> I have taken the practice of not publishing snapshot websites. The
> reason generateP
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.224500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.224500.txt
-
To unsubscribe, e-mai
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: vendredi 23 décembre 2005 22:23
> To: Maven Developers List
> Subject: Re: clover default?
>
> Without the threading settings? did you change something?
The defaults are:
- flushPolicy = threaded
- flushInterva
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.223000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.223000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.221500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.221500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MSITE-59?page=all ]
Brett Porter closed MSITE-59:
-
Assign To: Brett Porter (was: Jason van Zyl)
Resolution: Fixed
this is a bug in SVN, not a released version. I've got it fixed locally.
> "mvn site" fails when n
[ http://jira.codehaus.org/browse/MNG-897?page=comments#action_54152 ]
Brett Porter commented on MNG-897:
--
Should this be closed John?
> allows use of Ant build files
> -
>
> Key: MNG-897
> URL: http://jira.code
I have taken the practice of not publishing snapshot websites. The
reason generatePom is not up on the site is because it isn't in the
released plugin. I think we should revert to the *released* sites (or
better yet, release those plugins - didn't John have votes up for them?)
Changing the parent
I'd like to see the other thread on the clover default resolved first
and am withholding my vote until then.
- Brett
Vincent Massol wrote:
> Hi,
>
> I've just fixed an issue with the clover plugin when used in a multimodule
> project. I think we're ready to release version 2.0. There are some iss
Without the threading settings? did you change something?
I had been getting 0 results running clover:clover. This is because it
terminates immediately after the tests complete, before flushing the db.
When run under site it works, because other things happen after clover
giving the jvm long enoug
Moderators: please pay more attention. This is a duped jira message that
appears to be bouncing to us from [EMAIL PROTECTED] I've seen 2 or 3 of
these modded through. I just ignore them.
- Brett
[EMAIL PROTECTED] wrote:
> [ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54110 ]
[ http://jira.codehaus.org/browse/MPA-36?page=comments#action_54151 ]
Brett Porter commented on MPA-36:
-
since it's not associated with individual projects, then we'd just be adding:
svn.root.6=http://svn.apache.org/repos/asf/maven
viewcvs.url.6=http://svn.ap
create a site skin archetype
Key: ARCHETYPE-20
URL: http://jira.codehaus.org/browse/ARCHETYPE-20
Project: Maven Archetype
Type: Task
Reporter: Brett Porter
Assigned to: Jason van Zyl
--
This message is automatically generated
> -Original Message-
> From: Martin van den Bemt [mailto:[EMAIL PROTECTED]
> Sent: vendredi 23 décembre 2005 21:11
> To: Maven Developers List
> Subject: Re: maven ear release 2.1 - web site not up to date
>
> It prevents running the plugin on maven 2.0 (for the clover plugin I
> needed
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.20.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.20.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
It prevents running the plugin on maven 2.0 (for the clover plugin I needed to
install 2.0.1 when you changed that)
Mvgr,
Martin
Vincent Massol wrote:
-Original Message-
From: Arik Kfir [mailto:[EMAIL PROTECTED]
Sent: vendredi 23 décembre 2005 20:12
To: Maven Developers List
Subject:
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.194500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.194500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MEV-163?page=all ]
Carlos Sanchez closed MEV-163:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Fixed as groovy:1.0-jsr-03
It'd be nice to notify groovy developers
> Groovy pom has invalid dependencies
> -
> -Original Message-
> From: Arik Kfir [mailto:[EMAIL PROTECTED]
> Sent: vendredi 23 décembre 2005 20:12
> To: Maven Developers List
> Subject: Re: maven ear release 2.1 - web site not up to date
>
> The same is with the deploy/install sites (the 'generatePom' arguments
> are not there,
better yet, we need to release install and deloy plugins, it has
install-file and deploy-file features which are so useful and popular
On 12/23/05, Arik Kfir <[EMAIL PROTECTED]> wrote:
>
> The same is with the deploy/install sites (the 'generatePom' arguments
> are not there, for instance). They
[ http://jira.codehaus.org/browse/MEV-2?page=all ]
Carlos Sanchez closed MEV-2:
Assign To: Carlos Sanchez
Resolution: Fixed
> Broken dependency for groovy
>
>
> Key: MEV-2
> URL: http://jira.codehaus.o
The same is with the deploy/install sites (the 'generatePom' arguments
are not there, for instance). They were last published in october...
On 12/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
> I've just redeployed the web site for the ear plugin.
>
> -Vincent
>
> > -Original Message-
>
scm plugin ignores -Dusername for CSV provider
--
Key: SCM-123
URL: http://jira.codehaus.org/browse/SCM-123
Project: Maven SCM
Type: Bug
Components: maven-plugin
Versions: 1.0-beta-2
Environment: xp, cvs
R
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.174500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.174500.txt
-
To unsubscribe, e-mai
Vincent Massol wrote:
Hi,
I've just fixed an issue with the clover plugin when used in a multimodule
project. I think we're ready to release version 2.0. There are some issues
in JIRA but they're unconfirmed or minor and I think users have already
waited long enough for the plugin. Most are usin
+1.. (non-binding)
Too bad I couldn't figure out the report stuff :(
We'll leave that for the next release..
Mvgr,
Martin
Vincent Massol wrote:
Hi,
I've just fixed an issue with the clover plugin when used in a multimodule
project. I think we're ready to release version 2.0. There are some iss
+1
On 12/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've just fixed an issue with the clover plugin when used in a multimodule
> project. I think we're ready to release version 2.0. There are some issues
> in JIRA but they're unconfirmed or minor and I think users have already
>
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.173000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.173000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Hi,
I've just fixed an issue with the clover plugin when used in a multimodule
project. I think we're ready to release version 2.0. There are some issues
in JIRA but they're unconfirmed or minor and I think users have already
waited long enough for the plugin. Most are using version alpha1 which w
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.171501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.171501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MCLOVER-5?page=all ]
Vincent Massol closed MCLOVER-5:
Resolution: Fixed
Fixed.
> Clover fails on multi-module builds
> ---
>
> Key: MCLOVER-5
> URL: http://jira.cod
[ http://jira.codehaus.org/browse/MEV-4?page=all ]
Carlos Sanchez closed MEV-4:
Assign To: Carlos Sanchez
Resolution: Fixed
Fixed as 7.4.1-jdbc3
> Misnamed pom for Postgresql
> ---
>
> Key: MEV-4
> URL: ht
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.17.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.17.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051223.17.txt
[ http://jira.codehaus.org/browse/MNG-1783?page=comments#action_54137 ]
Dan Tran commented on MNG-1783:
---
mvn scm:validate -DconnectionUrl=scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:module
-X
shows the url is valid. So the problem is in release plugin?
> maven-re
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051223.164501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051223.164501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MEAR-3?page=all ]
Stephane Nicoll closed MEAR-3:
--
Resolution: Fixed
This is fixed. Thanks.
> ear includes and excludes don't handle comma separated tokens
>
[ http://jira.codehaus.org/browse/MSITE-59?page=comments#action_54134 ]
Vincent Massol commented on MSITE-59:
-
after some more investigation it seems the problem is not a missing site.xml.
Even with a site.xml the project is failing with the same error..
"mvn site" fails when no site.xml
-
Key: MSITE-59
URL: http://jira.codehaus.org/browse/MSITE-59
Project: Maven 2.x Site Plugin
Type: Bug
Environment: Maven 2.1-SNAPSHOT updated from 2005-12-23, ~17:00GMT+1
Reporter: Vincent Masso
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051223.163000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051223.163000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051223.163000.txt
I've just redeployed the web site for the ear plugin.
-Vincent
> -Original Message-
> From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
> Sent: vendredi 23 décembre 2005 17:37
> To: Maven Developers List
> Subject: maven ear release 2.1 - web site not up to date
>
> Guys,
>
> Maven EAR pl
Guys,
Maven EAR plugin 2.1 has been released but the web site has not been
updated. 2.1 contains new features which are not documented on the web site,
this is quite annoying.
Who can fix this?
Thanks,
Stéphane
--
.::You're welcome ::.
[ http://jira.codehaus.org/browse/MEAR-3?page=comments#action_54133 ]
Stephane Nicoll commented on MEAR-3:
David, your patch has been applied in the WAR plugin, Thanks!
> ear includes and excludes don't handle comma separated tokens
> ---
[ http://jira.codehaus.org/browse/MWAR-6?page=all ]
Stephane Nicoll closed MWAR-6:
--
Resolution: Duplicate
Fix Version: 2.0
This is fixed using the patch in MEAR-3 which fixes all parameters.
Thanks.
> dependentWarExcludes and dependentWarInclude
[ http://jira.codehaus.org/browse/MWAR-5?page=all ]
Stephane Nicoll reopened MWAR-5:
> warSourceExcludes not working properly
> --
>
> Key: MWAR-5
> URL: http://jira.codehaus.org/browse/MWAR-5
>
[ http://jira.codehaus.org/browse/MWAR-11?page=all ]
Stephane Nicoll closed MWAR-11:
---
Resolution: Fixed
Fix Version: 2.0
> Add war:exploded and war:inplace goals
> --
>
> Key: MWAR-11
> URL: h
[ http://jira.codehaus.org/browse/MWAR-5?page=all ]
Stephane Nicoll closed MWAR-5:
--
Resolution: Fixed
Fix Version: 2.0
> warSourceExcludes not working properly
> --
>
> Key: MWAR-5
> URL: http:
[ http://jira.codehaus.org/browse/MWAR-8?page=all ]
Stephane Nicoll closed MWAR-8:
--
Resolution: Fixed
Fix Version: 2.0
> Merge contents of dependent wars into war being built
> -
>
> Key
[ http://jira.codehaus.org/browse/MWAR-11?page=all ]
Stephane Nicoll reopened MWAR-11:
-
> Add war:exploded and war:inplace goals
> --
>
> Key: MWAR-11
> URL: http://jira.codehaus.org/browse/MWAR-11
>
[ http://jira.codehaus.org/browse/MWAR-8?page=all ]
Stephane Nicoll reopened MWAR-8:
> Merge contents of dependent wars into war being built
> -
>
> Key: MWAR-8
> URL: http://jira.cod
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051223.16.txt
[ http://jira.codehaus.org/browse/MWAR-3?page=all ]
Stephane Nicoll closed MWAR-3:
--
Resolution: Fixed
Fix Version: 2.0
> war:war launched from parent doesn't find module web.xml
>
>
>
[ http://jira.codehaus.org/browse/MWAR-3?page=all ]
Stephane Nicoll reopened MWAR-3:
> war:war launched from parent doesn't find module web.xml
>
>
> Key: MWAR-3
> URL: http://ji
[ http://jira.codehaus.org/browse/MWAR-1?page=all ]
Stephane Nicoll reopened MWAR-1:
> war:exploded removes content of .class files
>
>
> Key: MWAR-1
> URL: http://jira.codehaus.org/browse/M
[ http://jira.codehaus.org/browse/MWAR-1?page=all ]
Stephane Nicoll closed MWAR-1:
--
Resolution: Fixed
Fix Version: 2.0
> war:exploded removes content of .class files
>
>
> Key: MWAR-1
>
[ http://jira.codehaus.org/browse/MNG-1783?page=comments#action_54127 ]
Pascal Grange commented on MNG-1783:
If it is a simple fix, when do you think a new release fixing this bug will be
available ? I have to answer my boss.
Merry Christmas.
> maven-r
[ http://jira.codehaus.org/browse/MANTRUN-28?page=all ]
Gilles Scokart updated MANTRUN-28:
--
Attachment: MANTRUN-28.patch
> maven.test.classpath doesn't contain test scope dependancies
>
>
>
[ http://jira.codehaus.org/browse/MPA-36?page=all ]
Vincent Massol updated MPA-36:
--
Attachment: subversion-jira-plugin.properties
> associate Maven svn with JIRA projects
> --
>
> Key: MPA-36
> URL: http
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_54122
]
Eugene Kuleshov commented on MNGECLIPSE-15:
---
It seems to me that Eclipse is actually rignt and you should have these
properties files in a single place (perhaps common pr
[ http://jira.codehaus.org/browse/MEV-220?page=all ]
Carlos Sanchez closed MEV-220:
--
Resolution: Fixed
Set as optional in 1.2.5 and 1.2.6
Related docs for maven 2.1
http://docs.codehaus.org/display/MAVEN/Specification+Dependencies+Design
> spring-moc
[ http://jira.codehaus.org/browse/MEV-269?page=all ]
Carlos Sanchez closed MEV-269:
--
Assign To: Carlos Sanchez
Resolution: Fixed
It may take one day to reach ibiblio
> checkstyle 4.1 pom
> --
>
> Key: MEV-269
> U
mvn debug level not passed to ant
-
Key: MANTRUN-35
URL: http://jira.codehaus.org/browse/MANTRUN-35
Project: Maven 2.x Antrun Plugin
Type: Improvement
Environment: Any
Reporter: M. van der Plas
Assigned to: Jason van Zyl
Pr
[ http://jira.codehaus.org/browse/MEV-269?page=all ]
Brent Worden updated MEV-269:
-
Attachment: checkstyle-4.1.pom
> checkstyle 4.1 pom
> --
>
> Key: MEV-269
> URL: http://jira.codehaus.org/browse/MEV-269
> Project: Mav
checkstyle 4.1 pom
--
Key: MEV-269
URL: http://jira.codehaus.org/browse/MEV-269
Project: Maven Evangelism
Type: Task
Components: Invalid POM
Reporter: Brent Worden
same as 4.0 except for version number.
--
This message is automatically ge
Hi Brett,
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: vendredi 23 décembre 2005 04:00
> To: Maven Developers List
> Subject: clover default?
>
> Hi,
>
> I'm wondering what the default for clover should be:
> - everything as now, but set forkmode once when
[ http://jira.codehaus.org/browse/MNGECLIPSE-13?page=comments#action_54113
]
Michał Steiner commented on MNGECLIPSE-13:
---
Adding dependency brokes also encoding ( UTF characters are changed to '?')
and removes schema declaration from pom.x
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54110 ]
Edwin Punzalan commented on MNG-1703:
-
Hmmm... that\'s odd. can you do a \"mvn help:effective-pom\" on the child
module and see which have been inherited? Mine definitely has the
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54110 ]
Edwin Punzalan commented on MNG-1703:
-
Hmmm... that's odd. can you do a "mvn help:effective-pom" on the child module
and see which have been inherited? Mine definitely has the exec
77 matches
Mail list logo
