[jira] Created: (MCOMPILER-140) Compiler error messages do not contain drive letter on windows
Compiler error messages do not contain drive letter on windows --- Key: MCOMPILER-140 URL: http://jira.codehaus.org/browse/MCOMPILER-140 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.3.2, 2.3.1, 2.3, 2.2, 2.1 Environment: Maven 2.2.1, Windows Reporter: Anton Makeev Attachments: WidgetCore.zip See original bug request: http://youtrack.jetbrains.net/issue/IDEA-59521 User description: I tried it with a toy project and it worked as you say. The errors in the console for the toy project had the complete path in the error: [INFO] Compilation failure C:\projects\java\eclipseOnly\WidgetCore\src\main\java\com\acme\core\CoreClass.java:[6,8] not a statement C:\projects\java\eclipseOnly\WidgetCore\src\main\java\com\acme\core\CoreClass.java:[6,14] ';' expected In my non-toy project where I'm seeing the error, the C: is not there. [ERROR] COMPILATION ERROR : [INFO] [ERROR] \projects\java\eclipseproj\MyProj\unittests\com\acme\messaging\configuration\ConfigurationTest.java:[12,8] not a statement [ERROR] \projects\java\eclipseproj\MyProj\unittests\com\acme\messaging\configuration\ConfigurationTest.java:[12,14] ';' expected -- 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: (MSHARED-78) FilteringUtils escapeWindowsPath() doesn't work on Windows
[ http://jira.codehaus.org/browse/MSHARED-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170311#action_170311 ] Anton Makeev commented on MSHARED-78: - I reckon not only the windows paths should be escaped, but all the properties filtered. For example, if I have a property defined as xxx\yyy:zzz it will be read from the *.properties file incorrectly as well. Thanks, Anton Makeev > FilteringUtils escapeWindowsPath() doesn't work on Windows > -- > > Key: MSHARED-78 > URL: http://jira.codehaus.org/browse/MSHARED-78 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-filtering >Affects Versions: maven-filtering-1.0-beta-2 >Reporter: Marvin Froeder >Assignee: Olivier Lamy > Fix For: maven-filtering-1.0-beta-4 > > Attachments: filtering.patch, FilteringUtilsTest.java > > > The method escapeWindowsPath() is replacing colon by backslash + colon. > I.e. > D:\temp > is escaped as > D\:\\temp > But windows doesn't recognize that. If you try to open D\:\\temp on > explorer, will not work. > Even java.io.File is not able to handle that too. The attached test proves > it. > I'm not sure why this backslash was add to colon, but commenting line 44 of > org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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-3670) Running 'compile' goal on specific project leads to exception.
Running 'compile' goal on specific project leads to exception.
--
Key: MNG-3670
URL: http://jira.codehaus.org/browse/MNG-3670
Project: Maven 2
Issue Type: Bug
Components: Embedding
Affects Versions: 2.1
Reporter: Anton Makeev
Attachments: problem.zip
The exception arises if particular artifacts have not been downloaded yet.
{code}
org.apache.maven.wagon.observers.ChecksumObserver.transferStarted(ChecksumObserver.java:68)
org.apache.maven.wagon.events.TransferEventSupport.fireTransferStarted(TransferEventSupport.java:106)
org.apache.maven.wagon.AbstractWagon.fireGetStarted(AbstractWagon.java:528)
org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:293)
org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:274)
org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:97)
org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
org.apache.maven.artifact.manager.DefaultWagonManager.verifyChecksum(DefaultWagonManager.java:733)
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:577)
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:424)
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:341)
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:167)
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:552)
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:233)
org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:132)
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:509)
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:539)
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:132)
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:347)
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:321)
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:289)
org.apache.maven.plugin.DefaultPluginManager.getPluginArtifacts(DefaultPluginManager.java:436)
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:279)
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:211)
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:186)
org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:79)
org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:52)
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.loadPluginDescriptor(DefaultBuildPlanner.java:322)
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.findForkModifiers(DefaultBuildPlanner.java:192)
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.addForkedLifecycleModifiers(DefaultBuildPlanner.java:179)
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody0(DefaultBuildPlanner.java:117)
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody1$advice(DefaultBuildPlanner.java:403)
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:1)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:400)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:235)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3479) Maven Embedder incorrectly resolves properties in multiprojects and incorrectly resolves dependency management for POM dependencies
[ http://jira.codehaus.org/browse/MNG-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128364#action_128364 ] Anton Makeev commented on MNG-3479: --- Yes, we use 2.1-SNAPSHOT. Currently, the bundled version is of 2008-02-12. > Maven Embedder incorrectly resolves properties in multiprojects and > incorrectly resolves dependency management for POM dependencies > --- > > Key: MNG-3479 > URL: http://jira.codehaus.org/browse/MNG-3479 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.0.8 >Reporter: Ben Gidley > Attachments: MultiprojectTestCase.patch > > > Maven Embedder incorrectly resolves properties in multiprojects and > incorrectly resolves dependency management for POM dependencies > This was first noticed using IntelliJ embedder - see JIRA's are > * http://www.jetbrains.net/jira/browse/IDEA-17318 - Parent POM properties are > not working in child POM's > * http://www.jetbrains.net/jira/browse/IDEA-17320 - Dependency Management > section is not cascading correctly > The first issue prevents maven embedder from parsing a child POM that uses a > parent POM to set the version of an artifact, if the parent POM using > properties to set the version. > The second issue shows even if you set the version explicitly the parent > POM's dependency management section does not cascade in embedder (but it does > in maven) correctly for POM type dependencies. > I have written a unit test (attached) to embedder to test for this. But am > unsure how to 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
[jira] Created: (MNG-3386) Specific dependencies list makes the embedder to set 'varsionRange' for one of them to 'null'
Specific dependencies list makes the embedder to set 'varsionRange' for one of
them to 'null'
-
Key: MNG-3386
URL: http://jira.codehaus.org/browse/MNG-3386
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.1
Reporter: Anton Makeev
Priority: Minor
For the following project the embedder resolves a transitive dependency of
'ws-commons-util' named 'xml-apis:xml-apis:jar:1.0.b2:compile' and sets its
'versionRange' into null. I dunno wheither it's a bug or intended behaviour,
but changing the order of dependencies or removing 'dom4j' seems to solve the
problem.
{code}
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";>
4.0.0
test
project
1
dom4j
dom4j
1.6.1
runtime
org.apache.ws.commons.util
ws-commons-util
1.0.2
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3339) Embedder does not resolve transitive dependencies in multi-module project, unless the modules were installed into local repository previously.
Embedder does not resolve transitive dependencies in multi-module project, unless the modules were installed into local repository previously. -- Key: MNG-3339 URL: http://jira.codehaus.org/browse/MNG-3339 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.1 Reporter: Anton Makeev Attachments: transitive-deps.zip I've attached the project that have three modules: m1 (depends on m2) m2 (depends on m3) m3 (depends on junit) all the dependencies are of the 'compile' scope. I would expect that embedder resolves dependencies for m1 into m2, m3, and junit. But it doesn't do that if repository does not contain these modules installed. The only dependency is the direct one (m2). On the other hand, if I previously install the entire project into repository, I'll have the expected behaviour. -- 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
