[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/09-Jul-2005_12.00.48/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/08-Jul-2005_08.00.31/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM issues in the repository
John Casey wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think that such a drastic step will only serve to completely marginalize maven 2.x, and alienate users. Who would convert to using m2 if they first had to re-request uploads for the 10 dependencies they have?? I hope that m2 users will help you to get this problem fixed. While I agree that the repository information we currently have is inadequate and incomplete, such is life. When have you ever worked on a product revision/rewrite where you *didn't* have to deal with bad data? In my build system?? Never! That's too high risk to take. I would only change the build system if I would be certain that if will not deceive me as I have to many problems to deal with elsewhere. The answer is *never* to blow away everything you know and replace it with only the things you know to a perfect degree...you'd be re-creating your datastore with every new major version. Also, to address your assertion about Maven 2.x's readiness for production - perhaps you noticed the -alpha-3 notation we've used on the latest release? ;) This software isn't perfect yet, and neither is the data it relies on...but we're working on it, and it *will* get better. But you are aiming at 2.0 release real soon: in August, do not you? I personally would keep maven in alpha stage as long as repository is not ready for public use even if the m2 code will be prefect and ready for prime time as you simply cannot use m2 without reliable repository. This gives a full right to use the current strategy for improving the repository data. Obviously, having naked poms isn't a good idea, but it will help users trying to migrate from maven 1.x (where they couldn't use the transitivity of dependencies anyway), and as these users attempt to trim their own dep lists, they can help us fix these bad poms. We cannot adopt the strategy of only putting perfect metadata into the repository, since our users need access to such a wide spectrum of libraries. Initially, for upgrading users, it will be better to have *some* access to these artifacts rather than clogging the MAVENUPLOAD project with re-requests. I am complete agreeing with you. I am just linking 2.0 release (which gives clear signal to users: __it is production ready__) with readiness of the repository for the demanding (normal?) users and not just for those brave early adopters, which are generally fans of maven and will use it anyway. Once m2 final relases will get the label of being not reliable as its repository is constantly changing this is what can be actually the factor (just hypothesis) which "marginalize maven 2.x, and alienate users" as it is very difficult to change such negative image after "bad press", which you will surly have. I am just feeling that missisng poms in the repository give more motivation to provide good ones then naked ones as they give the false impression that data in the repository is OK. I do hope to have time to help you to clean you poms I am using. And I am hoping that your community will really help you to get it fixed asap. just my 2 cents regards Michal -- Zamachy w Londynie: FOTO RAPORT >>> http://link.interia.pl/f18a1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSIMIAN-9) report generations fails with "String index out of range: -24"
[ http://jira.codehaus.org/browse/MPSIMIAN-9?page=all ] David Eric Pugh closed MPSIMIAN-9: -- Assign To: David Eric Pugh (was: Jason van Zyl) Resolution: Won't Fix Just use the excludes rules to make sure the fiels are excluded.. The latest version of the plugin only includes .java anyway, so you should be good. > report generations fails with "String index out of range: -24" > -- > > Key: MPSIMIAN-9 > URL: http://jira.codehaus.org/browse/MPSIMIAN-9 > Project: maven-simian-plugin > Type: Bug > Environment: Maven instaled on Windows XP > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) > Reporter: Pavel Jetensky > Assignee: David Eric Pugh > Attachments: merdivbezp.zip > > > In my project there is just one file with source. It is not java file, but > XQW file (XQW is a kind of programming language in XML). > When I try to generate Simian report, build fails with such a message: > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 > build:start: > site: > xdoc:register-reports: > maven-simian-plugin:register: > site:run-reports: > [echo] Generating the Simian Report... > BUILD FAILED > File.. C:\Documents and > Settings\host\.maven\cache\maven-simian-plugin-1.4\p > lugin.jelly > Element... simian:simianLog > Line.. 139 > Column 11 > String index out of range: -24 > Total time: 6 seconds > Finished at: Thu Jul 15 12:33:47 CEST 2004 > My project structure: > src/test/TestApp.xqw > project.properties > project.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSIMIAN-7) customization of patternsets searched in test dir
[ http://jira.codehaus.org/browse/MPSIMIAN-7?page=all ] David Eric Pugh closed MPSIMIAN-7: -- Assign To: David Eric Pugh (was: Jason van Zyl) Resolution: Fixed Done! > customization of patternsets searched in test dir > - > > Key: MPSIMIAN-7 > URL: http://jira.codehaus.org/browse/MPSIMIAN-7 > Project: maven-simian-plugin > Type: Wish > Reporter: Omair-Inam Abdul-Matin > Assignee: David Eric Pugh > Priority: Minor > > > Would it be possible to provide the equivalent of a > maven.simian.testincludes(testexcludes) properties that would allow us to > specify what files simian includes/excludes when searching the tests dir? > Sometimes we may want to exclude e.g. Mocks that have been generated > automatically but look in other test files for duplication. -- 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: (MPSIMIAN-11) Includes/excludes pattern does not support multiple patterns
[ http://jira.codehaus.org/browse/MPSIMIAN-11?page=all ]
David Eric Pugh closed MPSIMIAN-11:
---
Assign To: David Eric Pugh
Resolution: Fixed
done!
> Includes/excludes pattern does not support multiple patterns
>
>
> Key: MPSIMIAN-11
> URL: http://jira.codehaus.org/browse/MPSIMIAN-11
> Project: maven-simian-plugin
> Type: Bug
> Environment: maven 1.0 maven-simian-plugin 1.4
> Reporter: Thomas Recloux
> Assignee: David Eric Pugh
> Attachments: plugin.jelly
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> The maven simian plugin seems to ignore includes/excludes pattern when they
> specify multiple patterns, this is because of the definition
> which is wrong.
> it is :
>
>
>
> and shhould be :
> excludes="${maven.simian.excludes}"
> includes="${maven.simian.includes}" >
> Il will update the issue with the plugin.jelly file updated.
> Thanks, Thomas
--
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]
svn commit: r209894 - in /maven/maven-1/plugins/trunk/simian: plugin.jelly plugin.properties project.properties src/test/org/apache/maven/simian/ExcludeMe.java xdocs/changes.xml xdocs/properties.xml
Author: epugh
Date: Fri Jul 8 14:32:44 2005
New Revision: 209894
URL: http://svn.apache.org/viewcvs?rev=209894&view=rev
Log:
MPSIMIAN-7 customization of patternsets searched in test dir
Added:
maven/maven-1/plugins/trunk/simian/src/test/org/apache/maven/simian/ExcludeMe.java
Modified:
maven/maven-1/plugins/trunk/simian/plugin.jelly
maven/maven-1/plugins/trunk/simian/plugin.properties
maven/maven-1/plugins/trunk/simian/project.properties
maven/maven-1/plugins/trunk/simian/xdocs/changes.xml
maven/maven-1/plugins/trunk/simian/xdocs/properties.xml
Modified: maven/maven-1/plugins/trunk/simian/plugin.jelly
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/plugin.jelly?rev=209894&r1=209893&r2=209894&view=diff
==
--- maven/maven-1/plugins/trunk/simian/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/simian/plugin.jelly Fri Jul 8 14:32:44 2005
@@ -84,7 +84,10 @@
-
+
+
+
+
Modified: maven/maven-1/plugins/trunk/simian/plugin.properties
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/plugin.properties?rev=209894&r1=209893&r2=209894&view=diff
==
--- maven/maven-1/plugins/trunk/simian/plugin.properties (original)
+++ maven/maven-1/plugins/trunk/simian/plugin.properties Fri Jul 8 14:32:44
2005
@@ -25,3 +25,5 @@
maven.simian.includes = **/*.java
maven.simian.excludes =
+maven.simian.testincludes = **/*.java
+maven.simian.testexcludes =
Modified: maven/maven-1/plugins/trunk/simian/project.properties
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/project.properties?rev=209894&r1=209893&r2=209894&view=diff
==
--- maven/maven-1/plugins/trunk/simian/project.properties (original)
+++ maven/maven-1/plugins/trunk/simian/project.properties Fri Jul 8 14:32:44
2005
@@ -19,3 +19,4 @@
# ---
maven.javadoc.links = http://java.sun.com/j2se/1.4.1/docs/api/
maven.junit.fork=yes
+maven.simian.testexcludes = **/ExcludeMe.java
Added:
maven/maven-1/plugins/trunk/simian/src/test/org/apache/maven/simian/ExcludeMe.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/src/test/org/apache/maven/simian/ExcludeMe.java?rev=209894&view=auto
==
---
maven/maven-1/plugins/trunk/simian/src/test/org/apache/maven/simian/ExcludeMe.java
(added)
+++
maven/maven-1/plugins/trunk/simian/src/test/org/apache/maven/simian/ExcludeMe.java
Fri Jul 8 14:32:44 2005
@@ -0,0 +1,52 @@
+package org.apache.maven.simian;
+
+/*
+ * Copyright 2001-2004 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+/**
+ *
+ * @author Eric Pugh
+ * @version $Revision: 170200 $
+ */
+public class ExcludeMe {
+public void iShouldNotBeIncluded() {
+String one = "one";
+String two = "two";
+String three = "three";
+String four = "four";
+String five= "five";
+String six = "six";
+String seven = "seven";
+String eight = "eight";
+String nine = "nine";
+String ten = "ten";
+}
+
+public void iShouldNotBeIncluded2() {
+String one = "one";
+String two = "two";
+String three = "three";
+String four = "four";
+String five= "five";
+String six = "six";
+String seven = "seven";
+String eight = "eight";
+String nine = "nine";
+}
+
+
+}
Modified: maven/maven-1/plugins/trunk/simian/xdocs/changes.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/xdocs/changes.xml?rev=209894&r1=209893&r2=209894&view=diff
==
--- maven/maven-1/plugins/trunk/simian/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/simian/xdocs/changes.xml Fri Jul 8 14:32:44
2005
@@ -26,7 +26,8 @@
- Upgrade to Simian 2.2.4 and
[jira] Commented: (MPSIMIAN-5) Upgrade to latest version of Ant
[ http://jira.codehaus.org/browse/MPSIMIAN-5?page=comments#action_42583 ] David Eric Pugh commented on MPSIMIAN-5: I was about to do this, and realized that we are up to Ant 1.6.5.. is there any poilicy about ant? Is there a blessed version of Ant? Should I just make the change, seems small envough... > Upgrade to latest version of Ant > > > Key: MPSIMIAN-5 > URL: http://jira.codehaus.org/browse/MPSIMIAN-5 > Project: maven-simian-plugin > Type: Improvement > Reporter: Archimedes Trajano > Assignee: Jason van Zyl > Priority: Minor > > > This plugin has a dependency on Ant 1.6, perhaps should be upgraded to 1.6.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSIMIAN-14) Upgrade to Simian 2.2.4 and uses XML format
[ http://jira.codehaus.org/browse/MPSIMIAN-14?page=all ] David Eric Pugh closed MPSIMIAN-14: --- Assign To: David Eric Pugh Resolution: Fixed I have applied your fixes. I didn't quite change the release as we haven't released yet. Can you test the chagnes and if it looks good I'll release next week. > Upgrade to Simian 2.2.4 and uses XML format > --- > > Key: MPSIMIAN-14 > URL: http://jira.codehaus.org/browse/MPSIMIAN-14 > Project: maven-simian-plugin > Type: Improvement > Reporter: Benoit Xhenseval > Assignee: David Eric Pugh > Attachments: changes.xml.diff.txt, plugin-resources.zip, > plugin.jelly.diff.txt, project.xml > > > why the usage of XML report for Simian is so important to us? > > This is due to a new open source project that my company www.objectlab.co.uk > is sponsoring: QALab (see http://qalab.sourceforge.net) > we have been using it internally with Ant and not Maven. We evaluated Simian > and created an extension for it, we wanted an XML interface so we used > version 2.2.4. > > QALab consolidates statistics from checkstyle, pmd, findbugs and (recently) > simian all based on the xml interfaces. QALab also keeps track of these > stats over time and generates reports & charts on the back of this. > > Hope this helps & that you will consider our changes to the maven 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-548) Add the reactor projects to MavenSession
[ http://jira.codehaus.org/browse/MNG-548?page=comments#action_42581 ]
Joakim Erdfelt commented on MNG-548:
MNG-559 is a duplicate of this jira.
I would like to see this patch be applied for site / report / plugin /
documentation reasons.
> Add the reactor projects to MavenSession
>
>
> Key: MNG-548
> URL: http://jira.codehaus.org/browse/MNG-548
> Project: Maven 2
> Type: Improvement
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Attachments: reactor.patch
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I've made a patch to add the projects from the 'reactor' as discovered by
> DefaultMaven.collectProjects
> to MavenSession, the plexus Context and make it available to the
> PluginParameterExpressionEvaluator.
> This is needed for the maven-eclipse-plugin to be able to make references to
> other projects
> (and not to their installed artifacts).
> Now you can do the following:
> /**
>* @parameter expression="${reactorProjects}"
>* @required
>* @readonly
>*/
> private List reactorProjects; // List of MavenProject objects, ordered for
> dependencies.
> I've had a discussion with trygve about this and he said there was no idea
> what to do with the reactor.
> I think for the mean time, this is an elegant enough solution.
--
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: (MPSIMIAN-12) Simian report contains broken links
[ http://jira.codehaus.org/browse/MPSIMIAN-12?page=comments#action_42582 ] David Eric Pugh commented on MPSIMIAN-12: - Can you retest with the recently updated version 1.5-SNAPSHOT? I am hoping the switch to simian.jsl will have fixed this. > Simian report contains broken links > --- > > Key: MPSIMIAN-12 > URL: http://jira.codehaus.org/browse/MPSIMIAN-12 > Project: maven-simian-plugin > Type: Bug > Environment: Maven 1.0, Java 1.4.2, all platforms. > Reporter: Ricardo Gladwell > > > Reports generated through the simian maven plugin contain broken links for > all entries in the "duplications" section. Please see simian report on my > site: > http://jexus.sourceforge.net/simian-report.html > I have seen this in other maven project sites with simian reports. -- 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]
svn commit: r209890 - in /maven/maven-1/plugins/trunk/simian: ./ src/main/org/apache/maven/simian/ src/plugin-resources/ src/test/org/apache/maven/simian/ xdocs/
Author: epugh
Date: Fri Jul 8 14:11:08 2005
New Revision: 209890
URL: http://svn.apache.org/viewcvs?rev=209890&view=rev
Log:
MPSIMIAN-14 upgrade simian
Added:
maven/maven-1/plugins/trunk/simian/src/plugin-resources/
maven/maven-1/plugins/trunk/simian/src/plugin-resources/simian.jsl (with
props)
Removed:
maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/Duplication.java
maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/DuplicationArea.java
maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/SimianLog.java
maven/maven-1/plugins/trunk/simian/src/test/org/apache/maven/simian/SimianLogTest.java
Modified:
maven/maven-1/plugins/trunk/simian/plugin.jelly
maven/maven-1/plugins/trunk/simian/project.xml
maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/FileSimianTask.java
maven/maven-1/plugins/trunk/simian/xdocs/changes.xml
Modified: maven/maven-1/plugins/trunk/simian/plugin.jelly
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/plugin.jelly?rev=209890&r1=209889&r2=209890&view=diff
==
--- maven/maven-1/plugins/trunk/simian/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/simian/plugin.jelly Fri Jul 8 14:11:08 2005
@@ -30,14 +30,6 @@
xmlns:ant="jelly:ant"
xmlns:simian="simian">
-
-
-
-
@@ -65,10 +57,11 @@
-
+Generating the Simian raw report ...
+
+
+
@@ -122,86 +115,25 @@
+
+
+Converting the Simian report to xdoc ...
+
+
+
-
-
-
-
-
-
-
-
-
-
-Simian Report
-
-
-
- ${simLog.copyright1}
- ${simLog.copyright2}
-
-
-
- Similarity threshold (lines)
- ${maven.simian.linecount}
-
-
- Total number of duplicate lines
- ${simLog.totalDuplicateLineCount}
-
-
- Total number of duplicate blocks
- ${simLog.blockCount}
-
-
- Total number of files with duplicates
- ${simLog.fileWithDuplicateCount}
-
-
- Total number of processed lines
- ${simLog.loc}
-
-
- Total number of processed files
- ${simLog.fileParseCount}
-
-
- Scan time
- ${simLog.time}
-
-
-
-
-
-
-
-
-
-
-
-${duplicationArea.className}(${duplicationArea.startLine}-${duplicationArea.endLine})
-
-
-
-
-
-
-
-
-
-
-
No sources to run Simian on
Modified: maven/maven-1/plugins/trunk/simian/project.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/project.xml?rev=209890&r1=209889&r2=209890&view=diff
==
--- maven/maven-1/plugins/trunk/simian/project.xml (original)
+++ maven/maven-1/plugins/trunk/simian/project.xml Fri Jul 8 14:11:08 2005
@@ -22,7 +22,7 @@
../plugin-parent/project.xml
maven-simian-plugin
Maven Simian Plugin
- 1.4.1-SNAPSHOT
+ 1.5-SNAPSHOT
Simian Plugin for Maven
Simian Plugin for Maven
http://maven.apache.org/reference/plugins/simian/
@@ -89,12 +89,17 @@
Maurice Montgénie
[EMAIL PROTECTED]
+
+ Benoit Xhenseval
+ [EMAIL PROTECTED]
+ ObjectLab.co.uk
+
redhill
simian
- 1.9.1
+ 2.2.4
http://www.redhillconsulting.com.au/products/simian/
Modified:
maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/FileSimianTask.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/FileSimianTask.java?rev=209890&r1=209889&r2=209890&view=diff
==
---
maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/FileSimianTask.java
(original)
+++
maven/maven-1/plugins/trunk/simian/src/main/org/apache/maven/simian/FileSimianTask.java
Fri Jul 8 14:11:08 2005
@@ -17,24 +17,14 @@
*
*/
-import au.com.redhillconsulting.simian.b;
import au.com.redhillconsulting.simian.SimianTask;
import java.io.File;
import java.io.FileOutputStream;
-import java.io.IOException;
import java.io.FileNotFoundException;
-import java.util.Iterator;
-import java.util.List;
-import java.util.LinkedList;
-import java.lang.reflect.Constructor;
-import java.lang.reflect.InvocationTargetException;
-import java.lang.reflect.Method;
-import org.apache.tools.ant.types.FileSet;
import org.apa
[jira] Resolved: (MPSIMIAN-6) typo on prpperties.html
[ http://jira.codehaus.org/browse/MPSIMIAN-6?page=all ] David Eric Pugh resolved MPSIMIAN-6: Assign To: David Eric Pugh (was: Jason van Zyl) Resolution: Cannot Reproduce this has been fixed... > typo on prpperties.html > --- > > Key: MPSIMIAN-6 > URL: http://jira.codehaus.org/browse/MPSIMIAN-6 > Project: maven-simian-plugin > Type: Bug > Reporter: Omair-Inam Abdul-Matin > Assignee: David Eric Pugh > > > There is a typo on the site > http://maven.apache.org/reference/plugins/simian/properties.html > The T should be small as it is maven.simian.includetests. This had me > confused for a day or two until I look at the default project.properties file -- 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: (MPSIMIAN-10) Upgrade simian.jar to version 2.1.6-beta2
[ http://jira.codehaus.org/browse/MPSIMIAN-10?page=all ] David Eric Pugh closed MPSIMIAN-10: --- Assign To: David Eric Pugh (was: Jason van Zyl) Resolution: Won't Fix MPSIMIAN-14 duplicates this bug, but upgrades to a newer version. > Upgrade simian.jar to version 2.1.6-beta2 > - > > Key: MPSIMIAN-10 > URL: http://jira.codehaus.org/browse/MPSIMIAN-10 > Project: maven-simian-plugin > Type: Improvement > Environment: maven-simian-plugin CVS MAIN branch snapshot as of 2004-08-09 > Reporter: David Skyba > Assignee: David Eric Pugh > Attachments: simian.patch > > > I had to use newer simian version than 1.9.1 on large project because of > memory consumption. > Somewhere between 1.9.1 and 2.1.6-beta2 simian changed little bit the plaint > text output format so I've modified SimianLog and SimianLogTest classes. > What are the proper steps to publish new simian-2.1.6.jar to iBiblio > repository? -- 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: [m2] Artifact in two different versions?
Carlos Sanchez wrote: > Ok, I can copy them in the repo > > hibernate 2.x to groupId net.sf.hibernate > hibernate 3.x to groupId org.hibernate > > ibatis 1.x to artifactId ibatis1 > ibatis 2.x to artifactId ibatis2 > > do you think this is the right way? Sounds good. Same for OpenSymphonies WebWorks ... which comes from a mirrored site. This gets interesting ;-) - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/08-Jul-2005_04.00.42/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Artifact in two different versions?
On Fri, Jul 08, 2005 at 10:27:51AM -0700, Carlos Sanchez wrote: > hibernate should be in different groupIds because they have changed > the package names. Right, ok. Then you could actually have both in your class path at the same time too. For Hibernate this actually makes sense now :) Still unsure about Ibatis though. -- Trygve > > On 7/8/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > > On Fri, Jul 08, 2005 at 10:14:15AM -0700, Carlos Sanchez wrote: > > > Ok, I can copy them in the repo > > > > > > hibernate 2.x to groupId net.sf.hibernate > > > hibernate 3.x to groupId org.hibernate > > > > > > ibatis 1.x to artifactId ibatis1 > > > ibatis 2.x to artifactId ibatis2 > > > > I don't think having different group ids is a good solution to this > > problem and probably just confusing to the users. I'm honestly not sure > > what the best solution is. Is it really possible to have both artifacts in > > the classpath at the same time? At least I would assume that this would > > depend on the ordering of the classpath. > > > > > > > > do you think this is the right way? > > > > Not sure, anybody else have a opinion? > > > > -- > > Trygve signature.asc Description: Digital signature
svn commit: r209846 - /maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt
Author: evenisse Date: Fri Jul 8 10:29:26 2005 New Revision: 209846 URL: http://svn.apache.org/viewcvs?rev=209846&view=rev Log: (empty) Modified: maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt Modified: maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt?rev=209846&r1=209845&r2=209846&view=diff == --- maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt (original) +++ maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt Fri Jul 8 10:29:26 2005 @@ -64,6 +64,7 @@ *.tld = svn:eol-style=native;svn:keywords="Author Date Id Revision" *.txt = svn:eol-style=native;svn:keywords="Author Date Id Revision" *.types = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.vm = svn:eol-style=native;svn:keywords="Author Date Id Revision" *.xcat = svn:eol-style=native;svn:keywords="Author Date Id Revision" *.xconf = svn:eol-style=native;svn:keywords="Author Date Id Revision" *.xdoc = svn:eol-style=native;svn:keywords="Author Date Id Revision" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Artifact in two different versions?
hibernate should be in different groupIds because they have changed the package names. On 7/8/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > On Fri, Jul 08, 2005 at 10:14:15AM -0700, Carlos Sanchez wrote: > > Ok, I can copy them in the repo > > > > hibernate 2.x to groupId net.sf.hibernate > > hibernate 3.x to groupId org.hibernate > > > > ibatis 1.x to artifactId ibatis1 > > ibatis 2.x to artifactId ibatis2 > > I don't think having different group ids is a good solution to this > problem and probably just confusing to the users. I'm honestly not sure > what the best solution is. Is it really possible to have both artifacts in > the classpath at the same time? At least I would assume that this would > depend on the ordering of the classpath. > > > > > do you think this is the right way? > > Not sure, anybody else have a opinion? > > -- > Trygve > > > BodyID:254779857.2.n.logpart (stored separately) > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Artifact in two different versions?
Ok, I can copy them in the repo hibernate 2.x to groupId net.sf.hibernate hibernate 3.x to groupId org.hibernate ibatis 1.x to artifactId ibatis1 ibatis 2.x to artifactId ibatis2 do you think this is the right way? On 7/8/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > On Fri, Jul 08, 2005 at 10:09:02AM +0200, Jörg Schaible wrote: > > Hi Tryvge, > > > > Trygve Laugstøl wrote on Friday, July 08, 2005 10:02 AM: > > > > > On Fri, Jul 08, 2005 at 09:53:19AM +0200, Jörg Schaible wrote: > > [snip] > > >> As long as the libraries are not incompatible to themselves, it > > >> should be possible to use both. This might not be the use case for an > > >> application, but building a framework supporting those different > > >> versions. We are in the same situation in the Nano camp. > > > > > > Maven has a strong concept of artifacts. A artifact is > > > identified by the group id and the artifact id and it can have > > > multiple versions. > > > > > > If a project has version 1 and version 2 artifacts that can > > > exists in the same classpath at the same time they they are > > > basically two different artifacts and should have different > > > artifact ids. In the case of hibernate the artifacts should > > > then be named something like this: > > > > > > | Group id | Artifact id | Version > > > | org.sf.hibernate | hibernate2 | 2.0 > > > | org.sf.hibernate | hibernate3 | 3.0 > > > > Well, this is exactly what we did in M1 locally by introducing a > > different artifactId and using the override mechanism to point to a > > project relative version managed by the scm. But this is no longer > > possible in M2 and I am looking for a solution. The problem is, that > > there are quite some artifacts existing, where this situation applies. > > Hibernate is just one example. > > You can still do the same with Maven 2 by naming the artifacs differently > and putting them in the repository. I really don't see the big difference. > What we really should do is to get upstream to name their artifacts > properly. > > -- > Trygve > > > BodyID:254544622.2.n.logpart (stored separately) > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM issues in the repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think that such a drastic step will only serve to completely marginalize maven 2.x, and alienate users. Who would convert to using m2 if they first had to re-request uploads for the 10 dependencies they have?? While I agree that the repository information we currently have is inadequate and incomplete, such is life. When have you ever worked on a product revision/rewrite where you *didn't* have to deal with bad data? The answer is *never* to blow away everything you know and replace it with only the things you know to a perfect degree...you'd be re-creating your datastore with every new major version. Also, to address your assertion about Maven 2.x's readiness for production - perhaps you noticed the -alpha-3 notation we've used on the latest release? ;) This software isn't perfect yet, and neither is the data it relies on...but we're working on it, and it *will* get better. Obviously, having naked poms isn't a good idea, but it will help users trying to migrate from maven 1.x (where they couldn't use the transitivity of dependencies anyway), and as these users attempt to trim their own dep lists, they can help us fix these bad poms. We cannot adopt the strategy of only putting perfect metadata into the repository, since our users need access to such a wide spectrum of libraries. Initially, for upgrading users, it will be better to have *some* access to these artifacts rather than clogging the MAVENUPLOAD project with re-requests. - -j Maczka Michal wrote: > I the fact that repository is changing constantly is even worst then the > fact that some POMs are missing or are incorrect. > > I cannot imagine somebody using m2 in production and relaying on such > unstable repository which introduces indeterminism to builds. > It's just enough to change an order of dependencies in one of the POMs and > some builds might be broken or what's very serious > not possible to reproduce in the future. > >>From this perspective it might be better to have a smaller but high quality > repository which is growing then a big crappy repository containing > invalid POMs or "naked" POMs like that > (http://www.ibiblio.org/maven2/axis/axis/1.2/axis-1.2.pom): > > project> > 4.0.0 > axis > axis > 1.2 > > > > IMO at least project description and license should be present in all POMs > in the repository. > It will be nice to have more things in those POMs (e.g. url of the main > website, organization section etc) > And unfortunately no tool can provide this information automatically. You > need many people to help you with that! > > > Michal > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCzqbPK3h2CZwO/4URApURAJ9YpBUWlFU4KJsD1p+3J5d/4HALtgCeI9iS 7a2AtOpduYGebUVd3YrxPZI= =nyW2 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-476) site:deploy only partially deploys site
[ http://jira.codehaus.org/browse/MNG-476?page=all ] Yann Le Du updated MNG-476: --- Attachment: MNG-476.txt If it wasn't executed on Unix, 'rm' would fail anyway... :) && didn't solve the issue. Moreover, it seemed to be a problem in cases when unzip gave a warning like " warning: site53426.zip appears to use backslashes as path separators " (did it exit with a different code or... ? ) Anyway, I solved the issue in a clumsy - yet efficient :) - way : redirecting the standard output of the unzip command seems to "force" the system to wait for command termination : unzip site53426.zip > output.txt I don't know if such a patch is OK for you, but here's the diff... > site:deploy only partially deploys site > --- > > Key: MNG-476 > URL: http://jira.codehaus.org/browse/MNG-476 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-alpha-2 > Environment: Windows XP for local run > IBM AIX for deployment server > Reporter: Yann Le Du > Assignee: Brett Porter > Fix For: 2.0-alpha-3 > Attachments: MNG-476.txt, fix.txt, log1.txt, log2.txt > > > I have forged a site in target/site (since site:site doesn't work yet, see > http://jira.codehaus.org/browse/MNG-389). Here is what I get when I try to > deploy it : log1.txt > When I look in //server/home/user, the directory www/docs/foo is created, but > it's either empty, either incomplete (it depends). > My guess is that these two commands : >cd /home/user/www/docs/foo/;unzip -o site6665.zip >rm /home/user/www/docs/foo//site6665.zip > were running concurrently, and the ZIP file was deleted before unzip was > finished. > To check this, I have tried to pause the process at different points, and > here is the result : log2.txt > I've tried to check out the Maven source code to fix and build it at my > place, but I got a lot of error messages at compile-time, so I gave up :) > Here is the fix that I would have tried (I didn't make a diff since I'm not > sure of the fix) : fix.txt -- 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] Reopened: (MNG-476) site:deploy only partially deploys site
[ http://jira.codehaus.org/browse/MNG-476?page=all ] Yann Le Du reopened MNG-476: I think I've found a solution and need to reopen the issue to attach the patch. > site:deploy only partially deploys site > --- > > Key: MNG-476 > URL: http://jira.codehaus.org/browse/MNG-476 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-alpha-2 > Environment: Windows XP for local run > IBM AIX for deployment server > Reporter: Yann Le Du > Assignee: Brett Porter > Fix For: 2.0-alpha-3 > Attachments: MNG-476.txt, fix.txt, log1.txt, log2.txt > > > I have forged a site in target/site (since site:site doesn't work yet, see > http://jira.codehaus.org/browse/MNG-389). Here is what I get when I try to > deploy it : log1.txt > When I look in //server/home/user, the directory www/docs/foo is created, but > it's either empty, either incomplete (it depends). > My guess is that these two commands : >cd /home/user/www/docs/foo/;unzip -o site6665.zip >rm /home/user/www/docs/foo//site6665.zip > were running concurrently, and the ZIP file was deleted before unzip was > finished. > To check this, I have tried to pause the process at different points, and > here is the result : log2.txt > I've tried to check out the Maven source code to fix and build it at my > place, but I got a lot of error messages at compile-time, so I gave up :) > Here is the fix that I would have tried (I didn't make a diff since I'm not > sure of the fix) : fix.txt -- 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]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/08-Jul-2005_12.00.50/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (MNG-556) NPE in MavenProject class
*checks pockets* Not yet. Finishing up the xmlbeans plugin right now. But I'll add one to the ticket later today. In the mean time, what should I look for to determine if the @requiresDependencyResolution tag is present? I want to be certain the exception is only thrown if it isn't set and not when it is set but there really are no dependencies to be returned. Kris On Fri, 2005-07-08 at 10:03 -0500, Emmanuel Venisse (JIRA) wrote: > [ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42572 ] > > Emmanuel Venisse commented on MNG-556: > -- > > do you have a patch? > > > NPE in MavenProject class > > - > > > > Key: MNG-556 > > URL: http://jira.codehaus.org/browse/MNG-556 > > Project: Maven 2 > > Type: Bug > > Components: maven-project > > Versions: 2.0-beta-1 > > Reporter: Vincent Siveton > > Fix For: 2.0-beta-1 > > Attachments: mavenproject.patch > > > > > > A NPE could be thrown in some circumstances (ie by the javadoc plugin) in > > the MavenProject class. > > getArtifacts() could be null. > > Lets see the patch. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r209815 - in /maven/components/trunk/maven-site/src/site/resources/developers: ./ svn-eol-style.txt
Author: evenisse Date: Fri Jul 8 08:21:58 2005 New Revision: 209815 URL: http://svn.apache.org/viewcvs?rev=209815&view=rev Log: Add our own svn config file. Added: maven/components/trunk/maven-site/src/site/resources/developers/ maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt (with props) Added: maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt?rev=209815&view=auto == --- maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt (added) +++ maven/components/trunk/maven-site/src/site/resources/developers/svn-eol-style.txt Fri Jul 8 08:21:58 2005 @@ -0,0 +1,79 @@ +[miscellany] +enable-auto-props = yes +[auto-props] +INSTALL = svn:eol-style=native;svn:keywords="Author Date Id Revision" +KEYS = svn:eol-style=native;svn:keywords="Author Date Id Revision" +Makefile = svn:eol-style=native;svn:keywords="Author Date Id Revision" +README = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.aart = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.ac = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.am = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.apt = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.bat = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.c = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.cat = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.cgi = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.classpath = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.cmd = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.cpp = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.css = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.cwiki = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.data = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.dcl = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.doc = svn:mime-type=application/msword +*.dsp = svn:eol-style=CRLF +*.dsw = svn:eol-style=CRLF +*.dtd = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.egrm = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.ent = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.ft = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.fml = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.fn = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.fv = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.grm = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.g = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.h = svn:eol-style=native;svn:keywords="Author Date Id Revision" +.htaccess = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.html = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.ico = svn:mime-type=image/x-icon +*.ihtml = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.in = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.java = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.jpg = svn:mime-type=image/jpeg +*.jsp = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.js = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.junit = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.m4 = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.mod = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.pdf = svn:mime-type=application/pdf +*.pen = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.pl = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.png = svn:mime-type=image/png +*.pod = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.project = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.properties = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.py = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.rb = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.rdf = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.rnc = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.rng = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.rnx = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.rss = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.sh = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.svg = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.tld = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.txt = svn:eol-style=native;svn:keywords="Author Date Id Revision" +*.types = svn:e
svn commit: r209814 - /maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Author: evenisse
Date: Fri Jul 8 08:19:28 2005
New Revision: 209814
URL: http://svn.apache.org/viewcvs?rev=209814&view=rev
Log:
Add our own svn config file.
Modified:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Modified:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt?rev=209814&r1=209813&r2=209814&view=diff
==
---
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
(original)
+++
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Fri Jul 8 08:19:28 2005
@@ -25,4 +25,4 @@
Before committing files in subversion repository, you need to read the
{{{http://www.apache.org/dev/version-control.html#https-svn}Committer
Subversion Access}}
document and you must set your svn client
-with these properties file :
{{http://www.apache.org/dev/svn-eol-style.txt}}
+with these properties file : {{svn-eol-style.txt}}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-556) NPE in MavenProject class
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42572 ] Emmanuel Venisse commented on MNG-556: -- do you have a patch? > NPE in MavenProject class > - > > Key: MNG-556 > URL: http://jira.codehaus.org/browse/MNG-556 > Project: Maven 2 > Type: Bug > Components: maven-project > Versions: 2.0-beta-1 > Reporter: Vincent Siveton > Fix For: 2.0-beta-1 > Attachments: mavenproject.patch > > > A NPE could be thrown in some circumstances (ie by the javadoc plugin) in the > MavenProject class. > getArtifacts() could be null. > Lets see the 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-556) NPE in MavenProject class
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42571 ] Trygve Laugstol commented on MNG-556: - Throwing a exception instead of silently ignoring it is definitely a better solution. > NPE in MavenProject class > - > > Key: MNG-556 > URL: http://jira.codehaus.org/browse/MNG-556 > Project: Maven 2 > Type: Bug > Components: maven-project > Versions: 2.0-beta-1 > Reporter: Vincent Siveton > Fix For: 2.0-beta-1 > Attachments: mavenproject.patch > > > A NPE could be thrown in some circumstances (ie by the javadoc plugin) in the > MavenProject class. > getArtifacts() could be null. > Lets see the 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-556) NPE in MavenProject class
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42570 ] Corridor Software Developer commented on MNG-556: - Ran into this as well while developing a plugin, only it was caused by not having @requiresDependencyResolution in the class javadoc. If the patch simply returns an empty Collection, it will quietly fail to return a proper classpath for plugin developers not familiar with this javadoc tag. So I recommend that, if the requiresDependencyResolution flag wasn't set properly, throw the DependencyResolutionRequiredException with a verbose message: "Dependencies have not been resolved. If this is a plugin, verify that @requiresDependencyResolution is set in the mojo object. See the developer's documentation for more detail." If it has been set and their are no artifacts, then an empty Collection would be appropriate. > NPE in MavenProject class > - > > Key: MNG-556 > URL: http://jira.codehaus.org/browse/MNG-556 > Project: Maven 2 > Type: Bug > Components: maven-project > Versions: 2.0-beta-1 > Reporter: Vincent Siveton > Fix For: 2.0-beta-1 > Attachments: mavenproject.patch > > > A NPE could be thrown in some circumstances (ie by the javadoc plugin) in the > MavenProject class. > getArtifacts() could be null. > Lets see the 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-562) Implement -Dmaven.test.skip=true
[ http://jira.codehaus.org/browse/MNG-562?page=all ] Emmanuel Venisse closed MNG-562: Resolution: Fixed Fix Version: 2.0-beta-1 Applied. Thanks. > Implement -Dmaven.test.skip=true > > > Key: MNG-562 > URL: http://jira.codehaus.org/browse/MNG-562 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Reporter: Trygve Laugstol > Fix For: 2.0-beta-1 > Attachments: surefire-skip-ignore.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r209803 - in /maven/components/trunk/maven-plugins/maven-surefire-plugin: pom.xml src/main/java/org/apache/maven/test/SurefirePlugin.java
Author: evenisse
Date: Fri Jul 8 07:53:06 2005
New Revision: 209803
URL: http://svn.apache.org/viewcvs?rev=209803&view=rev
Log:
[MNG-562] Add ignore failures
Modified:
maven/components/trunk/maven-plugins/maven-surefire-plugin/pom.xml
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
Modified: maven/components/trunk/maven-plugins/maven-surefire-plugin/pom.xml
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-surefire-plugin/pom.xml?rev=209803&r1=209802&r2=209803&view=diff
==
--- maven/components/trunk/maven-plugins/maven-surefire-plugin/pom.xml
(original)
+++ maven/components/trunk/maven-plugins/maven-surefire-plugin/pom.xml Fri Jul
8 07:53:06 2005
@@ -34,4 +34,10 @@
runtime
+
+
+ Joakim Erdfelt
+ [EMAIL PROTECTED]
+
+
Modified:
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java?rev=209803&r1=209802&r2=209803&view=diff
==
---
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
(original)
+++
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
Fri Jul 8 07:53:06 2005
@@ -46,11 +46,17 @@
{
/**
* Set this to 'true' to bypass unit tests entirely. Its use is NOT
RECOMMENDED, but quite convenient on occasion.
- * @parameter expression=${maven.test.skip}"
+ *
+ * @parameter expression="${maven.test.skip}"
*/
private boolean skip;
/**
+ * @parameter expression="${maven.test.failure.ignore}"
+ */
+private boolean testFailureIgnore = false;
+
+/**
* @parameter expression="${basedir}"
* @required
*/
@@ -238,7 +244,16 @@
if ( !success )
{
-throw new MojoExecutionException( "There are some test failures."
);
+String msg = "There are some test failure.";
+
+if ( testFailureIgnore )
+{
+getLog().error( msg );
+}
+else
+{
+throw new MojoExecutionException( msg );
+}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
SSH libraries in the Ant tasks
Hello, Can I request that the Ant tasks for Maven do not include the third party Jsch libraries in their own jar It may seem a good solution to your dependencies -bundle them in your own JAR, but the consequences are -unless you release the libs in perfect syncrhonisation with the jsch releases, your version will be behind -if someone has a different version of the jsch stuff on the classpath, they may not get what they want -the ant team ends up fielding the bug reports We have problems with existing libraries including stuff like oro and antlr, and have documented it http://ant.apache.org/manual/install.html#librarydependencies Please dont add to the list. I understand the value in secure downloads, but feel this is the wrong tactic. If having the library is a prerequisite, please point to the library at download time. Otherwise, well, surely dynamic downloading of stuff is what the library is meant to be good at? -steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-208) If an SCM command fails it would be useful to see the command that caused the failure
If an SCM command fails it would be useful to see the command that caused the failure - Key: CONTINUUM-208 URL: http://jira.codehaus.org/browse/CONTINUUM-208 Project: Continuum Type: Improvement Reporter: Jason van Zyl Fix For: 1.0-beta-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: [M2]NullPointerException on getCompileClasspathElements()
Already added in jira:
http://jira.codehaus.org/browse/MNG-556
Cheers,
Vincent
2005/7/8, Kris Bravo <[EMAIL PROTECTED]>:
> Thanks Kenney, that fixed the problem. At the same time, it would be
> helpful if the error explained this nuance.
>
> Before I add to Jira, can we assume that MavenProject.getArtifacts()
> should *never* return null for a valid project with resolved
> dependencies? If so, the method could throw an
> DependencyResolutionRequiredException instead:
>
> "Dependencies have not been resolved. If this is a plugin, verify that
> @requiresDependencyResolution is set in the mojo object. See the
> developer's documentation for more detail."
>
> Thoughts?
>
> Kris
>
> On Fri, 2005-07-08 at 09:29 +0200, Kenney Westerhof wrote:
> > On Fri, 8 Jul 2005, Kris Bravo wrote:
> >
> > You should define
> >
> > @requiresDependencyResolution compile
> >
> > in the class-level javadoc.
> >
> > > I have the following handle to the MavenProject defined in a plugin
> > > written for maven 2.
> > >
> > >/**
> > > * The project whose project files to create.
> > > *
> > > * @parameter expression="${project}"
> > > * @required
> > > */
> > >private MavenProject project;
> > >
> > > When I attempt to get the list of classpath elements, i.e.,
> > >
> > > project.getCompileClasspathElements()
> > >
> > > I receive a null pointer exception due to a call to
> > > getArtifacts().size();
> > >
> > > java.lang.NullPointerException
> > > at
> > > org.apache.maven.project.MavenProject.getCompileClasspathElements(MavenProject.java:282)
> > > at
> > > org.apache.maven.plugin.xmlbeans.XmlBeansPlugin.getClasspath(XmlBeansPlugin.java:271)
> > > at
> > > org.apache.maven.plugin.xmlbeans.ParameterAdapter.getCompilerParameters(ParameterAdapter.java:31)
> > > at
> > > org.apache.maven.plugin.xmlbeans.XmlBeansPlugin.execute(XmlBeansPlugin.java:203)
> > > at
> > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:401)
> > > at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:169)
> > > at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:143)
> > >
> > > Is there another way to retrieve a List of the classpath elements used
> > > by the java compiler during a build? Also, the debug lists elements
> > > (calls them constituents) in the classpath, but doesn't include those
> > > defined in the dependencies section of the pom.
> > >
> > > Am I barking up the wrong tree?
> > >
> > > Kris
> > >
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> > --
> > Kenney Westerhof
> > http://www.neonics.com
> > GPG public key: http://www.gods.nl/~forge/kenneyw.key
> >
> > -
> > 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]
Re: [M2]NullPointerException on getCompileClasspathElements()
Thanks Kenney, that fixed the problem. At the same time, it would be
helpful if the error explained this nuance.
Before I add to Jira, can we assume that MavenProject.getArtifacts()
should *never* return null for a valid project with resolved
dependencies? If so, the method could throw an
DependencyResolutionRequiredException instead:
"Dependencies have not been resolved. If this is a plugin, verify that
@requiresDependencyResolution is set in the mojo object. See the
developer's documentation for more detail."
Thoughts?
Kris
On Fri, 2005-07-08 at 09:29 +0200, Kenney Westerhof wrote:
> On Fri, 8 Jul 2005, Kris Bravo wrote:
>
> You should define
>
> @requiresDependencyResolution compile
>
> in the class-level javadoc.
>
> > I have the following handle to the MavenProject defined in a plugin
> > written for maven 2.
> >
> >/**
> > * The project whose project files to create.
> > *
> > * @parameter expression="${project}"
> > * @required
> > */
> >private MavenProject project;
> >
> > When I attempt to get the list of classpath elements, i.e.,
> >
> > project.getCompileClasspathElements()
> >
> > I receive a null pointer exception due to a call to
> > getArtifacts().size();
> >
> > java.lang.NullPointerException
> > at
> > org.apache.maven.project.MavenProject.getCompileClasspathElements(MavenProject.java:282)
> > at
> > org.apache.maven.plugin.xmlbeans.XmlBeansPlugin.getClasspath(XmlBeansPlugin.java:271)
> > at
> > org.apache.maven.plugin.xmlbeans.ParameterAdapter.getCompilerParameters(ParameterAdapter.java:31)
> > at
> > org.apache.maven.plugin.xmlbeans.XmlBeansPlugin.execute(XmlBeansPlugin.java:203)
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:401)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:169)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:143)
> >
> > Is there another way to retrieve a List of the classpath elements used
> > by the java compiler during a build? Also, the debug lists elements
> > (calls them constituents) in the classpath, but doesn't include those
> > defined in the dependencies section of the pom.
> >
> > Am I barking up the wrong tree?
> >
> > Kris
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> -
> 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]
svn commit: r209772 - /maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Author: evenisse
Date: Fri Jul 8 06:42:56 2005
New Revision: 209772
URL: http://svn.apache.org/viewcvs?rev=209772&view=rev
Log:
set svn properties
Modified:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
(contents, props changed)
Modified:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt?rev=209772&r1=209771&r2=209772&view=diff
==
---
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
(original)
+++
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Fri Jul 8 06:42:56 2005
@@ -1,28 +1,28 @@
- --
-Development Guide
- --
-Emmanuel Venisse
- --
-8 July 2005
- --
-
-~~ Copyright 2001-2004 The Apache Software Foundation.
-~~
-~~ Licensed under the Apache License, Version 2.0 (the "License");
-~~ you may not use this file except in compliance with the License.
-~~ You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing, software
-~~ distributed under the License is distributed on an "AS IS" BASIS,
-~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-~~ See the License for the specific language governing permissions and
-~~ limitations under the License.
-
-Subversion configuration
-
-Before committing files in subversion repository, you need to read the
-{{{http://www.apache.org/dev/version-control.html#https-svn}Committer
Subversion Access}}
-document and you must set your svn client
-with these properties file :
{{http://www.apache.org/dev/svn-eol-style.txt}}
+ --
+Development Guide
+ --
+Emmanuel Venisse
+ --
+8 July 2005
+ --
+
+~~ Copyright 2001-2004 The Apache Software Foundation.
+~~
+~~ Licensed under the Apache License, Version 2.0 (the "License");
+~~ you may not use this file except in compliance with the License.
+~~ You may obtain a copy of the License at
+~~
+~~ http://www.apache.org/licenses/LICENSE-2.0
+~~
+~~ Unless required by applicable law or agreed to in writing, software
+~~ distributed under the License is distributed on an "AS IS" BASIS,
+~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+~~ See the License for the specific language governing permissions and
+~~ limitations under the License.
+
+Subversion configuration
+
+Before committing files in subversion repository, you need to read the
+{{{http://www.apache.org/dev/version-control.html#https-svn}Committer
Subversion Access}}
+document and you must set your svn client
+with these properties file :
{{http://www.apache.org/dev/svn-eol-style.txt}}
Propchange:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
--
svn:eol-style = native
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r209770 - in /maven/components/trunk/maven-site/src/site: apt/developers/development-guide.apt site.xml
Author: evenisse
Date: Fri Jul 8 06:36:35 2005
New Revision: 209770
URL: http://svn.apache.org/viewcvs?rev=209770&view=rev
Log:
Add subversion config in developer guide.
Added:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Modified:
maven/components/trunk/maven-site/src/site/site.xml
Added:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt?rev=209770&view=auto
==
---
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
(added)
+++
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Fri Jul 8 06:36:35 2005
@@ -0,0 +1,28 @@
+ --
+Development Guide
+ --
+Emmanuel Venisse
+ --
+8 July 2005
+ --
+
+~~ Copyright 2001-2004 The Apache Software Foundation.
+~~
+~~ Licensed under the Apache License, Version 2.0 (the "License");
+~~ you may not use this file except in compliance with the License.
+~~ You may obtain a copy of the License at
+~~
+~~ http://www.apache.org/licenses/LICENSE-2.0
+~~
+~~ Unless required by applicable law or agreed to in writing, software
+~~ distributed under the License is distributed on an "AS IS" BASIS,
+~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+~~ See the License for the specific language governing permissions and
+~~ limitations under the License.
+
+Subversion configuration
+
+Before committing files in subversion repository, you need to read the
+{{{http://www.apache.org/dev/version-control.html#https-svn}Committer
Subversion Access}}
+document and you must set your svn client
+with these properties file :
{{http://www.apache.org/dev/svn-eol-style.txt}}
Modified: maven/components/trunk/maven-site/src/site/site.xml
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/site.xml?rev=209770&r1=209769&r2=209770&view=diff
==
--- maven/components/trunk/maven-site/src/site/site.xml (original)
+++ maven/components/trunk/maven-site/src/site/site.xml Fri Jul 8 06:36:35 2005
@@ -48,6 +48,7 @@
${reports}
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-207) Continuum should be in sync with the version of m2 used by the CI machine
Continuum should be in sync with the version of m2 used by the CI machine - Key: CONTINUUM-207 URL: http://jira.codehaus.org/browse/CONTINUUM-207 Project: Continuum Type: Task Reporter: Jason van Zyl Fix For: 1.0-alpha-3 Continuum should use the same repository and settings that m2 does on the CI machine. -- 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-206) Document the use of Continuum behind Apache using mod_proxy
[ http://jira.codehaus.org/browse/CONTINUUM-206?page=all ] Jason van Zyl updated CONTINUUM-206: Fix Version: (was: 1.0-beta-1) 1.0-alpha-3 > Document the use of Continuum behind Apache using mod_proxy > --- > > Key: CONTINUUM-206 > URL: http://jira.codehaus.org/browse/CONTINUUM-206 > Project: Continuum > Type: Task > Reporter: Jason van Zyl > Fix For: 1.0-alpha-3 > > > Write a simple APT document for those wishing to use Continuum with Apache. -- 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-206) Document the use of Continuum behind Apache using mod_proxy
Document the use of Continuum behind Apache using mod_proxy --- Key: CONTINUUM-206 URL: http://jira.codehaus.org/browse/CONTINUUM-206 Project: Continuum Type: Task Reporter: Jason van Zyl Fix For: 1.0-beta-1 Write a simple APT document for those wishing to use Continuum with Apache. -- 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-206) Document the use of Continuum behind Apache using mod_proxy
[ http://jira.codehaus.org/browse/CONTINUUM-206?page=all ] Jason van Zyl updated CONTINUUM-206: Fix Version: 1.0-beta-1 > Document the use of Continuum behind Apache using mod_proxy > --- > > Key: CONTINUUM-206 > URL: http://jira.codehaus.org/browse/CONTINUUM-206 > Project: Continuum > Type: Task > Reporter: Jason van Zyl > Fix For: 1.0-beta-1 > > > Write a simple APT document for those wishing to use Continuum with Apache. -- 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-198) Ability to pass a settings.xml file as a argument to the m2 cli
[ http://jira.codehaus.org/browse/CONTINUUM-198?page=all ]
Jason van Zyl updated CONTINUUM-198:
Fix Version: 1.0-beta-1
> Ability to pass a settings.xml file as a argument to the m2 cli
> ---
>
> Key: CONTINUUM-198
> URL: http://jira.codehaus.org/browse/CONTINUUM-198
> Project: Continuum
> Type: New Feature
> Reporter: Trygve Laugstol
> Fix For: 1.0-beta-1
>
>
> For continuum I need to be able to override the settings.xml file that used
> so I can give it ${continuum-home}/settings.xml instead of
> ${user.home}/.m2/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] Updated: (CONTINUUM-176) adding parent pom create duplicate continuum projects for all children
[ http://jira.codehaus.org/browse/CONTINUUM-176?page=all ] Jason van Zyl updated CONTINUUM-176: Fix Version: 1.0-beta-1 > adding parent pom create duplicate continuum projects for all children > -- > > Key: CONTINUUM-176 > URL: http://jira.codehaus.org/browse/CONTINUUM-176 > Project: Continuum > Type: Bug > Versions: 1.0-alpha-2 > Reporter: Ryan Sonnek > Fix For: 1.0-beta-1 > > > adding my parent maven2 project to continuum creates a continuum project for > each of my subprojects. the continuum project's start off with the label of > my subprojects, but once the build run's they all revert to the label of the > parent projects. > the build process for each of the subproject's is the same as well. they > don't actually just build the subproject. continuum builds the entire > project. > try using my project's pom at > https://shard.dev.java.net/source/browse/*checkout*/shard/pom.xml for an > example. -- 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-175) package continuum as a war
[ http://jira.codehaus.org/browse/CONTINUUM-175?page=all ] Jason van Zyl updated CONTINUUM-175: Fix Version: 1.0-beta-1 > package continuum as a war > -- > > Key: CONTINUUM-175 > URL: http://jira.codehaus.org/browse/CONTINUUM-175 > Project: Continuum > Type: New Feature > Components: continuum-web > Reporter: Ryan Sonnek > Fix For: 1.0-beta-1 > > > 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] Updated: (CONTINUUM-45) ability to use snapshot versions instead
[ http://jira.codehaus.org/browse/CONTINUUM-45?page=all ] Jason van Zyl updated CONTINUUM-45: --- Fix Version: 1.0-beta-1 > ability to use snapshot versions instead > > > Key: CONTINUUM-45 > URL: http://jira.codehaus.org/browse/CONTINUUM-45 > Project: Continuum > Type: New Feature > Reporter: Brett Porter > Fix For: 1.0-beta-1 > > > some profiles should build using all the latest artifacts regardless of what > the POM says (ala Gump). -- 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-187) Add yahoo messenger notifier
[ http://jira.codehaus.org/browse/CONTINUUM-187?page=all ] Jason van Zyl updated CONTINUUM-187: Fix Version: 1.0-beta-1 > Add yahoo messenger notifier > > > Key: CONTINUUM-187 > URL: http://jira.codehaus.org/browse/CONTINUUM-187 > Project: Continuum > Type: Improvement > Components: continuum-core > Reporter: Emmanuel Venisse > Fix For: 1.0-beta-1 > > > Use jymsg (http://jymsg9.sourceforge.net/) > http://www.devx.com/Java/Article/22546/0/page/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] Updated: (CONTINUUM-183) Should be able to build without using SCM.
[ http://jira.codehaus.org/browse/CONTINUUM-183?page=all ] Jason van Zyl updated CONTINUUM-183: Fix Version: 1.0-beta-1 > Should be able to build without using SCM. > -- > > Key: CONTINUUM-183 > URL: http://jira.codehaus.org/browse/CONTINUUM-183 > Project: Continuum > Type: Wish > Components: continuum-core > Versions: 1.0-alpha-2 > Environment: x86 > Windows NT 4.0 > j2sdk1.4.2_05 > maven 1.0.2 > Reporter: Simon Richardson > Priority: Blocker > Fix For: 1.0-beta-1 > > > The scm module does not support our version control system and I wondered if > there was a way to circumvent the scm aspect of continuum so that it only > builds what is on the file 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] Updated: (CONTINUUM-186) Can't set password in SCM url and neither a field is available for it
[ http://jira.codehaus.org/browse/CONTINUUM-186?page=all ] Jason van Zyl updated CONTINUUM-186: Fix Version: 1.0-beta-1 > Can't set password in SCM url and neither a field is available for it > - > > Key: CONTINUUM-186 > URL: http://jira.codehaus.org/browse/CONTINUUM-186 > Project: Continuum > Type: Improvement > Versions: 1.0-alpha-2 > Environment: Windows - CVS - Ant > Reporter: Erik Bengtson > Priority: Blocker > Fix For: 1.0-beta-1 > > > I have the following url > scm:cvs:pserver:user:[EMAIL PROTECTED]:/cvsroot:module > With the above url it says, invalid url. We need a place to set the password > for cvs login -- 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-193) Collapse the CheckoutScmResult and UpdateScmResult
[ http://jira.codehaus.org/browse/CONTINUUM-193?page=all ] Jason van Zyl updated CONTINUUM-193: Fix Version: 1.0-beta-1 > Collapse the CheckoutScmResult and UpdateScmResult > -- > > Key: CONTINUUM-193 > URL: http://jira.codehaus.org/browse/CONTINUUM-193 > Project: Continuum > Type: Task > Components: continuum-web, continuum-core > Reporter: Trygve Laugstol > Fix For: 1.0-beta-1 > > > Having two separate objects for this is just overkill and makes life more > complicated than it has to be. Right not the DefaultBuildController has to > transform the CheckOutScmResult to a UpdateScmResult and that should be > removed. -- 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-41) sort by different columns
[ http://jira.codehaus.org/browse/CONTINUUM-41?page=all ] Jason van Zyl updated CONTINUUM-41: --- Fix Version: 1.0-beta-1 > sort by different columns > - > > Key: CONTINUUM-41 > URL: http://jira.codehaus.org/browse/CONTINUUM-41 > Project: Continuum > Type: New Feature > Reporter: Brett Porter > Priority: Trivial > Fix For: 1.0-beta-1 > > > it would be nice to be able to sort by the various columns in the summary > page, in particular so you can elevate failed projects to the top. -- 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-68) Make Continuum control database initialization and destruction.
[ http://jira.codehaus.org/browse/CONTINUUM-68?page=all ] Jason van Zyl updated CONTINUUM-68: --- Fix Version: 1.0-beta-1 > Make Continuum control database initialization and destruction. > --- > > Key: CONTINUUM-68 > URL: http://jira.codehaus.org/browse/CONTINUUM-68 > Project: Continuum > Type: Improvement > Components: continuum-core > Versions: 1.0-alpha-1 > Reporter: Trygve Laugstol > Fix For: 1.0-beta-1 > > > Continuum should be able to autodetect if the application has been properly > configured and if not autmatically set up a database given a configuration > either from the user or from a configuration file. This should possibly be > integrated into the web view so the application won't start up all the way > without a proper storage. -- 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-27) Display the type of the component that was built
[ http://jira.codehaus.org/browse/CONTINUUM-27?page=all ] Jason van Zyl updated CONTINUUM-27: --- Fix Version: 1.0-beta-1 > Display the type of the component that was built > > > Key: CONTINUUM-27 > URL: http://jira.codehaus.org/browse/CONTINUUM-27 > Project: Continuum > Type: Improvement > Reporter: Emmanuel Venisse > Fix For: 1.0-beta-1 > > > And the type of the component can be help to find wich default goal we can > run. > pom => pom:install > jar(or empty) => jar:install > war => war:install > plugin => plugin:install > ... -- 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-197) Improve the start page of the web application
[ http://jira.codehaus.org/browse/CONTINUUM-197?page=all ] Jason van Zyl updated CONTINUUM-197: Fix Version: 1.0-beta-1 > Improve the start page of the web application > - > > Key: CONTINUUM-197 > URL: http://jira.codehaus.org/browse/CONTINUUM-197 > Project: Continuum > Type: Improvement > Versions: 1.0-alpha-2 > Reporter: Trygve Laugstol > Fix For: 1.0-beta-1 > > > Currently the web application only has a link saying "GO HERE" which isn't > exactly elegant. -- 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-205) Document the use of Continuum behind Apache using mod_proxy
Document the use of Continuum behind Apache using mod_proxy --- Key: CONTINUUM-205 URL: http://jira.codehaus.org/browse/CONTINUUM-205 Project: Continuum Type: Task Reporter: Jason van Zyl Fix For: 1.0-beta-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
svn commit: r209763 - in /maven/components/trunk/maven-plugins/maven-clover: ./ maven-clover-plugin-samples/ maven-clover-plugin-samples/maven-clover-plugin-sample-simple/ maven-clover-plugin/ maven-clover-plugin/src/main/resources/ maven-clover-plugin...
Author: vmassol Date: Fri Jul 8 06:17:26 2005 New Revision: 209763 URL: http://svn.apache.org/viewcvs?rev=209763&view=rev Log: Fixed svn properties (eol and keywords) that were not set for non-java files in my config. Modified: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/pom.xml (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/pom.xml (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/resources/META-INF/maven/lifecycle.xml (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/resources/META-INF/plexus/components.xml (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/resources/clover-report_en.properties (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/resources/clover-report_fr.properties (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/resources/clover.license (contents, props changed) maven/components/trunk/maven-plugins/maven-clover/pom.xml (contents, props changed) Modified: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml?rev=209763&r1=209762&r2=209763&view=diff == --- maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml (original) +++ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml Fri Jul 8 06:17:26 2005 @@ -1,55 +1,55 @@ - - 4.0.0 - -org.apache.maven.plugins -maven-clover-plugin-samples -1.0-SNAPSHOT - - maven-clover-plugin-sample-simple - jar - Maven Clover Plugin Simple Sample - Maven Clover Plugin Simple Sample - 1.0-SNAPSHOT - - - junit - junit - 3.8.1 - test - - - - clover - clover - 1.3.8 - - - - - -org.apache.maven.plugins -maven-clover-plugin -1.0-SNAPSHOT - - - - - - -org.apache.maven.plugins -maven-clover-plugin -1.0-SNAPSHOT - - - - 50 - - - check - - - - - - - + + 4.0.0 + +org.apache.maven.plugins +maven-clover-plugin-samples +1.0-SNAPSHOT + + maven-clover-plugin-sample-simple + jar + Maven Clover Plugin Simple Sample + Maven Clover Plugin Simple Sample + 1.0-SNAPSHOT + + + junit + junit + 3.8.1 + test + + + + clover + clover + 1.3.8 + + + + + +org.apache.maven.plugins +maven-clover-plugin +1.0-SNAPSHOT + + + + + + +org.apache.maven.plugins +maven-clover-plugin +1.0-SNAPSHOT + + + + 50 + + + check + + + + + + + Propchange: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml -- svn:eol-style = native Propchange: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml -- svn:keywords = "Author Date Id Revision" Modified: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/pom.xml?rev=209763&r1=209762&r2=209763&view=diff == --- maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/pom.xml (original) +++ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/pom.xml Fri Jul 8 06:17:26 2005 @@ -1,16 +1,16 @@ - - 4.0.0 - -org.apache.maven.plugins -maven-clover -1.0-SNAPSHOT - - maven-clover-plugin-samples - pom - Maven Clover Plugin Samples - Maven Clover Plugin Samples - 1.0-SN
svn commit: r209758 - in /maven/components/trunk/maven-plugins/maven-clover: ./ maven-clover-plugin-samples/ maven-clover-plugin-samples/maven-clover-plugin-sample-simple/
Author: vmassol Date: Fri Jul 8 06:10:21 2005 New Revision: 209758 URL: http://svn.apache.org/viewcvs?rev=209758&view=rev Log: added ignore files Modified: maven/components/trunk/maven-plugins/maven-clover/ (props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/ (props changed) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/ (props changed) Propchange: maven/components/trunk/maven-plugins/maven-clover/ -- --- svn:ignore (added) +++ svn:ignore Fri Jul 8 06:10:21 2005 @@ -0,0 +1,5 @@ +.classpath +.project +*.iml +*.ipr +*.iws Propchange: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/ -- --- svn:ignore (added) +++ svn:ignore Fri Jul 8 06:10:21 2005 @@ -0,0 +1,3 @@ +*.iml +*.ipr +*.iws Propchange: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/ -- --- svn:ignore (added) +++ svn:ignore Fri Jul 8 06:10:21 2005 @@ -0,0 +1,4 @@ +target +*.iml +*.ipr +*.iws - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-562) Implement -Dmaven.test.skip=true
[ http://jira.codehaus.org/browse/MNG-562?page=all ] Joakim Erdfelt updated MNG-562: --- Attachment: surefire-skip-ignore.patch I already had this implemented... Patch is attached. > Implement -Dmaven.test.skip=true > > > Key: MNG-562 > URL: http://jira.codehaus.org/browse/MNG-562 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Reporter: Trygve Laugstol > Attachments: surefire-skip-ignore.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r209755 - /maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
Author: evenisse
Date: Fri Jul 8 06:01:15 2005
New Revision: 209755
URL: http://svn.apache.org/viewcvs?rev=209755&view=rev
Log:
[MNG-562] Implement -Dmaven.test.skip=true
Modified:
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
Modified:
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java?rev=209755&r1=209754&r2=209755&view=diff
==
---
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
(original)
+++
maven/components/trunk/maven-plugins/maven-surefire-plugin/src/main/java/org/apache/maven/test/SurefirePlugin.java
Fri Jul 8 06:01:15 2005
@@ -44,6 +44,11 @@
public class SurefirePlugin
extends AbstractMojo
{
+/**
+ * Set this to 'true' to bypass unit tests entirely. Its use is NOT
RECOMMENDED, but quite convenient on occasion.
+ * @parameter expression=${maven.test.skip}"
+ */
+private boolean skip;
/**
* @parameter expression="${basedir}"
@@ -124,6 +129,13 @@
public void execute()
throws MojoExecutionException
{
+if ( skip )
+{
+getLog().info( "Tests are skipped." );
+
+return;
+}
+
//
--
// Setup the surefire booter
//
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r209753 - /maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/
Author: vmassol Date: Fri Jul 8 05:57:46 2005 New Revision: 209753 URL: http://svn.apache.org/viewcvs?rev=209753&view=rev Log: added ignore files Modified: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/ (props changed) Propchange: maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/ -- --- svn:ignore (added) +++ svn:ignore Fri Jul 8 05:57:46 2005 @@ -0,0 +1,6 @@ +.classpath +.project +*.iml +*.ipr +*.iws +target - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-204) Add SOAP interface using xfire
Add SOAP interface using xfire -- Key: CONTINUUM-204 URL: http://jira.codehaus.org/browse/CONTINUUM-204 Project: Continuum Type: New Feature Reporter: Jason van Zyl Fix For: 1.0-beta-1 Dan will be taking care of this. -- 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-203) Plexus runtime should have solaris capability
Plexus runtime should have solaris capability - Key: CONTINUUM-203 URL: http://jira.codehaus.org/browse/CONTINUUM-203 Project: Continuum Type: Improvement Reporter: Jason van Zyl Fix For: 1.0-beta-1 The plexus runtime generator needs to be improved to have this. -- 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
svn commit: r209751 - in /maven/components/trunk/maven-plugins/maven-clover: ./ maven-clover-plugin-samples/ maven-clover-plugin-samples/maven-clover-plugin-sample-simple/ maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/ maven-clover-...
Author: vmassol Date: Fri Jul 8 05:52:48 2005 New Revision: 209751 URL: http://svn.apache.org/viewcvs?rev=209751&view=rev Log: - Initial commit of the Clover plugin - The CloverCheckMojo still doesn't seem to work and report a coverage error when used in the simple sample. Not sure why yet - The CloverReportMojo doesn't work as mixed plugins do not seem to be supported yet. Added: maven/components/trunk/maven-plugins/maven-clover/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/pom.xml maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/apache/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/apache/maven/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/apache/maven/plugin/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/apache/maven/plugin/clover/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/apache/maven/plugin/clover/samples/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/apache/maven/plugin/clover/samples/simple/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/main/java/org/apache/maven/plugin/clover/samples/simple/Simple.java (with props) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/apache/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/apache/maven/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/apache/maven/plugin/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/apache/maven/plugin/clover/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/apache/maven/plugin/clover/samples/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/apache/maven/plugin/clover/samples/simple/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/maven-clover-plugin-sample-simple/src/test/java/org/apache/maven/plugin/clover/samples/simple/SimpleTest.java (with props) maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin-samples/pom.xml maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/pom.xml maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/java/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/java/org/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/java/org/apache/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/java/org/apache/maven/ maven/components/trunk/maven-plugins/maven-clover/maven-clover-plugin/src/main/java/org/apache/maven/plugin/ maven/components/trunk/maven-plugins/maven-clover/maven-cl
[jira] Created: (MNG-562) Implement -Dmaven.test.skip=true
Implement -Dmaven.test.skip=true Key: MNG-562 URL: http://jira.codehaus.org/browse/MNG-562 Project: Maven 2 Type: Improvement Components: maven-plugins Reporter: Trygve Laugstol -- 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]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/08-Jul-2005_08.00.39/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-561) Adding more options for the javadoc plugin
Adding more options for the javadoc plugin -- Key: MNG-561 URL: http://jira.codehaus.org/browse/MNG-561 Project: Maven 2 Type: Bug Components: maven-reports Versions: 2.0-beta-1 Reporter: Vincent Siveton Fix For: 2.0-beta-1 Actually, we cannot set specific option for the javadoc plugin, ie at least those m1. Moreover, with maven-artifact-test plugin, the javadoc goal doesn't work without the package option. -- 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-560) project-info-reports doesnt handle correctly locales
project-info-reports doesnt handle correctly locales Key: MNG-560 URL: http://jira.codehaus.org/browse/MNG-560 Project: Maven 2 Type: Bug Components: maven-reports Versions: 2.0-beta-1 Reporter: Vincent Siveton Fix For: 2.0-beta-1 This following configuration fr_CA has no effect for this plugin. Maybe, we could display a warn message if a locale is unsupported. Moreover, we could validate the user entry with Locale.getAvailableLocales() -- 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: (MNG-552) javacc plugin in m2
[ http://jira.codehaus.org/browse/MNG-552?page=all ] allan ramirez updated MNG-552: -- Attachment: maven-javacc-plugin.zip Hi, Attached file is the 2nd version of the javacc-plugin. It can now support the rest of the option settings. listed below. LOOKAHEAD CHOICE_AMBIGUITY_CHECK OTHER_AMBIGUITY_CHECK STATIC DEBUG_PARSER DEBUG_LOOKAHEAD DEBUG_TOKEN_MANAGER OPTIMIZE_TOKEN_MANAGER ERROR_REPORTING JAVA_UNICODE_ESCAPE UNICODE_INPUT IGNORE_CASE COMMON_TOKEN_ACTION USER_TOKEN_MANAGER USER_CHAR_STREAM BUILD_PARSER BUILD_TOKEN_MANAGER SANITY_CHECK FORCE_LA_CHECK CACHE_TOKENS KEEP_LINE_COLUMN OUTPUT_DIRECTORY The plugin can be invoked using the goal "javacc:override-generate". -allan > javacc plugin in m2 > --- > > Key: MNG-552 > URL: http://jira.codehaus.org/browse/MNG-552 > Project: Maven 2 > Type: New Feature > Components: maven-plugins > Versions: 2.0-alpha-3 > Environment: Windows XP Home Edition, JDK 1.5, Maven 2.0 alpha 3, JavaCC 3.2 > Reporter: allan ramirez > Priority: Minor > Attachments: maven-javacc-plugin.zip, maven-javacc-plugin.zip, reports.txt > > > A javacc (parser generator) plugin for M2, As of now it only supports 2 > option settings, OUTPUT_DIRECTORY, which the user can set their desired > directory and the TARGET FILE NAME, which refers to the directory of the .jj > file. > The attachment includes junit test case and the source code. > I am almost done with the rest of the option settings. -- 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: (MAVEN-1258) Can't run replacetoken ant tag inside maven
[ http://jira.codehaus.org/browse/MAVEN-1258?page=comments#action_42559 ] Jacek Laskowski commented on MAVEN-1258: A tested workaround in Maven 1.0.2 is to call from within maven.xml. The build.xml file would then look as follows: It works fine. > Can't run replacetoken ant tag inside maven > --- > > Key: MAVEN-1258 > URL: http://jira.codehaus.org/browse/MAVEN-1258 > Project: maven > Type: Bug > Versions: 1.0-rc2 > Environment: Maven 1.0-rc2 > Windows 2000 SP4 > J2SDK 1.4.2_04 > Ant 1.5.3 > Reporter: Cassio Matsuo Nosshe > Fix For: 1.1-beta-2 > > > Maven can't run replacetoken tag... Maven, Jelly or Werkz seams to > delete the content inside replacetoken tag before ant is > executed by maven... > >123 >12345 > > With this example, String "123" is deleted, and ant (executed by maven) can't > run because "The token attribute must not be an empty string." > I've tested it in my build.xml and works: > > > 123 > 12345 > > > but with maven 1.0-rc2 (maven.xml), with the same code: > > > 123 > 12345 > > > ...does not work. > NOTE: There is no workaround for this, because replacetoken/replacevalue are > used for special characters like '<' and '>' (inside ), and the tag > won't work, because such > characters are not allowed in this construction... -- 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]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/08-Jul-2005_04.00.56/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: POM issues in the repository
> -Original Message- > From: John Casey [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 07, 2005 7:12 PM > To: Maven Developers List > Subject: Re: POM issues in the repository > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > 1. define sanity. > > 2. define validity. > > We have a tool out there right now that converts POMs from > the m1 repository to the m2 repository, and does some meager > checking on the XML/model validity of the POM on the way. > HOWEVER, that's not the same as saying it checks that all of > that POM's deps are in the repository. > > Reiterating what Emmanuel said, we do have plans to enhance > this application and provide much more > functionality...eventually. So far, we've been emphasizing > the development and stability of m2 over this tool. If you'd > like to log a specific issue, you might want to do so in the > Maven Repository Manager project (MRM) in JIRA...if it's a > specific POM you're having trouble with, you can do one of two things: > > 1. add an exclusions block to your dependency (useful for > dom4j). This will work if the dependency has a dependency > which is only used in certain cases, which you are not interested in. > > 2. file an issue in MEV (Maven Evangelism) JIRA, or enhance a > current issue. If the POM is really bad (not just a bad build > design on the part of dom4j or something), then we can only > fix our copy and get in touch with the dom4j guys to fix it > at the source. However, if for some reason that POM's > filesystem timestamp changes in our staging repository, the > same old problems will be re-propagated. This is because we > consider the dependencies given by a project's development > team in the POM to be authoritative by default. > > We're all pretty much aware that the metadata from the > maven-1 repository is somewhat lacking, to say the least. > Unfortunately, due to the decentralized control over the > repository's contents (projects are supposed to be in control > of their own information, as we cannot be experts on all > projects we supply in the repository), I'm not at all > convinced that there is an easier way to clean this stuff up. > > Of course, suggestions and help are both very welcome. :) > If I can have a suggestion: I the fact that repository is changing constantly is even worst then the fact that some POMs are missing or are incorrect. I cannot imagine somebody using m2 in production and relaying on such unstable repository which introduces indeterminism to builds. It's just enough to change an order of dependencies in one of the POMs and some builds might be broken or what's very serious not possible to reproduce in the future. >From this perspective it might be better to have a smaller but high quality repository which is growing then a big crappy repository containing invalid POMs or "naked" POMs like that (http://www.ibiblio.org/maven2/axis/axis/1.2/axis-1.2.pom): project> 4.0.0 axis axis 1.2 IMO at least project description and license should be present in all POMs in the repository. It will be nice to have more things in those POMs (e.g. url of the main website, organization section etc) And unfortunately no tool can provide this information automatically. You need many people to help you with that! Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2]NullPointerException on getCompileClasspathElements()
On Fri, 8 Jul 2005, Kris Bravo wrote:
You should define
@requiresDependencyResolution compile
in the class-level javadoc.
> I have the following handle to the MavenProject defined in a plugin
> written for maven 2.
>
>/**
> * The project whose project files to create.
> *
> * @parameter expression="${project}"
> * @required
> */
>private MavenProject project;
>
> When I attempt to get the list of classpath elements, i.e.,
>
> project.getCompileClasspathElements()
>
> I receive a null pointer exception due to a call to
> getArtifacts().size();
>
> java.lang.NullPointerException
> at
> org.apache.maven.project.MavenProject.getCompileClasspathElements(MavenProject.java:282)
> at
> org.apache.maven.plugin.xmlbeans.XmlBeansPlugin.getClasspath(XmlBeansPlugin.java:271)
> at
> org.apache.maven.plugin.xmlbeans.ParameterAdapter.getCompilerParameters(ParameterAdapter.java:31)
> at
> org.apache.maven.plugin.xmlbeans.XmlBeansPlugin.execute(XmlBeansPlugin.java:203)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:401)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:169)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:143)
>
> Is there another way to retrieve a List of the classpath elements used
> by the java compiler during a build? Also, the debug lists elements
> (calls them constituents) in the classpath, but doesn't include those
> defined in the dependencies section of the pom.
>
> Am I barking up the wrong tree?
>
> Kris
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
