[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18772:
----------------------------------------
{quote}Re: the Take 2 solution... that looks OK but ONLY for project builds.{quote}
Ok, so we could move this to parent pom. However, there are other thing we deploy (via regular Nexus) that depend on this parent pom and that won't like this plugin. Is it possible to make the rsync.sh just "warn" when the source folder ("target/repository") doesn't exist?
{quote}Aggregate builds need TWO pushes [one into builds, one into updates]{quote}
Ok. We can add an additional invocation of the rsync.sh in the aggregate.
{quote}and the matrix job that handles webtools/central/EA must make sure it's passing in the correct paths, since the JOB_NAME doesn't include the name of the matrix config (eg., webtools-site, central-site, earlyaccess-site). {quote}
I plan to make the deploy url a property that can be overriden via CLI.
This approach makes that we'll slowly prefer avoiding JOB_NAME and other Jenkins property in favor of properties that are inside the pom directly.
> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha2
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3383:
--------------------------------------
{quote}
I haven't done a PR for JBDS.1 above (`include in JBDS core .feature so it's installed by default via installer jar`), because if I use <include>, we will have to include this patch feature in any future 8.1.x releases, even if it's replaced by a future WTP 3.6.4 release.
{quote}
What about adding this patch feature to the installer as we do it for testng? - https://github.com/jbdevstudio/jbdevstudio-product/pull/287
I don't like the idea to include it to JBDS core feature.
> Include Feature Patch for WTP 3.6.3 into JBDS 8.1
> -------------------------------------------------
>
> Key: JBDS-3383
> URL: https://issues.jboss.org/browse/JBDS-3383
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 8.1.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 8.1.0.GA
>
> Attachments: WTP Patches 3.6.3-P.png
>
>
> When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream.
> JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160]
> Can we apply this fix into JBDS 8.1?
> Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug.
> Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-618) 8.1.0.CR1 release notes are listed under Beta1
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-618?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-618:
------------------------------------
We usually just use web labels to make the Version appear to be {Version} Beta for non-GA content, and then just {Version} for GA content.
The reason we just use Beta to indicate non-GA content (and usually Release Notes have the specific milestone in the title instead) is to prevent unnecessary overhead in changing the version web label and republishing all docs, irrespective of any actual updates, to the new version. Unless there is a compelling reason for extra work in updating the metadata for every single document for every milestone, docs would prefer to continue to use this way to indicate the changes.
Would you prefer to discuss this some more, [~mmalina] (which I am happy to do) or are you OK to close this as NOTABUG?
> 8.1.0.CR1 release notes are listed under Beta1
> ----------------------------------------------
>
> Key: TOOLSDOC-618
> URL: https://issues.jboss.org/browse/TOOLSDOC-618
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Affects Versions: 4.2.3.CR1
> Reporter: Martin Malina
> Assignee: Misha Ali
> Fix For: 4.2.3.Final
>
>
> I noticed that JBDS 8.1.0.CR1 Release Notes are listed under 8.1.0.Beta1 version of the product:
> https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu...
> In the URL it says just 8.1, so it seems that this will eventually be used for all 8.1 (GA) docs. Maybe. But right now it seems a bit confusing.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years