[JBoss JIRA] (JBIDE-15614) Add support for EAP 6.2
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-15614:
-------------------------------------
Assignee: Rob Stryker (was: Snjezana Peco)
> Add support for EAP 6.2
> -----------------------
>
> Key: JBIDE-15614
> URL: https://issues.jboss.org/browse/JBIDE-15614
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.1.0.Final
> Environment: JBDS 7.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Beta1
>
>
> 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0.
> 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2
> Let me know if you want subtasks for these two.
--
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
12 years, 6 months
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2623:
----------------------------------
Install grinder is happy for JBT in 4.1.x and master, but still timing out for JBDS. See JBIDE-15612
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Alpha2, 7.1.0.Beta1
>
> Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15482:
------------------------------------
1. Policy as coded today is "keep anything newer than 5 days old" and "if nothing newer than 5 days, keep 1 newest build only".
2. Yes.
3. No, we will be migrating from /staging/<jobName>/all/repo to /staging/CI/<jobName><buildID>/all/repo>
The composite site will also change, so that we can retain the old approach if needed and rollback if necessary:
old: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1....
old: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/
new: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1....
new: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/master/
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.1.Alpha2
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15509:
------------------------------------
TODO:
Probably want to update these pages:
https://www.jboss.org/tools/download/stable/4_1
https://www.jboss.org/tools/download/dev/4_1_x
with a note about:
{quote}
The createTempFile issue has been fixed in Java 8 and is set to be included in Java 7 update 45: https://bugs.openjdk.java.net/browse/JDK-8025128 and the Backports section.
Recommendation is to use a version of Oracle JDK 7 up to and including 1.7.0_39 or 1.7.0_45 and after.
{quote}
> prepare for JBDS 7.0.1 patch release
> ------------------------------------
>
> Key: JBIDE-15509
> URL: https://issues.jboss.org/browse/JBIDE-15509
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: updatesite
> Affects Versions: 4.1.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.1.Final
>
> Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png
>
>
> Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA:
> 1. branch jbosstools-central from 4.1.x to 4.1.0.x
> 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources)
> 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch
> 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg.,
> http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1....
> 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x
> 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0)
> 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration:
> {code}
> jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
> jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (JBTIS-182) Publish to ModeShape: Finish Button Disabled
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-182?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-182:
-----------------------------
Assignee: Dan Florian
> Publish to ModeShape: Finish Button Disabled
> --------------------------------------------
>
> Key: JBTIS-182
> URL: https://issues.jboss.org/browse/JBTIS-182
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: modeshape
> Affects Versions: 4.1.3
> Environment: JBDS 7.0.0.GA, JBoss Tools 4.1.3.Beta3, EAP 6.1 (in DV 6.0.0)
> Reporter: Lucie Fabrikova
> Assignee: Dan Florian
> Attachments: modeshape.png
>
>
> If no publish area is created, it cannot be created in dialog "Publish to ModeShape", via rght-click Modeshape->Publish.
> 1. start EAP 6.1 server
> 2. create new Modeshape server (http://localhost:8080/modeshape-rest, admin/admin)
> 3. rght-click a project, Modeshape -> Publish
> 4. dialog "Publish to ModeShape" appears, with warning "A publish area must be selected. If there aren't any to choose from, you can create one here or in the ModeShape View"
> 5. click to add new Publish Area
> 6. button "Finish" is still disabled
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15576) CLONE - Software/Update page - Cannot create temporary directory
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15576?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15576:
----------------------------------
Description:
Recently, Software/Update page of JBoss Central stopped working (No Connectors Found).
Error log:
{noformat}
Cannot download bundle at http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...: Unable to create temporary file
{noformat}
{noformat}
a.io.IOException: Unable to create temporary file
at java.io.File$TempDirectory.generateFile(File.java:1891)
at java.io.File.createTempFile(File.java:1979)
at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217)
at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
{noformat}
This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in 7.0.0.Final (4.1.0.Final), thus it's marked as blocker.
Upstream issue is https://bugs.openjdk.java.net/browse/JDK-8025128
was:
Recently, Software/Update page of JBoss Central stopped working (No Connectors Found).
Error log:
{noformat}
Cannot download bundle at http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...: Unable to create temporary file
{noformat}
{noformat}
a.io.IOException: Unable to create temporary file
at java.io.File$TempDirectory.generateFile(File.java:1891)
at java.io.File.createTempFile(File.java:1979)
at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217)
at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
{noformat}
This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in 7.0.0.Final (4.1.0.Final), thus it's marked as blocker.
> CLONE - Software/Update page - Cannot create temporary directory
> ----------------------------------------------------------------
>
> Key: JBIDE-15576
> URL: https://issues.jboss.org/browse/JBIDE-15576
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Final, 4.1.1.Alpha1
> Reporter: Jakub Niedermertl
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.1.1.Alpha2
>
>
> Recently, Software/Update page of JBoss Central stopped working (No Connectors Found).
> Error log:
> {noformat}
> Cannot download bundle at http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...: Unable to create temporary file
> {noformat}
> {noformat}
> a.io.IOException: Unable to create temporary file
> at java.io.File$TempDirectory.generateFile(File.java:1891)
> at java.io.File.createTempFile(File.java:1979)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
> This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in 7.0.0.Final (4.1.0.Final), thus it's marked as blocker.
> Upstream issue is https://bugs.openjdk.java.net/browse/JDK-8025128
--
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
12 years, 6 months