[continuum build - FAILED - update] Wed Oct 26 07:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.073000.txt
[continuum build - FAILED - update] Wed Oct 26 09:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.09.txt
[continuum build - FAILED - update] Wed Oct 26 11:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.11.txt
[continuum build - FAILED - update] Wed Oct 26 11:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.113000.txt
[continuum build - FAILED - update] Wed Oct 26 12:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.123000.txt
[continuum build - FAILED - update] Wed Oct 26 15:30:01 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.153001.txt
[continuum build - FAILED - update] Wed Oct 26 16:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.16.txt
[ANN] Continuum 1.0 Final released
The Maven team is pleased to announce the 1.0 of Continuum. Continuum is a continous integration server. We have progressively improved Continuum over five previous releases and now provides the following features: * Support for Maven 2.x * Support for Maven 1.x * Support for Ant * Support for shell scripts * Tight integration with Maven SCM * Subversion * CVS * Starteam * Easy to use web-based setup and interface * XML-RPC and SOAP interfaces for integration, automation and remoting * Mail Notification * IM notification * IRC * Jabber * MSN * Blame Mechanism For a complete list of changes please refer to the complete changelog: http://maven.apache.org/continuum/change-log.html To get started with Continuum take a look at the download and install instructions: http://maven.apache.org/continuum/download.html And then take a look at our getting started guide: http://maven.apache.org/continuum/guides/getting-started/index.html
[continuum build - FAILED - update] Wed Oct 26 16:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.163000.txt
[jira] Reopened: (CONTINUUM-367) error when calling getprojects() through xml-rpc
[ http://jira.codehaus.org/browse/CONTINUUM-367?page=all ]
Milos Kleint reopened CONTINUUM-367:
not really. I've installed 1.0 final and get a similar problem.
not sure what I'm doing wrong. teh code is fairly simple:
// Create an object to represent our server.
XmlRpcClient server = new XmlRpcClient(http://localhost:8000;);
Object obj = server.execute(continuum.getProjects, new Vector());
I get this error back.
result=failure, stackTrace=java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.continuum.xmlrpc.DefaultXmlRpcHelper.objectToHashtable(DefaultXmlRpcHelper.java:212)
at
org.apache.maven.continuum.xmlrpc.DefaultXmlRpcHelper.objectToHashtable(DefaultXmlRpcHelper.java:67)
at
org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.convertContinuumProject(DefaultContinuumXmlRpc.java:395)
at
org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.getProjects(DefaultContinuumXmlRpc.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.xmlrpc.Invoker.execute(Unknown Source)
at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(Unknown Source)
at org.apache.xmlrpc.XmlRpcWorker.execute(Unknown Source)
at org.apache.xmlrpc.XmlRpcServer.execute(Unknown Source)
at org.apache.xmlrpc.XmlRpcServer.execute(Unknown Source)
at org.apache.xmlrpc.WebServer$Connection.run(Unknown Source)
at org.apache.xmlrpc.WebServer$Runner.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jdo.JDODetachedFieldAccessException: You have just attempted
to access field buildResults yet this field was not detached when you
detached the object. Either dont access this field, or detach the field when
detaching the object.
at
org.apache.maven.continuum.model.project.Project.jdoGetbuildResults(Project.java)
at
org.apache.maven.continuum.model.project.Project.getBuildResults(Project.java:338)
... 20 more
, message=, method=ContinuumXmlRpc.getProjects()}
error when calling getprojects() through xml-rpc
-
Key: CONTINUUM-367
URL: http://jira.codehaus.org/browse/CONTINUUM-367
Project: Continuum
Type: Bug
Components: continuum-xmlrpc
Versions: 1.0-beta-1
Environment: mandrake linux 2005
Reporter: Milos Kleint
Assignee: Emmanuel Venisse
Priority: Blocker
Fix For: 1.0
when I call getProjects() method through xml-rpc, it returns correctly when
there are no projects, but fails when there are some.
happened both on my localhost server and maven.zones.apache.org server.
the error is following:
obj={result=failure, stackTrace=java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.continuum.xmlrpc.DefaultXmlRpcHelper.objectToHashtable(DefaultXmlRpcHelper.java:212)
at
org.apache.maven.continuum.xmlrpc.DefaultXmlRpcHelper.objectToHashtable(DefaultXmlRpcHelper.java:67)
at
org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.convertContinuumProject(DefaultContinuumXmlRpc.java:395)
at
org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.getProjects(DefaultContinuumXmlRpc.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.xmlrpc.Invoker.execute(Unknown Source)
at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(Unknown Source)
at org.apache.xmlrpc.XmlRpcWorker.execute(Unknown Source)
at org.apache.xmlrpc.XmlRpcServer.execute(Unknown Source)
at org.apache.xmlrpc.XmlRpcServer.execute(Unknown Source)
at org.apache.xmlrpc.WebServer$Connection.run(Unknown Source)
at org.apache.xmlrpc.WebServer$Runner.run(Unknown Source)
at
[continuum build - FAILED - update] Wed Oct 26 18:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.180001.txt
[jira] Created: (CONTINUUM-370) cvs tag ignored
cvs tag ignored --- Key: CONTINUUM-370 URL: http://jira.codehaus.org/browse/CONTINUUM-370 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0 Environment: maven-2.0.0, contiuum-1.0 Reporter: Ryan Sonnek Continuum ignores the CVS tag attribute set on a maven2 project. You can configure the branch/version for the build using the edit project page, but it should respect the tag in the pom.xml example pom.xml: scm connectionscm:cvs:pserver:[EMAIL PROTECTED]:/cvs:project//connection developerConnectionscm:cvs:pserver:[EMAIL PROTECTED]:/cvs:project//developerConnection tagVERSION_1_0/tag /scm Continuum output: 2005-10-26 13:13:15,015 [Thread-1] DEBUG ScmManager - Command line: cvs -f -d :pserver:[EMAIL PROTECTED]:2401/cvs -q checkout -d 2 project I could be misunderstanding the purpose of the scm tag. Any clarification on this would be appreciated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[continuum build - FAILED - update] Wed Oct 26 19:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.190001.txt
[continuum build - FAILED - update] Wed Oct 26 21:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.21.txt
[continuum build - FAILED - update] Wed Oct 26 22:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.22.txt
[continuum build - FAILED - update] Wed Oct 26 22:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.223000.txt
[continuum build - FAILED - update] Thu Oct 27 00:30:02 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051027.003003.txt
[continuum build - FAILED - checkout] Thu Oct 27 01:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051027.013000.txt
[continuum build - FAILED - update] Thu Oct 27 03:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051027.03.txt
[continuum build - FAILED - update] Thu Oct 27 03:30:01 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051027.033001.txt
[continuum build - FAILED - update] Thu Oct 27 04:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051027.043000.txt
[continuum build - FAILED - update] Thu Oct 27 05:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051027.05.txt
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/26-Oct-2005_02.02.11/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 06:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.06.txt
RE: [m1] New Release managers for plugins
Ok, I summarize what we actually said (I keep the plugins I currently have - I'll take some others if needed). Abbot : To be decommissioned in sandbox Announcement : Lukas Ant: Arnaud Antlr : Artifact : AspectJ: Castor : Changelog : Lukas Changes: Lukas Checkstyle : Carlos (always interested ?) Clean : Clover : Vincent M Console: Cruise Control : Dashboard : Developer Activity : Lukas Distribution : EAR: Stephan Eclipse: EJB: FAQ: Lukas File Activity : Lukas Genapp : Arnaud Gump : Hibernate : Html2XDoc : IDEA : Stephan J2EE : Jalopy : Jar: Java : Javacc : Stephan Javadoc: Arnaud JBoss : JBuilder : JCoverage : JDepend: JDiff : JellyDoc : Jetty : JIRA : JNLP : JUnit Report : JXR: License: LinkCheck : MultiChanges : Multi-Project : Lukas Native : NSIS : PDF: Arnaud Plugin : Lukas PMD: POM: Lukas RAR: Stephan Release: Repository : SCM: Simian : Site : Lukas Tasklist : Test : Uberjar: WAR: XDoc : Arnaud Others volunteers ? Others plugins to remove ? Brett, do you think you'll find some time to work on m1 and its plugins ? Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] New Release managers for plugins
I don't think so, I already did this some time ago. - Brett Arnaud HERITIER wrote: [snip] Maven Abbot plugin Decommissioned in sandbox Not yet done but I agree with this. Is there some others plugins that should be moved to the sandbox ? Arnaud - 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]
[maven2 build - FAILED - update] Wed Oct 26 06:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.06.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-369) Stop button to cancel the in progress of a project.
Stop button to cancel the in progress of a project. - Key: CONTINUUM-369 URL: http://jira.codehaus.org/browse/CONTINUUM-369 Project: Continuum Type: New Feature Components: continuum-web Versions: 1.0-beta-1 Environment: Linux and Windows Reporter: Fritz Oconer Request feature that will enable a user to cancel the build of a particular project. Kinda like hitting ctrl c when maven is executed. There are times when a project is stuck indefinitely in in progress state (e.g. when running a broken testcase that executes indefinitely). This affects other projects because it has to wait for the previous one to finish. Restarting continuum is not much help because it just goes back to the original state or you cannot delete the project itself because delete link is disable. The only solution now is to redeploy continuum. Now, having a cancel button would definitely help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVEN-1717) Website glossary entry plugin has bad link to Jelly
[ http://jira.codehaus.org/browse/MAVEN-1717?page=all ] Arnaud Heritier closed MAVEN-1717: -- Resolution: Fixed Fixed. Thanks. Be careful, due to the web site refactoring the new url for this page is : http://maven.apache.org/maven-1.x/reference/glossary.html#Plugin Website glossary entry plugin has bad link to Jelly - Key: MAVEN-1717 URL: http://jira.codehaus.org/browse/MAVEN-1717 Project: Maven Type: Bug Components: documentation Reporter: Doug Hockin Priority: Minor Website glossary entry plugin has bad link to Jelly http://maven.apache.org/reference/glossary.html#Plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 06:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.061501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: my plugin is invoked okay directly but not at all as part of site.
I took the day off work yesterday as
I was sick, and took the time to check out all the maven-plugins stuff
from SVN. Reading through the code I 'discovered' reference to the
AbstractMavenReport - something that so far has not made its way into the
documentation, and which almost certainly explains why my QALabMojo (which
only extends AbstractMojo) is not working as a report :-)
I'll look further into this today. Is
there any documentation I should be reading? Any more hidden classes
I should know about? Or shoudl I just read the entire source code?
I'm still not quite sure how I tell
the report which goal to run however.
Kind regards,
Dave Sag
Brett Porter [EMAIL PROTECTED] wrote on 24/10/2005
08:12:30 PM:
It's hard without a full POM to tell exactly what you are doing. Let
me
explain how this is processed.
Your Mojo should extend AbstractMavenReport, which enables it as both
a
report and a mojo.
When running as a mojo, configuration is used with first winning:
1) build plugin execution configuration
2) build plugin general configuration
3) reporting plugin general configuration
When running as a report, configuration is used with the first winning:
1) reporting plugin individual report configuration
2) reporting plugin general configuration
So in general you configure the report in the reporting section, adding
configuration only specific to build executions in the build section.
Hope this helps.
- Brett
David Sag wrote:
still more on this.
if i move the configuration from out of the eexcutions and up
into the
main plugin thus:
plugin
groupIdcom.davesag/groupId
artifactIdqalab-plugin/artifactId
configuration
quietfalse/quiet
handlernet.objectlab.qalab.parser.CheckstyleStatMerge/handler
inputFile${project.build.directory}/target/checkstyle-result.
xml/inputFile
/configuration
executions
execution
goals
goalmerge/goal
/goals
/execution
/executions
/plugin
the configuration is recongnised okay. but that's no good
for me as i
need different configs for different goals.
Kind regards,
Dave Sag
David Sag [EMAIL PROTECTED] wrote on 24/10/2005 04:05:09 PM:
Even weirder -
the below is slightly wrong.
in my reporting block I must specify the plugin config
again thus:
plugin
groupIdcom.davesag/groupId
artifactIdqalab-plugin/artifactId
configuration
quietfalse/quiet
handlernet.objectlab.qalab.parser.CheckstyleStatMerge/handler
inputFile${project.build.directory}/target/checkstyle-
result.xml/inputFile
/configuration
/plugin
or maven claims that i have not specified any parameters.
i still get nothing generated if i run mvn site however
if i remove the entire reporting block i get the same
error, as if i
had not configured it.
so can someone please explain what the sotry is with
plugin
configuration? it seems you must configure plugins
both in the
build section AND the reporting section for anything
to work.
similarly for the javadoc plugin, as of the latest
change, i must
now specify source = 1.4 in both the rewporting configuration
of the
plugin, AND the build configuration of the plugin.
am i just hopelessly confused?
Kind regards,
Dave Sag
[image removed]
David Sag [EMAIL PROTECTED] wrote on 24/10/2005
03:55:25 PM:
Dear People,
My mojo is built and installed.
I have specified the goal and phase thus:
* @goal merge
* @phase validate
I have added a reference to the build
block of a shell project thus:
plugin
groupIdcom.davesag/groupId
artifactIdqalab-plugin/artifactId
executions
execution
idqalab-blah/id
phasevalidate/phase
configuration
quietfalse/quiet
handlernet.objectlab.qalab.parser.
CheckstyleStatMerge/handler
inputFile${project.build.directory}
/target/checkstyle-result.xml/inputFile
/configuration
goals
goalmerge/goal
/goals
/execution
/executions
/plugin
when i type
mvn qalab:merge
i get an error telling me it can't read from
the checkstyle results
file. this is a reasonable result.
BUT
in the reporting section of the pom.xml I have
added
plugin
groupIdcom.davesag/groupId
artifactIdqalab-plugin/artifactId
/plugin
and when I type
mvn site
it's as if my plugin just wasn't even there.
It never gets run.
the checkstyle report is run (yet to work out
how to get it to
export as an xml file), and the javadocs are
generated and so forth,
but my qalab plugin may as well not exist.
if i try deliberately breaking the name then
maven complains that
[continuum build - FAILED - update] Wed Oct 26 06:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.063000.txt
[maven2 build - FAILED - update] Wed Oct 26 06:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.063000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 06:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.064500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 07:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.07.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 07:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.071500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-963) add toplinks configuration for FAQs
[ http://jira.codehaus.org/browse/MNG-963?page=comments#action_49273 ] Johnny R. Ruiz III commented on MNG-963: In FML file, Can we add the configuration as one attribute to faqs title=FAQs toplink=true tag? If set to true then generate all [top] links of the FAQs. or an individual configuration per faq toplink=true is required? add toplinks configuration for FAQs - Key: MNG-963 URL: http://jira.codehaus.org/browse/MNG-963 Project: Maven 2 Type: Improvement Components: maven-site-plugin Reporter: Brett Porter Assignee: Johnny R. Ruiz III Fix For: 2.0.1 Original Estimate: 3 hours Remaining: 3 hours need to be able to tell the FAQ whether to generate the top links. There are probably a few options for configuring the sinks: - put it in the fml file as metadata - add that configuration to the site mojo as various subsections that can be passed as beans to doxia - add to site.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 07:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.073000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1204) don't show disabled repositories in artifact exceptions
[ http://jira.codehaus.org/browse/MNG-1204?page=comments#action_49274 ] Edwin Punzalan commented on MNG-1204: - I can't see when a repo is disabled... is that the same as blacklisted ? don't show disabled repositories in artifact exceptions --- Key: MNG-1204 URL: http://jira.codehaus.org/browse/MNG-1204 Project: Maven 2 Type: Bug Components: maven-artifact Reporter: Brett Porter Priority: Minor Fix For: 2.0.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1326) Using CVS/CVN/etc. as source-code repository for Maven + having list of known projects.
Using CVS/CVN/etc. as source-code repository for Maven + having list of known projects. --- Key: MNG-1326 URL: http://jira.codehaus.org/browse/MNG-1326 Project: Maven 2 Type: New Feature Reporter: Miks Rozenbergs INTRODUCTION This feature is about Maven being able to automatically download source for dependent projects and compile them. The desired procedure would be to: 1. manually check out the project you wish to build 2. run maven on it Maven itself would then: 1. read through dependencies, 2. checkout each of the dependencies from Source Control system 3. for each checked out project, do step #1. This would for example solve the issue of re-build everything from an arbitrary node on dependency graph e.g. creating a hotfix for some big application. IMPLEMENTATION It would require to have a list of all known groupId/artifactId/version with they corresponding location. Maven would know the location of this list (it can be provided in settings.xml) and for each dependency it would check this list to see where to get the it's source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 07:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.074500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/26-Oct-2005_04.01.14/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 08:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.08.txt
[maven2 build - FAILED - update] Wed Oct 26 08:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.08.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 08:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.081501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 08:30:01 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.083001.txt
[maven2 build - FAILED - update] Wed Oct 26 08:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.083001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 08:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.084500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-963) add toplinks configuration for FAQs
[ http://jira.codehaus.org/browse/MNG-963?page=comments#action_49279 ] Johnny R. Ruiz III commented on MNG-963: I submitted patch for DOXIA-21. [top] links will be generated if attribute toplink=true. eg. faqs title=FAQs toplink=true Is this OK? add toplinks configuration for FAQs - Key: MNG-963 URL: http://jira.codehaus.org/browse/MNG-963 Project: Maven 2 Type: Improvement Components: maven-site-plugin Reporter: Brett Porter Assignee: Johnny R. Ruiz III Fix For: 2.0.1 Original Estimate: 3 hours Remaining: 3 hours need to be able to tell the FAQ whether to generate the top links. There are probably a few options for configuring the sinks: - put it in the fml file as metadata - add that configuration to the site mojo as various subsections that can be passed as beans to doxia - add to site.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 09:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.09.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-904) the maven-created target directory needs to be excluded from the idea projects
[ http://jira.codehaus.org/browse/MNG-904?page=all ] Allan Ramirez updated MNG-904: -- Attachment: MNG-904-maven-idea-plugin.patch -This patch will excludes all source files in target directory the maven-created target directory needs to be excluded from the idea projects -- Key: MNG-904 URL: http://jira.codehaus.org/browse/MNG-904 Project: Maven 2 Type: Improvement Components: maven-idea-plugin Reporter: Matthew Pocock Assignee: Allan Ramirez Attachments: MNG-904-maven-idea-plugin.patch, target.patch The idea plugin creates idea projects where the target/classes directory is excluded. However, all the content in target is generated, and it confused idea, forcing reloads and other glitches. I've patched the skeleton project artifact to exclude the target directory entirely. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-904) the maven-created target directory needs to be excluded from the idea projects
[ http://jira.codehaus.org/browse/MNG-904?page=comments#action_49281 ] Allan Ramirez commented on MNG-904: --- I mean, will exclude all non-source files in target directory :) the maven-created target directory needs to be excluded from the idea projects -- Key: MNG-904 URL: http://jira.codehaus.org/browse/MNG-904 Project: Maven 2 Type: Improvement Components: maven-idea-plugin Reporter: Matthew Pocock Assignee: Allan Ramirez Attachments: MNG-904-maven-idea-plugin.patch, target.patch The idea plugin creates idea projects where the target/classes directory is excluded. However, all the content in target is generated, and it confused idea, forcing reloads and other glitches. I've patched the skeleton project artifact to exclude the target directory entirely. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 09:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.093000.txt
[maven2 build - FAILED - update] Wed Oct 26 09:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.091500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1314) The default project-jdk-name in project.ipr doesn't work when used on Idea when jdkName is not specified in pom
[ http://jira.codehaus.org/browse/MNG-1314?page=all ] Johnny R. Ruiz III updated MNG-1314: Attachment: MNG-1314-maven-idea-plugin.patch I have created a patch for this. - By default it will use the project-jdk-name format from Idea version 5.0.1 which is 1.4 or 1.5. - You can set argument -DideaVersion=4.xxx to use the format java version quot;1.4.2_08quot; Please apply. Thanks. The default project-jdk-name in project.ipr doesn't work when used on Idea when jdkName is not specified in pom - Key: MNG-1314 URL: http://jira.codehaus.org/browse/MNG-1314 Project: Maven 2 Type: Bug Components: maven-idea-plugin Reporter: Johnny R. Ruiz III Assignee: Johnny R. Ruiz III Fix For: 2.0.1 Attachments: MNG-1314-maven-idea-plugin.patch When jdkName is not specified in configuration of idea:idea, the default java version is used. It creates an entry in project.ipr that is not working. component name=ProjectRootManager version=2 assert-keyword=false jdk-15=false project-jdk-name=java version 1.4.2_08 / -- this doesn't work component name=ProjectRootManager version=2 assert-keyword=true jdk-15=false project-jdk-name=java version quot;1.4.2_08quot; / -- this worked. Does anyone experience the same problem? I'll create a patch for this, might be useful if this is really an error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONTINUUM-369) Stop button to cancel the in progress of a project.
[ http://jira.codehaus.org/browse/CONTINUUM-369?page=comments#action_49285 ] Trygve Laugstol commented on CONTINUUM-369: --- I know Hiram Chirino had some ideas about this when I talked to him about stopping processes from java. Stop button to cancel the in progress of a project. - Key: CONTINUUM-369 URL: http://jira.codehaus.org/browse/CONTINUUM-369 Project: Continuum Type: New Feature Components: continuum-web Versions: 1.0-beta-1 Environment: Linux and Windows Reporter: Fritz Oconer Request feature that will enable a user to cancel the build of a particular project. Kinda like hitting ctrl c when maven is executed. There are times when a project is stuck indefinitely in in progress state (e.g. when running a broken testcase that executes indefinitely). This affects other projects because it has to wait for the previous one to finish. Restarting continuum is not much help because it just goes back to the original state or you cannot delete the project itself because delete link is disable. The only solution now is to redeploy continuum. Now, having a cancel button would definitely help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[maven2 build - FAILED - update] Wed Oct 26 10:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.10.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 10:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.101500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2][Proposal] J2EE builds best practices and conventions
-Original Message- From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: mardi 25 octobre 2005 00:46 To: Maven Developers List Subject: Re: [M2][Proposal] J2EE builds best practices and conventions [snip] Cool. I wonder if there could be synergies with Cargo... It seems there is potentially some overlap. Cargo could even possibly be used internally by Smartfrog to start/stop/deploy to containers as it already supports a big number of containers... The opposite could be true so that Cargo could have an EL for generating container configurations (ATM we have either a default config for which users can configure important parameters such as ports, log levels, security, etc) or a config provided by the user). If it works in a world of signed jars, then yes, we could use it. I'm not sure whether this affects Cargo or not. The only jars manipulated by Cargo are the J2EE modules (WAR, EAR, RAR, etc) that need to be copied/deployed into the containers and those are not created by Cargo so they're pretty transparent (one exception though: Cargo can do some introspection to look for container-specific deployment descriptor in those J2EE modules but that's optional). Another thing we like to add is liveness; that is every component supports a health check that can be triggered in a walk down the graph of deployed components. Some components do nothing but liveness, such as one that probes for a web page and fails if the response is out of range, the size too small or the content type wrong. Cool. This is useful. Cargo is not a monitoring tool. It's just a wrapper that provides a common Java API to configure, start, stop containers and deploy J2EE archives into them. So I guess it could be used by a higher level framework such as smartfrog for at least container start/stop. WRT the configuration, we have something very basic that I'd like to improve but as Cargo supports existing configuration too it should be easy to integrate with any tool that generates the config itself. In any case thanks for pointing out smartfrog. This gives me a new perspective. I'll need to understand it better but it gives me a new perspective for cargo to see how it fits into this ecosystem of J2EE management in general. I've started a wiki page on http://cargo.codehaus.org/Comparisons+with+other+tools?refresh=1 I'd be interested to get your feedback on it. [snip] Grab the latest release off the site -http://smartfrog.org/ . Start with the tutorial. I dont think we have any out the box demo apps, but maybe we should. Ok. I'll try to find some time to play with it... Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r328190 - /maven/components/trunk/maven-plugins/maven-checkstyle-plugin/pom.xml
On Tue, 25 Oct 2005, Brett Porter wrote: Kenney, Please revert this. It works in a clean environment, and we can't block development of this plugin until 2.0.1. I really couldn't even bootstrap m2 with this. M2 doesn't see that plexus:plexus-utils is the same as org.codehaus.plexus:plexus-utils, so they both end up in the classpath, and the plexus:plexus-utils one (1.0.2) is first. At worst, this should have added the exclusions to the reporting-impl dependency rather than updating the version as there is no code change. An exclusion might work though, but reporting-impl (using doxia that brings p-u in) might break with the exclusion because of the api-change (FileUtils.getDefaultExcludes() was moved). Btw, we're not blocking development, just a release of that plugin. All the other plugins also depend on the 2.0.1 version of reporting-impl so I didn't see it as a problem. There is a code change in the deps.. the plugin won't compile or run with svn-HEAD. All, Seriously consider before bumping up dependency versions. It means that it can't be released until 2.0.1. Certainly for metadata changes, we should at least use 2.0-1, 2.0-2 releases which can be done immediately. That's a good plan. How would we go about it in this case? If it does actually depend on 2.0.1 and will have to wait, please comment on why it was necessary and add the required prerequisites if it was a /lib dependency (not the case here). I'll run a clean bootstrap now (empty ~/.m2/repository/) and if it works I'll revert, but i spent hours to get it to work using excludes which didn't take then. Thanks, - Brett [EMAIL PROTECTED] wrote: Author: kenney Date: Mon Oct 24 16:31:22 2005 New Revision: 328190 URL: http://svn.apache.org/viewcvs?rev=328190view=rev Log: Bumped version for reporting-impl since that version correctly excludes plexus-utils. The group renaming adds both 1.0.2 (old groupId) and 1.0.4 (new groupId) to the compilation classpath, which makes this build fail. Modified: maven/components/trunk/maven-plugins/maven-checkstyle-plugin/pom.xml Modified: maven/components/trunk/maven-plugins/maven-checkstyle-plugin/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-checkstyle-plugin/pom.xml?rev=328190r1=328189r2=328190view=diff == --- maven/components/trunk/maven-plugins/maven-checkstyle-plugin/pom.xml (original) +++ maven/components/trunk/maven-plugins/maven-checkstyle-plugin/pom.xml Mon Oct 24 16:31:22 2005 @@ -51,7 +51,7 @@ dependency groupIdorg.apache.maven.reporting/groupId artifactIdmaven-reporting-impl/artifactId - version2.0/version + version2.0.1-SNAPSHOT/version /dependency dependency groupIdantlr/groupId @@ -68,4 +68,4 @@ version3.4/version /dependency /dependencies -/project \ No newline at end of file +/project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 10:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.103000.txt
[maven2 build - FAILED - update] Wed Oct 26 10:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.103000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 10:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.104500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: download report was: svn commit: r322514
Hi Brett, (Sorry for the delayed response) Putting the assembly report in project info reports is the logical way. To do this change, we need to change the visibility of some methods/attributes in the AssemblyMojo and AbstractUnpackingMojo classes (depending the package choose) Also, projectinfos plugins needs to have new deps. I ll try to do this shift ASAP, if, of course, everybody is ok. WDYT? Thanks. Cheers, Vincent 2005/10/23, Brett Porter [EMAIL PROTECTED]: Vincent Massol wrote: What does it do? Same as the download report in the m1 xdoc plugin? That's my understanding. It certainly doesn't go into the assembly plugin IMO. However it could possibly go in the release plugin or in the changes report or in the info plugin or ... I agree that it shouldn't be in assembly (nor release). I'd prefer to keep functional plugins separate from report plugins within reason (due to it requiring additional deps to be downloaded). For me, the project info report is the most natural home. IIRC there was an issue with obtaining the correct location of the download though. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 11:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.11.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 11:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.111500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 11:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.113000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 12:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.121500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 12:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.123000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 12:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.124500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 13:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.13.txt
[maven2 build - FAILED - update] Wed Oct 26 13:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.13.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1328) relative filesets incorrectly resolved when when used within reactor
relative filesets incorrectly resolved when when used within reactor Key: MNG-1328 URL: http://jira.codehaus.org/browse/MNG-1328 Project: Maven 2 Type: Bug Components: maven-assembly-plugin Versions: 2.0 Reporter: Jerome Lacoste Priority: Critical Attachments: MNG-_absolute_fileset_paths_work_in_reactor.diff When used within the reactor, relative filesets path are taken from the current root directory instead of the project's basedir. The attached patch solves the issue while keeping the old behavior (i.e. if we use absolute paths). It breaks the plugin if one was to use a path relative to the parent directory, but that was a broken set up anyway (would make the build fail when run from within the sub-module directory). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 13:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.131500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 13:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.133000.txt
[maven2 build - FAILED - update] Wed Oct 26 13:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.133000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1329) duplicate project references
duplicate project references Key: MNG-1329 URL: http://jira.codehaus.org/browse/MNG-1329 Project: Maven 2 Type: Bug Components: maven-eclipse-plugin Versions: 2.0 Reporter: Jorg Heymans eclipse:eclipse generates duplicate project references for following pom dependencies dependency groupIdapache-cocoon/groupId artifactIdcocoon-core/artifactId version2.2-SNAPSHOT/version /dependency dependency groupIdapache-cocoon/groupId artifactIdcocoon-core/artifactId version2.2-SNAPSHOT/version classifiertests/classifier /dependency The classifier should be taken into account. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] New Release managers for plugins
On Wed, 2005-10-26 at 07:48 +0200, Arnaud HERITIER wrote: If you are already a m2 plugins committer, you have the rights to commit on m1 plugins. I think that actually there are 2 groups of committers : - m1/m2 plugins committers only Plugin committers have access to plugins across the board. - m1/m2 plugins and core committers. And there's a group for the m1-core committers and m2-core committers. Jason are we agree ? Arnaud -Message d'origine- De : Stephane Nicoll [mailto:[EMAIL PROTECTED] Envoyé : mardi 25 octobre 2005 14:56 À : Maven Developers List Objet : Re: [m1] New Release managers for plugins Hi, I can take the following if necessary: - ear - idea - javacc - rar I am maven2 plugins committers ; I don't know If I have access to the M1 repository. Cheers, Stéphane On 10/25/05, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi guys (committers only), As we do it from time to time, I propose we change release managers for m1 plugins. Here is the current list of m1 plugins. Add your name beside each plugin you want to be the leader. Maven Abbot plugin Maven Announcement Plugin Maven Ant Plugin Maven Antlr Plugin Maven Artifact Plugin Maven AspectJ Plugin Maven Castor Plugin Maven Changelog Plugin Maven Changes Plugin Maven Checkstyle Plugin Maven Clean Plugin Maven Clover Plugin Maven Console Plugin Maven Cruise Control Plugin Maven Dashboard Plugin Maven Developer Activity Plugin Maven Distribution Plugin Maven EAR Plugin Maven Eclipse Plugin Maven EJB Plugin Maven FAQ Plug-in Maven File Activity Plug-in Maven Genapp Plugin Maven Gump Plug-in Maven Hibernate Plug-in Maven Html2XDoc Plug-in Maven IDEA Plug-in Maven J2EE Plugin Maven Jalopy Plugin Maven Jar Plug-in Maven Java Plug-in Maven Javacc Plugin Maven Javadoc Plug-in Maven JBoss plugin Maven JBuilder Plug-in Maven JCoverage plugin Maven JDepend Plugin Maven JDiff Plugin Maven JellyDoc Plug-in Maven Jetty plugin Maven JIRA Plug-in Maven JNLP Plug-in Maven JUnit Report Plug-in Maven JXR Plug-in Maven License Plug-in Maven LinkCheck Plug-in Maven MultiChanges plugin Maven Multi-Project Plug-in Maven Native Plug-in Maven NSIS Plug-in Maven PDF Plug-in Maven Plugin Plugin Maven PMD Plug-in Maven POM Plugin Maven RAR Plugin Maven Release Plug-in Maven Repository Plug-in Maven Source Control Management Plug-in Maven Simian Plugin Maven Site Plugin Maven Tasklist Plug-in Maven Test Plug-in Maven Uberjar Plugin Maven WAR Plugin Maven XDoc Plug-in Cheers. Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1330) direct support for mock classes
direct support for mock classes --- Key: MNG-1330 URL: http://jira.codehaus.org/browse/MNG-1330 Project: Maven 2 Type: New Feature Versions: 2.0 Reporter: Jorg Heymans a mockSourceDirectory element of some sort would allow projects to easily deal with mock classes. At the moment you would have to create a separate module myproject-mocks and include it as a dependency in your project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1331) dealing with licenses
dealing with licenses - Key: MNG-1331 URL: http://jira.codehaus.org/browse/MNG-1331 Project: Maven 2 Type: New Feature Versions: 2.0 Reporter: Jorg Heymans Priority: Minor maven could offer a configurable way to include project licenses in the jar, briefly discussed on IRC today jorgdoes m2 have anything built-in to deal with library licenses ? just wondering ... kenney license tag in the pom is all I think jorgah yep, i knew I saw something about it somewhere, tnx kenney kenney and just distribute poms for non-freely-distributable jars (like the sun ones), stating where you can download/purchase them jorgmmm Typically the licenses listed for the project are that of the project itself, and not of dependencies. jorgok so unless all our dependencies are good maven citizens this won't really work ... jorgno prob, we'll just include them ourselves then kenney do you have to? kenney if people distribute a jar/pom without a license, it's their fault jorgwell we (cocoon) have always done so jorgthat's true though , it's up to them to include them trygvis I think people are a bit slack when it comes to adding that information jorgdefinitely kenney what about the bundle upload system? jorgthat's why i was hoping for maven to be able enforce something trygvis we should probably start to enumerate the various licenses and give them IDs instead kenney bundles have to have a LICENSE file.. where does that go? trygvis not sure, ask carlos kenney yeah or maybe extend the license tag to name the license (ASL-2.0) and the online-url, or alternatively list the license content itself.. or just add a bla-X-LICENSE.txt on ibiblio per project jorgsomething like that yeah, and perhaps offering a configurable way of having the license file included in the jar ? jorgor is that a hairy legal thing maven shouldn't get into ? trygvis kenney: the name there (ASL-2.0) would be the id trygvis jorg: good idea jorgit would certainly advocate , albeit rather enforced, correct usage of libraries -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 13:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.134500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: my plugin is invoked okay directly but not at all as part of site.
On Wed, 2005-10-26 at 08:35 +0200, David Sag wrote:
I took the day off work yesterday as I was sick, and took the time to
check out all the maven-plugins stuff from SVN. Reading through the
code I 'discovered' reference to the AbstractMavenReport - something
that so far has not made its way into the documentation, and which
almost certainly explains why my QALabMojo (which only extends
AbstractMojo) is not working as a report :-)
I'll look further into this today. Is there any documentation I
should be reading? Any more hidden classes I should know about? Or
shoudl I just read the entire source code?
I'm still not quite sure how I tell the report which goal to run
however.
I've noted it for documentation, but as always the best way is to look
at an existing example.
Kind regards,
Dave Sag
Brett Porter [EMAIL PROTECTED] wrote on 24/10/2005 08:12:30 PM:
It's hard without a full POM to tell exactly what you are doing. Let
me
explain how this is processed.
Your Mojo should extend AbstractMavenReport, which enables it as
both a
report and a mojo.
When running as a mojo, configuration is used with first winning:
1) build plugin execution configuration
2) build plugin general configuration
3) reporting plugin general configuration
When running as a report, configuration is used with the first
winning:
1) reporting plugin individual report configuration
2) reporting plugin general configuration
So in general you configure the report in the reporting section,
adding
configuration only specific to build executions in the build
section.
Hope this helps.
- Brett
David Sag wrote:
still more on this.
if i move the configuration from out of the eexcutions and up into
the
main plugin thus:
plugin
groupIdcom.davesag/groupId
artifactIdqalab-plugin/artifactId
configuration
quietfalse/quiet
handlernet.objectlab.qalab.parser.CheckstyleStatMerge/handler
inputFile${project.build.directory}/target/checkstyle-result.
xml/inputFile
/configuration
executions
execution
goals
goalmerge/goal
/goals
/execution
/executions
/plugin
the configuration is recongnised okay. but that's no good for me
as i
need different configs for different goals.
Kind regards,
Dave Sag
David Sag [EMAIL PROTECTED] wrote on 24/10/2005 04:05:09 PM:
Even weirder -
the below is slightly wrong.
in my reporting block I must specify the plugin config again
thus:
plugin
groupIdcom.davesag/groupId
artifactIdqalab-plugin/artifactId
configuration
quietfalse/quiet
handlernet.objectlab.qalab.parser.CheckstyleStatMerge/handler
inputFile${project.build.directory}/target/checkstyle-
result.xml/inputFile
/configuration
/plugin
or maven claims that i have not specified any parameters.
i still get nothing generated if i run mvn site however
if i remove the entire reporting block i get the same error, as
if i
had not configured it.
so can someone please explain what the sotry is with plugin
configuration? it seems you must configure plugins both in the
build section AND the reporting section for anything to work.
similarly for the javadoc plugin, as of the latest change, i
must
now specify source = 1.4 in both the rewporting configuration
of the
plugin, AND the build configuration of the plugin.
am i just hopelessly confused?
Kind regards,
Dave Sag
[image removed]
David Sag [EMAIL PROTECTED] wrote on 24/10/2005 03:55:25 PM:
Dear People,
My mojo is built and installed.
I have specified the goal and phase thus:
* @goal merge
* @phase validate
I have added a reference to the build block of a shell
project thus:
plugin
groupIdcom.davesag/groupId
artifactIdqalab-plugin/artifactId
executions
execution
idqalab-blah/id
phasevalidate/phase
configuration
quietfalse/quiet
handlernet.objectlab.qalab.parser.
CheckstyleStatMerge/handler
inputFile${project.build.directory}
/target/checkstyle-result.xml/inputFile
/configuration
goals
goalmerge/goal
/goals
/execution
/executions
/plugin
when i type
mvn qalab:merge
i get an error telling me it can't read from the checkstyle
results
file. this
[continuum build - FAILED - update] Wed Oct 26 14:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.14.txt
[jira] Commented: (MEV-150) jMock 1.0.1 POM has /dependecy instead of /dependency
[ http://jira.codehaus.org/browse/MEV-150?page=comments#action_49294 ] Mark Hobson commented on MEV-150: - This is also true of jmock-cglib too. jMock 1.0.1 POM has /dependecy instead of /dependency - Key: MEV-150 URL: http://jira.codehaus.org/browse/MEV-150 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: David Jackman -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 14:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.14.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Continuum 1.0 Final released
The Maven team is pleased to announce the 1.0 of Continuum. Continuum is a continous integration server. We have progressively improved Continuum over five previous releases and now provides the following features: * Support for Maven 2.x * Support for Maven 1.x * Support for Ant * Support for shell scripts * Tight integration with Maven SCM * Subversion * CVS * Starteam * Easy to use web-based setup and interface * XML-RPC and SOAP interfaces for integration, automation and remoting * Mail Notification * IM notification * IRC * Jabber * MSN * Blame Mechanism For a complete list of changes please refer to the complete changelog: http://maven.apache.org/continuum/change-log.html To get started with Continuum take a look at the download and install instructions: http://maven.apache.org/continuum/download.html And then take a look at our getting started guide: http://maven.apache.org/continuum/guides/getting-started/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 14:30:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.143001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Wed Oct 26 15:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051026.15.txt
[jira] Commented: (MNG-1327) Clover default target percentage too high - should be 0%
[ http://jira.codehaus.org/browse/MNG-1327?page=comments#action_49300 ] Vincent Massol commented on MNG-1327: - Hi Mark, Have you realized that this parameter is only used by clover:check mojo? If you're doing checks it cannot be 0% as it wouldn't mean anything. I don't understand why it is a problem for you and I certainly won't encourage a default where 0% test coverage will pass a build verified by clover:check :-) When you run the site goal the check is not performed of course! Have you tried using the plugin? I think there's a misundestanding in how it is used (no wonder as there's still no doc yet ;-) I'm working on that but please bear in mind the plugin is not released yet). Thanks Clover default target percentage too high - should be 0% Key: MNG-1327 URL: http://jira.codehaus.org/browse/MNG-1327 Project: Maven 2 Type: Bug Components: maven-clover-plugin Versions: 2.0 Reporter: Mark Kuzmycz Priority: Trivial The target percentage attribute is a good idea. However, it should be treated as optional as most projects will want to build irrespective of the target. This is especially true when you run the site goal. In which case you want the execution to complete (irrespective of clover restrictions) so that you can communicate the results to the developers. Can we please have the default value set to 0% -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 15:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.15.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 15:30:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.153001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 16:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.16.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 16:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.161500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 16:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.163000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Oct 26 16:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051026.164500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1450) jsl:template Property 'match' has no write method
[ http://jira.codehaus.org/browse/MAVEN-1450?page=comments#action_49307 ] Norman Jarvis commented on MAVEN-1450: -- This is still an issue in Maven 1.1-beta-2. Is this going to be fixed in the final Maven 1.1 release? jsl:template Property 'match' has no write method - Key: MAVEN-1450 URL: http://jira.codehaus.org/browse/MAVEN-1450 Project: Maven Type: Bug Reporter: Nicolas Chalumeau Assignee: Brett Porter Attachments: info.txt classpath issue. Please post this to JIRA with maven --info output. - Brett On Wed, 22 Sep 2004 10:12:13 +0200, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I use cc 2.1.6 with the the 1.5 plugin. It seem I have a probleme with the jsl:template tag. I try by setting the properties maven.cruisecontrol.template=cruisecontrol or use it with the default value but there is no change allways the same message. I probally forgot to set some properties or don't set them with correct value. [EMAIL PROTECTED] ...maven-struts-module-plugin/]$ maven cruisecontrol:configure __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 build:start: scm:parse-connection: [echo] Using connection: scm:cvs:pserver:[EMAIL PROTECTED]:/usr/ngasi/contexts/codeczar/cvs:maven-struts-module-plugin Using SCM method: cvs Using CVSROOT: :pserver:[EMAIL PROTECTED]:/usr/ngasi/contexts/codeczar/cvs Using module: maven-struts-module-plugin BUILD FAILED File.. C:\Documents and Settings\PropriÚtaire\.maven\cache\maven-cruisecontrol-plugin-1.5\plugin.jelly Element... j:include Line.. 72 Column 51 file:C:/Documents and Settings/PropriÚtaire/.maven/cache/maven-cruisecontrol-plugin-1.5/plugin-resources/cruisecontrol.jsl:30:52: jsl:template Property 'match' has no write method Total time: 4 seconds Finished at: Wed Sep 22 20:56:03 GMT+01:00 2004 I'm not on the same environment actually so I will add later the --info output. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (ARCHETYPE-1) cannot create project based on archetype that is not in cetral repository
[ http://jira.codehaus.org/browse/ARCHETYPE-1?page=all ] Jason van Zyl moved MNG-1252 to ARCHETYPE-1: Assign To: (was: Jason van Zyl) Version: (was: 2.0 (RC)) Component: (was: maven-archetype-plugin) Complexity: (was: Intermediate) Workflow: jira (was: Maven) Key: ARCHETYPE-1 (was: MNG-1252) Project: Maven Archetype (was: Maven 2) cannot create project based on archetype that is not in cetral repository - Key: ARCHETYPE-1 URL: http://jira.codehaus.org/browse/ARCHETYPE-1 Project: Maven Archetype Type: Bug Reporter: Milos Kleint Priority: Critical Attachments: settings.xml it's not possible to create an archetype based on a template from non-default repository. the archetype's artifact never gets downloaded. I tried to create a project based on archetype from mevenide.codehaus.org/m2-repository (the repository is listed in the settings.xml file - the file is attached) the command line looks like this: m2 archetype:create -DgroupId=com.mycompany -DartifactId=myapp -DarchetypeGroupId=org.codehaus.mevenide.plugins -DarchetypeArtifactId=maven-archetype-nbm -DarchetypeVersion=1.0 The artifact is there: http://mevenide.codehaus.org/m2-repository/org/codehaus/mevenide/plugins/maven-archetype-nbm/ but the repository never gets contacted. here is the output of the command: THE m2 COMMMAND IS DEPRECATED - PLEASE RUN mvn INSTEAD [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] ** [INFO] Starting Jakarta Velocity v1.4 [INFO] RuntimeInstance initializing. [INFO] Default Properties File: org/apache/velocity/runtime/defaults/velocity.properties [INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl) [INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader [INFO] ClasspathResourceLoader : initialization starting. [INFO] ClasspathResourceLoader : initialization complete. [INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource.ResourceCacheImpl) [INFO] Default ResourceManager initialization complete. [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [INFO] Created: 20 parsers. [INFO] Velocimacro : initialization starting. [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in anyresource loader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm' [INFO] Velocimacro : VM library template macro registration complete. [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOTreplace previous VM definitions [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed. [INFO] Velocimacro : messages on : VM system will output logging messages [INFO] Velocimacro : autoload off : VM system will not automatically reload global library macros [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [archetype:create] [INFO] Defaulting package to group ID: com.mycompany Downloading: http://repo1.maven.org/maven2/org/codehaus/mevenide/plugins/maven-archetype-nbm/1.0/maven-archetype-nbm-1.0.jar [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.codehaus.mevenide.plugins
[jira] Moved: (ARCHETYPE-3) binary resources
[ http://jira.codehaus.org/browse/ARCHETYPE-3?page=all ] Jason van Zyl moved MNG-1234 to ARCHETYPE-3: Version: (was: 2.0 (RC)) Component: (was: maven-archetype-plugin) Complexity: (was: Intermediate) Workflow: jira (was: Maven) Key: ARCHETYPE-3 (was: MNG-1234) Project: Maven Archetype (was: Maven 2) binary resources Key: ARCHETYPE-3 URL: http://jira.codehaus.org/browse/ARCHETYPE-3 Project: Maven Archetype Type: Bug Environment: xp Reporter: Jorg Heymans As described here http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28710 , the archetype plugin fails to recognize binary files from text files for template substitution. [ERROR] ResourceManager.getResource() parse exception: org.apache.velocity.exception.ParseErrorException: Lexical error: org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 44, column 36. Encountered: EOF after : Is defining binary resources disallowed ? I can upload the created archetype if necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (ARCHETYPE-2) complete templates
[ http://jira.codehaus.org/browse/ARCHETYPE-2?page=all ] Jason van Zyl moved MNG-960 to ARCHETYPE-2: --- Component: (was: maven-archetype-plugin) Complexity: (was: Intermediate) Workflow: jira (was: Maven) Key: ARCHETYPE-2 (was: MNG-960) Project: Maven Archetype (was: Maven 2) complete templates -- Key: ARCHETYPE-2 URL: http://jira.codehaus.org/browse/ARCHETYPE-2 Project: Maven Archetype Type: Improvement Reporter: Brett Porter finish the existing templates, and ensure there are templates for: - maven plugin - multiproject - ear - ejb - rar - site (or is this added to the others?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (ARCHETYPE-4) Add input validation
[ http://jira.codehaus.org/browse/ARCHETYPE-4?page=all ] Jason van Zyl moved MNG-1312 to ARCHETYPE-4: Version: (was: 2.0) Component: (was: maven-archetype-plugin) Complexity: (was: Novice) Workflow: jira (was: Maven) Key: ARCHETYPE-4 (was: MNG-1312) Project: Maven Archetype (was: Maven 2) Add input validation Key: ARCHETYPE-4 URL: http://jira.codehaus.org/browse/ARCHETYPE-4 Project: Maven Archetype Type: Bug Environment: WinXP SP2, JDK 1.5.0_05 Reporter: Jon Ekdahl Priority: Minor Add input verification and proper error message(s) in the case of invalid input. The command mvn archetype:create -DgroupId=my-group -DarchetypeId=my-app creates an application with a generated App.java file that starts with the line: package my-group; my-group is not a valid package definition, so the code won't compile (mvn compile fails). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
