[jira] Created: (MASSEMBLY-539) Link to Assembly Descriptor Schemas (XSD) for 1.1.2 is broken
Link to Assembly Descriptor Schemas (XSD) for 1.1.2 is broken - Key: MASSEMBLY-539 URL: http://jira.codehaus.org/browse/MASSEMBLY-539 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Eric Lewis Priority: Minor At the bottom of http://maven.apache.org/plugins/maven-assembly-plugin/ there are links to the XSD files. The one for 1.1.2 points to http://maven.apache.org/xsd/assembly-1.1.1.xsd but should point to http://maven.apache.org/xsd/assembly-1.1.2.xsd Also, http://maven.apache.org/xsd/assembly-1.1.2.xsd is delivered as MIME type text/html instead of text/plain -- 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: (SUREFIRE-636) Wrong plugin parameter documentation for includes and excludes
Wrong plugin parameter documentation for includes and excludes -- Key: SUREFIRE-636 URL: http://jira.codehaus.org/browse/SUREFIRE-636 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Reporter: Eric Lewis Priority: Minor The documentation for the plugin parameters includes (http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#includes) and excludes (http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#excludes) states that it expects a "List of patterns (separated by commas) used to specify the tests that should be included/excluded in testing." However, that's not the case, as shown in http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-447) Redefined scope is ignored for dependencies
Redefined scope is ignored for dependencies --- Key: MASSEMBLY-447 URL: http://jira.codehaus.org/browse/MASSEMBLY-447 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-4 Reporter: Eric Lewis I have a dependency which is defined with test. In another project, however, it is redefined to runtime. Now, when I get the runtime dependencies with true false runtime *:sources the dependency is not included. -- 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: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Lewis closed MINSTALL-70.
--
Resolution: Fixed
Fix Version/s: 2.3
Sorry for that! I was using 2.2 without knowing.
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.3
>Reporter: Eric Lewis
> Fix For: 2.3
>
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="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";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {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] Commented: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191170#action_191170
]
Eric Lewis commented on MINSTALL-70:
Here's the output from {{mvn:help effective-pom}}
$ mvn help:effective-pom
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO] artifact org.apache.maven.plugins:maven-help-plugin: checking for
updates from Codehaus
[INFO]
[INFO] Building Spring LDAP Core
[INFO]task-segment: [help:effective-pom] (aggregator-style)
[INFO]
[INFO] [help:effective-pom {execution: default-cli}]
[INFO]
Effective POMs, after inheritance, interpolation, and profiles are applied:
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/xsd/maven-4.0.0.xsd";>
4.0.0
spring-ldap-parent
org.springframework.ldap
1.3.0.RELEASE
org.springframework.ldap
spring-ldap-core
1.3.0.RELEASE
Spring LDAP Core
...
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.3
>Reporter: Eric Lewis
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="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";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {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] Created: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
install-file should take the version from the parent if the version for the
artifact is missing in the POM
--
Key: MINSTALL-70
URL: http://jira.codehaus.org/browse/MINSTALL-70
Project: Maven 2.x Install Plugin
Issue Type: Bug
Components: install:install-file
Affects Versions: 2.3
Reporter: Eric Lewis
Spring Source seems to release POM which have no version. According to the
Maven philosophy this means that they inherit their parent's version.
However, if I try
{{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
-DpomFile=pom.xml}}
I get
{quote}
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'install'.
[INFO]
[INFO] Building Spring LDAP Core
[INFO]task-segment: [install:install-file] (aggregator-style)
[INFO]
[INFO] [install:install-file {execution: default-cli}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] An invalid artifact was detected.
This artifact might be in your project's POM, or it might have been included
transitively during the resolution process. Here is the information we do have
for this artifact:
o GroupID: org.springframework.ldap
o ArtifactID: spring-ldap-core
o Version: <<< MISSING >>>
o Type:pom
[INFO]
[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
empty.
{quote}
The POM looks like this:
{quote}
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";>
org.springframework.ldap
spring-ldap-parent
1.3.0.RELEASE
4.0.0
spring-ldap-core
jar
Spring LDAP Core
...
{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] Commented: (MENFORCER-83) Banned dependencies should support regular expressions
[ http://jira.codehaus.org/browse/MENFORCER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187572#action_187572 ] Eric Lewis commented on MENFORCER-83: - Sorry, I wasn't aware of the syntax in JIRA. The last sentence should read To be compatible, the wildcard * would be treated as regular expression .* > Banned dependencies should support regular expressions > -- > > Key: MENFORCER-83 > URL: http://jira.codehaus.org/browse/MENFORCER-83 > Project: Maven 2.x Enforcer Plugin > Issue Type: Improvement > Components: Standard Rules >Affects Versions: 1.0-beta-1 >Reporter: Eric Lewis > > The includes and excludes of the bannedDependencies rule support wildcards, > but only for an entire section. > They should be enhanced to support regular expressions. > For instance instead of having > > my.company:abc-api > my.company:def-api > my.company:ghi-api > my.company:jkl-api > > one would specify > > my.company:.*\-api > > To be compatible, the wildcard '*' would be treated as regular expression '.*' -- 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: (MENFORCER-83) Banned dependencies should support regular expressions
Banned dependencies should support regular expressions -- Key: MENFORCER-83 URL: http://jira.codehaus.org/browse/MENFORCER-83 Project: Maven 2.x Enforcer Plugin Issue Type: Improvement Components: Standard Rules Affects Versions: 1.0-beta-1 Reporter: Eric Lewis The includes and excludes of the bannedDependencies rule support wildcards, but only for an entire section. They should be enhanced to support regular expressions. For instance instead of having my.company:abc-api my.company:def-api my.company:ghi-api my.company:jkl-api one would specify my.company:.*\-api To be compatible, the wildcard '*' would be treated as regular expression '.*' -- 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: (MSITE-389) Maven's CSS shows ugly green shadows
[ http://jira.codehaus.org/browse/MSITE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lewis closed MSITE-389. Resolution: Fixed Ok, I just tested it on 2.0-beta-7, the text-shadow is gone. Thanks! > Maven's CSS shows ugly green shadows > > > Key: MSITE-389 > URL: http://jira.codehaus.org/browse/MSITE-389 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Environment: Windows, the shadows are not shown on Firefox < 3.1, but > on 3.1 they are shown. Also, doesn't appear on my IE 7 >Reporter: Eric Lewis >Priority: Minor > Attachments: uglyGreenShadows.png > > > The maven-base.css contains text shadowing for the banner > text-shadow: #7CFC00 1px 1px 1px; > This has problably not been reported before, because it's only shown in > Firefox 3.1. > However, it looks terrible, so please remove it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-389) Maven's CSS shows ugly green shadows
[ http://jira.codehaus.org/browse/MSITE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168766#action_168766 ] Eric Lewis commented on MSITE-389: -- I'm using Maven 2.0.9, so according to its release notes, it's 2.0-beta-6. > Maven's CSS shows ugly green shadows > > > Key: MSITE-389 > URL: http://jira.codehaus.org/browse/MSITE-389 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Environment: Windows, the shadows are not shown on Firefox < 3.1, but > on 3.1 they are shown. Also, doesn't appear on my IE 7 >Reporter: Eric Lewis >Priority: Minor > Attachments: uglyGreenShadows.png > > > The maven-base.css contains text shadowing for the banner > text-shadow: #7CFC00 1px 1px 1px; > This has problably not been reported before, because it's only shown in > Firefox 3.1. > However, it looks terrible, so please remove 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: (MSITE-389) Maven's CSS shows ugly green shadows
Maven's CSS shows ugly green shadows Key: MSITE-389 URL: http://jira.codehaus.org/browse/MSITE-389 Project: Maven 2.x Site Plugin Issue Type: Improvement Environment: Windows, the shadows are not shown on Firefox < 3.1, but on 3.1 they are shown. Also, doesn't appear on my IE 7 Reporter: Eric Lewis Priority: Minor Attachments: uglyGreenShadows.png The maven-base.css contains text shadowing for the banner text-shadow: #7CFC00 1px 1px 1px; This has problably not been reported before, because it's only shown in Firefox 3.1. However, it looks terrible, so please remove 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
