[jira] Created: (MAVENUPLOAD-1001) Stopwatch
Stopwatch - Key: MAVENUPLOAD-1001 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1001 Project: maven-upload-requests Issue Type: Task Reporter: Milen Dyankov Attachments: stopwatch-0.3-bundle.jar http://prdownloads.sourceforge.net/jstopwatch/stopwatch-0.3.jar?download http://jstopwatch.sourceforge.net http://jstopwatch.sourceforge.net/team-list.html Stopwatch is a free, simple, highly extensible, Java API that allows developers to easily monitor whole application or any part of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MWAR-62) The comma separated list of tokens doesn't work with the property .
The comma separated list of tokens doesn't work with the property . -- Key: MWAR-62 URL: http://jira.codehaus.org/browse/MWAR-62 Project: Maven 2.x War Plugin Issue Type: Bug Environment: windows XP Reporter: Alexandre Vivien The comma separated list of tokens doesn't work with the property . It doesn't understand it, this property only work with one token. example : This configuration doesn't exclude the file mail_config.propertires.dev and the file mail_config.propertires.prod from the web directory. org.apache.maven.plugins maven-war-plugin web **/*.dev,**/*.prod but the configuration below exclude the file mail_config.propertires.dev org.apache.maven.plugins maven-war-plugin web **/*.dev -- 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] Commented: (MJAR-50) "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab char in pom Description
[ http://jira.codehaus.org/browse/MJAR-50?page=comments#action_70339 ]
Mike Laurie commented on MJAR-50:
-
Wow - thanks Mike; you've been busy!
It's good to know the "more than once in the same section" error is already
fixed in archiver 2.2.
The only thing causing this MJAR issue now seems to be the _possibility_ of
including \r and \n characters in manifest header fields. While we're at it, I
guess that NUL characters also ought to be quashed since they're the only other
invalid attribute chars according to the sun spec. I think these characters
should be replaced with spaces as a matter of course.
Last question: Does the archiver-plugin take responsibility for this, or should
plexus change their jar.Manifest class to replace them? I think plexus should
be changed anyway, since it currently allows invalid jar manifests to be
created. However, is it worth changing the archiver-plugin to fix the problem
now, since it's an easy fix and there needs to be a release soon anyway?
> "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab
> char in pom Description
> ---
>
> Key: MJAR-50
> URL: http://jira.codehaus.org/browse/MJAR-50
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Mike Laurie
>Priority: Trivial
>
> I typed a element into my pom; the description spanned 2 lines,
> and my text editor put a tab char at the beginning of the 2nd line.
> The project built correctly, but another project depended on the resulting
> jar.
> The compilation of the depending project failed with "invalid header" on the
> jar I'd just compiled.
> When I looked at the jar's manifest, I saw the Specification-Title attribute
> had the tab character still in it from the element.
> Replacing the tab with spaces in the pom solved the problem.
> However, this was valid xml that caused a compilation problem, so I think
> it's a minor bug with the jar production code.
> Note that the full description is trimmed before going into the manifest, so
> any
> Easy to work around, but it would be nice if whitespace in the
> element were consolidated into spaces before copying to the manifest.
> Doesn't need any fancy layout stuff - just any multiple instances of tabs,
> spaces, lf or cr should be replaced by a single space.
> Try (I haven't tried to compile this!):
> {code}
> public String consolidateWhitespace(String input){
> StringTokenizer st = new StringTokenizer(input);
> StringBuffer rv = new StringBuffer();
> while (st.hasMoreTokens()){
> rv.append(st.nextToken() + (st.hasMoreTokens()?" ":""));
> }
> return rv.toString();
> }
> {code}
--
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] Commented: (MJAR-50) "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab char in pom Description
[ http://jira.codehaus.org/browse/MJAR-50?page=comments#action_70342 ]
Mike Laurie commented on MJAR-50:
-
Plexus are aware of this issue and it will get fixed there (PLX-185).
I guess this issue doesn't need any more attention, so despite the fact that
it's not actually fixed and released yet, I'm confident it's being addressed
elsewhere.
I'd be happy to close it.
> "Invalid Header" in jar's Manifest (Specification-Title attribute) when tab
> char in pom Description
> ---
>
> Key: MJAR-50
> URL: http://jira.codehaus.org/browse/MJAR-50
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Mike Laurie
>Priority: Trivial
>
> I typed a element into my pom; the description spanned 2 lines,
> and my text editor put a tab char at the beginning of the 2nd line.
> The project built correctly, but another project depended on the resulting
> jar.
> The compilation of the depending project failed with "invalid header" on the
> jar I'd just compiled.
> When I looked at the jar's manifest, I saw the Specification-Title attribute
> had the tab character still in it from the element.
> Replacing the tab with spaces in the pom solved the problem.
> However, this was valid xml that caused a compilation problem, so I think
> it's a minor bug with the jar production code.
> Note that the full description is trimmed before going into the manifest, so
> any
> Easy to work around, but it would be nice if whitespace in the
> element were consolidated into spaces before copying to the manifest.
> Doesn't need any fancy layout stuff - just any multiple instances of tabs,
> spaces, lf or cr should be replaced by a single space.
> Try (I haven't tried to compile this!):
> {code}
> public String consolidateWhitespace(String input){
> StringTokenizer st = new StringTokenizer(input);
> StringBuffer rv = new StringBuffer();
> while (st.hasMoreTokens()){
> rv.append(st.nextToken() + (st.hasMoreTokens()?" ":""));
> }
> return rv.toString();
> }
> {code}
--
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] Commented: (ARCHETYPE-36) j2ee-simple archetype causes error
[ http://jira.codehaus.org/browse/ARCHETYPE-36?page=comments#action_70343 ]
Franz Allan Valencia See commented on ARCHETYPE-36:
---
Good day,
I checked out the current version of maven-archetype-j2ee-simple and the
"offending references" of the archetype.xml were still there. I've also tried
using the command posted in the description and it also failed (as well as my
other tries to use it).
However, I created a patch to fix the problem. May I request that this issue be
reopened so that I can attach the patch.
Thanks a bunch
-Franz
> j2ee-simple archetype causes error
> --
>
> Key: ARCHETYPE-36
> URL: http://jira.codehaus.org/browse/ARCHETYPE-36
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 1.0-alpha-4
>Reporter: Alex Mayorga Adame
> Assigned To: Jesse McConnell
>
> Something seems to be missing inside the archetype.
> Here's the stack trace for what is worth:
> {code:none}
> bash-2.03$ mvn archetype:create -DgroupId=com.mycompany.app
> -DartifactId=j2ee-simple -DarchetypeArtifactId=maven-archetype-j2ee-simple -e
> + Error stacktraces are turned on.
> [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: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [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
> any resource 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
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [archetype:create]
> [INFO] Defaulting package to group ID: com.mycompany.app
> [INFO]
>
> [INFO] Using following parameters for creating Archetype:
> maven-archetype-j2ee-simple:RELEASE
> [INFO]
>
> [INFO] Parameter: groupId, Value: com.mycompany.app
> [INFO] Parameter: packageName, Value: com.mycompany.app
> [INFO] Parameter: basedir, Value: /export1/eae/am74839/demos
> [INFO] Parameter: package, Value: com.mycompany.app
> [INFO] Parameter: version, Value: 1.0-SNAPSHOT
> [INFO] Parameter: artifactId, Value: j2ee-simple
> [INFO] * End of debug info from resources from generated
> POM ***
> [ERROR] ResourceManager : unable to find resource
> 'archetype-resources/site/pom.xml' in any resource loader.
>
[jira] Reopened: (ARCHETYPE-36) j2ee-simple archetype causes error
[ http://jira.codehaus.org/browse/ARCHETYPE-36?page=all ]
Allan Ramirez reopened ARCHETYPE-36:
Assignee: Allan Ramirez (was: Jesse McConnell)
confirmed
> j2ee-simple archetype causes error
> --
>
> Key: ARCHETYPE-36
> URL: http://jira.codehaus.org/browse/ARCHETYPE-36
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 1.0-alpha-4
>Reporter: Alex Mayorga Adame
> Assigned To: Allan Ramirez
>
> Something seems to be missing inside the archetype.
> Here's the stack trace for what is worth:
> {code:none}
> bash-2.03$ mvn archetype:create -DgroupId=com.mycompany.app
> -DartifactId=j2ee-simple -DarchetypeArtifactId=maven-archetype-j2ee-simple -e
> + Error stacktraces are turned on.
> [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: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [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
> any resource 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
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [archetype:create]
> [INFO] Defaulting package to group ID: com.mycompany.app
> [INFO]
>
> [INFO] Using following parameters for creating Archetype:
> maven-archetype-j2ee-simple:RELEASE
> [INFO]
>
> [INFO] Parameter: groupId, Value: com.mycompany.app
> [INFO] Parameter: packageName, Value: com.mycompany.app
> [INFO] Parameter: basedir, Value: /export1/eae/am74839/demos
> [INFO] Parameter: package, Value: com.mycompany.app
> [INFO] Parameter: version, Value: 1.0-SNAPSHOT
> [INFO] Parameter: artifactId, Value: j2ee-simple
> [INFO] * End of debug info from resources from generated
> POM ***
> [ERROR] ResourceManager : unable to find resource
> 'archetype-resources/site/pom.xml' in any resource loader.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error creating from archetype
> Embedded error: Error merging velocity templates
> Unable to find resource 'archetype-resources/site/pom.xml'
> [INFO]
>
[jira] Updated: (MASSEMBLY-122) Apply docck rules to the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-122?page=all ] Edwin Punzalan updated MASSEMBLY-122: - Due Date: 24/Jul/06 (was: 21/Jul/06) > Apply docck rules to the assembly plugin > > > Key: MASSEMBLY-122 > URL: http://jira.codehaus.org/browse/MASSEMBLY-122 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan > Original Estimate: 1 day, 9 hours > Time Spent: 14 hours > Remaining Estimate: 19 hours > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ARCHETYPE-36) j2ee-simple archetype causes error
[ http://jira.codehaus.org/browse/ARCHETYPE-36?page=all ]
Franz Allan Valencia See updated ARCHETYPE-36:
--
Attachment: ARCHETYPE-36-maven-archetype-parent.patch
In
maven-archetype\maven-archetype-plugin\src\main\java\org\apache\maven\plugin\archetype\MavenArchetypeMojo.java
changed the default-value of the archetypeGroupId from
"org.apache.maven.archetypes" to "org.apache.maven.archetype"
In
maven-archetype-bundles\maven-archetype-j2ee-simple\src\main\resources\META-INF\archetype.xml
removed the following lines:
site/pom.xml
site/src/site/site.xml
site/src/site/apt/site.apt
which Jesse McConnell mentioned as the solution.
> j2ee-simple archetype causes error
> --
>
> Key: ARCHETYPE-36
> URL: http://jira.codehaus.org/browse/ARCHETYPE-36
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 1.0-alpha-4
>Reporter: Alex Mayorga Adame
> Assigned To: Allan Ramirez
> Attachments: ARCHETYPE-36-maven-archetype-parent.patch
>
>
> Something seems to be missing inside the archetype.
> Here's the stack trace for what is worth:
> {code:none}
> bash-2.03$ mvn archetype:create -DgroupId=com.mycompany.app
> -DartifactId=j2ee-simple -DarchetypeArtifactId=maven-archetype-j2ee-simple -e
> + Error stacktraces are turned on.
> [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: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [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
> any resource 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
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [archetype:create]
> [INFO] Defaulting package to group ID: com.mycompany.app
> [INFO]
>
> [INFO] Using following parameters for creating Archetype:
> maven-archetype-j2ee-simple:RELEASE
> [INFO]
>
> [INFO] Parameter: groupId, Value: com.mycompany.app
> [INFO] Parameter: packageName, Value: com.mycompany.app
> [INFO] Parameter: basedir, Value: /export1/eae/am74839/demos
> [INFO] Parameter: package, Value: com.mycompany.app
> [INFO] Parameter: version, Value: 1.0-SNAPSHOT
> [INFO] Parameter: artifactId, Value: j2ee-simple
> [INFO] * End of debug info from resources from generated
> POM
[jira] Closed: (ARCHETYPE-36) j2ee-simple archetype causes error
[ http://jira.codehaus.org/browse/ARCHETYPE-36?page=all ]
Allan Ramirez closed ARCHETYPE-36.
--
Resolution: Fixed
Patch applied. Thanks
> j2ee-simple archetype causes error
> --
>
> Key: ARCHETYPE-36
> URL: http://jira.codehaus.org/browse/ARCHETYPE-36
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 1.0-alpha-4
>Reporter: Alex Mayorga Adame
> Assigned To: Allan Ramirez
> Attachments: ARCHETYPE-36-maven-archetype-parent.patch
>
>
> Something seems to be missing inside the archetype.
> Here's the stack trace for what is worth:
> {code:none}
> bash-2.03$ mvn archetype:create -DgroupId=com.mycompany.app
> -DartifactId=j2ee-simple -DarchetypeArtifactId=maven-archetype-j2ee-simple -e
> + Error stacktraces are turned on.
> [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: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [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
> any resource 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
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [archetype:create]
> [INFO] Defaulting package to group ID: com.mycompany.app
> [INFO]
>
> [INFO] Using following parameters for creating Archetype:
> maven-archetype-j2ee-simple:RELEASE
> [INFO]
>
> [INFO] Parameter: groupId, Value: com.mycompany.app
> [INFO] Parameter: packageName, Value: com.mycompany.app
> [INFO] Parameter: basedir, Value: /export1/eae/am74839/demos
> [INFO] Parameter: package, Value: com.mycompany.app
> [INFO] Parameter: version, Value: 1.0-SNAPSHOT
> [INFO] Parameter: artifactId, Value: j2ee-simple
> [INFO] * End of debug info from resources from generated
> POM ***
> [ERROR] ResourceManager : unable to find resource
> 'archetype-resources/site/pom.xml' in any resource loader.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error creating from archetype
> Embedded error: Error merging velocity templates
> Unable to find resource 'archetype-resources/site/pom.xml'
> [INFO]
> --
[jira] Created: (MPWAR-62) maven-war-plugin doesn't compile java sources when used with maven-test-plugin 1.8
maven-war-plugin doesn't compile java sources when used with maven-test-plugin 1.8 --- Key: MPWAR-62 URL: http://jira.codehaus.org/browse/MPWAR-62 Project: maven-war-plugin Issue Type: Bug Affects Versions: 1.6.2 Reporter: nicolas de loof I've found an issue when using latest versions of maven-test-plugin (1.8) : when maven.test.skip=true is set, the goal is not executed. This sounds good, BUT the maven-war-plugin use "test:test" goal to attain the "java:compile" goal, so the generated war has no classes ! The war:resources plugin should have prereqs="war:war-resources,*java:compile*,test:test". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPWAR-62) maven-war-plugin doesn't compile java sources when used with maven-test-plugin 1.8
[ http://jira.codehaus.org/browse/MPWAR-62?page=all ] nicolas de loof updated MPWAR-62: - Attachment: MPWAR-62.patch patch on plugin.jelly to add a prereq for "java:compile" to "war:webapp" goal. This has as a side effect that java:compile is run twice when tests are enabled > maven-war-plugin doesn't compile java sources when used with > maven-test-plugin 1.8 > --- > > Key: MPWAR-62 > URL: http://jira.codehaus.org/browse/MPWAR-62 > Project: maven-war-plugin > Issue Type: Bug >Affects Versions: 1.6.2 >Reporter: nicolas de loof > Attachments: MPWAR-62.patch > > > I've found an issue when using latest versions of maven-test-plugin (1.8) : > when maven.test.skip=true is set, the goal is not executed. > This sounds good, BUT the maven-war-plugin use "test:test" goal to attain the > "java:compile" goal, so the generated war has no classes ! > The war:resources plugin should have > prereqs="war:war-resources,*java:compile*,test:test". -- 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] Commented: (MAVENUPLOAD-982) Relocate jWebUnit and upload 1.3-rc2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-982?page=comments#action_70353 ] Julien HENRY commented on MAVENUPLOAD-982: -- The deploy was done in http://jwebunit.sourceforge.net/m2-repo. You can sync. Thanks. > Relocate jWebUnit and upload 1.3-rc2 > > > Key: MAVENUPLOAD-982 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-982 > Project: maven-upload-requests > Issue Type: Task >Reporter: Julien HENRY > > As I didn't manage to create an upload bundle for a multi-module project, I > deployed jWebUnit in a private repository. > Please upload the parent pom: > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit > And only the following modules: > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit-core/ > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit-htmlunit-plugin/ > I don't know if you should upload the last module (jwebunit-commons-tests), > as it is only used to run tests. > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPTEST-66) 1.8 version introduces bug in other plugins
[ http://jira.codehaus.org/browse/MPTEST-66?page=all ] nicolas de loof updated MPTEST-66: -- Attachment: MPTEST-66.patch Patch to attach java:compile as a test:test prereqs this patch also solves MPWAR-62 > 1.8 version introduces bug in other plugins > --- > > Key: MPTEST-66 > URL: http://jira.codehaus.org/browse/MPTEST-66 > Project: maven-test-plugin > Issue Type: Bug >Affects Versions: 1.8 >Reporter: nicolas de loof > Attachments: MPTEST-66.patch > > > When maven-war-plugin is run with maven.test.skip=true, the sources are not > compiled. > Latest version of test-plugin has removed prereqs on java:compile & > java:jar-resources. > Assuming other plugins themself run the java:compile goal may have impact on > lots of plugin and can break many application builds. I think the "test:test" > goal may have a prereqs="java:compile,java:jar-resources", and the > "test:compile" goal only prereqs="test:prepare-filesystem,test:test-resources" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPTEST-66) 1.8 version introduces bug in other plugins
1.8 version introduces bug in other plugins --- Key: MPTEST-66 URL: http://jira.codehaus.org/browse/MPTEST-66 Project: maven-test-plugin Issue Type: Bug Affects Versions: 1.8 Reporter: nicolas de loof Attachments: MPTEST-66.patch When maven-war-plugin is run with maven.test.skip=true, the sources are not compiled. Latest version of test-plugin has removed prereqs on java:compile & java:jar-resources. Assuming other plugins themself run the java:compile goal may have impact on lots of plugin and can break many application builds. I think the "test:test" goal may have a prereqs="java:compile,java:jar-resources", and the "test:compile" goal only prereqs="test:prepare-filesystem,test:test-resources" -- 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] Commented: (MPWAR-62) maven-war-plugin doesn't compile java sources when used with maven-test-plugin 1.8
[ http://jira.codehaus.org/browse/MPWAR-62?page=comments#action_70355 ] nicolas de loof commented on MPWAR-62: -- This issue can be considered a duplicated of MPTEST-66 as the problem seems to be better solved in the test plugin > maven-war-plugin doesn't compile java sources when used with > maven-test-plugin 1.8 > --- > > Key: MPWAR-62 > URL: http://jira.codehaus.org/browse/MPWAR-62 > Project: maven-war-plugin > Issue Type: Bug >Affects Versions: 1.6.2 >Reporter: nicolas de loof > Attachments: MPWAR-62.patch > > > I've found an issue when using latest versions of maven-test-plugin (1.8) : > when maven.test.skip=true is set, the goal is not executed. > This sounds good, BUT the maven-war-plugin use "test:test" goal to attain the > "java:compile" goal, so the generated war has no classes ! > The war:resources plugin should have > prereqs="war:war-resources,*java:compile*,test:test". -- 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] Commented: (MPTEST-46) Do not execute test:test-resources unless tests will be run
[ http://jira.codehaus.org/browse/MPTEST-46?page=comments#action_70356 ] nicolas de loof commented on MPTEST-46: --- Current solution introduces MPTEST-66. Other plugin expect test plugin to attain java:compile. The prereqs in test:* goals should be splited to allways invoque java:compile, and skip test:compile is skip=true > Do not execute test:test-resources unless tests will be run > --- > > Key: MPTEST-46 > URL: http://jira.codehaus.org/browse/MPTEST-46 > Project: maven-test-plugin > Issue Type: Improvement >Reporter: thierry lach > Assigned To: Lukas Theussl >Priority: Minor > Fix For: 1.8 > > > If maven.test.skip is set (or if there are no unit tests), there should be no > need to execute test:test-resources. > This allows putting preGoals and postGoals against test:test-resources which > may be very time-consuming (such as database loads), and these other goals > would not be executed if the tests are not run. -- 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] Commented: (MNGECLIPSE-115) add functionality to manage dependencies
[ http://jira.codehaus.org/browse/MNGECLIPSE-115?page=comments#action_70362 ] Ovidio Mallo commented on MNGECLIPSE-115: - Hi, I have been thinking about how one could implement such a dependency manager. I think it would be nice to display the dependencies in a tree which contains the XML elements of a dependency as child nodes which can be edited in place. That way, you could even represent the element of a dependency by inserting a subtree with checkboxes for the transitive dependencies. However, it seems as if Eclipse does not support having different kinds of CellEditors for the same column in a tree. This would be necessary to edit some tree nodes in Text fields (e.g. the version of the dependency) while the transitive dependencies would be edited by a checkbox. Does anyone know whether this can somehow be achieved. Or are there any other suggestions as of how to implement this feature? Maybe just with plain Dialogs to type in the dependency information... > add functionality to manage dependencies > > > Key: MNGECLIPSE-115 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-115 > Project: Maven 2.x Extension for Eclipse > Issue Type: Improvement >Affects Versions: 0.0.6 >Reporter: Ovidio Mallo > Assigned To: Eugene Kuleshov > > Maybe the current functionality to add dependencies to a maven project could > be extended by > some "Manage dependencies" capability which would list the current > dependencies and allow for > the following operations to be performed: > - add some dependency (as is done currently) > - remove some dependency > - add 3rd party dependencies from the local drive (see mvn > install:install-file) > - edit some dependency (change the version, scope, ...) > Such an interface would thereby allow to manage the maven dependencies > without having > to directly edit the POM file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2459) Problem parsing XML in code run using antrun plugin
[ http://jira.codehaus.org/browse/MNG-2459?page=all ] Carlos Sanchez closed MNG-2459. --- Assignee: Carlos Sanchez Resolution: Won't Fix You probably need to make java task to fork the jvm, see ant documentation. In any case this is not a maven bug. > Problem parsing XML in code run using antrun plugin > --- > > Key: MNG-2459 > URL: http://jira.codehaus.org/browse/MNG-2459 > Project: Maven 2 > Issue Type: Bug > Components: Ant tasks >Affects Versions: 2.0.4 > Environment: Red Hat Enterprise Linux WS release 4 (Nahant Update 3) > java version "1.5.0_06" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) > Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing) >Reporter: Kris Nuttycombe > Assigned To: Carlos Sanchez > Attachments: antrun-log4j-xml-test.tgz > > > I'm not certain whether this is an antrun problem or a log4j problem, but > considering that the same application run from the command line has no > problems, I'm going to point to antrun as the first possible culprit. > This error occurs when I attempt to use the antrun plugin to run a standalone > Java program that is, for deployment, packaged as a jar-with-dependencies jar > using the assembly plugin. I use antrun during development for the purpose of > giving me the benefit of the classpath information from the POM; if there's a > better way of doing this I'd be happy to work around the problem. > The error appears to occur when log4j attempts to parse an XML configuration > file using the DOMConfigurator. It appears that the DocumentBuilderFactory > package name is being prepended with "com.sun." when the application is run > using the antrun plugin. Is there some aspect of Maven or of the antrun > plugin that is altering the XML parsing environment? > [java] javax.xml.parsers.FactoryConfigurationError: Provider > com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl could not > be instantiated: java.lang.NullPointerException > [java] at > org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180) > [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:710) > [java] at > org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178) > [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84) > [java] at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > [java] at org.apache.tools.ant.Task.perform(Task.java:364) > [java] at org.apache.tools.ant.Target.execute(Target.java:341) > [java] at > org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108) > [java] at > org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83) > [java] at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > [java] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > [java] at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > [java] at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > [java] at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [java] Caused by: javax.xml.parsers.FactoryConfigurationError: Provider > com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl could not > be instantiated: java.lang.NullPointer
[jira] Closed: (MAVENUPLOAD-982) Relocate jWebUnit and upload 1.3-rc2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-982?page=all ] Carlos Sanchez closed MAVENUPLOAD-982. -- Assignee: Carlos Sanchez Resolution: Fixed Synced from there, next times you just need to deploy there and ping us to sync. Relocation poms were not present, so they were not added to ibiblio > Relocate jWebUnit and upload 1.3-rc2 > > > Key: MAVENUPLOAD-982 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-982 > Project: maven-upload-requests > Issue Type: Task >Reporter: Julien HENRY > Assigned To: Carlos Sanchez > > As I didn't manage to create an upload bundle for a multi-module project, I > deployed jWebUnit in a private repository. > Please upload the parent pom: > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit > And only the following modules: > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit-core/ > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit-htmlunit-plugin/ > I don't know if you should upload the last module (jwebunit-commons-tests), > as it is only used to run tests. > Thanks -- 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] Commented: (MAVENUPLOAD-982) Relocate jWebUnit and upload 1.3-rc2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-982?page=comments#action_70366 ] Carlos Sanchez commented on MAVENUPLOAD-982: well I finally added the relocation pom myself for this version > Relocate jWebUnit and upload 1.3-rc2 > > > Key: MAVENUPLOAD-982 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-982 > Project: maven-upload-requests > Issue Type: Task >Reporter: Julien HENRY > Assigned To: Carlos Sanchez > > As I didn't manage to create an upload bundle for a multi-module project, I > deployed jWebUnit in a private repository. > Please upload the parent pom: > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit > And only the following modules: > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit-core/ > http://jwebunit.sourceforge.net/m2-repo/net/sourceforge/jwebunit/jwebunit-htmlunit-plugin/ > I don't know if you should upload the last module (jwebunit-commons-tests), > as it is only used to run tests. > Thanks -- 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] Commented: (MAVENUPLOAD-1001) Stopwatch
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1001?page=comments#action_70367 ] Carlos Sanchez commented on MAVENUPLOAD-1001: - You must proof your ownership over the domain com.commsen.stopwatch Parent is missing and can't be snapshot > Stopwatch > - > > Key: MAVENUPLOAD-1001 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1001 > Project: maven-upload-requests > Issue Type: Task >Reporter: Milen Dyankov > Attachments: stopwatch-0.3-bundle.jar > > > http://prdownloads.sourceforge.net/jstopwatch/stopwatch-0.3.jar?download > http://jstopwatch.sourceforge.net > http://jstopwatch.sourceforge.net/team-list.html > Stopwatch is a free, simple, highly extensible, Java API that allows > developers to easily monitor > whole application or any part of it. -- 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] Commented: (MAVENUPLOAD-980) Upload JUG (Java UUID Generator) 2.0.0 (LGPL)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-980?page=comments#action_70372 ] Patrick Kimber commented on MAVENUPLOAD-980: I cannot find a way to use this jar... The dependency in my pom.xml is org.safehaus jug jug-2.0.0-asl Maven tries to download the jar file from: http://www.ibiblio.org/maven2/org/safehaus/jug/jug/2.0.0-asl/ but the jar file is in: http://www.ibiblio.org/maven2/org/safehaus/jug/jug/2.0.0/ > Upload JUG (Java UUID Generator) 2.0.0 (LGPL) > - > > Key: MAVENUPLOAD-980 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-980 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > Assigned To: Carlos Sanchez > Attachments: jug-lgpl-2.0.0-bundle.jar > > > http://home.mattwhitlock.com:8080/~mattw/jug-lgpl-2.0.0-bundle.jar > http://jug.safehaus.org/ > JUG is a pure java UUID generator, that can be used either as a component in > a bigger application, or as a standalone command line tool (a la 'uuidgen'). > UUIDs are 128-bit Universally Unique IDentifiers (aka GUID, Globally Unique > IDentifier used in Windows world). [see project site for more] -- 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] Commented: (MAVENUPLOAD-980) Upload JUG (Java UUID Generator) 2.0.0 (LGPL)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-980?page=comments#action_70374 ] Matt Whitlock commented on MAVENUPLOAD-980: --- You're forgetting the element. org.safehaus jug 2.0.0 asl > Upload JUG (Java UUID Generator) 2.0.0 (LGPL) > - > > Key: MAVENUPLOAD-980 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-980 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > Assigned To: Carlos Sanchez > Attachments: jug-lgpl-2.0.0-bundle.jar > > > http://home.mattwhitlock.com:8080/~mattw/jug-lgpl-2.0.0-bundle.jar > http://jug.safehaus.org/ > JUG is a pure java UUID generator, that can be used either as a component in > a bigger application, or as a standalone command line tool (a la 'uuidgen'). > UUIDs are 128-bit Universally Unique IDentifiers (aka GUID, Globally Unique > IDentifier used in Windows world). [see project site for more] -- 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] Commented: (MAVENUPLOAD-980) Upload JUG (Java UUID Generator) 2.0.0 (LGPL)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-980?page=comments#action_70375 ] Patrick Kimber commented on MAVENUPLOAD-980: Thanks. What a quick response! I still had the pom.xml slightly wrong. It should be: org.safehaus.jug jug 2.0.0 asl Thank you very much for your help. I never knew about the classifier tag. > Upload JUG (Java UUID Generator) 2.0.0 (LGPL) > - > > Key: MAVENUPLOAD-980 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-980 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > Assigned To: Carlos Sanchez > Attachments: jug-lgpl-2.0.0-bundle.jar > > > http://home.mattwhitlock.com:8080/~mattw/jug-lgpl-2.0.0-bundle.jar > http://jug.safehaus.org/ > JUG is a pure java UUID generator, that can be used either as a component in > a bigger application, or as a standalone command line tool (a la 'uuidgen'). > UUIDs are 128-bit Universally Unique IDentifiers (aka GUID, Globally Unique > IDentifier used in Windows world). [see project site for more] -- 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-1384) Display something when a snapshot dependency is newer
[ http://jira.codehaus.org/browse/MAVEN-1384?page=all ]
Lukas Theussl closed MAVEN-1384.
Assignee: Lukas Theussl
Resolution: Fixed
Fix Version/s: 1.1-beta-3
> Display something when a snapshot dependency is newer
> -
>
> Key: MAVEN-1384
> URL: http://jira.codehaus.org/browse/MAVEN-1384
> Project: Maven
> Issue Type: Improvement
> Components: core
>Affects Versions: 1.0
>Reporter: Julien Kirch
> Assigned To: Lukas Theussl
>Priority: Minor
> Fix For: 1.1-beta-3
>
>
> When a project dependency is a snasphot, a download.message is displayed,
> then when the external repository version is newer, the download starts, but
> when the local version is newer, no message is displayed and maven jump to
> the next dependency.
> It would be nice to have a message explaining why no download occured.
> ("Local version is ok" or something like this") because user doesn't
> understand why sometimes a download occurs and why sometimes not.
> In the same idea, I think that the download.message (Attempting to download
> ${1}.) is not well choosen because it's not really an attempt to download,
> but perhaps more a "Checking ${1}." or something like this sometimes followed
> by a download.
--
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: (CONTINUUM-781) move AbstractContinuumAction to plexus-xwork-integration
[ http://jira.codehaus.org/browse/CONTINUUM-781?page=all ] Carlos Sanchez closed CONTINUUM-781. Assignee: Carlos Sanchez (was: Emmanuel Venisse) Resolution: Fixed > move AbstractContinuumAction to plexus-xwork-integration > > > Key: CONTINUUM-781 > URL: http://jira.codehaus.org/browse/CONTINUUM-781 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1 >Reporter: Jesse McConnell > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: continuum-759-with-plexus-xwork-baseclass-2.patch > > > trygve mentioned in the commit notes that the abstraction action ought to > live in the xwork integration so I switched to over to that package and > deployed an updated snapshot with that new abstract action in it. -- 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] Commented: (CONTINUUM-733) can Mail notifier be configurable as to whether it sends a msg even when the state is not changed from previous build?
[ http://jira.codehaus.org/browse/CONTINUUM-733?page=comments#action_70379 ] Bugittaa Pahasti commented on CONTINUUM-733: alwaysSend is too restricted. It should be possible to be defined per notifier, for example for some emai address send just changes, for other send always. > can Mail notifier be configurable as to whether it sends a msg even when the > state is not changed from previous build? > -- > > Key: CONTINUUM-733 > URL: http://jira.codehaus.org/browse/CONTINUUM-733 > Project: Continuum > Issue Type: Improvement > Components: Mail Notifier >Affects Versions: 1.0.3 > Environment: Windows XP (doesn't really matter) >Reporter: Xiheng >Priority: Minor > Fix For: 1.1 > > > It's desirable that the mail notifier be made configurable so that the user > can choose to have continuum deliver a notification even when the build state > is not changed from the previous one (both success, or both failure, etc.). > Also, if continuum determines that "The project was not built because all > changes are unknown", it is desirable for the user to have an option of > receiving a message indicate as such. > Thanks! -- 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-1521) loading properties file via Ant property task does not work from maven.xml
[ http://jira.codehaus.org/browse/MAVEN-1521?page=all ] Lukas Theussl closed MAVEN-1521. Assignee: Lukas Theussl Resolution: Duplicate > loading properties file via Ant property task does not work from maven.xml > -- > > Key: MAVEN-1521 > URL: http://jira.codehaus.org/browse/MAVEN-1521 > Project: Maven > Issue Type: Bug > Components: jelly/ant integration >Affects Versions: 1.0.1 > Environment: n/a >Reporter: Ian Springer > Assigned To: Lukas Theussl > > If I have the following line in maven.xml, either within a goal or outside of > any goals: > > where my.properties exists and is a valid Java props file, any properties > that are in my.properties end up with a value of "0" (yes, simply the zero > character) in Maven. -- 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] Commented: (MAVEN-1688) The ${pom.versions} List behaves differently when running plugins under maven 1.1 and maven 1.0
[ http://jira.codehaus.org/browse/MAVEN-1688?page=comments#action_70380 ]
Lukas Theussl commented on MAVEN-1688:
--
The pom:validate goal correctly reports an error here because the id element is
required by the xsd. However, we need some basic validation routine within the
core, how is this done in m2?
> The ${pom.versions} List behaves differently when running plugins under maven
> 1.1 and maven 1.0
> ---
>
> Key: MAVEN-1688
> URL: http://jira.codehaus.org/browse/MAVEN-1688
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 1.1-beta-2
>Reporter: Henning Schmiedehausen
>
> Consider the following POM snipped:
>
>
> 2.1
> TURBINE_2_1
>
>
> 2.2
> TURBINE_2_2_0
>
>
> 2.3-rc1
> TURBINE_2_3_RC1
>
>
> 2.3-rc2
> TURBINE_2_3_RC2
>
>
> 2.3
> TURBINE_2_3
>
>
> 2.3.1-RC1
> TURBINE_2_3_1_RC1
>
>
> 2.3.1-RC2
> TURBINE_2_3_1_RC2
>
>
> 2.3.1
> TURBINE_2_3_1
> 2.3.1
>
>
> 2.3.2-RC1
> TURBINE_2_3_2_RC1
>
>
> echoing ${pom.versions} under the 1.0.2 maven release issues the following
> output:
> [echo] [2.1, 2.2, 2.3-rc1, 2.3-rc2, 2.3, 2.3.1-RC1, 2.3.1-RC2, 2.3.1,
> 2.3.2-RC1]
> doing the same thing under the 1.1-beta 2 core results in
> [echo] [null, null, null, null, null, null, null, 2.3.1, null]
> It seems that 1.0 uses the name as key and 1.1 uses the id. This causes e.g.
> the clirr plugin to fail if a project
> defines names for a version entry but no id.
> If it is necessary that a version entry contains name and/or id, it should be
> enforced by the maven core and bad
> entries should be reported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-129) BaseDirectory Ignored When Including a Repository
BaseDirectory Ignored When Including a Repository - Key: MASSEMBLY-129 URL: http://jira.codehaus.org/browse/MASSEMBLY-129 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Todd Wolff false lib Using goal assembly:assembly, outputDirectory, i.e. 'lib' in this case, is added to root of assembly archive rather than beneath the BaseDirectory. If includeBaseDirectory=false, outputDirectory is ommitted altogether and repository is written to archive root. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-122) Deploy the site
Deploy the site --- Key: MRM-122 URL: http://jira.codehaus.org/browse/MRM-122 Project: Maven Repository Manager Issue Type: Task Reporter: Jason van Zyl Would be good to have something there, even if only the introductory page as there were many questions about the repository manager in Maven sessions, and tutorials. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-783) Use standard jstl for links or they will break
Use standard jstl for links or they will break -- Key: CONTINUUM-783 URL: http://jira.codehaus.org/browse/CONTINUUM-783 Project: Continuum Issue Type: Bug Components: Web interface Reporter: Carlos Sanchez Fix For: 1.1 I see a lot of links constructed like this This will break under certain circustancies, like cookies disabled or variables with some chars that need to be encoded Also jstl automatically adds the contextPath at the beggining See http://www-128.ibm.com/developerworks/java/library/j-jstl0318/#N105D3 for more info The right way do do it is when no parameters need to be added it can just be "> -- 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] Commented: (CONTINUUM-771) Add user management screens
[ http://jira.codehaus.org/browse/CONTINUUM-771?page=comments#action_70386 ] Carlos Sanchez commented on CONTINUUM-771: -- Applied the patch in the branch, please look to CONTINUUM-783 for improvements on link construction > Add user management screens > --- > > Key: CONTINUUM-771 > URL: http://jira.codehaus.org/browse/CONTINUUM-771 > Project: Continuum > Issue Type: Sub-task > Components: Web interface >Reporter: Carlos Sanchez > Assigned To: Henry S. Isidro > Fix For: 1.1 > > Attachments: > CONTINUUM-771-continuum-webapp-using-PlexusActionSupport.patch, > CONTINUUM-771-continuum-webapp-with-improved-logging.patch, > CONTINUUM-771-continuum-webapp.patch > > > Add a page for listing the users, with options to add/edit/delete user > Users can have an unlimited number of roles (Continuum Permission) like > addProject, addUser,... they are already created by the ContinuumInitializer > and are static (no new roles/permissions can be added) -- 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: (MRM-122) Deploy the site
[ http://jira.codehaus.org/browse/MRM-122?page=all ] Jason van Zyl closed MRM-122. - Resolution: Fixed Deployed the simple site. Now will ping the choose.org folks. > Deploy the site > --- > > Key: MRM-122 > URL: http://jira.codehaus.org/browse/MRM-122 > Project: Maven Repository Manager > Issue Type: Task >Reporter: Jason van Zyl > Assigned To: Jason van Zyl > > Would be good to have something there, even if only the introductory page as > there were many questions about the repository manager in Maven sessions, and > tutorials. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2460) Incorrect POM inheritance for plugins
Incorrect POM inheritance for plugins - Key: MNG-2460 URL: http://jira.codehaus.org/browse/MNG-2460 Project: Maven 2 Issue Type: Bug Components: Documentation: General Affects Versions: 2.0.5 Reporter: Vincent Siveton Issue management and mailing list pages are not displayed correctly in the website. Originally http://www.nabble.com/-m2--Jira-for-maven-war-plugin--tf1979596.html -- 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-1644) Running Maven in a directory not containing a POM file always results in 'Build Successful'.
[ http://jira.codehaus.org/browse/MAVEN-1644?page=all ] Lukas Theussl closed MAVEN-1644. Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.1-beta-3 Just issuing a warning message should be enough. > Running Maven in a directory not containing a POM file always results in > 'Build Successful'. > > > Key: MAVEN-1644 > URL: http://jira.codehaus.org/browse/MAVEN-1644 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 1.0.2, 1.1-beta-1 > Environment: Not of importance. >Reporter: Davy Toch > Assigned To: Lukas Theussl >Priority: Minor > Fix For: 1.1-beta-3 > > > In maven 1.0.2 and 1.1-beta-1, running 'maven' in a directory that doesn't > contain a POM file always results in 'Build Succesful'. > == > $.\maven.bat > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 > BUILD SUCCESSFUL > Total time : 1 seconds > Finished at : vrijdag 8 juli 2005 13:32:35 CEST > == > This could be confusing for novice users of Maven and it would be better to > generate an error stating > that no POM file was found. -- 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] Commented: (MEV-425) plexus-container-default, junit scope compile is bad
[ http://jira.codehaus.org/browse/MEV-425?page=comments#action_70390 ] David Smiley commented on MEV-425: -- Actually... this isn't causing junit to show up in my war file; it was something else that I fixed. Nonetheless... someone should investigate the scope of this dependency. > plexus-container-default, junit scope compile is bad > > > Key: MEV-425 > URL: http://jira.codehaus.org/browse/MEV-425 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies >Reporter: David Smiley > > Has junit as a compile-time dependency, instead of test or even optional, > which is causing it to end up in my war file, I believe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2460) Incorrect POM inheritance for plugins
[ http://jira.codehaus.org/browse/MNG-2460?page=all ] Vincent Siveton updated MNG-2460: - Assignee: Vincent Siveton Fix Version/s: 2.0.5 > Incorrect POM inheritance for plugins > - > > Key: MNG-2460 > URL: http://jira.codehaus.org/browse/MNG-2460 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Affects Versions: 2.0.5 >Reporter: Vincent Siveton > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > > Issue management and mailing list pages are not displayed correctly in the > website. > Originally > http://www.nabble.com/-m2--Jira-for-maven-war-plugin--tf1979596.html -- 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: (MNG-2460) Incorrect POM inheritance for plugins
[ http://jira.codehaus.org/browse/MNG-2460?page=all ] Vincent Siveton closed MNG-2460. Resolution: Fixed Added missing tags in each POM > Incorrect POM inheritance for plugins > - > > Key: MNG-2460 > URL: http://jira.codehaus.org/browse/MNG-2460 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Affects Versions: 2.0.5 >Reporter: Vincent Siveton > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > > Issue management and mailing list pages are not displayed correctly in the > website. > Originally > http://www.nabble.com/-m2--Jira-for-maven-war-plugin--tf1979596.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1002) remove stalke quartz/1.5.2 folder
remove stalke quartz/1.5.2 folder - Key: MAVENUPLOAD-1002 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1002 Project: maven-upload-requests Issue Type: Task Reporter: Rainer Wasserfuhr http://www.ibiblio.org/maven2/quartz/quartz/1.5.2/ contains a broken upload. -- 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] Commented: (MSITE-137) The 'name' element does not work for a menu that references modules
[ http://jira.codehaus.org/browse/MSITE-137?page=comments#action_70394 ] Jörg Hohwiller commented on MSITE-137: -- I think I was to quick on this one. Seems to be a different issue... I have no clue how to remove the duplication in Jira, sorry... > The 'name' element does not work for a menu that references modules > --- > > Key: MSITE-137 > URL: http://jira.codehaus.org/browse/MSITE-137 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Dennis Lundberg > Attachments: site-plugin-test11.zip > > > There are a couple of special menus that can be used in the site descriptor, > for modules and reports. These menus will automatically be populated and they > have a default name. If you want to change this name you are supposed to be > able to change this using the 'name' element. This works fine for reports but > it doesn't work for modules. -- 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
