[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=160884#action_160884 ] Casey Butterworth commented on MSHARED-78: -- Unless there's a workaround that I'm not aware of, this defect is effectively rendering the 2.3 resources plugin unusable for any projects that uses resource filtering to directory locations (e.g. basedir) on windows, which I imagine is a large number of projects. MRESOURCES-81 is a good description of the problem. I've noticed that this is targeted at maven-filtering-1.0-beta-4, but i'm wondering if it should not be in the next release instead, and also be accompanied by a maven-release-plugin release? > 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 > Fix For: maven-filtering-1.0-beta-4 > > Attachments: 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] Commented: (MPMD-86) Using JDK 1.5 causes ParseException: Can't use generics unless running in JDK 1.5 mode!
[ http://jira.codehaus.org/browse/MPMD-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160878#action_160878 ] Paul Sundling commented on MPMD-86: --- When running site, it can also give this error if using JDK 1.6 and using targetJdk of 1.6 instead. It seems to expect 1.5 specifically. > Using JDK 1.5 causes ParseException: Can't use generics unless running in JDK > 1.5 mode! > --- > > Key: MPMD-86 > URL: http://jira.codehaus.org/browse/MPMD-86 > Project: Maven 2.x PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 2.4 > Environment: JAVA 1.5, Maven 2.0.9 >Reporter: Debabrat Panda >Assignee: Benjamin Bentmann > > While running PMD with Maven i am getting parsing error "Error while parsing > ../../../java file" > The errors are > 1. Can't use generics unless running in JDK 1.5 mode! > 2. Can't use static imports when running in JDK 1.4 mode! > Can't use annotations when running in JDK 1.4 mode! > Any help will be appreciated. > Thanks in advance. -- 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: (MPMD-67) Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode!
[ http://jira.codehaus.org/browse/MPMD-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160864#action_160864 ] Paul Sundling commented on MPMD-67: --- I don't think the typo is the issue. I think you have to specify targetJdk to be 1.5 even if you're using JDK 1.6 This failed with lots of errors "Can't use generics unless running in JDK 1.5 mode": org.apache.maven.plugins maven-pmd-plugin 1.6 even though I'm using JDK 1.6 for compiler plugin settings and an actual JDK 1.6. But if I change that to 1.5 Then it quits failing. I think it should work even if we have a later setting than 1.5! This bug should be reopened or another one created. This is using version PMD 2.4 Now for the strange part. This behavior happens when doing 'mvn site:site site:deploy', but NOT when running 'mvn pmd:pmd' directly. > Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK > 1.5 mode! > --- > > Key: MPMD-67 > URL: http://jira.codehaus.org/browse/MPMD-67 > Project: Maven 2.x PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 2.2 > Environment: Maven 2.0.8 > JDK 1.6 >Reporter: Will Hoover >Assignee: Dennis Lundberg > Fix For: 2.3 > > > While using Maven PMD plugin with: > > org.apache.maven.plugins > maven-pmd-plugin > 2.2 > > true > utf-8 > 100 > > 1.6 > > > > **/generated/*.java > > > > I get the following error even though JDK is 1.6: > [WARNING] Failure executing PMD for: SomeGenericJavaClass.java > net.sourceforge.pmd.PMDException: Error while parsing > SomeGenericJavaClass.java > at net.sourceforge.pmd.PMD.processFile(PMD.java:104) > at net.sourceforge.pmd.PMD.processFile(PMD.java:64) > at net.sourceforge.pmd.PMD.processFile(PMD.java:150) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:228) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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.classworld
[jira] Closed: (MNG-3990) CLONE -ERROR: JAVA_HOME is set to an invalid directory.... even when the JAVA_HOME is set correctly
[ http://jira.codehaus.org/browse/MNG-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thad Cox closed MNG-3990. - Resolution: Not A Bug Please Ignore this, put in the wrong project. > CLONE -ERROR: JAVA_HOME is set to an invalid directory even when the > JAVA_HOME is set correctly > > > Key: MNG-3990 > URL: http://jira.codehaus.org/browse/MNG-3990 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 > Environment: Windows Vista >Reporter: Thad Cox > Fix For: 2.0.9 > > > ERROR: JAVA_HOME is set to an invalid directory. > JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03;C:\jai-1_1_2 > Please set the JAVA_HOME variable in your environment to match the > location of your Java installation > My JAVA_HOME is set perfectly ( i checked java.exe set on C:\Program > Files\Java\jdk1.6.0_03\bin\) JAI and JMF all working ... javac and rest of > the commands also work so i guess i good with it. > i tried the following options: > 1.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03;C:\jai-1_1_2 > 2.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03; > 3.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03\ > 4.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03;C:\jai-1_1_2; > I put JAVA_HOME in both user enviroment variables and system one still didn't > work. > I copy pasted the path from the browser so i can't be wrong in that. > I have nothing more to try ... any Idea's ? -- 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-3990) CLONE -ERROR: JAVA_HOME is set to an invalid directory.... even when the JAVA_HOME is set correctly
CLONE -ERROR: JAVA_HOME is set to an invalid directory even when the JAVA_HOME is set correctly Key: MNG-3990 URL: http://jira.codehaus.org/browse/MNG-3990 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.9 Environment: Windows Vista Reporter: Thad Cox Fix For: 2.0.9 ERROR: JAVA_HOME is set to an invalid directory. JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03;C:\jai-1_1_2 Please set the JAVA_HOME variable in your environment to match the location of your Java installation My JAVA_HOME is set perfectly ( i checked java.exe set on C:\Program Files\Java\jdk1.6.0_03\bin\) JAI and JMF all working ... javac and rest of the commands also work so i guess i good with it. i tried the following options: 1.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03;C:\jai-1_1_2 2.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03; 3.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03\ 4.) JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03;C:\jai-1_1_2; I put JAVA_HOME in both user enviroment variables and system one still didn't work. I copy pasted the path from the browser so i can't be wrong in that. I have nothing more to try ... any Idea's ? -- 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-3955) [regression] ${settings.localRepository} does not reflect actual repo path if maven.repo.local used
[
http://jira.codehaus.org/browse/MNG-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-3955.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-2
Fixed in [r734219|http://svn.eu.apache.org/viewvc?view=rev&revision=734219].
> [regression] ${settings.localRepository} does not reflect actual repo path if
> maven.repo.local used
> ---
>
> Key: MNG-3955
> URL: http://jira.codehaus.org/browse/MNG-3955
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-2
>
>
> For a command line like
> {noformat}
> mvn ... -D maven.repo.local=path
> {noformat}
> the plugin parameter expression {{${settings.localRepository}}} resolves to
> the path given in the global/user {{settings.xml}}, i.e. the override from
> CLI is not reflected.
--
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-179) should accept regexp to include/exclude specified jars
should accept regexp to include/exclude specified jars -- Key: MWAR-179 URL: http://jira.codehaus.org/browse/MWAR-179 Project: Maven 2.x War Plugin Issue Type: Improvement Affects Versions: 2.1-alpha-2 Environment: any Reporter: Matthew Grzechociński Priority: Minor It will be nice to be able to pass regular expression fo . Now we can only specify WEB-INF/lib/*.jar and it will exclude all jars. What if I have o profile in which I want to exclude all external libraries which are stored on server (and there are many of them) but I want to include submodules of my application. Copying dependencies to profile with provided creates my pom really messy. Summing up, It will be nice to set ^WEB-INF/lib/prefix*.jar to exclude all jars except those which starts with prefix. Can I expect this feature in the nearest future? -- 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-3989) Simple handling of external jars
Simple handling of external jars Key: MNG-3989 URL: http://jira.codehaus.org/browse/MNG-3989 Project: Maven 2 Issue Type: New Feature Affects Versions: 2.0.9 Reporter: Greg Wilkins For whatever reason, there will always be jars that don't exist in a maven repository. There are numerous techniques for these - installing them in your local repo (either manually or with some bootstrap.sh script or special profile activation). Checking in the jars into a local maven repository that is checked into svn and then point to it from your settings.xml and/or top level pom (with aid of an env variable). But all these methods lack a very important features. You can just do: "svn co http:/myproj.com/foo; cd foo; mvn" If the jars change, you can't just do "svn up; mvn", you have to re-run whatever script/profile installed the repo. It's all rather a PITA. What I want, is some way to have a module of a project that contains some non-maven jars that when I do a "mvn install" in that project, install those jars in my local repository for use by my other modules. If the jars are not updated, then nothing is done. With something like this, projects that have external dependencies could describe them to maven and make them available for use, without manual steps and special scripts. -- 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: (DOXIA-274) Broken link in "What is Doxia?" page
[ http://jira.codehaus.org/browse/DOXIA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160820#action_160820 ] Trevor Harmon commented on DOXIA-274: - So... where has aptconvert gone? It's a useful link; would be better to replace it instead of remove it. > Broken link in "What is Doxia?" page > > > Key: DOXIA-274 > URL: http://jira.codehaus.org/browse/DOXIA-274 > Project: Maven Doxia > Issue Type: Bug > Components: Documentation >Reporter: Trevor Harmon >Assignee: Lukas Theussl >Priority: Minor > Fix For: 1.1 > > > The following page has a broken link: > http://maven.apache.org/doxia/ > The link to "Aptconvert" is broken. -- 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-1911) Building plugins with extensions in a reactor fails
[ http://jira.codehaus.org/browse/MNG-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160815#action_160815 ] Marvin Froeder commented on MNG-1911: - Hi John, Do you have any news on that? Flex-mojos is suffering with this too. VELO > Building plugins with extensions in a reactor fails > --- > > Key: MNG-1911 > URL: http://jira.codehaus.org/browse/MNG-1911 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0.1 >Reporter: Guillaume Nodet >Assignee: John Casey >Priority: Critical > Fix For: 3.x > > > I have the following in my main pom > > > > > org.apache.servicemix.plugins > maven2-jbi-plugin > 1.0-SNAPSHOT > true > > > > > If i try to add it to the modules, the first time, maven complains that it > can not download the plugin. > If i remove the tag, all works, but i need 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] Closed: (MNG-3788) Profiles in profiles.xml not activated properly
[ http://jira.codehaus.org/browse/MNG-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3788. -- Assignee: Benjamin Bentmann Resolution: Duplicate Fix Version/s: (was: 2.0.x) > Profiles in profiles.xml not activated properly > --- > > Key: MNG-3788 > URL: http://jira.codehaus.org/browse/MNG-3788 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.9 > Environment: Windows XP Professional >Reporter: Walt Barrow >Assignee: Benjamin Bentmann > > I created a profiles.xml file with three profiles in it as shown below. When > I execute a Maven command like: > >mvn -f \pom.xml -PconwebDev ... > the properties defined by profile conwebFinal are used. I shuffled the > profiles around in the file and whichever one was defined last was the one > whose values took effect. It seems as if all profiles are being activated > and the last one wins. > When I put these same profiles in settings.xml or inside the main pom.xml, > everything works properly. > Here are the profiles: > > > > conwebDev > > conweb.properties > DEV > > > > > conwebTest > > conweb.properties > TEST > > > > conwebFinal > > conweb.properties > FINAL > > > -- 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-3933) Profiles.xml does not pickup OS family
[
http://jira.codehaus.org/browse/MNG-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3933:
---
Affects Version/s: 3.0-alpha-1
2.1.0-M1
Fix Version/s: 3.0-alpha-2
> Profiles.xml does not pickup OS family
> --
>
> Key: MNG-3933
> URL: http://jira.codehaus.org/browse/MNG-3933
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.9, 2.1.0-M1, 3.0-alpha-1
> Environment: Ubuntu 8.0.4 64-bit [2.6.24-21-generic #1 SMP Tue Oct 21
> 23:09:30 UTC 2008 x86_64 GNU/Linux] and
> Windows XP sp2 32-bit
>Reporter: sanjiv sahayam
>Assignee: Benjamin Bentmann
> Fix For: 2.0.11, 2.1.0-M2, 3.0-alpha-2
>
> Attachments: MNG-3933-set-activation-os-properly-when-converting.patch
>
>
> When using profiles.xml and specifying an OS family activator such as :
>
> unix
>
> The OS family is not detected and hence the profile never activates. I have
> verified this through mvn help:active-profiles. I have tried this on
> Windows(XP sp2) as well as Linux (Ubuntu 8.0.4). The only way I can get the
> profiles to activate is via systems properties:
>
>
> unix-profile
>
>
> and then use something of the form: mvn clean test -Dunix-profile.
> I've created an example that depends on a specific version of Junit depending
> on the OS. Unix depends on 4.5 and Windows on 3.8.
> Here's my profiles.xml:
> xmlns="http://maven.apache.org/PROFILES/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/PROFILES/1.0.0
> http://maven.apache.org/xsd/profiles-1.0.0.xsd";>
>
>
> unix
>
>
> unix
>
>
>
> 4.5
>
>
>
> windows
>
>
> windows
>
>
>
> 3.8
>
>
>
>
> Here's my pom.xml:
> 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
> au.maven.test
> profiles-bug
> 1.0-SNAPSHOT
>
>
> junit
> junit
> ${junit.version}
>
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
>
>
>
> The only way I can get the correct artefact to be used is via a system
> property.
--
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-3988) [regression] Profiles.xml is not processed
[
http://jira.codehaus.org/browse/MNG-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-3988.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 3.0-alpha-2
Fixed in [r734142|http://svn.eu.apache.org/viewvc?view=rev&revision=734142].
> [regression] Profiles.xml is not processed
> --
>
> Key: MNG-3988
> URL: http://jira.codehaus.org/browse/MNG-3988
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-2
>
>
> Various of the existing core ITs show that the {{profiles.xml}} isn't
> processed at all.
--
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-3988) [regression] Profiles.xml is not processed
[regression] Profiles.xml is not processed
--
Key: MNG-3988
URL: http://jira.codehaus.org/browse/MNG-3988
Project: Maven 2
Issue Type: Bug
Components: Profiles
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Various of the existing core ITs show that the {{profiles.xml}} isn't processed
at all.
--
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-382) Review IT failure on Windows
Review IT failure on Windows
Key: MASSEMBLY-382
URL: http://jira.codehaus.org/browse/MASSEMBLY-382
Project: Maven 2.x Assembly Plugin
Issue Type: Task
Affects Versions: 2.2-beta-3
Reporter: Benjamin Bentmann
Priority: Minor
Attachments: build.log
I observe the following IT failure on my WinXP box as well as on [Hudson's
Vista
box|https://grid.sonatype.org/ci/job/plugins-IT-with-maven-2.0.x/jdk=1.5,label=windows/53/console]:
{noformat}
[INFO] Building: container-descriptors\custom-containerDescriptorHandler\pom.xml
[INFO] ...FAILED. The post-build script returned false.
{noformat}
Attached is the {{build.log}} of this 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: (MANTRUN-104) Documentation for referring to artifacts classpaths is wrong
Documentation for referring to artifacts classpaths is wrong
Key: MANTRUN-104
URL: http://jira.codehaus.org/browse/MANTRUN-104
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.3
Reporter: Andreas Kohn
The documentation on
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html
claims that referring to the path of an artifact can be accomplished with
{code}
{code}
This is using the wrong separators, ':' does not work. Instead, one needs to
use '.', like this:
{code}
{code}
Also while there: it would be nice to have the documentation be clear about the
fact that the classifier part is only set if a classifier is defined on the
artifact. For an artifact without classifier, the property would be called
maven.dependency.my.group.id.my.artifact.id.jar.path.
And of course, 'jar' should be replaced by 'type' to match the other parts.
This information now has to be found by trying the documented way, seeing it
fail, and then scanning through the debug output which eventually says:
{quote}
[INFO] [antrun:run {execution: build}]
[DEBUG] Storing:
maven.dependency.rhino.js.jar.path=/home/andreask/.m2/repository/rhino/js/1.7R1/js-1.7R1.jar
{quote}
--
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: (DOXIA-274) Broken link in "What is Doxia?" page
[ http://jira.codehaus.org/browse/DOXIA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-274. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.1 The aptconvert site seems to have been removed, I removed the link. Thanks! > Broken link in "What is Doxia?" page > > > Key: DOXIA-274 > URL: http://jira.codehaus.org/browse/DOXIA-274 > Project: Maven Doxia > Issue Type: Bug > Components: Documentation >Reporter: Trevor Harmon >Assignee: Lukas Theussl >Priority: Minor > Fix For: 1.1 > > > The following page has a broken link: > http://maven.apache.org/doxia/ > The link to "Aptconvert" is broken. -- 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: (DOXIA-275) Block level elements are ignored in HTML output
[ http://jira.codehaus.org/browse/DOXIA-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160780#action_160780 ] Lukas Theussl commented on DOXIA-275: - As discussed on the mailing list [1], I think this is a won't fix. As I said there, I think that title/date/author is by definition meta-data, it's up to the processing Sink to decide what to do with it. If you are doing just a single-document translation (eg generate one pdf from one apt file), then the sink might use the meta-data to put title/author/date on a cover page, for instance. But the site plugin aggregates several source documents into one coherent site, I don;t think the default xhtml sink should make this meta information visible for every page (by default). If the author intents to show this information he should include it as content. Alternatives are to write a specialized sink, or include a flag to optionally include the meta-information. [1] http://www.nabble.com/Block-level-elements-do-not-appear-in-output-td21382546.html > Block level elements are ignored in HTML output > --- > > Key: DOXIA-275 > URL: http://jira.codehaus.org/browse/DOXIA-275 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Apt >Reporter: Trevor Harmon > > The APT format includes a facility for specifying the title, author, and date > of the document, as described here: > http://maven.apache.org/doxia/references/apt-format.html > For example: > -- > Title > -- > Author > -- > Date > However, after running "mvn site", these elements do not appear in the text > of the generated HTML. The title is only placed in the HTML's > element, not anywhere in the body. The author is in a tag, which > cannot be seen without looking at the source. And the date doesn't seem to be > put anywhere at all. -- 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-3986) Remote repos not being used if it is in a profile
[ http://jira.codehaus.org/browse/MNG-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160779#action_160779 ] Benjamin Bentmann commented on MNG-3986: Shane, this looks a duplicate of MNG-3970, can you confirm? > Remote repos not being used if it is in a profile > - > > Key: MNG-3986 > URL: http://jira.codehaus.org/browse/MNG-3986 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > Remote repos not being used if it is in an active profile. -- 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: (DOXIA-276) Typo in "Proposed Changes to the APT Format"
[ http://jira.codehaus.org/browse/DOXIA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-276. --- Resolution: Not A Bug Fixed, thanks! But please don't use JIRA to report typos in the wiki, just sign up and fix it yourself! :) > Typo in "Proposed Changes to the APT Format" > > > Key: DOXIA-276 > URL: http://jira.codehaus.org/browse/DOXIA-276 > Project: Maven Doxia > Issue Type: Bug > Components: Documentation >Reporter: Trevor Harmon >Priority: Trivial > > http://docs.codehaus.org/display/DOXIA/Proposed+Changes+to+the+APT+Format > "it's limitations" should be "its limitations" -- 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-381) Classpath entry of MANIFEST breaks jar filenames
Classpath entry of MANIFEST breaks jar filenames Key: MASSEMBLY-381 URL: http://jira.codehaus.org/browse/MASSEMBLY-381 Project: Maven 2.x Assembly Plugin Issue Type: Bug Reporter: Alexander Attachments: MANIFEST.MF See attached MANIFEST for an example. Solution: Add each jar file on a newline, and rename jar files which are longer than 72 chars. -- 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
