[jira] Updated: (MCOMPILER-100) Can compile a very simple java program in Chinese platform when turn "true" on
[
http://jira.codehaus.org/browse/MCOMPILER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated MCOMPILER-100:
--
Attachment: testCompile_updated.zip
Please use this updated one to recreate the problem. The error will be：
{noformat}
D:\testCompile>mvn clean compile
[INFO] Scanning for projects...
[INFO]
[INFO] Building testCompile
[INFO]task-segment: [clean, compile]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\testCompile\target
[INFO] [resources:resources]
[WARNING] Using platform encoding (GBK actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory D:\testCompile\src\main\resources
[INFO] [compiler:compile]
[INFO] Compiling 1 source file to D:\testCompile\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
D:\testCompile\src\main\java\org\apache\App.java:[15,5]
警告：[deprecation] java.util.Date 中的
Date(int,int,int) 已过时
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Jun 25 14:58:04 CST 2009
[INFO] Final Memory: 7M/15M
[INFO]
{noformat}
> Can compile a very simple java program in Chinese platform when turn
> "true" on
> -
>
> Key: MCOMPILER-100
> URL: http://jira.codehaus.org/browse/MCOMPILER-100
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.0, 2.0.1, 2.0.2
> Environment: Chinese Windows XP + sun JDK 1.5 + maven 2.10
>Reporter: Shawn Jiang
> Attachments: testCompile.zip, testCompile_updated.zip
>
>
> Use the attached project, note there is a Deprecated class DefaultTextUI . I
> put that in code on purpose because only when there's Deprecated class in
> use.
> And I turn on "true" in compiler plugin.
> The compile fails. This is not another platform problem because as you can
> see. There's no non-ASCII characters in the code. And I can use javac to
> compile it without any problem.
> It's a defect of compiler plugin when outputing the globalization
> Deprecation warning message.
> {quote}
> D:\testCompile>g10 compile -X
> + Error stacktraces are turned on.
> Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800)
> Java version: 1.5.0_15
> Java home: D:\dev\JDKs\sun_jdk5\jre
> Default locale: zh_CN, platform encoding: GBK
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> ..
> [DEBUG] Classpath:
> [DEBUG] D:\testCompile\target\classes
> [DEBUG] Source roots:
> [DEBUG] D:\testCompile\src\main\java
> [INFO] Compiling 1 source file to D:\testCompile\target\classes
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
> D:\testCompile\src\main\java\org\apache\App.java:[3,24]
> 警告：[deprecation] javax.swing.text 中的
> javax.swing.te
> D:\testCompile\src\main\java\org\apache\App.java:[12,1]
> 警告：[deprecation] javax.swing.text 中的
> javax.swing.te
> D:\testCompile\src\main\java\org\apache\App.java:[15,8]
> 警告：[deprecation] javax.swing.text 中的
> javax.swing.te
> D:\testCompile\src\main\java\org\apache\App.java:[15,4]
> javax.swing.text.DefaultTextUI
> 是抽象的；无法对其进行实例
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Compilation failure
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:699)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExec
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>
[jira] Commented: (MRELEASE-455) Doesn't update the versions correctly if end tag is on a seperate line
[
http://jira.codehaus.org/browse/MRELEASE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181452#action_181452
]
Maria Catherine Tan commented on MRELEASE-455:
--
the patch only cleanup leading and trailing spaces for ,
and
> Doesn't update the versions correctly if end tag is on a seperate line
> --
>
> Key: MRELEASE-455
> URL: http://jira.codehaus.org/browse/MRELEASE-455
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-8
>Reporter: Maria Catherine Tan
> Attachments: MRELEASE-455.patch
>
>
> {noformat}
>
>
> com.test
>
> test
>
> 1.0-SNAPSHOT
>
>
> {noformat}
> The released artifact contains snapshot dependency of com.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: (MRELEASE-455) Doesn't update the versions correctly if end tag is on a seperate line
[
http://jira.codehaus.org/browse/MRELEASE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Catherine Tan updated MRELEASE-455:
-
Attachment: MRELEASE-455.patch
Attached patch that will remove leading and trailing spaces in between tags.
e.g.
{noformat}
groupId
to
groupId
{noformat}
> Doesn't update the versions correctly if end tag is on a seperate line
> --
>
> Key: MRELEASE-455
> URL: http://jira.codehaus.org/browse/MRELEASE-455
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-8
>Reporter: Maria Catherine Tan
> Attachments: MRELEASE-455.patch
>
>
> {noformat}
>
>
> com.test
>
> test
>
> 1.0-SNAPSHOT
>
>
> {noformat}
> The released artifact contains snapshot dependency of com.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] Issue Comment Edited: (MRELEASE-455) Doesn't update the versions correctly if end tag is on a seperate line
[
http://jira.codehaus.org/browse/MRELEASE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181451#action_181451
]
Maria Catherine Tan edited comment on MRELEASE-455 at 6/25/09 3:22 AM:
---
Attached patch that will remove leading and trailing spaces in between tags
during rewriting of pom.
e.g.
{noformat}
groupId
to
groupId
{noformat}
was (Author: ctan):
Attached patch that will remove leading and trailing spaces in between tags.
e.g.
{noformat}
groupId
to
groupId
{noformat}
> Doesn't update the versions correctly if end tag is on a seperate line
> --
>
> Key: MRELEASE-455
> URL: http://jira.codehaus.org/browse/MRELEASE-455
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-8
>Reporter: Maria Catherine Tan
> Attachments: MRELEASE-455.patch
>
>
> {noformat}
>
>
> com.test
>
> test
>
> 1.0-SNAPSHOT
>
>
> {noformat}
> The released artifact contains snapshot dependency of com.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] Closed: (MPDF-6) Schedule and release Doxia 1.1.1
[ http://jira.codehaus.org/browse/MPDF-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPDF-6. Assignee: Lukas Theussl Resolution: Fixed Done. > Schedule and release Doxia 1.1.1 > > > Key: MPDF-6 > URL: http://jira.codehaus.org/browse/MPDF-6 > Project: Maven 2.x PDF Plugin > Issue Type: Task >Affects Versions: 1.0 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 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
[jira] Closed: (MAVENUPLOAD-2412) wurfl-pro sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filippo De Luca closed MAVENUPLOAD-2412. Resolution: Incomplete The information are not right > wurfl-pro sync > -- > > Key: MAVENUPLOAD-2412 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2412 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Filippo De Luca >Assignee: Brian Fox > > "net.sourceforge.net", > "mavens...@dev.wurflpro.com:/home/nexus/sonatype-work/nexus/storage/public-releases", > "rsync_ssh", "Filippo De Luca", "filippo.del...@wurflpro.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: (MAVENUPLOAD-2495) dev.wurflpro.com synchornization
dev.wurflpro.com synchornization Key: MAVENUPLOAD-2495 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2495 Project: Maven Upload Requests Issue Type: Task Reporter: Filippo De Luca Hi I am a wurfl-pro developer and responsible of wurfl-pro maven repository. We request our repository will be synced with the central repository. The sync request line: "net.sourceforge.wurfl","mavens...@dev.wurflpro.com:/home/nexus/sonatype-work/nexus/storage/public-releases","rsync_ssh","Filippo De Luca","filippo.del...@wurflpro.it",, Thank you -- 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-200) Filtering resource don't work as expected
Filtering resource don't work as expected
-
Key: MWAR-200
URL: http://jira.codehaus.org/browse/MWAR-200
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.1-beta-1, 2.1-alpha-1
Environment: windows and unix
Reporter: hugo lassiege
Attachments: toto.txt
Hi,
I try to use maven war plugin and cargo however I have a problem with
maven-war-plugin and the filtering.
I tried with 2.1-beta-1 and alpha1
My configuration for the maven-war-plugin is the following :
{code:xml}
org.apache.maven.plugins
maven-war-plugin
2.1-beta-1
${basedir}/src/main/webapp/META-INF
true
context.xml
META-INF/
{code}
My goal is to filter the context.xml to modify the name of the datasource
My context.xml unfiltered is :
{code:xml}
{code}
I use mvn clean install to launch the build
In DEBUG mode I have :
{code}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-war-plugin:2.1-alpha-1:war' -->
[DEBUG] (f) addDefaultSpecificationEntries = true
[DEBUG] (f) addDefaultImplementationEntries = true
[DEBUG] (s) manifest = org.apache.maven.archiver.manifestconfigurat...@1d50fd2
[DEBUG] (f) archive =
org.apache.maven.archiver.mavenarchiveconfigurat...@101ac1c
[DEBUG] (s) archiveClasses = true
[DEBUG] (s) cacheFile =
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\war\work\webapp-cache.xml
[DEBUG] (s) classesDirectory =
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\classes
[DEBUG] (s) filters = []
[DEBUG] (f) outputDirectory =
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target
[DEBUG] (f) primaryArtifact = true
[DEBUG] (s) project = MavenProject:
fr.sgf.wit:webintake-security-integration:3.5.0-alpha3-SNAPSHOT @
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\pom.xml
[DEBUG] (s) useCache = true
[DEBUG] (f) warName = webintake-security-integration-3.5.0-alpha3-SNAPSHOT
[DEBUG] (s) warSourceDirectory =
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\src\main\webapp
[DEBUG] (s) directory =
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF
[DEBUG] (s) filtering = true
[DEBUG] (s) includes = [context.xml]
[DEBUG] (s) targetPath = META-INF/
[DEBUG] (s) webResources = [Resource {targetPath: META-INF/, filtering: true,
FileSet {directory:
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF,
PatternSet [includes: {context.xml}, excludes: {}]}}]
[DEBUG] (s) webappDirectory =
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT
[DEBUG] (s) workDirectory =
E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\war\work
[DEBUG] -- end configuration --
[INFO] [war:war]
[INFO] Packaging webapp
[INFO] Assembling webapp[webintake-security-integration] in
[E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT]
[INFO] Processing war project
[INFO] Copy webapp
webResources[E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF]
to[E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT]
[DEBUG] + META-INF/\context.xml has been copied.
[DEBUG] + META-INF/context.xml has been copied.
{code}
So the filtering is active and the context.xml is copied as expected but not
filtered !
The file is not modified, I still have the variable not filtered.
If I make mvn install (removing the clean) it works the second time, I guess
the file is read from the right place the second time ?
I attached the mvn command with option -X
--
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-2363) does not work in a multi-project build
[
http://jira.codehaus.org/browse/MNG-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-2363.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: (was: 2.2.x)
3.0-alpha-3
Fixed in [r788334|http://svn.apache.org/viewvc?view=rev&revision=788334].
> does not work in a multi-project build
> ---
>
> Key: MNG-2363
> URL: http://jira.codehaus.org/browse/MNG-2363
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Reporter: David Boden
>Assignee: Benjamin Bentmann
>Priority: Critical
> Fix For: 3.0-alpha-3
>
> Attachments: DefaultMavenProjectBuilder.java,
> DefaultMavenProjectBuilder.java, DefaultMavenProjectBuilder.java.diff,
> problemactivation.zip, screenshot-1.jpg
>
>
> I would expect each subproject to have the profile turned on or off depending
> on whether ${basedir}/file-to-check-for exists.
> Instead, during a multi-project build the profile is either on or off
> depending on whether the file exists relative to the *aggregator pom*. The
> decision is made once.
> Variable substitution doesn't work, so I can't explicitly use
> ${basedir}/file-to-check-for or any variation on this theme
> to workaround the bug.
> Some background to my particular problem. I have 10 modules to build. Some of
> them are GUI modules and contain a file called plugin.xml in the subproject
> directory. I want to package these up specially and sign them, ready for
> deployment to webstart. The other modules are shared and server code and I
> don't want these packaged in the same way. So, I've got a dependency in my
> *parent* pom file which activates a profile called "guibundle" if a
> plugin.xml file exists in the subproject directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4174) Inheritance from profiles from parent-pom to child-pom
[ http://jira.codehaus.org/browse/MNG-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4174. -- Assignee: Benjamin Bentmann Resolution: Duplicate > Inheritance from profiles from parent-pom to child-pom > -- > > Key: MNG-4174 > URL: http://jira.codehaus.org/browse/MNG-4174 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Thilo Väth >Assignee: Benjamin Bentmann > Attachments: TestProject.rar > > > what is the problem with the tag wich is passed from a > parent-pom (and works there) to a child-pom.?! > In the child-pom, the tag (for example with an clause) > isn´t observed. > I´ve an example project attached... > - > Parent POM X > - > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > > root > org.richfaces > 3.2.3-SNAPSHOT > - > 4.0.0 > org.richfaces > samples > pom > RichFaces Components Examples > http://labs.jboss.com/jbossrichfaces/samples > > > TEST_PROFILE > > > 123text.txt > > > > > > > org.apache.maven.plugins > > maven-compiler-plugin > > 1.4 > 1.4 > > > > > > > > > > > > > - > Child POM X > - > > > > samples > org.richfaces > 3.2.3-SNAPSHOT > > 4.0.0 > org.richfaces.samples > beanValidatorSample > war > beanValidatorSample Maven Webapp > 3.2.3-SNAPSHOT > > beanValidatorSample > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > > > -- 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-4218) NPE in AbstractArtifactResolutionException if DefaultArtifactResolver.resolveTransitively is interrupted
NPE in AbstractArtifactResolutionException if DefaultArtifactResolver.resolveTransitively is interrupted Key: MNG-4218 URL: http://jira.codehaus.org/browse/MNG-4218 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.1.0 Environment: all platforms Reporter: Stefan Wismer Priority: Minor If an InterruptedException occurs in DefaultArtifactResolver.resolveTransitively, it is caught and an ArtifactResolutionException is thrown where the Artifact parameter is null (line 350): throw new ArtifactResolutionException( "Resolution interrupted", null, e ); Unfortunately, AbstractArtifactResolutionException tries to access properties from that null-Artifact... The error output is therefore hiding the actual problem: java.lang.NullPointerException at org.apache.maven.artifact.resolver.AbstractArtifactResolutionException.(AbstractArtifactResolutionException.java:92) at org.apache.maven.artifact.resolver.ArtifactResolutionException.(ArtifactResolutionException.java:57) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:350) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1492) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:435) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:597) 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
[jira] Commented: (MNG-4181) system path dependencies are not resolved
[
http://jira.codehaus.org/browse/MNG-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181499#action_181499
]
Norbert Truchsess commented on MNG-4181:
here's something I found out:
I have system-scoped dependency in my pom.xml:
weblogic
wls-api
${weblogic.version}
system
${weblogic.home}/server/lib/wls-api.jar
If I specify weblogic-home in settings.xml profile:
default
true
C:\localdata\lib\bea\wlserver_10.0
it fails to resolve and I get the same warning:
[WARNING] POM for '' is invalid.
Its dependencies (if any) will NOT be available to the current build.
But if I specify the same property via -D-parameter on the mvn commandline
mvn -Dweblogic.home=c:\\localdata\\weblogic
then it's going to be resolved and it builds without errors.
> system path dependencies are not resolved
> -
>
> Key: MNG-4181
> URL: http://jira.codehaus.org/browse/MNG-4181
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.1.0
> Environment: Windows Vista
>Reporter: Karsten Ohme
>Priority: Critical
>
> If a system path dependency is used, the depencies are not included.
> I cannot build my project anymore and I'm stuck.
> This is the error I get:
> [WARNING] POM for 'net.sf:microlog-instrument:pom:1.1.1:compile' is invalid.
> Its dependencies (if any) will NOT be available to the current build.
> [DEBUG] Reason: Failed to validate POM for project net.sf:microlog-instrument
> at
> Artifact [net.sf:microlog-instrument:pom:1.1.1:compile]
> [DEBUG]
> Validation Errors:
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=jsr21
> 1, version=2.2, type=jar}: system-scoped dependency must specify an absolute
> pat
> h systemPath.
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=jsr08
> 2, version=2.2, type=jar}: system-scoped dependency must specify an absolute
> pat
> h systemPath.
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=jsr75
> , version=2.2, type=jar}: system-scoped dependency must specify an absolute
> path
> systemPath.
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=wma20
> , version=2.2, type=jar}: system-scoped dependency must specify an absolute
> path
> systemPath.
--
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-4218) NPE in AbstractArtifactResolutionException if DefaultArtifactResolver.resolveTransitively is interrupted
[ http://jira.codehaus.org/browse/MNG-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4218. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.2.1 2.1.1 Fixed in [r788378|http://svn.apache.org/viewvc?view=rev&revision=788378] and [r788380|http://svn.apache.org/viewvc?view=rev&revision=788380], respectively. > NPE in AbstractArtifactResolutionException if > DefaultArtifactResolver.resolveTransitively is interrupted > > > Key: MNG-4218 > URL: http://jira.codehaus.org/browse/MNG-4218 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.1.0 > Environment: all platforms >Reporter: Stefan Wismer >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.1.1, 2.2.1 > > > If an InterruptedException occurs in > DefaultArtifactResolver.resolveTransitively, it is caught and an > ArtifactResolutionException is thrown where the Artifact parameter is null > (line 350): > throw new ArtifactResolutionException( "Resolution interrupted", null, e ); > Unfortunately, AbstractArtifactResolutionException tries to access properties > from that null-Artifact... > The error output is therefore hiding the actual problem: > java.lang.NullPointerException > at > org.apache.maven.artifact.resolver.AbstractArtifactResolutionException.(AbstractArtifactResolutionException.java:92) > at > org.apache.maven.artifact.resolver.ArtifactResolutionException.(ArtifactResolutionException.java:57) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:350) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1492) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:435) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) > 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:597) > 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
[jira] Updated: (MANT-52) NullPointerException when maven-javadoc-plugin configuration defines multiple group elements within a groups list element.
[
http://jira.codehaus.org/browse/MANT-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MANT-52:
--
Description:
When attempting to run mvn ant:ant on sesame-2.2.4 available here [1]. A
NullPointerException is raised. [2] for build log segment.
It seems that when a pom ( or a parents pom ) defines the following
configuration the existing code the error was occuring. I have assumed in my
patch that this is the only valid way of defining groups. But at least the fix
is small and easy for you to figure out.
{code:xml}
org.apache.maven.plugins
maven-javadoc-plugin
true
1.5
Repository API
org.openrdf.repository*
RDF Model API
org.openrdf.model*
...
...
http://java.sun.com/j2se/1.5.0/docs/api/
http://repository.aduna-software.org/docs/info.aduna/api/
{code}
[1] svn co http://repo.aduna-software.org/svn/org.openrdf/sesame/tags/2.2.4/
[2]
{noformat}
[INFO] Building OpenRDF Sesame Core
[INFO]task-segment: [ant:ant]
[INFO]
[INFO] [ant:ant]
[INFO] Wrote Ant project for sesame-core to
/home/alistair/gentoo/tmp/sesame-2.2.4/core
[INFO]
[INFO] Building OpenRDF Sesame: Model
[INFO]task-segment: [ant:ant]
[INFO]
[INFO] [ant:ant]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXml(PrettyPrintXMLWriter.java:151)
at
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXmlAttribute(PrettyPrintXMLWriter.java:166)
at
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:190)
at
org.apache.maven.plugin.ant.AntBuildWriterUtil.writeJavadocTask(AntBuildWriterUtil.java:473)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeJavadocTarget(AntBuildWriter.java:991)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:304)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:113)
at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
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.mai
[jira] Issue Comment Edited: (WAGON-264) compressed tarball download problems
[
http://jira.codehaus.org/browse/WAGON-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179794#action_179794
]
John Casey edited comment on WAGON-264 at 6/25/09 12:09 PM:
The following headers are set by default in the latest trunk revisions of the
httpclient-driven wagon (this is the http wagon that will be used in Maven
2.2.0):
{code}
method.addRequestHeader( "Cache-control", "no-cache" );
method.addRequestHeader( "Cache-store", "no-store" );
method.addRequestHeader( "Pragma", "no-cache" );
method.addRequestHeader( "Expires", "0" );
method.addRequestHeader( "Accept-Encoding", "gzip" );
{code}
To disable the Accept-Encoding header, you will have to disable all of these
default headers, then re-add the ones you want to keep. As of the versions
checked into trunk, you can do this by editing the settings.xml, like this:
{code:xml}
myrepo
false
Cache-control
no-cache
Cache-store
no-store
Pragma
no-cache
Expires
0
{code}
Note that the above configuration will work for wagons accessed through the
WagonManager in maven-artifact-manager. If you're managing Wagon instances
elsewhere, you may need to provide access to the new HttpConfiguration and
HttpMethodConfiguration config classes in wagon-http-shared.
was (Author: jdcasey):
The following headers are set by default in the latest trunk revisions of
the httpclient-driven wagon (this is the http wagon that will be used in Maven
2.2.0):
{code}
method.addRequestHeader( "Cache-control", "no-cache" );
method.addRequestHeader( "Cache-store", "no-store" );
method.addRequestHeader( "Pragma", "no-cache" );
method.addRequestHeader( "Expires", "0" );
method.addRequestHeader( "Accept-Encoding", "gzip" );
{code}
To disable the Accept-Encoding header, you will have to disable all of these
default headers, then re-add the ones you want to keep. As of the versions
checked into trunk, you can do this by editing the settings.xml, like this:
{code:xml}
myrepo
false
no-cache
no-store
no-cache
0
{code}
Note that the above configuration will work for wagons accessed through the
WagonManager in maven-artifact-manager. If you're managing Wagon instances
elsewhere, you may need to provide access to the new HttpConfiguration and
HttpMethodConfiguration config classes in wagon-http-shared.
> compressed tarball download problems
>
>
> Key: WAGON-264
> URL: http://jira.codehaus.org/browse/WAGON-264
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http-lightweight
>Affects Versions: 1.0-beta-2, 1.0-beta-3, 1.0-beta-4, 1.0-beta-5
>Reporter: Lee Thompson
>Assignee: John Casey
> Fix For: 1.0-beta-6
>
>
> HTTP wagon will uncompress tarballs it downloads, sometimes badly.
> Downloading openssl results in an unpressed download
> $ mvn -X wagon:download-single -Dwagon.fromFile=openssl-0.9.8k.tar.gz
> -Dwagon.url=http://www.openssl.org/source -Dwagon.toDir=./
> $ tar tzf openssl-0.9.8k.tar.gz
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Error exit delayed from previous errors
> $ tar tf openssl-0.9.8k.tar.gz | more
> openssl-0.9.8k/apps/
> openssl-0.9.8k/apps/app_rand.c
> Downloading expat results in a corrupted file
> mvn -X wagon:download-single -Dwagon.fromFile=expat-1.98.8.tar.gz
> -Dwagon.url=http://prdownloads.sourceforge.net/expat -Dwagon.toDir=./
> $ tar tf expat-1.98.8.tar.gz
> tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Read 1943 bytes from expat-1.98.8.tar.gz
> tar: Error exit delayed from previous errors
--
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: (MNG-4181) system path dependencies are not resolved
[
http://jira.codehaus.org/browse/MNG-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181524#action_181524
]
Benjamin Bentmann commented on MNG-4181:
Norbert, the cause for your issue is captured by MNG-4148.
> system path dependencies are not resolved
> -
>
> Key: MNG-4181
> URL: http://jira.codehaus.org/browse/MNG-4181
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.1.0
> Environment: Windows Vista
>Reporter: Karsten Ohme
>Priority: Critical
>
> If a system path dependency is used, the depencies are not included.
> I cannot build my project anymore and I'm stuck.
> This is the error I get:
> [WARNING] POM for 'net.sf:microlog-instrument:pom:1.1.1:compile' is invalid.
> Its dependencies (if any) will NOT be available to the current build.
> [DEBUG] Reason: Failed to validate POM for project net.sf:microlog-instrument
> at
> Artifact [net.sf:microlog-instrument:pom:1.1.1:compile]
> [DEBUG]
> Validation Errors:
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=jsr21
> 1, version=2.2, type=jar}: system-scoped dependency must specify an absolute
> pat
> h systemPath.
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=jsr08
> 2, version=2.2, type=jar}: system-scoped dependency must specify an absolute
> pat
> h systemPath.
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=jsr75
> , version=2.2, type=jar}: system-scoped dependency must specify an absolute
> path
> systemPath.
> [DEBUG] For managed dependency Dependency {groupId=com.sun.wtk,
> artifactId=wma20
> , version=2.2, type=jar}: system-scoped dependency must specify an absolute
> path
> systemPath.
--
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: (WAGON-264) compressed tarball download problems
[ http://jira.codehaus.org/browse/WAGON-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181523#action_181523 ] John Casey commented on WAGON-264: -- The wagon-maven-plugin will have to adjust (and be re-released) to handle httpConfiguration, I would expect. That is, unless it deals with the WagonManager component from maven-artifact-manager, which in turn handles Wagon instances that are configured using entries in the settings.xml...which IMO is probably a good practice for it to do... > compressed tarball download problems > > > Key: WAGON-264 > URL: http://jira.codehaus.org/browse/WAGON-264 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http-lightweight >Affects Versions: 1.0-beta-2, 1.0-beta-3, 1.0-beta-4, 1.0-beta-5 >Reporter: Lee Thompson >Assignee: John Casey > Fix For: 1.0-beta-6 > > > HTTP wagon will uncompress tarballs it downloads, sometimes badly. > Downloading openssl results in an unpressed download > $ mvn -X wagon:download-single -Dwagon.fromFile=openssl-0.9.8k.tar.gz > -Dwagon.url=http://www.openssl.org/source -Dwagon.toDir=./ > $ tar tzf openssl-0.9.8k.tar.gz > gzip: stdin: not in gzip format > tar: Child returned status 1 > tar: Error exit delayed from previous errors > $ tar tf openssl-0.9.8k.tar.gz | more > openssl-0.9.8k/apps/ > openssl-0.9.8k/apps/app_rand.c > Downloading expat results in a corrupted file > mvn -X wagon:download-single -Dwagon.fromFile=expat-1.98.8.tar.gz > -Dwagon.url=http://prdownloads.sourceforge.net/expat -Dwagon.toDir=./ > $ tar tf expat-1.98.8.tar.gz > tar: This does not look like a tar archive > tar: Skipping to next header > tar: Read 1943 bytes from expat-1.98.8.tar.gz > tar: Error exit delayed from previous errors -- 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: (MANT-52) NullPointerException when maven-javadoc-plugin configuration defines multiple group elements within a groups list element.
[
http://jira.codehaus.org/browse/MANT-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MANT-52:
--
Affects Version/s: (was: 2.2)
2.1
> NullPointerException when maven-javadoc-plugin configuration defines multiple
> group elements within a groups list element.
> --
>
> Key: MANT-52
> URL: http://jira.codehaus.org/browse/MANT-52
> Project: Maven 2.x Ant Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: $ mvn --version
> Maven version: 2.0.10
> Java version: 1.6.0_0
> OS name: "linux" version: "2.6.29-gentoo-r3" arch: "amd64" Family: "unix"
>Reporter: Alistair Bush
> Attachments: maven-ant-plugin.patch
>
>
> When attempting to run mvn ant:ant on sesame-2.2.4 available here [1]. A
> NullPointerException is raised. [2] for build log segment.
> It seems that when a pom ( or a parents pom ) defines the following
> configuration the existing code the error was occuring. I have assumed in my
> patch that this is the only valid way of defining groups. But at least the
> fix is small and easy for you to figure out.
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> true
> 1.5
>
>
> Repository API
> org.openrdf.repository*
>
>
> RDF Model API
> org.openrdf.model*
>
> ...
> ...
>
>
> http://java.sun.com/j2se/1.5.0/docs/api/
>
> http://repository.aduna-software.org/docs/info.aduna/api/
>
>
> {code}
> [1] svn co http://repo.aduna-software.org/svn/org.openrdf/sesame/tags/2.2.4/
> [2]
> {noformat}
> [INFO] Building OpenRDF Sesame Core
>
> [INFO]task-segment: [ant:ant]
>
> [INFO]
>
> [INFO] [ant:ant]
>
> [INFO] Wrote Ant project for sesame-core to
> /home/alistair/gentoo/tmp/sesame-2.2.4/core
> [INFO]
>
>
> [INFO] Building OpenRDF Sesame: Model
>
> [INFO]task-segment: [ant:ant]
>
> [INFO]
>
>
> [INFO] [ant:ant]
>
> [INFO]
>
>
> [ERROR] FATAL ERROR
>
> [INFO]
>
>
> [INFO] null
>
> [INFO]
>
>
> [INFO] Trace
>
> java.lang.NullPointerException
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXml(PrettyPrintXMLWriter.java:151)
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXmlAttribute(PrettyPrintXMLWriter.java:166)
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:190)
> at
> org.apache.maven.plugin.ant.AntBuildWriterUtil.writeJavadocTask(AntBuildWriterUtil.java:473)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeJavadocTarget(AntBuildWriter.java:991)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:304)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:113)
> at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegm
[jira] Closed: (MANT-52) NullPointerException when maven-javadoc-plugin configuration defines multiple group elements within a groups list element.
[
http://jira.codehaus.org/browse/MANT-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MANT-52.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.2
Fixed in [r788423|http://svn.apache.org/viewvc?view=rev&revision=788423],
snapshot deployed.
> NullPointerException when maven-javadoc-plugin configuration defines multiple
> group elements within a groups list element.
> --
>
> Key: MANT-52
> URL: http://jira.codehaus.org/browse/MANT-52
> Project: Maven 2.x Ant Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: $ mvn --version
> Maven version: 2.0.10
> Java version: 1.6.0_0
> OS name: "linux" version: "2.6.29-gentoo-r3" arch: "amd64" Family: "unix"
>Reporter: Alistair Bush
>Assignee: Benjamin Bentmann
> Fix For: 2.2
>
> Attachments: maven-ant-plugin.patch
>
>
> When attempting to run mvn ant:ant on sesame-2.2.4 available here [1]. A
> NullPointerException is raised. [2] for build log segment.
> It seems that when a pom ( or a parents pom ) defines the following
> configuration the existing code the error was occuring. I have assumed in my
> patch that this is the only valid way of defining groups. But at least the
> fix is small and easy for you to figure out.
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> true
> 1.5
>
>
> Repository API
> org.openrdf.repository*
>
>
> RDF Model API
> org.openrdf.model*
>
> ...
> ...
>
>
> http://java.sun.com/j2se/1.5.0/docs/api/
>
> http://repository.aduna-software.org/docs/info.aduna/api/
>
>
> {code}
> [1] svn co http://repo.aduna-software.org/svn/org.openrdf/sesame/tags/2.2.4/
> [2]
> {noformat}
> [INFO] Building OpenRDF Sesame Core
>
> [INFO]task-segment: [ant:ant]
>
> [INFO]
>
> [INFO] [ant:ant]
>
> [INFO] Wrote Ant project for sesame-core to
> /home/alistair/gentoo/tmp/sesame-2.2.4/core
> [INFO]
>
>
> [INFO] Building OpenRDF Sesame: Model
>
> [INFO]task-segment: [ant:ant]
>
> [INFO]
>
>
> [INFO] [ant:ant]
>
> [INFO]
>
>
> [ERROR] FATAL ERROR
>
> [INFO]
>
>
> [INFO] null
>
> [INFO]
>
>
> [INFO] Trace
>
> java.lang.NullPointerException
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXml(PrettyPrintXMLWriter.java:151)
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXmlAttribute(PrettyPrintXMLWriter.java:166)
> at
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:190)
> at
> org.apache.maven.plugin.ant.AntBuildWriterUtil.writeJavadocTask(AntBuildWriterUtil.java:473)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeJavadocTarget(AntBuildWriter.java:991)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:304)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:113)
> at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)
> at
> org.apache.maven
[jira] Commented: (MNG-4182) Properties from profiles.xml are not replaced when builing in parent module
[
http://jira.codehaus.org/browse/MNG-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181525#action_181525
]
Benjamin Bentmann commented on MNG-4182:
Karsten, could you provide a minimal test project that demonstrates the issue?
> Properties from profiles.xml are not replaced when builing in parent module
> ---
>
> Key: MNG-4182
> URL: http://jira.codehaus.org/browse/MNG-4182
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.1.0
> Environment: Windows Vista
>Reporter: Karsten Ohme
>Priority: Critical
>
> When running a submodule in its own directory properties form a parent
> profiles.xml are honored.
> Trying to build in the parent, this properties are not honored. The
> properties are not replaced.
> I get this result with help:effective-pom. See the ${appletkeyalias} instead
> of the proper replacment.
>
> maven-jar-plugin
> 2.2
>
>
> package
>
> sign
>
>
>
>
> ../${keystore}
> ${appletkeyalias}
> ${keystorepass}
>
> C:\Users\widerstand_2\Documents\mobifetch\apps\coupon\j2se
> coupon-install-applet\target/coupon-install-applet-1.0.2-SNAPSHOT-jar-with-depe
> dencies.jar
>
> C:\Users\widerstand_2\Documents\mobifetch\apps\coupon\j2
> e\coupon-install-applet\target/signed/coupon-install-applet-1.0.2-SNAPSHOT-jar-
> ith-dependencies.jar
> true
>
>
--
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: (MPDF-16) Add German translation
Add German translation -- Key: MPDF-16 URL: http://jira.codehaus.org/browse/MPDF-16 Project: Maven 2.x PDF Plugin Issue Type: Wish Affects Versions: 1.0 Reporter: Benjamin Bentmann Priority: Minor -- 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: (MPDF-16) Add German translation
[ http://jira.codehaus.org/browse/MPDF-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPDF-16. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 1.1 Done in [r788460|http://svn.apache.org/viewvc?view=rev&revision=788460]. > Add German translation > -- > > Key: MPDF-16 > URL: http://jira.codehaus.org/browse/MPDF-16 > Project: Maven 2.x PDF Plugin > Issue Type: Wish >Affects Versions: 1.0 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 1.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-427) ComponentsXmlArchiverFileFilter misses component descriptors on Windows
ComponentsXmlArchiverFileFilter misses component descriptors on Windows
---
Key: MASSEMBLY-427
URL: http://jira.codehaus.org/browse/MASSEMBLY-427
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-4
Reporter: Benjamin Bentmann
The {{ComponentsXmlArchiverFileFilter}} detects descriptors by equality with
the string "META-INF/plexus/components.xml" which fails for resource
collections that use the backslash as separator. Just see the existing IT
"descriptor-refs\jar-with-dependencies\component-descriptors-merged\pom.xml".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MASSEMBLY-427) ComponentsXmlArchiverFileFilter misses component descriptors on Windows
[
http://jira.codehaus.org/browse/MASSEMBLY-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MASSEMBLY-427.
---
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.2-beta-5
Fixed in [r788498|http://svn.apache.org/viewvc?view=rev&revision=788498].
> ComponentsXmlArchiverFileFilter misses component descriptors on Windows
> ---
>
> Key: MASSEMBLY-427
> URL: http://jira.codehaus.org/browse/MASSEMBLY-427
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-4
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 2.2-beta-5
>
>
> The {{ComponentsXmlArchiverFileFilter}} detects descriptors by equality with
> the string "META-INF/plexus/components.xml" which fails for resource
> collections that use the backslash as separator. Just see the existing IT
> "descriptor-refs\jar-with-dependencies\component-descriptors-merged\pom.xml".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-242) The "remote" archchetype-catalog doesn't really exist.
[ http://jira.codehaus.org/browse/ARCHETYPE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181547#action_181547 ] Tamás Cservenák commented on ARCHETYPE-242: --- Not quite true. Central is meant only as "convenience" artifact source, nobody should use it directly anyway. All Maven users should use some sort of MRM (Maven Repository Manager, http://maven.apache.org/repository-management.html) For example, using Nexus OSS or Pro (http://nexus.sonatype.org/) together with Nexus Archetype Plugin (https://docs.sonatype.org/display/Nexus/Nexus+Archetype+Plugin) gives you exactly that: "live" archetype catalogs. When you deploy an archetype, it immediately gets listed in catalog, and is available to all other consumers of the repository. > The "remote" archchetype-catalog doesn't really exist. > -- > > Key: ARCHETYPE-242 > URL: http://jira.codehaus.org/browse/ARCHETYPE-242 > Project: Maven Archetype > Issue Type: Bug >Reporter: Jörg Henne >Priority: Minor > > This page > http://maven.apache.org/plugins/maven-archetype-plugin/specification/archetype-catalog.html > states that the default "remote" catalog is located at > http://repo1.maven.org/maven2/archetype-catalog.xml. However, there is no > such file on repo1.maven.org and thus the remote catalog is useless. -- 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-4201) Custom packaging break in trunk (rev 784628)
[
http://jira.codehaus.org/browse/MNG-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MNG-4201:
--
Fix Version/s: 3.0-alpha-3
> Custom packaging break in trunk (rev 784628)
>
>
> Key: MNG-4201
> URL: http://jira.codehaus.org/browse/MNG-4201
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-3
>Reporter: Olivier Lamy
>Priority: Blocker
> Fix For: 3.0-alpha-3
>
>
> Custom packaging doesn't.
> Log output :
> {code}
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecycleExecutor.java:784)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:58)
> at
> org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:174)
> at
> org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:100)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:109)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:84)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:193)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:239)
> at
> org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:181)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:91)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:534)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:167)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun{code}
> {code}
> By example try to run a hudson plugin or run its for the maven-zip-plugin
> which in the maven plugins sandbox.
--
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-329) infinite build loop during site generation
[ http://jira.codehaus.org/browse/MSITE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181554#action_181554 ] Benson Margulies commented on MSITE-329: I appear to be seeing this with 2.0. with site:stage > infinite build loop during site generation > -- > > Key: MSITE-329 > URL: http://jira.codehaus.org/browse/MSITE-329 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: Maven 2.0.9; Sun JDK 1.6.0_06; Linux Ubuntu 8.04 >Reporter: Alessio Pace > Fix For: 2.0-beta-6 > > > My multi module project can be correctly built from the top most parent > module with a simple mvn -DskipTests clean install, but trying instead to > perform a mvn -DskipTests clean site causes an infinite loop in the build > process, where the overall build and site generation is performed all and all > over again. -- 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-4215) Review and fix hashCode/equals methods of ArtifactRepository implementations
[ http://jira.codehaus.org/browse/MNG-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko updated MNG-4215: Attachment: MNG-4215.patch Proposed fix > Review and fix hashCode/equals methods of ArtifactRepository implementations > > > Key: MNG-4215 > URL: http://jira.codehaus.org/browse/MNG-4215 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Reporter: Igor Fedorenko > Attachments: MNG-4215.patch > > > DefaultMavenMetadataCache relies on proper hashCode/equals of > ArtifactRepository and quick checks that at least some implementations do not > honour hashCode/equals contract (for example, > DelegatingLocalArtifactRepository and ReactorArtifactRepository). -- 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: (MSITE-409) Incorrect URLs in multi-module project
Incorrect URLs in multi-module project -- Key: MSITE-409 URL: http://jira.codehaus.org/browse/MSITE-409 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0 Reporter: Benson Margulies I have a top-level pom and some modules. One of the modules serves as a parent for most, but not all, of the rest. Thus, for most, the parent is ../parent, and for that the parent is the top-level project itself. I ran: mvn site:stage -DstagingDirectory=/Users/benson/stage It takes a very long time. All of my child links came out incorrectly: e.g: RLPJ Buildtools There aren't distinct subdirectories in the staged dir for those of my modules that use the parent. Actually, now that I look, I see that the ones that parent into ../parent are subdirectories of 'parent' instead of subdirectories of the top-level. But the links are still all wrong. -- 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-409) Incorrect URLs in multi-module project
[
http://jira.codehaus.org/browse/MSITE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181557#action_181557
]
Benson Margulies commented on MSITE-409:
I turn out to have hit two problems here. One is MSITE-395. The other has to do
with parent structure, so I'll detail it more clearly.
{noformat}
pom.xml
|
---
| | | |
parent mod1 mod2 mod3
{noformat}
In, say, mod1, the pom.xml declares the parent to have a relative path of
../parent.
In parent, the parent is the toplevel project.
If I run the site plugin at toplevel, the modN modules have their sites
generated inside of the directory of the parent module. Explicitly declaring
the URL doesn't help. I guess explicitly declaring the distributionManagement
URL might help.
> Incorrect URLs in multi-module project
> --
>
> Key: MSITE-409
> URL: http://jira.codehaus.org/browse/MSITE-409
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0
>Reporter: Benson Margulies
>
> I have a top-level pom and some modules. One of the modules serves as a
> parent for most, but not all, of the rest.
> Thus, for most, the parent is ../parent, and for that the parent is the
> top-level project itself.
> I ran:
> mvn site:stage -DstagingDirectory=/Users/benson/stage
> It takes a very long time.
> All of my child links came out incorrectly: e.g:
> href="../../Users/benson/x/trunk/greenhouse/etrog/../../../../hudson.basistech.net/home/projects/etrog">RLPJ
> Buildtools
> There aren't distinct subdirectories in the staged dir for those of my
> modules that use the parent. Actually, now that I look, I see that the ones
> that parent into ../parent are subdirectories of 'parent' instead of
> subdirectories of the top-level. But the links are still all wrong.
--
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: (MRELEASE-455) Doesn't update the versions correctly if end tag is on a seperate line
[
http://jira.codehaus.org/browse/MRELEASE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Catherine Tan closed MRELEASE-455.
Resolution: Fixed
Fix Version/s: 2.0-beta-9
This seems to be fixed in 2.0-beta-9
> Doesn't update the versions correctly if end tag is on a seperate line
> --
>
> Key: MRELEASE-455
> URL: http://jira.codehaus.org/browse/MRELEASE-455
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-8
>Reporter: Maria Catherine Tan
> Fix For: 2.0-beta-9
>
> Attachments: MRELEASE-455.patch
>
>
> {noformat}
>
>
> com.test
>
> test
>
> 1.0-SNAPSHOT
>
>
> {noformat}
> The released artifact contains snapshot dependency of com.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] Created: (MNG-4219) update plexus-utils to avoid leaking processes in CommandLineUtils.getSystemEnvars()
update plexus-utils to avoid leaking processes in CommandLineUtils.getSystemEnvars() Key: MNG-4219 URL: http://jira.codehaus.org/browse/MNG-4219 Project: Maven 2 Issue Type: Bug Components: Performance Affects Versions: 2.2.0 Reporter: John Casey Not long ago, it was discovered that CommandLineUtils leaks processes in come circumstances (in older versions of plexus-utils) because it fails to read stderr. Later versions of plexus-utils (1.5.11 and above) have fixed this problem. Interestingly, Hudson has had a persistent problem with leaking processes on the Windows slave VM out on https://grid.sonatype.org/ci/ - I'm pretty sure this will help alleviate those issues. We should move up to the latest version of plexus-utils to take advantage of this bugfix. -- 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-4219) update plexus-utils to avoid leaking processes in CommandLineUtils.getSystemEnvars()
[ http://jira.codehaus.org/browse/MNG-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-4219. --- Assignee: John Casey Resolution: Fixed Fix Version/s: 2.2.0 had to adjust some old imports that used interpolation classes from plexus-utils, since it seems that plexus-interpolation is no longer shaded into plexus-utils. This is no problem, as it really only served to highlight a latent problem in Maven's source. The code in plexus-utils has been a delegator pattern for some time now... > update plexus-utils to avoid leaking processes in > CommandLineUtils.getSystemEnvars() > > > Key: MNG-4219 > URL: http://jira.codehaus.org/browse/MNG-4219 > Project: Maven 2 > Issue Type: Bug > Components: Performance >Affects Versions: 2.2.0 >Reporter: John Casey >Assignee: John Casey > Fix For: 2.2.0 > > > Not long ago, it was discovered that CommandLineUtils leaks processes in come > circumstances (in older versions of plexus-utils) because it fails to read > stderr. Later versions of plexus-utils (1.5.11 and above) have fixed this > problem. > Interestingly, Hudson has had a persistent problem with leaking processes on > the Windows slave VM out on https://grid.sonatype.org/ci/ - I'm pretty sure > this will help alleviate those issues. We should move up to the latest > version of plexus-utils to take advantage of this bugfix. -- 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] Reopened: (MNG-4219) update plexus-utils to avoid leaking processes in CommandLineUtils.getSystemEnvars()
[ http://jira.codehaus.org/browse/MNG-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey reopened MNG-4219: - need to update plexus-interpolation as well to avoid process leaks there related to the envar value source. > update plexus-utils to avoid leaking processes in > CommandLineUtils.getSystemEnvars() > > > Key: MNG-4219 > URL: http://jira.codehaus.org/browse/MNG-4219 > Project: Maven 2 > Issue Type: Bug > Components: Performance >Affects Versions: 2.2.0 >Reporter: John Casey >Assignee: John Casey > Fix For: 2.2.0 > > > Not long ago, it was discovered that CommandLineUtils leaks processes in come > circumstances (in older versions of plexus-utils) because it fails to read > stderr. Later versions of plexus-utils (1.5.11 and above) have fixed this > problem. > Interestingly, Hudson has had a persistent problem with leaking processes on > the Windows slave VM out on https://grid.sonatype.org/ci/ - I'm pretty sure > this will help alleviate those issues. We should move up to the latest > version of plexus-utils to take advantage of this bugfix. -- 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: (ARCHETYPE-248) can not support i18n
can not support i18n -- Key: ARCHETYPE-248 URL: http://jira.codehaus.org/browse/ARCHETYPE-248 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 2.0-alpha-4 Environment: OS:simple chinese windows XP ,develop tools: eclipse 3.4(wtp),maven 2.0.9. Reporter: 李凤文 Priority: Blocker Attachments: error.bmp if the *.java file contains chinese Symbol ( javadoc ) , after create a project that the chinese Symbol not display correct. -- 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-4189) Maven not picking up specific timestamped version dependency when a later timestamped version was downloaded and already present in the local repository
[ http://jira.codehaus.org/browse/MNG-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MNG-4189. - Resolution: Fixed Fix Version/s: (was: 2.2.x) 2.1.1 Fix committed in 2.1.x branch -r788583 and merged to 2.2.x branch -r788596. Integration tests committed in core-integration-testing trunk -r788584. > Maven not picking up specific timestamped version dependency when a later > timestamped version was downloaded and already present in the local repository > > > Key: MNG-4189 > URL: http://jira.codehaus.org/browse/MNG-4189 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, General >Affects Versions: 2.0.9, 2.1.0 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 2.1.1 > > Attachments: MNG-4189-core-integration-testing.patch, > MNG-4189-maven-2.1.x.patch, MNG-4189.patch, mng-4189.zip > > > To reproduce this issue: > # Create a project (let's call this projectA) with a class named ClassA > having a method named methodA(). Set the version as 1.0-SNAPSHOT and set > uniqueVersion=true. > # Deploy this in a remote repository > # Create another project (let's call this projectB) which has a dependency on > projectA. Set the dependency's version to the specific timestamped version > when projectA was deployed in step 2. Create a class named ClassB and add a > method which invokes ClassA's methodA(). > # Add your remote repository either in the settings or in the pom. > # Build projectB. You will get a successful build. > # Now go back to projectA and remove methodA() from classA. > # Deploy projectA to the remote repository again. > # Update the dependency version of projectA in projectB's pom.xml. Set it to > the latest timestamp version. > # Build projectB. Your build will fail because methodA() was removed. > # Revert the dependency version of projectA in projectB's pom.xml. Set it to > the same value you've set in step 3. > # Build projectB. Your build will still fail even though you've set the > correct version. -- 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: (MPDF-17) Test fails with JDK 1.5+ if base directory has a space in its path
Test fails with JDK 1.5+ if base directory has a space in its path
--
Key: MPDF-17
URL: http://jira.codehaus.org/browse/MPDF-17
Project: Maven 2.x PDF Plugin
Issue Type: Bug
Affects Versions: 1.0
Environment: windows (I guess), jdk 1.5+
Reporter: Lukas Theussl
stack trace posted by Benjamin:
{noformat}
---
Test set: org.apache.maven.plugins.pdf.PdfMojoTest
---
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 15.453 sec <<<
FAILURE!
testITextImpl(org.apache.maven.plugins.pdf.PdfMojoTest) Time elapsed: 2.594
sec <<< ERROR!
org.apache.maven.plugin.MojoExecutionException: Error during document generation
at org.apache.maven.plugins.pdf.PdfMojo.execute(PdfMojo.java:269)
at
org.apache.maven.plugins.pdf.PdfMojoTest.testITextImpl(PdfMojoTest.java:89)
Caused by: org.apache.maven.doxia.docrenderer.DocumentRendererException: Error
transforming Document [#document: null]: java.io.FileNotFoundException:
M:\Neuer%20Ordner\maven-pdf-plugin-1.0\target\test-output\pdf\maven-pdf-plugin-doc.xml
(Das System kann den angegebenen Pfad nicht finden)
at
org.apache.maven.doxia.docrenderer.pdf.itext.ITextPdfRenderer.transform(ITextPdfRenderer.java:485)
at
org.apache.maven.doxia.docrenderer.pdf.itext.ITextPdfRenderer.render(ITextPdfRenderer.java:178)
at
org.apache.maven.doxia.docrenderer.AbstractDocumentRenderer.render(AbstractDocumentRenderer.java:109)
at org.apache.maven.plugins.pdf.PdfMojo.execute(PdfMojo.java:260)
... 27 more
{noformat}
--
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
