[jira] Commented: (MAVENUPLOAD-656) cewolf:cewolf:1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-656?page=comments#action_54634 ] Brian Fox commented on MAVENUPLOAD-656: --- One of these days I'll get it right the first time. Please use this bundle http://osdn.dl.sourceforge.net/sourceforge/cewolf/cewolf-1.0-bundle-2.jar > cewolf:cewolf:1.0 > - > > Key: MAVENUPLOAD-656 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-656 > Project: maven-upload-requests > Type: Bug > Reporter: Brian Fox > > > cewolf version stable 1.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]
[jira] Created: (MAVENUPLOAD-656) cewolf:cewolf:1.0
cewolf:cewolf:1.0 - Key: MAVENUPLOAD-656 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-656 Project: maven-upload-requests Type: Bug Reporter: Brian Fox cewolf version stable 1.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]
[jira] Commented: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54633 ] Brett Porter commented on MNG-1323: --- note above that this is scheduled for 2.0.3 (Feb release). > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Type: Bug > Components: Plugins and Lifecycle > Versions: 2.0 > Reporter: Kenney Westerhof > Fix For: 2.0.3 > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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 trunk - SUCCESS - update] Sun Jan 1 02:30:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060101.023000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060101.023000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Sun Jan 1 02:15:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060101.021500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060101.021500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MCHECKSTYLE-15) Exception: Can't find resource bundle for current bundle
[ http://jira.codehaus.org/browse/MCHECKSTYLE-15?page=comments#action_54632 ] Brett Porter commented on MCHECKSTYLE-15: - it hasn't been released yet, no. > Exception: Can't find resource bundle for current bundle > > > Key: MCHECKSTYLE-15 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-15 > Project: Maven 2.x Checkstyle Plugin > Type: Bug > Environment: WinXP SP2 > Maven 2.0 > maven-checkstyle-plugin 2.0-beta-1 > Reporter: Michael Böckling > Assignee: John Casey > > > When I try to execute mvn site with checkstyle configured in my POM, it > throws an exception saying it can't find the resource bundle for my locale. > Explicitly setting en in my POM has not effect. > Console: > [INFO] [site:site] > [INFO] > - > --- > [ERROR] FATAL ERROR > [INFO] > - > --- > [INFO] Can't find bundle for base name checkstyle-report, locale de_CH > [INFO] > - > --- > [INFO] Trace > java.util.MissingResourceException: Can't find bundle for base name > checkstyle-r > eport, locale de_CH > at > java.util.ResourceBundle.throwMissingResourceException(ResourceBundle > .java:804) > at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:773) > at java.util.ResourceBundle.getBundle(ResourceBundle.java:661) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.getBundle(Checkst > yleReport.java:539) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.getName(Checkstyl > eReport.java:201) > at > org.apache.maven.plugins.site.ReportComparator.compare(ReportComparat > or.java:40) > at java.util.Arrays.mergeSort(Arrays.java:1278) > at java.util.Arrays.sort(Arrays.java:1219) > at java.util.Collections.sort(Collections.java:155) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:240) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:399) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:469) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:448) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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 branches/maven-2.0.x - SUCCESS - update] Sun Jan 1 01:45:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060101.014500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060101.014500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1832) built-in property containing current timestamp
[ http://jira.codehaus.org/browse/MNG-1832?page=comments#action_54631 ]
Chris Hagmann commented on MNG-1832:
I basically need access to the timestamp to create a JAR manifest entry similar
to the following:
Build-date: 20051231-1841
Ideally we should be able to format the timestamp, but that is not absolutely
necessary.
P.S: I'm using a custom manifest template (not as part of pom.xml) and use
filtering to prepare the manifest file. E.g. My template looks like:
Package: ${product.name}
Build-Date: ${timestamp}
Specification-Title: ${product.name}
Specification-Version: ${product.specification.version}
Specification-Vendor: ${pom.organization.name}
Implementation-Title: ${product.name}
Implementation-Version: ${pom.version}
Implementation-Vendor: ${pom.organization.name}
...
...
> built-in property containing current timestamp
> --
>
> Key: MNG-1832
> URL: http://jira.codehaus.org/browse/MNG-1832
> Project: Maven 2
> Type: New Feature
> Versions: 2.0.1
> Reporter: Michal Stochmialek
>
>
> Current timestamp (time or date) is often used while filtering resources or
> creating manifest in ant builds. There is no equivalent 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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Sun Jan 1 01:15:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060101.011500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - checkout] Sun Jan 1 00:30:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060101.003000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - checkout] Sun Jan 1 00:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060101.01.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060101.01.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Sat Dec 31 19:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051231.193000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051231.193000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Sat Dec 31 19:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051231.191500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.191500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MANTRUN-36) Esccape property replacement inside quote
[ http://jira.codehaus.org/browse/MANTRUN-36?page=comments#action_54622 ]
Carlos Sanchez commented on MANTRUN-36:
---
test4 in plugin sources covers this issue
> Esccape property replacement inside quote
> -
>
> Key: MANTRUN-36
> URL: http://jira.codehaus.org/browse/MANTRUN-36
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Reporter: Gilles Scokart
> Attachments: MANTRUN-36.patch, MANTRUN-36.patch, ant.xml, pom.xml
>
>
> The propoerties placed not alone inside quotes are not correctly interpreted.
> For example :
>
>
>
> not alone in text ${myProp}.
>
>
> Succeed and print :
> [echo] alone in quote :
> [echo] OK
> [echo] not alone in text OK.
> [echo] not alone in quote null.
> While executed directly into ant prints :
> [echo] alone in quote :
> [echo] OK
> [echo] not alone in text OK.
> [echo] not alone in quote OK.
> You can find in attachment the pom.xml and the ant.xml I used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MANTRUN-36) Esccape property replacement inside quote
[ http://jira.codehaus.org/browse/MANTRUN-36?page=all ]
Carlos Sanchez updated MANTRUN-36:
--
Version: 1.1
> Esccape property replacement inside quote
> -
>
> Key: MANTRUN-36
> URL: http://jira.codehaus.org/browse/MANTRUN-36
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Reporter: Gilles Scokart
> Attachments: MANTRUN-36.patch, MANTRUN-36.patch, ant.xml, pom.xml
>
>
> The propoerties placed not alone inside quotes are not correctly interpreted.
> For example :
>
>
>
> not alone in text ${myProp}.
>
>
> Succeed and print :
> [echo] alone in quote :
> [echo] OK
> [echo] not alone in text OK.
> [echo] not alone in quote null.
> While executed directly into ant prints :
> [echo] alone in quote :
> [echo] OK
> [echo] not alone in text OK.
> [echo] not alone in quote OK.
> You can find in attachment the pom.xml and the ant.xml I used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MANTRUN-36) Esccape property replacement inside quote
[ http://jira.codehaus.org/browse/MANTRUN-36?page=all ]
Carlos Sanchez updated MANTRUN-36:
--
Attachment: MANTRUN-36.patch
> Esccape property replacement inside quote
> -
>
> Key: MANTRUN-36
> URL: http://jira.codehaus.org/browse/MANTRUN-36
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Reporter: Gilles Scokart
> Attachments: MANTRUN-36.patch, MANTRUN-36.patch, ant.xml, pom.xml
>
>
> The propoerties placed not alone inside quotes are not correctly interpreted.
> For example :
>
>
>
> not alone in text ${myProp}.
>
>
> Succeed and print :
> [echo] alone in quote :
> [echo] OK
> [echo] not alone in text OK.
> [echo] not alone in quote null.
> While executed directly into ant prints :
> [echo] alone in quote :
> [echo] OK
> [echo] not alone in text OK.
> [echo] not alone in quote OK.
> You can find in attachment the pom.xml and the ant.xml I used.
--
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 trunk - SUCCESS - update] Sat Dec 31 18:30:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051231.183001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051231.183001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Sat Dec 31 18:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051231.181502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.181502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MANTRUN-29) antrun: properties not resolved in attributes
[ http://jira.codehaus.org/browse/MANTRUN-29?page=all ]
Carlos Sanchez closed MANTRUN-29:
-
Assign To: Carlos Sanchez
Resolution: Duplicate
Fix Version: (was: 1.2)
> antrun: properties not resolved in attributes
> -
>
> Key: MANTRUN-29
> URL: http://jira.codehaus.org/browse/MANTRUN-29
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Environment: windows xp pro
> Reporter: Michal Stochmialek
> Assignee: Carlos Sanchez
> Attachments: pom.xml
>
>
> I found strange behavior of antrun plugin. I believe that properties are not
> resolved correctly in attributes content. For example task is
> producing different output depending on place where property is used. When
> property is used in tag body, the result is correct. But when used in
> attributes the result contains 'null's.
> I've tested it on example below.
>
> maven-antrun-plugin
>
>
> package
>
>
>
> location="${maven.build.directory}/jarInEar"/>
> # Those two lines below produce
> different output
> 1: ${destdir}
>
>
>
>
> run
>
>
>
>
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
> [DEBUG] getProperty(ns=null, name=destdir, user=false)
> [echo] 1: P:\projects\endpoint\target\jarInEar
> [echo] 2: null
> [INFO] Executed tasks
> This bug prevents from using properties in general, since almost most task's
> arguments are applied using arguments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MANTRUN-34) StringIndexOutOfBoundsException in custom ant task referencing 'basedir'
[ http://jira.codehaus.org/browse/MANTRUN-34?page=all ]
Carlos Sanchez closed MANTRUN-34:
-
Assign To: Carlos Sanchez (was: Jason van Zyl)
Resolution: Fixed
> StringIndexOutOfBoundsException in custom ant task referencing 'basedir'
>
>
> Key: MANTRUN-34
> URL: http://jira.codehaus.org/browse/MANTRUN-34
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Environment: XP, sun 1.4.2 JDK, maven 2.0.1, maven-antrun-plugin
> 1.1-SNAPSHOT (built from svn HEAD)
> Reporter: Marcel Schutte
> Assignee: Carlos Sanchez
> Fix For: 1.1
> Attachments: AntPropertyHelper.patch, CustomAntTask-extra-tests.zip,
> CustomAntTask.zip
>
>
> A custom ant task that in its java implementation references 'basedir' throws
> a StringIndexOutOfBoundsException. Executions continues and the result is
> correct.
> The attached zip contains a M2 project that builds the jar with the ant task
> and then calls it with the antrun plugin. The result for me is:
> C:\Data\WSAD\POC\CustomAntTask>mvn package
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Unnamed - nl.ohra.test:CustomAntTask:jar:1.0-SNAPSHOT
> [INFO]task-segment: [package]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> Compiling 1 source file to C:\Data\WSAD\POC\CustomAntTask\target\classes
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
> [INFO] [jar:jar]
> [INFO] Building jar:
> C:\Data\WSAD\POC\CustomAntTask\target\CustomAntTask-1.0-SNAPSHOT.jar
> [INFO] [antrun:run {execution: testant}]
> [INFO] Executing tasks
> Trying to override old definition of datatype test
> [WARNING] Error evaluating expression 'basedir'
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1444)
> at java.lang.String.substring(String.java:1411)
> at
> org.apache.maven.plugin.antrun.AntPropertyHelper.getPropertyHook(AntPropertyHelper.java:51)
> at
> org.apache.tools.ant.PropertyHelper.getPropertyHook(PropertyHelper.java:184)
> at
> org.apache.tools.ant.PropertyHelper.getProperty(PropertyHelper.java:438)
> at org.apache.tools.ant.Project.getProperty(Project.java:474)
> at nl.ohra.test.TestTask.execute(TestTask.java:11)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:103)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:47
> 2)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.s
[jira] Updated: (MANTRUN-34) StringIndexOutOfBoundsException in custom ant task referencing 'basedir'
[ http://jira.codehaus.org/browse/MANTRUN-34?page=all ]
Carlos Sanchez updated MANTRUN-34:
--
Testcase included: yes
Version: 1.1
Fix Version: 1.1
Added testcase as test5
> StringIndexOutOfBoundsException in custom ant task referencing 'basedir'
>
>
> Key: MANTRUN-34
> URL: http://jira.codehaus.org/browse/MANTRUN-34
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Environment: XP, sun 1.4.2 JDK, maven 2.0.1, maven-antrun-plugin
> 1.1-SNAPSHOT (built from svn HEAD)
> Reporter: Marcel Schutte
> Assignee: Jason van Zyl
> Fix For: 1.1
> Attachments: AntPropertyHelper.patch, CustomAntTask-extra-tests.zip,
> CustomAntTask.zip
>
>
> A custom ant task that in its java implementation references 'basedir' throws
> a StringIndexOutOfBoundsException. Executions continues and the result is
> correct.
> The attached zip contains a M2 project that builds the jar with the ant task
> and then calls it with the antrun plugin. The result for me is:
> C:\Data\WSAD\POC\CustomAntTask>mvn package
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Unnamed - nl.ohra.test:CustomAntTask:jar:1.0-SNAPSHOT
> [INFO]task-segment: [package]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> Compiling 1 source file to C:\Data\WSAD\POC\CustomAntTask\target\classes
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
> [INFO] [jar:jar]
> [INFO] Building jar:
> C:\Data\WSAD\POC\CustomAntTask\target\CustomAntTask-1.0-SNAPSHOT.jar
> [INFO] [antrun:run {execution: testant}]
> [INFO] Executing tasks
> Trying to override old definition of datatype test
> [WARNING] Error evaluating expression 'basedir'
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1444)
> at java.lang.String.substring(String.java:1411)
> at
> org.apache.maven.plugin.antrun.AntPropertyHelper.getPropertyHook(AntPropertyHelper.java:51)
> at
> org.apache.tools.ant.PropertyHelper.getPropertyHook(PropertyHelper.java:184)
> at
> org.apache.tools.ant.PropertyHelper.getProperty(PropertyHelper.java:438)
> at org.apache.tools.ant.Project.getProperty(Project.java:474)
> at nl.ohra.test.TestTask.execute(TestTask.java:11)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:103)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:47
> 2)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>
[jira] Commented: (MANTRUN-29) antrun: properties not resolved in attributes
[ http://jira.codehaus.org/browse/MANTRUN-29?page=comments#action_54618 ]
Carlos Sanchez commented on MANTRUN-29:
---
A workaround is using an external build.xml and call it with
> antrun: properties not resolved in attributes
> -
>
> Key: MANTRUN-29
> URL: http://jira.codehaus.org/browse/MANTRUN-29
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Environment: windows xp pro
> Reporter: Michal Stochmialek
> Fix For: 1.2
> Attachments: pom.xml
>
>
> I found strange behavior of antrun plugin. I believe that properties are not
> resolved correctly in attributes content. For example task is
> producing different output depending on place where property is used. When
> property is used in tag body, the result is correct. But when used in
> attributes the result contains 'null's.
> I've tested it on example below.
>
> maven-antrun-plugin
>
>
> package
>
>
>
> location="${maven.build.directory}/jarInEar"/>
> # Those two lines below produce
> different output
> 1: ${destdir}
>
>
>
>
> run
>
>
>
>
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
> [DEBUG] getProperty(ns=null, name=destdir, user=false)
> [echo] 1: P:\projects\endpoint\target\jarInEar
> [echo] 2: null
> [INFO] Executed tasks
> This bug prevents from using properties in general, since almost most task's
> arguments are applied using arguments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MANTRUN-35) mvn debug level not passed to ant
[ http://jira.codehaus.org/browse/MANTRUN-35?page=all ] Carlos Sanchez updated MANTRUN-35: -- Version: 1.1 Fix Version: 1.2 > mvn debug level not passed to ant > - > > Key: MANTRUN-35 > URL: http://jira.codehaus.org/browse/MANTRUN-35 > Project: Maven 2.x Antrun Plugin > Type: Improvement > Versions: 1.1 > Environment: Any > Reporter: M. van der Plas > Assignee: Jason van Zyl > Priority: Minor > Fix For: 1.2 > > > Ant task like have a property level which can be set to trigger > activation based on the loglevel. > Maven mvn has the commandline option to activate the debug log level. > Currently it is not possible to set the ant task log level. > The mvn log level should be passed to ant so it can be used in log level > aware ant tasks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MANTRUN-29) antrun: properties not resolved in attributes
[ http://jira.codehaus.org/browse/MANTRUN-29?page=all ]
Carlos Sanchez updated MANTRUN-29:
--
Testcase included: yes
Version: 1.1
Fix Version: 1.2
Seems that it's trying to resolve that properties in maven properties instead
of ant properties
Testcase test4 committed
> antrun: properties not resolved in attributes
> -
>
> Key: MANTRUN-29
> URL: http://jira.codehaus.org/browse/MANTRUN-29
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Environment: windows xp pro
> Reporter: Michal Stochmialek
> Fix For: 1.2
> Attachments: pom.xml
>
>
> I found strange behavior of antrun plugin. I believe that properties are not
> resolved correctly in attributes content. For example task is
> producing different output depending on place where property is used. When
> property is used in tag body, the result is correct. But when used in
> attributes the result contains 'null's.
> I've tested it on example below.
>
> maven-antrun-plugin
>
>
> package
>
>
>
> location="${maven.build.directory}/jarInEar"/>
> # Those two lines below produce
> different output
> 1: ${destdir}
>
>
>
>
> run
>
>
>
>
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
> [DEBUG] getProperty(ns=null, name=destdir, user=false)
> [echo] 1: P:\projects\endpoint\target\jarInEar
> [echo] 2: null
> [INFO] Executed tasks
> This bug prevents from using properties in general, since almost most task's
> arguments are applied using arguments.
--
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 branches/maven-2.0.x - SUCCESS - update] Sat Dec 31 17:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051231.171501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.171501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MANTRUN-32) ant tasks don't use correct environment in antrun plugin
[ http://jira.codehaus.org/browse/MANTRUN-32?page=all ]
Carlos Sanchez updated MANTRUN-32:
--
Testcase included: yes
Version: 1.1
Fix Version: 1.2
Testcase is test3 in plugin
> ant tasks don't use correct environment in antrun plugin
>
>
> Key: MANTRUN-32
> URL: http://jira.codehaus.org/browse/MANTRUN-32
> Project: Maven 2.x Antrun Plugin
> Type: Bug
> Versions: 1.1
> Reporter: Brett Porter
> Fix For: 1.2
>
>
> eg, ${user.home} does not resolve to the java system property as it would
> when you execute it standalone
--
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 trunk - SUCCESS - update] Sat Dec 31 17:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051231.17.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051231.17.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Sat Dec 31 16:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051231.164500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.164500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54612 ] Georges Polyzois commented on MNG-1323: --- Is this beeing resolved? I have exactly this problem as Kenney stated on 04/Nov/05. I am using Maven 2.0.1 and even changed to using antrun version 1.1-SNAPSHOT - with no sucess. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Type: Bug > Components: Plugins and Lifecycle > Versions: 2.0 > Reporter: Kenney Westerhof > Fix For: 2.0.3 > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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 branches/maven-2.0.x - SUCCESS - update] Sat Dec 31 12:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051231.121500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.121500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Sat Dec 31 12:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051231.12.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051231.12.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Sat Dec 31 11:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051231.114501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051231.114501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MCHECKSTYLE-24) Jdk14logger exception
[ http://jira.codehaus.org/browse/MCHECKSTYLE-24?page=all ] fabrizio giustina closed MCHECKSTYLE-24: Assign To: fabrizio giustina (was: Jason van Zyl) Resolution: Fixed Fix Version: 2.0-beta-2 cannot be reproduced anymore, probably fixed together with other classloader-related issues > Jdk14logger exception > - > > Key: MCHECKSTYLE-24 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-24 > Project: Maven 2.x Checkstyle Plugin > Type: Bug > Environment: Maven 2.0.1, checkstyle plugin 2.0-beta-1, JDK5, Win2000 > Reporter: darren hartford > Assignee: fabrizio giustina > Priority: Blocker > Fix For: 2.0-beta-2 > Attachments: checkstyletrace.txt > > > Problem with checkstyle plugin when used with 'site' - see attached trace. > 'mvn checkstyle:checkstyle' works fine. > Also reference http://jira.codehaus.org/browse/MCHECKSTYLE-10 as may be > similar issue/fix. -- 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: (MCHECKSTYLE-27) checktyle:check does not use custom checkstyle xml files when used in a multiproject mode with a build-tools project passed as a plugin dependency
checktyle:check does not use custom checkstyle xml files when used in a multiproject mode with a build-tools project passed as a plugin dependency -- Key: MCHECKSTYLE-27 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-27 Project: Maven 2.x Checkstyle Plugin Type: Bug Reporter: Vincent Massol Here's the config I have: maven-checkstyle-plugin org.codehaus.cargo cargo-build-tools 0.8-SNAPSHOT build-tools/checkstyle.xml build-tools/checkstyle.license build-tools/checkstyle-suppressions.xml check When i run the project I get lots of checkstyle errors due to the fact that checkstyle is using the default rules and not my projcect's. Note that I have created a build-tools project as defined in tips.apt. -- 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: (MCHECKSTYLE-26) checkstyle:check fails when the project has no sources
[ http://jira.codehaus.org/browse/MCHECKSTYLE-26?page=comments#action_54601
]
Vincent Massol commented on MCHECKSTYLE-26:
---
Thanks Fabrizio, it works.
The only change I would make is to output the message in debug severity instead
of info.
> checkstyle:check fails when the project has no sources
> ---
>
> Key: MCHECKSTYLE-26
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-26
> Project: Maven 2.x Checkstyle Plugin
> Type: Bug
> Reporter: Vincent Massol
> Assignee: fabrizio giustina
> Fix For: 2.0-beta-2
>
>
> See MCHECKSTYLE-25
> When there are no sources, the checkstyle goal do not generate an output file
> and thus the checkstyle:check goal fails:
> C:\dev\cargo\trunk\core>mvn clean install
> [INFO] Scanning for projects...
> [INFO] snapshot org.codehaus.cargo:cargo:0.8-SNAPSHOT: checking for updates
> from maven-snapshot
> [INFO] Reactor build order:
> [INFO] Cargo Core
> [INFO] Cargo Core API
> [INFO] Cargo Core Util API
> [INFO] Cargo Core Module API
> [INFO] Cargo Core Container API
> [INFO] Cargo Core Generic API
> [INFO] Cargo Core Containers
> [INFO] Cargo Core Tomcat Container
> [INFO] Cargo Core Resin Container
> [INFO] Cargo Core JBoss Container
> [INFO] Cargo Core Orion Container
> [INFO] Cargo Core Jetty Container
> [INFO] Cargo Core WebLogic Container
> [INFO] Cargo Core jo! Container
> [INFO] Cargo Core Uberjar
> [INFO]
>
> [INFO] Building Cargo Core
> [INFO] task-segment: [clean, install]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] Preparing checkstyle:check
> [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.ResourceNotFoundExcepti
> on: 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] [checkstyle:checkstyle]
> [INFO] Source directory does not exist - skipping report.
> [INFO] [checkstyle:check {execution: default}]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 10 seconds
> [INFO] Finished at: Fri Dec 30 20:38:28 CET 2005
> [INFO] Final Memory: 6M/11M
> [INFO]
