[jira] Commented: (MNG-483) sort out artifact attachment
[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44078 ] Brett Porter commented on MNG-483: -- 1) Jason Grant is looking at implementing the attaching of artifacts during assembly:assembly which is a part of this 2) on my "tricky bit" comment above, this can probably be resolved by having that be @execute phase="package" cliOnly="true" (where cliOnly is a new construct indicating the goal had to be called explicitly to trigger it, instead of during the lifecycle for package). This hearkens back to "reverse lookup of the lifecycle for a goal", so should review that issue first to see whether there are other reasons to beware of here. > sort out artifact attachment > > > Key: MNG-483 > URL: http://jira.codehaus.org/browse/MNG-483 > Project: Maven 2 > Type: Bug > Reporter: Brett Porter > Assignee: John Casey > Priority: Blocker > Fix For: 2.0-beta-1 > > > currently, there is an attachArtifact call inside the plugin building the > attachment. It imposes a m-a and m-p dependency, as well as an > artifactFactory requirement to be able to construct the artifact to attach. > sort out > - if there is an easier way to achieve this > - how to retain the default source binding, but also how to turn it off > - how to make the source binding happen only on "release" (bear in mind > people may not be using the release plugin... a profile was the original idea) > - how to bind assembly similarly -- 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: Question About Reactor Operation
Hi, Allison, Bob wrote: >(I was going to try to find the reactor code in my SVN tree before >asking this, but can't seem to find it :-( ) > > It's in DefaultMaven presently (it may have moved to the DefaultLifecycleExecutor in part, I haven't looked since the recent aggregation changes). >Use Case 1: There are a number of project directories which do not >produce artifacts (the top level and all mid-level directories, for >example) as well as a few projects which are samples and should not be >included in the production deliverables. > > Set these to packaging "pom". >Use Case 2: When generating documentation, I need to include the top >level and mid-level directories in order to get the lower-level projects >documented. I also want some of the samples to be included in the >product documentation. > > We're working on a proposal for having the site become reactor aware out of the box. >Use Case 3: Because of some constraints in the portal server we are >using, we need to combine a few of the portlets into a single web >application. We would like to keep the portlets in individual projects >and be able to deploy the portlet either by itself or as part of a >combined web application. > > This should be done by creating a web application subproject that depends on the portlet projects. >In case 2, I filter the list of projects by replacing the >"multiproject:projects-init" goal with one that has all of the original >code plus some additional code to remove projects that do not have one >of the use case properties set to true (case 1 is >"productname.production", case 2 is "productname.document", case 3 is >"productname.one-app"). For the other two cases, I wrote my own search >goal and provide the reactor with a list of projects. > > I didn't catch how this acheieved what you were doing for the site? >It would be really nice to be able to create a plugin which can contain >a method that the reactor calls after finding the project but before >starting to work on it; the method could return a true/false to indicate >whether or not the project passes the filter. To make this transparent >to plugins that don't need this functionality, we would need a concrete >implementation of the method in AbstractMojo which always returns true >(unfortunately, this doesn't help those which choose to implement the >interface rather than extend the abstract base class). > > I'm not sure this is necessary: you can simply check what you need to know about the project at the start of the execute() method and return successfully if you don't deal with it. What you might be wanting is when it works in an aggregate mode, which works differently - the plugin goal is run at the top level with a selection of projects instead of being run on the subprojects - in this case you can again filter the project list in the execute() method. Interesting idea, but I'd probably want to look at more use cases and check whether they are already covered or not. Thanks, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question About Reactor Operation
I forgot to mention that I am trying to get this working in Maven 2 -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Saturday, August 06, 2005 23:53 To: dev@maven.apache.org Subject: Question About Reactor Operation (I was going to try to find the reactor code in my SVN tree before asking this, but can't seem to find it :-( ) General Info: Our Maven 1.0.2 development tree consists of three directory levels: The top level has global goals and properties, the mid-level directories are artifact-specific (portlet, webapp, library, ...) and contains goals and properties related to the particular type of artifact being produced (this includes alias-type goals which allow the developer to type "maven install" in any project and get the right goal executed), the bottom-layer directories contain artifact-generating projects. I was wondering if there has been any thought towards being able to optionally filter the projects that the reactor is going to run. I have three use cases that I have working to various degrees in Maven 1.0.2: Use Case 1: There are a number of project directories which do not produce artifacts (the top level and all mid-level directories, for example) as well as a few projects which are samples and should not be included in the production deliverables. Use Case 2: When generating documentation, I need to include the top level and mid-level directories in order to get the lower-level projects documented. I also want some of the samples to be included in the product documentation. Use Case 3: Because of some constraints in the portal server we are using, we need to combine a few of the portlets into a single web application. We would like to keep the portlets in individual projects and be able to deploy the portlet either by itself or as part of a combined web application. In case 2, I filter the list of projects by replacing the "multiproject:projects-init" goal with one that has all of the original code plus some additional code to remove projects that do not have one of the use case properties set to true (case 1 is "productname.production", case 2 is "productname.document", case 3 is "productname.one-app"). For the other two cases, I wrote my own search goal and provide the reactor with a list of projects. It would be really nice to be able to create a plugin which can contain a method that the reactor calls after finding the project but before starting to work on it; the method could return a true/false to indicate whether or not the project passes the filter. To make this transparent to plugins that don't need this functionality, we would need a concrete implementation of the method in AbstractMojo which always returns true (unfortunately, this doesn't help those which choose to implement the interface rather than extend the abstract base class). I have not yet been able to spend the required amount of time to start building a plugin, so I do not understand how things work well enough to know if this is even a reasonable request. If this is not feasible, I understand and will do my best to rearrange how we are doing things (or stick with 1.0.2 for a while longer). - 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]
Question About Reactor Operation
(I was going to try to find the reactor code in my SVN tree before asking this, but can't seem to find it :-( ) General Info: Our Maven 1.0.2 development tree consists of three directory levels: The top level has global goals and properties, the mid-level directories are artifact-specific (portlet, webapp, library, ...) and contains goals and properties related to the particular type of artifact being produced (this includes alias-type goals which allow the developer to type "maven install" in any project and get the right goal executed), the bottom-layer directories contain artifact-generating projects. I was wondering if there has been any thought towards being able to optionally filter the projects that the reactor is going to run. I have three use cases that I have working to various degrees in Maven 1.0.2: Use Case 1: There are a number of project directories which do not produce artifacts (the top level and all mid-level directories, for example) as well as a few projects which are samples and should not be included in the production deliverables. Use Case 2: When generating documentation, I need to include the top level and mid-level directories in order to get the lower-level projects documented. I also want some of the samples to be included in the product documentation. Use Case 3: Because of some constraints in the portal server we are using, we need to combine a few of the portlets into a single web application. We would like to keep the portlets in individual projects and be able to deploy the portlet either by itself or as part of a combined web application. In case 2, I filter the list of projects by replacing the "multiproject:projects-init" goal with one that has all of the original code plus some additional code to remove projects that do not have one of the use case properties set to true (case 1 is "productname.production", case 2 is "productname.document", case 3 is "productname.one-app"). For the other two cases, I wrote my own search goal and provide the reactor with a list of projects. It would be really nice to be able to create a plugin which can contain a method that the reactor calls after finding the project but before starting to work on it; the method could return a true/false to indicate whether or not the project passes the filter. To make this transparent to plugins that don't need this functionality, we would need a concrete implementation of the method in AbstractMojo which always returns true (unfortunately, this doesn't help those which choose to implement the interface rather than extend the abstract base class). I have not yet been able to spend the required amount of time to start building a plugin, so I do not understand how things work well enough to know if this is even a reasonable request. If this is not feasible, I understand and will do my best to rearrange how we are doing things (or stick with 1.0.2 for a while longer). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPOCLEAN] Error(s) occurred while converting repository
Ok, you shouldn't see any more of these - they've all been corrected. If the mail comes again, it means something actually broke and should be fixed at the source. Cheers, Brett REPOCLEAN wrote: >Errors occurred while performing maven-1 to maven-2 repository conversion. > >For more details, see: > >http://test.maven.codehaus.org/reports/repoclean/06-Aug-2005_11.23.17/repository.report.txt > >- >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]
[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/06-Aug-2005_11.23.17/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-47) Codehaus synced poms
[ http://jira.codehaus.org/browse/MEV-47?page=all ] Brett Porter closed MEV-47: --- Assign To: Brett Porter Resolution: Fixed > Codehaus synced poms > > > Key: MEV-47 > URL: http://jira.codehaus.org/browse/MEV-47 > Project: Maven Evangelism > Type: Task > Components: Invalid POM > Reporter: Brett Porter > Assignee: Brett Porter > > > these ones go off every time :( -- 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/06-Aug-2005_11.20.25/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/06-Aug-2005_11.06.18/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-695) Exceptions thrown building project information report "Source Repository"
[ http://jira.codehaus.org/browse/MNG-695?page=all ] Vincent Siveton closed MNG-695: --- Resolution: Won't Fix Partially applied. Thanks! > Exceptions thrown building project information report "Source Repository" > - > > Key: MNG-695 > URL: http://jira.codehaus.org/browse/MNG-695 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Reporter: Bob Allison > Assignee: Vincent Siveton > Fix For: 2.0-beta-1 > > > (This was working yesterday. This morning I updated my SVN tree to 227227 > and this started happening.) > I am not currently using SCM features of Maven, so I do not have a developer > connection defined. In v1.0.2, I have always had an empty tag in the > project.xml. > If the v2 POM has "", I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:209) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:267) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: java.lang.StringIndexOutOfBoundsException: String index out of > range: -4 > at java.lang.String.substring(String.java:1768) > at java.lang.String.substring(String.java:1735) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.findDelimiter(DefaultScmManager.java:218) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmRepository(DefaultScmManager.java:118) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.getScmRepository(ScmReport.java:632) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderBody(ScmReport.java:200) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.ScmReport.executeReport(ScmReport.java:135) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:290) > ... 16 more > If a comment out the stanza, I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Defaul
svn commit: r230612 - in /maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src: main/java/org/apache/maven/report/projectinfo/ test/projects/project-info-reports-plugin-test11/
Author: vsiveton
Date: Sat Aug 6 17:07:50 2005
New Revision: 230612
URL: http://svn.apache.org/viewcvs?rev=230612&view=rev
Log:
MNG-695: Added more tests on anonymousConnection, devConnection and scmUrl to
prevent NPE. Added the test case num 11.
Added:
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/test/projects/project-info-reports-plugin-test11/
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/test/projects/project-info-reports-plugin-test11/pom.xml
(with props)
Modified:
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/ScmReport.java
Modified:
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/ScmReport.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/ScmReport.java?rev=230612&r1=230611&r2=230612&view=diff
==
---
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/ScmReport.java
(original)
+++
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/ScmReport.java
Sat Aug 6 17:07:50 2005
@@ -196,6 +196,19 @@
anonymousConnection = scm.getConnection();
devConnection = scm.getDeveloperConnection();
+if ( StringUtils.isEmpty( anonymousConnection ) &&
+StringUtils.isEmpty( devConnection ) &&
+StringUtils.isEmpty( scm.getUrl() ) )
+{
+startSection( getTitle() );
+
+paragraph( getBundle( locale ).getString( "report.scm.noscm" )
);
+
+endSection();
+
+return;
+}
+
ScmRepository anonymousRepository = getScmRepository(
anonymousConnection );
ScmRepository devRepository = getScmRepository( devConnection );
@@ -264,7 +277,7 @@
{
startSection( getBundle( locale ).getString(
"report.scm.webaccess.title" ) );
-if ( scmUrl == null )
+if ( StringUtils.isEmpty( scmUrl ) )
{
paragraph( getBundle( locale ).getString(
"report.scm.webaccess.nourl" ) );
}
@@ -288,7 +301,8 @@
{
if ( ( isScmSystem( anonymousRepository, "clearcase" ) )
|| ( isScmSystem( anonymousRepository, "perforce" ) )
-|| ( isScmSystem( anonymousRepository, "starteam" ) ) )
+|| ( isScmSystem( anonymousRepository, "starteam" ) )
+|| ( StringUtils.isEmpty( anonymousConnection ) ) )
{
return;
}
@@ -313,6 +327,11 @@
{
paragraph( getBundle( locale ).getString(
"report.scm.anonymousaccess.general.intro" ) );
+if ( anonymousConnection.length() < 4 )
+{
+throw new IllegalArgumentException( "The source repository
connection is too short." );
+}
+
verbatimText( anonymousConnection.substring( 4 ) );
}
@@ -326,6 +345,11 @@
*/
private void renderDeveloperAccessSection( ScmRepository devRepository
)
{
+if ( StringUtils.isEmpty( devConnection ) )
+{
+return;
+}
+
startSection( getBundle( locale ).getString(
"report.scm.devaccess.title" ) );
if ( ( devRepository != null ) && ( isScmSystem( devRepository,
"clearcase" ) ) )
@@ -365,6 +389,11 @@
{
paragraph( getBundle( locale ).getString(
"report.scm.devaccess.general.intro" ) );
+if ( devConnection.length() < 4 )
+{
+throw new IllegalArgumentException( "The source repository
connection is too short." );
+}
+
verbatimText( devConnection.substring( 4 ) );
}
@@ -622,7 +651,7 @@
*/
public ScmRepository getScmRepository( String scmUrl )
{
-if ( scmUrl == null )
+if ( StringUtils.isEmpty( scmUrl ) )
{
return null;
}
Added:
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/test/projects/project-info-reports-plugin-test11/pom.xml
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/test/projects/project-info-reports-plugin-test11/pom.xml?rev=230612&view=auto
==
---
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/test
[jira] Updated: (MNG-699) Add EJB3 support in a plugin
[ http://jira.codehaus.org/browse/MNG-699?page=all ] Brett Porter updated MNG-699: - Priority: Minor (was: Major) Summary: Add EJB3 support in a plugin (was: Jar plugin - provide possibility to change generated jar file extension) > Add EJB3 support in a plugin > > > Key: MNG-699 > URL: http://jira.codehaus.org/browse/MNG-699 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Reporter: Piotr Bzdyl > Priority: Minor > > > Please, provide possibility to generate artifact with extension other than > 'jar' only. It is not possible to set the project (artifactId = example) > artifact type i.e. to 'par' (persistance archive) or 'ejb3' and get > example.par or example.ejb3 - jar plugin will always generate *.jar files. > There is no way to change this behaviour via plugin properties - jar > extension is hardcoded in the plugin source code. > IMHO it would be better to generate default file extension based on the > project artifact ID or let it to specify via plugin properties. -- 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-139) server definitions should be reusable
[ http://jira.codehaus.org/browse/MNG-139?page=all ] Brett Porter updated MNG-139: - Description: currently if multiple projects use the same server for deployment, we are relying on inheritence to share the definition, or it must be copied. This applies similarly to the SCM connection and the dist/site management settings. It would be a good idea to be able to declare these elements in a deployed artifact. It may still be reasonable to do this through inheritence, but there is a chance we'll hit the need for multiple inheritence (because multiple projects inherit things from different sources), so we should enumerate the use cases and verify it. eg. A B / \ / \ C D E Where A and B declare two different things that D uses both of, but which C and E desire only to inherit one of. This essentially using composition for some elements instead of inheritence. was: currently if multiple projects use the same server for deployment, we are relying on inheritence to share the definition, or it must be copied. This applies similarly to the SCM connection and the dist/site management settings. It would be a good idea to be able to declare these elements in a deployed artifact. It may still be reasonable to do this through inheritence, but there is a chance we'll hit the need for multiple inheritence (because multiple projects inherit things from different sources), so we should enumerate the use cases and verify it. eg. A B / \ / \ C D E Where A and B declare two different things that D uses both of, but which C and E desire only to inherit one of. This essentially using composition for some elements instead of inheritence. Fix Version: 2.0-beta-1 Environment: consider or close this. we're butting up against some nastiness syncing id's at the moment. > server definitions should be reusable > - > > Key: MNG-139 > URL: http://jira.codehaus.org/browse/MNG-139 > Project: Maven 2 > Type: Task > Components: design > Reporter: Brett Porter > Fix For: 2.0-beta-1 > > > currently if multiple projects use the same server for deployment, we are > relying on inheritence to share the definition, or it must be copied. This > applies similarly to the SCM connection and the dist/site management settings. > It would be a good idea to be able to declare these elements in a deployed > artifact. > It may still be reasonable to do this through inheritence, but there is a > chance we'll hit the need for multiple inheritence (because multiple projects > inherit things from different sources), so we should enumerate the use cases > and verify it. > eg. >A B > / \ / \ > C D E > Where A and B declare two different things that D uses both of, but which C > and E desire only to inherit one of. > This essentially using composition for some elements instead of inheritence. -- 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-695) Exceptions thrown building project information report "Source Repository"
[ http://jira.codehaus.org/browse/MNG-695?page=all ] Brett Porter closed MNG-695: Resolution: Fixed application fixes the problem > Exceptions thrown building project information report "Source Repository" > - > > Key: MNG-695 > URL: http://jira.codehaus.org/browse/MNG-695 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Reporter: Bob Allison > Assignee: Vincent Siveton > Fix For: 2.0-beta-1 > > > (This was working yesterday. This morning I updated my SVN tree to 227227 > and this started happening.) > I am not currently using SCM features of Maven, so I do not have a developer > connection defined. In v1.0.2, I have always had an empty tag in the > project.xml. > If the v2 POM has "", I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:209) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:267) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: java.lang.StringIndexOutOfBoundsException: String index out of > range: -4 > at java.lang.String.substring(String.java:1768) > at java.lang.String.substring(String.java:1735) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.findDelimiter(DefaultScmManager.java:218) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmRepository(DefaultScmManager.java:118) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.getScmRepository(ScmReport.java:632) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderBody(ScmReport.java:200) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.ScmReport.executeReport(ScmReport.java:135) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:290) > ... 16 more > If a comment out the stanza, I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecy
[jira] Closed: (MNG-600) Two level menu with collapse : the collapsing is not correct
[ http://jira.codehaus.org/browse/MNG-600?page=all ] Brett Porter closed MNG-600: Resolution: Fixed this was fixed in the past, changing resolution > Two level menu with collapse : the collapsing is not correct > > > Key: MNG-600 > URL: http://jira.codehaus.org/browse/MNG-600 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-alpha-3 > Environment: M2 / Maven-site-plugin > Reporter: Antoine > Assignee: Vincent Siveton > Priority: Minor > Fix For: 2.0-beta-1 > > > When using a two level items in a menu with the collapse option, it does not > work correctly. (with M2 / maven-site-plugin) > Menu example: > > > > > > > > > > > > > > > If the user is on page X2.1 or page X2.2, ALL the items X1 and X2 and X3 are > expanded. > Only item X2 should be expanded. X1 and X3 should remain collapsed. > This is not easy for navigation and not clear "where I am" when menus are big. > See a example at : > http://www.hearing-test-base.com/htbDocumentation/RG%20-%20Liste%20Persons%20Mask.html > (still under 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]
[jira] Reopened: (MNG-600) Two level menu with collapse : the collapsing is not correct
[ http://jira.codehaus.org/browse/MNG-600?page=all ] Brett Porter reopened MNG-600: -- changing resolution > Two level menu with collapse : the collapsing is not correct > > > Key: MNG-600 > URL: http://jira.codehaus.org/browse/MNG-600 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-alpha-3 > Environment: M2 / Maven-site-plugin > Reporter: Antoine > Assignee: Vincent Siveton > Priority: Minor > Fix For: 2.0-beta-1 > > > When using a two level items in a menu with the collapse option, it does not > work correctly. (with M2 / maven-site-plugin) > Menu example: > > > > > > > > > > > > > > > If the user is on page X2.1 or page X2.2, ALL the items X1 and X2 and X3 are > expanded. > Only item X2 should be expanded. X1 and X3 should remain collapsed. > This is not easy for navigation and not clear "where I am" when menus are big. > See a example at : > http://www.hearing-test-base.com/htbDocumentation/RG%20-%20Liste%20Persons%20Mask.html > (still under 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]
[jira] Reopened: (MNG-695) Exceptions thrown building project information report "Source Repository"
[ http://jira.codehaus.org/browse/MNG-695?page=all ] Brett Porter reopened MNG-695: -- changing resolution > Exceptions thrown building project information report "Source Repository" > - > > Key: MNG-695 > URL: http://jira.codehaus.org/browse/MNG-695 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Reporter: Bob Allison > Assignee: Vincent Siveton > Fix For: 2.0-beta-1 > > > (This was working yesterday. This morning I updated my SVN tree to 227227 > and this started happening.) > I am not currently using SCM features of Maven, so I do not have a developer > connection defined. In v1.0.2, I have always had an empty tag in the > project.xml. > If the v2 POM has "", I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:209) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:267) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: java.lang.StringIndexOutOfBoundsException: String index out of > range: -4 > at java.lang.String.substring(String.java:1768) > at java.lang.String.substring(String.java:1735) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.findDelimiter(DefaultScmManager.java:218) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmRepository(DefaultScmManager.java:118) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.getScmRepository(ScmReport.java:632) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderBody(ScmReport.java:200) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.ScmReport.executeReport(ScmReport.java:135) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:290) > ... 16 more > If a comment out the stanza, I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) >
[jira] Created: (MNG-707) model should parse "organisation" as well
model should parse "organisation" as well - Key: MNG-707 URL: http://jira.codehaus.org/browse/MNG-707 Project: Maven 2 Type: Improvement Components: maven-model Reporter: Brett Porter Fix For: 2.0-beta-2 noticed this in the repository converter. It would be good to accept the alternate spellings on input (not necessarily preserve it on output though). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Releasing Clover plugin v1.10
+1 On 8/6/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to release Clover plugin v1.10. Here are the changes: > > > > Upgrade to Clover 1.3.9. > > > The ant:clover-check Ant task requires > initString parameter. > > > Upgrade to Clover 1.3.8. > > > When calling clover:on a second time, an updated > maven.compile.src.set was ignored. > > > > Here's my +1 > > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2 build - FAILED - update] Thu Aug 4 22:45:00 GMT 2005
it0046 seems to have an intermitten failure - John, any ideas? - Brett [EMAIL PROTECTED] wrote: >Log: >http://maven.zones.apache.org/~maven/logs/m2-build-log-20050804.224500.txt > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-691) Ability to assign a report to choosen navigation menu
[ http://jira.codehaus.org/browse/MNG-691?page=all ] Brett Porter updated MNG-691: - Fix Version: 2.0-beta-2 this would be helpful for plugin:xdoc > Ability to assign a report to choosen navigation menu > -- > > Key: MNG-691 > URL: http://jira.codehaus.org/browse/MNG-691 > Project: Maven 2 > Type: Wish > Reporter: Michal Maczka > Fix For: 2.0-beta-2 > > > It will be nice to have a possibiliy of deciding per report basis where (in > which menu) given report will appear in the left side navigation instead of > putting all reports into one bag (reports menu). -- 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/06-Aug-2005_08.00.20/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - checkout] Sun Aug 7 00:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050807.001500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050807.001500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Sat Aug 6 22:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050806.223000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050806.223000.txt
[jira] Updated: (MNG-685) FAQ about compiling with Java 1.5 are incomplete.
[ http://jira.codehaus.org/browse/MNG-685?page=all ] Brett Porter updated MNG-685: - Fix Version: 2.0-beta-1 > FAQ about compiling with Java 1.5 are incomplete. > - > > Key: MNG-685 > URL: http://jira.codehaus.org/browse/MNG-685 > Project: Maven 2 > Type: Bug > Components: documentation > Versions: 2.0-alpha-3 > Reporter: Ken Weiner > Priority: Minor > Fix For: 2.0-beta-1 > > > The example on how to compile with Java 1.5 is incomplete. > http://maven.apache.org/maven2/general.html#Compiling-J2SE-5 > The HTML renders the following: > > ... > > > org.apache.maven.plugins > maven-compiler-plugin > > 1.5 > It should actually render: > > ... > > > org.apache.maven.plugins > maven-compiler-plugin > > 1.5 > 1.5 > > > > ... > -- 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-693) Reporting stanza is not inherited from parent
[ http://jira.codehaus.org/browse/MNG-693?page=all ] Brett Porter updated MNG-693: - Fix Version: 2.0-beta-1 > Reporting stanza is not inherited from parent > - > > Key: MNG-693 > URL: http://jira.codehaus.org/browse/MNG-693 > Project: Maven 2 > Type: Bug > Versions: 2.0-beta-1 > Reporter: Bob Allison > Priority: Minor > Fix For: 2.0-beta-1 > > > I have a multi-level project using Maven 1.0.2 that I am working on > converting to Maven 2. In the 1.0.2 environment, I have the top level > project define a number of defaults for all of the projects; this allows the > project.xml and maven.xml files for lower-level projects to be small (or in > the case of the maven.xml file, unneeded). > While working towards building up the inheritance in the new model, it > appears that the information in the stanza of the top level > project is not getting inherited by the lower-level projects. To get any > reports to be generated, I need to copy the stanza from the > parent into each lower-level project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
[ http://jira.codehaus.org/browse/MNG-705?page=comments#action_44064 ] Kristian Nordal commented on MNG-705: - Yes, I just stumbled upon it while playing around =) > Declared dependency is not included when there exist an exclusion of the > artifact in another dependency > --- > > Key: MNG-705 > URL: http://jira.codehaus.org/browse/MNG-705 > Project: Maven 2 > Type: Bug > Versions: 2.0-beta-1 > Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347 > Reporter: Kristian Nordal > Priority: Minor > Fix For: 2.0-beta-2 > > > I have declared a dependency (commons-collections), but I also have an > exclusion of commons-collections in another dependency. In this case > commons-collection is not added to the classpath. Part of my POM: > > ... > > ... > > > hibernate > hibernate > 3.0.5 > > ... > > commons-collections > commons-collections > > ... > > ... > > commons-collections > commons-collections > 3.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] Updated: (MNG-694) war:war launched from parent doesn't find module web.xml
[ http://jira.codehaus.org/browse/MNG-694?page=all ]
Brett Porter updated MNG-694:
-
Fix Version: 2.0-beta-1
simple fix - change warSourceDirectory to a java.io.File.
BTW, you should be running "package", not war:war
> war:war launched from parent doesn't find module web.xml
>
>
> Key: MNG-694
> URL: http://jira.codehaus.org/browse/MNG-694
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-alpha-3
> Reporter: Yann Le Du
> Fix For: 2.0-beta-1
>
>
> foo
> +-- pom.xml
> +-- foo-contact
> +-- pom.xml
> +-- contact
> +-- WebContent
> +-- WEB-INF
> +-- web.xml
> In foo-contact pom.xml :
>
> org.apache.maven.plugins
> maven-war-plugin
>
> contact/WebContent
>
>
> war:war launched from foo-contact is OK.
> war:war launched from foo produces :
> org.apache.maven.plugin.MojoExecutionException: Error assembling WAR
> at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:224)
> ...
> Caused by: org.codehaus.plexus.archiver.ArchiverException: Deployment
> descriptor:
> /devel/maven/src/RIC/trunk/ric-contact/target/contact/WEB-INF/web.xml does
> not exist.
> at
> org.codehaus.plexus.archiver.war.WarArchiver.setWebxml(WarArchiver.java:70)
> ...
> Adding contact/WebContent/WEB-INF/web.xml produces the same
> message.
> Adding ${basedir}/contact/WebContent/WEB-INF/web.xml solves
> the issue.
> I guess out two things here :
> * when you launch war:war from parent, webXml does not default to
> ${warSourceDirectory}/WEB-INF/web.xml
> * webXml isn't implicitly prefixed with ${basedir}/
> See also
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111623705811553&w=2 for
> a previous report of this issue.
--
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-699) Jar plugin - provide possibility to change generated jar file extension
[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_44061 ] Brett Porter commented on MNG-699: -- yes, perhaps these could be added to the ejb plugin (or create an ejb3 plugin since they may be very different) > Jar plugin - provide possibility to change generated jar file extension > --- > > Key: MNG-699 > URL: http://jira.codehaus.org/browse/MNG-699 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Reporter: Piotr Bzdyl > > > Please, provide possibility to generate artifact with extension other than > 'jar' only. It is not possible to set the project (artifactId = example) > artifact type i.e. to 'par' (persistance archive) or 'ejb3' and get > example.par or example.ejb3 - jar plugin will always generate *.jar files. > There is no way to change this behaviour via plugin properties - jar > extension is hardcoded in the plugin source code. > IMHO it would be better to generate default file extension based on the > project artifact ID or let it to specify via plugin properties. -- 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-695) Exceptions thrown building project information report "Source Repository"
[ http://jira.codehaus.org/browse/MNG-695?page=all ] Brett Porter updated MNG-695: - Fix Version: 2.0-beta-1 was this already applied? > Exceptions thrown building project information report "Source Repository" > - > > Key: MNG-695 > URL: http://jira.codehaus.org/browse/MNG-695 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Reporter: Bob Allison > Fix For: 2.0-beta-1 > > > (This was working yesterday. This morning I updated my SVN tree to 227227 > and this started happening.) > I am not currently using SCM features of Maven, so I do not have a developer > connection defined. In v1.0.2, I have always had an empty tag in the > project.xml. > If the v2 POM has "", I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:209) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:267) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: java.lang.StringIndexOutOfBoundsException: String index out of > range: -4 > at java.lang.String.substring(String.java:1768) > at java.lang.String.substring(String.java:1735) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.findDelimiter(DefaultScmManager.java:218) > at > org.apache.maven.scm.manager.plexus.DefaultScmManager.makeScmRepository(DefaultScmManager.java:118) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.getScmRepository(ScmReport.java:632) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderBody(ScmReport.java:200) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.ScmReport.executeReport(ScmReport.java:135) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:290) > ... 16 more > If a comment out the stanza, I get the following exception: > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error during site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:491) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) > a
[jira] Updated: (MNG-702) Add ability to exclude all transitive dependencies except those specified as inclusions
[ http://jira.codehaus.org/browse/MNG-702?page=all ] Brett Porter updated MNG-702: - Fix Version: 2.0-beta-1 need to consider this for beta-1 - maybe WON'T FIX, not sure yet. > Add ability to exclude all transitive dependencies except those specified as > inclusions > --- > > Key: MNG-702 > URL: http://jira.codehaus.org/browse/MNG-702 > Project: Maven 2 > Type: Improvement > Versions: 2.0-alpha-3 > Reporter: Ken Weiner > Fix For: 2.0-beta-1 > > > Currently there is an ability to specify an optional element as > a child of within a POM. This has the effect of excluding one > or more of a dependency's transitive dependencies. > It is often the case that a dependency itself has many dependencies needed > for compilation, but are not necessarily needed at runtime. > This is a request to add an optional element as a child to > within a POM so that it is possible to express the instruction > "Don't get any of the transitive dependencies except for X, Y, Z, etc." For > example: > > springframework > spring > 1.2.2 > compile > > > hibernate > hibernate > > > > Brett Porter pointed out on the maven users mailing list that this approach > could have some pitfalls, but that I should still submit the issue for > discussion. -- 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-703) Adding validation in PluginXdocGenerator class?
[ http://jira.codehaus.org/browse/MNG-703?page=all ] Brett Porter updated MNG-703: - Fix Version: 2.0-beta-2 > Adding validation in PluginXdocGenerator class? > --- > > Key: MNG-703 > URL: http://jira.codehaus.org/browse/MNG-703 > Project: Maven 2 > Type: Bug > Components: maven-plugin-tools > Versions: 2.0-beta-1 > Reporter: Vincent Siveton > Fix For: 2.0-beta-2 > > > If we call the plugin:xdoc goal on a mojo defined like the following: > /** > * Generates something for the project. > * > * @goal agoal > */ > The generated file (mymojo-mojo.xml) is not valid but the build is successful. > Thus, the site:site goal generates the following exception: > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag > name must be the same as start tag from line 7 (position: TEXT seen > ... Checkstyle definitions defined by the project @7:150) > I think that the PluginXdocGenerator class should validate the generated 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] Updated: (MNG-704) javadoc plugin doesn't honor multiple custom tags
[ http://jira.codehaus.org/browse/MNG-704?page=all ] Brett Porter updated MNG-704: - Fix Version: 2.0-rc1 > javadoc plugin doesn't honor multiple custom tags > - > > Key: MNG-704 > URL: http://jira.codehaus.org/browse/MNG-704 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-alpha-3 > Reporter: Indrajit Raychaudhuri > Assignee: Vincent Siveton > Fix For: 2.0-rc1 > > > M2 javaodc plugin doesn't honor multiple tag as it did with M1. > In M1 we could specify this in project.properties: > maven.javadoc.customtags = usage todo fixme > usage.name = .usage > usage.description = Usage: > usage.enabled = true > usage.scope = all > todo.name = .todo > todo.description = Todo: > todo.enabled = false > todo.scope = all > fixme.name = .fixme > fixme.description = Fixme: > fixme.enabled = false > fixme.scope = all > However, in M2 the putting the switch isn't honor multiple times. Only > the last one get passed to the javadoc -tag switch. -- 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-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
[ http://jira.codehaus.org/browse/MNG-705?page=all ] Brett Porter updated MNG-705: - Fix Version: 2.0-beta-2 this a rather pointless thing to do, but a bug nonetheless :) > Declared dependency is not included when there exist an exclusion of the > artifact in another dependency > --- > > Key: MNG-705 > URL: http://jira.codehaus.org/browse/MNG-705 > Project: Maven 2 > Type: Bug > Versions: 2.0-beta-1 > Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347 > Reporter: Kristian Nordal > Priority: Minor > Fix For: 2.0-beta-2 > > > I have declared a dependency (commons-collections), but I also have an > exclusion of commons-collections in another dependency. In this case > commons-collection is not added to the classpath. Part of my POM: > > ... > > ... > > > hibernate > hibernate > 3.0.5 > > ... > > commons-collections > commons-collections > > ... > > ... > > commons-collections > commons-collections > 3.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] Created: (MNG-706) plugin:xdoc should be a report
plugin:xdoc should be a report -- Key: MNG-706 URL: http://jira.codehaus.org/browse/MNG-706 Project: Maven 2 Type: Improvement Components: maven-plugins Reporter: Brett Porter Fix For: 2.0-beta-2 this has been around since before the reporting api, but now needs to be converted so that the plugin docs can be seamlessly added to the website. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Releasing Clover plugin v1.10
+1 Vincent Massol wrote: >Hi, > >I'd like to release Clover plugin v1.10. Here are the changes: > > > >Upgrade to Clover 1.3.9. > > >The ant:clover-check Ant task requires >initString parameter. > > >Upgrade to Clover 1.3.8. > > >When calling clover:on a second time, an updated >maven.compile.src.set was ignored. > > > >Here's my +1 > >Thanks >-Vincent > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-28) bogus dependencies in commons-configuration
[ http://jira.codehaus.org/browse/MEV-28?page=comments#action_44057 ] Brett Porter commented on MEV-28: - Tore, you can also use inside the dependency element to block these 3 from commons-configuration where you use it. http://maven.apache.org/maven2/maven-model/maven.html#class_Exclusion > bogus dependencies in commons-configuration > --- > > Key: MEV-28 > URL: http://jira.codehaus.org/browse/MEV-28 > Project: Maven Evangelism > Type: Task > Components: Dependencies > Reporter: Brett Porter > > > as previously sent to commons-dev: > There are a few suspect dependencies in the POM from the 1.1 release: > - - resources:resources:1.0 doesn't exist - how does Maven build with this? > - - as of commons-logging 1.0.4, I believe you should be dependening on > commons-logging-api? > - - dependency on dbunit, which is LGPL (Eric Pugh is a committer on > both - perhaps he could propose a change to ASL/BSD?) > - - badly specified mockobjects IDs (I thought the old format used + > instead of :, but regardless - you should split it to group/artifactId > - - dependency on findbugs, which is LGPL. (The plugin being used is > ASL, but findbugs is LGPL) -- 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-705) Declared dependency is not included when there exist an exclusion of the artifact in another dependency
Declared dependency is not included when there exist an exclusion of the artifact in another dependency --- Key: MNG-705 URL: http://jira.codehaus.org/browse/MNG-705 Project: Maven 2 Type: Bug Versions: 2.0-beta-1 Environment: Maven version: 2.0-beta-1-SNAPSHOT, Revision: 227347 Reporter: Kristian Nordal Priority: Minor I have declared a dependency (commons-collections), but I also have an exclusion of commons-collections in another dependency. In this case commons-collection is not added to the classpath. Part of my POM: ... ... hibernate hibernate 3.0.5 ... commons-collections commons-collections ... ... commons-collections commons-collections 3.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]
Re: [m2] POM inheritance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, John Casey wrote: > try adding true to the plugin definition at the top > level...I can't remember whether the compiler plugin inherits by default > or not (my suspicions are "not"). Not about POM inheritance but about dependency inheritance (transitive dependencies): Can I also put false to a dependency definition so it will not be inherited. E.g. if commons-logging does not want to carry out all of their supported implementations? Regards Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC9R4ImPuec2Dcv/8RAgp0AJ9IAb0yV2fqNeBwt5WgFJ0Tr734aQCfd6Dy TEC4U7jV3ldvW0Wg1TDdn24= =PKUr -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-28) bogus dependencies in commons-configuration
[ http://jira.codehaus.org/browse/MEV-28?page=comments#action_44055 ] Tore Garder Larsen commented on MEV-28: --- Hei, There are 3 dependency entries in the commons-configuration-1.1 POM that makes building my projects with commons-configuration-1.1 as my dependency impossible without manual corrections in my local repository: These are: mockobjects:mockobjects-core mockobjects:mockobjects-core 0.09 mockobjects:mockobjects-jdk1.4-j2ee1.3 mockobjects:mockobjects-jdk1.4-j2ee1.3 0.09 resources resources 1.0 The first two should be changed to: mockobjects mockobjects-core 0.09 mockobjects mockobjects-jdk1.4-j2ee1.3 0.09 The resources:resources dependency may be deleted because it is a fake dependency just to test property file reading from a jar called resources.jar Thank you. Regards from Tore Garder Larsen > bogus dependencies in commons-configuration > --- > > Key: MEV-28 > URL: http://jira.codehaus.org/browse/MEV-28 > Project: Maven Evangelism > Type: Task > Components: Dependencies > Reporter: Brett Porter > > > as previously sent to commons-dev: > There are a few suspect dependencies in the POM from the 1.1 release: > - - resources:resources:1.0 doesn't exist - how does Maven build with this? > - - as of commons-logging 1.0.4, I believe you should be dependening on > commons-logging-api? > - - dependency on dbunit, which is LGPL (Eric Pugh is a committer on > both - perhaps he could propose a change to ASL/BSD?) > - - badly specified mockobjects IDs (I thought the old format used + > instead of :, but regardless - you should split it to group/artifactId > - - dependency on findbugs, which is LGPL. (The plugin being used is > ASL, but findbugs is LGPL) -- 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]
IoC (was Re: [m2] getting involved?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thomas, Thomas Van de Velde wrote: >>BTW - I like plexus. Haven't noticed the project before. I had used >>avalon and had a look at pico+nano before. Plexus seems to be powerfull >>like avalon containers but less invasive (like the spring-framework). >>Maybe I'll use that in my project. Would you again decide for plexus if >>you'd choose now? > > > > In what way would Spring be more invasive than Plexus? None. That is what I was saying: Plexuse seems to be less invasive than avalon. And shares this ability with spring. > My issue with the > Plexus container is that it is completely unknown to most developers, that > there are no books and hardly any documentation on the site. I assume there > must be good reasons for starting yet another IoC container (Can somebody > elaborate on those reasons?) For me the reason was that the Avalon API is inacceptable for me because I am bound to it. If I would later switch to spring or anything else, I would need to rewrite a lot of my code. And the message on the avalon homepage says a clear language. So I looked at spring and it seemed that it solves that issue but on the other hand the bean-factory approach is a little too low-level for me. I have to do way too much just to get simple things done (e.g. injecting a component-specific logger) and the configuration is xml but what you are doing is not configuration but programming. So besides I looked at various other solutions but havent found anything acceptable so far. So I started my own Container. As I pointed out in my mail: I found plexus and it looks good. There is hardly no documentation and if you just start on the homepage of plexus you will never even come to the point deciding to use it. Maybe I'll drop my own container and switch to plexus - time will show. But in may case the requirements for the container are so simple that it might be easier to develop my own than understanding plexus :) Anyways I started an experiment by writing some sort of API or better specification for component "descriptoring" that could be understood by any container-framework so components could be developed completely container independent - for those who are interesed: http://m-m-m.sourceforge.net/container/javadoc/ http://m-m-m.sourceforge.net/container/container.jar I would love to hear comments from your point of view since you have a lot more requirements for the container. So would you say that just some things are missing in the suggested API or would you say that the complete approach would be inacceptable for you / for plexus / for whatever thing and reason. Take care Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC9RtvmPuec2Dcv/8RAskQAKCAO6qbi6nP4pLpMkVlRVImHF+CEACdHR7t Sh+dq7eixO5g1g1IewMDUzA= =2s+b -END PGP SIGNATURE- - 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/06-Aug-2005_04.00.32/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Mavenbook.org with more tips and more feeds
Hi Vincent, On 8/6/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > Hi there, > Also, I'm interested to get some feedback from you readers. Do you find the > information there useful? Do you like the tips that have been posted so far? > I've bought your book to introduce maven to other team in the company I am working for. Very good job, I like the 'How do I do that' way of explaining things ;-) I am interested in writing m2 tips as they come along. Cheers, Stéphane -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Splitting commit messages and dev messages
OK. Let's call for a vote on this list then. Cheers, Stéphane On 8/6/05, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: > They are not interesting to everyone. And I am not suggesting that they > be totally removed, just moved to their own list where people who are > interested in them can subscribe to them. > > While your work around would work, it is still a work around. > Splitting the traffic would be better done by putting the commit > messages back into their own mailing list. > > > Regards, > Alan > > Stephane Nicoll wrote, On 8/3/2005 12:12 AM: > > >Alan, > > > >All mail clients support the creation of rules. I am personnaly using > >gmail and have a forwarding rule to a specific folder for SVN commit. > > > >I could be the trahsh bin in your case :-) > > > >SVN commits are interesting to the dev list, I would not suggest to remove > >them. > > > >Cheers, > >Stéphane > > > >On 8/3/05, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: > > > > > >>As it stands, it appears that all SVN commit messages are automatically > >>forwarded to the developer list. Some people, like me, are not all that > >>interested in the commit messages. I propose that we turn off the > >>forwarding. > >> > >>How this should be done is to automatically subscribe everyone in the > >>dev list to the SVN list then, turn off forwarding; this way the status > >>quo is maintained. > >> > >>I recommend that future subscribers of the dev list do not get > >>automatically subscribed to the SVN list as this practice seems unorthodox. > >> > >> > >>Regards, > >>Alan > >> > >> > >> > >> > >>- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> > > > > > > > > > > > -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Splitting commit messages and dev messages
They are not interesting to everyone. And I am not suggesting that they be totally removed, just moved to their own list where people who are interested in them can subscribe to them. While your work around would work, it is still a work around. Splitting the traffic would be better done by putting the commit messages back into their own mailing list. Regards, Alan Stephane Nicoll wrote, On 8/3/2005 12:12 AM: Alan, All mail clients support the creation of rules. I am personnaly using gmail and have a forwarding rule to a specific folder for SVN commit. I could be the trahsh bin in your case :-) SVN commits are interesting to the dev list, I would not suggest to remove them. Cheers, Stéphane On 8/3/05, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: As it stands, it appears that all SVN commit messages are automatically forwarded to the developer list. Some people, like me, are not all that interested in the commit messages. I propose that we turn off the forwarding. How this should be done is to automatically subscribe everyone in the dev list to the SVN list then, turn off forwarding; this way the status quo is maintained. I recommend that future subscribers of the dev list do not get automatically subscribed to the SVN list as this practice seems unorthodox. Regards, Alan - 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/06-Aug-2005_12.00.20/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Mavenbook.org with more tips and more feeds
Sorry, this was meant for Thomas alone... :-) -Vincent > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: samedi 6 août 2005 17:32 > To: 'Maven Developers List' > Subject: RE: [ANN] Mavenbook.org with more tips and more feeds > > Hi Thomas, > > > -Original Message- > > From: Thomas Van de Velde [mailto:[EMAIL PROTECTED] > > Sent: samedi 6 août 2005 14:30 > > To: Maven Developers List > > Subject: Re: [ANN] Mavenbook.org with more tips and more feeds > > [snip] > > > Good stuff though! I can add a couple of M1 tips if you want. > > That would be very cool. Thanks for proposing. I'm currently creating a > page > that explains how to do that. I should have this ready in 1 or 2 days. > > In the meantime, could you please register on the mavenbook wiki so that I > can give you rights? > > The register URL is: > http://mavenbook.xwiki.com/xwiki/bin/view/XWiki/RegisterNewUser > > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Mavenbook.org with more tips and more feeds
Hi Thomas, > -Original Message- > From: Thomas Van de Velde [mailto:[EMAIL PROTECTED] > Sent: samedi 6 août 2005 14:30 > To: Maven Developers List > Subject: Re: [ANN] Mavenbook.org with more tips and more feeds [snip] > Good stuff though! I can add a couple of M1 tips if you want. That would be very cool. Thanks for proposing. I'm currently creating a page that explains how to do that. I should have this ready in 1 or 2 days. In the meantime, could you please register on the mavenbook wiki so that I can give you rights? The register URL is: http://mavenbook.xwiki.com/xwiki/bin/view/XWiki/RegisterNewUser Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r230549 - in /maven/components/trunk/maven-plugins/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/test/projects/javadoc-plugin-test1/ src/test/projects/javadoc-plugin-test1/src/main/java/org/apache/maven/plugin
Hi again, [SNIP] > Ok, that's right. Could you please make sure to include a more explicit > reason when doing this in the future? > > Including the reasons why you're changing a dependency, eg: adding, > removing or changing the scope/version is important as it might have a > impact on projects depending on the current project. I will try to be clearer on comments, especially on dependencies. Thanks! Cheers, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Sat Aug 6 14:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050806.144500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050806.144500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r230549 - in /maven/components/trunk/maven-plugins/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/test/projects/javadoc-plugin-test1/ src/test/projects/javadoc-plugin-test1/src/main/java/org/apache/maven/plugin
On Sat, Aug 06, 2005 at 10:42:10AM -0400, Vincent Siveton wrote: > Hi, > > [SNIP] > > > > > Why did you add plexus-utils as a dependency? > > Brett tells me to do that. > > "it is better to be explicit if you actually depend on it to avoid the side > effect of it being removed from a transitive dep and inadvertently breaking > your build." Ok, that's right. Could you please make sure to include a more explicit reason when doing this in the future? Including the reasons why you're changing a dependency, eg: adding, removing or changing the scope/version is important as it might have a impact on projects depending on the current project. -- Trygve signature.asc Description: Digital signature
RE: svn commit: r230549 - in /maven/components/trunk/maven-plugins/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/test/projects/javadoc-plugin-test1/ src/test/projects/javadoc-plugin-test1/src/main/java/org/apache/maven/plugin
Hi, [SNIP] > > Why did you add plexus-utils as a dependency? Brett tells me to do that. "it is better to be explicit if you actually depend on it to avoid the side effect of it being removed from a transitive dep and inadvertently breaking your build." Cheers, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r230549 - in /maven/components/trunk/maven-plugins/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/test/projects/javadoc-plugin-test1/ src/test/projects/javadoc-plugin-test1/src/main/java/org/apache/maven/plugin/...
On Sat, Aug 06, 2005 at 02:32:49PM -, [EMAIL PROTECTED] wrote: > Author: vsiveton > Date: Sat Aug 6 07:32:43 2005 > New Revision: 230549 > > URL: http://svn.apache.org/viewcvs?rev=230549&view=rev > Log: > Added methods to repeat arguments (for group, tag, link and linkoffline > options provided by the Javadoc standard doclet). Added plexus-utils as > transitive dep. > Why did you add plexus-utils as a dependency? [snip] -- Trygve signature.asc Description: Digital signature
[jira] Commented: (MNG-704) javadoc plugin doesn't honor multiple custom tags
[ http://jira.codehaus.org/browse/MNG-704?page=comments#action_44051 ] Vincent Siveton commented on MNG-704: - The plugin tag option is a comma separated of Javadoc tag options: http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#tag Thus, the following configuration should work: .usage:a:Usage:, .todo:a:To do something:, .fixme:a:Fixme: Do you think that it should be better to describe each tag in sub properties or to use Javadoc tag definition? > javadoc plugin doesn't honor multiple custom tags > - > > Key: MNG-704 > URL: http://jira.codehaus.org/browse/MNG-704 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-alpha-3 > Reporter: Indrajit Raychaudhuri > Assignee: Vincent Siveton > > > M2 javaodc plugin doesn't honor multiple tag as it did with M1. > In M1 we could specify this in project.properties: > maven.javadoc.customtags = usage todo fixme > usage.name = .usage > usage.description = Usage: > usage.enabled = true > usage.scope = all > todo.name = .todo > todo.description = Todo: > todo.enabled = false > todo.scope = all > fixme.name = .fixme > fixme.description = Fixme: > fixme.enabled = false > fixme.scope = all > However, in M2 the putting the switch isn't honor multiple times. Only > the last one get passed to the javadoc -tag switch. -- 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: r230549 - in /maven/components/trunk/maven-plugins/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/test/projects/javadoc-plugin-test1/ src/test/projects/javadoc-plugin-test1/src/main/java/org/apache/maven/plugin/...
Author: vsiveton
Date: Sat Aug 6 07:32:43 2005
New Revision: 230549
URL: http://svn.apache.org/viewcvs?rev=230549&view=rev
Log:
Added methods to repeat arguments (for group, tag, link and linkoffline options
provided by the Javadoc standard doclet). Added plexus-utils as transitive dep.
Modified:
maven/components/trunk/maven-plugins/maven-javadoc-plugin/pom.xml
maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/test/projects/javadoc-plugin-test1/pom.xml
maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/test/projects/javadoc-plugin-test1/src/main/java/org/apache/maven/plugin/javadoc/test1/App.java
Modified: maven/components/trunk/maven-plugins/maven-javadoc-plugin/pom.xml
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-javadoc-plugin/pom.xml?rev=230549&r1=230548&r2=230549&view=diff
==
--- maven/components/trunk/maven-plugins/maven-javadoc-plugin/pom.xml (original)
+++ maven/components/trunk/maven-plugins/maven-javadoc-plugin/pom.xml Sat Aug
6 07:32:43 2005
@@ -40,6 +40,10 @@
commons-lang
2.1
+
+ plexus
+ plexus-utils
+
Modified:
maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java?rev=230549&r1=230548&r2=230549&view=diff
==
---
maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
(original)
+++
maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
Sat Aug 6 07:32:43 2005
@@ -26,7 +26,6 @@
import java.util.StringTokenizer;
import org.apache.commons.lang.ClassUtils;
-import org.apache.commons.lang.StringUtils;
import org.apache.commons.lang.SystemUtils;
import org.apache.commons.lang.math.NumberUtils;
import org.apache.maven.project.MavenProject;
@@ -37,6 +36,7 @@
import org.codehaus.doxia.site.renderer.SiteRenderer;
import org.codehaus.plexus.util.FileUtils;
import org.codehaus.plexus.util.IOUtil;
+import org.codehaus.plexus.util.StringUtils;
import org.codehaus.plexus.util.cli.CommandLineUtils;
import org.codehaus.plexus.util.cli.Commandline;
import org.codehaus.plexus.util.cli.DefaultConsumer;
@@ -60,24 +60,29 @@
extends AbstractMavenReport
{
/** The current class directory */
-private static final String RESOURCE_DIR =
ClassUtils.getPackageName(JavadocReport.class).replace('.', '/');
+private static final String RESOURCE_DIR = ClassUtils.getPackageName(
JavadocReport.class ).replace( '.', '/' );
/** Default location for css */
private static final String DEFAULT_CSS_NAME = "stylesheet.css";
+
private static final String RESOURCE_CSS_DIR = RESOURCE_DIR + "/css";
-
+
// Using for the plugin:xdoc goal. Best way?
/** Default bottom */
private static final String DEFAULT_BOTTOM = "Copyright
${project.inceptionYear-currentYear} ${project.organization.name}. All Rights
Reserved.";
+
/** Default bottom */
private static final String DEFAULT_DESTDIR =
"${project.build.directory}/site/apidocs";
+
/** Default doctitle */
private static final String DEFAULT_DOCTITLE = "${windowtitle}";
+
/** Default organization name */
private static final String DEFAULT_ORGANIZATION_NAME = "The Apache
Software Foundation";
+
/** Default window title */
private static final String DEFAULT_WINDOW_TITLE = "${project.name}
${project.version} API";
-
+
/**
* @parameter expression="${project.build.directory}/site"
* @required
@@ -112,7 +117,7 @@
* See http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#breakiterator";>breakiterator.
*
* @parameter expression="${breakiterator}"
- *default-value="false"
+ * default-value="false"
*/
private boolean breakiterator = false;
@@ -185,7 +190,7 @@
* See http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#1.1";>1.1.
*
* @parameter expression="${old}"
- *default-value="false"
+ * default-value="false"
*/
private boolean old = false;
@@ -202,7 +207,7 @@
* See http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#package";>package.
*
* @parameter expression="${package}"
- *default-value="true"
+ * default-value="true"
*/
private boolean package_ = true;
@@ -211,7 +216,7 @@
* See http://java.sun.com/j2se/
[maven2 build - SUCCESS - update] Sat Aug 6 13:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050806.131500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050806.131500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 6 13:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050806.13.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 6 12:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050806.124500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Releasing Clover plugin v1.10
> -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: samedi 6 août 2005 11:14 > To: 'Maven Developers List' > Subject: RE: [VOTE] Releasing Clover plugin v1.10 > > +1 if you remove from the changes file : > > > > > Upgrade to Clover 1.3.8. > > > > :-) Fixed. [snip] Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r230548 - /maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
Author: vmassol Date: Sat Aug 6 05:44:40 2005 New Revision: 230548 URL: http://svn.apache.org/viewcvs?rev=230548&view=rev Log: Do not include intermediate issues that are superseded by other ones. Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/changes.xml?rev=230548&r1=230547&r2=230548&view=diff == --- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Sat Aug 6 05:44:40 2005 @@ -26,14 +26,11 @@ - + Upgrade to Clover 1.3.9. - + The ant:clover-check Ant task requires initString parameter. - - -Upgrade to Clover 1.3.8. When calling clover:on a second time, an updated - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Mavenbook.org with more tips and more feeds
> -Original Message- > From: Thomas Van de Velde [mailto:[EMAIL PROTECTED] > Sent: samedi 6 août 2005 14:30 > To: Maven Developers List > Subject: Re: [ANN] Mavenbook.org with more tips and more feeds > > Hi Vincent, > > There's a problem with the "Dynamic Propery" tip: > > Error number 4001 in 4: Error while parsing velocity page > Main.Tip8DynamicProperty Wrapped Exception: Encountered " == > 'whatever'}">rn" at line 5, column 51. Was expecting one of: "}" Oops... sorry, I had forgotten to espace some characters. I've fixed it. Thanks. > Good stuff though! I can add a couple of M1 tips if you want. Cool. I'm sending you the details in a separate email. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r230547 - /maven/components/trunk/maven-plugins/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/AbstractCompilerMojo.java
Author: trygvis
Date: Sat Aug 6 05:36:48 2005
New Revision: 230547
URL: http://svn.apache.org/viewcvs?rev=230547&view=rev
Log:
o Adding parameters:
- Show deprecation
- Show warnings
o Using the setters on the configuration object instead of passing them in
their raw format (eg -target 1.1).
Modified:
maven/components/trunk/maven-plugins/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/AbstractCompilerMojo.java
Modified:
maven/components/trunk/maven-plugins/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/AbstractCompilerMojo.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/AbstractCompilerMojo.java?rev=230547&r1=230546&r2=230547&view=diff
==
---
maven/components/trunk/maven-plugins/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/AbstractCompilerMojo.java
(original)
+++
maven/components/trunk/maven-plugins/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/AbstractCompilerMojo.java
Sat Aug 6 05:36:48 2005
@@ -45,6 +45,20 @@
private boolean debug;
/**
+ * Output source locations where deprecated APIs are used
+ *
+ * @parameter
+ */
+private boolean showDeprecation;
+
+/**
+ * Output warnings
+ *
+ * @parameter
+ */
+private boolean showWarnings;
+
+/**
* The -source argument for the Java compiler
*
* @parameter
@@ -130,22 +144,17 @@
compilerConfiguration.setSourceFiles( staleSources );
}
-if ( source != null )
-{
-compilerConfiguration.addCompilerOption( "-source", source );
-}
+compilerConfiguration.setDebug( debug );
-if ( target != null )
-{
-compilerConfiguration.addCompilerOption( "-target", target );
-}
+compilerConfiguration.setShowDeprecation( showDeprecation );
-if ( encoding != null )
-{
-compilerConfiguration.addCompilerOption( "-encoding" , encoding );
-}
+compilerConfiguration.setShowWarnings( showWarnings );
-compilerConfiguration.setDebug( debug );
+compilerConfiguration.setSourceVersion( source );
+
+compilerConfiguration.setTargetVersion( target );
+
+compilerConfiguration.setSourceEncoding( encoding );
//
--
// Dump configuration
@@ -189,7 +198,7 @@
throw new MojoExecutionException( "No such compiler '" +
e.getCompilerId() + "'." );
}
-getLog().info( "Using compiler '" + compilerId + "'." );
+getLog().debug( "Using compiler '" + compilerId + "'." );
try
{
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Mavenbook.org with more tips and more feeds
Hi Vincent, There's a problem with the "Dynamic Propery" tip: Error number 4001 in 4: Error while parsing velocity page Main.Tip8DynamicProperty Wrapped Exception: Encountered " == 'whatever'}">rn" at line 5, column 51. Was expecting one of: "}" … … Good stuff though! I can add a couple of M1 tips if you want. Cheers, Thomas On 8/6/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > Hi there, > > Just an update. I've modifed the http://www.mavenbook.org web site to > include more tips. I've now started to add M2 tips as well. We currently > have the following categories: > > - m1 tips > - m2 tips > - Maven news > > I've also added 3 more RSS feeds. We now have 4 feeds: > - news feed > - m1 tips feed > - m2 tips feed > - All previous feeds in one feed > > I need your help to get even more tips posted on the site. If you're > interested, send me an email and I'll give you access the underlying wiki > so > that you post tips yourself. > > Also, I'm interested to get some feedback from you readers. Do you find > the > information there useful? Do you like the tips that have been posted so > far? > > Thanks > -Vincent > > > - > 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/06-Aug-2005_08.00.19/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Mavenbook.org with more tips and more feeds
Hi there, Just an update. I've modifed the http://www.mavenbook.org web site to include more tips. I've now started to add M2 tips as well. We currently have the following categories: - m1 tips - m2 tips - Maven news I've also added 3 more RSS feeds. We now have 4 feeds: - news feed - m1 tips feed - m2 tips feed - All previous feeds in one feed I need your help to get even more tips posted on the site. If you're interested, send me an email and I'll give you access the underlying wiki so that you post tips yourself. Also, I'm interested to get some feedback from you readers. Do you find the information there useful? Do you like the tips that have been posted so far? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Releasing Clover plugin v1.10
+1 if you remove from the changes file : > > Upgrade to Clover 1.3.8. > :-) Arnaud > -Message d'origine- > De : Vincent Massol [mailto:[EMAIL PROTECTED] > Envoyé : samedi 6 août 2005 11:11 > À : 'Maven Developers List' > Objet : [VOTE] Releasing Clover plugin v1.10 > > Hi, > > I'd like to release Clover plugin v1.10. Here are the changes: > > > > Upgrade to Clover 1.3.9. > > > The ant:clover-check Ant task requires > initString parameter. > > > Upgrade to Clover 1.3.8. > >due-to="Eric Lapierre"> > When calling clover:on a second time, an updated > maven.compile.src.set was ignored. > > > > Here's my +1 > > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Releasing Clover plugin v1.10
Hi, I'd like to release Clover plugin v1.10. Here are the changes: Upgrade to Clover 1.3.9. The ant:clover-check Ant task requires initString parameter. Upgrade to Clover 1.3.8. When calling clover:on a second time, an updated maven.compile.src.set was ignored. Here's my +1 Thanks -Vincent - 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/06-Aug-2005_04.00.58/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-704) javadoc plugin doesn't honor multiple custom tags
javadoc plugin doesn't honor multiple custom tags - Key: MNG-704 URL: http://jira.codehaus.org/browse/MNG-704 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-alpha-3 Reporter: Indrajit Raychaudhuri M2 javaodc plugin doesn't honor multiple tag as it did with M1. In M1 we could specify this in project.properties: maven.javadoc.customtags = usage todo fixme usage.name = .usage usage.description = Usage: usage.enabled = true usage.scope = all todo.name = .todo todo.description = Todo: todo.enabled = false todo.scope = all fixme.name = .fixme fixme.description = Fixme: fixme.enabled = false fixme.scope = all However, in M2 the putting the switch isn't honor multiple times. Only the last one get passed to the javadoc -tag switch. -- 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]
