William Ferguson created MASSEMBLY-838:
--
Summary: Assembly descriptor schemas are missing from web site
Key: MASSEMBLY-838
URL: https://issues.apache.org/jira/browse/MASSEMBLY-838
Project: Maven A
[
https://jira.codehaus.org/browse/MASSEMBLY-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344701#comment-344701
]
William Ferguson commented on MASSEMBLY-671:
NB I would open the issue again if I co
[
https://jira.codehaus.org/browse/MASSEMBLY-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344699#comment-344699
]
William Ferguson commented on MASSEMBLY-671:
Sent pull request containing a simple m
[
https://jira.codehaus.org/browse/MSHARED-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343754#comment-343754
]
William Ferguson commented on MSHARED-326:
--
Thanks Herve.
And thanks for the pointer to t
[
https://jira.codehaus.org/browse/MSHARED-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343713#comment-343713
]
William Ferguson commented on MSHARED-326:
--
Wish we had a GIT repo to submit too instead
[
https://jira.codehaus.org/browse/MSHARED-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MSHARED-326:
-
Patch Submitted: Yes
Issue Type: Bug (was: Improvement)
> Patch that enables all ma
[
https://jira.codehaus.org/browse/MSHARED-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343662#comment-343662
]
William Ferguson commented on MSHARED-326:
--
These changes work find for Maven 3.0 and 3.1
William Ferguson created MSHARED-326:
Summary: Patch that enables all maven-dependency-tree ITs
Key: MSHARED-326
URL: https://jira.codehaus.org/browse/MSHARED-326
Project: Maven Shared Components
Add a DateBuilt field to the Build Information section of the Project Summary
page
--
Key: MSITE-485
URL: http://jira.codehaus.org/browse/MSITE-485
Project: Maven 2.x Sit
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MAVENUPLOAD-2312:
--
Attachment: hibernate-entitymanager-3.4.0.GA.pom
There seems to be a problem wi
[
http://jira.codehaus.org/browse/MDEP-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson closed MDEP-123.
-
Resolution: Fixed
Fix Version/s: 2.0
It appears that an excellent solution for this was provide in
[
http://jira.codehaus.org/browse/MCHANGES-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121209
]
William Ferguson commented on MCHANGES-78:
--
JIRA already has a plugin that integrates with SVN and its grammar is:
dependency:tree to optionally display all instances of a transitive dependency,
not just the first one found
Key: MDEP-123
URL: http://jira.codehaus.org/b
[
http://jira.codehaus.org/browse/MDEP-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MDEP-123:
--
Attachment: pom.xml
> dependency:tree to optionally display all instances of a transitive
> dependency
UnsupportedOperationException on depdendency:analyze
Key: MDEP-121
URL: http://jira.codehaus.org/browse/MDEP-121
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components:
Too much irrelevant information generated at INFOduring execution of Site goal
--
Key: MSITE-272
URL: http://jira.codehaus.org/browse/MSITE-272
Project: Maven 2.x Site Plugin
[
http://jira.codehaus.org/browse/MSITE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114274
]
William Ferguson commented on MSITE-255:
Forgot to mention, the above failure can be seen when executing the following
[
http://jira.codehaus.org/browse/MSITE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MSITE-255:
---
Attachment: dev-200.zip
Dennis, its caused by the faq.fml not having any faq elements within the par
[
http://jira.codehaus.org/browse/MRELEASE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113615
]
William Ferguson commented on MRELEASE-280:
---
According to the stacktrace you are getting this on release:prepare
[
http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113267
]
William Ferguson commented on MNG-3244:
---
Brian, we all seem to want this fix, but don't want to break existing behaviour
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110709
]
William Ferguson commented on MNG-2290:
---
Joerg, I'm satisfied that all my concerns raised with this issue have been
reso
[
http://jira.codehaus.org/browse/MRESOURCES-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110137
]
William Ferguson commented on MRESOURCES-47:
Thanks Mauro, 2.3-20071013.152223-3 is good.
> POM properties ca
[
http://jira.codehaus.org/browse/MJAR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110124
]
William Ferguson commented on MJAR-83:
--
Thanks Mauro, the maven-jar-plugin-2.2-20071013.140436-2 snapshot works like
dream
Documentation for configuring for Tomcat is invalid
---
Key: MRM-545
URL: http://jira.codehaus.org/browse/MRM-545
Project: Archiva
Issue Type: Bug
Components: documentation
Affect
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109252
]
William Ferguson commented on MNG-2290:
---
Joerg,
I've come to the conclusion that while this is definitely an issue that
[
http://jira.codehaus.org/browse/MRELEASE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107800
]
William Ferguson commented on MRELEASE-211:
---
Um, correct me if I'm wrong, but isn't this what the *useReleaseProf
[
http://jira.codehaus.org/browse/MRELEASE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107334
]
William Ferguson commented on MRELEASE-270:
---
I have validated that the fix for http://jira.codehaus.org/browse/MN
[
http://jira.codehaus.org/browse/MNG-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107214
]
William Ferguson edited comment on MNG-3099 at 9/13/07 12:57 AM:
-
Invoking a Mojo that doesn't
[
http://jira.codehaus.org/browse/MNG-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MNG-3099:
--
Attachment: Plugin-showing-MNG3099.zip
Invoking a Mojo that doesn't require a project (ie [EMAIL PROTEC
[
http://jira.codehaus.org/browse/MJAR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MJAR-83:
-
Attachment: patch.txt
The patch adds @requiresDependencyResolution tags of *runtime* to
* JarMojo
* JarSig
[
http://jira.codehaus.org/browse/MJAR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106350
]
William Ferguson edited comment on MJAR-83 at 9/3/07 10:29 PM:
---
The patch adds @requiresDependency
[
http://jira.codehaus.org/browse/MJAR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106345
]
William Ferguson commented on MJAR-83:
--
The workaround for this is to
* List all deps with a scope of compile
* Execute *mv
addClasspath is not respected for runtime dependencies
--
Key: MJAR-83
URL: http://jira.codehaus.org/browse/MJAR-83
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.1,
Output the dependencies in a consistent and natural order
-
Key: MDEP-107
URL: http://jira.codehaus.org/browse/MDEP-107
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
[
http://jira.codehaus.org/browse/MNG-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105594
]
William Ferguson commented on MNG-3112:
---
Deepal, your description of the problem is a little vague.
But perhaps this issu
[
http://jira.codehaus.org/browse/MRESOURCES-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MRESOURCES-47:
---
Attachment: MRESOURCES-47-maven-resources-plugin.patch
Here's the patch for this issue,
POM properties cannot be accessed within a filter file
--
Key: MRESOURCES-47
URL: http://jira.codehaus.org/browse/MRESOURCES-47
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affec
[
http://jira.codehaus.org/browse/WAGON-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104150
]
William Ferguson commented on WAGON-73:
---
Ah good. I'd just realised that my cursory investigation from before was a
litt
[
http://jira.codehaus.org/browse/WAGON-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104148
]
William Ferguson commented on WAGON-73:
---
I can't checkout the all the code necessary to fully inspect this right now,
bu
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104043
]
William Ferguson commented on MNG-2290:
---
Yes, but that doesn't solve this issue.
Essentially the whole childPathAdjustmen
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103905
]
William Ferguson commented on MNG-2290:
---
Well if you do, I'll have to create another issue with the same title and copy
[
http://jira.codehaus.org/browse/ARCHETYPE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103904
]
William Ferguson commented on ARCHETYPE-39:
---
Thanks Wendy, though I think you meant
\ ${artifactId}
(without t
[
http://jira.codehaus.org/browse/WAGON-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103900
]
William Ferguson commented on WAGON-73:
---
OK, our workaround to this bug (overriding the central repository in
settings.x
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103841
]
William Ferguson commented on MNG-2290:
---
Sorry Jorge, you lost me.
The URL *is* inherited (if it is not specified in the
[
http://jira.codehaus.org/browse/ARCHETYPE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103839
]
William Ferguson commented on ARCHETYPE-59:
---
The workaround for this is to specify a 'remoteRepositories' propert
[
http://jira.codehaus.org/browse/ARCHETYPE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103824
]
William Ferguson commented on ARCHETYPE-39:
---
For those interested in a solution, specify
#set($dollar = '$')
at
[
http://jira.codehaus.org/browse/ARCHETYPE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103823
]
William Ferguson commented on ARCHETYPE-39:
---
OK, I'm confused.
The issue is marked as WON'T FIX, but the comment
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103822
]
William Ferguson commented on MNG-2290:
---
The work around for this is top specify the project#url and
project#distributi
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92415
]
William Ferguson edited comment on MNG-2290 at 8/1/07 6:35 PM:
---
It doesn't need to be a complex pr
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92415
]
William Ferguson edited comment on MNG-2290 at 8/1/07 6:35 PM:
---
It doesn't need to be a complex pr
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103820
]
William Ferguson edited comment on MNG-2290 at 8/1/07 6:34 PM:
---
I realise I wasn't as clear in my
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103820
]
William Ferguson commented on MNG-2290:
---
I realise I wasn't as clear in my comment above as I could have been. So I'll
t
[
http://jira.codehaus.org/browse/MRELEASE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103062
]
William Ferguson commented on MRELEASE-270:
---
NB the attached zip contains a project with uncompilable source.
>
release:prepare doesn't fail when the project it is building fails to compile
-
Key: MRELEASE-270
URL: http://jira.codehaus.org/browse/MRELEASE-270
Project: Maven 2.x Release
[
http://jira.codehaus.org/browse/MRELEASE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson closed MRELEASE-212.
-
Resolution: Won't Fix
I got around this issue by retrieving the information from Subversion d
[
http://jira.codehaus.org/browse/MRELEASE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson closed MRELEASE-213.
-
Resolution: Won't Fix
I got around this issue by retrieving the information from Subversion d
[
http://jira.codehaus.org/browse/WAGON-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated WAGON-73:
--
Attachment: WAGON-73-ConnectAndGetTest.patch
OK, can we get this issued reopened now?
The test case th
[
http://jira.codehaus.org/browse/WAGON-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97452
]
William Ferguson commented on WAGON-75:
---
Sorry about that, managed to attach the patch to the wrong issue twice in a row.
[
http://jira.codehaus.org/browse/WAGON-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated WAGON-75:
--
Attachment: WAGON-73-ConnectAndGetTest.patch
OK, can we get this issued reopened now?
The test case th
[
http://jira.codehaus.org/browse/WAGON-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated WAGON-75:
--
Attachment: WAGON-73-ConnectAndGetTest.patch
OK, can we get this issued reopened now?
The test case th
[
http://jira.codehaus.org/browse/MRELEASE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97112
]
William Ferguson commented on MRELEASE-236:
---
>From recollection it was originally
scm:svn:http://iago.oz.hubbub.c
[
http://jira.codehaus.org/browse/WAGON-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97032
]
William Ferguson commented on WAGON-73:
---
Can we get this reopened please.
Phil's patch has not been applied and AFAICT #co
[
http://jira.codehaus.org/browse/MRELEASE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MRELEASE-235:
--
Attachment: MRELEASE-235-patch.txt
This patch adds another preparation phase (run-post-prep
ArrayindexoutofBoundsException rewriting the Poms for release
-
Key: MRELEASE-236
URL: http://jira.codehaus.org/browse/MRELEASE-236
Project: Maven 2.x Release Plugin
Issue Type: Bug
[
http://jira.codehaus.org/browse/MRELEASE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MRELEASE-236:
--
Attachment: MRELEASE-236-patch.txt
I believe this patch fixes the issue.
> Arrayindexoutof
[
http://jira.codehaus.org/browse/MRELEASE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MRELEASE-236:
--
Attachment: pom.xml
I've attached the POM that was causing the problem.
Though I think its
Need ability to execute goals during prepare after scm-tag but before
scm-commit-development phase
--
Key: MRELEASE-235
URL: http://jira.codehaus.org/browse/MRELEASE-2
RewritePomsForReleasePhase requires JDK 5.0
---
Key: MRELEASE-234
URL: http://jira.codehaus.org/browse/MRELEASE-234
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-5
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92415
]
William Ferguson commented on MNG-2290:
---
It doesn't need to be a complex project structure for this to cause pain.
I would
[
http://jira.codehaus.org/browse/MRELEASE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91996
]
William Ferguson commented on MRELEASE-213:
---
Loks like I also need access to the SCM version that has been checked
[
http://jira.codehaus.org/browse/MRELEASE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91963
]
William Ferguson commented on MRELEASE-212:
---
Thanks Emmanuel - that does allow the property to get passed in.
I w
Need ability to access values gathered by maven-release-plugin in Mojos
executed as part of preparationGoals element
Key: MRELEASE-213
URL: http:/
Mojo executed using preparationGoals does not get its parameters populated on
execution
---
Key: MRELEASE-212
URL: http://jira.codehaus.org/browse/MRELEASE-212
Projec
[ http://jira.codehaus.org/browse/MNGECLIPSE-124?page=comments#action_78147
]
William Ferguson commented on MNGECLIPSE-124:
-
Sorry, to be clear - I still the issue in version 0.0.9
> Plugin fail to initialize when default maven repo
[ http://jira.codehaus.org/browse/MNGECLIPSE-124?page=comments#action_78146
]
William Ferguson commented on MNGECLIPSE-124:
-
I still see the issue relating to the embedder not reading the location of the
local repository from the M2
[ http://jira.codehaus.org/browse/MSUREFIRE-148?page=comments#action_76940
]
William Ferguson commented on MSUREFIRE-148:
I presume that the appropriate work around for this is to move your local
repository to somewhere that doesn't
76 matches
Mail list logo
