[
https://jira.codehaus.org/browse/MANTTASKS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358068#comment-358068
]
Paul King commented on MANTTASKS-213:
-
Michael, thanks for the info. Before I try to create
[
https://jira.codehaus.org/browse/MEV-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280329#comment-280329
]
Paul King commented on MEV-624:
---
actually it looks like xalan:xalan is fixed but xalan:serializer is sti
[
https://jira.codehaus.org/browse/MANTTASKS-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272977#comment-272977
]
Paul King commented on MANTTASKS-213:
-
I suspect it affects all embedded usage of the maven
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211610#action_211610
]
Paul King commented on MAVENUPLOAD-2695:
Thanks for fixing it so fast! The issue trend
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211608#action_211608
]
Paul King commented on MAVENUPLOAD-2695:
Cool. That looks better now - give or take wha
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211605#action_211605
]
Paul King commented on MAVENUPLOAD-2695:
Alternatively, the files here look OK:
http://
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211600#action_211600
]
Paul King edited comment on MAVENUPLOAD-2695 at 2/25/10 6:01 AM:
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul King updated MAVENUPLOAD-2695:
---
Attachment: junit-4.8.1-sources.jar
junit-4.8.1.jar
> NOT A DEVELOPER
> -
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211600#action_211600
]
Paul King commented on MAVENUPLOAD-2695:
I can supply valid versions of the first two j
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211599#action_211599
]
Paul King commented on MAVENUPLOAD-2695:
In the bundle jar, there seems to be a number
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117479
]
Paul King commented on MEV-549:
---
I am keen to close off this issue. Groovy 1.5 is out. So I feel less need to
have perfect 1.0 ar
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112602
]
Paul King commented on MEV-549:
---
Not specifically related, but the 1.1-rc-2 release went ahead over the last 24
hrs and (after ou
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112394
]
Paul King commented on MEV-549:
---
It would be nice to copy:
http://dist.codehaus.org/groovy/poms/groovy-1.0.pom
to:
http://repo1.ma
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112321
]
Paul King commented on MEV-549:
---
OK, for the 1.1 milestone releases, the simplest path to correct the errant
poms is to ignore th
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112196
]
Paul King edited comment on MEV-549 at 10/31/07 2:44 AM:
-
Yes, I believe we are trying to use the mechan
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112196
]
Paul King commented on MEV-549:
---
Yes, I believe we are trying to use the mechanism designed for publishing to
the maven1 repo whi
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112192
]
Paul King edited comment on MEV-549 at 10/31/07 2:14 AM:
-
Do we need to remove the link in the maven 1 r
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul King reopened MEV-549:
---
We still need to do the groovy and groovy-all-minimal artifacts
> Strange Groovy entries in the repository
>
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112192
]
Paul King commented on MEV-549:
---
Do we need to remove the link in the maven 1 repo? Currently I think the
mechanism for copying g
[
http://jira.codehaus.org/browse/MEV-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112185
]
Paul King commented on MEV-553:
---
I don't know how but my guess is that it is related to this: HAUS-1560, the
timing feels right b
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112143
]
Paul King commented on MEV-549:
---
Brilliant, thanks. The only other thing I noticed for the groovy-all artifacts
is that:
http://r
[
http://jira.codehaus.org/browse/MEV-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112132
]
Paul King commented on MEV-553:
---
As a work-around until this is fixed, you can exclude castor as a dependency of
openejb and then
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111926
]
Paul King commented on MEV-549:
---
1.1-beta-1 was a change in decision about case in naming the release but
1.1-BETA-1 was already
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111664
]
Paul King edited comment on MEV-549 at 10/28/07 3:51 AM:
-
Take 2: Let me know if this sounds OK.
Please
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111664
]
Paul King commented on MEV-549:
---
Take 2: Let me know if this sounds OK.
Please remove the following file as it is unusable:
maven
[
http://jira.codehaus.org/browse/MEV-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111643
]
Paul King commented on MEV-550:
---
Please swap to using the groovy-all-minimal artifact for 1.0. If you need the
optional dependenc
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111616
]
Paul King commented on MEV-549:
---
Seems like the sanctioned way forward is to leave these spurious entries where
they are but we s
[
http://jira.codehaus.org/browse/MEV-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111395
]
Paul King commented on MEV-550:
---
I will own up to adding the groovy 1.0 pom. I extracted the pom from version
control that we use
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111336
]
Paul King commented on MEV-549:
---
Re: I just looked at maven2/groovy/groovy/1.1-rc-1/* and i don't see what's
"unusable" about it,
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111229
]
Paul King commented on MEV-549:
---
Thanks Carlos. They are already gone from codehaus.
Here are the spurious entries:
maven2/groov
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111202
]
Paul King commented on MEV-549:
---
Well, that depends on what you mean by unusable. All of the correct artifacts
are already in the
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110989
]
Paul King commented on MEV-549:
---
Thanks Carlos, that info helped me track down the problem. Looks like we hadn't
updated our doco
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110952
]
Paul King commented on MEV-549:
---
Forgot to ask. Is there any way to stop the m1 to m2 auto conversion for a
particular artifactId
[
http://jira.codehaus.org/browse/MEV-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110951
]
Paul King commented on MEV-549:
---
Thanks for the info. Our project build process definately doesn't publish to
http://dist.codehau
Strange Groovy entries in the repository
Key: MEV-549
URL: http://jira.codehaus.org/browse/MEV-549
Project: Maven Evangelism
Issue Type: Task
Components: Relocation
Reporter: Pau
[
http://jira.codehaus.org/browse/MEV-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105204
]
Paul King commented on MEV-540:
---
thanks
> Please remove incorrectly copied snapshot directories for Groovy
>
[
http://jira.codehaus.org/browse/MEV-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105193
]
Paul King commented on MEV-540:
---
I should also have mentioned that the SNAPSHOT version is available from
http://snapshots.reposi
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103558
]
Paul King commented on MAVENUPLOAD-1619:
Any suggestions on the path forward? Is there a standard maven way to
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102908
]
Paul King edited comment on MAVENUPLOAD-1619 at 7/22/07 9:25 PM:
-
It is needed to compi
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102908
]
Paul King commented on MAVENUPLOAD-1619:
It is needed to compile a production class file. The class file is onl
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102899
]
Paul King commented on MAVENUPLOAD-1619:
Actually, thinking a bit more about this, junit is a required compile-
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102867
]
Paul King commented on MAVENUPLOAD-1619:
Changing the dependencies to the following was what I required to comp
Please remove incorrectly copied snapshot directories for Groovy
Key: MEV-540
URL: http://jira.codehaus.org/browse/MEV-540
Project: Maven Evangelism
Issue Type: Bug
[ http://jira.codehaus.org/browse/MEV-451?page=comments#action_81032 ]
Paul King commented on MEV-451:
---
Is there anything else that needs to be done ot move this along? Thanks, Paul.
> pom for xmlbeans:xbean:2.2
> --
>
>
[ http://jira.codehaus.org/browse/MEV-451?page=all ]
Paul King updated MEV-451:
--
Attachment: xbean-2.2.0.pom
I added further info. The only thing left out is the dependency on Saxon 8.6.1
which isn't in the repository so I left that out and I think this may be
[ http://jira.codehaus.org/browse/MEV-451?page=comments#action_79765 ]
Paul King commented on MEV-451:
---
So, is there anything wrong with the 2.1.0 pom, if not, then the attached is
what you are after.
> pom for xmlbeans:xbean:2.2
> ---
[ http://jira.codehaus.org/browse/MEV-451?page=all ]
Paul King updated MEV-451:
--
Attachment: xbean-2.2.0.pom
Attached the one we are using with 2.2.0 - it is just a modified version from
2.1.0
> pom for xmlbeans:xbean:2.2
> --
>
>
[ http://jira.codehaus.org/browse/MEV-456?page=comments#action_78131 ]
Paul King commented on MEV-456:
---
Thanks.
> BSF 2.4.0 is missing a M2 POM file
> --
>
> Key: MEV-456
> URL: http:/
[ http://jira.codehaus.org/browse/MEV-456?page=all ]
Paul King updated MEV-456:
--
Attachment: bsf.pom
attached
> BSF 2.4.0 is missing a M2 POM file
> --
>
> Key: MEV-456
> URL: http://jira.codehaus
BSF 2.4.0 is missing a M2 POM file
--
Key: MEV-456
URL: http://jira.codehaus.org/browse/MEV-456
Project: Maven Evangelism
Issue Type: Bug
Components: Missing POM
Reporter: Paul King
50 matches
Mail list logo
