[jbosstools-issues] [JBoss JIRA] (JBIDE-15145) Published site (on Nexus) doesn't contain .pack.gz files

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12822892#comment-12822892 ] 

Nick Boldt commented on JBIDE-15145:
------------------------------------

For the Locus 1.1.0 release, do we NEED .pack.gz files? Why not just deploy w/o 'em and wait until this is fixed upstream to release a 1.1.1 WITH .pack.gz files? #deferral

Or failing that, if it's really important that we have pack200'd files, we can publish to dl.jb.org like we do for everything else in JBoss Tools land. #workaround
                
> Published site (on Nexus) doesn't contain .pack.gz files
> --------------------------------------------------------
>
>                 Key: JBIDE-15145
>                 URL: https://issues.jboss.org/browse/JBIDE-15145
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, locus, upstream
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 1.1.0-LOCUS
>
>
> This is a general issue with Maven:
> $ mvn clean verify -P pack200
> $ cd site
> $ mvn clean verify -P pack200
> makes that output site in site/target/repository doesn't contain .pack.gz files for the dependencies that are installed in Maven repo.
> This is a general Tycho issue. We need to make sure this use-case.gets fixed in next version of Tycho. It seems related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=393004

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