Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051229.073000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051229.073000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MRM-41?page=comments#action_54396 ]
John Tolentino commented on MRM-41:
---
I see your point. I confused the repository poms with pom.xml.
> discover standalone POMs
>
>
> Key: MRM-41
>
[ http://jira.codehaus.org/browse/MSITE-48?page=all ]
Brett Porter closed MSITE-48:
-
Resolution: Fixed
> add reusable skin functionality and create skins default, stylus and classic
> -
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051229.071500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
track attempted downloads and only re-attempt on certain intervals
--
Key: MNG-1902
URL: http://jira.codehaus.org/browse/MNG-1902
Project: Maven 2
Type: Improvement
Components: Artifacts and Repositor
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051229.041500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051229.041500.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051229.033001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051229.033001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54390 ]
Rahul Thakur commented on MECLIPSE-47:
--
Sorry about the code formatting (not sure why that would've happened I am
positive I am using the Maven code style for eclipse).
I have
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051229.031502.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051229.031502.txt
-
To unsubscribe, e-mai
Brett Porter wrote:
If we just do pre/post, won't the next point be that pre-pre-compile is
needed?
I imagine that 90% of what people do will be covered by the standard
lifecycle, 5% of people might make custom lifecycle and 5% might need to
do some really weird stuff with a big pile of rop
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 places in the lifecycle w
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 places in the lifecycle where the
same argument applies
Jesse McConnell wrote:
I worry a bit about mixing unit and integration tests generally...
maybe we have the recommended case for them go into
src/integration-test/java or something along those lines...
+1
When I said parallel to unit testing that's what I meant so that
everything was distinc
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (7 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-645Jini Service Archetype version 2.0
http://jira.codehaus.org/browse/MAVENUPLOAD-645
MAVENUPLOAD-644Maven Jini Plug-in version 2.0
ht
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (12 issues)
Subscriber: mavendevlist
Key Summary
MEV-255 Problem with junit-addons 1.4
http://jira.codehaus.org/browse/MEV-255
MEV-126 poms for som emissing sun xml API + javamail 1.3.3
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051229.011500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051229.011500.txt
-
To unsubscribe, e-mai
Sounds like a great idea! They should all go in maven-core-it (possibly
as multiple projects). This is really the integration testing of the
Maven distribution, not just the maven-core library.
- Brett
Joakim Erdfelt wrote:
> There are a number of issues within JIRA that are the result of
> Resou
There are a number of issues within JIRA that are the result of Resource
access issues.
They way I see it, we have 4 different resource access issues when
dealing with plugins/reports.
1) resources from dependency in parent pom.
2) resources from transitive dependency.
3) resources from plugi
The netbeans-freeform project has not been released yet, and no snapshot
is available in the repo too ( i wonder why)
If you still want to use it ( I recommend you do so ^_^), please follow
the procedure herein:
http://maven.apache.org/guides/development/guide-testing-development-plugins.html
Sorry to top reply, am trying to capture a response to several emails in
the thread:
+1 to src/it/java, and a reproduction of all test phases for integration
testing
We may want to have a functional test set as well that is separate to
integration testing (I know there a bunch of different names,
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051229.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I believe this was already fixed in SVN (branches/maven-2.0.x, there is
a test version up on cvs.apache.org/maven-snapshot-repository).
- Brett
Steve Loughran wrote:
> I've just upgraded to maven2.01 and things are breaking :
>
> compile-classpath:
> [m2:dependencies] An error has occurred while
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051229.00.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051229.00.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
I've just upgraded to maven2.01 and things are breaking :
compile-classpath:
[m2:dependencies] An error has occurred while processing the Maven
artifact tasks.
[m2:dependencies] Diagnosis:
[m2:dependencies]
[m2:dependencies] Unable to build project:
C:\Personal\examples\diary\persist\build\pr
Actually, the checkstyle 4.1 pom was ok.
However the commons-beanutils-core/1.7.0 had a typo in its pom
1.7
it should have been
1.7.0
Carlos has already fixed this.
/* joakim */
Brett Porter wrote:
When checkstyle was upgraded to 4.1, nobody checked the checkstyle POM,
which is a dud. It's
[ http://jira.codehaus.org/browse/MNG-1901?page=all ]
Joakim Erdfelt updated MNG-1901:
Attachment: MNG-1901.patch
> Report Classloaders out of sync when executed from within the site:site goal.
> --
[ http://jira.codehaus.org/browse/MEV-271?page=comments#action_54380 ]
Brian Bonner commented on MEV-271:
--
Hmm. At the time, I was able to hit the other parts of ibiblio (i.e. jar,
metadata, etc.). Glad it's fixed though. Thanks.
> springframework:sprin
[ http://jira.codehaus.org/browse/MJAVADOC-19?page=comments#action_54379 ]
Martin Desruisseaux commented on MJAVADOC-19:
-
Since this issue as about the path to an overview file, it may be related to
MJAVADOC-39.
> Overview parameter isn't havin
javadoc plugin (beta 3) chdir in 'target/site/apidocs', causing
parameter to fail
Key: MJAVADOC-39
URL: http://jira.codehaus.org/browse/MJAVADOC-39
Project: Maven 2.x Javadoc Plugi
[ http://jira.codehaus.org/browse/MJAVADOC-25?page=comments#action_54377 ]
Martin Desruisseaux commented on MJAVADOC-25:
-
It still not fixed in maven-javadoc-plugin 2.0-beta-3. We still have the error
"-locale argument must be first".
> option
On 12/28/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
>
>
> Sure but there's a very common use case for integration testing: the need
> to
> have environment setup before the test and to clean it after the tests. Of
> course you could write all sort of plugin to that the plugin support doing
> t
Report Classloaders out of sync when executed from within the site:site goal.
-
Key: MNG-1901
URL: http://jira.codehaus.org/browse/MNG-1901
Project: Maven 2
Type: Bug
Components: Plugins a
> -Original Message-
> From: Jesse McConnell [mailto:[EMAIL PROTECTED]
> Sent: mercredi 28 décembre 2005 20:44
> To: Maven Developers List
> Subject: Re: [discussion] Integration testing location
>
> I worry a bit about mixing unit and integration tests generally...
>
> maybe we have th
[
http://jira.codehaus.org/browse/MAVENUPLOAD-645?page=comments#action_54371 ]
Chris Sterling commented on MAVENUPLOAD-645:
I have updated the groupId to org.jini.maven-jini-plugin from org.jini. Thanks.
> Jini Service Archetype version 2.0
> -
[
http://jira.codehaus.org/browse/MAVENUPLOAD-644?page=comments#action_54370 ]
Chris Sterling commented on MAVENUPLOAD-644:
Thanks. I have uploaded the new bundle in the same location with groupId of
org.jini.maven-jini-plugin.
> Maven Jini Pl
I worry a bit about mixing unit and integration tests generally...
maybe we have the recommended case for them go into
src/integration-test/java or something along those lines...
logically the structure src/test/java and src/test/it doesn't do it for me
since it tests are probably written in java
Eclipse WSDL and XSD
Key: MAVENUPLOAD-653
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-653
Project: maven-upload-requests
Type: Task
Reporter: Guillaume Nodet
http://codehaus.org/~gnt/bundles/wsdl.jar
http://codehaus.org/~gnt/bundles/x
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: mercredi 28 décembre 2005 19:51
> To: Maven Developers List
> Subject: Re: [discussion] Integration testing location
>
> Vincent Massol wrote:
> > Hi there,
> >
> > I'd like to continue the discussion about inte
[ http://jira.codehaus.org/browse/MNG-1317?page=comments#action_54367 ]
Stephen B. Hahn commented on MNG-1317:
--
The following modifiaction fixed m2.bat:
for %%i in (%~sf0) do %%~dspimvn %*
> m2.bat doesn't work on Windows 2000
> --
[ http://jira.codehaus.org/browse/MNG-1273?page=comments#action_54366 ]
Stephen B. Hahn commented on MNG-1273:
--
This is a known bug in Windows 2000 and XP. It has been fixed in XP SP2. I have
successfully modified mvn.bat as follows:
if "%OS%"=="Window
[ http://jira.codehaus.org/browse/MNG-1317?page=comments#action_54365 ]
Stephen B. Hahn commented on MNG-1317:
--
This is a known bug in Windows 2000 and XP. It has been fixed in XP SP2. I have
successfully modified mvn.bat as follows:
if "%OS%"=="Window
[ http://jira.codehaus.org/browse/MNG-1318?page=comments#action_54364 ]
Stephen B. Hahn commented on MNG-1318:
--
This is a known bug in Windows 2000 and XP. It has been fixed in XP SP2. I
have successfully modified mvn.bat as follows:
if "%OS%"=="Wind
Vincent Massol wrote:
Hi there,
I'd like to continue the discussion about integration testing (see
http://docs.codehaus.org/display/MAVEN/Testing+Strategies). Here are some
topics on which I'd like to get your opinion:
1) Need for a pre/post phase to integration-test. See
http://jira.codehaus.o
version can not be supplied in parent pom
-
Key: MNGECLIPSE-19
URL: http://jira.codehaus.org/browse/MNGECLIPSE-19
Project: Maven 2.x Plug-in for Eclipse
Type: Bug
Reporter: Lee Meador
If I don't have a tag in the POM, I
Eclipse JUnit runner doesn't seem to get all the dependencies on its classpath
--
Key: MNGECLIPSE-18
URL: http://jira.codehaus.org/browse/MNGECLIPSE-18
Project: Maven 2.x Plug-in for Eclipse
Can't Attach Source to Maven Dependencies
-
Key: MNGECLIPSE-17
URL: http://jira.codehaus.org/browse/MNGECLIPSE-17
Project: Maven 2.x Plug-in for Eclipse
Type: Improvement
Reporter: Lee Meador
There does not seem to be an
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051228.173000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051228.173000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051228.171501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051228.171501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MPIR-10?page=all ]
fabrizio giustina closed MPIR-10:
-
Assign To: fabrizio giustina
Resolution: Fixed
Fix Version: 2.0
looks good, committed to svn. Thanks
a small modification: since the report is actuall
[ http://jira.codehaus.org/browse/MPIR-12?page=all ]
fabrizio giustina updated MPIR-12:
--
Version: 2.0-beta-3
> Dutch (NL) translation for site and reports plugins
> ---
>
> Key: MPIR-12
>
[ http://jira.codehaus.org/browse/MPIR-10?page=all ]
fabrizio giustina updated MPIR-10:
--
Version: 2.0-beta-3
> Add Dependency Convergence (w/Ready for Release indicator) report.
> --
>
>
[ http://jira.codehaus.org/browse/MPIR-11?page=all ]
fabrizio giustina updated MPIR-11:
--
Version: 2.0-beta-3
> improved dependency report
> --
>
> Key: MPIR-11
> URL: http://jira.codehaus.org/browse/MPIR-11
>
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051228.163000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051228.163000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Hi there,
I'd like to continue the discussion about integration testing (see
http://docs.codehaus.org/display/MAVEN/Testing+Strategies). Here are some
topics on which I'd like to get your opinion:
1) Need for a pre/post phase to integration-test. See
http://jira.codehaus.org/browse/MNG-1880.
I g
[ http://jira.codehaus.org/browse/MIDEA-5?page=comments#action_54357 ]
Geoffrey commented on MIDEA-5:
--
Thanks, this comment just saved me a lot of time, was already trying with maven
2.0 for an hour trying to fix the corrupted issue.
> using copyright plugin g
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051228.161500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051228.161500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MPIR-11?page=comments#action_54356 ]
fabrizio giustina commented on MPIR-11:
---
Checked in a small improvement: dependencies are listed by scope and optional
dependencies are flagged. Not yet optimal, but better...
note
Brett Porter wrote:
I don't know much about Ruby, but took a quick look over the docs for
this and I'm impressed. Keep up the good work, and hope you find plenty
of interest in this!
I worked with Eric yesterday for a bit to sort out his login problems at
the Mojo project so all this good stuf
I have created a new archetype project and then try to run
mvn netbeans-freeform:generate-netbeans-project
To create a netbeans project but I am presented with the following error.
C:\u0da2\abbsonline2006>mvn netbeans-freeform:generate-netbeans-project
[INFO] Scanning for projects...
[INFO] Sear
Eclipse EMF 2.1.1
-
Key: MAVENUPLOAD-652
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-652
Project: maven-upload-requests
Type: Task
Reporter: Guillaume Nodet
http://codehaus.org/~gnt/bundles/ant.jar
http://codehaus.org/~gnt/bundles/codegen-
Esccape property replacement inside quote
-
Key: MANTRUN-36
URL: http://jira.codehaus.org/browse/MANTRUN-36
Project: Maven 2.x Antrun Plugin
Type: Bug
Reporter: Gilles Scokart
Attachments: ant.xml, pom.xml
The propoertie
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051228.140001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051228.140001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051228.134501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051228.134501.txt
-
To unsubscribe, e-mai
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 28 décembre 2005 14:35
> To: Maven Developers List
> Subject: Re: plugin project leads
>
> Jason van Zyl wrote:
> > People will always come and go but some people are willing to steward
> > a particular
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051228.133001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051228.133001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MECLIPSE-36?page=all ]
fabrizio giustina closed MECLIPSE-36:
-
Assign To: fabrizio giustina
Resolution: Fixed
Fix Version: 2.1
fix in svn for 2.1, thansk
> use project.build.finalName for WTP context-
Jason van Zyl wrote:
> People will always come and go but some people are willing to steward
> a particular plugin. If there ends up not being those people then
> that's fine. But I would hope some people care enough. They can always
> work with the group of interested people and person who wants t
[ http://jira.codehaus.org/browse/MNG-1886?page=all ]
Brett Porter updated MNG-1886:
--
Fix Version: 2.1
> Need way to share code between report mojos and main build mojos
>
>
> Key: MN
Hi,
Our production is currently running m1.0.2 and I am planning to move
to 1.1 as soon as possible (is there a release date for 1.1 by the
way?).
We have used for a long time eclipse plugin 1.9 patched with
MPECLIPSE-60 (which basically download java sources from the
repository).
Eclipse plugin
[ http://jira.codehaus.org/browse/MNG-1886?page=all ]
Brett Porter reopened MNG-1886:
---
ok, there's something else here. I guess its going to be something like
MavenArchiveConfiguration, but with a @parameter nested="false" or something
like that. Won't
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051228.131501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MEV-271?page=all ]
Carlos Sanchez closed MEV-271:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
Seems that you accessed ibiblio when it had a downtime. Now it works
> springframework:spring-mock:1.2.6
> --
[ http://jira.codehaus.org/browse/MECLIPSE-37?page=all ]
fabrizio giustina closed MECLIPSE-37:
-
Assign To: fabrizio giustina
Resolution: Fixed
Fix Version: 2.1
phase changed to "generate-test-resources" as suggested by Trygve
> ecli
[ http://jira.codehaus.org/browse/MECLIPSE-8?page=all ]
fabrizio giustina closed MECLIPSE-8:
Assign To: fabrizio giustina
Resolution: Fixed
Fix Version: 2.1
Release 2.0 already supported generated sources in the "generate-source" phas
[ http://jira.codehaus.org/browse/MNG-1886?page=comments#action_54344 ]
Vincent Massol commented on MNG-1886:
-
I'm talking about sharing configuration elements (fields).
Here's an example:
...
...
[...]
Is there any doc on the plugin context? I
[ http://jira.codehaus.org/browse/MNG-1896?page=all ]
Brett Porter closed MNG-1896:
-
Assign To: Brett Porter
Resolution: Duplicate
> Can't load a class from a plugin, when this class is in a parent
> pom's/build/pluginManagement/plugins/plugin/dep
[ http://jira.codehaus.org/browse/MNG-1900?page=all ]
Brett Porter updated MNG-1900:
--
Attachment: MDEPLOY-13.diff
> Error while deploying when using scpexe protocol with non-default scp/ssh
> executables
> --
[ http://jira.codehaus.org/browse/MNG-1900?page=all ]
Brett Porter updated MNG-1900:
--
Fix Version: 2.0.2
> Error while deploying when using scpexe protocol with non-default scp/ssh
> executables
> ---
[ http://jira.codehaus.org/browse/MNG-1900?page=all ]
Brett Porter moved MDEPLOY-13 to MNG-1900:
--
Key: MNG-1900 (was: MDEPLOY-13)
Project: Maven 2 (was: Maven 2.x Deploy Plugin)
> Error while deploying when using scpexe protocol with n
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051228.13.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54340 ]
Grégory Joseph commented on MNG-1703:
-
then this is duplicate with MNG-1896 :)
> is not propagated to child POMs
>
>
springframework:spring-mock:1.2.6
-
Key: MEV-271
URL: http://jira.codehaus.org/browse/MEV-271
Project: Maven Evangelism
Type: Bug
Components: Missing POM
Reporter: Brian Bonner
This seems to be related to MEV-267. Maven say
[ http://jira.codehaus.org/browse/MJAVADOC-30?page=comments#action_54339 ]
Brett Porter commented on MJAVADOC-30:
--
the fix has not yet been officially released. It is due shortly.
> javadoc plugin does not work on war projects
> ---
[ http://jira.codehaus.org/browse/MNG-1882?page=all ]
Brett Porter updated MNG-1882:
--
Fix Version: 2.0.3
> activeByDefault is ignored in pom.xml
> -
>
> Key: MNG-1882
> URL: http://jira.codehaus.org/brow
[ http://jira.codehaus.org/browse/MNG-1886?page=all ]
Brett Porter closed MNG-1886:
-
Assign To: Brett Porter
Resolution: Won't Fix
can you elaborate on what you mean here?
If they are sharing types - there is no reason this can't be done with a
s
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051228.124500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051228.124500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNG-1703?page=all ]
Brett Porter updated MNG-1703:
--
Summary: is not propagated to child POMs
(was: is not propagated to child POMs)
I've updated the subject accordingly.
> is not propagated to child POMs
> ---
[ http://jira.codehaus.org/browse/MRM-41?page=comments#action_54335 ]
Brett Porter commented on MRM-41:
-
John, why would pom.xml need to be discovered? All poms in the repository are
*.pom. By standalone pom, I mean the ones where there is no corresponding J
On 12/26/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
> 2/ The release:perform goal failed on me with some error about my .svn/tmp
> directory having some errors. Doing a svn cleanup did not fix it. Not sure
> what this second error was about.
I got this error too when trying to merge a change f
[ http://jira.codehaus.org/browse/MECLIPSE-50?page=all ]
fabrizio giustina closed MECLIPSE-50:
-
Assign To: fabrizio giustina (was: Jason van Zyl)
Resolution: Fixed
Fix Version: 2.1
committed
> Add getter/setter methods to the Eclips
[ http://jira.codehaus.org/browse/MECLIPSE-26?page=all ]
fabrizio giustina closed MECLIPSE-26:
-
Assign To: fabrizio giustina
Resolution: Cannot Reproduce
Fix Version: 2.0
the JRE added to classpath by the current release is correct ac
Remove or fix strange "battery = null" messages displayed on the console
Key: MSUREFIRE-37
URL: http://jira.codehaus.org/browse/MSUREFIRE-37
Project: Maven 2.x Surefire Plugin
Type: Bug
Rep
Ervacon Spring Web Flow 1.0.0
-
Key: MAVENUPLOAD-651
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-651
Project: maven-upload-requests
Type: Task
Reporter: Erwin Vervaet
http://users.telenet.be/ervacon/ervacon/files/webflow-1.0.0-
[ http://jira.codehaus.org/browse/CONTINUUM-497?page=comments#action_54328
]
Guillaume Nodet commented on CONTINUUM-497:
---
It can be quite important in some cases: to check builded jars, or download
logs which are too big to be viewed online
> Abi
Groovy 1.0-jsr-04 not uploaded correctly
Key: MAVENUPLOAD-650
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-650
Project: maven-upload-requests
Type: Bug
Reporter: Dominik Roblek
The groovy is declared in POM as:
groo
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051228.111500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051228.111500.txt
-
To unsubscribe, e-mai
We went over these suggestions in March and I was originally a proponent
of phase or goal-based scoping instead of what we kept, but now agree we
made the right choice.
Basically, the scope is an intelligent default for most settings, it
maps well to a number of different scenarios, and scopes are
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20051228.11.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051228.11.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_54327 ]
fabrizio giustina commented on MECLIPSE-47:
---
Patch committed to svn, with a few changes. R7 is left as the default since
there are some left for wtp 1.0, see the following c
Sorry for the delayed response. It's that time of year :)
Mauro Botelho wrote:
> Is the idea to capture detailed information for each plug in or just
> high level statistics like the old dashboard used to do?
I'd like each plugin to be able to have its own stats so they can easily
do some form of
1 - 100 of 123 matches
Mail list logo
