[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-11065:
------------------------------------
Appear to be missing some files:
a) READMEs & category.xml
b) results.html
c) copied/renamed SNAPSHOT.zip -> site_assembly.zip (this one we can work around if we update publish.sh to handle other filename patterns)
!http://snag.gy/MBH7D.jpg!
> Replace build.xml by a Maven plugin
> -----------------------------------
>
> Key: JBIDE-11065
> URL: https://issues.jboss.org/browse/JBIDE-11065
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png
>
>
> In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning.
--
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, 7 months
[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-11065 at 3/27/13 4:37 PM:
-------------------------------------------------------------
Not sure we need to call the FetchZips for anything other than site/ and soa-site/ (previously called "custom.build" from build.xml). Feels like overkill for the webtools-site/, coretests-site/, and soatests-site/ (we didn't collect them previously for those sites - we only called "basic.build" from build.xml, so your adding it in for those is new). You did not enable it for soa-site/ however. It should be turned on there.
The big reason for not pulling all the zips for the webtools site is that it only depends on Base and Server, yet it's doing this (if I add <version>0.16.0-SNAPSHOT</version> into webtools-site/pom.xml):
{code}
[INFO] --- repository-utils:0.16.0-SNAPSHOT:fetch-zips-for-aggregate (generate-facade) @ org.jboss.tools.site.webtools ---
[INFO] Getting zips and metadata from repo 'http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_master'
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-base_master-Update-SNAPSHOT.zip
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-base_master-Sources-SNAPSHOT.zip
[INFO] Getting zips and metadata from repo 'http://download.jboss.org/jbosstools/builds/staging/jbosstools-birt_master'
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-birt_master-Update-SNAPSHOT.zip
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-birt_master-Sources-SNAPSHOT.zip
[INFO] Getting zips and metadata from repo 'http://download.jboss.org/jbosstools/builds/staging/jbosstools-central_ma...'
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-central_master-Update-SNAPSHOT.zip
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-central_master-Sources-SNAPSHOT.zip
[INFO] Getting zips and metadata from repo 'http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_master'
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-forge_master-Update-SNAPSHOT.zip
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-forge_master-Sources-SNAPSHOT.zip
[INFO] Getting zips and metadata from repo 'http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_...'
[INFO] Got /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/webtools-site/zips/all/jbosstools-hibernate_master-Update-SNAPSHOT.zip
{code}
Otherwise the PR looks OK at a first glance, but with the above issues. Need to review the new code in org.jboss.tools.tycho-plugins:repository-utils:0.16.0-SNAPSHOT to verify that the mojo does in fact do everything that the ant script previously did:
{quote}
- add.repo.properties :: use org.eclipse.wtp.releng.tools.addRepoProperties to add p2.statsURI and download.stats properties for a list of features
- remove.uncategorized.category
- remove.uninstallable (eg., central discovery feature)
- collect.zips :: look for http://download.jboss.org/jbosstools/builds/staging/<job_name>/logs/zip.list.txt; if found, load file get list of relative path zips to then fetch
- collect.metadata :: collect metadata (JOB_NAME, BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE), zip file names+sizes+md5sums
- create.results.html :: generate a results.html from a template + a bunch of variables, which links to test results, metadata, target platforms. Page is then copied into build folder when publish.sh runs from a job w/ .aggregate in the name
{quote}
was (Author: nickboldt):
Not sure we need to call the FetchZips for anything other than site/ and soa-site/ (previously called "custom.build" from build.xml). Feels like overkill for the webtools-site/, coretests-site/, and soatests-site/ (we didn't collect them previously for those sites - we only called "basic.build" from build.xml, so your adding it in for those is new). You did not enable it for soa-site/ however. It should be turned on there.
Otherwise the PR looks OK at a first glance, but with the above issues. Need to review the new code in org.jboss.tools.tycho-plugins:repository-utils:0.16.0-SNAPSHOT to verify that the mojo does in fact do everything that the ant script previously did:
{quote}
- add.repo.properties :: use org.eclipse.wtp.releng.tools.addRepoProperties to add p2.statsURI and download.stats properties for a list of features
- remove.uncategorized.category
- remove.uninstallable (eg., central discovery feature)
- collect.zips :: look for http://download.jboss.org/jbosstools/builds/staging/<job_name>/logs/zip.list.txt; if found, load file get list of relative path zips to then fetch
- collect.metadata :: collect metadata (JOB_NAME, BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE), zip file names+sizes+md5sums
- create.results.html :: generate a results.html from a template + a bunch of variables, which links to test results, metadata, target platforms. Page is then copied into build folder when publish.sh runs from a job w/ .aggregate in the name
{quote}
> Replace build.xml by a Maven plugin
> -----------------------------------
>
> Key: JBIDE-11065
> URL: https://issues.jboss.org/browse/JBIDE-11065
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png
>
>
> In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning.
--
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, 7 months
[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-11065:
------------------------------------
Forgot to update a pom:
{code}
cd ~/tru/jbosstools-build-sites/aggregate/webtools-site; mvn install -Pjbosstools-nightly-staging-composite,unified.target,maximum
[INFO] Building JBoss Tools - Web Tools 4.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:48.252s
[INFO] Finished at: Wed Mar 27 16:08:29 EDT 2013
[INFO] Final Memory: 39M/478M
[INFO] ------------------------------------------------------------------------
[ERROR] Could not find goal 'fetch-zips-for-aggregate' in plugin org.jboss.tools.tycho-plugins:repository-utils:0.16.0.CR1 among available goals generate-repository-facade -> [Help 1]
{code}
> Replace build.xml by a Maven plugin
> -----------------------------------
>
> Key: JBIDE-11065
> URL: https://issues.jboss.org/browse/JBIDE-11065
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png
>
>
> In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning.
--
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, 7 months
[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-11065 at 3/27/13 4:15 PM:
-------------------------------------------------------------
Forgot to update a pom to add <version>0.16.0-SNAPSHOT</version>:
{code}
cd ~/tru/jbosstools-build-sites/aggregate/webtools-site; mvn install -Pjbosstools-nightly-staging-composite,unified.target,maximum
[INFO] Building JBoss Tools - Web Tools 4.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:48.252s
[INFO] Finished at: Wed Mar 27 16:08:29 EDT 2013
[INFO] Final Memory: 39M/478M
[INFO] ------------------------------------------------------------------------
[ERROR] Could not find goal 'fetch-zips-for-aggregate' in plugin org.jboss.tools.tycho-plugins:repository-utils:0.16.0.CR1 among available goals generate-repository-facade -> [Help 1]
{code}
Also missing for soa-site/site/pom.xml and soatests-site/pom.xml
was (Author: nickboldt):
Forgot to update a pom:
{code}
cd ~/tru/jbosstools-build-sites/aggregate/webtools-site; mvn install -Pjbosstools-nightly-staging-composite,unified.target,maximum
[INFO] Building JBoss Tools - Web Tools 4.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:48.252s
[INFO] Finished at: Wed Mar 27 16:08:29 EDT 2013
[INFO] Final Memory: 39M/478M
[INFO] ------------------------------------------------------------------------
[ERROR] Could not find goal 'fetch-zips-for-aggregate' in plugin org.jboss.tools.tycho-plugins:repository-utils:0.16.0.CR1 among available goals generate-repository-facade -> [Help 1]
{code}
> Replace build.xml by a Maven plugin
> -----------------------------------
>
> Key: JBIDE-11065
> URL: https://issues.jboss.org/browse/JBIDE-11065
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png
>
>
> In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning.
--
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, 7 months
[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-11065:
------------------------------------
Not sure we need to call the FetchZips for anything other than site/ and soa-site/ (previously called "custom.build" from build.xml). Feels like overkill for the webtools-site/, coretests-site/, and soatests-site/ (we didn't collect them previously for those sites - we only called "basic.build" from build.xml, so your adding it in for those is new). You did not enable it for soa-site/ however. It should be turned on there.
Otherwise the PR looks OK at a first glance, but with the above issues. Need to review the new code in org.jboss.tools.tycho-plugins:repository-utils:0.16.0-SNAPSHOT to verify that the mojo does in fact do everything that the ant script previously did:
{quote}
- add.repo.properties :: use org.eclipse.wtp.releng.tools.addRepoProperties to add p2.statsURI and download.stats properties for a list of features
- remove.uncategorized.category
- remove.uninstallable (eg., central discovery feature)
- collect.zips :: look for http://download.jboss.org/jbosstools/builds/staging/<job_name>/logs/zip.list.txt; if found, load file get list of relative path zips to then fetch
- collect.metadata :: collect metadata (JOB_NAME, BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE), zip file names+sizes+md5sums
- create.results.html :: generate a results.html from a template + a bunch of variables, which links to test results, metadata, target platforms. Page is then copied into build folder when publish.sh runs from a job w/ .aggregate in the name
{quote}
> Replace build.xml by a Maven plugin
> -----------------------------------
>
> Key: JBIDE-11065
> URL: https://issues.jboss.org/browse/JBIDE-11065
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png
>
>
> In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning.
--
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, 7 months
[JBoss JIRA] (JBDS-2501) App code and config migration to EAP 6 (QuickFixes, refactoring)
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2501?page=com.atlassian.jira.plugin.... ]
Ondrej Zizka updated JBDS-2501:
-------------------------------
Summary: App code and config migration to EAP 6 (QuickFixes, refactoring) (was: App code and config migration to EAP 6 (QuckFixes, refactoring))
> App code and config migration to EAP 6 (QuickFixes, refactoring)
> ----------------------------------------------------------------
>
> Key: JBDS-2501
> URL: https://issues.jboss.org/browse/JBDS-2501
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Ondrej Zizka
> Labels: eap6, migration
> Attachments: NetBeans-analyzers-FS.png, NetBeans-analyzers.png
>
>
> This feature would identify
> 1) configuration bits
> 2) source code constructs
> 3) old API usage
> and help migrating these to EAP 6 or later, in the form of QuickFixes and refactoring dialogs.
--
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, 7 months
[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13869:
------------------------------------
Of course in the case of JBDS 6.0.1 we really wanted to rebuild, not just re-test, because of the fact that TP contents are INCLUDED in JBDS installer.
> Find a way to run testsuite against existing builds but with different TP without requiring publishing
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13869
> URL: https://issues.jboss.org/browse/JBIDE-13869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.0.2.Final, 4.1.0.Alpha2
>
>
> Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again.
> Possible options:
> 1) Create new testsuite that depends on all other testsuites and run them in surefire test.
> 2) use something else than surefire to run the already built testsuites.
--
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, 7 months