[jira] [Commented] (MBUILDCACHE-49) Allow caching for pom package projects
[
https://issues.apache.org/jira/browse/MBUILDCACHE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739131#comment-17739131
]
Felix Simmendinger commented on MBUILDCACHE-49:
---
It is not only the build logic. The comment in the
{{org.apache.maven.buildcache.checksum.MavenProjectInput#getMutableDependencies}}
that it is sufficient to cache effective poms is wrong. In our project, we
have a pom module that serves as a dependency holder for runtime dependencies
to be managed by a command-line client to enable/disable extensions to an
application. With the extension ignoring to cache pom dependencies, the
depenency tracking is broken and changes to transitive dependencies referenced
by this pom project won't trigger a rebuild of the application module.
{code:java}
app
|
-
|\
libs `- module-x (type jar)
| (runtime scope, snapshot from same project)
extension-dependencies (type pom)
| (runtime scope, snapshot from same project)
`- extension-a (type jar, snapshot from same project){code}
if i change a line in extension-a, app won't be rebuild.
> Allow caching for pom package projects
> --
>
> Key: MBUILDCACHE-49
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-49
> Project: Maven Build Cache Extension
> Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Tomáš Mrázek
>Priority: Major
>
> In class `MavenProjectInput` and method `calculateChecksum()` at line `207`
> is check for pom project and if true, input files are skipped. What was the
> reason behind ignoring pom projects? I've seen plenty of pom projects with
> some build logic where caching does make a sense. For example some resource
> transformations or building external projects via exec-maven-plugin. In those
> cases both source and target files exist but different packaing other than
> pom does not make a lot of sense.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] Created: (SCM-637) parsing of git urls fails on windows
parsing of git urls fails on windows Key: SCM-637 URL: https://jira.codehaus.org/browse/SCM-637 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.5 Reporter: Felix Simmendinger Priority: Blocker please fix this issue raised in the release plugin http://jira.codehaus.org/browse/MRELEASE-624 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-190) deploy-file goal adding artifacts as attached items, prevents multiple executions of the goal in one module
Felix Simmendinger created MDEPLOY-190:
--
Summary: deploy-file goal adding artifacts as attached items,
prevents multiple executions of the goal in one module
Key: MDEPLOY-190
URL: https://jira.codehaus.org/browse/MDEPLOY-190
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Reporter: Felix Simmendinger
Priority: Blocker
If you define multiple {{deploy-file}} goal executions within one module, each
execution deploys also the artifacts of its predecessor. This is because the
goal adds attached artifacts which will then be deployed too with the next
execution. This seems to be introduced with MDEPLOY-134.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] Commented: (MJAVADOC-304) failOnError is ignored if javadoc:javadoc is called via Site Plugin 3.0-beta
[
http://jira.codehaus.org/browse/MJAVADOC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258509#action_258509
]
Felix Simmendinger commented on MJAVADOC-304:
-
This bug is very nasty since you have to configure your release plugin to use
preparationGoals "clean install" otherwise thirdparty javadoc references will
fail the build as those dependencies aren't present in the classpath of javadoc.
> failOnError is ignored if javadoc:javadoc is called via Site Plugin 3.0-beta
>
>
> Key: MJAVADOC-304
> URL: http://jira.codehaus.org/browse/MJAVADOC-304
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Sebastian Annies
> Attachments: MJAVADOC-304_IT_Test.patch, MJAVADOC-304_Patch.patch
>
>
> {{failOnError}} works for the case that javadoc:jar is executed. This
> invocation calls {{execute()}} and then {{generate(sink, locale)}}. The
> generate is surrounded with a try/catch-block catching any exception thrown
> by the javadoc generation. In case of {{failOnError==false}} the exception
> does not interrupt the build. That perfectly ok!
> {{failOnError}} does not work if it is called during site generation. During
> site generation only {{generate(sink, locale}} is called which misses the
> try/catch guard for failures during generation of javadoc.
> Effectively you cannot ignore failures during site generation.
--
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-1991) Can't get transitive dependencies from a war pom when this war is added as a depdency of a project
[ http://jira.codehaus.org/browse/MNG-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209657#action_209657 ] Felix Simmendinger commented on MNG-1991: - we work with skinny wars a lot and we got use to declare also a dependency to the pom of the war. By doing this you get all dependencies resolved and retrieved to the WEB-INF/lib dir. > Can't get transitive dependencies from a war pom when this war is added as a > depdency of a project > -- > > Key: MNG-1991 > URL: http://jira.codehaus.org/browse/MNG-1991 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.2 >Reporter: Emmanuel Venisse > Fix For: 3.x (to be reviewed) > > > I have a project (continuum-core-it) that need to use all transitive > dependencies of a war (continuum-webapp). If i add the war as a dependency of > the project with packaging war, war dependencies aren't shown by project, > maven doesn't try to resolve them and doesn't add them in classpath. > If if replace packaging from war to pom, all dependencies are resolved and > added to classpath. -- 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-4717) Repository Ids containing ":" will lead to checksum errors on Windows machines
Repository Ids containing ":" will lead to checksum errors on Windows machines
--
Key: MNG-4717
URL: http://jira.codehaus.org/browse/MNG-4717
Project: Maven 2 & 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.2.1
Environment: Windows 7
Reporter: Felix Simmendinger
If a repositorys id element contains a ":" character, maven tries to create a
{{repository-metadata-<>.xml}} file under certain circumstances
(in our case when version ranges are used). Under windows this is not possible
and will lead to an error looking like this:
{code}
[WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING
[WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING
[WARNING] repository metadata for: 'artifact XX:XX' could not be retrieved from
repository: YY:YY due to an error: Error copying temporary file to the final
destination: Die Syntax für den Dateinamen, Verzeichnisnamen oder die
Datenträgerbezeichnung ist falsch
{code}
The Problem is in
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata#getLocalFilename.
Better Logging, robustness check or documentation of this issue would be
helpfull.
--
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] (SCM-714) mvn release:prepare fails if the command line is too long on windows
Felix Simmendinger created SCM-714: -- Summary: mvn release:prepare fails if the command line is too long on windows Key: SCM-714 URL: https://jira.codehaus.org/browse/SCM-714 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.8.1 Reporter: Felix Simmendinger Priority: Blocker The issue from SCM-697 does not solve the issue as the gitprovider is not using the add command but the checkin command during a release. -- 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-714) mvn release:prepare fails if the command line is too long on windows
[ https://jira.codehaus.org/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321741#comment-321741 ] Felix Simmendinger commented on SCM-714: actually that would work but then each release would result in 100+ commits and that is not what you want. It is only the add command that needs to be splitted up in multiple steps. > mvn release:prepare fails if the command line is too long on windows > > > Key: SCM-714 > URL: https://jira.codehaus.org/browse/SCM-714 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.8.1 >Reporter: Felix Simmendinger >Priority: Blocker > > The issue from SCM-697 does not solve the issue as the gitprovider is not > using the add command but the checkin command during a release. -- 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-714) mvn release:prepare fails if the command line is too long on windows
[ https://jira.codehaus.org/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321741#comment-321741 ] Felix Simmendinger edited comment on SCM-714 at 3/11/13 3:25 AM: - actually that would work but then each release would result in 100+ commits and that is not what you want. It is only the add command that needs to be splitted up in multiple steps. For the maven-scm-plugin:add there is already the functionality to split up the adds. was (Author: fsimmend): actually that would work but then each release would result in 100+ commits and that is not what you want. It is only the add command that needs to be splitted up in multiple steps. > mvn release:prepare fails if the command line is too long on windows > > > Key: SCM-714 > URL: https://jira.codehaus.org/browse/SCM-714 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.8.1 >Reporter: Felix Simmendinger >Priority: Blocker > > The issue from SCM-697 does not solve the issue as the gitprovider is not > using the add command but the checkin command during a release. -- 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
