cvs commit: maven-plugins/java/xdocs faq.fml navigation.xml
dion2004/08/02 23:49:47 Modified:java/xdocs navigation.xml Added: java/xdocs faq.fml Log: Document 1.5 settings Revision ChangesPath 1.5 +1 -0 maven-plugins/java/xdocs/navigation.xml Index: navigation.xml === RCS file: /home/cvs/maven-plugins/java/xdocs/navigation.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- navigation.xml4 Mar 2004 18:35:34 - 1.4 +++ navigation.xml3 Aug 2004 06:49:47 - 1.5 @@ -29,6 +29,7 @@ + 1.1 maven-plugins/java/xdocs/faq.fml Index: faq.fml === JDK 1.5 How do I get Maven to compile using JDK 1.5? The default javac settings cause problems with jdk 1.5 because the target is set to 1.1 and no source has been set. You will need to provide two properties to allow compilation to work with 1.5: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Options for the Jakarta Taglibs Maven repository
[*] +1 Create one directory for group
Notice some artifact allready have been uploaded on ibiblio in inconsistant
directories :
/xerces/jars/xmlParserApis-2.0.0/2.0.2/2.2.1
=
/xml-apis/jars/xmlParserApis-2.0.0/2.0.2
Assuming 2.2.1 is only in xerces group, it looks to be the 'correct' groupid for this
artifact. But for compatibility
those jars remain in xml-api with a Readme.html warning.
MAVEN ENHANCEMENT SUGGESTION:
Could'nt we have an automatic way to 'deprecate' some artifcat location, giving the
alternative group/artifactId to be
used ? It may been displayed by maven as a warning when downloading dependencies.
For example, a stamp file "groupid/type/artifactid-version.deprecated" may be a text
file containing the warning message
that maven can search when it downloads an artifact.
Nico.
- Original Message -
From: "Felipe Leme" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, August 03, 2004 7:02 AM
Subject: [VOTE] Options for the Jakarta Taglibs Maven repository
> Hi all,
>
> As we haven't reached a common sense on how to name the groups, I think
> we should vote for it. The issues are:
>
>
> 1.Multiple directories x one directory:
>
> [ ] +1 Put everything in one directory (such as jakarta-taglibs)
>Advantage: less groups on ibiblio
>Disadvantage: the group is going to be huge (around 30-80 files on
> each artifact sub-dir)
> [ ] +1 Create one directory for group (ex: taglibs-standard,
> taglibs-request).
>Advantages: easier to locate artifacts; consistent with the way
> Jakarta Commons is organized
> [ ] +0 Doesn't matter for me
>
> 2.(In case one directory wins previous poll)
> [ ] +1 Use new directory 'jakarta-taglibs
>Advantage: better identify which taglibs that group refers too
>Disadvantage: replication of existing directory ('taglibs')
> [ ] +1 Use existing directory 'taglibs'
>Advantage: no replication of existing directory
>Disadvantage: name is too generic
> [ ] +0 Doesn't matter for me
>
> 3.Where to put jstl.jar
> [ ] +1 Wherever standard.jar is
> Advantage: jstl.jar is created by Jakarta Standard Taglibs
> Disadvantage: it's a JCP API of its own; replication of existing
> directory ('jstl')
> [ ] +1 On existing group jstl
> Advantage: no replication of existing directory; better separation
> between specification (JSTL) and implementation (Jakarta Standard
> Taglibs)
> Disadvantage: jar is created by another project (there is no JSTL
> project on Jakarta/ASF); inconsistent with another groups (like
> servletapi)
> [ ] +1 On new group jstlapi
> Advantage: consistent with another groups (like servletapi); better
> separation between specification (JSTL) and implementation (Jakarta
> Standard Taglibs)
> Disadvantage: jar is created by another project (there is no JSTL
> project on Jakarta/ASF), replication of existing directory ('jstl');
> ugly name
> [ ] +0 Doesn't matter for me
>
>
> Notice that this is note a typical committer-issue-vote (it's not even
> totally related to the Maven project itself), but I rather listen your
> opinions now then decide the structure myself and have to handle the
> consequences later (specially because we cannot change it once it's
> uploaded to ibiblio).
>
> Regards,
>
> Felipe
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
Our name has changed. Please update your address book to the following format:
"[EMAIL PROTECTED]".
This message contains information that may be privileged or confidential and is the
property of the Capgemini Group. It is intended only for the person to whom it is
addressed. If you are not the intended recipient, you are not authorized to read,
print, retain, copy, disseminate, distribute, or use this message or any part
thereof. If you receive this message in error, please notify the sender immediately
and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPXDOC-114) cvs-usage presumes pserve protocol on
The following comment has been added to this issue: Author: dion gillard Created: Tue, 3 Aug 2004 2:37 AM Body: "The problem I have now is that this really isn't a "report", it is a "Project Info" menu item in the navigation. But I now have it under "Project Reports" instead. What can be done about that? Do we need a mechanism in the xdoc-plugin to register such items as well as reports?" Yes, we do... - View this comment: http://jira.codehaus.org/browse/MPXDOC-114?page=comments#action_22672 - View the issue: http://jira.codehaus.org/browse/MPXDOC-114 Here is an overview of the issue: - Key: MPXDOC-114 Summary: cvs-usage presumes pserve protocol on Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-xdoc-plugin Assignee: Jason van Zyl Reporter: Erik Husby Created: Wed, 7 Jul 2004 4:10 PM Updated: Tue, 3 Aug 2004 2:37 AM Description: The Repository report makes some assumptions about ones use of cvs that are not necessarily true. 1. The pom.repository.connection is assumed to be the pserve protocol. Not true for our in-house projects. 2. The pom.repository.developerConnection is only displayed when there is a pom.repository.connection entry. The two fields are not connected. 3. The CVS Access behind firewall is always included if pom.repository.connection is specified. This is not true in our in-house environment. The changelog report works fine if only pom.repository.developerConnection is specified, I would like to not specify pom.repository.connnection Problem#1 can be addressed by examinging the cvs protocol and adjusting the comments. Problem#2 I experimented with modifing the cvs-usage.xml but not being knowledge in velocity, I could not see why problem #2 occurs. Problem#3 can be solved in a number of ways from an addition to the pom.repository or by an additional maven-xdoc-plugin property. - 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-1412) command line -D options seemingly ignored
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1412 Here is an overview of the issue: - Key: MAVEN-1412 Summary: command line -D options seemingly ignored Type: Bug Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.0 Assignee: Reporter: David Blevins Created: Tue, 3 Aug 2004 2:04 AM Updated: Tue, 3 Aug 2004 2:04 AM Environment: $ uname -a CYGWIN_NT-5.1 Pepe 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown Cygwin $ $JAVA_HOME/bin/java -version java version "1.4.2_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b01) Java HotSpot(TM) Client VM (build 1.4.2_03-b01, mixed mode) Description: Trying to run the Geronimo build with -Dmaven.test.failure.ignore=true does not work on the command line. This option does work when added to the project.properties file. Editing the maven shell script to echo the java command rather than execute yeilds this output: /program_files/jdk1.4.2/bin/java -Xmx256m -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djava.endorsed.dirs=C:\program_files\jdk1.4.2\lib\endorsed;C:\program_files\maven-1.0\lib\endorsed -classpath C:\program_files\maven-1.0/lib/forehead-1.0-beta-5.jar -Dforehead.conf.file=C:\program_files\maven-1.0/bin/forehead.conf -Dtools.jar=C:\program_files\jdk1.4.2/lib/tools.jar -Dmaven.home=C:\program_files\maven-1.0 com.werken.forehead.Forehead -Dmaven.test.failure.ignore=true - 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]
Re: [VOTE] Options for the Jakarta Taglibs Maven repository
Just curious, but are you in control of the jakarta-taglibs builds? I
understand if you're pinging the maven-dev list for best practices (I
suppose, but the maven-user list would probably be better), but if
you're wanting us to actually make a change in the layout of the
jakarta-taglibs organization on ibiblio, you're talking to the wrong
people...the taglibs people are able to control that.
just FYI.
-j
On Tue, 2004-08-03 at 01:02, Felipe Leme wrote:
> Hi all,
>
> As we haven't reached a common sense on how to name the groups, I think
> we should vote for it. The issues are:
>
>
> 1.Multiple directories x one directory:
>
> [ ] +1 Put everything in one directory (such as jakarta-taglibs)
>Advantage: less groups on ibiblio
>Disadvantage: the group is going to be huge (around 30-80 files on
> each artifact sub-dir)
> [ ] +1 Create one directory for group (ex: taglibs-standard,
> taglibs-request).
>Advantages: easier to locate artifacts; consistent with the way
> Jakarta Commons is organized
> [ ] +0 Doesn't matter for me
>
> 2.(In case one directory wins previous poll)
> [ ] +1 Use new directory 'jakarta-taglibs
>Advantage: better identify which taglibs that group refers too
>Disadvantage: replication of existing directory ('taglibs')
> [ ] +1 Use existing directory 'taglibs'
>Advantage: no replication of existing directory
>Disadvantage: name is too generic
> [ ] +0 Doesn't matter for me
>
> 3.Where to put jstl.jar
> [ ] +1 Wherever standard.jar is
> Advantage: jstl.jar is created by Jakarta Standard Taglibs
> Disadvantage: it's a JCP API of its own; replication of existing
> directory ('jstl')
> [ ] +1 On existing group jstl
> Advantage: no replication of existing directory; better separation
> between specification (JSTL) and implementation (Jakarta Standard
> Taglibs)
> Disadvantage: jar is created by another project (there is no JSTL
> project on Jakarta/ASF); inconsistent with another groups (like
> servletapi)
> [ ] +1 On new group jstlapi
> Advantage: consistent with another groups (like servletapi); better
> separation between specification (JSTL) and implementation (Jakarta
> Standard Taglibs)
> Disadvantage: jar is created by another project (there is no JSTL
> project on Jakarta/ASF), replication of existing directory ('jstl');
> ugly name
> [ ] +0 Doesn't matter for me
>
>
> Notice that this is note a typical committer-issue-vote (it's not even
> totally related to the Maven project itself), but I rather listen your
> opinions now then decide the structure myself and have to handle the
> consequences later (specially because we cannot change it once it's
> uploaded to ibiblio).
>
> Regards,
>
> Felipe
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
[EMAIL PROTECTED]
CommonJava Open Components Project
http://www.commonjava.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Options for the Jakarta Taglibs Maven repository
Hi all,
As we haven't reached a common sense on how to name the groups, I think
we should vote for it. The issues are:
1.Multiple directories x one directory:
[ ] +1 Put everything in one directory (such as jakarta-taglibs)
Advantage: less groups on ibiblio
Disadvantage: the group is going to be huge (around 30-80 files on
each artifact sub-dir)
[ ] +1 Create one directory for group (ex: taglibs-standard,
taglibs-request).
Advantages: easier to locate artifacts; consistent with the way
Jakarta Commons is organized
[ ] +0 Doesn't matter for me
2.(In case one directory wins previous poll)
[ ] +1 Use new directory 'jakarta-taglibs
Advantage: better identify which taglibs that group refers too
Disadvantage: replication of existing directory ('taglibs')
[ ] +1 Use existing directory 'taglibs'
Advantage: no replication of existing directory
Disadvantage: name is too generic
[ ] +0 Doesn't matter for me
3.Where to put jstl.jar
[ ] +1 Wherever standard.jar is
Advantage: jstl.jar is created by Jakarta Standard Taglibs
Disadvantage: it's a JCP API of its own; replication of existing
directory ('jstl')
[ ] +1 On existing group jstl
Advantage: no replication of existing directory; better separation
between specification (JSTL) and implementation (Jakarta Standard
Taglibs)
Disadvantage: jar is created by another project (there is no JSTL
project on Jakarta/ASF); inconsistent with another groups (like
servletapi)
[ ] +1 On new group jstlapi
Advantage: consistent with another groups (like servletapi); better
separation between specification (JSTL) and implementation (Jakarta
Standard Taglibs)
Disadvantage: jar is created by another project (there is no JSTL
project on Jakarta/ASF), replication of existing directory ('jstl');
ugly name
[ ] +0 Doesn't matter for me
Notice that this is note a typical committer-issue-vote (it's not even
totally related to the Maven project itself), but I rather listen your
opinions now then decide the structure myself and have to handle the
consequences later (specially because we cannot change it once it's
uploaded to ibiblio).
Regards,
Felipe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPANNOUNCEMENT-9) Add a goal to send the announcement by mail to a list of email addresses
The following comment has been added to this issue: Author: Felipe Leme Created: Mon, 2 Aug 2004 11:39 PM Body: > You can do cvs add foo/bar.java, it's only a client side operation. That's what I thought too, but it didn't work: [EMAIL PROTECTED]/cvs/maven/maven-plugins/announcement: cvs add src/main/org/apache/maven/announcement/MailUtils.java cvs [server aborted]: "add" requires write access to the repository - View this comment: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9?page=comments#action_22660 - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9 Here is an overview of the issue: - Key: MPANNOUNCEMENT-9 Summary: Add a goal to send the announcement by mail to a list of email addresses Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Versions: 1.2 Assignee: Vincent Massol Reporter: Vincent Massol Created: Thu, 8 Jul 2004 4:16 AM Updated: Mon, 2 Aug 2004 11:39 PM 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: (MPANNOUNCEMENT-9) Add a goal to send the announcement by mail to a list of email addresses
The following comment has been added to this issue: Author: Trygve Laugstol Created: Mon, 2 Aug 2004 11:34 PM Body: You can do cvs add foo/bar.java, it's only a client side operation. You won't be able to commit the file though. This will as you said make cvs diff include the new files. - View this comment: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9?page=comments#action_22659 - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9 Here is an overview of the issue: - Key: MPANNOUNCEMENT-9 Summary: Add a goal to send the announcement by mail to a list of email addresses Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Versions: 1.2 Assignee: Vincent Massol Reporter: Vincent Massol Created: Thu, 8 Jul 2004 4:16 AM Updated: Mon, 2 Aug 2004 11:34 PM 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] Updated: (MPANNOUNCEMENT-9) Add a goal to send the announcement by mail to a list of email addresses
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 11:25 PM Comment: After a few more tests, I'm sending a new patch (this is the last one, I promise :-), with the following improvements: - better handling on network exceptions - removal of CC: (as commons-net CC doesn't work properly) Notice that I've packed the patch and the new Java file in one zip (cvs diff -u would only work if I could do a cvs add first). Felipe Changes: Attachment changed to ultimate_patch.zip - For a full history of the issue, see: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9?page=history - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9 Here is an overview of the issue: - Key: MPANNOUNCEMENT-9 Summary: Add a goal to send the announcement by mail to a list of email addresses Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Versions: 1.2 Assignee: Vincent Massol Reporter: Vincent Massol Created: Thu, 8 Jul 2004 4:16 AM Updated: Mon, 2 Aug 2004 11:25 PM 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] Updated: (MPANNOUNCEMENT-9) Add a goal to send the announcement by mail to a list of email addresses
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 10:04 PM Comment: Oops, looks like 'cvs diff -u' does not add new files... Changes: Attachment changed to MailUtils.java - For a full history of the issue, see: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9?page=history - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9 Here is an overview of the issue: - Key: MPANNOUNCEMENT-9 Summary: Add a goal to send the announcement by mail to a list of email addresses Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Versions: 1.2 Assignee: Vincent Massol Reporter: Vincent Massol Created: Thu, 8 Jul 2004 4:16 AM Updated: Mon, 2 Aug 2004 10:04 PM 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] Updated: (MPANNOUNCEMENT-9) Add a goal to send the announcement by mail to a list of email addresses
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 10:03 PM Comment: New patch, using commons-net instead of jelly-email. Changes: Attachment changed to mpannouncement-9-commons_net.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9?page=history - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-9 Here is an overview of the issue: - Key: MPANNOUNCEMENT-9 Summary: Add a goal to send the announcement by mail to a list of email addresses Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Versions: 1.2 Assignee: Vincent Massol Reporter: Vincent Massol Created: Thu, 8 Jul 2004 4:16 AM Updated: Mon, 2 Aug 2004 10:03 PM 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: (MPMULTIPROJECT-38) multiproject:site doesn't generate overview page with links to projects
The following comment has been added to this issue: Author: dion gillard Created: Mon, 2 Aug 2004 9:18 PM Body: Do you have any more detail to help us solve this? If not, it's been a month and we haven't heard anything - View this comment: http://jira.codehaus.org/browse/MPMULTIPROJECT-38?page=comments#action_22654 - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-38 Here is an overview of the issue: - Key: MPMULTIPROJECT-38 Summary: multiproject:site doesn't generate overview page with links to projects Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-multiproject-plugin Assignee: dion gillard Reporter: Michael Mattox Created: Thu, 17 Jun 2004 9:40 AM Updated: Mon, 2 Aug 2004 9:18 PM Environment: maven 1.0rc3, win2k, jsdk1.4.2 Description: I don't know what happened, but now multiproject:site doesn't generate overview page with links to projects. All the projects are there under the multiproject dir, but there is no overview page. I've spent hours and hours on this and I can't figure it out. When I use multiproject.includes=**/project.xml it doesn't produce an overview. When I list the projects it does. - 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]
cvs commit: maven-plugins/multiproject/xdocs reports.xml
dion2004/08/02 18:15:41 Modified:multiproject/xdocs reports.xml Log: Little more detail Revision ChangesPath 1.3 +1 -1 maven-plugins/multiproject/xdocs/reports.xml Index: reports.xml === RCS file: /home/cvs/maven-plugins/multiproject/xdocs/reports.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- reports.xml 3 Aug 2004 01:13:43 - 1.2 +++ reports.xml 3 Aug 2004 01:15:41 - 1.3 @@ -31,7 +31,7 @@ of artifacts between the projects of a multiproject build. -To register this report, include the following in your project.xml: +To register this report, include the following in your top-level project.xml:
cvs commit: maven-plugins/multiproject/xdocs reports.xml
dion2004/08/02 18:13:44 Modified:multiproject plugin.jelly multiproject/xdocs reports.xml Log: Typo Revision ChangesPath 1.46 +1 -1 maven-plugins/multiproject/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/multiproject/plugin.jelly,v retrieving revision 1.45 retrieving revision 1.46 diff -u -r1.45 -r1.46 --- plugin.jelly 29 Jul 2004 06:40:44 - 1.45 +++ plugin.jelly 3 Aug 2004 01:13:43 - 1.46 @@ -314,7 +314,7 @@ name="Dependency Convergence" link="dependency-convergence-report" pluginName="maven-multiproject-plugin" - description="Generate report which shows how consistent are the versions of artitfacts between projects."/> + description="Generate report which shows how consistent are the versions of artifacts between projects."/> 1.2 +1 -1 maven-plugins/multiproject/xdocs/reports.xml Index: reports.xml === RCS file: /home/cvs/maven-plugins/multiproject/xdocs/reports.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- reports.xml 3 Aug 2004 00:58:40 - 1.1 +++ reports.xml 3 Aug 2004 01:13:43 - 1.2 @@ -28,7 +28,7 @@ This plug-in provides a report which shows how consistent the versions -of artitfacts between the projects of a multiproject build. +of artifacts between the projects of a multiproject build. To register this report, include the following in your project.xml: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/multiproject/xdocs changes.xml
dion2004/08/02 18:01:42 Modified:multiproject/xdocs changes.xml Log: Document dependency convergence report. Issue MPMULTIPROJECT-41 Revision ChangesPath 1.28 +1 -0 maven-plugins/multiproject/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/multiproject/xdocs/changes.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- changes.xml 29 Jul 2004 06:40:44 - 1.27 +++ changes.xml 3 Aug 2004 01:01:42 - 1.28 @@ -26,6 +26,7 @@ + Document multiproject dependency convergence report Add multiproject:site Deprecate dependency handle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPMULTIPROJECT-41) Document the multiproject report
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-41 Here is an overview of the issue: - Key: MPMULTIPROJECT-41 Summary: Document the multiproject report Type: Improvement Status: Closed Priority: Trivial Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-multiproject-plugin Fix Fors: 1.4 Assignee: dion gillard Reporter: Carlos Sanchez Created: Tue, 20 Jul 2004 8:05 AM Updated: Mon, 2 Aug 2004 9:02 PM 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]
cvs commit: maven-plugins/multiproject/xdocs reports.xml index.xml navigation.xml
dion2004/08/02 17:58:41 Modified:multiproject/xdocs index.xml navigation.xml Added: multiproject/xdocs reports.xml Log: Document dependency convergence report. Issue MPMULTIPROJECT-41 Revision ChangesPath 1.3 +6 -1 maven-plugins/multiproject/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/maven-plugins/multiproject/xdocs/index.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- index.xml 4 Mar 2004 18:36:33 - 1.2 +++ index.xml 3 Aug 2004 00:58:40 - 1.3 @@ -30,13 +30,18 @@ This plug-in provides the ability to work with many projects via the same interface as a single project. - + For more information on the functionality provided by this plugin, please see the Goals document. For more information on how to customise the functionality provided by this plugin, please see the properties +document. + + +For more information on the reports provided +by this plugin, please see the reports document. 1.10 +1 -0 maven-plugins/multiproject/xdocs/navigation.xml Index: navigation.xml === RCS file: /home/cvs/maven-plugins/multiproject/xdocs/navigation.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- navigation.xml2 May 2004 10:26:36 - 1.9 +++ navigation.xml3 Aug 2004 00:58:40 - 1.10 @@ -28,6 +28,7 @@ + 1.1 maven-plugins/multiproject/xdocs/reports.xml Index: reports.xml === Maven Multi-Project Plugin dIon Gillard This plug-in provides a report which shows how consistent the versions of artitfacts between the projects of a multiproject build. To register this report, include the following in your project.xml: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1410) pom.artifactId is missing from XML schema and pom.id should be removed
The following issue has been updated: Updater: Dennis Lundberg (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 7:46 PM Comment: Documentation patches for the HEAD branch. Changelog: 1. I have replaced all occurances of "id" and replaced them with "artifactId", except in xdocs/reference/project-descriptor.xml. 2. Added a section for "artifactId" in xdocs/reference/project-descriptor.xml. 3. Put notes on the deprecated elements in xdocs/reference/project-descriptor.xml so that you can clearly see which elements are deprecated. Changes: Attachment changed to xdocs-artifactId.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1410?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1410 Here is an overview of the issue: - Key: MAVEN-1410 Summary: pom.artifactId is missing from XML schema and pom.id should be removed Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: model Versions: 1.0 Assignee: Reporter: Dennis Lundberg Created: Fri, 30 Jul 2004 4:06 PM Updated: Mon, 2 Aug 2004 7:46 PM Description: After some discussion on the dev-list "pom.id versus pom.artifactId - which is correct?" there seems to be some inconsistencies in the 1.0 release. The discussion resulted in the following conclusions: 1. The element project.id should be removed from the XML schema 2. The element project.artifactId should be added to the XML schema 3. Documentation needs to be updated to reflect the above issues 1 and 2 should probably be done by one of the core developers, including decisions regarding version numbers for the XML schema. I can make a patch for it if you think that's ok. I can make patches for the xdocs to fix 3. On which branch should I create the patches? - 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: (MPMULTIPROJECT-42) Multiproject fails calculating dependencies due to internal exception
Message: The following issue has been closed. Resolver: dion gillard Date: Mon, 2 Aug 2004 7:35 PM Duplicate of MPMULTIPROJECT-40 by the looks - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-42 Here is an overview of the issue: - Key: MPMULTIPROJECT-42 Summary: Multiproject fails calculating dependencies due to internal exception Type: Bug Status: Closed Priority: Blocker Resolution: DUPLICATE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-multiproject-plugin Assignee: dion gillard Reporter: Joerg Schaible Created: Wed, 21 Jul 2004 5:54 AM Updated: Mon, 2 Aug 2004 7:35 PM Environment: WinXP, Cygwin, Sun JDK 1.4.2, Maven 1.0, maven-multiproject-plugin-1.3.1 (not available for selection in JIRA) included in Maven 1.0 Description: I cannot build with Maven in a simple multiproject setup (root and 2 subprojects), since Maven tries to build the two dependent subprojects in wrong order. Using "maven -X multiproject:install" shows, that an exception occurs before the dependencies are calculated: %< multiproject:projects-init: [echo] Gathering project list Starting the reactor... Using userBuildPropertiesFile: C:\Dokumente und Einstellungen\jos\build.properties Using projectPropertiesFile: C:\Work\Projects\credit-suisse\csfnh\root\..\fnHandler\project.properties Using projectBuildPropertiesFile: C:\Work\Projects\credit-suisse\csfnh\root\..\fnHandler\build.properties Using userBuildPropertiesFile: C:\Dokumente und Einstellungen\jos\build.properties Using projectPropertiesFile: C:\Work\Projects\credit-suisse\csfnh\root\project.properties Using projectBuildPropertiesFile: C:\Work\Projects\credit-suisse\csfnh\root\build.properties Using userBuildPropertiesFile: C:\Dokumente und Einstellungen\jos\build.properties Using projectPropertiesFile: C:\Work\Projects\credit-suisse\csfnh\root\..\rPicStub\project.properties Using projectBuildPropertiesFile: C:\Work\Projects\credit-suisse\csfnh\root\..\rPicStub\build.properties Unexpected error evaluating expression java.lang.ClassCastException at org.apache.maven.MavenUtils.integrateMapInContext(MavenUtils.java:820) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:240) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenUtils.getProjects(MavenUtils.java:290) at org.apache.maven.jelly.tags.maven.ReactorTag.getSortedProjects(ReactorTag.java:400) at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:296) 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.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.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.cli.App.doMain(App.java:486) at org.apache.maven.cli.App.main(App.java:1215) 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) Unexpected error evaluating expression java.lang.ClassCastException at org.apache.maven.MavenUtils.integrateMapInContext(MavenUtils.java:820) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:240) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenUtils.getProjects(MavenUtils.java:290)
[jira] Closed: (MPMULTIPROJECT-23) multiproject:site fails if a subproject's site could not be found
Message: The following issue has been closed. Resolver: dion gillard Date: Mon, 2 Aug 2004 7:34 PM AFAIK, this was fixed by adding a mkdir to the plugin. If this is not the case, please reopen - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-23 Here is an overview of the issue: - Key: MPMULTIPROJECT-23 Summary: multiproject:site fails if a subproject's site could not be found Type: Improvement Status: Closed Priority: Major Resolution: FIXED Original Estimate: 15 minutes Time Spent: Unknown Remaining: 15 minutes Project: maven-multiproject-plugin Assignee: dion gillard Reporter: Oliver Noelle Created: Fri, 26 Mar 2004 5:30 AM Updated: Mon, 2 Aug 2004 7:34 PM Environment: maven-rc-2, win2k Description: When a subproject could not build its site, the goal multiproject:site fails due to the fact that it can not find the directory to copy over to maven.docs.dest. I don't know whether this is normally the desired behaviour, for our context we would like to have the site generated as far as it is possible, and not make a single site problem to fail the multiproject site goal. Possible workaround: I added a line to check for the existence of the index.html file in the maven.docs.dest dir of the subproject. If this file does not exist, it skips the copy goal which would fail. Code snippet, see the comment and 2 lines added: - 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: (MPMULTIPROJECT-23) multiproject:site fails if a subproject's site could not be found
The following issue has been updated: Updater: dion gillard (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 7:28 PM Changes: Fix Version changed to 1.4 - For a full history of the issue, see: http://jira.codehaus.org/browse/MPMULTIPROJECT-23?page=history - View the issue: http://jira.codehaus.org/browse/MPMULTIPROJECT-23 Here is an overview of the issue: - Key: MPMULTIPROJECT-23 Summary: multiproject:site fails if a subproject's site could not be found Type: Improvement Status: Open Priority: Major Original Estimate: 15 minutes Time Spent: Unknown Remaining: 15 minutes Project: maven-multiproject-plugin Fix Fors: 1.4 Assignee: dion gillard Reporter: Oliver Noelle Created: Fri, 26 Mar 2004 5:30 AM Updated: Mon, 2 Aug 2004 7:28 PM Environment: maven-rc-2, win2k Description: When a subproject could not build its site, the goal multiproject:site fails due to the fact that it can not find the directory to copy over to maven.docs.dest. I don't know whether this is normally the desired behaviour, for our context we would like to have the site generated as far as it is possible, and not make a single site problem to fail the multiproject site goal. Possible workaround: I added a line to check for the existence of the index.html file in the maven.docs.dest dir of the subproject. If this file does not exist, it skips the copy goal which would fail. Code snippet, see the comment and 2 lines added: - 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-1410) pom.artifactId is missing from XML schema and pom.id should be removed
The following issue has been updated: Updater: Dennis Lundberg (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 6:18 PM Comment: 1. OK, it stays in POM3. 2. To add "artifactId" and still keep "id" we should probably use a "choice" in the XML schema. See attached patch for an example of how this can be done. 3. I will start writing documentation patches for the HEAD branch, unless someone objects. Changes: Attachment changed to maven-project-3.xsd.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1410?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1410 Here is an overview of the issue: - Key: MAVEN-1410 Summary: pom.artifactId is missing from XML schema and pom.id should be removed Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: model Versions: 1.0 Assignee: Reporter: Dennis Lundberg Created: Fri, 30 Jul 2004 4:06 PM Updated: Mon, 2 Aug 2004 6:18 PM Description: After some discussion on the dev-list "pom.id versus pom.artifactId - which is correct?" there seems to be some inconsistencies in the 1.0 release. The discussion resulted in the following conclusions: 1. The element project.id should be removed from the XML schema 2. The element project.artifactId should be added to the XML schema 3. Documentation needs to be updated to reflect the above issues 1 and 2 should probably be done by one of the core developers, including decisions regarding version numbers for the XML schema. I can make a patch for it if you think that's ok. I can make patches for the xdocs to fix 3. On which branch should I create the patches? - 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-180) Upload dynaop 1.0 beta
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-180 Here is an overview of the issue: - Key: MAVENUPLOAD-180 Summary: Upload dynaop 1.0 beta Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Joerg Schaible Created: Mon, 2 Aug 2004 6:12 PM Updated: Mon, 2 Aug 2004 6:12 PM Description: dynaop, a proxy-based Aspect-Oriented Programming (AOP) framework. Lisence is ASF 2.0. - 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: (MPANNOUNCEMENT-13) [PATCH] announcement:generate cannot handle accentuation
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-13 Here is an overview of the issue: - Key: MPANNOUNCEMENT-13 Summary: [PATCH] announcement:generate cannot handle accentuation Type: Bug Status: Unassigned Priority: Major Original Estimate: 15 minutes Time Spent: Unknown Remaining: 15 minutes Project: maven-announcement-plugin Versions: 1.3 Assignee: Reporter: Felipe Leme Created: Mon, 2 Aug 2004 6:08 PM Updated: Mon, 2 Aug 2004 6:08 PM Description: The announcement message is always generate as UTF-8, which makes some accentuated characters (like á,ç,ã, etc...) pretty messy. I'm providing a simple patch where the user can supply the encoding as a Maven property (which by default is UTF-8) Felipe - 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: (MPANNOUNCEMENT-13) [PATCH] announcement:generate cannot handle accentuation
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 6:09 PM Comment: Vincent, Here is the patch I promissed... Felipe Changes: Attachment changed to mpannouncement-13.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MPANNOUNCEMENT-13?page=history - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-13 Here is an overview of the issue: - Key: MPANNOUNCEMENT-13 Summary: [PATCH] announcement:generate cannot handle accentuation Type: Bug Status: Unassigned Priority: Major Original Estimate: 15 minutes Time Spent: Unknown Remaining: 15 minutes Project: maven-announcement-plugin Versions: 1.3 Assignee: Reporter: Felipe Leme Created: Mon, 2 Aug 2004 6:08 PM Updated: Mon, 2 Aug 2004 6:09 PM Description: The announcement message is always generate as UTF-8, which makes some accentuated characters (like á,ç,ã, etc...) pretty messy. I'm providing a simple patch where the user can supply the encoding as a Maven property (which by default is UTF-8) Felipe - 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-1405) Maven can not authentificate to a HTTP Proxy
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Mon, 2 Aug 2004 5:21 PM
Changes:
Fix Version changed to 1.0.1
-
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1405?page=history
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1405
Here is an overview of the issue:
-
Key: MAVEN-1405
Summary: Maven can not authentificate to a HTTP Proxy
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.0.1
Versions:
1.0
Assignee:
Reporter: Philipp Kohl
Created: Mon, 26 Jul 2004 4:05 AM
Updated: Mon, 2 Aug 2004 5:21 PM
Environment: Windows 2000,
Squid Proxy on Linux with User Authentification
Description:
I am using windows 2000 and I'm sitting behind a firewall, so I added this to my
%USERPROFILE%\build.properties:
maven.proxy.host = myProxyHostIpAddress
maven.proxy.port = 8080
maven.proxy.username = myUsername
maven.proxy.password = myPassword
this should enable the usage of our proxy, right?
But unfortunately I still get this error messages when I start maven for my
project:
###snipp###
> maven
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0
Plugin cache will be regenerated
Directory C:\java\.maven\repository does not exist. Attempting to create.
Attempting to download dom4j-1.4-dev-8.jar.
Recoverable exception caught but MethodRetryHandler.retryMethod() returned
false, rethrowing exception
A recoverable exception
occurred.org.apache.commons.httpclient.HttpRecoverableException: Error in
parsing the status line from the response: unable to find line starting
with "HTTP"
retrying (1)
Error retrieving artifact from
[http://www.ibiblio.org/maven/dom4j/jars/dom4j-1.4-dev-8.jar]:
org.apache.commons.httpclient.HttpException: Already used, but not
recycled.
WARNING: Failed to download dom4j-1.4-dev-8.jar.
Attempting to download commons-jelly-20030902.160215.jar.
Recoverable exception caught but MethodRetryHandler.retryMethod() returned
false, rethrowing exception
A recoverable exception
occurred.org.apache.commons.httpclient.HttpRecoverableException: Error in
parsing the status line from the response: unable to find line starting
with "HTTP"
retrying (1)
Error retrieving artifact from
[http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-20030902.160215.jar]:
org.apache.commons.httpclient.HttpException: Already used, but not
recycled.
WARNING: Failed to download commons-jelly-20030902.160215.jar.
...
WARNING: Failed to download xml-apis-1.0.b2.jar.
The build cannot continue because of the following unsatisfied
dependencies:
dom4j-1.4-dev-8.jar
commons-jelly-20030902.160215.jar
commons-jelly-tags-jsl-20030211.143151.jar
commons-jelly-tags-log-20030211.142821.jar
commons-jelly-tags-velocity-20030303.205659.jar
commons-jelly-tags-xml-20040613.030723.jar (try downloading from
http://jakarta.apache.org/commons/jelly/libs/xml/)
commons-logging-1.0.3.jar
velocity-1.4-dev.jar
velocity-dvsl-0.45.jar
xml-apis-1.0.b2.jar
###snapp###
After changing
org.apache.maven.util.HttpUtils
>diff -a -b -u HttpUtils.bak HttpUtils.java
--- HttpUtils.bak 2004-07-25 11:33:23.668054700 +0200
+++ HttpUtils.java 2004-07-26 09:51:40.34700 +0200
@@ -367,6 +367,7 @@
client.setHostConfiguration(hc);
if (creds != null) {
client.getState().setProxyCredentials(null, null, creds);
+client.getState().setAuthenticationPreemptive(true);
}
// Basic authentication
It works fine...
-
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: (MPASPECTJ-12) Optional Aspects
The following comment has been added to this issue:
Author: Mark Proctor
Created: Mon, 2 Aug 2004 4:28 PM
Body:
I have further enhanced this in drools and include for reference purposes.
So that users can specify features they want compiled in at runtime I create a file in
src/aspects/conf that specifes the aspects to weave for that feature. That way I can
just do the following to specify the features I want:
drools.aspects = event-model, trace
The code to achieve this is:
${droolsAspects}
-
View this comment:
http://jira.codehaus.org/browse/MPASPECTJ-12?page=comments#action_22641
-
View the issue:
http://jira.codehaus.org/browse/MPASPECTJ-12
Here is an overview of the issue:
-
Key: MPASPECTJ-12
Summary: Optional Aspects
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-aspectj-plugin
Assignee:
Reporter: Mark Proctor
Created: Mon, 2 Aug 2004 4:22 PM
Updated: Mon, 2 Aug 2004 4:28 PM
Description:
We need the ability to weave in optional aspects.
-
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: (MPASPECTJ-12) Optional Aspects
The following issue has been updated: Updater: Mark Proctor (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 4:25 PM Comment: This diff allows optional aspects files to be included by specifying a comma delimited list in maven.aspectj.aspects. It uses the iajc argfiles propertly. if you use maven.aspectj.aspects only those files are weaved, other aspects in your aspect source directory will be ignored. The files specifed in maven.aspectj.aspects are line delimeted files either specifying the aspects to weave, or other line delimited files to process. Aspects are relative to the config file that specifies them. Changes: Attachment changed to optional-aspects.diff - For a full history of the issue, see: http://jira.codehaus.org/browse/MPASPECTJ-12?page=history - View the issue: http://jira.codehaus.org/browse/MPASPECTJ-12 Here is an overview of the issue: - Key: MPASPECTJ-12 Summary: Optional Aspects Type: New Feature Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-aspectj-plugin Assignee: Reporter: Mark Proctor Created: Mon, 2 Aug 2004 4:22 PM Updated: Mon, 2 Aug 2004 4:25 PM Description: We need the ability to weave in optional aspects. - 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: (MPASPECTJ-12) Optional Aspects
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPASPECTJ-12 Here is an overview of the issue: - Key: MPASPECTJ-12 Summary: Optional Aspects Type: New Feature Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-aspectj-plugin Assignee: Reporter: Mark Proctor Created: Mon, 2 Aug 2004 4:22 PM Updated: Mon, 2 Aug 2004 4:22 PM Description: We need the ability to weave in optional aspects. - 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-36) [PATCH] JUnit jar not add in a specific condition
The following issue has been updated: Updater: Felipe Leme (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 3:05 PM Comment: A simple fix for this issue. Changes: Attachment changed to mpeclipse-36.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MPECLIPSE-36?page=history - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-36 Here is an overview of the issue: - Key: MPECLIPSE-36 Summary: [PATCH] JUnit jar not add in a specific condition Type: Bug Status: Unassigned Priority: Major Original Estimate: 15 minutes Time Spent: Unknown Remaining: 15 minutes Project: maven-eclipse-plugin Versions: 1.8 Assignee: Reporter: Felipe Leme Created: Mon, 2 Aug 2004 3:03 PM Updated: Mon, 2 Aug 2004 3:05 PM Description: If your project doesn't have a in the POM, the JUnit jar is never included, even if it used by other classes (like Cactus testcases). The reason is the following code: This is not always true, because junit dependency is added inside the following statement: So, I'm providing a quick fix for this situation. - 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-36) [PATCH] JUnit jar not add in a specific condition
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-36 Here is an overview of the issue: - Key: MPECLIPSE-36 Summary: [PATCH] JUnit jar not add in a specific condition Type: Bug Status: Unassigned Priority: Major Original Estimate: 15 minutes Time Spent: Unknown Remaining: 15 minutes Project: maven-eclipse-plugin Versions: 1.8 Assignee: Reporter: Felipe Leme Created: Mon, 2 Aug 2004 3:03 PM Updated: Mon, 2 Aug 2004 3:03 PM Description: If your project doesn't have a in the POM, the JUnit jar is never included, even if it used by other classes (like Cactus testcases). The reason is the following code: This is not always true, because junit dependency is added inside the following statement: So, I'm providing a quick fix for this situation. - 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]
Re: Uploading jars for Maven
Hi Nick, You'll need to follow the repository-upload doco. The Apache committer bit is only for Apache projects (by publishing to www.apache.org/dist/java-repository Cheers, Brett Quoting Nick Lothian <[EMAIL PROTECTED]>: > Hi, > > I'd like to get some jars uploaded for the Rome project > (http://rome.dev.java.net). > > I'm an Apache committer - > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=16046 > says that I can/should just upload them myself, but > http://nagoya.apache.org/wiki/apachewiki.cgi?MavenRepository seem to > indicate I should follow > http://maven.apache.org/repository-upload.html, although if that is > the case it could be a little clearer. > > Which is it? > > Nick > > - > 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: (MPARTIFACT-36) ScpExeDeployer fails when maven.repo.[name].ssh.args and maven.repo.[name].scp.args not set
The following issue has been updated: Updater: Mark Church (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 9:13 AM Comment: This patch omits the option args attribute from the cmd array if the attribute is not specified. Changes: Attachment changed to MPARTIFACT-36.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MPARTIFACT-36?page=history - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-36 Here is an overview of the issue: - Key: MPARTIFACT-36 Summary: ScpExeDeployer fails when maven.repo.[name].ssh.args and maven.repo.[name].scp.args not set Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Assignee: Reporter: Mark Church Created: Sun, 1 Aug 2004 11:09 PM Updated: Mon, 2 Aug 2004 9:13 AM Environment: Fedora Core 2, J2SDK 1.4.2_05, Maven 1.0 Description: The ScpExeDeployer fails when the properties : maven.repo.[name].ssh.args maven.repo.[name].scp.args are not set. - 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: (MPARTIFACT-37) ScpExeDeployer ignores the maven.repo.[name].port attribute
The following issue has been updated: Updater: Mark Church (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 9:12 AM Comment: This patch adds the -p and -P options to ssh and scp respectively when the appropriate attributes are set. It depends on the patch attached to MPARTIFACT36. Changes: Attachment changed to MPARTIFACT-37.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MPARTIFACT-37?page=history - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-37 Here is an overview of the issue: - Key: MPARTIFACT-37 Summary: ScpExeDeployer ignores the maven.repo.[name].port attribute Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Assignee: Reporter: Mark Church Created: Mon, 2 Aug 2004 8:41 AM Updated: Mon, 2 Aug 2004 9:12 AM Environment: Fedora Core 2, J2SDK 1.4.2_05, Maven 1.0 Description: The ScpExeDeployer does not honor the maven.repo.[name].port attribute if it is set. - 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: (MPTEST-40) test:single reports a test error even when it can't find the test case
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPTEST-40 Here is an overview of the issue: - Key: MPTEST-40 Summary: test:single reports a test error even when it can't find the test case Type: Bug Status: Open Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-test-plugin Assignee: Jason van Zyl Reporter: Michael Mattox Created: Mon, 2 Aug 2004 8:52 AM Updated: Mon, 2 Aug 2004 8:52 AM Description: I run the test:single target and it tells me "tests run:1, failures:0, errors:1" even when it can't find the test case. When it can't find the testcase it should display an error. - 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: (MPARTIFACT-37) ScpExeDeployer ignores the maven.repo.[name].port attribute
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-37 Here is an overview of the issue: - Key: MPARTIFACT-37 Summary: ScpExeDeployer ignores the maven.repo.[name].port attribute Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-artifact-plugin Assignee: Reporter: Mark Church Created: Mon, 2 Aug 2004 8:41 AM Updated: Mon, 2 Aug 2004 8:41 AM Environment: Fedora Core 2, J2SDK 1.4.2_05, Maven 1.0 Description: The ScpExeDeployer does not honor the maven.repo.[name].port attribute if it is set. - 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: (MPJAR-34) Add an option to include test classes in jars
The following comment has been added to this issue: Author: dion gillard Created: Mon, 2 Aug 2004 8:32 AM Body: "Sometimes a few people really want/need a feature but others do not. I think it's not possible to satisify everyone 100% of the time." Hence maven.xml and post/pre goals, plugins... "If you don't want the test classes in the jar then that's fine, why force others to feel as you do?" I'm not forcing anyone, but Maven simply can't be all configurable, it'd be a mess. "Overall I think adding the property is the easiest quick fix to this problem. As it currently is I'm forced to put mock objects and some of my integration junit tests in my src/java tree. Anything is better than that." Quick fixes are not often the best ones. A quicker fix would be for you to postGoal the jar goal and add any test classes into the jar - View this comment: http://jira.codehaus.org/browse/MPJAR-34?page=comments#action_22624 - View the issue: http://jira.codehaus.org/browse/MPJAR-34 Here is an overview of the issue: - Key: MPJAR-34 Summary: Add an option to include test classes in jars Type: New Feature Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: Michael Mattox Created: Fri, 30 Jul 2004 5:26 AM Updated: Mon, 2 Aug 2004 8:32 AM Description: I have mock objects defined in my src/test tree. Other projects then use these mock objects for their tests. With Maven, test classes are not included in the distribution jars. Searching the mailing list, this seems to be a common need. The only viable solution I've seen is to move the mock objects to the src/java tree. I don't like this at all. I'd like to propose a new property: maven.jar.include.test.classes it could be false by default. Setting it to true would include the test classes in the jar. I consider test code just as important as my application code, so this option makes a lot of sense to me. I don't see any reason not to include, but at least adding the property would give the user the choice. - 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]
RE: Maven shared via Samba-Share
Thank's. It seems that I missed that answer :-) Am Mo, den 02.08.2004 schrieb Carlos Sanchez um 14:16: > Your question has been already answered in the maven-user list. > > > -Original Message- > > From: Christian Mouttet [mailto:[EMAIL PROTECTED] > > Sent: Monday, August 02, 2004 12:55 PM > > To: [EMAIL PROTECTED] > > Subject: Maven shared via Samba-Share > > > > Hi, > > > > i recently updated our Maven installation from 1.0-rc1 to 1.0 > > final. The installation directory lives on a Linux box and is > > shared via NFS and Samba. Working with Linux everything is > > o.k. but running Maven on a Windows machine shows me the > > following error message: > > > > -%<-- > > __ __ > > | \/ |__ _Apache__ ___ > > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > > |_| |_\__,_|\_/\___|_||_| v. 1.0 > > > > org.apache.maven.MavenException: Maven was badly installed. > > Please reinstall it. > > at > > org.apache.maven.plugin.PluginManager.initialize(PluginManager > > .java:240) > > at > > org.apache.maven.MavenSession.initializePluginManager(MavenSes > > sion.java:207) > > at > > org.apache.maven.MavenSession.initialize(MavenSession.java:174) > > at org.apache.maven.cli.App.doMain(App.java:473) > > at org.apache.maven.cli.App.main(App.java:1215) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > > orImpl.java:39) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl.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) > > > > You have encountered an unknown error running Maven. Please > > help us to correct this problem by following these simple steps: > > - read the Maven FAQ at http://maven.apache.org/faq.html > > - run the same command again with the '-e' parameter, eg maven -e jar > > - search the maven-user archives for the error at > > http://nagoya.apache.org/eyebrowse/SummarizeList?listName=user > [EMAIL PROTECTED] > > - post the output of maven -e to JIRA at > > http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up > > first) > > - run 'maven --info' and post the output as the environment > > to the bug above > > > > > > Total time: 24 seconds > > Finished at: Thu Jul 29 10:26:16 CEST 2004 > > -%<-- > > > > > > What is going wrong? > > > > This is my smb.conf: > > -%<-- > > [maven-1.0] > > path = /opt/maven-1.0 > > guest ok = Yes > > -%<-- > > > > Regards > > -Christian > > > > > > - > > 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: Maven shared via Samba-Share
Your question has been already answered in the maven-user list. > -Original Message- > From: Christian Mouttet [mailto:[EMAIL PROTECTED] > Sent: Monday, August 02, 2004 12:55 PM > To: [EMAIL PROTECTED] > Subject: Maven shared via Samba-Share > > Hi, > > i recently updated our Maven installation from 1.0-rc1 to 1.0 > final. The installation directory lives on a Linux box and is > shared via NFS and Samba. Working with Linux everything is > o.k. but running Maven on a Windows machine shows me the > following error message: > > -%<-- > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0 > > org.apache.maven.MavenException: Maven was badly installed. > Please reinstall it. > at > org.apache.maven.plugin.PluginManager.initialize(PluginManager > .java:240) > at > org.apache.maven.MavenSession.initializePluginManager(MavenSes > sion.java:207) > at > org.apache.maven.MavenSession.initialize(MavenSession.java:174) > at org.apache.maven.cli.App.doMain(App.java:473) > at org.apache.maven.cli.App.main(App.java:1215) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > orImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > odAccessorImpl.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) > > You have encountered an unknown error running Maven. Please > help us to correct this problem by following these simple steps: > - read the Maven FAQ at http://maven.apache.org/faq.html > - run the same command again with the '-e' parameter, eg maven -e jar > - search the maven-user archives for the error at > http://nagoya.apache.org/eyebrowse/SummarizeList?listName=user [EMAIL PROTECTED] > - post the output of maven -e to JIRA at > http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up > first) > - run 'maven --info' and post the output as the environment > to the bug above > > > Total time: 24 seconds > Finished at: Thu Jul 29 10:26:16 CEST 2004 > -%<-- > > > What is going wrong? > > This is my smb.conf: > -%<-- > [maven-1.0] > path = /opt/maven-1.0 > guest ok = Yes > -%<-- > > Regards > -Christian > > > - > 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: (MPJAR-34) Add an option to include test classes in jars
The following comment has been added to this issue: Author: Michael Mattox Created: Mon, 2 Aug 2004 8:14 AM Body: I'm glad to see some discussion on this topic. One of the challenges of Maven is to produce a utility that works for everyone. Sometimes a few people really want/need a feature but others do not. I think it's not possible to satisify everyone 100% of the time. I see both sides, for including the tests in the jar and for putting them in a separate project. I think the best thing to do is to give the user the choice. If you don't want the test classes in the jar then that's fine, why force others to feel as you do? Another topic came up today.. we'd like to run our junit tests on our integration servers. I pointed out that the tests aren't included in the jars. If we make a separate jar with test code, that complicates our deployment. So it's much simpler to use a property to toggle including the test classes or not. It's very useful during testing and integration to include them, and nice to not include them for production releases. Also if we put test classes in separate jars, that could theoretically double the number of projects. And that complicates the project.xmls. I think the dependencies are already a total mess as it is (I'm eagerly awaiting M2). What about conf files? Overall I think adding the property is the easiest quick fix to this problem. As it currently is I'm forced to put mock objects and some of my integration junit tests in my src/java tree. Anything is better than that. -Michael Mattox - View this comment: http://jira.codehaus.org/browse/MPJAR-34?page=comments#action_22622 - View the issue: http://jira.codehaus.org/browse/MPJAR-34 Here is an overview of the issue: - Key: MPJAR-34 Summary: Add an option to include test classes in jars Type: New Feature Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-jar-plugin Assignee: Jason van Zyl Reporter: Michael Mattox Created: Fri, 30 Jul 2004 5:26 AM Updated: Mon, 2 Aug 2004 8:14 AM Description: I have mock objects defined in my src/test tree. Other projects then use these mock objects for their tests. With Maven, test classes are not included in the distribution jars. Searching the mailing list, this seems to be a common need. The only viable solution I've seen is to move the mock objects to the src/java tree. I don't like this at all. I'd like to propose a new property: maven.jar.include.test.classes it could be false by default. Setting it to true would include the test classes in the jar. I consider test code just as important as my application code, so this option makes a lot of sense to me. I don't see any reason not to include, but at least adding the property would give the user the choice. - 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: (MAVEN-1410) pom.artifactId is missing from XML schema and pom.id should be removed
The following comment has been added to this issue: Author: dion gillard Created: Mon, 2 Aug 2004 7:40 AM Body: "1. The element project.id should be removed from the XML schema" id is a valid element in POM3. It's deprecated and shouldn't be removed. 2. The element project.artifactId should be added to the XML schema agree. 3. Documentation needs to be updated to reflect the above issues Yep. - View this comment: http://jira.codehaus.org/browse/MAVEN-1410?page=comments#action_22621 - View the issue: http://jira.codehaus.org/browse/MAVEN-1410 Here is an overview of the issue: - Key: MAVEN-1410 Summary: pom.artifactId is missing from XML schema and pom.id should be removed Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: model Versions: 1.0 Assignee: Reporter: Dennis Lundberg Created: Fri, 30 Jul 2004 4:06 PM Updated: Mon, 2 Aug 2004 7:40 AM Description: After some discussion on the dev-list "pom.id versus pom.artifactId - which is correct?" there seems to be some inconsistencies in the 1.0 release. The discussion resulted in the following conclusions: 1. The element project.id should be removed from the XML schema 2. The element project.artifactId should be added to the XML schema 3. Documentation needs to be updated to reflect the above issues 1 and 2 should probably be done by one of the core developers, including decisions regarding version numbers for the XML schema. I can make a patch for it if you think that's ok. I can make patches for the xdocs to fix 3. On which branch should I create the patches? - 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: (MAVEN-1410) pom.artifactId is missing from XML schema and pom.id should be removed
The following comment has been added to this issue:
Author: Peter Nabbefeld
Created: Mon, 2 Aug 2004 7:09 AM
Body:
Please do not change the schema for POM-3. Please only update the documentation.
Otherwise existent projects may break (my will, as I've had problems with the POM,
found the schema and corrected my POMs to contain id instead of artifactId. However,
there are inconsistencies I know about: ${pom.id} returns groupId:artifactId, while
${pom.artifactId} returns the id. IMO it would be better to release POM-4, so projects
can be moved to this. Please provide a doc then, how to move, or - better - provide a
tool/plugin for this move.
-
View this comment:
http://jira.codehaus.org/browse/MAVEN-1410?page=comments#action_22619
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1410
Here is an overview of the issue:
-
Key: MAVEN-1410
Summary: pom.artifactId is missing from XML schema and pom.id should be removed
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
model
Versions:
1.0
Assignee:
Reporter: Dennis Lundberg
Created: Fri, 30 Jul 2004 4:06 PM
Updated: Mon, 2 Aug 2004 7:09 AM
Description:
After some discussion on the dev-list "pom.id versus pom.artifactId - which is
correct?" there seems to be some inconsistencies in the 1.0 release.
The discussion resulted in the following conclusions:
1. The element project.id should be removed from the XML schema
2. The element project.artifactId should be added to the XML schema
3. Documentation needs to be updated to reflect the above issues
1 and 2 should probably be done by one of the core developers, including decisions
regarding version numbers for the XML schema. I can make a patch for it if you think
that's ok.
I can make patches for the xdocs to fix 3. On which branch should I create the patches?
-
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]
Maven shared via Samba-Share
Hi, i recently updated our Maven installation from 1.0-rc1 to 1.0 final. The installation directory lives on a Linux box and is shared via NFS and Samba. Working with Linux everything is o.k. but running Maven on a Windows machine shows me the following error message: -%<-- __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Maven was badly installed. Please reinstall it. at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:240) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:207) at org.apache.maven.MavenSession.initialize(MavenSession.java:174) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) 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) You have encountered an unknown error running Maven. Please help us to correct this problem by following these simple steps: - read the Maven FAQ at http://maven.apache.org/faq.html - run the same command again with the '-e' parameter, eg maven -e jar - search the maven-user archives for the error at http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] - post the output of maven -e to JIRA at http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up first) - run 'maven --info' and post the output as the environment to the bug above Total time: 24 seconds Finished at: Thu Jul 29 10:26:16 CEST 2004 -%<-- What is going wrong? This is my smb.conf: -%<-- [maven-1.0] path = /opt/maven-1.0 guest ok = Yes -%<-- Regards -Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dev@maven.apache.org
Yes, is for testing an issue with names that broke xml parsing > -Original Message- > From: Dion Gillard [mailto:[EMAIL PROTECTED] > Sent: Monday, August 02, 2004 1:20 AM > To: Maven Developers List > Subject: Re: cvs commit: > maven-plugins/linkcheck/src/plugin-test/xdocs &test.html > > On 1 Aug 2004 22:23:02 -, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > carlos 2004/08/01 15:23:02 > > > > Added: linkcheck/src/plugin-test/xdocs &test.html > > Did you mean this to have an & in the name? > -- > http://www.multitask.com.au/people/dion/ > > - > 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: (MPSCM-21) Cannot check-out a project :The ' characters not part of the command & CommandLauncher
The following issue has been updated: Updater: Maciejowski (mailto:[EMAIL PROTECTED]) Date: Mon, 2 Aug 2004 4:23 AM Comment: Here is the log output with the -X option. Concerning the port, CVS here , is set up to work with 2410, and not the default 2401. Changes: Attachment changed to maven_checkout_cvs.log - For a full history of the issue, see: http://jira.codehaus.org/browse/MPSCM-21?page=history - View the issue: http://jira.codehaus.org/browse/MPSCM-21 Here is an overview of the issue: - Key: MPSCM-21 Summary: Cannot check-out a project :The ' characters not part of the command & CommandLauncher Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-scm-plugin Assignee: Brett Porter Reporter: Maciejowski Created: Fri, 30 Jul 2004 8:35 AM Updated: Mon, 2 Aug 2004 4:23 AM Environment: Windows NT Maven 1.0 j2sdk1.4.2_05 CVS Description: Cannot check-out a project from CVS. Even from Eclipse or in command line: maven scm:checkout-project ... scm:validate: scm:checkout-project: scm:cvs-checkout-project: [echo] Checking out redouteSimbocoSptvteWeb; from CVSROOT: :pserver:[EMAIL PROTECTED]:2410/prod/cvs/data/repository/dev [mkdir] Created dir: D:\Norsys_david\eclipse3.0\eclipse\workspace\buildsimbocoSptvte\simbocosptvteWeb\target\checkouts\redouteSimbocoSptvteWeb [cvs] [VERBOSE] Executing 'cvs' with arguments: '-d:pserver:[EMAIL PROTECTED]:2410/prod/cvs/data/repository/dev' '-q' 'checkout' '-P' 'redouteSimbocoSptvteWeb' The ' characters around the executable and arguments are not part of the command. [cvs] [DEBUG] Execute:Java13CommandLauncher: Executing 'cvs' with arguments: '-d:pserver:[EMAIL PROTECTED]:2410/prod/cvs/data/repository/dev' '-q' 'checkout' '-P' 'redouteSimbocoSptvteWeb' The ' characters around the executable and arguments are not part of the command. - 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: (MPEJB-12) Update plugin properties documentation of default values
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPEJB-12 Here is an overview of the issue: - Key: MPEJB-12 Summary: Update plugin properties documentation of default values Type: Bug Status: Unassigned Priority: Trivial Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-ejb-plugin Versions: 1.5 Assignee: Reporter: Julien Kirch Created: Mon, 2 Aug 2004 3:17 AM Updated: Mon, 2 Aug 2004 3:17 AM Description: The plugin properties documentation is incomplete for the default values (some values are missing or are incomplete). - 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: (MPLINKCHECK-10) allo 303 and 304 http status to be validated
The following comment has been added to this issue: Author: Kees Jongenburger Created: Mon, 2 Aug 2004 3:05 AM Body: I partialy agree. following moved_permanently should not be automatic Still it's a valid url - View this comment: http://jira.codehaus.org/browse/MPLINKCHECK-10?page=comments#action_22610 - View the issue: http://jira.codehaus.org/browse/MPLINKCHECK-10 Here is an overview of the issue: - Key: MPLINKCHECK-10 Summary: allo 303 and 304 http status to be validated Type: Improvement Status: Open Priority: Major Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven-linkcheck-plugin Assignee: Ben Walding Reporter: Kees Jongenburger Created: Mon, 15 Mar 2004 6:55 PM Updated: Mon, 2 Aug 2004 3:05 AM Environment: maven rc2 Description: The linkchecker flows MOVED_TEMPORARILY moved links but sikps MOVED_PERMANENTLY while there are as valid as MOVED_TEMPORARILY example: http://www.mmbase.org/license resolution: add import org.apache.commons.httpclient.HttpStatus; to the class imports in HTTPLinkValidator at row 108 change the code to if (gm.getStatusCode() == HttpStatus.SC_MOVED_TEMPORARILY || gm.getStatusCode() == HttpStatus.SC_MOVED_PERMANENTLY) (and a small cleanup ) row 121 if (gm.getStatusCode() == HttpStatus.SC_OK) - 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]
