My resignation
Hereby I want to announce my resignation from Maven PMC and the retirement from the function of Maven Committer (this is including every project developed under maven umbrella). I just feel that I am no longer able to be a valuable part of the Maven team. There are two things which I recently started and which are not yet finished: - upload/download cancellation in wagon (I need it badly for one of my projects) - improved site navigation in m1 First thing was not committed to cvs and therefore there should not be any problem if I will implement it else where outiside the apache. For the second thing: I leave you the choice how you (it's probably up to Brett) want to handle it and if you want to continue in that direction. If you want me to revert this change in SVN just let me know. Thank you guys for all those things I learnt from you during all those years! Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1570) p6spy update on Ibiblio
The following comment has been added to this issue: Author: Emmanuel Bourg Created: Thu, 24 Feb 2005 6:56 AM Body: Closing the request because it's incomplete is a bit rude... - View this comment: http://jira.codehaus.org/browse/MAVEN-1570?page=comments#action_30258 - View the issue: http://jira.codehaus.org/browse/MAVEN-1570 Here is an overview of the issue: - Key: MAVEN-1570 Summary: p6spy update on Ibiblio Type: Task Status: Closed Priority: Major Resolution: INCOMPLETE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Assignee: Carlos Sanchez Reporter: Emmanuel Bourg Created: Tue, 22 Feb 2005 12:16 PM Updated: Thu, 24 Feb 2005 6:56 AM Description: This is a request to add the latest release (1.3) of p6spy on Ibiblio. The jar is available here: http://ovh.dl.sourceforge.net/sourceforge/p6spy/p6spy-install.zip Thank you - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVEN-1570) p6spy update on Ibiblio
Message: The following issue has been reopened. - View the issue: http://jira.codehaus.org/browse/MAVEN-1570 Here is an overview of the issue: - Key: MAVEN-1570 Summary: p6spy update on Ibiblio Type: Task Status: Reopened Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Assignee: Carlos Sanchez Reporter: Emmanuel Bourg Created: Tue, 22 Feb 2005 12:16 PM Updated: Thu, 24 Feb 2005 7:06 AM Description: This is a request to add the latest release (1.3) of p6spy on Ibiblio. The jar is available here: http://ovh.dl.sourceforge.net/sourceforge/p6spy/p6spy-install.zip Thank you - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1570) p6spy update on Ibiblio
The following issue has been updated: Updater: Emmanuel Bourg (mailto:[EMAIL PROTECTED]) Date: Thu, 24 Feb 2005 7:13 AM Comment: I attached the bundle to be deployed, sorry there is no POM. Changes: Attachment changed to p6spy-1.3-bundle.jar - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1570?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1570 Here is an overview of the issue: - Key: MAVEN-1570 Summary: p6spy update on Ibiblio Type: Task Status: Reopened Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Assignee: Carlos Sanchez Reporter: Emmanuel Bourg Created: Tue, 22 Feb 2005 12:16 PM Updated: Thu, 24 Feb 2005 7:13 AM Description: This is a request to add the latest release (1.3) of p6spy on Ibiblio. The jar is available here: http://ovh.dl.sourceforge.net/sourceforge/p6spy/p6spy-install.zip Thank you - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCLOVER-31) Add PDF report support
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPCLOVER-31 Here is an overview of the issue: - Key: MPCLOVER-31 Summary: Add PDF report support Type: New Feature Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-clover-plugin Versions: 1.7 Assignee: Reporter: Vincent Massol Created: Thu, 24 Feb 2005 7:18 AM Updated: Thu, 24 Feb 2005 7:18 AM Description: - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-307) p6spy update on Ibiblio
The following comment has been added to this issue: Author: Carlos Sanchez Created: Thu, 24 Feb 2005 7:28 AM Body: I have closed the request because it was incomplete and at the wrong place. You can reopen it if you want, and that was what you've done. Anyway you need to provide a pom, as stated in the instructions you can made a simple one. - View this comment: http://jira.codehaus.org/browse/MAVENUPLOAD-307?page=comments#action_30261 - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-307 Here is an overview of the issue: - Key: MAVENUPLOAD-307 Summary: p6spy update on Ibiblio Type: Task Status: Reopened Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Carlos Sanchez Reporter: Emmanuel Bourg Created: Tue, 22 Feb 2005 12:16 PM Updated: Thu, 24 Feb 2005 7:28 AM Description: This is a request to add the latest release (1.3) of p6spy on Ibiblio. The jar is available here: http://ovh.dl.sourceforge.net/sourceforge/p6spy/p6spy-install.zip Thank you - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r155182 - in maven/maven-1/plugins/trunk/clover: ./ src/plugin-test/testGenerateHistoryReport/ src/plugin-test/testGenerateHistoryReport/src/ src/plugin-test/testGenerateHistoryReport/src/main/ src/plugin-test/testGenerateHistoryReport/src/main/org/ src/plugin-test/testGenerateHistoryReport/src/main/org/apache/ src/plugin-test/testGenerateHistoryReport/src/main/org/apache/maven/ src/plugin-test/testGenerateHistoryReport/src/main/org/apache/maven/clover/ src/plugin-test/testGenerateHistoryReport/src/main/org/apache/maven/clover/test/ src/plugin-test/testGenerateHistoryReport/src/test/ src/plugin-test/testGenerateHistoryReport/src/test/org/ src/plugin-test/testGenerateHistoryReport/src/test/org/apache/ src/plugin-test/testGenerateHistoryReport/src/test/org/apache/maven/ src/plugin-test/testGenerateHistoryReport/src/test/org/apache/maven/clover/ src/plugin-test/testGenerateHistoryReport/src/test/org/apache/maven/clover/test/ xdocs/
Author: vmassol
Date: Thu Feb 24 04:39:06 2005
New Revision: 155182
URL: http://svn.apache.org/viewcvs?view=revrev=155182
Log:
Added support for historical reports by adding a new
codeclover:save-history/code goal that saves a Clover history point. The
history points are then used by codeclover:report/code to generate history
reports (including a link on the Maven-generated website).
Added:
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/maven.xml
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/project.properties
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/project.xml
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/main/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/main/org/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/main/org/apache/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/main/org/apache/maven/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/main/org/apache/maven/clover/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/main/org/apache/maven/clover/test/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/main/org/apache/maven/clover/test/Simple.java
(with props)
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/test/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/test/org/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/test/org/apache/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/test/org/apache/maven/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/test/org/apache/maven/clover/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/test/org/apache/maven/clover/test/
maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/src/test/org/apache/maven/clover/test/SimpleTest.java
(with props)
Modified:
maven/maven-1/plugins/trunk/clover/plugin.jelly
maven/maven-1/plugins/trunk/clover/plugin.properties
maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
maven/maven-1/plugins/trunk/clover/xdocs/goals.xml
maven/maven-1/plugins/trunk/clover/xdocs/properties.xml
Modified: maven/maven-1/plugins/trunk/clover/plugin.jelly
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/plugin.jelly?view=diffr1=155181r2=155182
==
--- maven/maven-1/plugins/trunk/clover/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/clover/plugin.jelly Thu Feb 24 04:39:06 2005
@@ -64,13 +64,10 @@
/j:otherwise
/j:choose
-j:set var=cloverReportDirectory value=${maven.docs.dest}/clover/
-
!-- Allow users to override the version of the Clover jar to use --
maven:addPath id=maven.dependency.classpath refid=clover.classpath/
ant:mkdir dir=${maven.clover.build.classes}/
-ant:mkdir dir=${cloverReportDirectory}/
ant:mkdir dir=${maven.clover.database.dir}/
!-- Add the Clover license to the classpath. --
@@ -81,6 +78,8 @@
/j:invokeStatic
/j:if
+u:file var=historyDirAsFile name=${maven.clover.history.dir}/
+
/goal
!--
@@ -317,7 +316,12 @@
--
goal name=clover:html-report-internal
+
+j:set var=cloverReportDirectory value=${maven.docs.dest}/clover/
+ant:mkdir dir=${cloverReportDirectory}/
+
ant:clover-report
+
ant:current
outfile=${cloverReportDirectory}
title=${pom.name} - ${pom.currentVersion}
@@ -331,7 +335,23 @@
/ant:format
/ant:current
+
+ !-- Only generate history report if there is at least one history point
--
+ j:if test=${historyDirAsFile.exists() and
!empty(historyDirAsFile.listFiles())}
+
+j:set var=cloverHistoryReportDirectory
value=${maven.docs.dest}/clover/history/
+ant:mkdir dir=${cloverHistoryReportDirectory}/
+
+ant:historical outfile=${cloverHistoryReportDirectory}
+ historyDir=${maven.clover.history.dir}
+ title=${pom.name} - ${pom.currentVersion} - History
+ ant:format type=html/
+/ant:historical
+
+ /j:if
+
/ant:clover-report
+
/goal
goal
name=clover:html-report
@@ -357,6 +377,7 @@
--
goal
svn commit: r155183 - maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport
Author: vmassol Date: Thu Feb 24 04:39:38 2005 New Revision: 155183 URL: http://svn.apache.org/viewcvs?view=revrev=155183 Log: more ignore files Modified: maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/ (props changed) Propchange: maven/maven-1/plugins/trunk/clover/src/plugin-test/testGenerateHistoryReport/ -- --- svn:ignore (added) +++ svn:ignore Thu Feb 24 04:39:38 2005 @@ -0,0 +1,2 @@ +velocity.log +target - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPCLOVER-6) historical report for clover
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Thu, 24 Feb 2005 7:42 AM
Done. I still need to add support for saving the historical data in the Maven
repositories but that'll be for later.
-
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-6
Here is an overview of the issue:
-
Key: MPCLOVER-6
Summary: historical report for clover
Type: Improvement
Status: Closed
Priority: Minor
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-clover-plugin
Fix Fors:
1.8
Versions:
1.6
Assignee: Vincent Massol
Reporter: Simon Matic Langford
Created: Tue, 22 Jul 2003 3:34 AM
Updated: Thu, 24 Feb 2005 7:42 AM
Environment: clover required
Description:
Does a historical clover report if there are results spanning more than one day.
Changes to plugin.jelly:
37a38,42
doc:registerReport
name=Clover Historical
pluginName=maven-clover-plugin
link=clover-history/historical
description=Clover test coverage historical report./
48a54
attainGoal name=clover:historic-report/
82a89,92
j:set
var=cloverHistoryReportDirectory
value=${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.docs.dest')}/clover-history/
89a100
ant:mkdir dir=${cloverHistoryReportDirectory}/
126c137
current
---
ant:current
130c141
/current
---
/ant:current
150a162,192
goal
name=clover:historic-report
description=Generate HTML test coverage reports with Clover
attainGoal name=clover:test/
ant:clover-historypoint historyDir=${maven.clover.historic.dir}/
attainGoal name=java:compile/
ant:taskdef name=check-clover-history
classname=org.apache.maven.clover.CheckCloverHistoryTask
classpath=${maven.build.dest}
/
ant:check-clover-history
historyDir=${maven.clover.historic.dir}
property=cloverHistoryOk
value=true
/
j:if test=${cloverHistoryOk == 'true'}
ant:clover-report
ant:historical
title=${pom.name} - ${pom.currentVersion}
outfile=${cloverHistoryReportDirectory}
historyDir=${maven.clover.historic.dir}
ant:overview /
ant:coverage /
ant:metrics /
ant:movers range=10 interval=1w /
ant:format type=html orderBy=ElementsCoveredAsc/
/ant:historical
/ant:clover-report
/j:if
/goal
New Ant task org/apache/maven/clover/CheckCloverHistoryTask.java:
===
package org.apache.maven.clover;
import java.io.IOException;
import java.io.File;
import java.util.Vector;
import org.apache.tools.ant.Task;
import org.apache.tools.ant.BuildException;
/**
* @author a href=mailto:[EMAIL PROTECTED]Simon Matic Langford/a
* @version 1.0
*/
public class CheckCloverHistoryTask extends Task
{
/**
* Location of the clover history files.
*/
private String historyDir = null;
/**
* Property to set if 2 or more days of data found.
*/
private String property = null;
/**
* Value of property to set if 2 or more days of data found.
*/
private String value = null;
/**
* @see #historyDir
*/
public String getHistoryDir()
{
return historyDir;
}
/**
* @see #historyDir
*/
public void setHistoryDir(String historyDir)
{
this.historyDir = historyDir;
}
/**
* @see #property
*/
public String getProperty()
{
return property;
}
/**
* @see #property
*/
public void setProperty(String property)
{
this.property = property;
}
/**
* @see #value
*/
public String getValue()
{
return value;
}
/**
* @see #value
*/
public void setValue(String value)
{
this.value = value;
}
/**
* Sets the property if at least 2 seperate days of clover
* history data found.
*/
public void execute() throws BuildException
{
File dir = new File(historyDir);
String[] filenames = dir.list();
Vector v = new Vector();
for (int i=0; ifilenames.length; i++)
{
String date = getDateBit(filenames[i]);
if (v.contains(date))
{
getProject().setProperty(property,value);
log(Found 2 different days.);
return;
}
else
{
v.addElement(date);
}
}
log(Found only 1 day.);
}
/**
* Gets the date part of a clover history file, in the form
codeclover-20030721151309.xml/code.
*/
private String getDateBit(String filename)
{
// clover-20030721151309.xml
int i = filename.indexOf(-)+1;
return filename.substring(i,i+8);
}
}
Changes to
[jira] Commented: (MPECLIPSE-62) maven.eclipse.conclasspath is ignored when junit test src is not present
The following comment has been added to this issue:
Author: Jason Taft
Created: Thu, 24 Feb 2005 9:10 AM
Body:
Though the workaround does work, I am not understanding the reasoning behind it.
Maybe my situation will help explain my lack of understanding?
I am working on improving the eclipse plugin to allow me to create the
appropriate .project and .classpath artifacts for use with Websphere Studio
Application Developer (WSAD) 5. Although I can use the currently (I'm using
v1.9 of this plugin) generated artifacts to successfully import a project into
WSAD's java perspective, these artifacts need some additional information in
order to be recognized by the J2EE perspective (the application assembly
toolkit is now the j2ee perspective) shipped with WSAD.
One of the additions I need to make is to add a conclasspath entry for the
websphere j2ee.ejb container.
My ejb project doesn't contain any unit tests (and it isn't necessary to get
into the merits of this decision).
I look forward to the enlightenment, be gentle :), but I currently fail to see
why creating an empty unit test src directory should be necessary as my
long-term solution.
Thanks,
Jason Taft
-
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-62?page=comments#action_30264
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-62
Here is an overview of the issue:
-
Key: MPECLIPSE-62
Summary: maven.eclipse.conclasspath is ignored when junit test src is not
present
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee: David Eric Pugh
Reporter: Dan Tran
Created: Wed, 29 Dec 2004 2:46 AM
Updated: Thu, 24 Feb 2005 9:10 AM
Environment: XP, jdk 1.4.2
Description:
Tracing thru the jelly code and tested it myself, maven-eclipse-plugin
completely ignore the processing of maven.eclipse.conclasspath when the
${unitTestSourcesPresent} is not true.
the code is in src/plugin-resources/templates/classpath.jelly
is it a bug?
-
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-308) Upload request for EasyConf
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-308 Here is an overview of the issue: - Key: MAVENUPLOAD-308 Summary: Upload request for EasyConf Type: Task Status: Unassigned Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Reporter: Jorge Ferrer Created: Thu, 24 Feb 2005 9:29 AM Updated: Thu, 24 Feb 2005 9:29 AM Description: http://easyconf.sourceforge.net http://easyconf.sourceforge.net/team-list.html EasyConf is a library to access configuration of software components and applications. It defines simple conventions to make it easier to use. It was born in a portlets-based portal and has several features useful for this and similar environments. It has been recently released with the Apache License Version 2 and this is the first public release. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPSCM-45) var delim not allways : (on CVSNT |)
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPSCM-45 Here is an overview of the issue: - Key: MPSCM-45 Summary: var delim not allways : (on CVSNT |) Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-scm-plugin Versions: 1.4.1 Assignee: Reporter: uri Created: Thu, 24 Feb 2005 11:04 AM Updated: Thu, 24 Feb 2005 11:04 AM Environment: On CVS kept on WINNT. Description: the char used to delimit words on scm connection is not allways :. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPSCM-46) can't access svn on nonstandard ports because of : issues
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPSCM-46 Here is an overview of the issue: - Key: MPSCM-46 Summary: can't access svn on nonstandard ports because of : issues Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-scm-plugin Versions: 1.5 Assignee: Reporter: Florian Nierhaus Created: Thu, 24 Feb 2005 1:04 PM Updated: Thu, 24 Feb 2005 1:04 PM Environment: windows I use scm plugin 1.5 beta 3 Description: Hi, the connection I configured is My connection is scm:svn:http://hostname:8080/f scm:parse-connecton gives: Using SCM method: svn Using SVN repisotory: http://hostname Using module: 8080/f this results in some uglyness in the cruisecontrol configuration such as localWorkingCopy=C:/mysources/8080/f best regards, Florian - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPECLIPSE-76) AspectJ nature and source not set when generating eclipse project
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-76 Here is an overview of the issue: - Key: MPECLIPSE-76 Summary: AspectJ nature and source not set when generating eclipse project Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Assignee: Reporter: Bert van Brakel Created: Thu, 24 Feb 2005 1:04 PM Updated: Thu, 24 Feb 2005 1:04 PM Description: When generating eclipse .classpath and .project files when aspects are part of the maven build, the aspect nature and source directory aren't included. I have a patch which seems to work on my box, I'll see if I can attach it - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPECLIPSE-76) AspectJ nature and source not set when generating eclipse project
The following issue has been updated: Updater: Bert van Brakel (mailto:[EMAIL PROTECTED]) Date: Thu, 24 Feb 2005 1:16 PM Comment: Patch to update classpath.jelly and project.jelly. Not sure if anyone wants an optional property like maven.eclipse.aspectj.ignore=true|false so aspects are not included in the generated project files, but that's easy enough to add in Changes: Attachment changed to eclipse-plugin-patch.txt - For a full history of the issue, see: http://jira.codehaus.org/browse/MPECLIPSE-76?page=history - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-76 Here is an overview of the issue: - Key: MPECLIPSE-76 Summary: AspectJ nature and source not set when generating eclipse project Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Assignee: Reporter: Bert van Brakel Created: Thu, 24 Feb 2005 1:04 PM Updated: Thu, 24 Feb 2005 1:16 PM Description: When generating eclipse .classpath and .project files when aspects are part of the maven build, the aspect nature and source directory aren't included. I have a patch which seems to work on my box, I'll see if I can attach it - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1571) Add organizationUrl to developer information
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1571 Here is an overview of the issue: - Key: MAVEN-1571 Summary: Add organizationUrl to developer information Type: New Feature Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: model additions Assignee: Reporter: Maarten Coene Created: Thu, 24 Feb 2005 4:23 PM Updated: Thu, 24 Feb 2005 4:23 PM Description: Hi, I would like to add a hyperlink to the organizations of the developers. However, this doesn't seem possible with the current version of the project descriptor. Is it possible to add an organizationUrl element to the developer element? thanks, Maarten - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSCM-46) can't access svn on nonstandard ports because of : issues
Message: The following issue has been closed. Resolver: Brett Porter Date: Thu, 24 Feb 2005 4:45 PM try: scm|svn|http://...:8080/repos/... - View the issue: http://jira.codehaus.org/browse/MPSCM-46 Here is an overview of the issue: - Key: MPSCM-46 Summary: can't access svn on nonstandard ports because of : issues Type: Bug Status: Closed Priority: Major Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-scm-plugin Versions: 1.5 Assignee: Reporter: Florian Nierhaus Created: Thu, 24 Feb 2005 1:04 PM Updated: Thu, 24 Feb 2005 4:45 PM Environment: windows I use scm plugin 1.5 beta 3 Description: Hi, the connection I configured is My connection is scm:svn:http://hostname:8080/f scm:parse-connecton gives: Using SCM method: svn Using SVN repisotory: http://hostname Using module: 8080/f this results in some uglyness in the cruisecontrol configuration such as localWorkingCopy=C:/mysources/8080/f best regards, Florian - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSCM-45) var delim not allways : (on CVSNT |)
Message: The following issue has been closed. Resolver: Brett Porter Date: Thu, 24 Feb 2005 4:47 PM this should work if you try 1.5-beta-3. maven plugin:download -DartifactId=maven-scm-plugin -DgroupId=maven -Dversion=1.5-beta-3 - View the issue: http://jira.codehaus.org/browse/MPSCM-45 Here is an overview of the issue: - Key: MPSCM-45 Summary: var delim not allways : (on CVSNT |) Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-scm-plugin Fix Fors: 1.5 Versions: 1.4.1 Assignee: Reporter: uri Created: Thu, 24 Feb 2005 11:04 AM Updated: Thu, 24 Feb 2005 4:47 PM Environment: On CVS kept on WINNT. Description: the char used to delimit words on scm connection is not allways :. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1572) Recursive loop in target
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1572 Here is an overview of the issue: - Key: MAVEN-1572 Summary: Recursive loop in target Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Assignee: Reporter: Jim Kerwood Created: Thu, 24 Feb 2005 5:09 PM Updated: Thu, 24 Feb 2005 5:09 PM Description: resources resource/ /resources Caused a recursive build in our target directory. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-309) Fastutil 4.4.0
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-309 Here is an overview of the issue: - Key: MAVENUPLOAD-309 Summary: Fastutil 4.4.0 Type: Task Status: Unassigned Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Reporter: Oscar Picasso Created: Thu, 24 Feb 2005 5:16 PM Updated: Thu, 24 Feb 2005 5:16 PM Description: http://fastutil.dsi.unimi.it/ - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1572) Recursive loop in target
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Thu, 24 Feb 2005 5:16 PM Comment: verified. Maven 1.1 should parse this correctly, however it currently gives this: java.lang.NullPointerException at java.io.File.init(File.java:180) at org.apache.maven.MavenUtils.makeAbsolutePath(MavenUtils.java:826) at org.apache.maven.project.Project.resolveDirectory(Project.java:981) at org.apache.maven.project.Project.resolveDirectories(Project.java:867) at org.apache.maven.project.Project.initialize(Project.java:547) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:125) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:99) need to improve the model validation. Changes: Fix Version changed to 1.1-beta-1 - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1572?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1572 Here is an overview of the issue: - Key: MAVEN-1572 Summary: Recursive loop in target Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.1-beta-1 Assignee: Reporter: Jim Kerwood Created: Thu, 24 Feb 2005 5:09 PM Updated: Thu, 24 Feb 2005 5:16 PM Description: resources resource/ /resources Caused a recursive build in our target directory. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPLINKCHECK-21) java.lang.NumberFormatException if proxy port is setted to
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPLINKCHECK-21 Here is an overview of the issue: - Key: MPLINKCHECK-21 Summary: java.lang.NumberFormatException if proxy port is setted to Type: Bug Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-linkcheck-plugin Fix Fors: 1.4 Versions: 1.3.4 Assignee: Reporter: Arnaud HERITIER Created: Thu, 24 Feb 2005 6:02 PM Updated: Thu, 24 Feb 2005 6:02 PM Environment: Maven 1.0.2 Description: If maven.proxy.port is an empty string we have this error : BUILD FAILED File.. D:\Work\Data\maven\cache\maven-linkcheck-plugin-1.3.4\plugin.jelly Element... linkcheck:linkcheck Line.. 91 Column 9 For input string: com.werken.werkz.UnattainableGoalException: Unable to obtain goal [site] -- D:\Work\Data\maven\cache\maven-linkcheck-plugin-1.3.4\plugin.jelly:91:9: linkcheck: linkcheck For input string: at com.werken.werkz.Goal.fire(Goal.java:646) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:488) at org.apache.maven.cli.App.main(App.java:1239) 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:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.apache.commons.jelly.JellyTagException: D:\Work\Data\maven\cache\maven-linkcheck-plugin-1.3.4\plugin.jelly:91:9: linkcheck:linkcheck For input string: at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:243) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:145) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at com.werken.werkz.jelly.PostGoalTag$1.firePostGoal(PostGoalTag.java:87) at com.werken.werkz.Goal.firePostGoalCallbacks(Goal.java:710) at com.werken.werkz.Goal.fire(Goal.java:654) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575)
svn commit: r155277 - in maven/maven-1/plugins/trunk/linkcheck: src/main/org/apache/maven/linkcheck/validation/HTTPLinkValidator.java xdocs/changes.xml
Author: aheritier
Date: Thu Feb 24 15:23:29 2005
New Revision: 155277
URL: http://svn.apache.org/viewcvs?view=revrev=155277
Log:
MPLINKCHECK-21 : java.lang.NumberFormatException if proxy port is setted to
Modified:
maven/maven-1/plugins/trunk/linkcheck/src/main/org/apache/maven/linkcheck/validation/HTTPLinkValidator.java
maven/maven-1/plugins/trunk/linkcheck/xdocs/changes.xml
Modified:
maven/maven-1/plugins/trunk/linkcheck/src/main/org/apache/maven/linkcheck/validation/HTTPLinkValidator.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/linkcheck/src/main/org/apache/maven/linkcheck/validation/HTTPLinkValidator.java?view=diffr1=155276r2=155277
==
---
maven/maven-1/plugins/trunk/linkcheck/src/main/org/apache/maven/linkcheck/validation/HTTPLinkValidator.java
(original)
+++
maven/maven-1/plugins/trunk/linkcheck/src/main/org/apache/maven/linkcheck/validation/HTTPLinkValidator.java
Thu Feb 24 15:23:29 2005
@@ -30,7 +30,7 @@
/**
* Checks links which are normal URLs
* @author a href=mailto:[EMAIL PROTECTED]Ben Walding/a
- * @version $Id: HTTPLinkValidator.java,v 1.13 2004/08/01 22:28:14 carlos Exp $
+ * @version $Id$
*/
public class HTTPLinkValidator implements LinkValidator
{
@@ -51,7 +51,7 @@
public HTTPLinkValidator(String proxyHost, String proxyPort, String
proxyUser, String proxyPass)
{
-if (proxyHost == null)
+if (proxyHost == null || proxyHost.trim().equals())
{
LOG.info(maven-linkcheck-plugin: Not using a proxy);
this.proxyHost = null;
@@ -59,7 +59,13 @@
else
{
this.proxyHost = proxyHost;
-this.proxyPort = Integer.parseInt(proxyPort);
+try{
+ this.proxyPort = Integer.parseInt(proxyPort);
+}catch(NumberFormatException e){
+ LOG.warn(maven-linkcheck-plugin: Invalid number for Proxy
Port: + proxyPort);
+ LOG.warn(maven-linkcheck-plugin: Proxy Port won't be used.);
+ this.proxyPort = 0;
+}
this.proxyUser = proxyUser;
this.proxyPass = proxyPass;
LOG.info(maven-linkcheck-plugin: Proxy Host: + proxyHost);
Modified: maven/maven-1/plugins/trunk/linkcheck/xdocs/changes.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/linkcheck/xdocs/changes.xml?view=diffr1=155276r2=155277
==
--- maven/maven-1/plugins/trunk/linkcheck/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/linkcheck/xdocs/changes.xml Thu Feb 24 15:23:29
2005
@@ -25,8 +25,9 @@
author email=[EMAIL PROTECTED]Vincent Massol/author
/properties
body
-release version=1.4-SNAPSHOT date=in CVS
+release version=1.4-SNAPSHOT date=in SVN
action dev=brett type=updateMake compatible with Maven 1.1/action
+ action dev=aheritier type=fix
issue=MPLINKCHECK-21java.lang.NumberFormatException if proxy port is setted
to /action
/release
release version=1.3.4 date=2004-11-20
action dev=carlos type=fix issue=MPLINKCHECK-17Made compatible
with JDK 1.3/action
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPLINKCHECK-21) java.lang.NumberFormatException if proxy port is setted to
Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Thu, 24 Feb 2005 6:23 PM Fixed - View the issue: http://jira.codehaus.org/browse/MPLINKCHECK-21 Here is an overview of the issue: - Key: MPLINKCHECK-21 Summary: java.lang.NumberFormatException if proxy port is setted to Type: Bug Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-linkcheck-plugin Fix Fors: 1.4 Versions: 1.3.4 Assignee: Reporter: Arnaud HERITIER Created: Thu, 24 Feb 2005 6:02 PM Updated: Thu, 24 Feb 2005 6:23 PM Environment: Maven 1.0.2 Description: If maven.proxy.port is an empty string we have this error : BUILD FAILED File.. D:\Work\Data\maven\cache\maven-linkcheck-plugin-1.3.4\plugin.jelly Element... linkcheck:linkcheck Line.. 91 Column 9 For input string: com.werken.werkz.UnattainableGoalException: Unable to obtain goal [site] -- D:\Work\Data\maven\cache\maven-linkcheck-plugin-1.3.4\plugin.jelly:91:9: linkcheck: linkcheck For input string: at com.werken.werkz.Goal.fire(Goal.java:646) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:488) at org.apache.maven.cli.App.main(App.java:1239) 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:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.apache.commons.jelly.JellyTagException: D:\Work\Data\maven\cache\maven-linkcheck-plugin-1.3.4\plugin.jelly:91:9: linkcheck:linkcheck For input string: at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:243) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:145) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at com.werken.werkz.jelly.PostGoalTag$1.firePostGoal(PostGoalTag.java:87) at com.werken.werkz.Goal.firePostGoalCallbacks(Goal.java:710) at com.werken.werkz.Goal.fire(Goal.java:654) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at
[jira] Commented: (MAVEN-1505) Allow project layout other than src/java src/test
The following comment has been added to this issue: Author: Nick Matthews Created: Thu, 24 Feb 2005 8:28 PM Body: Another use for this feature is keeping generated code seperate from the main source tree. In some large projects that we have, it makes it much easier to keep the source which is held under source control under a central directory (the src/ directory) and a tree containing source that is automatically generated (what we have as the autogen/ directory). Currently, to do this in maven is quite awkward. This also makes it simpler to do a 'clean' build. Removing the contents of the autogen/ directory is much simpler than a script which selectively prunes portions of the src/ directory. - View this comment: http://jira.codehaus.org/browse/MAVEN-1505?page=comments#action_30292 - View the issue: http://jira.codehaus.org/browse/MAVEN-1505 Here is an overview of the issue: - Key: MAVEN-1505 Summary: Allow project layout other than src/java src/test Type: Improvement Status: Reopened Priority: Blocker Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.1 Versions: 1.0.1 Assignee: Reporter: [EMAIL PROTECTED] Created: Sun, 14 Nov 2004 1:08 PM Updated: Thu, 24 Feb 2005 8:28 PM Description: At present, maven does not work properly unless the java source files are contained under the directory src/java. Seems wrong to have to change the project directory struture just in order to use maven. Would it not be possible to add some information to the project xml file to tell maven where to find the source files? - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1505) Allow project layout other than src/java src/test
Message: The following issue has been closed. Resolver: Brett Porter Date: Thu, 24 Feb 2005 8:34 PM ok, this has been revisted. The same solution will be kept. You will specify one source directory, but can easily add additional ones using plugins when source is generated, or if you have an existing build to convert (using maven:addPath / as per the FAQ). What will happen is that all plugins should become fully aware of the multiple source directories, and this is happening where possible. For the previous commenter - it is wise to generate your sources to target/generated-sources/foo, then add them to the compile.src.set so they get cleaned up afterwards. Many plugins do this - eg antlr, jaxb, etc. - View the issue: http://jira.codehaus.org/browse/MAVEN-1505 Here is an overview of the issue: - Key: MAVEN-1505 Summary: Allow project layout other than src/java src/test Type: Improvement Status: Closed Priority: Blocker Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.0.1 Assignee: Reporter: [EMAIL PROTECTED] Created: Sun, 14 Nov 2004 1:08 PM Updated: Thu, 24 Feb 2005 8:34 PM Description: At present, maven does not work properly unless the java source files are contained under the directory src/java. Seems wrong to have to change the project directory struture just in order to use maven. Would it not be possible to add some information to the project xml file to tell maven where to find the source files? - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
