[jbosstools-issues] [JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names
Nick Boldt (JIRA)
issues at jboss.org
Fri Jan 24 10:54:28 EST 2014
[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938613#comment-12938613 ]
Nick Boldt commented on JBDS-2669:
----------------------------------
Cleaned out archived p2 metadata as per https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/faq.md#what-if-ive-already-built-something-locally-but-i-want-to-build-against-the-server-version-instead-of-my-local-repo:
{code}
rm -f rm ~/.m2/repository/.meta/p2*
{code}
Then built using -U flag to force update, using instructions in the root pom.xml (all the extra flags are unnecessary but will control if eap bundles are built and how things are named):
{code:title=https://github.com/nickboldt/jbdevstudio-product/blob/00d21efcfa5ee377d1de8a925ad3fa657a6c7242/pom.xml#L108}
mvn clean install -P hudson,eap,pack200 -Dtpc.version=4.40.0.Alpha2-SNAPSHOT -DBUILD_NUMBER=440002 -DJOB_NAME=devstudio.product_master -Dupdate.site.description="Development Milestone" -U
{code}
You can also build with just this, but you won't get an EAP bundle:
{code}
mvn clean install
{code}
> rename/refactor JBDS product .feature / plugin / .product to have less confusing names
> --------------------------------------------------------------------------------------
>
> Key: JBDS-2669
> URL: https://issues.jboss.org/browse/JBDS-2669
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 8.0.0.Alpha2
>
> Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png
>
>
> We should consider some better names for these artifacts so they collide less and are more obvious which is which.
> 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/com.jboss.jbds.product.feature/feature.properties
> ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site
> 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/plugin.properties and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/META-INF/MANIFEST.MF
> ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true
> 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.jboss.jbds.product
> ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product"
--
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
More information about the jbosstools-issues
mailing list