Re: [vote] PMD plugin 2.0-beta-1 release
+1 for 2.0-beta-1 Emmanuel Mike Perham a écrit : All outstanding JIRA issues have been closed so I'd like to suggest a new release. http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide &sorter/order=ASC&sorter/field=priority&pid=11140&fixfor=12176 Brett asks: - How does its functionality compare to Maven 1.0? Maven 1.x's PMD plugin is documented here: http://maven.apache.org/maven-1.x/reference/plugins/pmd/ The only thing I think is missing is more flexibility around the source files: source excluding, multiple source roots, etc. CPD was added today. The m1 plugin did not have the capability to generate non-html output which m2 does. - Is this a 2.0 release? Beta release? Personally I think it's a 2.0-beta-1. There are no tests currently so I would be hesitant to call this a quality release without some sort of test suite. mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No longer syncing Maven 1.x repository to Ibiblio
http://www.ibiblio.org/maven/ Emmanuel Felipe Leme a écrit : Hi Brett, Sorry for the stupid question (I haven't been following the lists for a while), but where is the old repo right now? My maven1 projects are failing because the http://www.ibiblio.org/maven/public/html/maven/ only have 2 sub-dires, maven and poms... -- Felipe On 1/8/06, Brett Porter <[EMAIL PROTECTED]> wrote: The rewrites are back in place, so I've turned off the sync of the m1 repo to ibiblio. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-667) Upload OSUser
Upload OSUser - Key: MAVENUPLOAD-667 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-667 Project: maven-upload-requests Type: Task Reporter: Emmanuel Venisse Assigned to: Carlos Sanchez -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONTINUUM-550) Auto login AKA "remember me on this computer" option
[ http://jira.codehaus.org/browse/CONTINUUM-550?page=comments#action_55101 ] Emmanuel Venisse commented on CONTINUUM-550: duplicate of CONTINUUM-513 > Auto login AKA "remember me on this computer" option > > > Key: CONTINUUM-550 > URL: http://jira.codehaus.org/browse/CONTINUUM-550 > Project: Continuum > Type: New Feature > Components: Web interface > Versions: 1.0.2 > Environment: Firefox/Internet explorer > Reporter: Geoffrey > Priority: Minor > > > On the login page it would be very handy to have a checkbox "Remember me (on > this computer)" or "Auto-login", similar to the one you see when logging into > jira. > If the user enables it, he is automatically logged in the next time. > Although this can be considered as a potiential hole in security of which the > user should be aware when enabling it, > it's very handy on a computer you consider to be secure. > Extra issue: it might be a good idea to ask the old password when changing > the password of the current user. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [vote] release doxia 1.0-alpha-7
+1 Emmanuel Brett Porter a écrit : Hi, There's been a bunch of changes for site 2.0, and the sink api now includes some classes for backwards compatibility after the package change that need to go into the Maven 2.0.2 release. I'd like to release 1.0 alpha 7 [ ] +1 [ ] +0 [ ] -1 72 Hours. Tick Tock. - Brett
Re: Continuum v1.0.2 on MacOSX - no startup
ports are define in apps/continuum/conf/application.xml Emmanuel Graham Leggett a écrit : Emmanuel Venisse wrote: It's a known issue with wrapper (http://jira.codehaus.org/browse/CONTINUUM-385) You can use bin/plexus.sh instead That was it, thank you. Having managed to start up the server, according to the docs I should be able to bind to a configuration server at port 8080. This port doesn't work (nothing is listening). The XMLRPC service on port 8000 has started up correctly. I also cannot find where the 8000 and the 8080 port numbers are configured in the config file (a grep for 8080 returns nothing). Can these values be changed? Regards, Graham --
[jira] Commented: (CONTINUUM-546) Translate Continuum interface
[ http://jira.codehaus.org/browse/CONTINUUM-546?page=comments#action_55012 ] Emmanuel Venisse commented on CONTINUUM-546: spanish : Alex Mayorga Adame french: Emmanuel Venisse > Translate Continuum interface > - > > Key: CONTINUUM-546 > URL: http://jira.codehaus.org/browse/CONTINUUM-546 > Project: Continuum > Type: Improvement > Components: Web interface > Reporter: Emmanuel Venisse > Fix For: 1.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-546) Translate Continuum interface
Translate Continuum interface - Key: CONTINUUM-546 URL: http://jira.codehaus.org/browse/CONTINUUM-546 Project: Continuum Type: Improvement Components: Web interface Reporter: Emmanuel Venisse Fix For: 1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-531) Add back the "build now" button on the "view project" page.
[ http://jira.codehaus.org/browse/CONTINUUM-531?page=comments#action_55005 ] Emmanuel Venisse commented on CONTINUUM-531: trygvis: IMO next to edit, but it might fit elsewhere > Add back the "build now" button on the "view project" page. > --- > > Key: CONTINUUM-531 > URL: http://jira.codehaus.org/browse/CONTINUUM-531 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.2 > Reporter: Trygve Laugstol > Assignee: nick gonzalez > Fix For: 1.1-alpha-1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: wagon testing
I tested it with maven-scm and it seems to works fine. It's the first time i can deploy the whole project in one command. Thanks brett Emmanuel Brett Porter a écrit : (as sent to users@) In the lead up to the 2.0.2 release, I'd like anyone experiencing: [WAGONSSH-28] session is down [WAGONSSH-30] hangs during deployment to test the following wagon snapshots: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0-alpha-6-SNAPSHOT/wagon-ssh-1.0-alpha-6-20060105.062346-2.jar by including it in your $M2_HOME/lib directory. Please also include: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6-SNAPSHOT/wagon-provider-api-1.0-alpha-6-20060105.062346-7.jar and http://www.ibiblio.org/maven2/com/jcraft/jsch/0.1.24/jsch-0.1.24.jar Replace any existing wagon/jsch libraries. Another way to test is to pick up the following integration build instead: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060105.071501.tar.gz With this build, you can also test scpexe and sftp if you were having any problems with them. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] more m1 plugin releases
+1 Emmanuel Lukas Theussl a écrit : Hi all, The following m1 plugins all have zero issues open: [] faq [] multichanges [] clean [] genapp and I would like to release them for inclusion in m1.1-beta-3. The future documentation is here: http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/faq/ http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/multichanges/ http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/clean/ http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/genapp/ The genapp plugin is the only one with major changes since the last release, I'd appreciate if someone could have a closer look at it. Here's my +1 and 72h to go. Thanks, Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-532) Add ability to move from a particular build to the build list for a project.
[ http://jira.codehaus.org/browse/CONTINUUM-532?page=all ] Emmanuel Venisse closed CONTINUUM-532: -- Assign To: Emmanuel Venisse Resolution: Fixed Fixed. > Add ability to move from a particular build to the build list for a project. > > > Key: CONTINUUM-532 > URL: http://jira.codehaus.org/browse/CONTINUUM-532 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.2 > Reporter: Trygve Laugstol > Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-531) Add back the "build now" button on the "view project" page.
[ http://jira.codehaus.org/browse/CONTINUUM-531?page=comments#action_54861 ] Emmanuel Venisse commented on CONTINUUM-531: It isn't in template page (http://people.apache.org/~brett/white-site/viewProject.html). Where do you want it? > Add back the "build now" button on the "view project" page. > --- > > Key: CONTINUUM-531 > URL: http://jira.codehaus.org/browse/CONTINUUM-531 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.2 > Reporter: Trygve Laugstol > Fix For: 1.1-alpha-1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [vote] release maven-deploy-plugin 2.1
+1 Emmanuel Brett Porter a écrit : All scheduled issues in JIRA have been completed. Please test the published snapshot. [ ] +1 [ ] +0 [ ] -1 Release will proceed in 72 hours if vote carries. NB: The only change is the inclusion of the deploy:deploy-file mojo. Most of the issues filed actually must be addressed in wagon, which this release is independent of. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-install-plugin 2.1
+1 Emmanuel Brett Porter a écrit : All issues in JIRA have been completed. Please test the published snapshot. [ ] +1 [ ] +0 [ ] -1 Release will proceed in 72 hours if vote carries. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: working on and prioritizing dev issues
Jason van Zyl a écrit : Jesse McConnell wrote: Oh, I was thinking that the crux of this email was trying to determine was 'Where should these things be discussed?' Email is the classic traditional place to do it, but discussions have been getting dropped on here and Jira was a proposed solution. Perhaps someone just needs to keep bumping these discussion topics up :) The discussion of what to resolve will happen on the list or in irc but then get populated in JIRA so that what's up for discussion gets captured. JIRA can ping the list with unresolved issues and as we are discussing the issues I think someone needs to act as secretary and capture the salient ideas in the wiki. So for the dev process stuff I created a document and steward that document to completion. I think the same would go with the integration tests where this is something that Vincent is keen to resolve so he can be the secretary for that issue (if that's ok Vincent). So I think the flow becomes - everyone pushes issues they want resolved into JIRA - we prioritize a short list to work on in a particular week (or whatever), we can use votes or just decide amongst ourselves with that short list we: - pick the issue at hand - burst of discussion on the list - secretary captures the salient points - offers up the document for review - go back to discussion/capture/review until complete - a final document then accompanies the resolution and the issue is closed If that seems reasonable I can create a little doc for this :-) +1 Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: working on and prioritizing dev issues
So, we should combine our technologies: - discussion starts on [EMAIL PROTECTED] - poster decides it requires further discussion (most likely the original poster, possibly at same time as posting). Adds the issue to JIRA, under MNG (or relevant project, eg CONTINUUM, or MPA if it is the dev process), component = design where necessary, target version where appropriate (eg a Maven 2.1 design discussion) - when discussion reaches a suitable point (may start this way), a proposal is put on the wiki - discussion is regularly used to update the wiki page. - if discussion goes in circles and no agreement is being reached because its hard to communicate given the time lag on email, a breakout on IRC is arranged, logged, summarised and posted to the list, with the wiki updated. Further discussion may ensue. The creation of a JIRA item and the relevant wiki page requires that an issue needs a champion. This should be the original poster, but others can agree to do that, and anyone can update the wiki or JIRA if they feel that is appropriate. The champion does not have to be a committer - anyone can propose and follow through on design discussions. +1 Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: working on and prioritizing dev issues
Jason van Zyl a écrit : Hi, Of late I think many issues are coming up on the lists and we're not dealing with resolving them effectively because, as is natural, people have different priorities or are generally just thinking about different things that may be interesting or pressing. The three things of late I can think of is the development process thread, the integration testing thread, and a discussion of best practices which fell by the way side a month ago. So I intentionally picked up Brett's start at codifying the dev process so that at least two of us are on the same page and try and use that momentum to draw other people into the discussion. I talked to a couple of subversion developers (thanks to Garrett Rooney and Paul Querna), read Pragmatic Version Control, talked to Jesse and Brett and found what useful links I could find. I put it all together here: http://docs.codehaus.org/display/MAVEN/Development+Process I'm totally agree with this doc. Just a little comment about it: in several place, we have "svn copy" and mvn release:prepare release:perform". Do you consider them as two possible actions? because release prepare already do the copy. After this I think we should deal with the integration test issues, and then I'd like to work through the best practices listed in the wiki: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10500&sorter/order=DESC&sorter/field=priority&resolution=-1&component=11896 I'm not sure what would work best in terms of keeping the threads of thought visible when they pass out of the current thread on the mailing list but here's my idea based on notions in David Allen's "Getting Things Done" which is a fairly practical way of working through a series of issues. It basically boils down to collecting all issues that are important, putting those notions somewhere safe and then prioritizing them so they can be worked on. This is a little different where it's not an individual but a group of people but we can use JIRA to collect the issues and maybe the devs can vote to try and give some priority to the list. I like the idea to use jira for summarize issues. We can use it for little comment, but the dev list is better for big issue discussion, we'll can put in issue the link of mail thread. Once the priority is set then as a group we work through the issues and try to work through them one to three issues at a time and stick with them until we have a resolution. What I would like is a way for anyone interested to be able to pick up immediately and help. I'm all open to ideas but I don't think we're dealing effectively with our own issues because we have no locus to work because the email list is too hard to keep track of for a lot of people. Maybe something other then JIRA would work but we need to collect, store safely, prioritize the short list of issues and anyone who wants to see where we are in resolving those issues should be able to see in a few minutes where we are. I think it would be easy enough to setup a JIRA project and try it. If it doesn't work then we'll look for something else. I know this type of setup definitely helps me for issues tracked at the Maven TLP level: http://jira.codehaus.org/browse/MPA Any thoughts? At any rate I think the short list now is: 1. Dev process 2. Integration Testing 3. Prioritize best practices and start picking them off agree. Of course anyone is free to modify this list before a decision is made on priority. Just trying to get the ball rolling, and hopefully keep it rolling. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release surefire plugin 2.1.2 and surefire 1.5.2
+1 surefire-booter too? Emmanuel Carlos Sanchez a écrit : Hi, I'd like to propose a new release of the surefire plugin 2.1.2 with related dependencies (surefire and surefire booter 1.5.2) Changelogs: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10541&fixfor=12213 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11148&fixfor=12206 Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release antrun plugin 1.1
+1 Emmanuel Carlos Sanchez a écrit : Hi, I'd like to propose the release of the antrun plugin I'd like to see MANTRUN-32 fixed but in the meantime a release is needed. Changelog (since a jira project was created): http://tinyurl.com/bxcvd Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-401) cannot delete project (stuck on 'in progress')
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=all ] Emmanuel Venisse closed CONTINUUM-401: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0.2 Fixed by CONTINUUM-478 > cannot delete project (stuck on 'in progress') > -- > > Key: CONTINUUM-401 > URL: http://jira.codehaus.org/browse/CONTINUUM-401 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: running on linux debian > trying to access from winXP > Reporter: Adam Kiezun > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > Attachments: palulustuck.JPG, wrapper-2005-11-25.log, wrapper-2005-12-21.log > > > one of my projects got stuck in the 'in progress' state and cannot be deleted > from the web interface. > it's been in this state for > 24 hrs so it seems permanent. > attaching screenshot. > let me know if i should attach a log (and which one) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-541) Problems running multi-module build with maven2
[ http://jira.codehaus.org/browse/CONTINUUM-541?page=comments#action_54769 ] Emmanuel Venisse commented on CONTINUUM-541: There was a problem with schedules in 1.0.2. The fix is there : http://beaver.codehaus.org/~evenisse/continuum-core-1.1-SNAPSHOT.jar copy it in continuum/apps/continuum/lib and remove old continuum-core jar > Problems running multi-module build with maven2 > --- > > Key: CONTINUUM-541 > URL: http://jira.codehaus.org/browse/CONTINUUM-541 > Project: Continuum > Type: Task > Components: Web interface > Versions: 1.0.1 > Environment: linux debian > Reporter: Wolfgang Klein > > > Hello! > Maybe a similar problem has been posted, but i´ve got > problems running a multi-module maven2 build. > I´ve uploaded a small pom hirachy per URL as recommended, > the initialization of the sub modules in continuum has worked as wanted, > all poms defined in the modules element (below!) are located correctly. > The root pom has packaging type "pom" and a few modules are > included in the pom´s 'modules' element. > > > ../../signatur > ../library > ../weblib > ../portal > ../appserver/serverapp/Base > ../appserver/serverapp/UserManagement > ../appserver/serverapp/TemplateBeans > ../release/xml/infosets > ../release/xml/udFields > > > When i run the build, following exception occurs: > Reason: Could not find the model file > '/home/maven/tmp/continuum-1.0.1/apps/continuum/working-directory/37/../../signatur/pom.xml'. > > Since continuum creates a flat directory structure with automatically created > numbers as folder names, the corresponding > module can not be found at this location and the build stops. > My question is, if there is a way to determine the checkout folder, or have i > misunderstood anything? > I would be glad to establish continuum im my company, but i´m running out of > time. > Would be nice, if someone can give me an advice. > Greetings, > Wolfgang Klein -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [vote] Create a maven-sources-plugin for m1
+1 Emmanuel Arnaud HERITIER a écrit : Hi all, It seems useful for some users to have a maven-sources-plugin for m1. http://jira.codehaus.org/browse/MAVEN-1736 Are you agree if we add it in the m1 plugins ? [ ] +1 - It seems to be a good idea. [ ] +0 - Don't know [ ] -1 - No, I prefer . Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MSUREFIRE-38) Surefire plugin is failing
[ http://jira.codehaus.org/browse/MSUREFIRE-38?page=all ] Emmanuel Venisse closed MSUREFIRE-38: - Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 2.1.2 Fixed. > Surefire plugin is failing > -- > > Key: MSUREFIRE-38 > URL: http://jira.codehaus.org/browse/MSUREFIRE-38 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: maven-surefire-plugin-2.1.2-20060102.001705-3 > Reporter: Vincent Massol > Assignee: Emmanuel Venisse > Fix For: 2.1.2 > > > C:\dev\maven\trunks\plugins\maven-clover-plugin>mvn clean install > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Clover Plugin > [INFO]task-segment: [clean, install] > [INFO] > > [INFO] snapshot org.apache.maven.plugins:maven-clean-plugin:2.0.1-SNAPSHOT: > checking for updates from snapshots > [INFO] [clean:clean] > [INFO] Deleting directory > C:\dev\maven\trunks\plugins\maven-clover-plugin\target > [INFO] snapshot org.apache.maven.plugins:maven-plugin-plugin:2.0.1-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.apache.maven.plugins:maven-resources-plugin:2.2-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot > org.apache.maven.plugins:maven-compiler-plugin:2.0.1-SNAPSHOT: checking for > updates from snapshots > [INFO] snapshot > org.apache.maven.plugins:maven-surefire-plugin:2.1.2-SNAPSHOT: checking for > updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.2-SNAPSHOT/maven-surefi > re-plugin-2.1.2-20060102.001705-3.pom > 2K downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.2-SNAPSHOT/maven-surefi > re-plugin-2.1.2-20060102.001705-3.jar > 8K downloaded > [INFO] snapshot org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.apache.maven.plugins:maven-install-plugin:2.1-SNAPSHOT: > checking for updates from snapshots > [INFO] [plugin:descriptor] > [INFO] Using 2 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 4 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [WARNING] > Artifact junit:junit:jar:3.8.1 retains local scope 'test' overriding > broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] snapshot org.codehaus.plexus:plexus-compiler-javac:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compilers:1.6-SNAPSHOT: checking > for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler:1.6-SNAPSHOT: checking > for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler-api:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler-manager:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] [compiler:compile] > Compiling 5 source files to > C:\dev\maven\trunks\plugins\maven-clover-plugin\target\classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 1 source file to > C:\dev\maven\trunks\plugins\maven-clover-plugin\target\test-classes > [INFO] snapshot org.apache.maven.surefire:surefire:1.5.2-SNAPSHOT: checking > for updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire/1.5.2-SNAPSHOT/surefire-1.5.2-20060101. > 232902-4.pom > 751b downloaded > [INFO] snapshot org.apache.maven.surefire:surefire-booter:1.5.2-SNAPSHOT: > checking for updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire-booter/1.5.2-SNAPSHOT/surefire-booter-1 > .5.2-20060102.001256-4.pom > 805b downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire/1.5.2-SNAPSHOT/surefire-1.5.2-20060101. > 232902-4.jar > 60K downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire-booter/1.5.2-SNAPSHOT/surefire-booter-1 &
[jira] Commented: (MSUREFIRE-38) Surefire plugin is failing
[ http://jira.codehaus.org/browse/MSUREFIRE-38?page=comments#action_54669 ] Emmanuel Venisse commented on MSUREFIRE-38: --- works fine for me. Do you have latest snapshot surefire plugin? > Surefire plugin is failing > -- > > Key: MSUREFIRE-38 > URL: http://jira.codehaus.org/browse/MSUREFIRE-38 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: maven-surefire-plugin-2.1.2-20060102.001705-3 > Reporter: Vincent Massol > > > C:\dev\maven\trunks\plugins\maven-clover-plugin>mvn clean install > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Clover Plugin > [INFO]task-segment: [clean, install] > [INFO] > > [INFO] snapshot org.apache.maven.plugins:maven-clean-plugin:2.0.1-SNAPSHOT: > checking for updates from snapshots > [INFO] [clean:clean] > [INFO] Deleting directory > C:\dev\maven\trunks\plugins\maven-clover-plugin\target > [INFO] snapshot org.apache.maven.plugins:maven-plugin-plugin:2.0.1-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.apache.maven.plugins:maven-resources-plugin:2.2-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot > org.apache.maven.plugins:maven-compiler-plugin:2.0.1-SNAPSHOT: checking for > updates from snapshots > [INFO] snapshot > org.apache.maven.plugins:maven-surefire-plugin:2.1.2-SNAPSHOT: checking for > updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.2-SNAPSHOT/maven-surefi > re-plugin-2.1.2-20060102.001705-3.pom > 2K downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.2-SNAPSHOT/maven-surefi > re-plugin-2.1.2-20060102.001705-3.jar > 8K downloaded > [INFO] snapshot org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.apache.maven.plugins:maven-install-plugin:2.1-SNAPSHOT: > checking for updates from snapshots > [INFO] [plugin:descriptor] > [INFO] Using 2 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 4 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [WARNING] > Artifact junit:junit:jar:3.8.1 retains local scope 'test' overriding > broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] snapshot org.codehaus.plexus:plexus-compiler-javac:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compilers:1.6-SNAPSHOT: checking > for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler:1.6-SNAPSHOT: checking > for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler-api:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler-manager:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] [compiler:compile] > Compiling 5 source files to > C:\dev\maven\trunks\plugins\maven-clover-plugin\target\classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 1 source file to > C:\dev\maven\trunks\plugins\maven-clover-plugin\target\test-classes > [INFO] snapshot org.apache.maven.surefire:surefire:1.5.2-SNAPSHOT: checking > for updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire/1.5.2-SNAPSHOT/surefire-1.5.2-20060101. > 232902-4.pom > 751b downloaded > [INFO] snapshot org.apache.maven.surefire:surefire-booter:1.5.2-SNAPSHOT: > checking for updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire-booter/1.5.2-SNAPSHOT/surefire-booter-1 > .5.2-20060102.001256-4.pom > 805b downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire/1.5.2-SNAPSHOT/surefire-1.5.2-20060101. > 232902-4.jar > 60K downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire-booter/1.5.2-SNAPSHOT/surefire-booter-1 > .5.2-20060102.001256-4.jar > 10K downloaded > [INFO] [surefire:test] &g
[jira] Commented: (CONTINUUM-536) Show the elapsed time in addition to the start and end times.
[ http://jira.codehaus.org/browse/CONTINUUM-536?page=comments#action_54423 ] Emmanuel Venisse commented on CONTINUUM-536: why "project list" and project view"? start and end time are in build results page. > Show the elapsed time in addition to the start and end times. > - > > Key: CONTINUUM-536 > URL: http://jira.codehaus.org/browse/CONTINUUM-536 > Project: Continuum > Type: Improvement > Versions: 1.0, 1.0.1, 1.0.2 > Reporter: Trygve Laugstol > > > Affects at least the "project list" and "project" views. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (CONTINUUM-496) End Time contains junk value when I forced a build to run
[ http://jira.codehaus.org/browse/CONTINUUM-496?page=all ] Emmanuel Venisse reopened CONTINUUM-496: it seens that isn't fixed correctly > End Time contains junk value when I forced a build to run > - > > Key: CONTINUUM-496 > URL: http://jira.codehaus.org/browse/CONTINUUM-496 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Reporter: John Sisson > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.1-alpha-1 > > > The following is from the build history when it was building. Note the end > time on the first line: > Dec 1, 2005 10:23:11 PM Dec 31, 1969 4:00:00 PM > BuildingResult > 22Dec 1, 2005 10:00:18 PM Dec 1, 2005 10:06:51 PM Success > Result > 21Dec 1, 2005 7:00:16 PM Dec 1, 2005 7:03:57 PM Success Result > This occurred on http://ci.gbuild.org/continuum/servlet/continuum running a > 1.1-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-496) End Time contains junk value when I forced a build to run
[ http://jira.codehaus.org/browse/CONTINUUM-496?page=all ] Emmanuel Venisse updated CONTINUUM-496: --- Fix Version: (was: 1.0.2) 1.1-alpha-1 > End Time contains junk value when I forced a build to run > - > > Key: CONTINUUM-496 > URL: http://jira.codehaus.org/browse/CONTINUUM-496 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Reporter: John Sisson > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.1-alpha-1 > > > The following is from the build history when it was building. Note the end > time on the first line: > Dec 1, 2005 10:23:11 PM Dec 31, 1969 4:00:00 PM > BuildingResult > 22Dec 1, 2005 10:00:18 PM Dec 1, 2005 10:06:51 PM Success > Result > 21Dec 1, 2005 7:00:16 PM Dec 1, 2005 7:03:57 PM Success Result > This occurred on http://ci.gbuild.org/continuum/servlet/continuum running a > 1.1-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-528) Weird timestamp when running build is logged for end dtime
[ http://jira.codehaus.org/browse/CONTINUUM-528?page=all ] Emmanuel Venisse closed CONTINUUM-528: -- Resolution: Duplicate duplicate with CONTINUUM-496 > Weird timestamp when running build is logged for end dtime > -- > > Key: CONTINUUM-528 > URL: http://jira.codehaus.org/browse/CONTINUUM-528 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Reporter: David Eric Pugh > Priority: Minor > Attachments: funnydtime.png > > > when doing a build, the currently happening build has an enddtime that is > weird: Dec 31, 1969 7:00:00 PM -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Releasing Clover plugin 2.0
+1 Emmanuel Vincent Massol a écrit : 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 was very buggy and non-working. Please cast your votes. Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-519) scheduler not calling scm's update command at scheduled time
[ http://jira.codehaus.org/browse/CONTINUUM-519?page=all ] Emmanuel Venisse closed CONTINUUM-519: -- Assign To: Emmanuel Venisse Resolution: Fixed Applied. Thanks. > scheduler not calling scm's update command at scheduled time > > > Key: CONTINUUM-519 > URL: http://jira.codehaus.org/browse/CONTINUUM-519 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Environment: xp, starteam > Reporter: Dan Tran > Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-1 > Attachments: CONTINUUM-519.patch > > > The log shows the timer fires correctly but no attempt to call scm's update > command to detect changes > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - < > Continuum 1.0.2 started! > > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >\ ^__^ > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > \ (oo)\___ > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >(__)\ )\/\ > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >||w | > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >|| || > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > 4641 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.initialization.ContinuumInitializer - Continuum > initializer running ... > 4985 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Activating > schedules ... > 5016 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Mon Dec 19 > 05:00:00 PST 2005 > 5016 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Tue Dec 20 > 00:01:00 PST 2005 > 5016 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Thu Jan 01 > 10:15:00 PST 2099 > 5016 [WrapperSimpleAppMain] INFO org.codehaus.plexus.PlexusContainer - > Loading on start [role,roleHint]: > [org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor,build-project] > 5344 [WrapperSimpleAppMain] ERROR > org.codehaus.plexus.velocity.VelocityComponent - > ResourceManager.getResource() parse exception: > org.apache.velocity.exception.ParseErrorException: Lexical error: > org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 121, > column 17. Encountered: after : "" > 5438 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.notifier.Notifier:mail - The from mailbox > is not configured, will use the nag email address from the project. > 5438 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.notifier.Notifier:mail - From name: > Continuum > 5438 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.notifier.Notifier:mail - Build host name: > uscus-build2 > 5563 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.RecipientSource - To override address is > not configured, will use the nag email address from the project. > 5578 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - > Starting task executor, thread name 'build-project'. > 5578 [WrapperSimpleAppMain] INFO org.codehaus.plexus.PlexusContainer - > Loading on start [role,roleHint]: > [org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor,check-out-project] > 5578 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:check-out-project > - Starting task executor, thread name 'check-out-project'. > 2151003 [scheduler1_Worker-8] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - > >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)... > 2151112 [scheduler1_Worker-8] INFO > org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3 > 5750995 [scheduler1_Worker-7] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - > >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)... > 5750995 [scheduler1_Worker-7] INFO > org.apache.maven.
[jira] Commented: (CONTINUUM-175) package continuum as a war
[ http://jira.codehaus.org/browse/CONTINUUM-175?page=comments#action_53914 ] Emmanuel Venisse commented on CONTINUUM-175: nick: applied. > package continuum as a war > -- > > Key: CONTINUUM-175 > URL: http://jira.codehaus.org/browse/CONTINUUM-175 > Project: Continuum > Type: New Feature > Components: Web interface > Reporter: Ryan Sonnek > Fix For: 1.1-alpha-1 > Attachments: continuum-addproject.zip > > > the current bundling of continuum with a web server is convenient, but for > organizations that already have a webserver setup, a WAR file would be the > most convenient. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPA-34) Process Mike Perham
[ http://jira.codehaus.org/browse/MPA-34?page=comments#action_53867 ] Emmanuel Venisse commented on MPA-34: - account is created. Need to grant karma to maven-scm and maven plugins > Process Mike Perham > --- > > Key: MPA-34 > URL: http://jira.codehaus.org/browse/MPA-34 > Project: Maven Project Administration > Type: Task > Components: new-commiters > Reporter: Emmanuel Venisse > Assignee: Jason van Zyl > > > Preferred userid: mperham > Full name: Mike Perham > Forwarding email address: [EMAIL PROTECTED] > Requested UNIX groups: maven > Vote thread: > http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200512.mbox/[EMAIL > PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-643) Upload ExtremeComponents 1.0.1-M3
Upload ExtremeComponents 1.0.1-M3 - Key: MAVENUPLOAD-643 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-643 Project: maven-upload-requests Type: Task Reporter: Emmanuel Venisse eXtremeComponents is a jsp dynamically generated table. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPA-34) Process Mike Perham
[ http://jira.codehaus.org/browse/MPA-34?page=comments#action_53732 ] Emmanuel Venisse commented on MPA-34: - account request sended > Process Mike Perham > --- > > Key: MPA-34 > URL: http://jira.codehaus.org/browse/MPA-34 > Project: Maven Project Administration > Type: Task > Components: new-commiters > Reporter: Emmanuel Venisse > Assignee: Jason van Zyl > > > Preferred userid: mperham > Full name: Mike Perham > Forwarding email address: [EMAIL PROTECTED] > Requested UNIX groups: maven > Vote thread: > http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200512.mbox/[EMAIL > PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPA-34) Process Mike Perham
[ http://jira.codehaus.org/browse/MPA-34?page=comments#action_53730 ] Emmanuel Venisse commented on MPA-34: - CLA was faxed > Process Mike Perham > --- > > Key: MPA-34 > URL: http://jira.codehaus.org/browse/MPA-34 > Project: Maven Project Administration > Type: Task > Components: new-commiters > Reporter: Emmanuel Venisse > Assignee: Jason van Zyl > > > Preferred userid: mperham > Full name: Mike Perham > Forwarding email address: [EMAIL PROTECTED] > Requested UNIX groups: maven > Vote thread: > http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200512.mbox/[EMAIL > PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPA-34) Process Mike Perham
Process Mike Perham --- Key: MPA-34 URL: http://jira.codehaus.org/browse/MPA-34 Project: Maven Project Administration Type: Task Components: new-commiters Reporter: Emmanuel Venisse Assigned to: Jason van Zyl Preferred userid: mperham Full name: Mike Perham Forwarding email address: [EMAIL PROTECTED] Requested UNIX groups: maven Vote thread: http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200512.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (SCM-13) Investigate pure Java SVN interface
[ http://jira.codehaus.org/browse/SCM-13?page=comments#action_53704 ] Emmanuel Venisse commented on SCM-13: - it will be the default implementation. > Investigate pure Java SVN interface > --- > > Key: SCM-13 > URL: http://jira.codehaus.org/browse/SCM-13 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-svn > Reporter: Brett Porter > > > There is this: http://tmate.org/svn/ > I'd say javahl is out because it requires native binaries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [vote] release maven-rar-plugin 2.0.1
+1 Emmanuel Stephane Nicoll a écrit : Hi guys, First of all, I don't know if I am allowed to call for a vote but anyway ... The following has been fixed since 2.0: * MNG-1296: checking for optional artifact * MNG-1681: could not install the artifact (annoying!) Users are actually using the plugin and MNG-1681 seems quite major. Here's my +1 Cheers, Stéphane -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (SCM-85) Allow svn username/password to be set in servers section of settings.xml
[ http://jira.codehaus.org/browse/SCM-85?page=comments#action_53558 ] Emmanuel Venisse commented on SCM-85: - sure, maven-scm is independant from maven, it doesn't know settings.xml, but maven-scm-plugin can use it because is dependant from maven like you do it for starteam > Allow svn username/password to be set in servers section of settings.xml > > > Key: SCM-85 > URL: http://jira.codehaus.org/browse/SCM-85 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-svn > Reporter: Micah Schehl > Attachments: MNG-85-maven-scm.patch, SCM-85.patch > > > Allow developers to have their own subversion username/password set in > settings.xml.Also, this would prevent having to use the web setup to > enter username/password in Continuum since the info would be in settings.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (CONTINUUM-506) Fix typos and formatting in site docs and add faq entry about changing ports
[ http://jira.codehaus.org/browse/CONTINUUM-506?page=all ] Emmanuel Venisse reassigned CONTINUUM-506: -- Assign To: Emmanuel Venisse > Fix typos and formatting in site docs and add faq entry about changing ports > > > Key: CONTINUUM-506 > URL: http://jira.codehaus.org/browse/CONTINUUM-506 > Project: Continuum > Type: Improvement > Components: Documentation > Reporter: Dennis Lundberg > Assignee: Emmanuel Venisse > Priority: Minor > Attachments: faq-problem.jpg, site-improvements.patch > > > Updated the site documents by fixing typos and adding some formatting where I > thought it was appropiate. > Also added an FAQ entry: "How can I run Continuum on a different port?" > Note: I had some trouble generating the site using the released version of > Maven 2. When issuing the command > mvn -U site > some pages looked weird, even in sections that I had not touched. The pages > are the ones using the fml format, i.e. about.fml and faq.fml. The problem > appears when using the "source" element more than once within the same > "answer" element. This might be a bug in the site plugin for Maven 2. Please > advise me if I should open an issue for this for maven-site-plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1819) StringIndexOutOfBoundsException when running maven
[ http://jira.codehaus.org/browse/MNG-1819?page=comments#action_53491 ] Emmanuel Venisse commented on MNG-1819: --- the workaround is to modify all environment variables with carriage return. > StringIndexOutOfBoundsException when running maven > -- > > Key: MNG-1819 > URL: http://jira.codehaus.org/browse/MNG-1819 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Environment: win xp, cygwin > Reporter: Dan Diephouse > Assignee: John Casey > Fix For: 2.0.2 > > > Just trying out 2.0.1 and I am getting this message below. any ideas? > $ mvn.bat > [WARNING] Failed to initialize environment variable resolver. Skipping > environment substitution in settings. > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] String index out of range: -1 > [INFO] > > [INFO] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 >at java.lang.String.substring(String.java:1768) >at > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:188) >at > org.codehaus.plexus.util.interpolation.EnvarBasedValueSource.(EnvarBasedValueSource.java:16) >at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:86) >at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:725) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:632) >at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) >at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) >at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) >at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >at java.lang.reflect.Method.invoke(Method.java:585) >at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Mon Dec 12 16:50:03 PST 2005 > [INFO] Final Memory: 1M/2M > [INFO] > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (SCM-110) Perforce should force sync
[ http://jira.codehaus.org/browse/SCM-110?page=all ] Emmanuel Venisse closed SCM-110: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. > Perforce should force sync > -- > > Key: SCM-110 > URL: http://jira.codehaus.org/browse/SCM-110 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Reporter: mike perham > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: force2.txt > > > It's not pretty but it's the only way to get sync to work when files could be > deleted from the filesystem (e.g. mvn clean). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [vote] Release Maven 2.0.1-1 critical bugfix version
+1 I'd prefer too 2.0.2 I added MNG-1841 because it's blocker for site generation. All our reports are empty in maven site (http://maven.apache.org/maven-reports.html) Emmanuel John Casey a écrit : Hi all, If you've been watching this list, the users list, or JIRA, I'm sure you've noticed that we managed to introduce some new bugs in 2.0.1. Some of these are critical, and will block the use of this version. What I'd like to do is release a bugfix version, 2.0.1-1, to address these critical issues. I've opened a new version on the Maven roadmap in JIRA (http://jira.codehaus.org/browse/MNG) to track these. Currently there are two, and I don't expect that number to climb much more. Please note, this release is only for critical bugs. We're not going to be fixing anything that we can limp along without for a bit longer. Because of the hurried nature of this vote, this email thread will undoubtedly serve as a mechanism for determining which issues are critical to release here; I will make sure JIRA reflects this discussion. Here is my +1. Sincerely, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1841) maven-site-plugin break maven-javadoc-plugin JavaDocs
[ http://jira.codehaus.org/browse/MNG-1841?page=all ] Emmanuel Venisse updated MNG-1841: -- Fix Version: 2.0.1-1 > maven-site-plugin break maven-javadoc-plugin JavaDocs > - > > Key: MNG-1841 > URL: http://jira.codehaus.org/browse/MNG-1841 > Project: Maven 2 > Type: Bug > Components: maven-site-plugin > Environment: maven-site-plugin-2.0-beta-4 > Solaris 5.8SP4 > Maven 2.0/2.0.1 > Reporter: Alex Mayorga Adame > Fix For: 2.0.1-1 > Attachments: javadoc-javadoc-index.html, site-javadoc-index.html > > > When mvn javadoc:javadoc is used > \target\docs\apidocs\index.html is created with correct javadocs. > but when mvn site:site is used > \target\site\apidocs\index.html is created with a JavaDoc link to an empty > page. I believe the $bodyContent is not correctly handled by site-plugin. > Attached both pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1824) Add the possibility to filter webapp files
Add the possibility to filter webapp files -- Key: MNG-1824 URL: http://jira.codehaus.org/browse/MNG-1824 Project: Maven 2 Type: Improvement Components: maven-war-plugin Reporter: Emmanuel Venisse Fix For: 2.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1819) StringIndexOutOfBoundsException when running maven
[ http://jira.codehaus.org/browse/MNG-1819?page=comments#action_53341 ] Emmanuel Venisse commented on MNG-1819: --- Do you have a line without '=' when you run set and/or env command? > StringIndexOutOfBoundsException when running maven > -- > > Key: MNG-1819 > URL: http://jira.codehaus.org/browse/MNG-1819 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Environment: win xp, cygwin > Reporter: Dan Diephouse > > > Just trying out 2.0.1 and I am getting this message below. any ideas? > $ mvn.bat > [WARNING] Failed to initialize environment variable resolver. Skipping > environment substitution in settings. > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] String index out of range: -1 > [INFO] > > [INFO] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 >at java.lang.String.substring(String.java:1768) >at > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:188) >at > org.codehaus.plexus.util.interpolation.EnvarBasedValueSource.(EnvarBasedValueSource.java:16) >at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:86) >at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:725) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:632) >at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) >at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) >at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) >at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >at java.lang.reflect.Method.invoke(Method.java:585) >at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Mon Dec 12 16:50:03 PST 2005 > [INFO] Final Memory: 1M/2M > [INFO] > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (SCM-5) Create user guide/Guide for the impatient programmer (gipper)
[ http://jira.codehaus.org/browse/SCM-5?page=all ] Emmanuel Venisse updated SCM-5: --- Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > Create user guide/Guide for the impatient programmer (gipper) > - > > Key: SCM-5 > URL: http://jira.codehaus.org/browse/SCM-5 > Project: Maven SCM > Type: Task > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-1) Publish site for 1.0
[ http://jira.codehaus.org/browse/SCM-1?page=all ] Emmanuel Venisse updated SCM-1: --- Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > Publish site for 1.0 > > > Key: SCM-1 > URL: http://jira.codehaus.org/browse/SCM-1 > Project: Maven SCM > Type: Task > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-6) Development/Testing guide
[ http://jira.codehaus.org/browse/SCM-6?page=all ] Emmanuel Venisse updated SCM-6: --- Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > Development/Testing guide > - > > Key: SCM-6 > URL: http://jira.codehaus.org/browse/SCM-6 > Project: Maven SCM > Type: Task > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Fix For: 1.0-beta-3 > > > Guide on how to create new scm providers utilizing the abstract scm test case > for easy testing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-18) complete commands and expose through ScmManager
[ http://jira.codehaus.org/browse/SCM-18?page=all ] Emmanuel Venisse updated SCM-18: Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > complete commands and expose through ScmManager > --- > > Key: SCM-18 > URL: http://jira.codehaus.org/browse/SCM-18 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-clearcase, maven-scm-provider-starteam, > maven-scm-provider-local, maven-scm-provider-cvs, maven-scm-provider-svn, > maven-scm-provider-perforce, maven-scm-api > Reporter: Brett Porter > Fix For: 1.0-beta-3 > > > many commands are not completely implemented, or not implemented at all, and > some that are have not been exposed through the ScmManager interface. > These all need to be rounded out and tested via the TCK for a final 1.0 > release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-17) test structure needs further clean up
[ http://jira.codehaus.org/browse/SCM-17?page=all ] Emmanuel Venisse updated SCM-17: Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > test structure needs further clean up > - > > Key: SCM-17 > URL: http://jira.codehaus.org/browse/SCM-17 > Project: Maven SCM > Type: Test > Components: maven-scm-provider-clearcase, maven-scm-provider-starteam, > maven-scm-provider-local, maven-scm-provider-cvs, > maven-scm-provider-perforce, maven-scm-provider-svn > Reporter: Brett Porter > Fix For: 1.0-beta-3 > > > The following is needed: > - all providers need to utilise the TCK where possible. > - any tests in providers that can be generalised should be moved to the TCK > - other tests in the providers should just test provider specific functions, > and probably not be integration tests like the TCK is > - need further tests for other commands, including those yet to be added > - review coverage for each provider -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-2) Create POJO facade
[ http://jira.codehaus.org/browse/SCM-2?page=all ] Emmanuel Venisse updated SCM-2: --- Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > Create POJO facade > -- > > Key: SCM-2 > URL: http://jira.codehaus.org/browse/SCM-2 > Project: Maven SCM > Type: Task > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Fix For: 1.0-beta-3 > > > Make an easy to use POJO facade for maven-scm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-19) resolve file status ambiguities
[ http://jira.codehaus.org/browse/SCM-19?page=all ] Emmanuel Venisse updated SCM-19: Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > resolve file status ambiguities > --- > > Key: SCM-19 > URL: http://jira.codehaus.org/browse/SCM-19 > Project: Maven SCM > Type: Task > Components: maven-scm-api > Reporter: Brett Porter > Fix For: 1.0-beta-3 > > > currently ScmFileStatus just reports whatever the provider gave back, but > means different things in different SCM's. > eg. "updated" in CVS is UPDATED or PATCHED, in SVN it is UPDATED or MERGED. > "added" in CVS is UPDATED, in SVN it is ADDED. > The API should hide this from the user, though perhaps be able to give the > extended info if necessary. > I suggest isXXX flags instead: > isUpdated() > isAdded() - just came from an update > isMerged() > isInConflict() > isNew() - new locally > etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-10) Use cvslib instead of cvs command line in cvs provider
[ http://jira.codehaus.org/browse/SCM-10?page=all ] Emmanuel Venisse updated SCM-10: Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > Use cvslib instead of cvs command line in cvs provider > -- > > Key: SCM-10 > URL: http://jira.codehaus.org/browse/SCM-10 > Project: Maven SCM > Type: Task > Versions: 1.0-alpha-1 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > if cvslib support ext protocol. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-31) The scm url validator should return a code corresponding to the error
[ http://jira.codehaus.org/browse/SCM-31?page=all ] Emmanuel Venisse updated SCM-31: Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > The scm url validator should return a code corresponding to the error > - > > Key: SCM-31 > URL: http://jira.codehaus.org/browse/SCM-31 > Project: Maven SCM > Type: Improvement > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Fix For: 1.0-beta-3 > > > I would like an error code to be returned so that I can use the error code to > select an i18n key that will provide users with a localized error message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-21) separate revision and tag handling
[ http://jira.codehaus.org/browse/SCM-21?page=all ]
Emmanuel Venisse updated SCM-21:
Fix Version: (was: 1.0-beta-2)
1.0-beta-3
> separate revision and tag handling
> --
>
> Key: SCM-21
> URL: http://jira.codehaus.org/browse/SCM-21
> Project: Maven SCM
> Type: Task
> Components: maven-scm-api
> Reporter: Brett Porter
> Fix For: 1.0-beta-3
>
>
> while in CVS revision# and tag are handled in the same way, the concepts can
> be separated and will make other SCMs easier.
> for example, in subversion, valid revisions are:
> rev#
> HEAD
> BASE
> COMMITTED
> PREV
> {DATE}
> tags are normal checkouts from a different base.
> In CVS, revisions are:
> rev# (per file only really makes sense here, but can apply to several)
> HEAD
> SOME_BRANCH_TAG
> {DATE}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (SCM-101) Clean scm url in AbstractScmManager when scmurl contains "../"
[ http://jira.codehaus.org/browse/SCM-101?page=all ] Emmanuel Venisse updated SCM-101: - Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > Clean scm url in AbstractScmManager when scmurl contains "../" > -- > > Key: SCM-101 > URL: http://jira.codehaus.org/browse/SCM-101 > Project: Maven SCM > Type: Improvement > Components: maven-scm-api > Versions: 1.0-beta-1 > Reporter: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > scm url like this scm:provider:path_to_repository/directory1/../directory2 > must be clean to scm:provider:path_to_repository/directory2 before to run scm > commands -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-57) m2 maven-scm-plugin should use the same configurations/properties with M1 plugin
[ http://jira.codehaus.org/browse/SCM-57?page=all ] Emmanuel Venisse updated SCM-57: Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > m2 maven-scm-plugin should use the same configurations/properties with M1 > plugin > > > Key: SCM-57 > URL: http://jira.codehaus.org/browse/SCM-57 > Project: Maven SCM > Type: Bug > Components: maven-plugin > Versions: 1.0-alpha-3 > Environment: xp > Reporter: Dan Tran > Fix For: 1.0-beta-3 > > > I think m2 should try to make scm plugin configuration compatible with m2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-42) Create a ChangeSorter for sort and group ChangeSet list
[ http://jira.codehaus.org/browse/SCM-42?page=all ] Emmanuel Venisse updated SCM-42: Fix Version: (was: 1.0-beta-2) 1.0-beta-3 > Create a ChangeSorter for sort and group ChangeSet list > --- > > Key: SCM-42 > URL: http://jira.codehaus.org/browse/SCM-42 > Project: Maven SCM > Type: Improvement > Components: maven-scm-api > Versions: 1.0-alpha-2 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-508) Unable to add multimodule projects from CVS
[ http://jira.codehaus.org/browse/CONTINUUM-508?page=comments#action_53287 ] Emmanuel Venisse commented on CONTINUUM-508: Continuum can't find parent if it isn't in repository and it isn't in continuum projects list ;-) If you try to build it with maven, you will have the same problem if you don't have the parent pom in repository. In acegi, parent pom version is 1.0-SNAPSHOT and module use 1.0-RC1, so you need to have 1.0-RC1 in your repo > Unable to add multimodule projects from CVS > --- > > Key: CONTINUUM-508 > URL: http://jira.codehaus.org/browse/CONTINUUM-508 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Reporter: Carlos Sanchez > Priority: Critical > > > If you try to add a multimodule hosted in CVS you get things like > * Could not download > file:/C:/apps/continuum-1.0.2/bin/../temp/summit-1/core/pom.xml: > C:\apps\continuum-1.0.2\bin\..\temp\summit-1\core\pom.xml (The system cannot > find the path specified) > Check the logs for more details. > * Could not download > file:/C:/apps/continuum-1.0.2/bin/../temp/summit-1/core-tiger/pom.xml: > C:\apps\continuum-1.0.2\bin\..\temp\summit-1\core-tiger\pom.xml (The system > cannot find the path specified) > Check the logs for more details. > * Could not download > file:/C:/apps/continuum-1.0.2/bin/../temp/summit-1/adapters/pom.xml: > C:\apps\continuum-1.0.2\bin\..\temp\summit-1\adapters\pom.xml (The system > cannot find the path specified) > Check the logs for more details. > * Could not download > file:/C:/apps/continuum-1.0.2/bin/../temp/summit-1/domain/pom.xml: > C:\apps\continuum-1.0.2\bin\..\temp\summit-1\domain\pom.xml (The system > cannot find the path specified) > You can try with > http://cvs.sourceforge.net/viewcvs.py/*checkout*/acegisecurity/acegisecurity/pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Perforce provider
Thanks. Emmanuel Mike Perham a écrit : Patch submitted in issue. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, December 12, 2005 2:27 AM To: scm-dev@maven.apache.org Subject: Perforce provider Mike, Perforce provider show clear text password in logs. http://jira.codehaus.org/browse/CONTINUUM-504 Can you fix it with some "**"? Thanks Emmanuel
Perforce provider
Mike, Perforce provider show clear text password in logs. http://jira.codehaus.org/browse/CONTINUUM-504 Can you fix it with some "**"? Thanks Emmanuel
Continuum 1.0.2 is released
The Apache Maven team is pleased to announce Continuum 1.0.2. Continuum 1.0.2 is available for download from http://maven.apache.org/continuum/download.html Continuum is a continous integration server that will ensure the health of your code base. This release includes the following improvements: * Improved performance * Support for Clearcase * Support for Perforce * Added a default build definition for Ant project * Added specific build definition screens for Ant and shell projects * Added support of Ant build file in a subdirectory * Allowed modification of default schedule * Bug fixes We hope you enjoy using Continuum! If you have any questions, please consult: * The web site: http://maven.apache.org/continuum/ * The continuum-user mailing list: http://maven.apache.org/continuum/mail-lists.html For news and information, see: * Maven Blogs: http://www.mavenblogs.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-503) Refactor site like m2 site
[ http://jira.codehaus.org/browse/CONTINUUM-503?page=all ] Emmanuel Venisse closed CONTINUUM-503: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: (was: 1.1) 1.0.2 The home page is similar > Refactor site like m2 site > -- > > Key: CONTINUUM-503 > URL: http://jira.codehaus.org/browse/CONTINUUM-503 > Project: Continuum > Type: Task > Components: Documentation > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-503) Refactor site like m2 site
Refactor site like m2 site -- Key: CONTINUUM-503 URL: http://jira.codehaus.org/browse/CONTINUUM-503 Project: Continuum Type: Task Components: Documentation Reporter: Emmanuel Venisse Fix For: 1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Task Scheduler
Thanks. I assigned it to you. Emmanuel John Tolentino a écrit : Hi, Created JIRA issue (http://jira.codehaus.org/browse/PLX-176) but don't have rights in Plexus project to assign to myself. Thanks, John John Tolentino wrote: Hi Emmanuel, Understood. I'll open a JIRA issue for this and assign it to myself. Breakdown of tasks: - move code from org.apache.maven.continuum.build.settings.DefaultSchedulesActivator to plexus-quartz - transform org.apache.maven.continuum.web.validation.CronExpressionValidator into a POJO Will submit the patch later. Thanks, John Emmanuel Venisse wrote: Hi john, I'm totally agree to factoring this code. We can use the plexus-quartz component, but i want it use continuum code (similar code but with more methods like unschedule job and it was more tested) We can perhaps put in plexus-quartz some code from org.apache.maven.continuum.build.settings.DefaultSchedulesActivator and the cron expression validator org.apache.maven.continuum.web.validation.CronExpressionValidator transformed in a POJO We have some code too in org.apache.maven.continuum.DefaultContinuum : public void addSchedule( Schedule schedule ) private void updateSchedule( Schedule schedule, boolean updateScheduler ) but i don't think we can factorize it. Emmanuel John Tolentino a écrit : Hi, I've seen reusable code in both Plexus and Continuum. The following have similar code: org.apache.maven.continuum.scheduler.ContinuumScheduler org.apache.maven.continuum.scheduler.DefaultContinuumScheduler org.codehaus.plexus.scheduler.DefaultScheduler org.codehaus.plexus.scheduler.Scheduler Can we factor this out to task-scheduler? I'll also use the code to resolve MRM-38. It would make more sense if the code appears in just one place instead of three. Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1374) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
[ http://jira.codehaus.org/browse/MNG-1374?page=all ] Emmanuel Venisse closed MNG-1374: - Resolution: Fixed ok Mike, you're right > Release plugin fails to update SNAPSHOTS in the dependencyManagement section > > > Key: MNG-1374 > URL: http://jira.codehaus.org/browse/MNG-1374 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Versions: 2.0 > Environment: Maven 2.0 (release-plugin version: 2.0-beta3) > Reporter: Ørjan Austvold > Assignee: John Casey > Fix For: 2.0.1 > Attachments: prep.txt > > > In a multi project the parent-pom can specify "standard" versions for > dependencies within the project group. I have found it convenient to also > list group-members with versions in this section so that all child artifact > within the group simply specifies inter-group artifact dependencies without > versions. > The release plugin fails to alter SNAPSHOT dependencies within the > dependencyMangement section. The tagged version of child poms gets instead > the correct version explicitly stated in their dependency section. > It seems a bit strange that dependencies on artifacts within a group must > have dependencies on other artifacts within the group listed with version > numbers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Task Scheduler
Hi john, I'm totally agree to factoring this code. We can use the plexus-quartz component, but i want it use continuum code (similar code but with more methods like unschedule job and it was more tested) We can perhaps put in plexus-quartz some code from org.apache.maven.continuum.build.settings.DefaultSchedulesActivator and the cron expression validator org.apache.maven.continuum.web.validation.CronExpressionValidator transformed in a POJO We have some code too in org.apache.maven.continuum.DefaultContinuum : public void addSchedule( Schedule schedule ) private void updateSchedule( Schedule schedule, boolean updateScheduler ) but i don't think we can factorize it. Emmanuel John Tolentino a écrit : Hi, I've seen reusable code in both Plexus and Continuum. The following have similar code: org.apache.maven.continuum.scheduler.ContinuumScheduler org.apache.maven.continuum.scheduler.DefaultContinuumScheduler org.codehaus.plexus.scheduler.DefaultScheduler org.codehaus.plexus.scheduler.Scheduler Can we factor this out to task-scheduler? I'll also use the code to resolve MRM-38. It would make more sense if the code appears in just one place instead of three. Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MNG-1374) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
[ http://jira.codehaus.org/browse/MNG-1374?page=all ] Emmanuel Venisse reopened MNG-1374: --- We need to update dependency versions in dependencyManagement to new version after tagging process > Release plugin fails to update SNAPSHOTS in the dependencyManagement section > > > Key: MNG-1374 > URL: http://jira.codehaus.org/browse/MNG-1374 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Versions: 2.0 > Environment: Maven 2.0 (release-plugin version: 2.0-beta3) > Reporter: Ørjan Austvold > Assignee: John Casey > Fix For: 2.0.1 > Attachments: prep.txt > > > In a multi project the parent-pom can specify "standard" versions for > dependencies within the project group. I have found it convenient to also > list group-members with versions in this section so that all child artifact > within the group simply specifies inter-group artifact dependencies without > versions. > The release plugin fails to alter SNAPSHOT dependencies within the > dependencyMangement section. The tagged version of child poms gets instead > the correct version explicitly stated in their dependency section. > It seems a bit strange that dependencies on artifacts within a group must > have dependencies on other artifacts within the group listed with version > numbers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1730) release plugin doesn't tag correctly with svn+ssh when remote and local username don't match
[ http://jira.codehaus.org/browse/MNG-1730?page=comments#action_53090 ] Emmanuel Venisse commented on MNG-1730: --- for release plugin code in svn, tagBase isn't necessary if projects use subversion standards : trunk, tags, branches > release plugin doesn't tag correctly with svn+ssh when remote and local > username don't match > > > Key: MNG-1730 > URL: http://jira.codehaus.org/browse/MNG-1730 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Reporter: Brett Porter > > Original Estimate: 30 minutes > Remaining: 30 minutes > > svn is very stubborn about this. Basically you have to have the value in > match the url used to check it out. > Things that will fail: > - if you pass in a different username to --username, it is not passed on to > ssh > - if you specify a username in the ssh command it works, as long as the URL > is the same in both. svn+ssh://[EMAIL PROTECTED]/... is considered a > different repository to svn+ssh://foo/... even if I am bporter > I think we can take a couple of steps: > - for svn+ssh, put the username in the URL instead of passing --username > - possibly check the current checkout (svn info) and derive the tag location > from that, ignoring the local checkout OR if they don't match, relocate the > local checkout to that of developerConnection > - use javasvn instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (SCM-105) [patch] more logging for clearcase provider
[ http://jira.codehaus.org/browse/SCM-105?page=all ] Emmanuel Venisse closed SCM-105: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-2 Applied > [patch] more logging for clearcase provider > --- > > Key: SCM-105 > URL: http://jira.codehaus.org/browse/SCM-105 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-clearcase > Reporter: Wim Deblauwe > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-2 > Attachments: clearcase-debug.patch > > > This patch logs all calls to clearcase. This should allow easier debugging of > problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-500) windows client to windows server cvsnt connection: wrong cvsroot value?
[ http://jira.codehaus.org/browse/CONTINUUM-500?page=all ] Emmanuel Venisse closed CONTINUUM-500: -- Resolution: Fixed Fixed. I always remove now the default port (2401) from cvsroot, so cvsroot will be correct for standard cvs and cvsnt > windows client to windows server cvsnt connection: wrong cvsroot value? > --- > > Key: CONTINUUM-500 > URL: http://jira.codehaus.org/browse/CONTINUUM-500 > Project: Continuum > Type: Bug > Versions: 1.0.1 > Environment: Installed on PC running continuum server: > Windows XP Prof. 5.1.2600 > cvsnt 2.0.51d > Both Maven 1.0.2 and Maven 2.0 installed > Continuum 1.0.1 > j2sdk1.4.2_08 > CVS server: Windows Server 2003 (?) > Reporter: Peter Hertogen > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > problem in connecting from windows XP client to windows CVS server using > cvsnt. > This is the entry in registry for cvspass variable: :pserver:[EMAIL > PROTECTED]:2401:D:\dept\P-ITSource > This was put in the reg by running C:\Documents and Settings\myusername>cvs > -d :pserver:[EMAIL PROTECTED]:D:\dept\P-ITSource login > Logging in to :pserver:[EMAIL PROTECTED]:2401:D:\dept\P-ITSource > CVS password: > > The scm url in my Maven 1.0.2 project.xml is the following: > > > >scm|cvs|pserver|[EMAIL PROTECTED]|D:\dept\P-ITSource|testMaven > > > > However, in the continuum.log I see this: > > > .. cvsRoot: > :pserver:[EMAIL PROTECTED]:2401D:\dept\P-ITSource > 890622 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager - passFile: > C:\Documents and Settings\myusername\.cvspass > > I noticed there is no colon (and no pipe either) present anymore in the > cvsroot variable between 2401 and D > > So I tried manually : > > C:\Documents and Settings\myusername>cvs -d :pserver:[EMAIL > PROTECTED]:2401D:\dept\P-ITSource login > Logging in to :pserver:[EMAIL PROTECTED]:2401:\dept\P-ITSource > CVS password: > cvs [login aborted]: \dept\P-ITSource: no such repository > > Could this be the error, or is it normal that this colon between 2401 and D > is missing in cvsroot in continuum.log? > Feedback of Emmanuel on this was : "arrrg, bad cvsnt. It's an other standard > that cvsnt doesn't respect." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-500) windows client to windows server cvsnt connection: wrong cvsroot value?
[ http://jira.codehaus.org/browse/CONTINUUM-500?page=comments#action_53063 ] Emmanuel Venisse commented on CONTINUUM-500: cvsRoot that appears in logs is the cvsRoot that will be store in .cvspass file (not used by cvsnt). The standard format of cvsroot is without colon between port and path, but cvsNT add a colon between them. pipe are used only as separator in scm url, it's never used in cvsroot. > windows client to windows server cvsnt connection: wrong cvsroot value? > --- > > Key: CONTINUUM-500 > URL: http://jira.codehaus.org/browse/CONTINUUM-500 > Project: Continuum > Type: Bug > Versions: 1.0.1 > Environment: Installed on PC running continuum server: > Windows XP Prof. 5.1.2600 > cvsnt 2.0.51d > Both Maven 1.0.2 and Maven 2.0 installed > Continuum 1.0.1 > j2sdk1.4.2_08 > CVS server: Windows Server 2003 (?) > Reporter: Peter Hertogen > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > problem in connecting from windows XP client to windows CVS server using > cvsnt. > This is the entry in registry for cvspass variable: :pserver:[EMAIL > PROTECTED]:2401:D:\dept\P-ITSource > This was put in the reg by running C:\Documents and Settings\myusername>cvs > -d :pserver:[EMAIL PROTECTED]:D:\dept\P-ITSource login > Logging in to :pserver:[EMAIL PROTECTED]:2401:D:\dept\P-ITSource > CVS password: > > The scm url in my Maven 1.0.2 project.xml is the following: > > > >scm|cvs|pserver|[EMAIL PROTECTED]|D:\dept\P-ITSource|testMaven > > > > However, in the continuum.log I see this: > > > .. cvsRoot: > :pserver:[EMAIL PROTECTED]:2401D:\dept\P-ITSource > 890622 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager - passFile: > C:\Documents and Settings\myusername\.cvspass > > I noticed there is no colon (and no pipe either) present anymore in the > cvsroot variable between 2401 and D > > So I tried manually : > > C:\Documents and Settings\myusername>cvs -d :pserver:[EMAIL > PROTECTED]:2401D:\dept\P-ITSource login > Logging in to :pserver:[EMAIL PROTECTED]:2401:\dept\P-ITSource > CVS password: > cvs [login aborted]: \dept\P-ITSource: no such repository > > Could this be the error, or is it normal that this colon between 2401 and D > is missing in cvsroot in continuum.log? > Feedback of Emmanuel on this was : "arrrg, bad cvsnt. It's an other standard > that cvsnt doesn't respect." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-500) windows client to windows server cvsnt connection: wrong cvsroot value?
[ http://jira.codehaus.org/browse/CONTINUUM-500?page=all ] Emmanuel Venisse updated CONTINUUM-500: --- Assign To: Emmanuel Venisse Fix Version: 1.0.2 > windows client to windows server cvsnt connection: wrong cvsroot value? > --- > > Key: CONTINUUM-500 > URL: http://jira.codehaus.org/browse/CONTINUUM-500 > Project: Continuum > Type: Bug > Versions: 1.0.1 > Environment: Installed on PC running continuum server: > Windows XP Prof. 5.1.2600 > cvsnt 2.0.51d > Both Maven 1.0.2 and Maven 2.0 installed > Continuum 1.0.1 > j2sdk1.4.2_08 > CVS server: Windows Server 2003 (?) > Reporter: Peter Hertogen > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > problem in connecting from windows XP client to windows CVS server using > cvsnt. > This is the entry in registry for cvspass variable: :pserver:[EMAIL > PROTECTED]:2401:D:\dept\P-ITSource > This was put in the reg by running C:\Documents and Settings\myusername>cvs > -d :pserver:[EMAIL PROTECTED]:D:\dept\P-ITSource login > Logging in to :pserver:[EMAIL PROTECTED]:2401:D:\dept\P-ITSource > CVS password: > > The scm url in my Maven 1.0.2 project.xml is the following: > > > >scm|cvs|pserver|[EMAIL PROTECTED]|D:\dept\P-ITSource|testMaven > > > > However, in the continuum.log I see this: > > > .. cvsRoot: > :pserver:[EMAIL PROTECTED]:2401D:\dept\P-ITSource > 890622 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager - passFile: > C:\Documents and Settings\myusername\.cvspass > > I noticed there is no colon (and no pipe either) present anymore in the > cvsroot variable between 2401 and D > > So I tried manually : > > C:\Documents and Settings\myusername>cvs -d :pserver:[EMAIL > PROTECTED]:2401D:\dept\P-ITSource login > Logging in to :pserver:[EMAIL PROTECTED]:2401:\dept\P-ITSource > CVS password: > cvs [login aborted]: \dept\P-ITSource: no such repository > > Could this be the error, or is it normal that this colon between 2401 and D > is missing in cvsroot in continuum.log? > Feedback of Emmanuel on this was : "arrrg, bad cvsnt. It's an other standard > that cvsnt doesn't respect." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-102) Add scm:edit/unedit to plugin and starteam provider
[ http://jira.codehaus.org/browse/SCM-102?page=all ] Emmanuel Venisse closed SCM-102: Assign To: Emmanuel Venisse Resolution: Fixed Applied > Add scm:edit/unedit to plugin and starteam provider > --- > > Key: SCM-102 > URL: http://jira.codehaus.org/browse/SCM-102 > Project: Maven SCM > Type: New Feature > Components: maven-plugin > Versions: 1.0-beta-1 > Environment: xp, starteam > Reporter: Dan Tran > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-2 > Attachments: SCM-102.patch > > > - Add scm:edit, scm:unedit mojos > - Add Starteam's edit and unedit commands implementation + test > - Display warning when a provider does not support edit/unedit command ( > in maven-scm-api ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-250) jaas and ant dependencies are optional in jpox-1.1-beta-4
[ http://jira.codehaus.org/browse/MEV-250?page=comments#action_53007 ] Emmanuel Venisse commented on MEV-250: -- ojdbc is optional too > jaas and ant dependencies are optional in jpox-1.1-beta-4 > - > > Key: MEV-250 > URL: http://jira.codehaus.org/browse/MEV-250 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Emmanuel Venisse > > > Need to use new groupId for all dependencies moved to javax.* -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-250) jaas and ant dependencies are optional in jpox-1.1-beta-4
jaas and ant dependencies are optional in jpox-1.1-beta-4 - Key: MEV-250 URL: http://jira.codehaus.org/browse/MEV-250 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Emmanuel Venisse Need to use new groupId for all dependencies moved to javax.* -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-498) The continuum build depends via jpox on jaas. This is included in java 1.4 and will reach end of live in March 2006
[ http://jira.codehaus.org/browse/CONTINUUM-498?page=all ] Emmanuel Venisse closed CONTINUUM-498: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0.2 Fixed. > The continuum build depends via jpox on jaas. This is included in java 1.4 > and will reach end of live in March 2006 > --- > > Key: CONTINUUM-498 > URL: http://jira.codehaus.org/browse/CONTINUUM-498 > Project: Continuum > Type: Task > Components: Core system > Reporter: Andreas Hoheneder > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.0.2 > > > According to http://java.sun.com/products/jaas/index-10.html jaas reaches its > end of live (and it isn't needed as dependency anyway as it is included in > the java versions continuum requires). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-248) commons-pool 1.2 is invalid: v3 version instead of v4
commons-pool 1.2 is invalid: v3 version instead of v4 - Key: MEV-248 URL: http://jira.codehaus.org/browse/MEV-248 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Emmanuel Venisse -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-247) commons-dbcp 1.2 is invalid: v3 version instead of v4
commons-dbcp 1.2 is invalid: v3 version instead of v4 - Key: MEV-247 URL: http://jira.codehaus.org/browse/MEV-247 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Emmanuel Venisse -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] maven-pom-plugin-1.5 for Maven 1.x
+1 Emmanuel Lukas Theussl a écrit : And another one... The pom plugin has zero issues open and, depending on the result for the plugin-plugin, I think it's ready for release. The future documentation is here, note in particular the page about validation: http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/pom/ Vote is open for 72 hours. +1 Lukas === Changes in this version include: Fixed bugs: o pom:validate doesn't work with . Fixes MPPOM-1. o pom:validate doesn't work. Fixes MPPOM-5. Changes: o Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated : dom4j v1.4-dev-8 -> v1.4 maven v1.0 -> v1.0.2 Fixes MAVEN-1712. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-pom-plugin -Dversion=1.5-SNAPSHOT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] maven-announcement-plugin 1.4 for maven 1.X
+1
Emmanuel
Lukas Theussl a écrit :
Hi,
The announcement plugin has zero issues open and, together with the
changes plugin, I think it's ready for release.
The future documentation is here:
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/announcement/
Vote is open for 72 hours.
+1
Lukas
===
Changes in this version include:
New Features:
o Added property maven.announcement.lenient. Fixes MPANNOUNCEMENT-19.
o Support new format of element in changes.xml. Fixes
MPANNOUNCEMENT-18.
o Modified the announcement text "The ${pom.groupId} team is pleased..." in
favor of "We are pleased..." and changed the signature from "The
${pom.groupId} team" to "The ${pom.name} development team". Fixes
MPANNOUNCEMENT-15.
o Add information about the Maven remote repo to use in the generated
download instructions. Added a maven.announcement.repo.remote property
that
can be used to specify from which Maven remote repository the artifact
for
this project can be found. Fixes MPANNOUNCEMENT-16.
Fixed bugs:
o CR-LF generated do not match the platform. Fixes MPANNOUNCEMENT-3.
o Xml entities transformed in wrong direction. Fixes MPANNOUNCEMENT-10.
Changes:
o Update dependencies to match ones in maven 1.1 core and to unify them
between plugins. The following dependencies are updated : commons-net
v1.2.1 -> v1.4.0 commons-jelly-tags-xml v1.0 -> v1.1 Fixes
MAVEN-1712.
===
To automatically install the plugin, type the following on a single line:
maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
-DgroupId=maven
-DartifactId=maven-announcement-plugin
-Dversion=1.4-SNAPSHOT
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] maven-changes-plugin 1.6 for maven 1.X
+1 Emmanuel Lukas Theussl a écrit : Hi, The changes plugin has zero issues open and, depending on the result for the plugin-plugin, I think it's ready for release. The future documentation is here: http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/changes/ Vote is open for 72 hours. +1 Lukas === Changes in this version include: New Features: o Validate changes.xml. Fixes MPCHANGES-25. o Add multiple due-to/due-to-email support. Fixes MPCHANGES-15. o Add multiple issue support. Fixes MPCHANGES-16. o Add a live bookmark link for the RSS for Firefox. Fixed bugs: o The encoding of changes.xml is not preserved after scm:prepare-release. Fixes MPCHANGES-24. o Fix XTHML 1.0 compliance. o Document description attribute of release element. Fixes MPCHANGES-22. Thanks to Mike Traum. o Added sorting of elements. It is controlled by 2 properties. The maven.changes.sort property decides whether sorting is enabled or not and the maven.changes.sort.order one decides the sort order. Defaults to add,fix,update,remove. Fixes MPCHANGES-14. Changes: o Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated : dom4j v1.4-dev-8 -> v1.4 xml-apis v 1.0.b2 -> xmlParserAPIs v2.6.2 Fixes MAVEN-1712. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-changes-plugin -Dversion=1.6-SNAPSHOT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] maven-plugin-plugin-1.7 for Maven 1.x
+1 Emmanuel Lukas Theussl a écrit : Hi again, The plugin-plugin is the second plugin I would like to release after the arifact-plugin. The biggest change in this release is the introduction of the validate-xml tag which allows to validate arbitrary xml documents against schemas, dtds, rngs, etc. It will be used by a number of plugins to validate their respective input documents (xdoc, faq, pdf, pom, changes,...). There are two special points I want to emphasize to make sure people are aware of it and agree: - The xml validation routines are fully namespace aware, in particular, poms without a namespace declaration are considered invalid. Note that this does not in any way influence the functioning of the plugin/project, only the pom:validate goal will report an invalid pom. - The plugin:plugin goal requires the artifact plugin v1.7 and therefore maven 1.1. That means that maven 1.0 users will not be able to install and deploy plugins from sources (only plugin:download will work for them). The future documentation is here: http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/plugin/ I give it the usual 72 hours and my +1. -Lukas === Changes in this version include: New Features: o Allow plugin-test directory to be changed. Fixes MPPLUGIN-33. o Resolve project.xml inheritance when installing plugin. plugin:plugin goal now requires at least maven 1.1 and maven-artifact-plugin 1.7. Fixes MPPLUGIN-3. o new plugin:validate-xml tag to validate xml documents against a schema. o new assert:assertPluginAvailable tag to check if a minimal release of a plugin is present. Fixed bugs: o NTLM Proxy Problem. Fixes MPPLUGIN-25. Thanks to Jamie McCrindle, Barrie Treloar. o plugin:download didn't redownload SNAPSHOT plugins. Fixes MPPLUGIN-26. Changes: o Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated : commons-jelly-tags-xml v1.0 -> v1.1 commons-logging v1.0.3 -> v1.0.4 jdom v b10 -> v1.0 xercesImpl v 2.4.0 -> v2.6.2 xml-apis v 1.0.b2 -> xmlParserAPIs v2.6.2 Fixes MAVEN-1712. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-plugin-plugin -Dversion=1.7-SNAPSHOT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] maven-artifact-plugin-1.7 for Maven 1.x
+1 Emmanuel Lukas Theussl a écrit : Hello everybody, I'd like to pick up on the release cycle for m1 plugins, as Arnaud noted already some time ago, we have quite a few to do before maven-1.1-beta-3. The artifact plugin has been holding us back for quite a while because a number of other plugins depend on it. I have closed a few outstanding issues in the last days and I think we could release it in the current state. Note that this version (1.7) is a maven 1.1 plugin only, there is one blocking issue open in JIRA which I have scheduled for another intermediary release (1.5.3) which will be compatible with maven 1.0.2. The future documentation is here: http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/artifact/ The vote is open for 72 hours, Here's my +1 Cheers, -Lukas === Changes in this version include: New Features: o New attribute artifactIdOverride that allows to specify custom names for deployed/installed artifacts. Fixes MPARTIFACT-57. Thanks to Neil Crow. o Make deploying a timestamped SNAPSHOT artifact configurable. Fixes MPARTIFACT-59. o New tag artifact:rewritePOM to Rewrite a full model. Inheritence,expression, and versions of dependencies overrided are resolved. Fixed bugs: o When deploying a snapshot, jar and pom have different timestamped version. Fixes MPARTIFACT-56. o Correct handling of directory without a leading / Fixes MPARTIFACT-58. Changes: o Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated : commons-collections v3.1 -> v3.0 commons-httpclient v2.0 -> v2.0.2 commons-jelly v1.0-beta-4 -> v1.0 commons-jexl v1.0-beta-1 -> v1.0 commons-logging v1.0.3 -> v1.0.4 commons-net v1.1.0 -> v1.4.0 plexus-utils v1.0-alpha-3 -> v1.0.3 Fixes MAVEN-1712. o When rewriting POM, versions of dependencies overrided are resolved. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-artifact-plugin -Dversion=1.7-SNAPSHOT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Closed: (MPA-28) Process Dan Tran
Welcome Dan. Emmanuel Jason van Zyl (JIRA) a écrit : [ http://jira.codehaus.org/browse/MPA-28?page=all ] Jason van Zyl closed MPA-28: Resolution: Fixed SVN authorization setup, dan is good to go. Process Dan Tran Key: MPA-28 URL: http://jira.codehaus.org/browse/MPA-28 Project: Maven Project Administration Type: Task Components: new-commiters Reporter: Jason van Zyl Assignee: Jason van Zyl Voted in as a committer for Maven SCM and Maven Plugins. Not sure where we are in the process other then the completion of the vote. I will follow up with Dan in IRC. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (SCM-101) Clean scm url in AbstractScmManager when scmurl contains "../"
Clean scm url in AbstractScmManager when scmurl contains "../" -- Key: SCM-101 URL: http://jira.codehaus.org/browse/SCM-101 Project: Maven SCM Type: Improvement Components: maven-scm-api Versions: 1.0-beta-1 Reporter: Emmanuel Venisse Fix For: 1.0-beta-2 scm url like this scm:provider:path_to_repository/directory1/../directory2 must be clean to scm:provider:path_to_repository/directory2 before to run scm commands -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-485) Add a default build definition for ant project
[ http://jira.codehaus.org/browse/CONTINUUM-485?page=all ] Emmanuel Venisse closed CONTINUUM-485: -- Assign To: Emmanuel Venisse Resolution: Fixed Applied with some modifications. > Add a default build definition for ant project > -- > > Key: CONTINUUM-485 > URL: http://jira.codehaus.org/browse/CONTINUUM-485 > Project: Continuum > Type: Improvement > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > Attachments: CONTINUUM-485-continuum-core.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: site update
I didn't have time, it will be update before the release Emmanuel Wim Deblauwe a écrit : Hi, my patch http://jira.codehaus.org/browse/SCM-95 has not been applied yet. Is there a specific reason? regards, Wim
[jira] Commented: (JXR-5) JXR report html malformed
[ http://jira.codehaus.org/browse/JXR-5?page=comments#action_52865 ] Emmanuel Venisse commented on JXR-5: https://svn.apache.org/repos/asf/maven/jxr/trunk > JXR report html malformed > - > > Key: JXR-5 > URL: http://jira.codehaus.org/browse/JXR-5 > Project: Maven JXR > Type: Bug > Versions: 1.0-beta-1 > Reporter: mike perham > Fix For: 1.0-beta-1 > > > Here's a sample of the HTML generated. Note the invalid links and the > unresolved $name variable: > > > > WSF TripleStore SPI 2.2.0-SNAPSHOT Reference Package > $name >href="\.\./\.\./\.\./\.\./\.\./stylesheet.css" title="style" /> > > > > > >href="\.\./\.\./\.\./\.\./\.\./overview-summary.html">Overview > > Package > > > > > >target="_top">FRAMES > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-499) Update for README.txt with an hands on chapter for including the Sun jars into the m2 repository
[ http://jira.codehaus.org/browse/CONTINUUM-499?page=all ] Emmanuel Venisse closed CONTINUUM-499: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0.2 Applied. Thanks. > Update for README.txt with an hands on chapter for including the Sun jars > into the m2 repository > > > Key: CONTINUUM-499 > URL: http://jira.codehaus.org/browse/CONTINUUM-499 > Project: Continuum > Type: Improvement > Components: Core system > Reporter: Andreas Hoheneder > Assignee: Emmanuel Venisse > Priority: Trivial > Fix For: 1.0.2 > Attachments: sun_jars.patch > > > If an user tries to build continuum the first time he has the unpleasant > experience that the build fails because of the missing sun jars (and oracles > ojdbc14.jar). > This Patch adds a short description how to download and inject the jar files > from the various homepages to give newcomers a little help for their first > build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-492) Notifiers should be optional
[ http://jira.codehaus.org/browse/CONTINUUM-492?page=all ] Emmanuel Venisse closed CONTINUUM-492: -- Assign To: Emmanuel Venisse Resolution: Fixed Done. > Notifiers should be optional > > > Key: CONTINUUM-492 > URL: http://jira.codehaus.org/browse/CONTINUUM-492 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.1 > Reporter: Matthew Beermann > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > Continuum is very unhappy if you try to upload a POM where the > section in is missing or empty. As far as I understand it, > notification is an optional feature of Continuum, so that section of the POM > should be too. > As a matter of fact, the entire section should be optional. A > project shouldn't need to know that Continuum is building it - that's > unnecessarily tight coupling. It's entirely possible (as in our case) that > several unrelated CI systems could be building the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-352) scm value is erratic
[ http://jira.codehaus.org/browse/CONTINUUM-352?page=all ] Emmanuel Venisse closed CONTINUUM-352: -- Resolution: Won't Fix Fix Version: (was: 1.0.2) it's the actual mechanism of continuum. values defined in pom are always used instead of modified values in web interface. We think that this value is correct in pom because pom is the maven reference and it's used by lot of plugins. We'll reopen this issue if we change it in future or if we allow users to choose what is the value the most important. > scm value is erratic > > > Key: CONTINUUM-352 > URL: http://jira.codehaus.org/browse/CONTINUUM-352 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0-beta-1 > Reporter: Miguel Griffa > Priority: Blocker > > > Introduction: > I maven1 project that have inaccurate information in scm commection (since it > wasn't used then) > Problem > I uploaded the project.xml and edited online the scm url > all way down from there, the value seemed to be resetted (is it possible that > the scm url is taken from the new project.xml? in that case, why bother in > editing if it will be replaced by cvs location?) > I managed to compile the project one (manual trigger, but errors due to cvs > connection keep appearing (probably due to the scm url beeing modified on > project update) > MO: the information supplied on the webapp shuold always override the > provided by the sources, If it is a matter of documentation (it shuold > certainly be well clarified) the scm url is the one found in project.xml. It > shuold specially be weel informed (visually on the web) that the scm url will > be overwritten by the value of the one in project.xm, if that is the actual > behaviour. > PS: great pice of software -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-96) [patch] Set default edit mode for ClearCase
[ http://jira.codehaus.org/browse/SCM-96?page=all ] Emmanuel Venisse closed SCM-96: --- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-2 Applied. > [patch] Set default edit mode for ClearCase > --- > > Key: SCM-96 > URL: http://jira.codehaus.org/browse/SCM-96 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-clearcase > Reporter: Wim Deblauwe > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-2 > Attachments: editmode.patch > > > This is a patch for the clearcase provider implementing the correct default > for the edit mode (see SCM-88) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-440) Failed to start continuum on 64bit Linux
[ http://jira.codehaus.org/browse/CONTINUUM-440?page=comments#action_52775 ] Emmanuel Venisse commented on CONTINUUM-440: Can you try to run in bin/linux directory this command : ./wrapper wrapper.conf wrapper.pidfile=./continuum.pid wrapper.daemonize=TRUE Is it works, or do you have the same error? > Failed to start continuum on 64bit Linux > > > Key: CONTINUUM-440 > URL: http://jira.codehaus.org/browse/CONTINUUM-440 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: OS:Debian Linux x86-64, Proc: amd64-xeon > Reporter: Nic > Priority: Critical > Fix For: 1.0.2 > > > When starting continuum I get the following error: > # ./run.sh start > Starting continuum... > ./run.sh: line 192: /usr/local/continuum-1.0/bin/linux/wrapper: No such file > or directory > ./run.sh: line 192: /usr/local/continuum-1.0/bin/linux/wrapper: Success > But, there's no such error on a 32bit Linux system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-451) jabber doesn't work with talk.google.com
[ http://jira.codehaus.org/browse/CONTINUUM-451?page=all ] Emmanuel Venisse closed CONTINUUM-451: -- Resolution: Cannot Reproduce google notification works fine when sender is in friend list of recipient user, and with configuration define above. > jabber doesn't work with talk.google.com > > > Key: CONTINUUM-451 > URL: http://jira.codehaus.org/browse/CONTINUUM-451 > Project: Continuum > Type: Task > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > from what I can tell, talk.google.com is on port 5222, but still SSL. > However, selecting port 5222 and trying SSL conects on 5223, which gives an > exception that there is no response. > @4000437a7d6d2975942c Caused by: > org.codehaus.plexus.jabber.JabberClientException: Can't connect to > talk.google.com:5223 > @4000437a7d6d29759bfc at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:51) > @4000437a7d6d2975a3cc at > org.apache.maven.continuum.notification.jabber.JabberContinuumNotifier.sendMessage(JabberContinuumNotifier.java:207) > @4000437a7d6d2975c30c ... 7 more > @4000437a7d6d2975c6f4 Caused by: Connection failed. No response from > server.: > @4000437a7d6d2975cadc at > org.jivesoftware.smack.PacketReader.startup(PacketReader.java:170) > @4000437a7d6d2975d2ac at > org.jivesoftware.smack.XMPPConnection.init(XMPPConnection.java:766) > @4000437a7d6d2975d694 at > org.jivesoftware.smack.XMPPConnection.(XMPPConnection.java:222) > @4000437a7d6d2975f5d4 at > org.jivesoftware.smack.SSLXMPPConnection.(SSLXMPPConnection.java:87) > @4000437a7d6d2975fda4 at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:46) > @4000437a7d6d29760574 ... 8 more > Using no SSL gives: > @4000437a771714668e9c Caused by: > org.codehaus.plexus.jabber.JabberClientException: Can't connect to > talk.gmail.com:5222 > @4000437a77171466966c at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:51) > @4000437a771714669e3c at > org.apache.maven.continuum.notification.jabber.JabberContinuumNotifier.sendMessage(JabberContinuumNotifier.java:207) > @4000437a77171466c164 ... 7 more > @4000437a77171466c54c Caused by: Could not connect to > talk.gmail.com:5222.: (504) > @4000437a77171466c934 -- caused by: java.net.UnknownHostException: > talk.gmail.com > @4000437a77171466d104 at > org.jivesoftware.smack.XMPPConnection.(XMPPConnection.java:168) > @4000437a77171466d4ec at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:42) > @4000437a77171466f42c ... 8 more > Perhaps we can use Smack 2.0's special GoogleTalkConnection and add a new > notifier type? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-481) Continuum ignores .cvspass
[ http://jira.codehaus.org/browse/CONTINUUM-481?page=all ] Emmanuel Venisse closed CONTINUUM-481: -- Assign To: Emmanuel Venisse Resolution: Fixed Faq is added > Continuum ignores .cvspass > -- > > Key: CONTINUUM-481 > URL: http://jira.codehaus.org/browse/CONTINUUM-481 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.1 > Environment: TortoiseCVS 1.8.22 > Microsoft Windows Server 2003 SP1 > Reporter: Matthew Beermann > Assignee: Emmanuel Venisse > Priority: Critical > Fix For: 1.0.2 > > > Continuum seems to ignore the .cvspass file while building my projects, > resulting in the error: "Empty password used - try 'cvs login' with a real > password". Note that our CVS repository does not have anonymous access, nor > does it use the "anonymous" account. > I see these two lines in the log, which look suspicious: > 31321 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager - passFile: > C:\Documents and Settings\Default User\.cvspass > 31321 [Thread-1] DEBUG org.apache.maven.scm.manager.ScmManager - cvsroot > [CENSORED] already exists in C:\Documents and Settings\Default User\.cvspass. > SKIPPED. > ...what the heck? I don't want it to skip that password, I want it to USE > that password! This behavior seems completely wrong to me. Note that running > a "cvs checkout" command from the command line works just fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-451) jabber doesn't work with talk.google.com
[ http://jira.codehaus.org/browse/CONTINUUM-451?page=comments#action_52768 ] Emmanuel Venisse commented on CONTINUUM-451: smack doesn't have a "special" connection for google, but only a preconfigured connection. I tried this : host : talk.google.com port : 5222 login: google login password : domain name : gmail.com recipient : google recipient SSL connection false With this configuration, i don't have exception on connect, but i don't receive messages. I'll investigate. > jabber doesn't work with talk.google.com > > > Key: CONTINUUM-451 > URL: http://jira.codehaus.org/browse/CONTINUUM-451 > Project: Continuum > Type: Task > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > from what I can tell, talk.google.com is on port 5222, but still SSL. > However, selecting port 5222 and trying SSL conects on 5223, which gives an > exception that there is no response. > @4000437a7d6d2975942c Caused by: > org.codehaus.plexus.jabber.JabberClientException: Can't connect to > talk.google.com:5223 > @4000437a7d6d29759bfc at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:51) > @4000437a7d6d2975a3cc at > org.apache.maven.continuum.notification.jabber.JabberContinuumNotifier.sendMessage(JabberContinuumNotifier.java:207) > @4000437a7d6d2975c30c ... 7 more > @4000437a7d6d2975c6f4 Caused by: Connection failed. No response from > server.: > @4000437a7d6d2975cadc at > org.jivesoftware.smack.PacketReader.startup(PacketReader.java:170) > @4000437a7d6d2975d2ac at > org.jivesoftware.smack.XMPPConnection.init(XMPPConnection.java:766) > @4000437a7d6d2975d694 at > org.jivesoftware.smack.XMPPConnection.(XMPPConnection.java:222) > @4000437a7d6d2975f5d4 at > org.jivesoftware.smack.SSLXMPPConnection.(SSLXMPPConnection.java:87) > @4000437a7d6d2975fda4 at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:46) > @4000437a7d6d29760574 ... 8 more > Using no SSL gives: > @4000437a771714668e9c Caused by: > org.codehaus.plexus.jabber.JabberClientException: Can't connect to > talk.gmail.com:5222 > @4000437a77171466966c at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:51) > @4000437a771714669e3c at > org.apache.maven.continuum.notification.jabber.JabberContinuumNotifier.sendMessage(JabberContinuumNotifier.java:207) > @4000437a77171466c164 ... 7 more > @4000437a77171466c54c Caused by: Could not connect to > talk.gmail.com:5222.: (504) > @4000437a77171466c934 -- caused by: java.net.UnknownHostException: > talk.gmail.com > @4000437a77171466d104 at > org.jivesoftware.smack.XMPPConnection.(XMPPConnection.java:168) > @4000437a77171466d4ec at > org.codehaus.plexus.jabber.DefaultJabberClient.connect(DefaultJabberClient.java:42) > @4000437a77171466f42c ... 8 more > Perhaps we can use Smack 2.0's special GoogleTalkConnection and add a new > notifier type? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [vote] Release Maven 2.0.1
+1 Emmanuel John Casey a écrit : Hi everyone, I'd like to do the next release of the Maven core. We've fixed many important bugs since 2.0, along with expanded plugin support, and a new bootstrap. In total, we've resolved 125 issues (including those related in some fashion to the core plugins). We've also added support for Ant-driven mojos. All in all, the Maven core platform has become quite a bit more stable, and I'd like to make what we currently have available for public consumption. What do you all think? I'll give it 72 hours, and see where we stand. Here's my +1. Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
