[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111898
]
Daniel Kulp commented on MEV-498:
-
Created upload request for a 2.1-1 version.
http://jira.codehaus.org/browse/MAVENUPLOAD-178
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104806
]
Carlos Sanchez commented on MEV-498:
the solution was already proposed, we can host a 2.1-1 with the right pom and
jar, but
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104785
]
Dan Tran commented on MEV-498:
--
Marat, here is the work around
- install a good copy of javax-api at your internal repo.
- U
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104718
]
Carlos Sanchez commented on MEV-498:
Marat, that's not our responsibility, by definition releases shouldn' t be
changed on
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104698
]
Marat Radchenko commented on MEV-498:
-
This isn't good. My pom refers to both repo1 and java.net. I don't have any
means to
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98896
]
Henri Yandell commented on MEV-498:
---
Seems that this issue should be WONTFIX -> request 2.1-1 release. Sound right?
> javax.xm
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87378
]
Carlos Sanchez commented on MEV-498:
> jaxws-maven-plugin is in an odd situation where most of its dependencies are
> in jav
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87337
]
Dan Tran commented on MEV-498:
--
jaxws-maven-plugin is in an odd situation where most of its dependencies are in
java.net maven1 rep
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87330
]
Carlos Sanchez commented on MEV-498:
The fact that it's incorrect doesn't make it unusable. Unusable means jar
corrupt or em
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87328
]
Dan Tran commented on MEV-498:
--
I beleive it is unuable since the the jaxws-api at java.net has the correct
dependencies and the ja
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87320
]
Carlos Sanchez commented on MEV-498:
no, it's policy not to remove anything unless it's clearly unusable.
> javax.xml.ws:ja
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87278
]
Dan Tran commented on MEV-498:
--
Can you remove it from repo1?
> javax.xml.ws:jaxws-api:2.1 is bad
> ---
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87021
]
Carlos Sanchez commented on MEV-498:
that's what i did, but they changed it after sync, what can I do ?
the only thing that c
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86882
]
Dan Tran commented on MEV-498:
--
So what should we do? having the old jaxws-api-2.1 is also bad. Perhaps repo1
should leave the bu
[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86879
]
Carlos Sanchez commented on MEV-498:
They messed up, you can see how they kept changing the jar
https://maven-repository.dev.
15 matches
Mail list logo
