[jetty-dev] [jira] (JETTY-1493) Maven Dependency Behaviour Orbit Package Type

    [ https://jira.codehaus.org/browse/JETTY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297273#comment-297273 ] 

Jesse McConnell commented on JETTY-1493:
----------------------------------------

the packaging associated with 'jar' would not produce the jar in question here, the jar is built through an entirely different and somewhat alien incantation unique to eclipse orbit project...while I would like it to be jar it was not that easy to make happen an this approach addressed out immediate issues.

ideally at some point we'll have orbit goop published to central (which is a whole other nightmare of issues) so we can just use those, but for now this works fine and only mucks up other tooling which have ways to address it

its not ideal, but it is a whole lot better and brings us back to a reproducible build state that doesn't involve downloading jars with antrun scripting from non-durable orbit p2 repositories

I don't _like_ this approach anymore then anyone else, but its functioning
                
> Maven Dependency Behaviour Orbit Package Type
> ---------------------------------------------
>
>                 Key: JETTY-1493
>                 URL: https://jira.codehaus.org/browse/JETTY-1493
>             Project: Jetty
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: 7.6.1
>         Environment: Apache Ivy
>            Reporter: Andre Ben Hamou
>            Assignee: Jesse McConnell
>
> http://mvnrepository.com/artifact/org.eclipse.jetty/jetty-server/7.6.1.v20120215
> depends on
> http://mvnrepository.com/artifact/org.eclipse.jetty.orbit/javax.servlet/2.5.0.v201103041518
> The latter has a package type of 'orbit' which causes maven to think the target extension should be '.orbit'. Since it's actually a JAR, both the button on the latter page (Download (ORBIT)) and my local Ivy resolution chain are broken.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email