Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.06.txt
[ http://jira.codehaus.org/browse/CONTINUUM-150?page=all ]
Brett Porter updated CONTINUUM-150:
---
Fix Version: (was: 1.0-beta-2)
1.0
Continuum site needs screenshots
Key: CONTINUUM-150
[ http://jira.codehaus.org/browse/CONTINUUM-278?page=all ]
Brett Porter updated CONTINUUM-278:
---
Fix Version: (was: 1.0-beta-2)
1.1
associate project developers with continuum users
[ http://jira.codehaus.org/browse/CONTINUUM-272?page=all ]
Brett Porter updated CONTINUUM-272:
---
Fix Version: (was: 1.0-beta-2)
1.1
add installation configuration to white site
[ http://jira.codehaus.org/browse/CONTINUUM-140?page=all ]
Brett Porter updated CONTINUUM-140:
---
Fix Version: (was: 1.0-beta-2)
1.1
Allow the use of the CC in the web UI
-
Key:
[ http://jira.codehaus.org/browse/CONTINUUM-46?page=all ]
Brett Porter updated CONTINUUM-46:
--
Fix Version: (was: 1.0-beta-2)
1.1
view the build schedule
---
Key: CONTINUUM-46
URL:
[ http://jira.codehaus.org/browse/CONTINUUM-273?page=all ]
Brett Porter updated CONTINUUM-273:
---
Fix Version: (was: 1.0-beta-2)
1.1
implement screens for installation configuration
[ http://jira.codehaus.org/browse/CONTINUUM-59?page=all ]
Brett Porter updated CONTINUUM-59:
--
Fix Version: (was: 1.0-beta-2)
1.1
design and implement configurable installations
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=all ]
Brett Porter updated CONTINUUM-44:
--
Fix Version: (was: 1.0-beta-2)
1.1
multiple profiles
-
Key: CONTINUUM-44
URL:
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.083001.txt
[ http://jira.codehaus.org/browse/CONTINUUM-331?page=comments#action_47850
]
Yann Le Du commented on CONTINUUM-331:
--
This issue can be linked to CONTINUUM-316
Invalid build #
---
Key: CONTINUUM-331
URL:
[ http://jira.codehaus.org/browse/CONTINUUM-275?page=all ]
Emmanuel Venisse closed CONTINUUM-275:
--
Resolution: Fixed
implement and test user/permissions in store
Key: CONTINUUM-275
[ http://jira.codehaus.org/browse/CONTINUUM-6?page=all ]
Emmanuel Venisse closed CONTINUUM-6:
Resolution: Fixed
Permissions are :
- Add Projects
- Edit Projects
- Delete Projects
- Build Projects
- Show Projects
- Add Build Definitions
- Edit
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051005.203000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.203000.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051005.213000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.213000.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051006.013000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051006.013000.txt
fyi
---BeginMessage---
Subversion commit messages are sent to different lists
according to the following mapping
# Maven
[/maven]
for_paths = maven/
to_addr = commits at maven.apache.org
suppress_if_match = yes
[/maven/continuum]
for_paths = maven/continuum/
to_addr = continuum-commits at
[ http://jira.codehaus.org/browse/MPMULTIPROJECT-61?page=all ]
Lukas Theussl closed MPMULTIPROJECT-61:
---
Resolution: Fixed
Error in the projects list
--
Key: MPMULTIPROJECT-61
URL:
The Apache Maven team are proud to announce the third beta release of
Maven 2.0.
Download it from http://maven.apache.org/maven2/download.html
Maven is a software project management and comprehension tool. Based on
the concept of a project object model (POM), Maven can manage a
project's build,
[ http://jira.codehaus.org/browse/MNG-1091?page=all ]
Brett Porter updated MNG-1091:
--
Fix Version: 2.0-beta-4
Reformat the autogenerated goal parameters page to improve readibility.
---
Build statistics:
State: Error
Previous State: Ok
Started at: mar., 4 oct. 2005 23:09:38 +0200
Finished at: mar., 4 oct. 2005 23:11:49 +0200
Total time: 2m 11s
Build Trigger: Schedule
Exit code: 0
Building machine hostname: harlock
Operating system : Windows XP(Service Pack 2)
Hi, I was wondering, are the inconsistencies in the header of the 2
sites intenden or just human errors? (OBS, they are not BIG errors, you
might consider them more like build warnings :-)
anyway here they come those that I have found..
* The maven apache logo has links to 2 different places
[ http://jira.codehaus.org/browse/MNG-1040?page=all ]
Johnny R. Ruiz III updated MNG-1040:
Attachment: MNG-1040-maven-reporting.patch
Instead of printing the string created by
createLinkPatternedText(text,parameter) method, I only printed the href
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.063001.txt
[ http://jira.codehaus.org/browse/MNG-940?page=all ]
Brett Porter closed MNG-940:
Assign To: Brett Porter
Resolution: Fixed
applied, thanks
assembly:unpack should support more archive types
--
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.07.txt
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.07.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.07.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
minor site improvements
---
Key: MNG-1092
URL: http://jira.codehaus.org/browse/MNG-1092
Project: Maven 2
Type: Task
Components: documentation
Reporter: Brett Porter
* The maven apache logo has links to 2 different places the logo on the
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.073001.txt
I gave you access. I can't figure out how to do it.
- Brett
Carlos Sanchez wrote:
I can't change the Issue Type Screen Scheme in JIRA for MEV to show
this text when somebody enters a new issue. Can somebody give me
rights or do it himself?
Please note that we don't have full knowledge of the
Better handling of figures
--
Key: MPPDF-52
URL: http://jira.codehaus.org/browse/MPPDF-52
Project: maven-pdf-plugin
Type: Improvement
Versions: 2.4
Environment: linux, maven 1.0.2, jdk1.4.2
Reporter: Arnaud Bailly
Priority:
Brett Porter wrote on Tuesday, October 04, 2005 8:43 PM:
here is the proposed new site:
http://people.apache.org/~brett/maven2-stage-site/
http://people.apache.org/~brett/maven-stage-site/
any final objections?
Set white as background color in the CSS. If the browser does not use white as
This is a good idea, and is the approach taken in Maven 2.
This is probably more suited to a tag library than a plugin, and it must
remain backwards compatible with the properties used previously instead
of replacing them with the new properties.
- Brett
Marcel May wrote:
Hi!
I noticed that
Anthony B. Coates wrote:
Hi. I'm trying to understand how the SCM Wagon is intended to work,
but it isn't sufficiently obvious to me from scanning the Java
source. Is there any design documentation anywhere that anyone can
point me to?
This was actually just a proof of concept, it hasn't
[ http://jira.codehaus.org/browse/MEV-3?page=comments#action_47843 ]
Mark Hobson commented on MEV-3:
---
What's the current situation with the nanocontainer pom? I see:
Good point. We do need this. What should happen is the report have some
way to indicate whether it generated something or not. It should always
be called, but if there aren't any sources it shouldn't generate and the
site plugin should not include it in the menu.
Can you file it in JIRA?
- Brett
[ http://jira.codehaus.org/browse/MEV-3?page=comments#action_47846 ]
Brett Porter commented on MEV-3:
unfortunately its not what they released:
http://dist.codehaus.org/nanocontainer/poms/nanocontainer-1.0-RC-2.pom
If they replace that file, it'll be fine.
[ http://jira.codehaus.org/browse/MEV-3?page=comments#action_47847 ]
Mark Hobson commented on MEV-3:
---
Right thanks, I'll take it to the nano list.
Broken dependencies for nanocontainer
-
Key: MEV-3
Ah, it was on some elements but I'd removed it forgetting to put it at
the top level.
Will do.
- Brett
Jörg Schaible wrote:
Brett Porter wrote on Tuesday, October 04, 2005 8:43 PM:
here is the proposed new site:
http://people.apache.org/~brett/maven2-stage-site/
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.09.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.09.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Hi,
We discussed this briefly before. From looking at that, this seems to be
the most workable solution:
- for any new features added in m1 or m2, we add a description to the
plugin site so that we have a comparitive checklist
- for any bugs fixed in m1 that potentially impact m2, when fixed,
(comments also added to the wiki).
I think we should layer this. We already have the parsers for the
reports, and could attach listeners that generate/update the metric data.
From there, we need an aggregation step (Which the reports need to do
also), and then the dashboard is a summary of those
Allow creation of the project and module files in a subdirectory
Key: MPIDEA-44
URL: http://jira.codehaus.org/browse/MPIDEA-44
Project: maven-idea-plugin
Type: Improvement
Versions: 1.6
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051005.09.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.09.txt
[ http://jira.codehaus.org/browse/MEV-3?page=comments#action_47848 ]
Joerg Schaible commented on MEV-3:
--
Well, see the linkesd issue (and the linked issues of this).
Broken dependencies for nanocontainer
-
[ http://jira.codehaus.org/browse/MEV-3?page=comments#action_47849 ]
Mark Hobson commented on MEV-3:
---
I saw that this issue was depended on by another issue, but not that this issue
had any prerequisites. Is that correct?
Broken dependencies for
[ ] install plugin 2.0-rc1
+1
[ ] deploy plugin 2.0-rc1
+0
[ ] assembly plugin 2.0-beta-2
+1
[ ] site plugin 2.0-beta-3
+1
[ ] javadoc 2.0-beta-2
+1
Cheers,
Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Improve Error Handling
--
Key: MNG-1093
URL: http://jira.codehaus.org/browse/MNG-1093
Project: Maven 2
Type: Improvement
Components: maven-eclipse-plugin
Versions: 2.0-beta-3
Reporter: Thomas Van de Velde
Priority: Minor
When
[ http://jira.codehaus.org/browse/MNG-1035?page=comments#action_47854 ]
Vincent Siveton commented on MNG-1035:
--
Which JDK version?
javadoc:javadoc exits with error due to white-space in C:\Documents and
Settings\user.m2 path
[ http://jira.codehaus.org/browse/MNG-1035?page=comments#action_47855 ]
Stephen Duncan Jr commented on MNG-1035:
Occurred to me on JDK1.5
javadoc:javadoc exits with error due to white-space in C:\Documents and
Settings\user.m2 path
Hi,
Currently you are forced to define the modelVersion for each pom, even when
declaring a parent. To me this seems to be a purely technical element that
is of limited interest to end users. Would it not make sense to provide a
default value (4.0.0) if not defined explicitly in the POM?
Cheers,
Brett,
You solved the problem! Works fine for me on IE (and firefox)
http://maven.apache.org/maven2/getting-started.html
Good work for the new CSS!
Regards,
Vincent
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 04, 2005 8:02 PM
To: Maven
[ http://jira.codehaus.org/browse/MNG-1035?page=comments#action_47860 ]
Indrajit Raychaudhuri commented on MNG-1035:
Sun Java SDK 1.5.0_04 on Windows XP SP2
I couldn't recreate this specific one on M2-b3 (I had cleaned my .m2 anyway).
So Rev
[ http://jira.codehaus.org/browse/MNG-587?page=comments#action_47861 ]
Karsten Blees commented on MNG-587:
---
What about simply loading the ruleset from file or URL? No need to mess with
classpaths or packaging config files into jars.
The format property
[ http://jira.codehaus.org/browse/MNG-1035?page=comments#action_47862 ]
Vincent Siveton commented on MNG-1035:
--
Seems to be the same pb that MNG-620
javadoc:javadoc exits with error due to white-space in C:\Documents and
Settings\user.m2 path
Such a default value would be bad karma, in the sense that you have no
indication which version of the POM (Schema) the POM instance was written
against. That stops you from doing intelligent support of legacy POMs,
especially if you make a non-backwards-compatible major version change.
[ http://jira.codehaus.org/browse/MNG-1035?page=comments#action_47865 ]
Indrajit Raychaudhuri commented on MNG-1035:
With a difference :)
In MNG-620 the problem is due to white-space in the path of javadoc.exe but
this one is due to white-space
[ http://jira.codehaus.org/browse/MPIDEA-39?page=comments#action_47866 ]
Geir H. Pettersen commented on MPIDEA-39:
-
I found that the this can be fixed easily by adding the type of project in the
iml file generated for the module:
For a java module
maven.src.dir != pom.build.sourceDirectory
--
Key: MAVEN-1706
URL: http://jira.codehaus.org/browse/MAVEN-1706
Project: Maven
Type: Bug
Components: documentation, core
Versions: 1.0.2
Reporter: Peter Lynch
Maven
But this is irrelevant for people not using legecy POM's (which I would
think is the great majority). What would be the inconvenience of having
defaut values? People wanting to use legacy poms just need to override
those.
Thomas
On 10/5/05, Anthony B. Coates [EMAIL PROTECTED] wrote:
Such a
Hi
I'm on developer list. I don't get any svn/continuum mails
today. I read about new mailing lists, but links to then
are not present on maven site. What's going on?
Thanks
Greg Slowikowski
Poland
The problem is that as soon as the *default* changes, the POM may
suddenly not work any longer.
I really don't see the problem. If you are after getting rid of
technical cruft, there is a lot of XML baggage that could be
eliminated by going to a simple properties file format. The problem
with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It will help avoid another problem like we're having right now in moving
from maven 1 POMs to maven 2 POMs, for one thing.
I understand wanting to streamline the amount of xml you have to write
for a new project, but surely 34 characters that don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Last night, we split out dev list into dev and commits. I thought
everyone was supposed to have been automatically subscribed to the new
list, but apparently this is not the case. You should be able to remedy
this with an email to:
mailto:[EMAIL
I just tried that and it said I was already a subscriber. Was the email
address in the SVN stuff updated correctly?
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 10:28
To: Maven Developers List
Subject: Re: Mailing list
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I forwarded this thread on to the guy (Roy Fielding, I think?) who did
the work last night, so we'll see what he says.
- -j
Allison, Bob wrote:
| I just tried that and it said I was already a subscriber. Was the
email address in the SVN stuff
I am just asking if it's possible. Now it seems that taking this out will
torpedo Maven. I am and end-user and I just want to understand why I need to
copy the same line of xml to each and every POM that I define. Sure, I don't
mind doing so but I was just wondering if we could do without.
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have you ever used java object serialization without specifying:
static final long serialVersionUID = somevalue;
then changed the class once you had some serialized data somewhere? This
version element has a similar purpose to serialVersionUID, and
Again, just wondering if it can be set to a default value within the M2 API
given that this is a very technical requirement that is not directly related
to the build configuration.
On 10/5/05, John Casey [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have you ever
Hi,
I can't connect to the m2 subversion repository (for last few hours) .
Is it down, or have I some problem ?
Thanks for answer.
best regards
JUBU
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Repositories' uniqueVersion tag is not inhertied to child POMs
Key: MNG-1094
URL: http://jira.codehaus.org/browse/MNG-1094
Project: Maven 2
Type: Bug
Components: maven-core
Versions: 2.0-beta-3
it's down
Emmanuel
Juraj Burian a écrit :
Hi,
I can't connect to the m2 subversion repository (for last few hours) .
Is it down, or have I some problem ?
Thanks for answer.
best regards
JUBU
-
To unsubscribe, e-mail:
Images do not show in xdoc documents that are nested in sub-folders
---
Key: MNG-1095
URL: http://jira.codehaus.org/browse/MNG-1095
Project: Maven 2
Type: Bug
Components: maven-site-plugin
[ http://jira.codehaus.org/browse/MNG-449?page=comments#action_47878 ]
John Casey commented on MNG-449:
I don't understand. I just tested this, and after installing
maven-projecthelp-plugin - with the plugin registry enabled - the new
projecthelp entry was
Sounds reasonable to me. Somebody wants to come up with a template for
the plugin feature list?
Concerning all the great work we've done recently (:)), it shouldn't be
too hard to extract the information from the entries in changes.xml.
Maybe this could be implemented as part of the changes
But you can't do this?:
version${project.parent.version}/version
Sure would be nice to be able to keep my versions in sync more easily
if I don't want to bother independently versioning
modules/sub-projects.
-Stephen
On 10/1/05, Brett Porter [EMAIL PROTECTED] wrote:
[ http://jira.codehaus.org/browse/MNG-1021?page=comments#action_47879 ]
John Casey commented on MNG-1021:
-
Ah HA! Found it.
This is caused by attached artifacts having their own metadata, which is
written when the artifact is deployed - over the top of the
[ http://jira.codehaus.org/browse/MNG-1049?page=comments#action_47881 ]
John Casey commented on MNG-1049:
-
the behavior of creating a dummy POM was dependent on the artifact resolution
process throwing an ArtifactResolutionException, which doesn't happen
[ http://jira.codehaus.org/browse/MNG-1021?page=comments#action_47882 ]
Arik Kfir commented on MNG-1021:
cool! Let me know as soon as you commit, I'll give it a try.
Thanks!
Build numbers are incremented when they shouldn't
I am trying to build my first plugin and having a problem.
I wrote a plugin which I can run as
sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi and that works
perfectly.
I want to set things up so I can reference the goal as hello:sayhi but
can't seem to get it to work. I added sample.plugin
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.164500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.164500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Allow the generation of the compiler output report although compilation fails
-
Key: MPJAVA-41
URL: http://jira.codehaus.org/browse/MPJAVA-41
Project: maven-java-plugin
Type: Improvement
What is it that fixed it? Can we close MPXDOC-101 now?
-Lukas
Vincent Siveton wrote:
Brett,
You solved the problem! Works fine for me on IE (and firefox)
http://maven.apache.org/maven2/getting-started.html
Good work for the new CSS!
Regards,
Vincent
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.17.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.17.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Error handling needs improvement
Key: MNG-1096
URL: http://jira.codehaus.org/browse/MNG-1096
Project: Maven 2
Type: Improvement
Components: maven-site-plugin
Versions: 2.0-beta-2
Reporter: David Jackman
I'm actually
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.173001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.173001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051005.173001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.173001.txt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it's probably trying to resolve RELEASE metadata for the plugin. By
default, the plugin version manager only works with defined versions (on
the CLI, as you mentioned, or with version/ in the client POM) and
RELEASE versions. You have two options
Subversion commit messages are sent to different lists
according to the following mapping
# Maven
[/maven]
for_paths = maven/
to_addr = commits at maven.apache.org
suppress_if_match = yes
[/maven/continuum]
for_paths = maven/continuum/
to_addr = continuum-commits at maven.apache.org
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.181500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.181500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[ http://jira.codehaus.org/browse/MNG-1021?page=all ]
John Casey closed MNG-1021:
---
Resolution: Fixed
Build numbers are incremented when they shouldn't
-
Key: MNG-1021
URL:
Tried the first option and that got it working. Thanks!
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 14:20
To: Maven Developers List
Subject: Re: [m20b3] Problems Getting My First Plugin to Work
-BEGIN PGP SIGNED MESSAGE-
[ http://jira.codehaus.org/browse/MNG-1049?page=all ]
John Casey closed MNG-1049:
---
Resolution: Fixed
factored stub-model creation out of the catch() clause for
ArtifactResolutionException when retreiving a POM from the repository, and
added a call to
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.183000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.183000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[ http://jira.codehaus.org/browse/CONTINUUM-276?page=all ]
Emmanuel Venisse closed CONTINUUM-276:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Done.
hook users and permissions into store configuration
MavenEmbedder.getLocalRepositoryDirectory() return null after start()
-
Key: MNG-1097
URL: http://jira.codehaus.org/browse/MNG-1097
Project: Maven 2
Type: Bug
Components: maven-embedder
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.190001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.190001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051005.190001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051005.190001.txt
When is a POM a legacy POM? The problem is that if you don't label the
POM version up front, *that* is how you end up with a legacy issue.
People will just lose track of the correct POM versions. The problem with
assumed values is that assumptions change over time.
Cheers, Tony.
On
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051005.191500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051005.191500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
1 - 100 of 175 matches
Mail list logo
