[jira] (MRELEASE-431) Configuration of policy for calculating next (release) version
[
https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328897#comment-328897
]
Ziga Gregoric commented on MRELEASE-431:
While trying to stick to http://semver.org for a 'pre-release' as in
{{1.0.0-alpha.1}}, maven would increase it to {{1.0.1-alpha.1}} instead of
{{1.0.0-alpha.2}}.
Since {{1.0.0-alpha1}} is increased to {{1.0.0-alpha2}}, I was hoping we can
have default versioning policy accept notation for 'pre-release' with a dot as
delimiter after alpha/beta/milestone.
MRELEASE-797 is marked as a duplicate, therefore please excuse a non maven
committer if this belongs to a new issue. Thank you.
> Configuration of policy for calculating next (release) version
> --
>
> Key: MRELEASE-431
> URL: https://jira.codehaus.org/browse/MRELEASE-431
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: prepare
>Affects Versions: 2.0-beta-8
>Reporter: Carsten Ziegeler
> Attachments:
> 0001-MRELEASE-431-Configuration-of-policy-for-calculating.patch
>
>
> Currently, when preparing the release, the version to release is always the
> next version which usually is the current version without the snapshot
> extension.
> There are quiet a lot projects (Apache Felix, Sling and others) following an
> even release numbering policy. So while the current development version is
> odd (like 1.2.3-SNAPSHOT), the next released version will be 1.2.4.
> It would be nice if this could be made configuration through some
> configuration property like
> next-even (with possible values being: next
> (default, as-is), next-even, next-odd
> I briefly scanned through the code and it seems that adding support for this
> requires changes in both, the release-manager and the release-plugin.
> If this feature gets accepted and if someone could give me some minor hints
> how/where to add this I could come up with a patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-248) XML-Namespace in ITs for ant-based mojos are wrong.
Mirko Friedenhagen created MPLUGIN-248:
--
Summary: XML-Namespace in ITs for ant-based mojos are wrong.
Key: MPLUGIN-248
URL: https://jira.codehaus.org/browse/MPLUGIN-248
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: maven-plugin-tools-ant
Affects Versions: 3.2
Environment: git-svn-id:
https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122
13f79535-47bb-0310-9956-ffa450edef68
Reporter: Mirko Friedenhagen
Example error:
{code}
[mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
/dev/null
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
element pluginMetadata: Schemas validity error : Element
'{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
declaration available for the validation root.
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails to
validate
{code}
While Maven seems not choke on this, XML support in IDEs is broken because of
this. I consider this major because the documentation just references the ITs
and all the examples therefore are broken for users. I will submit a patch and
Github-Pull request for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-186) FileTabCharacter check not working
[
https://jira.codehaus.org/browse/MCHECKSTYLE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328900#comment-328900
]
Amichai Rothman commented on MCHECKSTYLE-186:
-
@Dipti, would you be able to share your working configuration? I've been
struggling with this for hours as well, with various forms of
includes/sourceDirectory/fileExtensions.
Eventually I peeked at the source for DefaultCheckstyleExecutor.java, from
which it appears that using the checkstyle-aggregate goal pretty much ignores
the configured sourceDirectory. I switched to using the checkstyle goal and it
finally picked up the xml files (under resources) and found the violations
there.
I'm not entirely sure how the sourceDirectory was desgined to function in
aggregate, I'd assumed that I can configure it once in the parent (aggregator)
and it would apply to the child modules and then aggregate the result, but the
code seems to just take the standard build source directory for each child
module, and ignoring the configured sourceDirectory when adding the files to
process. If someone can confirm that this is indeed a bug, I'd be happy to open
a separate issue for it. If the current behavior is by design, it would be
useful to mention this in the documentation, seeing that it may not be
intuitive for everyone.
In addition, as logic and comments in the code say, it would be nice if the
currently half-hacked resources directory treatment would be made generic:
ideally, there would be a separate configuration for the sourcesDirectory,
testSourcesDirectory and resourcesDirectory, and each one would have its own
includes clause as well - for maximum configurability.
> FileTabCharacter check not working
> --
>
> Key: MCHECKSTYLE-186
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-186
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Reporter: Dipti Desai
>Priority: Minor
>
> The FileTabCharacter check doesnt seem to work. Below is my config:
> {code:xml}
>
> ..
> ..
>
>
>
>
>
> ..
> ..
>
> ..
> ..
>
>
> {code}
> I have my xml files - pom.xml and checkstyle config xml containing tabs but
> none of them are flagged as violations.
> Some additional info - my plugin config looks like this:
> {code:xml}
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.9.1
>
>
> verify
>
> check
>
>
>
>
>
> checkstyle/kepler-checkstyle-config.xml
>
> ${project.parent.basedir}${file.separator}checkstyle/kepler-checkstyle-suppressions.xml
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-248) XML-Namespace in ITs for ant-based mojos are wrong.
[
https://jira.codehaus.org/browse/MPLUGIN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen updated MPLUGIN-248:
---
Description:
Example error:
{code}
[mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
/dev/null
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
element pluginMetadata: Schemas validity error : Element
'{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
declaration available for the validation root.
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails to
validate
{code}
While Maven seems not choke on this, XML support in IDEs is broken because of
this. I consider this major because the documentation
(http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
just references the ITs and all the examples therefore are broken for users. I
will submit a patch and Github-Pull request for this.
was:
Example error:
{code}
[mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
/dev/null
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
element pluginMetadata: Schemas validity error : Element
'{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
declaration available for the validation root.
maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails to
validate
{code}
While Maven seems not choke on this, XML support in IDEs is broken because of
this. I consider this major because the documentation just references the ITs
and all the examples therefore are broken for users. I will submit a patch and
Github-Pull request for this.
> XML-Namespace in ITs for ant-based mojos are wrong.
> ---
>
> Key: MPLUGIN-248
> URL: https://jira.codehaus.org/browse/MPLUGIN-248
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-ant
>Affects Versions: 3.2
> Environment: git-svn-id:
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122
> 13f79535-47bb-0310-9956-ffa450edef68
>Reporter: Mirko Friedenhagen
>
> Example error:
> {code}
> [mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
> http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
> /dev/null
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
> element pluginMetadata: Schemas validity error : Element
> '{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
> declaration available for the validation root.
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails
> to validate
> {code}
> While Maven seems not choke on this, XML support in IDEs is broken because of
> this. I consider this major because the documentation
> (http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
> just references the ITs and all the examples therefore are broken for users.
> I will submit a patch and Github-Pull request for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-248) XML-Namespace in ITs for ant-based mojos are wrong.
[
https://jira.codehaus.org/browse/MPLUGIN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328915#comment-328915
]
Mirko Friedenhagen commented on MPLUGIN-248:
I updated all samples and now receive the following error:
{code}
find maven-plugin-plugin/src/it/ -name \*.mojos.xml | xargs xmllint --schema
http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd > /dev/null
maven-plugin-plugin/src/it//ant-basic/src/main/scripts/touch.mojos.xml validates
maven-plugin-plugin/src/it//ant-reference-parameter/src/main/scripts/test.mojos.xml
validates
maven-plugin-plugin/src/it//ant-simple-usage/plugin/src/main/scripts/test.mojos.xml
validates
maven-plugin-plugin/src/it//ant-since-maven-plugin/src/main/scripts/sample.mojos.xml:31:
element since: Schemas validity error : Element
'{http://maven.apache.org/PLUGIN-METADATA/1.0.0}since': This element is not
expected.
maven-plugin-plugin/src/it//ant-since-maven-plugin/src/main/scripts/sample.mojos.xml
fails to validate
maven-plugin-plugin/src/it//fix-maven-since-3.x/antsample-maven-plugin/src/main/scripts/sample.mojos.xml:31:
element since: Schemas validity error : Element
'{http://maven.apache.org/PLUGIN-METADATA/1.0.0}since': This element is not
expected.
maven-plugin-plugin/src/it//fix-maven-since-3.x/antsample-maven-plugin/src/main/scripts/sample.mojos.xml
fails to validate
{code}
Seems, that a newer version of the XSD should include this :-).
> XML-Namespace in ITs for ant-based mojos are wrong.
> ---
>
> Key: MPLUGIN-248
> URL: https://jira.codehaus.org/browse/MPLUGIN-248
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-ant
>Affects Versions: 3.2
> Environment: git-svn-id:
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122
> 13f79535-47bb-0310-9956-ffa450edef68
>Reporter: Mirko Friedenhagen
>
> Example error:
> {code}
> [mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
> http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
> /dev/null
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
> element pluginMetadata: Schemas validity error : Element
> '{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
> declaration available for the validation root.
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails
> to validate
> {code}
> While Maven seems not choke on this, XML support in IDEs is broken because of
> this. I consider this major because the documentation
> (http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
> just references the ITs and all the examples therefore are broken for users.
> I will submit a patch and Github-Pull request for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-248) XML-Namespace in ITs for ant-based mojos are wrong.
[
https://jira.codehaus.org/browse/MPLUGIN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen updated MPLUGIN-248:
---
Attachment: MPLUGIN-248.patch
> XML-Namespace in ITs for ant-based mojos are wrong.
> ---
>
> Key: MPLUGIN-248
> URL: https://jira.codehaus.org/browse/MPLUGIN-248
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-ant
>Affects Versions: 3.2
> Environment: git-svn-id:
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122
> 13f79535-47bb-0310-9956-ffa450edef68
>Reporter: Mirko Friedenhagen
> Attachments: MPLUGIN-248.patch
>
>
> Example error:
> {code}
> [mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
> http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
> /dev/null
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
> element pluginMetadata: Schemas validity error : Element
> '{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
> declaration available for the validation root.
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails
> to validate
> {code}
> While Maven seems not choke on this, XML support in IDEs is broken because of
> this. I consider this major because the documentation
> (http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
> just references the ITs and all the examples therefore are broken for users.
> I will submit a patch and Github-Pull request for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-300) Group ID not usable in outputFileNameMapping
Jens Bannmann created MWAR-300:
--
Summary: Group ID not usable in outputFileNameMapping
Key: MWAR-300
URL: https://jira.codehaus.org/browse/MWAR-300
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Jens Bannmann
I configured the following output file name mapping:
@{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@
The files in WEB-INF/lib, however, do not have their group ID in the file name,
so a GSON jar file is named literally
@{groupId}_gson-2.2.2.jar
instead of the expected name
com.google.code.gson_gson-2.2.2.jar
It seems the group ID is simply not supported by outputFileNameMapping.
Note: The page
only says "You can use any property of Artifact and ArtifactHandler as a
token.", but does not offer a list of valid tokens - even a link to the
relevant Maven source files would have been fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-300) Group ID not usable in outputFileNameMapping
[
https://jira.codehaus.org/browse/MWAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Bannmann updated MWAR-300:
---
Description:
I configured the following output file name mapping:
{noformat}@{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@{noformat}
The files in WEB-INF/lib, however, do not have their group ID in the file name.
For example, a GSON jar file I depend on is copied as
{noformat}@{groupId}_gson-2.2.2.jar{noformat}
instead of the expected name
{noformat}com.google.code.gson_gson-2.2.2.jar{noformat}
It seems the group ID is simply not supported by outputFileNameMapping.
Note: The page
only says "You can use any property of Artifact and ArtifactHandler as a
token", but does not offer a list of valid tokens - even a link to the relevant
Maven source files would have been fine.
was:
I configured the following output file name mapping:
@{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@
The files in WEB-INF/lib, however, do not have their group ID in the file name,
so a GSON jar file is named literally
@{groupId}_gson-2.2.2.jar
instead of the expected name
com.google.code.gson_gson-2.2.2.jar
It seems the group ID is simply not supported by outputFileNameMapping.
Note: The page
only says "You can use any property of Artifact and ArtifactHandler as a
token.", but does not offer a list of valid tokens - even a link to the
relevant Maven source files would have been fine.
> Group ID not usable in outputFileNameMapping
>
>
> Key: MWAR-300
> URL: https://jira.codehaus.org/browse/MWAR-300
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Jens Bannmann
>
> I configured the following output file name mapping:
> {noformat}@{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@{noformat}
> The files in WEB-INF/lib, however, do not have their group ID in the file
> name. For example, a GSON jar file I depend on is copied as
> {noformat}@{groupId}_gson-2.2.2.jar{noformat}
> instead of the expected name
> {noformat}com.google.code.gson_gson-2.2.2.jar{noformat}
> It seems the group ID is simply not supported by outputFileNameMapping.
> Note: The page
>
> only says "You can use any property of Artifact and ArtifactHandler as a
> token", but does not offer a list of valid tokens - even a link to the
> relevant Maven source files would have been fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-300) Group ID not usable in outputFileNameMapping
[
https://jira.codehaus.org/browse/MWAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328920#comment-328920
]
Jens Bannmann commented on MWAR-300:
Never mind, this *does* work correctly after all. I managed to forget the @
character after the groupId placeholder. The following mapping works:
{noformat}@{groupId}@_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@{noformat}
Please close this issue as 'invalid' or the like.
> Group ID not usable in outputFileNameMapping
>
>
> Key: MWAR-300
> URL: https://jira.codehaus.org/browse/MWAR-300
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Jens Bannmann
>
> I configured the following output file name mapping:
> {noformat}@{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@{noformat}
> The files in WEB-INF/lib, however, do not have their group ID in the file
> name. For example, a GSON jar file I depend on is copied as
> {noformat}@{groupId}_gson-2.2.2.jar{noformat}
> instead of the expected name
> {noformat}com.google.code.gson_gson-2.2.2.jar{noformat}
> It seems the group ID is simply not supported by outputFileNameMapping.
> Note: The page
>
> only says "You can use any property of Artifact and ArtifactHandler as a
> token", but does not offer a list of valid tokens - even a link to the
> relevant Maven source files would have been fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5495) API incompatibility causes Swagger Maven Plugin (and others) to fail under Maven 3.1.0
[
https://jira.codehaus.org/browse/MNG-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-5495:
--
Fix Version/s: 3.1.1
> API incompatibility causes Swagger Maven Plugin (and others) to fail under
> Maven 3.1.0
> --
>
> Key: MNG-5495
> URL: https://jira.codehaus.org/browse/MNG-5495
> Project: Maven 2 & 3
> Issue Type: Bug
>Reporter: Brett Porter
> Fix For: 3.1.1
>
>
> {code}
> ERROR] Failed to execute goal
> com.github.kongchen:swagger-maven-plugin:1.1.1:generate (default) on project
> maestro-webapp: An API incompatibility was encountered during configuration
> of mojo com.github.kongchen:swagger-maven-plugin:1.1.1:generate:
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V
> [ERROR] -
> [ERROR] realm =plugin>com.github.kongchen:swagger-maven-plugin:1.1.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/brett/.m2/repository/com/github/kongchen/swagger-maven-plugin/1.1.1/swagger-maven-plugin-1.1.1.jar
> [ERROR] urls[1] =
> file:/Users/brett/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5495) API incompatibility causes Swagger Maven Plugin (and others) to fail under Maven 3.1.0
Brett Porter created MNG-5495:
-
Summary: API incompatibility causes Swagger Maven Plugin (and
others) to fail under Maven 3.1.0
Key: MNG-5495
URL: https://jira.codehaus.org/browse/MNG-5495
Project: Maven 2 & 3
Issue Type: Bug
Reporter: Brett Porter
{code}
ERROR] Failed to execute goal
com.github.kongchen:swagger-maven-plugin:1.1.1:generate (default) on project
maestro-webapp: An API incompatibility was encountered during configuration of
mojo com.github.kongchen:swagger-maven-plugin:1.1.1:generate:
java.lang.NoSuchMethodError:
org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V
[ERROR] -
[ERROR] realm =plugin>com.github.kongchen:swagger-maven-plugin:1.1.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/brett/.m2/repository/com/github/kongchen/swagger-maven-plugin/1.1.1/swagger-maven-plugin-1.1.1.jar
[ERROR] urls[1] =
file:/Users/brett/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-186) FileTabCharacter check not working
[
https://jira.codehaus.org/browse/MCHECKSTYLE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328928#comment-328928
]
Dipti Desai commented on MCHECKSTYLE-186:
-
This is what I am currently using in my checkstyle-config.xml
Hope this helps.
{code}
{code}
> FileTabCharacter check not working
> --
>
> Key: MCHECKSTYLE-186
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-186
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Reporter: Dipti Desai
>Priority: Minor
>
> The FileTabCharacter check doesnt seem to work. Below is my config:
> {code:xml}
>
> ..
> ..
>
>
>
>
>
> ..
> ..
>
> ..
> ..
>
>
> {code}
> I have my xml files - pom.xml and checkstyle config xml containing tabs but
> none of them are flagged as violations.
> Some additional info - my plugin config looks like this:
> {code:xml}
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.9.1
>
>
> verify
>
> check
>
>
>
>
>
> checkstyle/kepler-checkstyle-config.xml
>
> ${project.parent.basedir}${file.separator}checkstyle/kepler-checkstyle-suppressions.xml
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5470) Fix license headers on source files
[
https://jira.codehaus.org/browse/MNG-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-5470:
--
Fix Version/s: (was: 3.1.0)
3.1.1
> Fix license headers on source files
> ---
>
> Key: MNG-5470
> URL: https://jira.codehaus.org/browse/MNG-5470
> Project: Maven 2 & 3
> Issue Type: Task
> Components: General
>Affects Versions: 3.1.0-alpha-1
>Reporter: Stephen Connolly
>Priority: Blocker
> Fix For: 3.1.1
>
> Attachments: rat.txt
>
>
> RAT is reporting GIT HASH 262b9bb1ef91d1414e5162d9dd0f5522e7186202 has 391
> files that are either missing license headers or have not been flagged as
> files that cannot support a license header.
> Most of these are test data files and I would be happy to argue that the test
> may require a specific exact content for reproducibility, but the following I
> do not feel we can make a case for:
> {code}
> apache-maven/src/bin/m2.conf
> apache-maven/src/conf/logging/simplelogger.properties
>
> maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html
> maven-aether-provider/src/site/apt/index.apt
> maven-artifact/src/site/apt/index.apt
> maven-compat/compatibility.cfl
> maven-compat/src/main/resources/META-INF/maven/plugin.xml
> maven-core/lifecycle-executor.txt
> maven-core/plugin-manager.txt
> maven-core/project-builder.txt
> maven-core/src/main/resources/org/apache/maven/messages/build.properties
> maven-core/src/site/apt/artifact-handlers.apt
> maven-core/src/site/apt/configuration-management.apt
> maven-core/src/site/apt/default-bindings.apt.vm
> maven-core/src/site/apt/getting-to-container-configured-mojos.apt
> maven-core/src/site/apt/index.apt
> maven-core/src/site/apt/inheritance.apt
> maven-core/src/site/apt/lifecycles.apt.vm
> maven-core/src/site/apt/offline-mode.apt
> maven-core/src/site/apt/plugin-execution-isolation.apt
> maven-core/src/site/apt/scripting-support/marmalade-support.apt
> maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle
>
> maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java
>
> maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java
> maven-embedder/src/main/resources/META-INF/MANIFEST.MF
>
> maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties
> maven-embedder/src/site/apt/cli.apt.vm
> maven-embedder/src/site/apt/index.apt.vm
> maven-embedder/src/site/apt/logging.apt
> maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html
> maven-model/src/main/java/org/apache/maven/model/merge/package.html
> maven-model/src/main/java/org/apache/maven/model/package.html
> maven-model/src/site/apt/index.apt
> maven-model-builder/src/site/apt/index.apt
> maven-model-builder/src/site/apt/super-pom.apt.vm
> maven-plugin-api/src/site/apt/index.apt
> maven-plugin-api/src/test/resources/plugin.xml
> maven-repository-metadata/src/site/apt/index.apt
> maven-settings/src/site/apt/index.apt
> {code}
> Attached is the full RAT report
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-843) Child modules defined in profiles aren't updated by update-versions
M. Justin created MRELEASE-843:
--
Summary: Child modules defined in profiles aren't updated by
update-versions
Key: MRELEASE-843
URL: https://jira.codehaus.org/browse/MRELEASE-843
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: update-versions
Reporter: M. Justin
When I do a mvn:update-versions for a multi-module project that has one of its
modules defined in a profile, the modules defined in the profile don't have
their versions updated. I would expect these modules to also be updated.
{code:title=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
pom
com.example
example-parent
1.0.0-SNAPSHOT
example-module1
my-profile
example-module2
scm:git:examplerepo:example.git
{code}
In this example, when I execute mvn release:update-versions, I get queried to
update example-parent and example-module1, but not example-module2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-186) FileTabCharacter check not working
[
https://jira.codehaus.org/browse/MCHECKSTYLE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328949#comment-328949
]
Amichai Rothman commented on MCHECKSTYLE-186:
-
@Dipti, and the checkstyle plugin configuration (in the pom)?
> FileTabCharacter check not working
> --
>
> Key: MCHECKSTYLE-186
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-186
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Reporter: Dipti Desai
>Priority: Minor
>
> The FileTabCharacter check doesnt seem to work. Below is my config:
> {code:xml}
>
> ..
> ..
>
>
>
>
>
> ..
> ..
>
> ..
> ..
>
>
> {code}
> I have my xml files - pom.xml and checkstyle config xml containing tabs but
> none of them are flagged as violations.
> Some additional info - my plugin config looks like this:
> {code:xml}
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.9.1
>
>
> verify
>
> check
>
>
>
>
>
> checkstyle/kepler-checkstyle-config.xml
>
> ${project.parent.basedir}${file.separator}checkstyle/kepler-checkstyle-suppressions.xml
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-186) FileTabCharacter check not working
[
https://jira.codehaus.org/browse/MCHECKSTYLE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328950#comment-328950
]
Dipti Desai commented on MCHECKSTYLE-186:
-
{code}
org.apache.maven.plugins
maven-checkstyle-plugin
2.10
verify
check
**\/*.xml,**\/*.java
**/target/**/*,**/test/**/*
checkstyle/kepler-checkstyle-config.xml
${project.parent.basedir}${file.separator}checkstyle/kepler-checkstyle-suppressions.xml
{code}
> FileTabCharacter check not working
> --
>
> Key: MCHECKSTYLE-186
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-186
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Reporter: Dipti Desai
>Priority: Minor
>
> The FileTabCharacter check doesnt seem to work. Below is my config:
> {code:xml}
>
> ..
> ..
>
>
>
>
>
> ..
> ..
>
> ..
> ..
>
>
> {code}
> I have my xml files - pom.xml and checkstyle config xml containing tabs but
> none of them are flagged as violations.
> Some additional info - my plugin config looks like this:
> {code:xml}
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.9.1
>
>
> verify
>
> check
>
>
>
>
>
> checkstyle/kepler-checkstyle-config.xml
>
> ${project.parent.basedir}${file.separator}checkstyle/kepler-checkstyle-suppressions.xml
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5495) API incompatibility causes Swagger Maven Plugin (and others) to fail under Maven 3.1.0
[
https://jira.codehaus.org/browse/MNG-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5495:
---
Affects Version/s: 3.1.0
> API incompatibility causes Swagger Maven Plugin (and others) to fail under
> Maven 3.1.0
> --
>
> Key: MNG-5495
> URL: https://jira.codehaus.org/browse/MNG-5495
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Brett Porter
> Fix For: 3.1.1
>
>
> {code}
> ERROR] Failed to execute goal
> com.github.kongchen:swagger-maven-plugin:1.1.1:generate (default) on project
> maestro-webapp: An API incompatibility was encountered during configuration
> of mojo com.github.kongchen:swagger-maven-plugin:1.1.1:generate:
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V
> [ERROR] -
> [ERROR] realm =plugin>com.github.kongchen:swagger-maven-plugin:1.1.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/brett/.m2/repository/com/github/kongchen/swagger-maven-plugin/1.1.1/swagger-maven-plugin-1.1.1.jar
> [ERROR] urls[1] =
> file:/Users/brett/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-186) FileTabCharacter check not working
[
https://jira.codehaus.org/browse/MCHECKSTYLE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328954#comment-328954
]
Amichai Rothman commented on MCHECKSTYLE-186:
-
So no sourceDirectory... interesting. Thanks!
> FileTabCharacter check not working
> --
>
> Key: MCHECKSTYLE-186
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-186
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Reporter: Dipti Desai
>Priority: Minor
>
> The FileTabCharacter check doesnt seem to work. Below is my config:
> {code:xml}
>
> ..
> ..
>
>
>
>
>
> ..
> ..
>
> ..
> ..
>
>
> {code}
> I have my xml files - pom.xml and checkstyle config xml containing tabs but
> none of them are flagged as violations.
> Some additional info - my plugin config looks like this:
> {code:xml}
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.9.1
>
>
> verify
>
> check
>
>
>
>
>
> checkstyle/kepler-checkstyle-config.xml
>
> ${project.parent.basedir}${file.separator}checkstyle/kepler-checkstyle-suppressions.xml
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-996) and content of junit xml report are not escaped
[
https://jira.codehaus.org/browse/SUREFIRE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328955#comment-328955
]
Kristian Rosenvold commented on SUREFIRE-996:
-
You should test 2.16-SNAPSHOT, since we've had quite a few other reports of
this and will be releasing 2.16 "soon". let us know if your problem still
applies to 2.16-SNAPSHOT
> and content of junit xml report are not escaped
> -
>
> Key: SUREFIRE-996
> URL: https://jira.codehaus.org/browse/SUREFIRE-996
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.15
> Environment: maven 3.0.4
> surefire 2.15-SNAPSHOT (from apache snashot repo)
>Reporter: Julien Vermillard
>Assignee: Kristian Rosenvold
>Priority: Blocker
> Fix For: 2.15
>
> Attachments: 0001-added-test-case-for-SUREFIRE-996.patch,
> extended-test-case-for-SUREFIRE-996.patch
>
>
> Some of my junit xml report are not correctly generated :
> {code}
> 15:24:59.565 [pool-1-thread-5] INFO
> c.s.a.i.c.s.api.PartnerServicesUtils - Profile
>
> {code}
> The < and > in "" are not escaped.
> If I look at
> maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/StatelessXmlReporter.java
> code, I think the bug is here :
> {code}
> addOutputStreamElement( outputStreamWriter, fw, eos, ppw,
> report.getStdout(), "system-out" );
> addOutputStreamElement( outputStreamWriter, fw, eos, ppw,
> report.getStdErr(), "system-err" );
> ppw.endElement(); // test element
> }
> private void addOutputStreamElement( OutputStreamWriter
> outputStreamWriter, OutputStream fw, EncodingOutputStream eos, XMLWriter
> xmlWriter, DeferredFileOutputStream stdOut,
> String name )
> {
> if ( stdOut != null && stdOut.getByteCount() > 0 )
> {
> xmlWriter.startElement( name );
> try
> {
> xmlWriter.writeText( "" ); // Cheat sax to emit element
> outputStreamWriter.flush();
> stdOut.close();
> stdOut.writeTo( eos );
> eos.flush();
> }
> catch ( IOException e )
> {
> throw new ReporterException( "When writing xml report
> stdout/stderr", e );
> }
> xmlWriter.endElement();
> }
> }
> {code}
> and probably introduced by this commit :
> commit 33e110fc46aa43d10b38a93b3db74c09be6bc6d5
> Author: Kristian Rosenvold
> Date: Thu May 2 20:53:27 2013 +0200
> [SUREFIRE-938] Removed memory binding for stdout/stderr capture.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MENFORCER-161) Fix deploySite
[ https://jira.codehaus.org/browse/MENFORCER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MENFORCER-161: - Fix Version/s: 1.4 > Fix deploySite > -- > > Key: MENFORCER-161 > URL: https://jira.codehaus.org/browse/MENFORCER-161 > Project: Maven 2.x Enforcer Plugin > Issue Type: Task >Affects Versions: 1.3.1 >Reporter: Robert Scholte >Priority: Minor > Fix For: 1.4 > > > After a release only the root-pages of /enforcer/ are synced, not their > folders. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MENFORCER-161) Fix deploySite
Robert Scholte created MENFORCER-161: Summary: Fix deploySite Key: MENFORCER-161 URL: https://jira.codehaus.org/browse/MENFORCER-161 Project: Maven 2.x Enforcer Plugin Issue Type: Task Affects Versions: 1.3.1 Reporter: Robert Scholte Priority: Minor After a release only the root-pages of /enforcer/ are synced, not their folders. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-300) Group ID not usable in outputFileNameMapping
[
https://jira.codehaus.org/browse/MWAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MWAR-300.
---
Resolution: Not A Bug
Assignee: Robert Scholte
> Group ID not usable in outputFileNameMapping
>
>
> Key: MWAR-300
> URL: https://jira.codehaus.org/browse/MWAR-300
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Jens Bannmann
>Assignee: Robert Scholte
>
> I configured the following output file name mapping:
> {noformat}@{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@{noformat}
> The files in WEB-INF/lib, however, do not have their group ID in the file
> name. For example, a GSON jar file I depend on is copied as
> {noformat}@{groupId}_gson-2.2.2.jar{noformat}
> instead of the expected name
> {noformat}com.google.code.gson_gson-2.2.2.jar{noformat}
> It seems the group ID is simply not supported by outputFileNameMapping.
> Note: The page
>
> only says "You can use any property of Artifact and ArtifactHandler as a
> token", but does not offer a list of valid tokens - even a link to the
> relevant Maven source files would have been fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-729) Ability to specify tag for release:perform
[ https://jira.codehaus.org/browse/SCM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MRELEASE-813 to SCM-729: - Complexity: Intermediate Component/s: (was: Mercurial) (was: perform) maven-scm-provider-mercurial (hg) Affects Version/s: (was: 2.4) 1.8.1 Key: SCM-729 (was: MRELEASE-813) Project: Maven SCM (was: Maven 2.x Release Plugin) > Ability to specify tag for release:perform > -- > > Key: SCM-729 > URL: https://jira.codehaus.org/browse/SCM-729 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-mercurial (hg) >Affects Versions: 1.8.1 >Reporter: Gili > > We need a way to specify a tag either to release:perform or the HG scm > provider. > http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html > indicates that we should be able to release:perform from a tag without the > use of release.properties but there is no way to specify a tag for the HG scm > provider. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-317) GitHub: "API rate limit exceeded"
Johannes Schneider created MCHANGES-317: --- Summary: GitHub: "API rate limit exceeded" Key: MCHANGES-317 URL: https://jira.codehaus.org/browse/MCHANGES-317 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: github Affects Versions: 2.9 Reporter: Johannes Schneider I tried to generate a report and got this message: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project stax-mate: Error during page generation: Error rendering Maven report: API rate limit exceeded for 149.###.###.##. See http://developer.github.com/v3/#rate-limiting for details. (403) -> [Help 1] I think this is caused by having a low limit for unauthenticated requests. I think it would be great if there was a way to authenticate... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5496) Fixing NOTICE and LICENSE files
SebbASF created MNG-5496: Summary: Fixing NOTICE and LICENSE files Key: MNG-5496 URL: https://jira.codehaus.org/browse/MNG-5496 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.1.0 Reporter: SebbASF Priority: Blocker The NOTICE and LICENSE files are an essential part of any release. They need to relate to the contents of the bundle in which they are located and it is important that they don't contain anything superfluous [1] Each distribution artifact potentially needs its own specific N&L files. In particular, the source and binary artifacts will generally need different versions, as the binary often bundles additional items, for example 3rd party jars. However the jar files which are created from the SCM source probably can use the same license as the source archive. However, the existing N&L files in 3.1.0 fall short on several counts: The source and binary NOTICE files both start as follows: > = == NOTICE file corresponding to the section 4 d of== == the Apache License, Version 2.0, == == in this case for the Apache Maven distribution.== = Apache Maven Copyright 2001-2013 The Apache Software Foundation This product includes software developed by The Apache Software Foundation (http://www.apache.org/). <<< However, the file must start as follows: Apache Maven Copyright 2001-2013 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). Note particularly that the phrase is "developed at" not "developed by" The source NOTICE file is the same as the binary NOTICE file, yet the binary archive contains lots of additional jars. It looks to me as though the above 5 lines is all that are needed for the source archive. The existing source LICENSE.txt file looks OK. However, the binary LICENSE file makes no mention at all of any licenses for the additional products. It should point to the licenses for each of the additional products that are included, for example: Aether, Sisu, Plexus etc. These licenses need to be obtained and stored in a suitable directory which is referenced in LICENSE.txt. [1] http://www.apache.org/dev/licensing-howto.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5496) Fixing NOTICE and LICENSE files
[ https://jira.codehaus.org/browse/MNG-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328959#comment-328959 ] SebbASF commented on MNG-5496: -- Forgot to mention that it's possible the same NOTICE file can be used for the binary archive, see: http://www.apache.org/dev/licensing-howto.html#mod-notice > Fixing NOTICE and LICENSE files > --- > > Key: MNG-5496 > URL: https://jira.codehaus.org/browse/MNG-5496 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: SebbASF >Priority: Blocker > > The NOTICE and LICENSE files are an essential part of any release. > They need to relate to the contents of the bundle in which they are located > and it is important that they don't contain anything superfluous [1] > Each distribution artifact potentially needs its own specific N&L files. > In particular, the source and binary artifacts will generally need different > versions, as the binary often bundles additional items, for example 3rd party > jars. > However the jar files which are created from the SCM source probably can use > the same license as the source archive. > However, the existing N&L files in 3.1.0 fall short on several counts: > The source and binary NOTICE files both start as follows: > > >= >== NOTICE file corresponding to the section 4 d of== >== the Apache License, Version 2.0, == >== in this case for the Apache Maven distribution.== >= > Apache Maven > Copyright 2001-2013 The Apache Software Foundation > This product includes software developed by > The Apache Software Foundation (http://www.apache.org/). > <<< > However, the file must start as follows: > > Apache Maven > Copyright 2001-2013 The Apache Software Foundation > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > > Note particularly that the phrase is "developed at" not "developed by" > The source NOTICE file is the same as the binary NOTICE file, yet the binary > archive contains lots of additional jars. > It looks to me as though the above 5 lines is all that are needed for the > source archive. The existing source LICENSE.txt file looks OK. > However, the binary LICENSE file makes no mention at all of any licenses for > the additional products. It should point to the licenses for each of the > additional products that are included, for example: Aether, Sisu, Plexus etc. > These licenses need to be obtained and stored in a suitable directory which > is referenced in LICENSE.txt. > [1] http://www.apache.org/dev/licensing-howto.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-431) Configuration of policy for calculating next (release) version
[ https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-431: Fix Version/s: 2.5 Assignee: Robert Scholte Let's try to fix this for 2.5 > Configuration of policy for calculating next (release) version > -- > > Key: MRELEASE-431 > URL: https://jira.codehaus.org/browse/MRELEASE-431 > Project: Maven 2.x Release Plugin > Issue Type: New Feature > Components: prepare >Affects Versions: 2.0-beta-8 >Reporter: Carsten Ziegeler >Assignee: Robert Scholte > Fix For: 2.5 > > Attachments: > 0001-MRELEASE-431-Configuration-of-policy-for-calculating.patch > > > Currently, when preparing the release, the version to release is always the > next version which usually is the current version without the snapshot > extension. > There are quiet a lot projects (Apache Felix, Sling and others) following an > even release numbering policy. So while the current development version is > odd (like 1.2.3-SNAPSHOT), the next released version will be 1.2.4. > It would be nice if this could be made configuration through some > configuration property like > next-even (with possible values being: next > (default, as-is), next-even, next-odd > I briefly scanned through the code and it seems that adding support for this > requires changes in both, the release-manager and the release-plugin. > If this feature gets accepted and if someone could give me some minor hints > how/where to add this I could come up with a patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-697) Delete deprecated code
[ https://jira.codehaus.org/browse/MECLIPSE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar reassigned MECLIPSE-697: --- Assignee: (was: Barrie Treloar) Dont have the bandwidth to work on this. > Delete deprecated code > -- > > Key: MECLIPSE-697 > URL: https://jira.codehaus.org/browse/MECLIPSE-697 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Reporter: Barrie Treloar > Fix For: 2.10 > > > There are deprecated classes that have been there for a while. > As part of cleaning up, its time for them to go. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-668) jre/lib/rt.jar doesn't exist on OSX, rather bundle/Classes/classes.jar
[ https://jira.codehaus.org/browse/MECLIPSE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar reassigned MECLIPSE-668: --- Assignee: (was: Barrie Treloar) Dont have the bandwidth to work on this. > jre/lib/rt.jar doesn't exist on OSX, rather bundle/Classes/classes.jar > -- > > Key: MECLIPSE-668 > URL: https://jira.codehaus.org/browse/MECLIPSE-668 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath) >Affects Versions: 2.8 > Environment: OS X (Leopard/Snow Leopard) >Reporter: Martijn Dashorst > Attachments: patch.diff > > > When running mvn eclipse:eclipse we get annoying messages that the JDK > doesn't have a valid jre/lib/rt.jar. This file actually doesn't exist on OS X > installations, and can be found under bundle/Classes/classes.jar. The > attached patch fixes this issue, and is backwards compatible with other OS > (just tries another additional location). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
