Marcel Schutte created MENFORCER-318:
Summary: Upgrading maven-enforcer-plugin from 1.4 to 1.4.1 or
higher breaks maven-assembly-plugin
Key: MENFORCER-318
URL: https://issues.apache.org/jira/browse/MENFORCER-3
[
https://issues.apache.org/jira/browse/MNG-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144980#comment-15144980
]
Marcel Schutte commented on MNG-5935:
-
Thanks for fixing this, I can confirm that my iss
[
https://issues.apache.org/jira/browse/MNG-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Schutte updated MNG-5935:
Attachment: buildoutput.txt
Parent.zip
Sample project demonstrating my problem and out
Marcel Schutte created MNG-5935:
---
Summary: Optional true getting lost in dependency resolution when
transitive and having dependency management in different pom
Key: MNG-5935
URL: https://issues.apache.org/jira/brow
[
https://issues.apache.org/jira/browse/ARCHETYPE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Schutte updated ARCHETYPE-485:
-
Attachment: ARCHETYPE-485-maven-archetype.patch
patch against commit d2e45a6
> support
Marcel Schutte created ARCHETYPE-485:
Summary: support merge of dependencyManagement
Key: ARCHETYPE-485
URL: https://issues.apache.org/jira/browse/ARCHETYPE-485
Project: Maven Archetype
I
Error found in code: wrong order of parameters in createRepository for repo in
a profile in settings.xml
Key: MNG-4272
URL: http://jira.codehaus.org/browse/MN
Replace the current 'arguments' parameter with specialized version for each
mojo (eg. 'argumentsRelease')
-
Key: MRELEASE-282
URL: http://jira.codehaus.org/bro
[
http://jira.codehaus.org/browse/MJAVADOC-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105433
]
Marcel Schutte commented on MJAVADOC-135:
-
The following output shows why the AbstractJavadocMojo.getJavadocVersion
[
http://jira.codehaus.org/browse/MEAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104746
]
Marcel Schutte commented on MEAR-53:
Stephane,
Could you please release 2.3.1. This issue was fixed 7 months ago and I need
[
http://jira.codehaus.org/browse/MEAR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93586
]
Marcel Schutte commented on MEAR-60:
I agree that extra flexibility is needed. It is just that as far as I
understand maven,
Improve support for skinny war files
Key: MEAR-60
URL: http://jira.codehaus.org/browse/MEAR-60
Project: Maven 2.x Ear Plugin
Issue Type: Improvement
Affects Versions: 2.3
Environment: mvn 2.0
[ http://jira.codehaus.org/browse/MEAR-53?page=comments#action_84036 ]
Marcel Schutte commented on MEAR-53:
I've done a test with version 2.3.1-SNAPSHOT and it works as expected.
Thanks for your quick reaction.
> ejb-client dependencies shou
ejb-client dependencies should not be treated as J2EE application client modules
Key: MEAR-53
URL: http://jira.codehaus.org/browse/MEAR-53
Project: Maven 2.x Ear Plugin
[ http://jira.codehaus.org/browse/MRELEASE-91?page=comments#action_65807 ]
Marcel Schutte commented on MRELEASE-91:
Mike, I can follow your line of reasoning, it sounds like a valid way of
working. My reason for wanting to change everything in the re
[ http://jira.codehaus.org/browse/MRELEASE-91?page=comments#action_65798 ]
Marcel Schutte commented on MRELEASE-91:
See my original comment for this issue. There is an inconsistency between
handling of normal dependencies and dependencies in dependen
[ http://jira.codehaus.org/browse/MRELEASE-91?page=all ]
Marcel Schutte updated MRELEASE-91:
---
Attachment: depmgnt.zip
> Updating of dependencyManagement inconsistent with updating of dependencies
> with regard to SNAPSHOTs
> --
[ http://jira.codehaus.org/browse/MRELEASE-91?page=all ]
Marcel Schutte reopened MRELEASE-91:
Testing with mvn 2.0.4 and the 2.0-beta-4 version of release-plugin shows that
this issue is not yet fixed. Import the projects in the attached zip into y
release:prepare generates tags with dots, causing problems with CVS
---
Key: MRELEASE-110
URL: http://jira.codehaus.org/browse/MRELEASE-110
Project: Maven 2.x Release Plugin
Type: Bug
Versions: 2.0-
Username no longer defaults to the java system property user.name
-
Key: MRELEASE-109
URL: http://jira.codehaus.org/browse/MRELEASE-109
Project: Maven 2.x Release Plugin
Type: Bug
Versions: 2.0-beta
NullPointerException when POM has no SCM connection url
---
Key: MRELEASE-108
URL: http://jira.codehaus.org/browse/MRELEASE-108
Project: Maven 2.x Release Plugin
Type: Bug
Versions: 2.0-beta-4
Environment:
[ http://jira.codehaus.org/browse/MRELEASE-94?page=comments#action_64015 ]
Marcel Schutte commented on MRELEASE-94:
I've come across the same problem and I can confirm that it is cvs related. It
can be reproduced on cvsnt 2.5.03.2260 without using ma
make release:perform upload progress overwrite the previous xxK/yyK uploaded
line
-
Key: MRELEASE-97
URL: http://jira.codehaus.org/browse/MRELEASE-97
Project: Maven 2.x Release Plugin
Ty
[ http://jira.codehaus.org/browse/MRELEASE-91?page=comments#action_63509 ]
Marcel Schutte commented on MRELEASE-91:
I forgot to mention that I'm using the latest SVN of the release plugin.
> Updating of dependencyManagement inconsistent with updating
Updating of dependencyManagement inconsistent with updating of dependencies
with regard to SNAPSHOTs
Key: MRELEASE-91
URL: http://jira.codehaus.org/browse/MRELEASE-91
Projec
${pom.build.sourceDirectory} and ${pom.build.testSourceDirectory} no longer
recognized
--
Key: MNG-2220
URL: http://jira.codehaus.org/browse/MNG-2220
Project: Maven 2
Type: Bug
Co
JarMojoTest uses wrong import for maven-plugin-testing-harness
--
Key: MJAR-36
URL: http://jira.codehaus.org/browse/MJAR-36
Project: Maven 2.x Jar Plugin
Type: Test
Versions: 2.1
Environment: n/a
27 matches
Mail list logo