OK, so the bug here is that I'm reusing something of the github path
to create a temp folder / file to house the downloaded sources from
github. I'll need to ensure that colons and ats are replaced with
something that's more path-friendly.

https://issues.jboss.org/browse/JBIDE-20839

Regarding Portlet, if you want to update its root pom, bump its
versions, commit your changes, and rebuild it in the
jbosstools-portlet_master job, feel free. I'm not convinced we need to
INCLUDE those new built versions however, but your test might show
there's a problem which DOES require us to rebuild to be
Neon-compatible.

I'll let you open a JIRA for that task.

On Tue, Sep 29, 2015 at 1:38 PM, Denis Golovin <dgolovin@exadel.com> wrote:
>
>
> On Tue, Sep 29, 2015 at 2:17 AM, Max Rydahl Andersen <manderse@redhat.com>
> wrote:
>>
>> On 25 Sep 2015, at 14:08, Nick Boldt wrote:
>>
>>> 1. You have a colon and @ in your /tmp path. Try again with a less
>>> unfriendly path?
>>
>>
>> is this not the build itself that does this ?
>>
>> this is this funky workaround where instead of git cloning from
>> jbdevstudio it
>> uses the disk since otherwise it needs to be authorised ?
>
>
> I have no answers for any of yo questions, because I didn't look inside the
> code.
>
> For me this downloading it another build overhead, because we already have
> sources in resulting repository for JBDS and I would rather find the way to
> use them instead of downloading them again.
>
>>
>>
>>
>>> 2. Portlet is not currently being built at all. It has no new commits
>>> since
>>> JBT 4.2.x.
>>
>>
>> yup, which is why we got
>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L107
>> in parent pom (using luna build).
>>
>> Denis - your overall build should not have to build portlet at the moment
>> I would think ?
>
>
> I know we have it in parent.pom, but still it is not confirmed that it
> compiles with eclipse neon and with every TP update to include latest
> Eclipse M build there is a chance the portlet build fails, but we would not
> know, because we don't even build it.
>
> Denis
>
>>
>> /max
>>
>>> On Sep 24, 2015 10:52 PM, "Denis Golovin" <dgolovin@exadel.com> wrote:
>>>
>>>> All JBoss Tools projects can be built with latest TP, but I still have
>>>> couple glitches:
>>>> 1. jbds sources download fails 8 out of 10 builds
>>>> [INFO] [ERROR] Failed to execute goal
>>>>
>>>> org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests
>>>> (fetch-sources) on project com.jboss.devstudio.core.site: Error cloning
>>>> from /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product
>>>> to
>>>>
>>>> /tmp/git@github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip:
>>>>
>>>> /tmp/git@github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip
>>>> (No such file or directory) -> [Help 1]
>>>>
>>>> 2. Portlet is not using parent pom 4.4.0.Alpha2-SNAPSHOT.
>>>> On 09/23/2015 10:37 PM, Nick Boldt wrote:
>>>>
>>>> Seems legit. Merge with impunity.
>>>>
>>>> Merged with impunity.
>>>>
>>>>
>>>> --
>>>> Mickael Istria
>>>> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
>>>> My blog <http://mickaelistria.wordpress.com> - My Tweets
>>>> <http://twitter.com/mickaelistria>
>>>>
>>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>>> confidential. If you are not the intended recipient you are hereby
>>>> notified
>>>> that using, copying, distributing or taking any action in reliance on
>>>> the
>>>> contents of this information is strictly prohibited. If you have
>>>> received
>>>> this email in error please notify the sender and delete this email.
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev@lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>>> confidential. If you are not the intended recipient you are hereby
>>>> notified
>>>> that using, copying, distributing or taking any action in reliance on
>>>> the
>>>> contents of this information is strictly prohibited. If you have
>>>> received
>>>> this email in error please notify the sender and delete this email.
>>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>> --
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>
>
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.

--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

--


CONFIDENTIALITY NOTICE: This email and files attached to it are
confidential. If you are not the intended recipient you are hereby notified
that using, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited. If you have received
this email in error please notify the sender and delete this email.