[JBoss JIRA] (JBIDE-14711) Promotion process/script loses build metadata?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-14711:
----------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
As per the email I sent announcing Beta1b, here's the folder with the build & metadata:
http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core/
Updates go in /updates/
Builds go in /builds/
Also...
Discovery goes in /discovery/
Requirements go in /updates/requirements/
Target Platforms go in /targetplatforms/
> Promotion process/script loses build metadata?
> ----------------------------------------------
>
> Key: JBIDE-14711
> URL: https://issues.jboss.org/browse/JBIDE-14711
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng, updatesite
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> When promoting an aggregation build to nightly, metadata disappear. The only metadata available is the build ID (that we can read in qualifier) but this is not enough as Jenkins build are volatile.
> Loss of these metadata makes that it's not possible to find out which commit was used to build an aggregated component.
> We should copy metadata along with update-sites.
--
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, 10 months
[JBoss JIRA] (JBIDE-14711) Promotion process/script loses build metadata?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-14711:
-----------------------------------
Assignee: Nick Boldt (was: Mickael Istria)
Component/s: Build/Releng
updatesite
> Promotion process/script loses build metadata?
> ----------------------------------------------
>
> Key: JBIDE-14711
> URL: https://issues.jboss.org/browse/JBIDE-14711
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng, updatesite
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> When promoting an aggregation build to nightly, metadata disappear. The only metadata available is the build ID (that we can read in qualifier) but this is not enough as Jenkins build are volatile.
> Loss of these metadata makes that it's not possible to find out which commit was used to build an aggregated component.
> We should copy metadata along with update-sites.
--
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, 10 months
[JBoss JIRA] (JBDS-2618) JBDS 7.0 - sources .zip - includes many duplicate files
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2618?page=com.atlassian.jira.plugin.... ]
Len DiMaggio closed JBDS-2618.
------------------------------
Verified with jbdevstudio-product-sources-7.0.0.Beta1-v20130529-0631-B257.zip
> JBDS 7.0 - sources .zip - includes many duplicate files
> -------------------------------------------------------
>
> Key: JBDS-2618
> URL: https://issues.jboss.org/browse/JBDS-2618
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 7.0.0.Alpha2
> Environment: 7.0.0.Alpha2-v20130424-2146-B202
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> For example:
> unzip -t jbdevstudio-product-sources-7.0.0.Alpha2-v20130424-2146-B202.zip | grep twiddle
> testing: devstudio/product/installer/src/test-resources/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.5.0.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.5.0.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> unzip -t jbdevstudio-product-sources-7.0.0.Alpha2-v20130424-2146-B202.zip | grep twiddle
> testing: devstudio/product/installer/src/test-resources/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.5.0.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/jboss-soa-p.5.0.0/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-3.2.8.SP1/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-4.0.5.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.2.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-as-4.2.3.GA/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-eap-4.3.0.GA_CP1/jboss-as/bin/twiddle.jar OK
> testing: devstudio/product/installer/src/test-resources/servers/servers/jboss-soa-p.4.3.0/jboss-as/bin/twiddle.jar OK
> unzip jbdevstudio-product-sources-7.0.0.Alpha2-v20130424-2146-B202.zip | tee theLog.txt
> Archive: jbdevstudio-product-sources-7.0.0.Alpha2-v20130424-2146-B202.zip
> replace devstudio/product/.gitignore? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/.gitignore
> replace devstudio/product/README.Central.localhost.testing.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/README.Central.localhost.testing.txt
> replace devstudio/product/README.Central.milestone.testing.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/README.Central.milestone.testing.txt
> replace devstudio/product/audit-versions/.gitignore? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/audit-versions/.gitignore
> replace devstudio/product/audit-versions/README.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/audit-versions/README.txt
> replace devstudio/product/audit-versions/build.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/audit-versions/build.xml
> replace devstudio/product/audit-versions/exclude_list.txt_DISABLED? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/audit-versions/exclude_list.txt_DISABLED
> replace devstudio/product/audit-versions/include_list.txt_DISABLED? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/audit-versions/include_list.txt_DISABLED
> replace devstudio/product/audit-versions/org.eclipse.pde.api.tools.prefs? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/audit-versions/org.eclipse.pde.api.tools.prefs
> replace devstudio/product/discovery/README.md? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating: devstudio/product/discovery/README.md
--
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, 10 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-14544:
--------------------------------------
Still seeing the same issue:
!ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2013-05-31 10:18:43.863
!MESSAGE Error generating the native android project
!STACK 0
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:947)
at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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, 10 months
[JBoss JIRA] (JBIDE-14711) Promotion process/script loose build metadata
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-14711:
----------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
> Promotion process/script loose build metadata
> ---------------------------------------------
>
> Key: JBIDE-14711
> URL: https://issues.jboss.org/browse/JBIDE-14711
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> When promoting an aggregation build to nightly, metadata disappear. The only metadata available is the build ID (that we can read in qualifier) but this is not enough as Jenkins build are volatile.
> Loss of these metadata makes that it's not possible to find out which commit was used to build an aggregated component.
> We should copy metadata along with update-sites.
--
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, 10 months
[JBoss JIRA] (JBIDE-14711) Promotion process/script loses build metadata?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-14711:
-------------------------------
Summary: Promotion process/script loses build metadata? (was: Promotion process/script loose build metadata)
> Promotion process/script loses build metadata?
> ----------------------------------------------
>
> Key: JBIDE-14711
> URL: https://issues.jboss.org/browse/JBIDE-14711
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> When promoting an aggregation build to nightly, metadata disappear. The only metadata available is the build ID (that we can read in qualifier) but this is not enough as Jenkins build are volatile.
> Loss of these metadata makes that it's not possible to find out which commit was used to build an aggregated component.
> We should copy metadata along with update-sites.
--
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, 10 months